807 backers and this is all that's happening?

Derek, I know you've been very busy. I'm just surprised there aren't more backers on this forum exchanging experiences. But maybe we can get it a bit more lively here ;-)

Bought a breakout box last week so i can check to the different busses while I use the factory software tool. Havent found a good solution to analyzing the data yet. Anybody got suggestions?

Been thinking about getting a logic analyzer as well, these seem to be more aimed at well...analyzing!

With a scope you see the signal on the bus and check the speed.

Tried building and uploading the code with Sketchbook, first on Windows 8, lots of build errors. After that on Mac OSX, building and uploading works right way, no problems.

Thanks <a href="http://forum.canb.us/profile/254/Xag">Xag</a> , your posting about changing the baud rate to fixed speed of 500 did the trick for me! I am now receiving data using the ODBII port and a Mac with CoolTerm, when setting the receive option to Hex I get a logfile with hexdata :-*

Next challenge, figure out what this stuff means. Logged 458653 lines in 10 minutes driving, the data looks like this (Volvo XC70 2005):
03 01 00 28 00 19 84 00 00 8B 37 00 08 03 0D 03
01 00 3C 00 00 00 00 00 00 00 00 08 03 0D 03 01
00 58 40 00 00 CF 26 47 3D 10 08 03 0D 03 01 00
34 00 00 00 00 00 00 00 00 08 03 0D 03 01 04 30
00 00 00 60 00 00 00 00 08 03 0D 03 01 04 48 23
60 0F 3C 01 00 14 00 08 03 0D 03 01 00 40 00 00
00 01 BC 04 C0 00 08 02 0D 03 01 00 08 3F F8 00
00 13 FF D0 00 08 01 0D 03 01 00 38 00 01 60 E0
9F 00 00 00 08 03 0D 03 01 04 00 C0 00 00 00 C0
00 C0 00 08 03 0D 03 01 00 20 05 FE 02 9A 00 28
72 00 08 03 0D 03 01 00 50 00 00 00 00 00 00 00
00 08 03 0D 03 01 00 68 00 FD 02 07 80 00 80 00
08 03 0D 03 01 04 20 00 80 00 7F 00 00 00 00 08
03 0D 03 01 00 34 00 00 00 00 00 00 00 00 08 03
0D 03 01 00 28 03 19 84 00 00 8B 37 00 08 02 0D
03 01 00 18 02 05 43 8B EA 05 64 00 08 01 0D 03
01 00 20 1D FE 02 9A 00 28 72 00 08 03 0D 03 01
00 28 00 19 84 00 00 8B 37 00 08 03 0D 03 01 00
50 00 00 00 00 00 00 00 00 08 03 0D 03 01 00 40
00 00 00 01 BC 04 C0 00 08 03 0D 03 01 04 08 00
00 00 00 00 07 07 0E 08 03 0D 03 01 00 30 1E E4
00 00 07 FF C7 FF 08 03 0D 03 01 04 00 C0 00 00
00 C0 00 C0 00 08 03 0D 03 01 04 40 01 BB CC 00
00 6A 03 4A 08 03 0D 03 01 00 58 80 00 00 CF 26
47 3D 10 08 02 0D 03 01 00 18 02 05 43 8B EA 05
64 00 08 01 0D 03 01 00 20 05 FE 02 9A 00 28 72
00 08 03 0D 03 01 00 28 05 19 84 00 00 8B 37 00
08 03 0D 03 01 00 50 00 00 00 00 00 00 00 00 08
03 0D 03 01 04 44 00 00 00 1C 7E 22 80 00 08 03

Etc..

I would start with logging the data running with ignition on but engine not running. That will give you a base line and hopefully some repeating data that you can then filter out. Next is to trigger events (push a button) and look for new data. The amount of data from a running engine might be a bit much at this point ;-)

i am so far, that i already reveived my CBT, flashed the firmaware and coolterm works fine(mac)...
but i didn't have find time, yet, to connect my cbt with the car and log some lines.
But maybe mercedes will give some dresses and codes when i say please, please.

But maybe not :D

greets

administrators

@henk_kuipers: I'll break this down for you. Once the app is live you can use that for reading packets MUCH easier but for now Serial works.

From the first line of your dump:
03 01 00 28 00 19 84 00 00 8B 37 00 08 03 0D

03 is the prefix of the message data, if you remember the command you sent to start dumping was 030101XXXXXXXX so this is the response.

01 is the Bus ID either 1, 2, 3 (Triple! :D)

0028 is the Message ID of the CAN packet

00 19 84 00 00 8B 37 00 is the payload of the CAN packet. (8 bits of data)

08 is the length of the data

03 is the status of the CAN controller at the time the MCU read the data from the controller

and 0D is a newline in ASCII and it represents the end of the data.

As you can see that pattern repeats over and over and over, for every single packet.

