FHEM on OS X - Versionsgeschichte

AndreasMohr: Correct missing reference

2018-02-06T20:39:50Z

Correct missing reference

← Nächstältere Version		Version vom 6. Februar 2018, 22:39 Uhr
Zeile 12:		Zeile 12:

	== USB Driver for FHZ 1X00 PC ==		== USB Driver for FHZ 1X00 PC ==
	[[FHZ 1000]] PC (and the newer version FHZ 1300 PC) is an [[Interface\|interface]] device between the FS20 radio protocol and a PC via an USB interface. FHZ 1000 PC has a fairly straight forward structure based on standard components. It is built around a PIC16F628 processor and uses a FT232AM (FT8U232AM) chip from FTDI for USB communication. The vendor of this chip provides drivers for Mac OS X 10.3, 10.4, 10.5 and 10.6. Please download and install the most recent version from their website: [http://www.ftdichip.com/Drivers/VCP.htm FTDIUSBSerialDriver]		[[FHZ 1000]] PC (and the newer version [[FHZ_nn00\|FHZ 1300 PC]]) is an [[Interface\|interface]] device between the FS20 radio protocol and a PC via an USB interface. FHZ 1000 PC has a fairly straight forward structure based on standard components. It is built around a PIC16F628 processor and uses a FT232AM (FT8U232AM) chip from FTDI for USB communication. The vendor of this chip provides drivers for Mac OS X 10.3, 10.4, 10.5 and 10.6. Please download and install the most recent version from their website: [http://www.ftdichip.com/Drivers/VCP.htm FTDIUSBSerialDriver]

	When the computer has rebooted, plug in the device and check if the device is installed properly.		When the computer has rebooted, plug in the device and check if the device is installed properly.

AndreasMohr: Typos/Spelling

2018-02-06T20:27:16Z

Typos/Spelling

← Nächstältere Version		Version vom 6. Februar 2018, 22:27 Uhr
Zeile 15:		Zeile 15:

	When the computer has rebooted, plug in the device and check if the device is installed properly.		When the computer has rebooted, plug in the device and check if the device is installed properly.
	Take a look at the the OS X System Logfile (/var/log/system.log). The FHZ1000 device should ~~recognize~~ by the system as follows:		Take a look at the the OS X System Logfile (/var/log/system.log). The FHZ1000 device should have been recognized by the system as follows:
	:<code>kernel [0]: FTDIUSBSerialDriver: 0 403f06f start - ok</code>		:<code>kernel [0]: FTDIUSBSerialDriver: 0 403f06f start - ok</code>

Zeile 50:		Zeile 50:
	* Ensure that the option for command line development, which is labeled Unix Development in the Xcode 3.x installer, is checked.		* Ensure that the option for command line development, which is labeled Unix Development in the Xcode 3.x installer, is checked.

	== SerialPort Perl ~~Modul~~ ==		== SerialPort Perl Module ==
	SerialPort for Linux is a user interface to Serial API calls. The module provides an object-based user interface essentially identical to the one provided by the Win32::SerialPort module.		SerialPort for Linux is a user interface to Serial API calls. The module provides an object-based user interface essentially identical to the one provided by the Win32::SerialPort module.
	To install this ~~modul~~ you can get the right sources from the CPAN Website.		To install this module you can get the right sources from the CPAN Website.

	Open the OS X Terminal Application and execute the following command:		Open the OS X Terminal Application and execute the following command:
Zeile 63:		Zeile 63:

	=== Some testing ===		=== Some testing ===
	Now you should be ready to use the Module ''Device::SerialPort''. If have already configured your ~~Hardware~~ (CUN, CUL, FHZ1000...) you can check the functionality with a little Perl script:		Now you should be ready to use the Module ''Device::SerialPort''. If you have already configured your hardware (CUN, CUL, FHZ1000...) you can check the functionality with a little Perl script:
	[http://fhz4linux.info/tiki-download_file.php?fileId=4 elv.pl]		[http://fhz4linux.info/tiki-download_file.php?fileId=4 elv.pl]

Zeile 105:		Zeile 105:
	=== Modify fhem.cfg ===		=== Modify fhem.cfg ===
	You have to modify the main configuration file on your personal effort.		You have to modify the main configuration file on your personal effort.
	There are many samples an descriptions on the web...		There are many samples and descriptions on the web...

	== Run FHEM ==		== Run FHEM ==
Zeile 113:		Zeile 113:

	=== Launchd ===		=== Launchd ===
	The more modern way would be to create a ~~lauch~~ daemon like the following example.		The more modern way would be to create a launch daemon like the following example.

	<nowiki><?xml version="1.0" encoding="UTF-8"?>		<nowiki><?xml version="1.0" encoding="UTF-8"?>

Markusbloch: Ersetzung von Forum-Links mit Vorlage Link2Forum

2017-03-19T19:46:27Z

Ersetzung von Forum-Links mit Vorlage Link2Forum

← Nächstältere Version		Version vom 19. März 2017, 21:46 Uhr
Zeile 139:		Zeile 139:
	You might run into some permission problems if not running fhem as "root", but running as root is not a good idea, so go out and fix the file permissions for the user fhem runs as.		You might run into some permission problems if not running fhem as "root", but running as root is not a good idea, so go out and fix the file permissions for the user fhem runs as.

	'''Simpler:''' the tar file referenced in this ~~[http://forum.fhem.de/index.php/topic,~~19989~~.msg142757.html#msg142757~~ forum post] can be unpacked to <code>/Library/StartupItems</code>. In <code>/Library/StartupItems/FHEM/FHEM</code> the path and fhemuser should be adjusted to your installation.		'''Simpler:''' the tar file referenced in this {{Link2Forum\|Topic=19989\|Message=142757\|LinkText=forum post}} can be unpacked to <code>/Library/StartupItems</code>. In <code>/Library/StartupItems/FHEM/FHEM</code> the path and fhemuser should be adjusted to your installation.

	[[Kategorie:HOWTOS]]		[[Kategorie:HOWTOS]]
	[[Kategorie:OSX]]		[[Kategorie:OSX]]

Krikan: FHEM(R)

2017-01-24T14:58:37Z

FHEM(R)

← Nächstältere Version		Version vom 24. Januar 2017, 16:58 Uhr
Zeile 1:		Zeile 1:
	Most of the the time ~~Fhem~~ is installed on Linux based systems. That could be the reason why most of the HowTos, FAQs and Tips are dealing with Unix issues. As you may know, Apple's OS X is based on FreeBSD (a UNIX derivate) which is similar to Linux to some extent and therefore it is no big deal to run '''~~Fhem~~ on OS X'''.		Most of the the time FHEM is installed on Linux based systems. That could be the reason why most of the HowTos, FAQs and Tips are dealing with Unix issues. As you may know, Apple's OS X is based on FreeBSD (a UNIX derivate) which is similar to Linux to some extent and therefore it is no big deal to run '''FHEM on OS X'''.

	In some sections an alternate (and simplified) installation method is also described and marked with "'''Simpler:'''"		In some sections an alternate (and simplified) installation method is also described and marked with "'''Simpler:'''"

	== Overview ==		== Overview ==
	To install ~~Fhem~~ on a Mac, you have to follow these steps:		To install FHEM on a Mac, you have to follow these steps:
	* Install USB Driver for FHZ 1X00 PC		* Install USB Driver for FHZ 1X00 PC
	* Install the C Compiler from XTools		* Install the C Compiler from XTools
	* Install SerialPort Sources from CPAN		* Install SerialPort Sources from CPAN
	* Modify ~~Fhem~~ Makefile		* Modify FHEM Makefile
	* Install ~~Fhem~~		* Install FHEM

	== USB Driver for FHZ 1X00 PC ==		== USB Driver for FHZ 1X00 PC ==
Zeile 32:		Zeile 32:

	=== Symbolic Link to ttyUSB0 ===		=== Symbolic Link to ttyUSB0 ===
	Because ~~Fhem~~ is talking to the device using ''/dev/ttyUSB0'', for better handling you should define a symbolic link: Open the OS X Terminal Application and execute the following command:		Because FHEM is talking to the device using ''/dev/ttyUSB0'', for better handling you should define a symbolic link: Open the OS X Terminal Application and execute the following command:
	:<code>$ sudo ln -s /dev/tty.usbserial-xxxxxx /dev/ttyUSB0</code>		:<code>$ sudo ln -s /dev/tty.usbserial-xxxxxx /dev/ttyUSB0</code>

	'''NOTE!''': Under specific circumstances, the symlink disappears after a reboot. If someone can solve this issue or knows the reason for that, please edit this paragraph!		'''NOTE!''': Under specific circumstances, the symlink disappears after a reboot. If someone can solve this issue or knows the reason for that, please edit this paragraph!

	The issue can simply be fixed by specifying the /dev/cu.usbmodem-xxxx instead of /dev/ttyUSB0 as the serial device in the ~~Fhem~~ [[Konfiguration\|configuration]].		The issue can simply be fixed by specifying the /dev/cu.usbmodem-xxxx instead of /dev/ttyUSB0 as the serial device in the FHEM [[Konfiguration\|configuration]].

	'''Simpler:''' OS X will give each device a unique device name. a device that is unplugged and reconnected will receive the same device file, so these unique names should be used in fhem instead of the symbolic links.		'''Simpler:''' OS X will give each device a unique device name. a device that is unplugged and reconnected will receive the same device file, so these unique names should be used in fhem instead of the symbolic links.
Zeile 75:		Zeile 75:
	Got: 4c09 [2]</nowiki>		Got: 4c09 [2]</nowiki>

	== Install ~~Fhem~~ ==		== Install FHEM ==
	Download the most recent version of ~~Fhem~~ from [http://www.fhem.de Rudi's Website],		Download the most recent version of FHEM from [http://www.fhem.de Rudi's Website],
	extract the archive, and install the Software as described.		extract the archive, and install the Software as described.

Zeile 107:		Zeile 107:
	There are many samples an descriptions on the web...		There are many samples an descriptions on the web...

	== Run ~~Fhem~~ ==		== Run FHEM ==
	To make sure that ~~Fhem~~ Server is starting on every Reboot, just place a start script under /Library/StartupItems.		To make sure that FHEM Server is starting on every Reboot, just place a start script under /Library/StartupItems.

	Create a startup script:		Create a startup script:

Krikan: Krikan verschob die Seite Fhem on OS X nach FHEM on OS X: FHEM(TM)

2017-01-20T10:11:45Z

Krikan verschob die Seite Fhem on OS X nach FHEM on OS X: FHEM(TM)

← Nächstältere Version		Version vom 20. Januar 2017, 12:11 Uhr
(kein Unterschied)

Justme: added simplified versions of some of the installation steps

2014-04-30T22:58:38Z

added simplified versions of some of the installation steps

← Nächstältere Version		Version vom 1. Mai 2014, 00:58 Uhr
Zeile 1:		Zeile 1:
	Most of the the time Fhem is installed on Linux based systems. That could be the reason why most of the HowTos, FAQs and Tips are dealing with Unix issues. As you may know, Apple's OS X is based on FreeBSD (a UNIX derivate) which is similar to Linux to some extent and therefore it is no big deal to run '''Fhem on OS X'''.		Most of the the time Fhem is installed on Linux based systems. That could be the reason why most of the HowTos, FAQs and Tips are dealing with Unix issues. As you may know, Apple's OS X is based on FreeBSD (a UNIX derivate) which is similar to Linux to some extent and therefore it is no big deal to run '''Fhem on OS X'''.

			In some sections an alternate (and simplified) installation method is also described and marked with "'''Simpler:'''"

	== Overview ==		== Overview ==
Zeile 37:		Zeile 39:
	The issue can simply be fixed by specifying the /dev/cu.usbmodem-xxxx instead of /dev/ttyUSB0 as the serial device in the Fhem [[Konfiguration\|configuration]].		The issue can simply be fixed by specifying the /dev/cu.usbmodem-xxxx instead of /dev/ttyUSB0 as the serial device in the Fhem [[Konfiguration\|configuration]].

	OS X will give each device a unique device name. a device that is unplugged and reconnected will receive the same device file, so these unique names should be used in fhem instead of the symbolic links.		'''Simpler:''' OS X will give each device a unique device name. a device that is unplugged and reconnected will receive the same device file, so these unique names should be used in fhem instead of the symbolic links.

	== GNU C Compiler ==		== GNU C Compiler ==
Zeile 98:		Zeile 100:

	works on OSX 10.9.1		works on OSX 10.9.1

			'''Simpler:''' just unpack the source tar and move/rename the unpacked top-level directory to the location that you want. keep all subdirectories as they are.

	=== Modify fhem.cfg ===		=== Modify fhem.cfg ===
Zeile 134:		Zeile 138:

	You might run into some permission problems if not running fhem as "root", but running as root is not a good idea, so go out and fix the file permissions for the user fhem runs as.		You might run into some permission problems if not running fhem as "root", but running as root is not a good idea, so go out and fix the file permissions for the user fhem runs as.

			'''Simpler:''' the tar file referenced in this [http://forum.fhem.de/index.php/topic,19989.msg142757.html#msg142757 forum post] can be unpacked to <code>/Library/StartupItems</code>. In <code>/Library/StartupItems/FHEM/FHEM</code> the path and fhemuser should be adjusted to your installation.

	[[Kategorie:HOWTOS]]		[[Kategorie:HOWTOS]]
	[[Kategorie:OSX]]		[[Kategorie:OSX]]

Ph1959de: Diverse kleine Korrekturen

2014-02-17T08:07:33Z

Diverse kleine Korrekturen

← Nächstältere Version		Version vom 17. Februar 2014, 10:07 Uhr
Zeile 1:		Zeile 1:
	Most of the the time Fhem is installed on Linux based systems. That could be the reason why most of the HowTos, FAQs and Tips are dealing with Unix issues. As you may know, Apple's OS X is based on FreeBSD ( a UNIX ~~Derivate~~) which is similar zo Linux to some ~~extend~~ and therefore it is no big deal to run Fhem on OS X.		Most of the the time Fhem is installed on Linux based systems. That could be the reason why most of the HowTos, FAQs and Tips are dealing with Unix issues. As you may know, Apple's OS X is based on FreeBSD (a UNIX derivate) which is similar to Linux to some extent and therefore it is no big deal to run '''Fhem on OS X'''.


	~~= HOWTO install Fhem on OS X =~~
	~~== Description ==~~
	~~This HOWTO describes the necessary steps to install Fhem on a Mac running OS X. Especially Fhem in combination with the FHZ 1000 Device~~.

	== Overview ==		== Overview ==
	To install Fhem on a Mac, you have to follow these steps:		To install Fhem on a Mac, you have to follow these steps:

	* Install USB Driver for FHZ 1X00 PC		* Install USB Driver for FHZ 1X00 PC
	* Install the C Compiler from XTools		* Install the C Compiler from XTools
Zeile 14:		Zeile 8:
	* Modify Fhem Makefile		* Modify Fhem Makefile
	* Install Fhem		* Install Fhem

	== USB Driver for FHZ 1X00 PC ==		== USB Driver for FHZ 1X00 PC ==
	FHZ 1000 PC (and the newer version FHZ 1300 PC) is an interface device between the FS20 radio protocol and a PC via an USB interface.		[[FHZ 1000]] PC (and the newer version FHZ 1300 PC) is an [[Interface\|interface]] device between the FS20 radio protocol and a PC via an USB interface. FHZ 1000 PC has a fairly straight forward structure based on standard components. It is built around a PIC16F628 processor and uses a FT232AM (FT8U232AM) chip from FTDI for USB communication. The vendor of this chip provides drivers for Mac OS X 10.3, 10.4, 10.5 and 10.6. Please download and install the most recent version from their website: [http://www.ftdichip.com/Drivers/VCP.htm FTDIUSBSerialDriver]
	FHZ 1000 PC has a fairly straight forward structure based on standard components. It is ~~build~~ around a PIC16F628 processor and uses a FT232AM (FT8U232AM) chip from FTDI for USB communication.
	The vendor of this chip provides drivers for Mac OS X 10.3, 10.4, 10.5 and 10.6. Please download and install the most recent version from their website: [http://www.ftdichip.com/Drivers/VCP.htm FTDIUSBSerialDriver]

	When the computer has rebooted, plug in the device and check if the device is installed properly.		When the computer has rebooted, plug in the device and check if the device is installed properly.
	Take a look at the the OS X System Logfile (/var/log/system.log). The FHZ1000 device should recognize by the system as follows:		Take a look at the the OS X System Logfile (/var/log/system.log). The FHZ1000 device should recognize by the system as follows:
			:<code>kernel [0]: FTDIUSBSerialDriver: 0 403f06f start - ok</code>

	~~<nowiki>kernel [0]: FTDIUSBSerialDriver: 0 403f06f start - ok</nowiki>~~
	If not, please check the device and the USB cable on a different system (e.g. Linux > 2.6).		If not, please check the device and the USB cable on a different system (e.g. Linux > 2.6).

	After that, you will see two entries in the ''/dev''directory. To check this, open the OS X Terminal ~~Application~~ and execute the following command:		After that, you will see two entries in the ''/dev''directory. To check this, open the OS X Terminal application and execute the following command:

	~~<nowiki>~~$ls /dev/cu.*		$ls /dev/cu.*
	/dev/cu.usbserial-xxxxxxxx		/dev/cu.usbserial-xxxxxxxx
	$ls /dev/tty.*		$ls /dev/tty.*
	/dev/tty.usbserial-xxxxxxxx~~</nowiki>~~		/dev/tty.usbserial-xxxxxxxx
	~~where ''xxxxxxxx''is either the device's serial number.~~

	Now you can talk to the box via ''/dev/tty.usbserial-xxxx''using the FS20 Protocol.		where ''xxxxxxxx''is the device's serial number.

			Now you can talk to the box via ''/dev/tty.usbserial-xxxx'' using the FS20 Protocol.

	=== Symbolic Link to ttyUSB0 ===		=== Symbolic Link to ttyUSB0 ===
	Because Fhem is talking to the device using ''/dev/ttyUSB0'', for better handling you should define a symbolic link: Open the OS X Terminal Application and execute the following command:		Because Fhem is talking to the device using ''/dev/ttyUSB0'', for better handling you should define a symbolic link: Open the OS X Terminal Application and execute the following command:
			:<code>$ sudo ln -s /dev/tty.usbserial-xxxxxx /dev/ttyUSB0</code>

	~~:<code>$ sudo ln -s /dev/tty.usbserial-xxxxxx /dev/ttyUSB0</code>~~		'''NOTE!''': Under specific circumstances, the symlink disappears after a reboot. If someone can solve this issue or knows the reason for that, please edit this paragraph!
	'''NOTE!''': Under specific circumstances, the symlink disappears after a reboot. If someone can solve this issue or ~~know~~ the reason for that, please edit this paragraph!

	The issue can simply be fixed by specifying the /dev/cu.usbmodem-xxxx instead of /dev/ttyUSB0 as the serial device in ~~fhem.cfg~~.		The issue can simply be fixed by specifying the /dev/cu.usbmodem-xxxx instead of /dev/ttyUSB0 as the serial device in the Fhem [[Konfiguration\|configuration]].

	OS X will give each device a unique device name. a device that is unplugged and reconnected will receive the same device file. so these unique names should be used in fhem instead of the symbolic links.		OS X will give each device a unique device name. a device that is unplugged and reconnected will receive the same device file, so these unique names should be used in fhem instead of the symbolic links.

	== GNU C Compiler ==		== GNU C Compiler ==
Zeile 65:		Zeile 59:
	[cpan[1]>] install Device::SerialPort		[cpan[1]>] install Device::SerialPort
	[cpan[1]>] quit</nowiki>		[cpan[1]>] quit</nowiki>

	=== Some testing ===		=== Some testing ===
	Now you should be ready to use the Module ''Device::SerialPort''. If have already configured your Hardware (CUN, CUL, FHZ1000...) you can check the functionality with a little Perl script:		Now you should be ready to use the Module ''Device::SerialPort''. If have already configured your Hardware (CUN, CUL, FHZ1000...) you can check the functionality with a little Perl script:
Zeile 79:		Zeile 74:

	== Install Fhem ==		== Install Fhem ==
	Download the most recent version of Fhem from [http://www.~~koeniglich~~.de~~/fhem/fhem.html~~ Rudi's Website].		Download the most recent version of Fhem from [http://www.fhem.de Rudi's Website],
	~~Extract~~ the archive and install the Software as described ~~on the Website~~.		extract the archive, and install the Software as described.

	You most likely will have fhem installed in some custom directory, so you need to adapt the first lines in the Makefile, for example change to:		You most likely will have fhem installed in some custom directory, so you need to adapt the first lines in the Makefile, for example change to:
Zeile 139:		Zeile 134:

	You might run into some permission problems if not running fhem as "root", but running as root is not a good idea, so go out and fix the file permissions for the user fhem runs as.		You might run into some permission problems if not running fhem as "root", but running as root is not a good idea, so go out and fix the file permissions for the user fhem runs as.


	[[Kategorie:HOWTOS]]		[[Kategorie:HOWTOS]]
	[[Kategorie:OSX]]		[[Kategorie:OSX]]

Soulman am 17. Februar 2014 um 02:24 Uhr

2014-02-17T02:24:37Z

← Nächstältere Version		Version vom 17. Februar 2014, 04:24 Uhr
Zeile 1:		Zeile 1:
	Most of the the time Fhem is installed on Linux based systems. That could be the reason why most of the HowTos, FAQs and Tips are dealing with Unix issues. As you may know, Apple's OS X is based on ~~Unix as well~~ and it is no big deal to run Fhem on OS X.		Most of the the time Fhem is installed on Linux based systems. That could be the reason why most of the HowTos, FAQs and Tips are dealing with Unix issues. As you may know, Apple's OS X is based on FreeBSD ( a UNIX Derivate) which is similar zo Linux to some extend and therefore it is no big deal to run Fhem on OS X.

Ph1959de: Kleinere Korrekturen

2014-02-09T19:01:01Z

Kleinere Korrekturen

← Nächstältere Version		Version vom 9. Februar 2014, 21:01 Uhr
Zeile 36:		Zeile 36:

	=== Symbolic Link to ttyUSB0 ===		=== Symbolic Link to ttyUSB0 ===
	Because Fhem is talking to the device using ''/dev/ttyUSB0', for better handling you should define a symbolic link: ''Open the OS X Terminal Application and execute the following command:		Because Fhem is talking to the device using ''/dev/ttyUSB0'', for better handling you should define a symbolic link: Open the OS X Terminal Application and execute the following command:

	~~<nowiki>$ sudo ln -s /dev/tty.usbserial-xxxxxx /dev/ttyUSB0</nowiki>~~
	~~'''NOTE!'''Under specific circumstances, the symlink disappears after a reboot.~~
	~~If someone can solve this issue or know the reason for that, please edit this paragraph!~~


			:<code>$ sudo ln -s /dev/tty.usbserial-xxxxxx /dev/ttyUSB0</code>
			'''NOTE!''': Under specific circumstances, the symlink disappears after a reboot. If someone can solve this issue or know the reason for that, please edit this paragraph!

	The issue can simply be fixed by specifying the /dev/cu.usbmodem-xxxx instead of /dev/ttyUSB0 as the serial device in fhem.cfg.		The issue can simply be fixed by specifying the /dev/cu.usbmodem-xxxx instead of /dev/ttyUSB0 as the serial device in fhem.cfg.


	OS X will give each device a unique device name. a device that is unplugged and reconnected will receive the same device file. so these unique names should be used in fhem instead of the symbolic links.		OS X will give each device a unique device name. a device that is unplugged and reconnected will receive the same device file. so these unique names should be used in fhem instead of the symbolic links.

	== GNU C Compiler ==		== GNU C Compiler ==
	Apple's brand-name for the 'developer tools' is 'XCode Tools', it is GCC and a few other bits and bobs. To install it is a simple matter, you simply install the package on your OS X DVD. I'm led to believe the CD version of Mac OS X has a dedicated CD called 'X-Code Tools'.		Apple's brand-name for the 'developer tools' is 'XCode Tools', it is GCC and a few other bits and bobs. To install it is a simple matter, you simply install the package on your OS X DVD. I'm led to believe the CD version of Mac OS X has a dedicated CD called 'X-Code Tools'. If you have lost the DVD already then you can download X-code tools from [http://developer.apple.com/technologies/xcode.html Apple's website]. Although you must sign-in to be able to to get the file.
	If you have lost the DVD already then you can download X-code tools from [http://developer.apple.com/technologies/xcode.html Apple's website]. Although you must sign-in to be able to to get the file.

			'''NOTE''': Always make sure to install the latest available version of Xcode Tools for your Mac OS X release; using outdated versions of Xcode Tools may cause port install failures. Also note that Xcode Tools are not updated via Mac OS X's Software Update utility.
	'''NOTE!'''Always make sure to install the latest available version of Xcode Tools for your Mac OS X release; using outdated versions of Xcode Tools may cause port install failures. Also note that Xcode Tools are not updated via Mac OS X's Software Update utility.

	* Run the Xcode Tools package installer.		* Run the Xcode Tools package installer.
	* Click the button Customize, expand the Applications category and click the check box beside X11 SDK to add it to the default items.		* Click the button Customize, expand the Applications category and click the check box beside X11 SDK to add it to the default items.
	* Ensure that the option for command line development, which is labeled Unix Development in the Xcode 3.x installer, is checked.		* Ensure that the option for command line development, which is labeled Unix Development in the Xcode 3.x installer, is checked.



	== SerialPort Perl Modul ==		== SerialPort Perl Modul ==
Zeile 67:		Zeile 59:

	Open the OS X Terminal Application and execute the following command:		Open the OS X Terminal Application and execute the following command:
			:<code>sudo perl –MCPAN –e shell</code>
	<~~nowiki~~>sudo perl –MCPAN –e shell</~~nowiki~~>		If you do this the first time, Perl may ask you a few questions... just enter YES. At the end you will read something like ''cpan shell -- CPAN exploration and modules installation (v1.9205)''. Within the CPAN Shell, you have to execute the following two commands:
	If you do this the first time, Perl may ask you a few questions... just enter YES.
	At the end you will read something like ''cpan shell -- CPAN exploration and modules installation (v1.9205)''. Within the CPAN Shell, you have to execute the following two commands:

	<nowiki>[cpan[1]>] install Bundle::CPAN		<nowiki>[cpan[1]>] install Bundle::CPAN
Zeile 87:		Zeile 77:
	Got: 810fc9ae010284010807f8136e3118 [1]		Got: 810fc9ae010284010807f8136e3118 [1]
	Got: 4c09 [2]</nowiki>		Got: 4c09 [2]</nowiki>


	== Install Fhem ==		== Install Fhem ==
Zeile 104:		Zeile 93:

	<nowiki>sudo make install-pgm2</nowiki>		<nowiki>sudo make install-pgm2</nowiki>


	Comment fhainz:		Comment fhainz:
Zeile 115:		Zeile 103:

	works on OSX 10.9.1		works on OSX 10.9.1


	=== Modify fhem.cfg ===		=== Modify fhem.cfg ===

Justme: /* Symbolic Link to ttyUSB0 */

2014-02-09T18:10:46Z

Symbolic Link to ttyUSB0

← Nächstältere Version		Version vom 9. Februar 2014, 20:10 Uhr
Zeile 45:		Zeile 45:

	The issue can simply be fixed by specifying the /dev/cu.usbmodem-xxxx instead of /dev/ttyUSB0 as the serial device in fhem.cfg.		The issue can simply be fixed by specifying the /dev/cu.usbmodem-xxxx instead of /dev/ttyUSB0 as the serial device in fhem.cfg.


			OS X will give each device a unique device name. a device that is unplugged and reconnected will receive the same device file. so these unique names should be used in fhem instead of the symbolic links.

	== GNU C Compiler ==		== GNU C Compiler ==