Feature to READ engine data from any OBD-II vehicle ECU into MaxxECU, mostly used in piggyback applications.
Note: Please disconnect the MaxxECU when using any other OBD-II diagnostic tool.
Please be aware, that many vehicles DOES NOT HAVE this available in the system!
CAN OBD-II ID setup
Most OEM ECUs handles broadcast request differently, therefore we have the below options for you to try on your vehicle CAN bus.
request ecu id
The request ID sent to the system.
Note: The broadcast (0x7DF) is requesting data from ALL VEHICLES ECUs, which puts a high load on the CAN-bus, but it might be required for some vehicles.
response ecu id
The response ID the system is listening to.
Note: It is most likely that the request ecu id and the response ecu id has the same functional value.
An example where we request engine data parameters from the functional "0" and get response back from the functional "0".
An example where we request ALL vehicle data parameters with the broadcast request get response back from the functional "0".
Note: This will put a high load on the CAN-bus.
CAN OBD-II
Get CLT from OBD-II
Reads the CLT from the vehicle OBD-II protocol and uses it as the CLT in MaxxECU.
Get IAT from OBD-II
Reads the IAT from the vehicle OBD-II protocol and uses it as the IAT in MaxxECU.
Get TPS from OBD-II
Reads the TPS from the vehicle OBD-II protocol and uses it as the TPS in MaxxECU.
Get MAP from OBD-II
Reads the MAP from the vehicle OBD-II protocol and uses it as the MAP in MaxxECU.
Get SPEED from OBD-II
Reads the SPEED from the vehicle OBD-II protocol and uses it as the SPEED in MaxxECU.
Get Lambda from OBD-II
Reads the Lambda value from the vehicle OBD-II protocol and uses it as the Lambda in MaxxECU.
Note: Dont forget to change inputs --> lambda sensor, lambda sensor X to lambda from OBD2 input system.
Get TORQUE from OBD-II
Reads the engine Torque from the vehicle OBD-II protocol.
Get RPM from OBD-II
Reads the RPM from the vehicle OBD-II protocol and uses it as the MAP in MaxxECU.
Note: Only for reading, this value CANNOT be used for fuel/ignition control.
The CAN Inputs system can be used to request more customized CAN ODB2 PIDs.
1. Enable the get CLT from OBD2 feature in CAN Bus --> CAN OBD2 input, which now takes engine CLT from the stock ECU using OBD-II data and completely discards anything on the CLT electrical inputs.