Thanks for the explanation <a href="http://forum.canb.us/profile/1/Derek">Derek</a>! In the meantime I gained some more insight in using the #define JSON_OUT hint from Iseward. The logfile is now looking like this:
{"packet": {"status":"3","channel":"Bus 1","length":"8","id":"68","timestamp":"2515874","payload":["0","6D","92","7","80","0","80","0"]}}
{"packet": {"status":"3","channel":"Bus 1","length":"8","id":"68","timestamp":"2515994","payload":["0","AD","52","7","80","0","80","0"]}}
{"packet": {"status":"3","channel":"Bus 1","length":"8","id":"68","timestamp":"2516024","payload":["0","7D","82","7","80","0","80","0"]}}
I am looking forward to working with the app. I am perhaps a bit impatient by diving into this now already but so far it has helped me in becoming a bit more familiair with this fascinating piece of engineering!

Thanks Derek, this is really helpful info!

My latest findings:

  • Only baudrate 500 on canbus 1 works for me on the ODBII port. I tried baudrates 250 and 125 by hardcoding it in the software but when I use 250 or 125 I see no data whatsoever.
  • I always see a set of 29 message ID’s, it is the exact same set of ID’s when logging in four different scenario’s:
  • only contact on
  • contact on and pushing buttons (windows, radio, climate, mirrors -tried almost all-)
  • engine running
  • while driving and pushing buttons
  • I think I am only seeing data on the High Speed CAN for two reasons: the baudrate of highspeed CAN is 500 and I don’t see any new message ID’s appearing when pressing buttons. All the comfort stuff is on the low speed bus.
    It is probably time now to figure out how to wire the CBT to both the high and low speed CAN. What I want is to find are messages related to low speed connected things like windows and mirrors. Any ideas to help me find the interesting messages are still welcome...

@henk_kuipers‌ i have the same Problem. You have to figure out the correct baud rate for your low speed can. Today i will give ist a try and set my can 2 to the most common baud rates and look for data.

@<a href="http://forum.canb.us/profile/19/ichraffsnicht">ichraffsnicht</a> I have reason to believe I need to connect pin 3 and 11 voor Low Speed CAN, perhaps a Volvo thing. I tried to solder the wires on the ODBII plug tonight but this appears to be very challenging for me with pins dropping out and wires snapping off all the time >:P To be continued...

You need to have 3 hands :D

My low speed can is in on pin 1/9.(Fiat Grande Punto)

I also solder a New cable in the obd connector. The original cable is not flexible enoth to solder it as a beginner and in my case when i open the obd connector, 2 wires by moving it ;)

Nice starting place for Volvo is<a href="http://www.svxc.se/phpBB2/viewtopic.php?f=9&t=23011"> here</a>. It is mostly in Swedish and partly in English but isn't to difficult to figure out with google translate. <blockquote></blockquote>

Hi <a href="http://forum.canb.us/profile/519/HYTPUSSR">HYTPUSSR</a>, thank you. I also found that thread and read almost all of it, I can actually read Swedish reasonbly well :-) I know for sure now that pin 11 and 3 are Low Speed Canbus on my car's OBD port, it's in the wiring diagram I downloaded.

I am trying to add low speed can to the already hig speed can logging using OBD. So, I wired:
OBD pin 3 to the yellow CBT wire
OBD pin 11 to the blue CBT wire
I left following wires as they were originally:
OBD pin 14 to the CBT green wire
OBD pin 6 to the CBT red wire
OBD pin 16 to the CBT black wire
OBD pin 4/5 to the white CBT wire
I was thinking that this would connect the Low Speed Canbus to the CBT. However, this wiring blew up two fuses , generated an airbag maintance warning, reset the clock and triggered the alarm! Perhaps my soldering was too messy, it may have caused a shortcircuit because not very well done. But before I try anything again I would like to verify:
=> Should I connect the yellow CBT wire to OBD 3 and the blue CBT wire to pin 3???
This is the wiring diagram of my car where you can see the canbus pinout of the OBD connector:
https://plus.google.com/110529970729409407854/posts/UcMB38kwRqb?pid=6128773130273387122&oid=110529970729409407854

So, without connecting the yellow and blue wire (the original wiring of the CBT-OBD cable) I can log High Speed canbus data at baudrate 500. I also know that the baudrate of my Low Speed canbus is 250, I just need to get this wiring problem solved.... Any helpful ideas?

@henk_kuipers‌ . I would first check the wires you soldered with a multimeter, just to be sure your cable is okay. Looking at your wiring diagram OBD pin 3 is indeed the high (=yellow =pin 5 CBT) and OBD pin 11 the low (= blue = pin 6 CBT) CANbus. Should work like this.

administrators

@henk_kuipers‌ Just looking at your wiring specs it should work. Double check you connections. I'm running the same setup in my vehicle without issue.

You probably just caused some errors on the bus which caused all that stuff to happen. I've done the same thing a couple of times in the past when developing the PCB. You can clear the codes in your ECU and you should be good.

  • 29
    Posts
  • 19357
    Views

Looks like your connection to CANBus Triple was lost, please wait while we try to reconnect.