Mitsubishi ECU - OBD Command Code and Protocol

OBD Command
Since there is a mistake on my first post regarding of the protocol,  I've made some more research on that. Here is the result on how the ecu response to the command.

Based on Christia999 code, I found the OBD command code was setting at here (refer to picture 1 and picture 2 below)

Picture 1 (The OBD Command)

 

  Picture 2

If we look further on the code comment, the OBD code were divided into few table ranges to store the variable value. Here are the table range comments by Christia999:

So how does it work? Let say we want to get the RPM value from the ECU. So the command we should be use is 0x21 (based on Mitsubishi ECU command that I've posted before). Whenever we send 0x21 command, the ECU will look-up at the variable value of the table which can be refer at the picture below.

So it is prove that the function for RPM is correct where RPM function is y=31.25*x and x is a value response by ECU.

Communication Signal

As I've wrote before, the communication with the ECU can describe as below:

• Serial communications rate is 1953 baud, 8 bits, 1 stop bit, no parity, TTL. 
• Communication signal is "Inverted"
• Communication referral as 1 byte sent and 1 bytes receive

There are some people a little bit confuse including me about the multiplexing communication. Wikipedia explain that multiplexing (also known as muxing) is a method by which multiple analogue message signals or digital data streams are combined into one signal over a shared medium.

Multiplexing communication between ECU

Reference:

• E931/E932 source files with comments and symbols.
• Multiplexing on Wikipedia