Quote: Originally Posted by
hondamac 
Is there anything I have to do it? A setting I have to change?
There are not that many settings you may affect, I am afraid. You can just make sure the device itself works properly and contact RB support if you are sure the device is OK. To check the receiver works, follow these steps:
1. using terminal, run
This will list all serial ports/devices that OS X can see and access using POSIX API. This means modems, GPS receivers etc. In my case, the list looks like this:
Code:
crw-rw-rw- 1 root wheel 10, 11 Oct 16 12:06 /dev/cu.Bluetooth-Modem
crw-rw-rw- 1 root wheel 10, 9 Oct 16 12:06 /dev/cu.Bluetooth-PDA-Sync
crw-rw-rw- 1 root wheel 10, 3 Oct 16 12:06 /dev/cu.E6r-Dial-UpNetworking
crw-rw-rw- 1 root wheel 10, 13 Oct 16 12:06 /dev/cu.K750i-SerialPort
crw-rw-rw- 1 root wheel 10, 1 Oct 16 12:06 /dev/cu.NokiaLD-3W-DevB
You can also use the serial profiler to see whether the computer recognizes the device. If you are sure the device is visible, you will need to check that it actually sends data. To do this, use minicom or a similar serial terminal application, connect to the GPS receiver's device (like the /dev/cu.NokiaLD-3W-DevB in my example above) using 4800, 8, N, 1 and look at the terminal. If the device works OK, it should start to print the raw NMEA data to the output. If it does not work, you may try to change the speed to 9600 (although 4800 is the NMEA standard).
If you are not seeing any sensible output in the terminal or even can't see the device in /dev/ folder, your problem is in the receiver or its driver. If you can get the data in the terminal, the problem is with Routebuddy and you should contact their technical support, which is pretty good.