BMW S1000RR Forum banner

1 - 20 of 22 Posts

·
Registered
Joined
·
8 Posts
Discussion Starter #1 (Edited)
Hi there!

I know I'm just a rookie in the forum :eek: but perhaps someone finds this useful or he/she can even help me out.

I have connected a general CAN to USB card to our race bike, which as you may know has a 500kbps CANbus:


And the obtained messages are as follows (I have better resolution shots if anyone needs them):


Please note that our unit doesn't have the brake lines connected to the ABS system...

In any case, I have already deciphered some of the channels contained inside the messages and captured them with our 2D data logger:


However I was wondering if anyone here would have the complete coding of the channels contained in the CANbus messages.

It would be really helpful...most of all because we are going to get them anyway but we would like to spend 2 weeks in better things to do (like tempering with the race calibration kit 3...).

Thanks in advance and sorry for the techno-geek stuff...
 

·
Registered
Joined
·
8 Posts
Discussion Starter #5 (Edited)
I'm very interested in this. What hardware and software are you using? Can you share your data?
Hi there, let me respond one point at a time:

Hardware:
PEAK PCAN-USB , it is a CAN-USB interface for the PC, it costs around 200€ (not cheap, but as I have them at my job they're basically free for me...).
The´physical connection to the bike was made through the CANbus connector end located on the bike's saddle (don't have a picture right now but I can make one if needed). One quick comment here...please remember that a 120 ohm resistance must me connected between CANH & CANL terminals... As the plug is extracted the bus must be correctly terminated.


Software:
The software used for CANbus network setup is PCANstat I believe, and the one for message viewing and logging is PCANview, both are free and available at the manufacturer's webpage (and if I recall correctly, they're free). Software: PEAK-System

Data sharing:

I believe I have a 12 seconds long sample here in this PC...If I am not mistaken it should contain the messages of the bike being turned on and with a few twists of the throttle.

Let me find a way of posting a download link and I'll get back to all of you on the subject ASAP.

EDIT:

https://www.dropbox.com/s/ypqm0zwz8n0gbb2/BMW%20arrancado%203%20segundos%20toques%20de%20gas.trc?dl=0

It's not much...I know...But I can get more where it came from =)
 

·
Registered
Joined
·
8 Posts
Discussion Starter #6
Hi all,

I've notice that the image of the CANbus message list detected via the PC interface (second image of the first post) has a resolution less tan "ideal" and its hard to see anything:confused:

That's why I've turned it into a table using a text editor and you can find it below:


just thought it would be easier, hope it helps.

Although I haven't said anything before, please note that I can't be made responsible for any misuse of the information posted here...My intention is only to collect data from the CANbus system of the bike.

Also let me say this straight, I wish no profit from this, that's why I am sharing everything here. It is my believe that the more people have access to information, the faster we can all benefit from it.

So again, sorry for the long phrasing on boring subjects, and please feel free to ask or share whatever you like on the subject :)
 

·
Premium Member
Joined
·
569 Posts
What year is the bike?

10C is RPM, Throttle, Grip Position
2A0 is lean angle
2BC is Gear, water temp

3FF is odometer
 

·
Registered
Joined
·
8 Posts
Discussion Starter #10 (Edited)
What year is the bike?

10C is RPM, Throttle, Grip Position
2A0 is lean angle
2BC is Gear, water temp

3FF is odometer
Hi!, it's a brand new 2015 bike (will be competing this year on the European superbike championship)

I believe you are correct, although messages 2A0 and 3FF are unexplored by me yet =)

As I think it might be helpful for someone, it is important to not only know what channels are contained in each message but also what type of calibration and byte ordering are they using.

EDIT, the following capture is the message 10C (hex) as seen when turning on the contact and the bike on a rear stand with the engine stopped:


As seen on my first post, byte 2 is the first of 2 bytes (16bit resolution) of information regarding the RPM, this value has to be multiplied by 5 and no offset es required. I believe it comes coded as a high byte-low byte, but I'll have to check this in order to confirm it as I don't remember it now.
 

·
Registered
Joined
·
82 Posts
This is awesome, just starting my can bus adventure. My goal is to create an affordable setup for those track day junkies who are serious about rider improvement. Data doesn't lie.
I'm looking into integrating the Race Capture Pro into the bike. All I need is a proper CAN Bus cable and the DBC file: the deciphering link between the CAN data to readable data. Once I get my hardware, I'll see if i can support building a complete file.

