Race Technology Knowledge Base | GeneralCommsChannel / ConfigurePerformanceTest

(Type 9) Configure Performance Test

Byte offset	n bytes	Name	Notes
0	1	Triggered test flags	As existing definition
1	1	MFDD start threshold	Either a percentage or integer speed in user units depending on interval flags bit 3
2	1	MFDD end threshold	Either a percentage or integer speed in user units depending on interval flags bit 3
3	1	Units to display results	See definition
4	1	Interval flags	See definition
5	1	Info at intervals flags	See definition
6	1	1 = send new triggered configuration to speedbox 2 = reply with new triggered configuration from speedbox
7	1	This increments with each message sent
8	16	Test name	Terminate with 0 if less than 16 chars long
24	1	Triggered testing enabled
25	1	Spare
26	1	Spare
27	1	Spare
28	1	Start condition combining rule	0 => N/A (no additional condition), 1 => AND, 2 => OR
29	1	End condition combining rule	0 => N/A (no additional condition), 1 => AND, 2 => OR
30	2	Trigger rule 1 parameters	See definition
32	4	Trigger rule 1 threshold	F32 (see Trigger Rule Parameters table for units)
36	2	Trigger rule 2 parameters	See definition
38	4	Trigger rule 2 threshold	F32 (see Trigger Rule Parameters table for units)
42	2	Trigger rule 3 parameters	See definition
44	4	Trigger rule 3 threshold	F32 (see Trigger Rule Parameters table for units)
48	2	Trigger rule 4 parameters	See definition
50	4	Trigger rule 4 threshold	F32 (see Trigger Rule Parameters table for units)
54	4	Start/End marker longitude	S32 Degrees x 1e-7 (see Marker triggered definition)
58	4	Start/End marker latitude	S32 Degrees x 1e-7 (see Marker triggered definition)
62	4	Start/End marker heading	S32 degrees x 1e-5 (see Marker triggered definition)
66	4	End marker longitude	S32 Degrees x 1e-7 (see Marker triggered definition)
70	4	End marker latitude	S32 Degrees x 1e-7 (see Marker triggered definition)
74	4	End marker heading	S32 degrees x 1e-5 (see Marker triggered definition)

Note:

Trigger rule 1 is always used for start condition 1
Trigger rule 2 is always used for start condition 2
Trigger rule 3 is always used for end condition 1
Trigger rule 4 is always used for end condition 2

Previously this relationship was set by the indexes in old config msg 189, but in practice it was never varied from the above and hence the indexes have been abolished.

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