<b>EDIT: I got it working. I called the auto-baud command again and now I've got a metric ton of data flowing through. I've captured a bunch and just need to sit down and paw through it all.</b>
I got my CBT in the mail yesterday, and have just had a chance to start tinkering tonight. I followed the instructions on the Getting Started page and hooked my CBT up to my car using the OBD-II connector. Power came on (without USB) and I plugged the CBT into my netbook and fired up CoolTerm. Probing the CBT for information worked, but probing CAN 1 for info netted me this error:
<code>{"e":"busdgb", "name":"Bus 1", "canctrl":"4", "status":"0", "error":"1011"
"Receive Error Warning - TEC or REC >= 96",
"Receive Error Warning - REC >= 96",
"Receive Error Warning - REC >= 128", "nextTxBuffer":"0"}</code>
Probing CAN 2 and 3 got no errors though:
<code>{"e":"busdgb", "name":"Bus 2", "canctrl":"7", "status":"0", "error":"0 - No Errors", "nextTxBuffer":"0"}
{"e":"busdgb", "name":"Bus 3", "canctrl":"7", "status":"0", "error":"0 - No Errors", "nextTxBuffer":"0"}</code>
I then fired up the car and tried to listen on all three busses. I got "ÿ" back, which in hex, is "FF 00", for all three.
Being a programmer, but barely knowing what a car even is, let alone how it operates, I'm stumped. In general, do all cars expose at least one CAN bus via OBD-II (i.e. should I see at least something without having to wire this thing into my car?)
For troubleshooting purposes, here's what I did:
- Download Arduino for Windows 8.1 (64 bit), Download CBT from GitHub and extracted the CBT zip into the hardware folder
- Opened Arduino, picked the CBT as the board, the COM port and verified / compiled the unmodified CanBusTriple sketch. No errors.
- Plug the CBT into the car / laptop and sent the HEX to auto-detect the baud rate. I don't remember the outcome, but it said it finished. I then rebooted the CBT by unplugging both sources of power and plugging it back in.
- Ran the commands to probe / start logging and got the commands above.
Any clues?