ryandesign at macports.org
Thu Jan 16 19:34:12 PST 2014
On Jan 16, 2014, at 21:24, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Jan 16, 2014, at 21:09, Lenore Horner <LenoreHorner at sbcglobal.net> wrote:
>> On Jan 16, 2014, at 10:20, John Ruschmeyer <jruschme at gmail.com> wrote:
>>> I think you want /dev/pilot to be a symbolic link to the device for your serial port. Something like:
>>> # ln -s /dev/ttyUSB1 /dev/pilot
>> Doesn’t that mean I should have /dev/ttyUSB1 already? I don’t.
> I don’t either.
From the jpilot documentation:
> Serial Port Setup
> When syncing, J-Pilot uses the port and speed settings out of the J-Pilot preferences screen. If the port is blank then J-Pilot will use the PILOTPORT environment variables, as does pilot-link. If these are blank also then J-Pilot will default to /dev/pilot.
> It is recommended, but not necessary to make a link from /dev/pilot to the correct serial port. So, if your cradle is on COM1, this is /dev/ttyS0 under Linux. You could execute the command "ln -s /dev/ttyS0 /dev/pilot". COM2 is /dev/ttyS1, and so on. The Linux serial ports cua[n] are going away. You should use the ttyS[n] ports instead. USB ports are usually /dev/ttyUSB1, or /dev/usb/tts/1 (for devfs), but some devices use /dev/ttyUSB0, or /dev/usb/tts/0.
> You must also give non-root users permissions to access the serial port. The command to do this is (as root) "chmod 666 /dev/ttyS0" for the first serial port, ttyS1, for the second, and so on.
The mention of “/dev/ttyUSB1” could very well be a Linuxism not applicable to OS X. OS X might not expose the USB ports as a device; I don’t know. This post says it does not:
More information about the macports-users