1. Garmin Bobcat Mac

New to GPSBabel here and saw the recent thread on this. I, too, have not been able to get anywhere with my Garmin etrex Venture HC model on Mac OSX Leopard (10.5.2). I've tried 1.3.4 and 1.3.5-beta20080217 and get the same results. I fire up the GUI, select my Garmin unit over usb and output to Google Earth format. It says 'gpsbabel running' but nothing happens after that. In the meantime it consumes 100% CPU and has to be killed off.

If I attempt to run it again it complains that it can't get exclusive access of the USB port, so I'm guessing that USB module is still wedged in the system somewhere. I try to reboot, but it gets stuck trying to do a normal shutdown and I have to hard power down and restart the system (hold power for 5 seconds). Rinse and repeat here. Just now I did something different where I turned off the GPS while it was seemingly still trying to fetch the data just to see what would happen. A dialog popped up saying: Bad cmdsend r -103 sz 12 usbbulkwrite failed.

'usbbulkwrite: An error occurred during write (see messages above)' After acknowledging the error I can cleanly shutdown GPSBabel, so that's better. Any suggestions on other things to try? All I've tried so far is to download the track data and nothing more. I do have a small Windows system here at home and might try things there tomorrow night.

Joe Morris - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit. On Apr 13, 2008, at 9:17 PM, Joe Morris wrote: New to GPSBabel here and saw the recent thread on this. I, too, have not been able to get anywhere with my Garmin etrex Venture HC model on Mac OSX Leopard (10.5.2).

I've tried 1.3.4 and 1.3.5-beta20080217 and get the same results. Does that mean you are trying the CLI? Or just from within GPSBabel+ (the GUI)? I fire up the GUI, select my Garmin unit over usb and output to Google Earth format. It says 'gpsbabel running' but nothing happens after that. In the meantime it consumes 100% CPU and has to be killed off.

Can you try again, only this time open the log windows first (window menu, show log). Copy that and send it so I can see what command it's trying to execute. Karl - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2.

Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit. On Mon, Apr 14, 2008 at 2:41 AM, Karl Smith wrote: Does that mean you are trying the CLI? Or just from within GPSBabel+ (the GUI)? Nope, just the GUI for now. Can you try again, only this time open the log windows first (window menushow log). Copy that and send it so I can see what command it's trying to execute.

When I started it again, it logged nothing. After several minutes of it doing nothing I finally turned off the GPS and got this. EXECUTE- /Volumes/GPSBabel + -1.3.5 -beta20080217/gpsbabel -t -i garmin -f usb: -o kml -F /Users/morris/Desktop/gpsbabeloutput.kml ERROR CODE- 256 ERROR MSG- Bad cmdsend r -103 sz 12 usbbulkwrite failed. 'usbbulkwrite: An error occured during write (see messages above)' I did note on the GPS that the interface went into 'connected' mode when I started gpsbabel. Anything else to try next? Are there any modules I'm missing that I overlooked? Any prerequisites?

- Joe Morris - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit. I just tried under wxp and got a different error.

gpsbabel.exe -p ' -w -r -i garmin -f usb: -o gpx -F 'C: Documents and Settings Morris My Documents My Garmin sunday.gpx' ERROR SetupDiEnumDeviceInterfaces: No more data is available. Is the Garmin USB unit number 0 powered up and connected? Is it really a USB unit?

If it's serial, don't choose USB, choose serial.ERROR GetTime: Unknown date/time protocol GARMIN:Can't init usb: That error came back immediately. And, yes, it was turned on and ready to go. Tried is several times and got the same error. Starting to wonder if something is ill with the GPS now. Joe Morris - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event.

There's still time to save $100. Use priority code J8TL2D2. Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit.

You might try reloading the firmware. But I agree with your suspicions, there is a problem in GPSBabel, and not the GUI.

On Apr 14, 2008, at 7:15 PM, Joe Morris wrote: That error came back immediately. And, yes, it was turned on and ready to go. Tried is several times and got the same error. Starting to wonder if something is ill with the GPS now. This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2.

Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit. It's definitely not the GUI.

The installed base of Venture HC on non-windows OSes appears to be small; my shout out to babel-heads running that combination didn't get much interest. Still, there's just enough of a cloud hanging over that combination that I did reach out to Garmin on that just today. I'll let you know what we discover. However, the failure on Windows is interesting. I'm pretty sure we have lots of users Venture HC users on Windows. The Mac and Linux Garmin/USB backends are very similar, but the Windows one is rather different, and I'm pretty sure that works in the general case.

The quoted error implies we're having trouble talking to the Windows driver on your unit. As a sanity check, does this GPS work with any program on any OS?

I'd hate to think we're zoomed in too far to see some other problem, perhaps including a GPS that's just slightly broken or something. This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100.

Garmin Bobcat Mac

Use priority code J8TL2D2. Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit: - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event.

There's still time to save $100. Use priority code J8TL2D2.

Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit. Just a quick update as I head off to bed here. I did have success, but it wasn't with gpsbabel. I discovered another piece of software for Mac (was not sure if I should name it here).

It's like comparing apples to oranges here clearly, but wanted to try something to see what would happen. I fired it up, it recognized my GPS and acquired the data in 5 seconds (even the GPS chirped and displayed a message when the transfer was complete). I verified the data was good and was able to import it into Google Earth. This at least shows my GPS device is good and communicating OK. I will try out the other suggestions made here tomorrow night and report back. Joe Morris - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100.

