Innovate Motorsports OT-2 SDK - Manual (Page 17)

17
3 0 0 0 0 0 Ax1
9 Ax1
8 Ax1
7 0 Ax1
6 Ax1
5 Ax1
4 Ax1
3 Ax1
2 Ax1
1 Ax1
0
4 0 0 0 0 0 Ax2
9 Ax2
8 Ax2
7 0 Ax2
6 Ax2
5 Ax2
4 Ax2
3 Ax2
2 Ax2
1 Ax2
0
5 0 0 0 0 0 Ax3
9 Ax3
8 Ax3
7 0 Ax3
6 Ax3
5 Ax3
4 Ax3
3 Ax3
2 Ax3
1 Ax3
0
6 0 0 0 0 0 Ax4
9 Ax4
8 Ax4
7 0 Ax4
6 Ax4
5 Ax4
4 Ax4
3 Ax4
2 Ax4
1 Ax4
0
7 0 0 0 0 0 Ax5
9 Ax5
8 Ax5
7 0 Ax5
6 Ax5
5 Ax5
4 Ax5
3 Ax5
2 Ax5
1 Ax5
0
Although the Serial 2 specification documents this as 7 words, the last five (3-7) are Aux
Channels, and can be treated as such. Word 2 contains battery voltage (albeit in a
complex formula) and can also generally be ignored.
This leaves the first two words. The good news is that they contain the same three values
(L, F, and AF) as the ‘new’ lambda channel. And, better still, the meaning is the same.
The bad news is that bit 15 is set in the first word, and bit 14 may or may not be set,
eliminating our ability to find header bytes or count off channels simply. In any event, the
LM-1 channel would have to identified so the battery information would not be
inadvertently treated as an Aux Channel.
Response Packets
If you value your sanity (and the stability of the devices in the MTS chain), you will only
ever send two queries:
1
• 0xCE to obtain device names
• 0xF3 to obtain device types
Yes, there are other documented queries, and they look interesting, but these are the only
two that we use in our software, so they are the only ones consistently and correctly
implemented in all devices.
The response packet generated by each is very similar:
The header we covered above. The “Response Type” word is also pretty simple. It is the
Query (0xCE or 0xF3), placed in a word which follows the same rules as an Aux Channel
in a Data Packet. That is, the high bit of both bytes is 0:
Word Bit
15 Bit
14 Bit
13 Bit
12 Bit
11 Bit
10 Bit
9 Bit
8 Bit
7 Bit
6 Bit
5 Bit
4 Bit
3 Bit
3 Bit
1 Bit
0
1 For the one exception to this, see “Special Considerations for Network/Wi-Fi” later in this document.