Results 1 to 8 of 8

Thread: ROUTEBUDDY and GR-213 HOLUX???

  1. #1
    Low Bitrate
    Join Date
    Aug 2007
    Posts
    80

    ROUTEBUDDY and GR-213 HOLUX???

    Hi people,

    I just got my HOLUX 213 GPS, I downloaded the mac drivers, installed it, restarted...but I can't get ROUTEBUDDY to recognize it.

    Is there anything I have to do it? A setting I have to change?

    Thanks

  2. #2
    Low Bitrate
    Join Date
    Aug 2007
    Posts
    80

    Somebody PLEASE help **mac & GPS***

    I have a HOLUX GPS GR213 and I cannot connect to Routebuddy 1.4 I don't know why. The GPS is working just fine, I am running an intel mac. I've been inside and outside my home but I can't seem to bridge the gap between the two.

    Any suggestions?

  3. #3
    Low Bitrate
    Join Date
    Feb 2007
    Location
    Maryland
    Posts
    87
    "I've been inside and outside my home but I can't seem to bridge the gap between the two.
    "

    Not quite sure what you mean here. Are you saying you run routebuddy and it doesnt find your GPS unit?
    CarPC status:

    [XXXXXXXXXX] 100% Complete
    [XXXXXXXXXX] 100% Installed
    [XXXXXXXXXX] 100% Software

    CarPC v1.2 is now in effect. Software updates and hardware additions to come.

  4. #4
    QCar Creator Jirka Jirout's Avatar
    Join Date
    Jul 2005
    Location
    Netherlands
    Posts
    590
    Quote Originally Posted by hondamac View Post
    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
    Code:
    ls -l /dev/cu*
    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.

  5. #5
    Low Bitrate
    Join Date
    Aug 2007
    Posts
    80
    Yes, the holux light is blinking..which means it has acquired a fix. After that point though nothing happens. Routebuddy can't seem to recognize it. I thought maybe the issue was that I was indoors but nothing happens under the clear blue sky either. I don't know what the missing link is.

  6. #6
    Neither darque nor pervert DarquePervert's Avatar
    Join Date
    Apr 2004
    Location
    Elsewhere
    Posts
    13,948
    Quit crossposting, hondamac.
    Have you looked in the FAQ yet?
    How about the Wiki?



    Under normal circumstances, a signature would go here.

  7. #7
    Low Bitrate
    Join Date
    Aug 2007
    Posts
    80
    DP - sorry for the double posting...I was just hoping to hit this problem from all angles.
    Won't happen again.

    About Terminal. This is what I got (mind you the unit was flashing - which means it had acquired a fix when I tried this)

    ls -l /dev/cu*
    crw-rw-rw- 1 root wheel 10, 5 Oct 18 00:32 /dev/cu.Bluetooth-Modem
    crw-rw-rw- 1 root wheel 10, 3 Oct 18 00:32 /dev/cu.Bluetooth-PDA-Sync
    crw-rw-rw- 1 root wheel 10, 1 Oct 18 00:32 /dev/cu.V551-Dial-upnetworkingG-1

    Don't quite know what it means...but I don't see anything there that resembles a GPS unit

    Any thoughts?

  8. #8
    Newbie RouteBuddy's Avatar
    Join Date
    Aug 2007
    Posts
    34
    Give these drivers listed below a try.

    Note that GPS receivers are built for the Windows market and don't report to a Mac as expected by the OS - which means device drivers sometimes need to be built to read the packets.


    Neil


    ----------------------------------------------------------------------------------------------------------
    There are various drivers to try for the Mac where one is needed to support your USB NMEA GPS receiver.

    <http://homepage.mac.com/lonsing/SimpleGPS/>

    <http://sourceforge.net/projects/osx-pl2303/>

    <http://dfn.dl.sourceforge.net/sourceforge/osx-pl2303/osx-pl2303-0.2.2-10.4-universal.dmg>

    Sometimes the Prolific chipset is used in other adapters. You can try to install their driver:

    <http://tinyurl.com/2ex66h>

    ----------------------------------------------------------------------------------------------------------

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •