![]() ![]() The throttle data comes in at 50 samples per second so you can do the math on file size pretty quick. The wheel speed and brake data above comes in at 100 samples per second. I don’t have it yet but it seems like the perfect starting point for data logging. This being the goal, I ordered a few of these for a very reasonable $24. To do that, one can’t (should not) ride with a laptop taped to their race suit (unless they use 4+ wraps of tape). Per above, the real reason for this work was to have a data logger. It’s important to me for logging so if you happen to find it, please PM me! Yet to fully validate.ĭate Time - I don’t know where this is yet. Yet to fully validate.įuel level – I think it is provided by ID 1361, byte 1, as a percentage. Water temperature – I think it is provided by ID 1360, byte 2. Oil temperature – I think it is provided by ID 1344, byte 7/8. I expect byte 2 to be ABS intervention intensity, byte 4 to be MTC intervention intensity. I have figured out that the byte 1, 3, 5 express changes to ABS, MTC, and MODE settings respectively. I’ve more testing to do here while on the road. ![]() Traction Control – its provided by ID 1104. I *believe* the first 0x000 are tilt but I’ve yet to validate. 0x000 is neutral, 0x001 starts leaning to the right. The last 3 bytes (6,7,8) split into two 12bit counters. Rear Wheel Speed – it’s also provided by ID 299. I’ve not totally figured out the scale but expect it to be pulses off of the 48 tooth hall effect sensor. The wheel has to move at a certain minimal speed to get it to register. Start the engine and you’ll see it warm up around 2000 rpm and then settle in around 1500 rpm.įront Wheel Speed – it’s provided by ID 299. RPM – it’s provided by ID 288, in the 1st word position, right before throttle. No pressure is 0x0000 (off) and a fistful of brake registers to about 0x3500 on my bike. When you pull in the clutch the lower nibble goes from 0 to 8 and back.įront Brake Force – it’s provided by ID 656, in the 1st word (2 bytes) position. The upper nibble (hex digit) is 0 for Neutral, 1-6 for gears. ![]() Gearbox – it’s provided by ID 297, in the 1st byte position. Turn it and see how it goes from 00 (off) to FF (fully on). Throttle – it’s provided by ID 288, in the 3rd byte position. Here's what i found via tedious sleuthing and math modelling: In CANTACT-APP you can save data to disc but I found that it grinds to a halt around the 500 second mark so save smaller CSVs. In the CONFIG WINDOW tab, pick your port (likely COM3) and then Bitrate of 500KB. Plug the cable into the bike and into the PC. Prepare your laptop with the right software. Note that the CANABLE as exposed metal pins below the circuit board – don’t short them out on your bike frame. Screw this new cable to the CANABLE matching the pins. Be sure NOT to connect power – the CANABLE is powered by the USB port, not the bike. The connector is facing you, with tab on top (per Corsa site image). Get a set for the data logger project too. ![]() Get your Sumitomo connectors here for $ 3.26 a set. I can’t leave good enough alone regardless of my hobby (or job). I simply wanted to learn quickly, make cool RaceRender videos, and geek out. This said, don’t get the idea that I’m a hard core racer… can’t be further from the truth. I have a SpeedAngle ( ) but it lacks access to key data I wanted: throttle position, gearbox position, braking forces, shifting efficiency, tyre slip, ABS/traction control intervention, and bike lean and tilt. No warranties expressed or implied – reading this means you agree that you may blow up your bike on your time, and on your dime. I had searched far and wide but failed to find what I needed so I dug in and am taking the time to share what I found. This is a longish post about getting inside the CAN BUS protocol. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |