M400 Can bus and MCP2515

[kerail]

Hi guys, i've bought car with Motec M400 ECU. It's awesome. Previously the car was equipped with Motec ADL3 but it have been sold by previous owner. Currenly i want to receive RPM, sensor data from ECU via CAN and MCP2515 module.
First question, is MCP2515 compatible with CAN that used in M400? (i found articles that uses motec ADL with this chip, so it should work)
Can you share protocol specification for my ECU CAN (personal use only)?
I don't have UTC adaptor (it's a bit hard to get it in my region), so any modification to ECU software are currently unavailable to me. I'll receive it in month or more, but i need RPM, sensors and ECU status ASAP....

Thank for help!

[adrian]

Any CAN chip that meets the CAN2.0 spec will work fine with our devices, there shouldn't be any issue using the MCP2515.

The output data stream will be dependant on what you have configured in the ECU. If it is set to send out ADL messaging then it will have the following format:

IPS0006_MoTeC_M800_Set_1_Data_Protocol_v3+.pdf

(70.61 KiB) Downloaded 1231 times

If it is set to send out CRC32 then it will be as follows:

PSAU0015_MoTeC_M800_Set_3_Data_Protocol.pdf

(130.9 KiB) Downloaded 1089 times

If however it is set to send out a custom dataset then the only way you will know is by connecting to the ECU.

[kerail]

Hello. Thank you for links!

I've connected my motec M400 via MCP2515 and readed some data. But i have some problems with decoding data.
For example
MoTeC M800 Set 1 Data Protocol v3+
in specs it have 143 bytes, but CAN-bus in one standard packet can transfer up to 8 bytes.

I receving data like these:

Code: Select all

Standard ID: 0x5F0       DLC: 8  Data: 0x82 0x81 0x80 0x07 0x06 0x39 0x01 0x54
Standard ID: 0x5F0       DLC: 8  Data: 0x00 0xF3 0x01 0x46 0x00 0x00 0x09 0x80
Standard ID: 0x5F0       DLC: 6  Data: 0x00 0x00 0xC5 0xA9 0x05 0x3A
Standard ID: 0x5F0       DLC: 8  Data: 0x00 0xF3 0x01 0x46 0x00 0x00 0x09 0x82
Standard ID: 0x5F0       DLC: 8  Data: 0x82 0x81 0x80 0x07 0x06 0x3E 0x01 0x54
Standard ID: 0x5F0       DLC: 6  Data: 0x00 0x00 0x56 0x7D 0x4C 0xD2
Standard ID: 0x5F0       DLC: 8  Data: 0x00 0xF3 0x01 0x48 0x00 0x00 0x09 0x7F
Standard ID: 0x5F0       DLC: 8  Data: 0x82 0x81 0x80 0x07 0x06 0x3C 0x01 0x54
Standard ID: 0x5F0       DLC: 6  Data: 0x00 0x00 0xC0 0x69 0x89 0x70


File with full data that i receive via CAN in states for reference:
https://drive.google.com/file/d/0B3OMNOuTXQnJRTQ4cXlxalRIVXc/view?usp=sharing
- engine OFF
- start engine
- playing with throttle a bit

I tryied to find marker bytes 0xFC 0xFB 0xFA with no luck.
Can you give me some hints about right decoding of data?

[kerail]

Oh, 0x82 0x81 0x80 looks like Header "Set 3 Data Protocol".

Standard ID: 0x5F0 DLC: 8 Data: 0x82 0x81 0x80 0x07 0x06 0x39 0x01 0x54
Standard ID: 0x5F0 DLC: 8 Data: 0x00 0xF3 0x01 0x46 0x00 0x00 0x09 0x80
Standard ID: 0x5F0 DLC: 6 Data: 0x00 0x00 0xC5 0xA9 0x05 0x3A

0x82 0x81 0x80 - header
0x07 - Data Length (7 channels)
0x06 0x39 - channel 1
....
0x00 0x00 - channel 7
0xC5 0xA9 0x05 0x3A - CRC bytes

And channel 1 - 7 can be not in the same order as in Protocol description ? (seems that channel 1 is not RPM)

Am i right?

[kerail]

Awesome, seems that i was right. Channels can be unordered and the data structure is right.

Figure_1-3.png (40.95 KiB) Viewed 13893 times

Big thanks to you for sharing protocol description!