You need to UNinstall the brltty and libbrlapi0.5 (Braille TTY) packages to get ftdi working under Ubuntu.
Ftdi will work out of the box after that. See my HowTo document in the "HowTo" thread.
and then no pids are recognized. Its a hassle to test this so can't spend time on it right now but I'll look into what the response is later.Code:Didn't get parsable data back for cmd 00:
Could you start a new thread about your "unparsable response" error? As we were talking on irc, I think I have an answer, but it might need a bit more time on my part.
will do as soon as I get home. I'll include the serial logging output
I have seen online several less expensive (<$50 US) options for OBD-ii to USB dongles, such as this one:
and this one:
But I have no experience and can't tell if these devices would work or not. They look like the other devices that are confirmed to work from the online descriptions, to my untrained eyes, but I am wondering why they would be so much less expensive.
Should work without problem. So long as they say "elm327 compatible", you should get something out. IME, the more expensive ones perform better and provide more features, but for simple stuff [and obdgpslogger doesn't do anything really "not simple"], those should work fine.
There's been some substantial discussion on the board level above this one a few times about this. Anything that applies to others should apply to obdgpslogger.
I ordered the Scantool.net OBDLink BT/USB device and also need to order a GPS Bluetooth device. In your logger's documentation, you mention you used Globalsat BT-359. Would you recommend this device as it does everything you need or would you choose a different one, if you could do it all over again?
How often do you receive the location from the GPS receiver? I assume this is less-frequent than the rate at which you receive OBD-II information? If this is true, how do you create the log if the two data rates are different? I also assume you receive speed, rpm, etc. at the same data rate, so the number of samples of OBD-II information is the same.
I'm perfectly happy with my BT-359, as far as bluetooth goes.
I actually don't use it much; I have a BU-353 puck that I'm much happier with. If you specifically want bluetooth, then yes, the bt-359 is great. If you don't specifically need bluetooth, get the linked puck instead.
I sample gps at the same rate as I sample obd; by using gpsd, all the complexities of that are completely hidden. If you set the samplerate to 2 times a second, then it will ask gpsd for your position twice a second... whatever gpsd says your position is, that's what's logged.
And as a heads-up, if you use the wire to plug it into your computer, the OBDLink defaults to 38400 baud while obdgpslogger defaults to 9600.
You'll want to set that in the config file [since I haven't written a baudrate guesser yet]:
- I don't have a bluetooth-capable OBDLink, but I suspect that you won't suffer this artifact since rfcomm usually gets it right first time, in my experience.Code:echo "baudrate=38400" | sudo tee /etc/obdgpslogger
By the way I assume 500K baud rate is OK?