Call me back | My basket | Checkout | Add to email list

     You are here: Website » Knowledge base

« back to website
  1. Ordered list

DataAndConfigurationMessages / 102GeneralCommsChannel

General comms channel

Description of General Comms Channel (channel 102):

Channel Number102
Total LengthVariable length message
CHANNEL MESSAGE LENGTH MESSAGE TYPE DATA0 DATA1..............DATAn CHECKSUM


MESSAGE TYPE description

  1. type 0 - COMMUNICATION INITIALISE MESSAGE
  2. type 1 - REQUEST TOTAL RUN FILE COUNT MESSAGE
  3. type 2 - REQUEST RUN FILE NAME MESSAGE
  4. type 3 - REQUEST RUN FILE DATA MESSAGE
  5. type 4 - REQUEST DISCONNECT MESSAGE
  6. type 5 - TRIGGERED TEST DATA MESSAGE
  7. type 7 - GENERAL TEXT MESSAGE
  8. type 8 - EXTERNAL ADC CALIBRATION MESSAGE
  9. type 9 - CONFIGURE PERFORMANCE TEST
  10. type 32, 33 and 34 - ADAS
  11. type 128 -TIME SYNCHRONIZATION MESSAGE


Triggered test flags:

Bit 0: Enable analog output
Bit 1: Enable pulse output
Bit 2: Enable distance output (no longer used, but retained in case required again)
Bit 3: Subsequent start triggers reset test (no longer used)
Bits 4->7 Currently unused


Units to display results:

Bits 0-3 Speed units:
0 = m/s
1 = kph
2 = mph
3 = knots
4->7 currently unused
Bits 4->5 Distance units:
0 = m
1 = ft
2->3 currently unused
Bits 6->7 Accel units:
0 = g
1 = m/s/s
2->3 currently unused


Interval flags

No bits set: No interval output
Bit 0 set: Output at speed intervals
Bit 1 set: Output at distance intervals
Bit 2: Currently unused
Bit 3: 0 => MFDD thresholds are % of start speed

1 => MFDD thresholds are speed in currently selected speed units

Bits 4-7: Currently unused


Info at interval flags

Bit 0: Time into test
Bit 1: Deviation distance
Bit 2: Acceleration
Bits 3-7: Reserved for when a customer inevitably wants something else output!

Note: Path dist is always output for speed intervals, and speed is always output for dist intervals, hence we don't include them here.


Trigger rule parameters

Byte 0: Bits 0->1: Hardware index (trigger number or ADC number, 0->3)
Bits 2->6: Reserved in case we require larger hardware indexes in future
Bit 7: Polarity, 0 => falling, 1 => rising
Byte 1: Condition 0 => NULL (not configured)

1 => SPEED, units of m/s

2 => TO A HALT (end condition) or PULL AWAY (inertial based) (start condition)

3 => ACCEL_LONG , units of g

4 => ACCEL_LAT, units of g

5 => ANALOG, units of volts

6 => HARDWARE TRIGGER, no units

7 => COMMAND MSG, no units

8 => DISTANCE, units of meters

9 => PULL AWAY (speed based)

10 => MARKER TRIGGERED (unit of distance in meters)


Marker triggered:

Start/End marker (longitude, latitude, heading) [index 54 to 65] contains values of start marker if ‘Marker triggered’ is selected for one of the conditions of ‘Start condition’. If ‘Marker triggered’ isn’t selected for ‘Start condition’, and is selected for one of the conditions of ‘End condition’, these fields contain values of end marker.

End marker (longitude, latitude, heading) [index 66 to 77] contains values of end marker if ‘marker triggered’ is selected for one of the conditions of ‘End condition’ while ‘marker triggered’ is selected for one of the conditions of ‘Start condition’.

If ‘Marker triggered’ isn’t selected for any condition, these fields are not present in the message.

All marker values are big endian, 2's complement signed 32-bit integers.


Page last modified on June 25, 2018, at 02:58 PM