807 backers and this is all that's happening?
  • 0
  • To be honest I'm surprised (and a little bit disappointed) that with 807 backers the number of people being active on the forum is only a handful. Are most people using the CBT as a doorstop? ;-)

    Somehow I have the feeling a lot of people expected a more or less ready tool and have no idea what to do with the CBT at this point.

    So, why aren't you doing anything with your CBT?

  • 0
  • cant get mine to work right now its being stupid

  • 0
  • Okay, let's see where you're stuck.

    1 Able to install the Arduino software?
    2 Able to connect to you CBT?
    3 Able to upload the Blink sketch to the CBT?
    4 Able to download the CBT software from Github?
    5 Able to install the CBT software on the CBT?
    6 Able to find / download / install a serial program?
    7 Able to set up communication from the serial program to the CBT?
    8 Got response when entering Hex 0101 in the program?
    9 Do you know where there's a CANbus on your car?

    Up to which point have you come?

  • 0
  • Just found you other threat, you seem to be pretty advanced. Can't really help you with than one.

  • 0
  • Good point Xag, so here what I have done so far:

    • Connected the CBT to Mac using USB and tried the Hex commands from Coolterm, this worked
    • Downloaded the iOS/Android client from github, compiled and installed it on an Android smartphone. App runs but the bluetooth component is lacking so it doesn't do anything yet.
    • Connected the CBT to the ODBII port of my car, no response after entering the hex command to start logging. Apparently, I need to connect the K-line pin and send a keep-alive signal (Volvo specific). Not figured this out yet.
    • I know where I could connect the CBT to the Canbus, it is the Melbus interface at the back of the Volvo RTI DVD player. However, I cannot find the pinout of the Melbus interface so I don't know how to wire the CBT. I also asked some people form a swedish volvo forum for help on this but no luck yet.
    • I downloaded the latest CBT build from Github and tried to flash it using avrdude. The atmega32u4 platform is not listed in the avrdude.conf file. There are more people that ran into this and I found a fixed avrdude.conf file but I have tried it yet because I am not sure it is correct.

    My next actions will be:

    • Try the CBT on the ODBII port of another car so I can see some logging action
    • Pay a visit to a friend who owns a garage to see if he can help me to figure out where to connect the CBT to the canbus or see if he can figure out the pinout of the Melbus interface

    Alltogether not much progress. How are CBT-ers doing so far?

  • 0
  • My progress:

    • resoldered the obd connector to work with my 2 can buses

    -figured out that i have no idea busspeed i need for the low speed can and that i need 500kbps in the high speed can

    • logged some data in the HS-Can.

    -forked the github project and added my code

  • 0
  • administrators

    Agreed Xag! I've been so busy QAing and assembling the last units from the run I haven't had much time to do anything else. I'm really looking forward to advancing the software to make it easier.

  • 0
  • Don't you have a manual to see what the CANbus speed is?

  • 0
  • 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!

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

  • 0
  • 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.

  • 0
  • 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 :-*

  • 0
  • 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..

  • 0
  • 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 ;-)

  • 0
  • 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

  • 0
  • 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.

  • 0
  • 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!

  • 0
  • Thanks Derek, this is really helpful info!

  • 0
  • 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...

  • 0
  • @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.

  • 29
    Posts
  • 6295
    Views
  • Log in to reply