Hi Zantar,
Can I ask what you are trying to achieve?
I guess you are monitoring the CAN bus and your CAN tool is just reading the ID's and the Bit data as seen in your CAN log file.
That is probably all you will be able to access unless you have the manufactures CAN DBC file. I use Vector Canalzer and without the DBC file you can only see the ID and Bit data. The DBC file attached a human interface to the ID's such a 'Throttle_value' etc.
I have just watch an interesting video on youtube 'Goat Rope Garage' - CAN bus search replicating a CAN message. This goes through the very time consuming task of identifying a CAN message by trial and error.
If you are going down this path, trying to reduce the CAN traffic on the bus seems logical. Just power on e module at a time with sub harness and termination resistors as required.
Why do you need to identify these massages?
Can I ask what you are trying to achieve?
I guess you are monitoring the CAN bus and your CAN tool is just reading the ID's and the Bit data as seen in your CAN log file.
That is probably all you will be able to access unless you have the manufactures CAN DBC file. I use Vector Canalzer and without the DBC file you can only see the ID and Bit data. The DBC file attached a human interface to the ID's such a 'Throttle_value' etc.
I have just watch an interesting video on youtube 'Goat Rope Garage' - CAN bus search replicating a CAN message. This goes through the very time consuming task of identifying a CAN message by trial and error.
If you are going down this path, trying to reduce the CAN traffic on the bus seems logical. Just power on e module at a time with sub harness and termination resistors as required.
Why do you need to identify these massages?
