Editing CAN bus Mapping (section)

== Detailed CAN mappings ==

=== 0x085 – Steering angle ===

'''DLC:''' 5

{| class="wikitable"
! Bytes !! Encoding !! Formula !! Status
|-
| B0–B1 || Signed 16-bit, little-endian || Steering angle (degrees) = raw × 0.09 || '''Confirmed'''
|-
| B2–B4 || Undetermined || – || Unknown
|}

=== 0x0A2 – Wheel/vehicle speed ===

'''DLC:''' 7. An earlier Exige V6 RaceCapturePRO mapping associates this identifier with wheel/vehicle speed. Byte-level decoding has not yet been confirmed on this reference vehicle.

'''Status: Reference.'''

=== 0x0A4 – Additional wheel speed ===

'''DLC:''' 8. Earlier RaceCapturePRO material identifies additional wheel-speed information here. Byte-level validation remains outstanding.

'''Status: Reference.'''

=== 0x0A8 – Candidate status ===

'''DLC:''' 3

{| class="wikitable"
! Byte !! Observations !! Interpretation !! Status
|-
| B1 || <code>0x01</code>, <code>0x09</code> || Possible vehicle or mode status; not conclusively decoded || Provisional
|}

Do not treat these raw values as an established Normal/Sport/Race mapping.

=== 0x102 – Unidentified frame ===

'''DLC:''' 3. Example at standstill: <code>00 00 9C</code>. '''Status: Observed.'''

=== 0x114 – Engine and driver inputs ===

'''DLC:''' 6

{| class="wikitable"
! Byte/bit !! Signal !! Decode !! Status
|-
| B0–B1 || Engine RPM || Older reference: 16-bit raw × 0.25; endian/order must be checked against captures || Reference / calibration tested
|-
| B3 || Throttle / accelerator || Percent = raw × 100 / 255 || '''Confirmed'''
|-
| B4 bits 4–5 (<code>0x30</code>) || Clutch input || See below || '''Confirmed'''
|-
| B4 bit 7 (<code>0x80</code>) || Drive-mode button activity || 0 = inactive; 1 = active || '''Confirmed'''
|-
| B5 bit 0 (<code>0x01</code>) || Brake pedal || 0 = released; 1 = pressed || '''Confirmed'''
|}

==== Clutch input ====

Apply mask <code>0x30</code> to B4:

{| class="wikitable"
! Masked value !! Observed state
|-
| <code>0x00</code> || Released
|-
| <code>0x10</code> || Intermediate
|-
| <code>0x20</code> || Deeper / fully pressed
|}

==== Drive-mode button versus selected mode ====

B4 bit 7 captures activity of the mode selector. It does '''not''' directly report the selected driving mode. See [[#Driving modes – Normal, Sport and Race|Driving modes]].

==== Engine RPM testing ====

Engine tests have included idle and approximate 2,000 and 3,000 RPM holds. A discrepancy between the dashboard and an initial iPhone display led to subsequent firmware corrections. Publish a final byte order and scaling only after checking the corrected output against recorded raw frames.

=== 0x0B7 – High-rate unidentified frame ===

'''DLC:''' 7. B3 and B6 change frequently. '''Status: Observed.'''

=== 0x303 – Vehicle dynamics ===

'''DLC:''' 7. A strong candidate for yaw-rate and lateral-acceleration data. B4 has been investigated for lateral acceleration, but signedness, offsets and scale factors are not yet validated.

'''Status: Provisional.'''

=== 0x400 – Vehicle status, coolant and fuel candidates ===

'''DLC:''' 7

Recorded example: <code>00 00 00 02 C4 81 18</code>

The following assignments were investigated during firmware development and are '''not yet a validated decoding of this entire frame''':

{| class="wikitable"
! Byte !! Candidate signal !! Proposed calculation !! Status
|-
| B4 || Fuel level || Percent = raw × 100 / 255 || Provisional; exact byte/source needs correlation
|-
| B6 || Coolant temperature || Degrees C = raw − 40 || Provisional; raw frame correlation required
|}

'''Consistency check:''' In the example frame B6 is hexadecimal <code>0x18</code> (decimal 24), giving −16°C under the proposed temperature formula. That is not a plausible warm-engine reading. Accordingly, the example does '''not''' validate this coolant mapping. Similarly, B4 is <code>0xC4</code> (decimal 196), not the separately observed fuel candidate raw value 137. Avoid combining measurements taken at different times into a single supposedly validated frame.