CANbus reverse-engineering
Budget: €30 – €250 EUR
I have raw traffic from a CANbus network and need it reverse-engineered. Parallell to the CANbus-log, I have a modbus-log with known values. These two logs are time synced. Every available signal in the modbus-log should be easy to find, but there is also data NOT present in modbus (f.ex DC-bus high voltage).
Example target readings
• Temperature
• Voltage
• Power
• State of Charge (SOC)
• Charge power allowed
• Discharge power allowed
Acceptance criteria
1. A mapping document showing every discovered CAN ID, byte position, scaling factor, and its matched Modbus register.
If you already have experience sniffing CAN traffic with tools like SocketCAN, candump, Wireshark, or SavvyCAN and have built Modbus gateways before, this should be straightforward.
More detailed information about the system will be provided to the person/team awarded the task.
Example target readings
• Temperature
• Voltage
• Power
• State of Charge (SOC)
• Charge power allowed
• Discharge power allowed
Acceptance criteria
1. A mapping document showing every discovered CAN ID, byte position, scaling factor, and its matched Modbus register.
If you already have experience sniffing CAN traffic with tools like SocketCAN, candump, Wireshark, or SavvyCAN and have built Modbus gateways before, this should be straightforward.
More detailed information about the system will be provided to the person/team awarded the task.