Use priority code J8TL2D2. Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit. On Mon, Apr 14, 2008 at 11:02 PM, Karl Smith wrote: If you know how to run from the CLI, why don't you try running this from the terminal (copy and paste, it is all one line: /Volumes/GPSBabel + -1.3.5 -beta20080217/gpsbabel -t -i garmin -f usb: -o kml -F /Users/morris/Desktop/gpsbabeloutput.kml neversummer: morris$ more mygpsbabel /Volumes/GPSBabel + -1.3.5 -beta20080217/gpsbabel -t -i garmin -f usb: -o kml -F /Users/morris/Deskt op/gpsbabeloutput.kml neversummer: morris$./mygpsbabel Bad cmdsend r -103 sz 12 usbbulkwrite failed. 'usbbulkwrite: An error occured during write (see messages above)' When I ran the command, nothing happened. It just sat there, but the prompt did not return. There was no CPU utilization this time either. It was only after several minutes of waiting that I turned off the GPS and I got the error message above.

So, yeah, something is just not chatting right here for some reason. Joe Morris - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event.

There's still time to save $100. Use priority code J8TL2D2. Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit. There seems to be something unique about the Venture HC on Mac and Linux. I have a request in with Garmin, but haven't heard back from them yet. I suspect there's something in the firmware that is different than the other devices but that happens to work with their Windows driver. Apple's USB stack can become unstable when dealing with naughty USB devices.

Once it gets grumpy, unplugging and reconnecting the device will usually restore sanity. It usually won't 'heal' on its own. Joe, does it ever work for you? If you detach and reattach the device, does your debugging trace end in the same spot as the other reporter of this problem? Joe Morris - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100.

Use priority code J8TL2D2. Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit: - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100.

Use priority code J8TL2D2. Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit.

Hello everybody, like the other posters I am having the exact problem on Mac OS X with the same hanging and the same debug output. Has anything been done on this topic? I suspect not, as there was no answaer in this thread for 2 months.

The Garmin software Bobcat is working for me, however, I am used to gpsbabel and many nice applications are using gpsbabel as backend. I would be happy helping to narrow down the problem. I have some basic knowledge in proramming C and be happy doing any testing/debugging if someone could point to the spot in the source code where to look.

As the communication with Garmin Bobcat is working fine could it help to do some sniffing of the communication with the Venture HC? And if yes, which tools on Mac OS X could do this?

There seems to be something unique about the Venture HC on Mac and Linux. I have a request in with Garmin, but haven't heard back from them yet. I suspect there's something in the firmware that is different than the other devices but that happens to work with their Windows driver. Apple's USB stack can become unstable when dealing with naughty USB devices. Once it gets grumpy, unplugging and reconnecting the device will usually restore sanity. It usually won't 'heal' on its own.

Joe, does it ever work for you? If you detach and reattach the device, does your debugging trace end in the same spot as the other reporter of this problem? I contacted Garmin engineering about this asking why this model is different in some way than all their other models that support this protocol and got nowhere. Even with packet dumps in hand, they were unwilling to look into it, taking the 'Bobcat works' stance. Proramming C and be happy doing any testing/debugging if someone could point to the spot in the source code where to look. As the communication with Garmin Bobcat is working fine could it help to do some sniffing of the communication with the Venture HC? And if yes, which tools on Mac OS X could do this?

USB protocol analyzers are very expensive but very handy for debugging this kind of stuff as you can see things happening on the wire that host software just can't see. Apple has a debugging stack available, but it's probably not very helpful for device-specific problems like this. So it's probably going to come down to experimentation - poking the device slightly differently to see why it acts differently than the other couple of dozen Garmins that work fine. The code in GPSBabel that handles the USB stuff for the Garmins is in jeeps/.usb.c. The Mac build uses gpslibusb.c to build packets that get handed to libusb which ultimately hands them off to iokit. If you want to discuss bits and bytes, -code is probably a better place than -misc. Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!

Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit. If you're not a Mac/Linux users of a Venture HC, you're dismissed. I've had enough reports of this problem that I broke down and bought aVenture HC for the project (hey, that's what the 'support this project' link is for! If you've already donated, send friends.) studied its behavior on the USB, and spent the weekend whipping it into submission. This model works exactly like every other Garmin doesn't.

The undocumented workarounds required to make most Garmins work on Mac and Linux actually kill this model, so I've implemented a special case for it it in the code. You can find a beta GPSBabel for Mac containing this workaround on now. Please let us know success or failure. It's worth noting that this model has about a 5% failure rate of being recognized by the OS. It turns out that if you restart Garmin's own software repeatedly with the Venture HC version 2.70, the failure rate is about the same, so that may just be the way this model works. USB protocol analyzers are very expensive but very handy for debugging this kind of stuff as you can see things happening on the wire that host software just can't see. Apple has a debugging stack available, but it's probably not very helpful for device-specific problems like this.

So it's probably going to come down to experimentation - poking the device slightly differently to see why it acts differently than the other couple of dozen Garmins that work fine. The code in GPSBabel that handles the USB stuff for the Garmins is in jeeps/.usb.c. The Mac build uses gpslibusb.c to build packets that get handed to libusb which ultimately hands them off to iokit. If you want to discuss bits and bytes, -code is probably a better place than -misc. This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world Gpsbabel-misc mailing list To unsubscribe, change list options, or see archives, visit.

Full Specifications What's new in version 2.3.0 - Added support for MTP devices like the Monterra. Fixed bug where premium POIs where being deleted when custom POIs were removed from device. Fixed bug with importing GPX files. Added ability to create new folder while saving to computer.

Added support of Brazilian Portuguese language. Fixed bug with not displaying address information. General Publisher Publisher web site Release Date February 28, 2015 Date Added February 28, 2015 Version 2.3.0 Category Category Subcategory Operating Systems Operating Systems Mac OS X 10.10/10.7/10.8/10.9 Additional Requirements None Download Information File Size 12.57MB File Name External File Popularity Total Downloads 3,370 Downloads Last Week 1 Pricing License Model Free Limitations Not available Price Free.