If anyone has already solved this, I would certainly appreciate the support!

https://www.autosportlabs.com/racecapturepro-2/

Cheers,

Sent from my Nexus 6P using Tapatalk
 

·
Registered
Joined
·
82 Posts
Successfully connected to the bike last night.
Had to carve out some of the connector to make it seat correctly, the repair plug i got from BMW was slightly different...



Working to confirm the CAN coding now, had a great head start from dagor6.

The Race Capture Pro box interprets CAN a little differently, for example, offset, length, etc.

More to come!
 

·
Registered
Joined
·
85 Posts
Do not know if I am "hacking" the thread, but I am also decoding the S1000RR CAN messages. And have found most of the CANID's which are or seem relevant. And I am focussing first on the messsage 0x10C. I have found some documentation (link), but I cannot recognize the values given by our S1000RR and these algorithms. (Our BMW is a S1000RR 2012+HP RaceKit)

Some messages comming off are: (number/byte1/2/3/4/5/6/7/8)
Code:
1673	255	206	27	22	229	0	255	7
1674	255	225	27	22	229	0	255	7
1675	255	28	22	229	0	255	6	7
1676	255	28	22	229	0	255	6	7
1677	255	147	27	22	229	0	255	7
1678	255	147	27	22	229	0	255	7
1679	255	135	27	22	229	0	255	7
1680	255	151	27	22	229	0	255	7
1681	255	151	27	22	229	0	255	7
1682	255	27	22	229	0	255	6	7
1683	255	27	22	229	0	255	6	7
1684	255	183	27	22	229	0	255	7
1685	255	22	28	22	229	0	255	7
I am trying to make charts from the values to detect a pattern so I can recognize the "sensor"...

Do you have more info?
 

·
Registered
Joined
·
82 Posts
Do not know if I am "hacking" the thread, but I am also decoding the S1000RR CAN messages. And have found most of the CANID's which are or seem relevant. And I am focussing first on the messsage 0x10C. I have found some documentation (link), but I cannot recognize the values given by our S1000RR and these algorithms. (Our BMW is a S1000RR 2012+HP RaceKit)

Some messages comming off are: (number/byte1/2/3/4/5/6/7/8)
Code:
1673255206272222902557
1674255225272222902557
16752552822229025567
16762552822229025567
1677255147272222902557
1678255147272222902557
1679255135272222902557
1680255151272222902557
1681255151272222902557
16822552722229025567
16832552722229025567
1684255183272222902557
168525522282222902557
I am trying to make charts from the values to detect a pattern so I can recognize the "sensor"...

Do you have more info?
No worries man! Glad to get a fresh set of eyes.

I think you need to convert those numbers from (some format) to decimal. Easy in Excel. Problem is they look like decimal values already... Unless they need to be parsed?

Next you need to confirm the conversion factors. Usually it's given by 2 variables, A+Bx, where x is your digits above.

There is some published resources out there though I struggled with mine. You can very easily confirm when you have another gauge to test against (rpm, temp).

Let me dig into my old stuff tomorrow and see what I can find.

Sent from my Nexus 6P using Tapatalk
 

·
Registered
Joined
·
85 Posts
I am reading them live from the CANBUS and just logging them raw. Converting them from hex values to decimals (and yes that is what you see here).

A (raw) message is (from 0x10C ID)
Code:
Control Field: '8' (0x8) bytes
Data Field Byte: '255' (0xFF)
Data Field Byte: \n (0x0A)
Data Field Byte: h (0x68)
Data Field Byte: '24' (0x18)
Data Field Byte: '22' (0x16)
Data Field Byte: '229' (0xE5)
Data Field Byte: '0' (0x00)
Data Field Byte: '255' (0xFF)
CRC value: '1777' (0x06F1)
[\code]
 

·
Registered
Joined
·
82 Posts
You're way ahead of me, lol

Pm me your email, I'll send you my attempts and things I've gotten from others.

Out of curiosity, can you send me a picture of you set up/connection to the bike?

Software to sniff the CAN?

Thanks

Sent from my Nexus 6P using Tapatalk
 
1 - 20 of 22 Posts
Top