Attachment_0017_FASIT_PD_ICD_(DRAFT).pdf

ICD.FASIT.PD

PRESENTATION DEVICES

INTERFACE CONTROL DOCUMENT

RELEASE 1.2

22 MARCH 2016

Approved for public release; distribution is unlimited.

Page i

Release 1.2

22 March 2016

PREPARATION:

Prepared By:

Date:

James Todd

Lead Systems Engineer

LT2 - FASIT

Coordinated with:

Randi Kahl

Project Director

LT2 - FASIT

REVIEWED:

Endorsed by:

Paul Dumanoir

Chief Engineer, LT2

PM TRADE

Phil Gaylardo

Dep Dir Acq Log

PM TRADE

Robert Parrish

Dep Dir EL

APPROVED

Approved by:

Jorge Rivera

APM LT2

Page ii

List of Revisions

Revision Log

Revision/Version No. Description Date

Release 1.0

Initial Release

This is the initial release of this ICD since NGATS responsibility was moved within PEO STRI from PM ITTS to PM TRADE. It is part of the new set of FASIT ICDs based on the concept of a Common Interface Component.

The set now includes the System ICD, containing information common to all device types, and a series of ICDs with the messages and fault codes unique to each device type. This is one of that series.

Changes made due to the transition of responsibility include:

Changed project name from New Generation Army Targetry

Systems (NGATS) to Future Army System of Integrated

Targets (FASIT) per ATSC direction and updated all tables and diagrams accordingly.

Removed “For Official Use Only” designation. Received approval for public release with unlimited distribution.

Changed TMO to PM TRADE as the responsible lead agency for the document.

Changes from the previous NGATS ICD include:

Incorporated comments from the October 2005 Targetry WG meeting.

Incorporated comments from industry.

Changed Target Processor to Target Controller

Removed time stamp from all message headers.

Added “Reserved for Future Use” field to header (to fill space formerly occupied by the timestamp).

12/1/06

Page iii

Added text to indicate command IDs corresponding to unsupported capabilities should generate a “Can’t Comply.”

Deleted power and communication interface and cabling requirements which are common to all devices. This information is now in the System ICD referenced in Section

1.0.

Added default values for the Exposure Record and Sensor

Record fields in Message 2100 – Event Command (Table I).

Deleted the MILES Record field from this message.

In Message 2101 – Event Command Acknowledge (Table

II), deleted the Position Record, Hit Sensor Status, and

MILES Status fields.

Added a new Message 2111, Device ID and Capabilities, to respond to the common Device Definition Request (Message

100).

In Message 2102 – Presentation Device Status (Table IV) changed “Battery Status” to “Power Status” to indicate if the

PD is operating from installation (shore) power or from an alternative power source such as a battery.

Changed the MILES Ammo Type from “byte” to “unsigned char” to be consistent in the designation. This is in the

MILES Record (Table XIX) which is part of Message 2114

– Configure MILES Shootback Command (Table V) and

Message 2115 – MILES Shootback Status (Table VI).

Added new messages for Muzzle Flash and GPS location for

PDs supporting these features, as follows:

Message 2110 – Configure Muzzle Flash Command

Message 2112 - Muzzle Flash Simulation Status

Message 2113 – GPS Location

Added Section 2.3 and Table X to clarify the expected responses to the Event Command message for each

Page iv

Command ID.

In Table XI, Command ID, added Command IDs 5 through

7.

In Table XIII, Sensor Record, corrected the comment defining Hit Count, which had previously been a duplicate of the Hits to Kill description. Added clarification to the comments for the Reaction and Sensitivity fields.

In Table XIV, Response ID, clarified the requirement for the

Response Message Number and Response Sequence ID to be zero for unsolicited messages.

In Table XVII, Position Record, clarified the comment for the Exposure of the target to provide for a value of 45 while the PD is transitioning between concealed and exposed positions.

In Table XVIII, Hit Sensor Status, expanded the comment for Sensitivity to state the least sensitive and most sensitive values.

In Table XIX, MILES Record, updated the Basic MILES

Code enumeration to the current MILES Communication

Code (MCC) Standard, PMT 90-S002J, dated 19 January

2005. Added the statement that the MCC takes precedence over this document.

Added Table XXI, GPS Location Record in support of

Message 2113 – GPS Location Request (Table IX).

In Table XXII, PD Fault Codes, added Error Code 11 back to the table with a value of Unassigned.

Added Table XXIII, Target Reaction When Killed, to clarify expected PD reaction.

In Section 2.5, replaced the previous Messaging diagrams with more detailed, use specific diagrams.

Page v

Release 1.1

Added a note to Section 2.3, under Table X to clarify expected behaviors for moving targets upon issuance of a

Reset Device Command.

Added a note to Section 2.2.2, under Table II to clarify expected behaviors if Event Commands include data fields not supported by the Presentation Device.

Added a note to Section 2.2.4, under Table IV to clarify expected behavior if Hit Count is equal to Hits to Kill and an

Expose Command is issued.

Added a note to Section 2.2.1, under Table I to clarify expected behavior and utilization of the default values for the

Sensor Record data fields.

Modified Table XX to reflect that the Initial Delay and

Repeat Delay data fields as “Unsigned short” vice “Unsigned char”; added the range values of 0 to 60 to each of these

Delay data fields.

5/25/07

Release 1.2 Added command and status messages for multi-zone hit detection.

Updated “Additional Capabilities” field in Device ID and

Capabilities message to include a bit for declaring multi-zone hit detection capability.

Increased maximum value of hit count and hits-to-kill to 64.

Clarified when hits should be detected and reported.

Added Command IDs for Fire Tethered BES, Bob Target, Thermal On, Thermal Off, Aux1 On, Aux1 Off

Added Command message for tethered Audio control.

Corrected description of Battery Status field.

Corrected description of BOB reaction for moving targets.

Page vi

Revision Log

Redefined connection to thermal presentation devices.

Added descriptive text for “Reset Device” command to define behavior for resetting the target lifter.

Page vii

Table of Contents

1.0 SCOPE

1.1 DOCUMENT OVERVIEW

2.0 INTERFACE DESCRIPTION

2.1 POWER REQUIREMENTS

2.1.1 Thermal Device Control Characteristics

2.2 MESSAGES

2.2.1 Presentation Device Event Command Message

2.2.2 Event Command Acknowledgement Message

2.2.3 Device ID and Capabilities Message

2.2.4 Presentation Device Status Message

2.2.5 Configure MILES Shootback Command Message

2.2.6 MILES Shootback Status Message

2.2.7 Configure Muzzle Flash Command Message

2.2.8 Muzzle Flash Simulation Status Message

2.2.9 GPS Location Message

2.2.10 Tethered Audio Command

2.2.11 Hit Sensor Configuration Status Message

2.2.12 Hit Status Message

2.2.13 Presentation Device Simple Command

2.2.14 Configure Hit Sensor Command Message

2.3 COMMAND BEHAVIOR

2.4 PRESENTATION DEVICE MESSAGE COMPONENTS

2.4.1 Command ID

2.4.2 Simple PD Command Behavior

2.4.3 Simple PD Command ID

2.4.4 Simple Command Data

2.4.5 Zone Hit Sensor Configuration Record

2.4.6 Hit Record

2.4.7 Exposure Record

2.4.8 Sensor Record

2.4.9 Response ID

2.4.10 Acknowledge Response

2.4.11 Unit Status

2.4.12 Position Record

2.4.13 Hit Sensor Status

2.4.14 Extended Status

2.4.15 MILES Record

2.4.16 Muzzle Flash Simulation Record

2.4.17 GPS Location Record

2.4.18 Presentation Device Fault Field Codes

2.4.19 Presentation Device Reaction when Killed

2.5 FASIT TARGET CONTROLLER TO PRESENTATION DEVICE MESSAGING

Page viii

Page ix

List of Figures

Figure 1. Presentation Device's Thermal Control Connector Wiring Diagram .. Error! Bookmark not defined.

Figure 2. Device Connection Figure 3. Device Reconnect Figure 4. Device Connection Severed Figure 5. Expose Request Figure 6. Conceal Request

Figure 7. Movement Request Figure 8. Hit Detection Figure 9. Configure Hit Sensor

Figure 10. Device Definition Request Figure 11. Configure MILES Shootback Figure 12. Configure Muzzle Flash Simulation

Figure 13. GPS Location Request

Page x

List of Tables

Table I. Message Number 2100 - Event Command

Table II. Message Number 2101 - Event Command Acknowledge Table III. Message Number 2111 – Device ID and Capabilities Table IV. Message Number 2102 - Presentation Device Status Table V. Message Number 2114 - Configure MILES Shootback Command Table VI. Message Number 2115 - MILES Shootback Status

Table VII. Message Number 2110 - Configure Muzzle Flash Command Table VIII. Message Number 2112 - Muzzle Flash Simulation Status Table IX. Message Number 2113 - GPS Location Table X. Message Number 2116 – PD Audio Command

Table XI. Message Number 2117 – Hit Sensor Configuration Status Table XII. Message Number 2118 – Hit Status Table XIII. Message Number 2119 – Simple PD Command

Table XIV. Message Number 2120 – Configure Hit Sensor Table XV. Command Behavior

Table XVI. Command ID Table XVII. Simple PD Command Behavior Table XVIII. Simple Command ID

Table XIX. Simple Command Data Table XX. Zone Hit Sensor Configuration Record

Table XXI. Hit Record Table XXII. Hit Detect Zone Table XXIII. Exposure Record

Table XXIV. Sensor Record

Table XXV. Response ID Table XXVI. Acknowledge Response Table XXVII. Unit Status

Table XXVIII. Position Record Table XXIX. Hit Sensor Status Table XXX. Extended Status

Table XXXI. MILES Record Table XXXII. Muzzle Flash Simulation Record Table XXXIII. GPS Location Record Table XXXIV. Presentation Device Fault Field Codes Table XXXV. Target Reaction When Killed

Table XXXVI. Audio Record Table XXXVII. PD Audio Function Codes

Table XXXVIII. PD Audio Play Modes

1.0 Scope

The Presentation Devices Interface Control Document (ICD) describes the component interfaces required for two-way communication between the Future Army System of Integrated Targets

(FASIT) Target Presentation Devices and the FASIT Target Controller. This ICD is one of a set of documents that specifies the FASIT component interfaces required to support the FASIT system architecture. The physical and electrical characteristics of the interfaces as well as data types and requirements common to all device types are contained in the System Devices ICD, ICD.FASIT.SYS. In this document, Device means a FASIT compliant Target Presentation

Device.

1.1 Document Overview

This document is divided into two sections. Section 1.0 provides the scope of the document and a short overview of the document content. Section 2.0 discusses the specific power interfaces, communication message structures, and OEM fault codes used between the Target Controller and the Presentation Device. This document is intended to supplement the System Devices ICD referenced above.

2.0 Interface Description

2.1 Power Requirements

Primary and secondary power interfaces and cabling requirements are contained in the FASIT

System Devices ICD. The section below defines the additional requirement unique to the

Presentation Device.

2.1.1 Thermal Device Control Characteristics

A discrete control signal for the Target Direct Heating Representation Device will be supplied by the Presentation Device. The Presentation Device shall provide a connector that will supply the discrete control signal used for turning the thermal device On or Off. The Presentation Device is not responsible for providing power to the thermal device.

2.2 Messages

The set of messages used by a presentation device includes the typical Command, Command

Acknowledgement, Device ID and Capabilities, and Device Status messages, as well as PD-unique messages. These consist of Configure MILES Shootback, MILES Shootback Status, Configure Muzzle Flash, Muzzle Flash Simulation Status, and GPS Location messages. Each of these is documented below and the set is followed by the descriptions of the message fields. The

Message Header and Common BIT Request (Message 100) are described in the System Devices

ICD, ICD.FASIT.SYS.

In the event of communication link failure, the Presentation Device is responsible for reconnecting to the Target Controller and taking immediate precautionary measures. These measures include, but are not limited to, concealing the target silhouette if it is exposed, and bringing the PD to a complete stop if it is in motion.

Changes in PD status shall trigger an unsolicited Presentation Device Status message (2102) to be sent by the PD, regardless of the source of the status change (physical switches on the PD, field maintenance utilities, etc.). For exposure, the PD shall send an unsolicited Presentation

Device Status message (2102) when it locks into either the exposed or concealed position and when it is transitioning between the exposed and concealed state (Exposure value = 45) in either direction (exposing or concealing). For movement, the PD shall send an unsolicited Presentation

Device Status message (2102) when it starts moving, stops moving, and at regular increments when in motion (MIT 5 meter increments, MAT 10 meter increments). Commands will have sequence IDs ranging from 1 – (232 – 1). Unsolicited messages shall contain a response sequence

ID of zero. If a PD detects an error condition such as a target jam, it shall generate an unsolicited

Message Number 2102 – Presentation Device Status. The OEM fault field will be used to indicate the error.

2.2.1 Presentation Device Event Command Message

The PD Event Command message is sent from the Target Controller to instruct the PD to perform an operation based on the Command Identifier (ID). All commands require the PD to return an acknowledgement or status.

Table I. Message Number 2100 - Event Command

Field Size Message fields

Bits

0 – 127

Message Header

Message Number – unsigned short

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message (in bytes) – unsigned short

(Includes message header and body)

Bits

128 – 135

Command ID

(Table XVI) 8-bit enumeration

Bits

136 – 215

Exposure Record

(Table XXIII)

Exposure – unsigned char

Aspect – short integer

Direction – unsigned short

Move – 8-bit enumeration

Speed (MPH) – 32- bit floating point number

Default value Bits 136 – 215 = 0

Bits 216 –

Sensor Record

(Table XXIV)

ON/OFF – 8-bit enumerated type

Hit Count – unsigned short

Reaction – 8-bit enumerated type

Hits To Kill – unsigned short

Sensitivity – unsigned short

Mode – 8-bit enumeration

Burst Separation – unsigned short

Default value bits 216 – 303 = 0

Note: In the cases where the Sensor Record data fields are not utilized by the Command ID structure, the Event Command Message should set these values at zero. The default value for the bits is not reflective of Presentation Device behavior and the target controller must set these at the time of the exercise step execution.

2.2.2 Event Command Acknowledgement Message

This message is sent from the PD to the Target Controller in response to Command IDs (0, 1, 3, 4, 5) inside the Command message to inform the Target Controller that the PD has received a command, and whether or not it can perform the requested command.

Table II. Message Number 2101 - Event Command Acknowledge

Field Size Message fields

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message – unsigned short (Includes message header and body)

Bits

128 – 175

Response ID

(Table XXV)

Response Message Number - unsigned short

Response Sequence ID - unsigned integer

Bits

176 – 183

Acknowledge

Response (Table

XXVI)

8-bit enumeration

Note: If the Event Command Message is a Command ID (3), Expose Request, and the Exposure

Record contains values within the data fields for actions not supported by the Presentation

Device, the Presentation Device shall perform those behaviors that are applicable and ignore those behaviors that are not. If the device can perform some or all of the commanded behaviors, the device shall respond with an "S". Only if the device can not perform any of the behaviors commanded shall it respond with an "F".

2.2.3 Device ID and Capabilities Message

This message is sent by the PD to the Target Controller in response to a Device Definition

Request (Message Number 100) to provide the Target Controller with the device identifier and capabilities.

Table III. Message Number 2111 – Device ID and Capabilities

Message Header

Message Number – unsigned short

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message – unsigned short (Includes message header and body)

Bits

128 – 175

Response ID

(Table XXV)

Response Message Number – unsigned short

Response Sequence ID – unsigned integer

Bits

176 – 239

Device ID

64 bit globally unique identifier field. This field shall contain the MAC address for Ethernet interfaces. (MSB shall be padded with zeroes)

Field Size Message fields

Bits

240 - 247

Additional Device

Capabilities

1 Byte bit mask field. Bit 0 = MILES Shootback, Bit 1 = Muzzle Flash, Bit 2 = GPS, Bit 3 = Multi-

Zone Hit Detection, Bits 4 – 7 reserved for future use. Bit value of 1 indicates PD supports the capability. (e.g. 00000001 MILES support, 00000010 Muzzle Flash support, 00000111

MILES, Muzzle Flash and GPS support)

2.2.4 Presentation Device Status Message

This message is sent from the PD to the Target Controller in response to Command IDs (2, 6) inside the Command message to inform the Target Controller of the operational status of the device. In order for the Target Controller to maintain its internal hit count register, this message is also sent when the PD’s approved hit sensor registers a hit or whenever hit sensor status changes (either via command or otherwise). This is done without the Target Controller requesting this information. This message is also sent unsolicited to the Target Controller in the case of a device fault such as a target jam. This unsolicited message will contain the Fault Field code from Table XXXIV.

Table IV. Message Number 2102 - Presentation Device Status

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message – unsigned short (Includes message header and body)

Bits

128 – 175

Response ID

(Table XXV)

Response Message Number – unsigned short

Response Sequence ID – unsigned integer

Bits

176 – 199

Unit Status

(Table XXVII)

Power Status – unsigned char

OEM Fault Field – 16 bits (Table XXXIV)

Bits

200 – 303

Position Record

(Table XXVIII)

Exposure – unsigned char

Aspect – short integer

Direction Setting – unsigned short

Move Setting – 8-bit enumeration

Speed (MPH) – 32-bit floating point number

Track Position – unsigned short

Device Type – 8- bit enumeration

Bits 304 –

Hit Sensor Status

(Table XXIX)

Hit Count – unsigned short

ON/OFF – 8- bit enumerated type

Reaction – 8-bit enumerated type

Hits To Kill – unsigned short

Sensitivity – unsigned short

Field Size Message fields

Mode – 8-bit enumeration

Burst Separation – unsigned short

Bits 392 -

Extended Status

Thermal On/Off – Boolean (0 = Off, 1 = On)

Aux1 On/Off – Boolean (0 = Off, 1 = On)

Note: If the Hit Count is equal to Hits to Kill and an Expose Command is issued, the

Presentation Device shall take no action and shall stay concealed.

2.2.5 Configure MILES Shootback Command Message

This command is sent by the Target Controller to configure MILES Shootback on Devices which support that capability. Devices supporting this capability shall respond with a MILES

Shootback Status Message (2115) indicating the updated status. PDs that do not support MILES

Shootback shall respond with a negative command acknowledgement (Acknowledge Response =

‘F’) when receiving this command.

Table V. Message Number 2114 - Configure MILES Shootback Command

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message – unsigned short (Includes message header and body)

Bits 128 –

MILES Record

(Table XXXI)

Basic MILES Code – unsigned char

Ammo Type – unsigned char

Player ID# – unsigned short

Fire Delay – unsigned char

2.2.6 MILES Shootback Status Message

This message is sent by Presentation Devices that support MILES Shootback in order to communicate the current status to the Target Controller. If supported, this message shall be sent by the PD in response to Command ID 2. This message shall also be sent in response to a

Configure MILES Shootback Command (Message Number 2114).

Table VI. Message Number 2115 - MILES Shootback Status

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Field Size Message fields

Length of Message – unsigned short (Includes message header and body)

Bits

128 – 175

Response ID

(Table XXV)

Response Message Number – unsigned short

Response Sequence ID – unsigned integer

Bits 176 –

MILES Record

(Table XXXI)

Basic MILES Code – unsigned char

Ammo Type – unsigned char

Player ID# – unsigned short

Fire Delay – unsigned char

2.2.7 Configure Muzzle Flash Command Message

This command is sent by the Target Controller to configure Muzzle Flash simulation on Devices which support that capability. Devices supporting this capability shall respond with a Muzzle

Flash Simulation Status Message (2112) indicating the updated status. PDs that do not support

Muzzle Flash Simulation shall respond with a negative command acknowledgement

(Acknowledge Response = ‘F’) when receiving this command. PDs supporting muzzle flash shall accept and honor this command regardless of exposure status.

Table VII. Message Number 2110 - Configure Muzzle Flash Command

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message – unsigned short (Includes message header and body)

Bits

128 – 159

Muzzle Flash

Simulation

Record (Table

XXXII)

On/Off – Boolean (0 = Off)

Mode – 8-bit enumeration

Initial Delay – unsigned char

Repeat Delay – unsigned char

2.2.8 Muzzle Flash Simulation Status Message

This message is sent by Presentation Devices that support muzzle flash simulation in order to communicate the current status to the Target Controller. If supported, this message shall be sent by the PD in response to Command ID 2. This message shall also be sent in response to a

Configure Muzzle Flash Command (Message Number 2110)

Table VIII. Message Number 2112 - Muzzle Flash Simulation Status

Message Header

ICD Version Number – 2 unsigned short

Field Size Message fields

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message – unsigned short (Includes message header and body)

Bits

128 – 175

Response ID

(Table XXV)

Response Message Number – unsigned short

Response Sequence ID – unsigned integer

Bits

176 – 207

Muzzle Flash

Simulation Record

(Table XXXII)

On/Off – Boolean (0 = Off)

Mode – 8-bit enumeration

Initial Delay – unsigned char

Repeat Delay – unsigned char

2.2.9 GPS Location Message

This message is sent by Devices supporting GPS (i.e. those having an attached GPS receiver).

The purpose of the message is to inform the Target Controller of the GPS signal quality and where the target is currently located. After connecting to the Target Controller, the PD must report this data every 10 meters traveled. Moving targets (MIT/MAT) shall also report GPS location when detecting that carrier motion has stopped after having been in motion. All PDs supporting GPS must send this message when a command is received with a GPS Location

Request Command ID (Command ID = 7). When available, GPS Location data will be preferred over track position for determining target location. PDs that do not support GPS shall never send a GPS Location Message and shall respond with a negative command acknowledgement

(Acknowledge Response = ‘F’) when receiving a command requesting GPS location.

Table IX. Message Number 2113 - GPS Location

Message Header

Message Number – unsigned short

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message – unsigned short (Includes message header and body)

Bits

128 - 175

Response ID

(Table XXV)

Response Message Number – unsigned short

Response Sequence ID – unsigned integer

Bits

176 – 279

GPS Location

Record

(Table XXXIII)

GPS Figure of Merit (FOM) – 8-bit enumeration

Integral Latitude – unsigned short

Fractional Latitude – unsigned integer

Integral Longitude – unsigned short

Fractional Longitude – unsigned integer

2.2.10 Tethered Audio Command

This command message is intended to be used for legacy ranges with audio devices that are tethered to the PD. The PD will process this command and pass it on to the tethered device.

Table X. Message Number 2116 – PD Audio Command

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message (in bytes) – unsigned short

(Includes message header and body)

Bits

128 – 135

Audio Function

Code 8-bit enumeration

Bits

136 – 159 Audio Record

Track Number – unsigned char

Volume – unsigned char

Play Mode – 8-bit enumeration

2.2.11 Hit Sensor Configuration Status Message

This message is sent from the PD to the Target Controller in response to Command ID 5 (Table

XVIII) inside the Simple PD Command message (Table XIII) to inform the Target Controller of the operational status of the contact hit sensor and shall contain Zone Hit Sensor Configuration

Records for all hit detect zones that the PD supports. This message shall also be sent in response to a Configure Hit Sensor command, after the command acknowledgement, containing Zone Hit

Sensor Configuration Records for all affected hit detect zones. At least one Hit Zone

Configuration Record must be present in the message. A PD shall only send this message if it supports multiple hit zone detection and declares this capability by setting Bit 3 of the Additional

Capabilities field of the Device ID and Capabilities Message (Table III). Hit sensor configuration values in this message shall supercede settings in the Presentation Device Status message (Table

IV) but the PD is required to report values that are within the limits defined in this ICD.

Table XI. Message Number 2117 – Hit Sensor Configuration Status

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message – unsigned short (Includes message header and body)

Bits

128 – 175

Response ID

(Table XXV)

Response Message Number – unsigned short

Response Sequence ID – unsigned integer

Bits 176 –

(199 +

Zone Hit Sensor

Configuration

Hit Detect Zone – 8-bit enumeration

Reaction – 8-bit enumerated type

Field Size Message fields

(Number of zones –

1) * 24)

Record

(Table XX) Hits To Kill – unsigned char

2.2.12 Hit Status Message

This message is sent from the PD to the Target Controller when a hit is detected and when status is requested. The PD shall include one or more Hit Location Records in the hit status message.

For devices that are capable of detecting where the hit occurred, the Hit Location field shall be set to the value corresponding to what zone the hit occurred in. In response to a Simple PD

Command (Table XIII) with Command ID 5 (Table XVIII), the PD must include Hit Location

Records for all zones in which hits can be detected. In order for the Target Controller to maintain its internal hit count register, this message is also sent when the PD’s hit sensor registers a hit

(either via command or otherwise), containing a single record for the zone that the hit was registered in. This message shall also be sent whenever a command affecting the hit count is received, containing hit records for all affected hit detect zones. This is done without the Target

Controller explicitly requesting this information. A PD that is unable to detect hit location will send only one Hit Record, with a location of “Singular Zone” (0). A PD shall only send this message if it supports multiple hit zone detection and declares this capability by setting Bit 3 of the Additional Capabilities field of the Device ID and Capabilities Message (Table III). Hits reported with this message shall supersede the hit count in the Presentation Device Status message (Table IV) but the PD is required to report values that are within the limits defined in this ICD.

Table XII. Message Number 2118 – Hit Status

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message – unsigned short (Includes message header and body)

Bits

128 – 175

Response ID

(Table XXV)

Response Message Number – unsigned short

Response Sequence ID – unsigned integer

Bits 176 – (191

+ 24*(Number of zones-1))

Hit Record

(Table XXI)

Hit Count – unsigned char

Hit Location – 8-bit enumeration

Mortal – 8-bit Boolean (0 = False, 1 = True)

2.2.13 Presentation Device Simple Command

The PD Simple Command message is sent from the Target Controller to instruct the PD to perform simple operations that require little or no configuration information other than a command identifier. This command message also contains a data field for holding command data that applies to specific Command IDs (Table XVIII). For Command IDs where the Command

Data does not apply, the PD shall ignore this field. A PD shall only accept this message if it supports multiple hit zone detection and declares this capability by setting Bit 3 of the Additional

Capabilities field of the Device ID and Capabilities Message (Table III). A PD that does not support multiple hit zone detection shall respond to this message with a negative Command

Acknowledgment (Table II).

Table XIII. Message Number 2119 – Simple PD Command

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message (in bytes) – unsigned short

(Includes message header and body)

Bits

128 – 135

Simple

Command ID

(Table XVIII)

8-bit enumeration

Bits

136 – 151

Simple

Command Data

(Table XIX) short integer

2.2.14 Configure Hit Sensor Command Message

This command message is sent from the Target Controller to instruct the PD to configure one or more of its hit sensors. The command message shall contain at least one Zone Hit Sensor

Configuration record but may contain as many as one configuration record for each hit zone that it supports. The PD shall set the hit count to zero for all zones specified in this command. A PD shall only accept this message if it supports multiple hit zone detection and declares this capability by setting Bit 3 of the Additional Capabilities field of the Device ID and Capabilities

Message (Table III). If multiple hit zone detection is supported, the PD shall respond to this message with a Command Acknowledgment (Table II), Hit Zone Configuration Status message

(Table XI) and a Hit Status message (Table XII). If multiple hit zone detection is not supported, the PD shall respond to this message with a negative Command Acknowledgment (Table II).

Table XIV. Message Number 2120 – Configure Hit Sensor

Bits Message Header Message Number – unsigned short

ICD Version Number – 2 unsigned short

Sequence ID – unsigned integer

Reserved for future use. 4 bytes all zeros

Length of Message (in bytes) – unsigned short

(Includes message header and body)

Bits 128 –

(151 +

(Number of zones – 1) *

24)

Zone Hit Sensor

Configuration

Record

(Table XX)

Hit Detect Zone – 8-bit enumeration

Reaction – 8-bit enumerated type

Hits To Kill – unsigned char

2.3 Command Behavior

The table below specifies the fields from the Event Command Message (2100) that are to be read and applied by the PD for each Command ID, and the type of message that the PD shall respond with.

Table XV. Command Behavior

Command ID Command Fields Applied PD Response Message

0 – No Event (default) NONE Command Ack (2101)

1 – Reserved for Future Use NONE Command Ack (2101)

2 – Status Request

NONE Presentation Device Status

(2102)

MILES Shootback Status

(2115) if supported

Muzzle Flash Status

(2112) if supported

Hit Sensor Configuration

Status (2117) if supported

Hit Status (2118) if supported

3 – Expose Request Exposure

Aspect Command Ack (2101)

4 – Reset Device NONE Command Ack (2101)

5 – Move Request

Direction

Move

Speed

Command Ack (2101)

6 – Configure Hit Sensor

ON/OFF

Hit Count

Reaction

Hits To Kill

Sensitivity

Mode

Burst Separation

Presentation Device Status

(2102)

7 – GPS Location Request NONE GPS Location (2113)

8 – Fire Tethered BES Zone 1 NONE Command Ack (2101)

9 – Bob Target NONE Command Ack (2101)

10 – Thermal On

NONE Command Ack (2101)

Presentation Device Status

(2102)

11 – Thermal Off

NONE Command Ack (2101)

Presentation Device Status

(2102)

12 – Aux1 On

NONE Command Ack (2101)

Presentation Device Status

(2102)

13 – Aux1 Off

NONE Command Ack (2101)

Presentation Device Status

(2102)

14 – Fire Tethered BES Zone 2 NONE Command Ack (2101)

Note: A PD receiving a Reset Device command shall conceal, stop if in motion, gracefully close its TCP/IP connection (FIN or RST packet sent) with the Target Controller, and reboot. The reboot shall behave in the same manner as physically actuating the power switch to the OFF position and back to the ON position.

2.4 Presentation Device Message Components

This paragraph specifies the data types and records that will be contained in the message set described above.

2.4.1 Command ID

The Command ID is sent in the command message from the Target Controller to inform the PD as to which operation is to be performed. All commands require the PD to respond with either a negative Command Acknowledgement (Table II) if it can’t comply or with the messages specified in Table XV.

Table XVI. Command ID

Variable Type Definition Comments

1 Enumerated Type Unique identifier of this command

0 – No Event (default)

1 – Reserved for Future Use

2 – Status Request

3 – Expose Request

4 – Reset Device

5 – Move Request

6 – Configure Hit Sensor

7 – GPS Location Request

8 – Fire Tethered BES Zone 1

9 – Bob Target (Conceal and Expose)

10 – Thermal On

11 – Thermal Off

12 – Aux1 On

13 – Aux1 Off

14 – Fire Tethered BES Zone 2

2.4.2 Simple PD Command Behavior

The table below specifies messages that a PD should send in response to a Simple PD Command

Message (2119).

Table XVII. Simple PD Command Behavior

Simple Command ID PD Response Message

0 – No Event (default) Event Command Acknowledgement (2101)

5 – Request Hit Sensor Status

Event Command Acknowledgement (2101)

Hit Sensor Configuration Status (2117)

Hit Status (2118)

16 – Reset Hit Count Event Command Acknowledgement (2101)

Hit Status (2118)

17 – Increment Hit Count Event Command Acknowledgement (2101)

Hit Status (2118)

18 – Kill Event Command Acknowledgement (2101)

Hit Status (2118)

19 – Set Zone Hit Count Event Command Acknowledgement (2101)

Hit Status (2118)

2.4.3 Simple PD Command ID

The Simple PD Command ID is sent in the Simple PD command message (2119) from the

Target Controller to inform the PD as to which operation is to be performed. All commands require the PD to respond with either a negative Command Acknowledgement (Table II) if it can’t comply or with the message(s) specified in Table XVII.

Table XVIII. Simple Command ID

1 Enumerated Type Unique identifier of this command

0 – No Event (default)

5 – Request Hit Sensor Configuration

6 – Request Hit Count Status

16 – Reset Hit Count (Set Hit Count = 0 for all hit detect zones)

17 – Increment Hit Count

18 – Kill (Set Hit Count = Hits to Kill)

19 – Set Zone Hit Count

2.4.4 Simple Command Data

The table below specifies the meaning of the Command Data field in the Simple PD Command message for every Command ID. If the Command Data field is not applicable for a specific

Command ID, the PD shall ignore the value of this field. Otherwise, the PD shall interpret the value in the Command Data field as described in this table.

Table XIX. Simple Command Data

Command ID Command Data

0 – No Event (default) N/A

5 – Request Hit Sensor Status N/A

6 – Request Hit Count N/A

16 – Reset Hit Count N/A

17 – Increment Hit Count The Command Data field specifies which hit detect zone in which to increment the hit count.

18 – Kill The Command Data field specifies which hit detect zone in which to set hit count equal to hits to kill.

19 – Set Zone Hit Count

Command Data field contains two unsigned byte values:

Most Significant Byte: Hit Detect Zone

Least Significant Byte: Hit Count (0 – 64)

2.4.5 Zone Hit Sensor Configuration Record

The Hit Sensor Configuration is contained in the Hit Sensor Configuration Status and Hit Sensor

Configuration Command messages to specify the settings of the onboard hit sensor.

Table XX. Zone Hit Sensor Configuration Record

1 8-bit enumeration Hit Detect Zone

(Table XXII)

The value in this field indicates which hit detect zone the remaining fields apply to.

2 8-bit enumeration Reaction

(Table XXXV)

This value indicates how the PD should react when killed (Hit Count >= Hits to

Kill)

0 – Fall (default)

1 – Kill

2 – Stop

3 – Fall and Stop

4 – Bob Kill

5 – Bob Hold

Variable Type Definition Comments

3 Unsigned char Hits to Kill Number of times the target must be hit to register a kill (1 – default).

1 – 64

2.4.6 Hit Record

The Hit Record is sent in the Hit Count Status message from the PD to inform the Target

Controller how many hits have been detected. For devices capable of detecting hit locations, the

Hit Location field will be set to location the hit was detected.

Table XXI. Hit Record

Variable Type DEFINITION COMMENTS

Unsigned char Hit Count

The current hit count in the zone being reported. Valid range 0 - 64

8-bit enumeration

Hit Detect Zone

(Table XXII)

This field represents the zone where the hit was detected. For PDs that are unable to detect hit locations, the

“Singular Zone” value should be used.

8-bit enumeration Mortal Hit

Boolean value (0 = False, 1 = True) indicating if the most recently detected hit is considered Mortal.

Table XXII. Hit Detect Zone

This enumeration represents the zone where a hit was detected.

Hit Detect Zone Comments

0 Singular Zone Single hit detect zone for the entire target presentation

1 Head Head hit (Infantry targets only)

2 Chest Chest hit. (Infantry targets only)

3 Left Arm Left arm hit (Infantry targets only)

4 Right Arm Right arm hit (Infantry targets only)

5 Left Leg Left leg hit (Infantry targets only)

6 Right Leg Right leg hit (Infantry targets only)

7 Wheel Wheel hit. (Armor targets only)

8 Hull Hull hit (Armor targets only)

9 Armor Armor hit (Armor targets only)

10 Turret Turret hit (Armor targets only)

11-100 Future Reserved for future use.

2.4.7 Exposure Record

The Exposure Record is sent in the command message from the Target Controller to inform the

PD as to what parameters and/or positions to set the target presentation.

Table XXIII. Exposure Record

Variable Type DEFINITION COMMENTS

1 Unsigned char Exposure of the target

The value in this field informs the PD to place the presentation device to any position inclusive of between “0 = fully concealed to 90 = fully exposed”. (0 – default)

0 – 90 (degrees)

2 Short integer Aspect of the target

The value in this field sets the aspect of the presentation device. A value of 0 is considered “Hostile” and a value of 180 is considered “Friendly”. (0 – default)

3 Unsigned short Direction

The value in this field sets the direction for movement of a trackless moving presentation device. “0 = True North

(default).

0 – 359 Degrees

4 8-bit enumeration Move

The value in this field sets the direction for a moving presentation device using a track (1 = Moving away from a

‘HOME’ position and 2 = Moving toward the ‘HOME’ position). For a trackless moving presentation device, this value is used in conjunction with the ‘Direction’ value to determine how and where the device will move. A value of 0 should be interpreted as the target being stopped, regardless of the speed value.

0 – Stop (default)

1 – Forward

2 – Reverse

5 Float Speed (MPH)

The value in this field sets the speed at which a moving presentation device should move. (0 – default)

0 – 20 MPH

2.4.8 Sensor Record

The Sensor Record is sent in the command message from the Target Controller to inform the PD as to what parameters and/or positions are desired for the onboard hit sensor. For targets that support multi-zone hit detection, all of these fields except Hit Count and Reaction shall represent the global settings across all hit detection zones.

Table XXIV. Sensor Record

Variable Type Definition Comments

1 8-bit enumeration ON/OFF

The value in this field represents when the hit sensor should begin sensing hits.

0 – Off (default)

1 – On Immediately

2 – On at Commanded Position

3 – Off at Commanded Position

When the “On Immediately” setting is active, the target shall only report hits that are detected when the target is exposed or when it is transitioning from concealed to exposed. All other hits shall be ignored and not reported in status.

2 Unsigned Short Hit Count The value in this field represents the number of hits registered by the hit sensor since the last reset. For targets that support multi-zone hit detection, this field can be ignored. (0 – default)

0 – 64

3 8-bit enumeration Reaction

(Table XXXV)

This value indicates how the PD should react when killed (Hit Count >= Hits to

Kill). For targets that support multi-zone hit detection, this field can be ignored.

0 – Fall (default)

1 – Kill

2 – Stop

3 – Fall and Stop

4 – Bob

4 Unsigned Short Hits to Kill Number of times the target must be hit to register a kill (1 – default). For targets that support multi-zone hit detection, this field represents the cumulative hits to kill across all zones.

1 – 64

5 Unsigned Short Sensitivity This value will set the sensitivity of the hit sensor in order to record a hit. A value of 1 is least sensitive, 15 is most sensitive. By default, a PD shall set its

Variable Type Definition Comments sensitivity to a value that will reliably sense hits from commonly used ammunition in nominal weather conditions. A PD shall retain its current sensitivity when power cycled.

1 – 15

6 8-bit enumeration Mode The value in this field informs the target to count every impact as a hit or treat a string of hits separated by a defined interval as one hit. The ‘NCHS’ mode is used with a non-contact hit sensor.

0 – NCHS

1 – Single (default)

2 – Burst

7 Unsigned Short Burst Separation The time separation between object impacts on the target face that the target uses to differentiate hits when in the

“Burst’ mode. (250 – default)

100 – 10000 milliseconds

2.4.9 Response ID

The Response ID is used by the Target Controller to identify what message the device is responding to.

Table XXV. Response ID

Variable Type Definition Comments

1 Unsigned short Response Message

Number

This number informs the Target

Controller what type of message the PD is responding to. For unsolicited status, this field shall be set to zero. Otherwise, it shall be set to the message number of the command.

2 Unsigned integer Response Sequence ID

This number informs the Target

Controller that the response is the proper response that the device is responding to. For unsolicited status, this value should be set to zero. Otherwise, this value shall be set to the sequence ID of the command. (Default = 0)

2.4.10 Acknowledge Response

The Acknowledge Response is used to inform the Target Controller that the message sent was received by the PD and, based upon the value returned, whether or not it can or will perform the command requested. This response is used for commands that do not return status parameters requested by other command event IDs.

Table XXVI. Acknowledge Response

Variable Type Definition Comments

1 Char Acknowledgement from the PD to the Target

Controller of receipt of the command.

This value will inform the Target

Controller whether the message was received and whether the device can comply with the command. (Default = “S”)

“S” – Received and complied.

“F” – Received, can’t comply.

2.4.11 Unit Status

The unit status provides the Target Controller information on the operational status of the PD.

The manufacturer will provide information about possible operational errors within their unit by setting specific bits in the Original Equipment Manufacturer (OEM) Fault Field.

Table XXVII. Unit Status

Variable Type Definition Comments

1 Unsigned char Power Status

The value in this field represents the power status:

0 – Shore Power (default)

1 – 10 Battery Power. A value of 10 indicates fully charged battery. A Power

Status value of 1 is “critically low”, meaning that the target can no longer operate on battery power. When the battery power is critically low, the PD shall send the “Low battery detected”

OEM fault (Fault code 20. Table

XXXIV). If the value of bits 0 – 3 of this field is 1 – 10, bits 4 – 7 of this field shall indicate “Charging Status”. If the

PD is connected to a battery charging device (battery actively charging), the

Charging Status shall be set to 1.

Otherwise it should be set to zero.

2 Bit Field Error Codes OEM Fault Field (default = 0000 Hex)

0000 – Fully Operational

2.4.12 Position Record

The Position Record is received in the acknowledge and status messages from the PD to inform the Target Controller as to what parameters and/or positions that the target representation is in.

Table XXVIII. Position Record

VARIABLE

TYPE

DEFINITION COMMENTS

1 Unsigned char Exposure of the target

The value in this field informs the Target

Controller what position the presentation device is

in. “0 = fully concealed to 90 = fully exposed”. (0

– default) When transitioning between exposed and concealed states in either direction (exposing or concealing), the PD shall send a value of 45.

0 – 90 (degrees)

2 Short integer Aspect of the target

The value in this field informs the Target

Controller what the aspect of the presentation device is currently at. A value of 0 is considered

“Hostile” and a value of 180 is considered

“Friendly”. (0 – default)

3 Unsigned short Direction

The value in this field informs the Target

Controller of the direction of movement of the trackless presentation device. “0 = True North

(default).

0 – 359 Degrees

4 8-bit enumeration Move setting

The value in this field informs the Target

Controller of the direction a moving presentation device using a track is moving. (1 = Moving away from a ‘HOME’ position and 2 = Moving toward the ‘HOME’ position). For a trackless moving presentation device, this value is used in conjunction with the ‘Direction’ value to determine how and where the device is moving.

0 – Stop (default)

1 – Forward

2 – Reverse

5 Float Speed (MPH) setting

The value in this field informs the Target

Controller of the speed at which a moving presentation device is moving. (0 – default)

0 – 20 MPH

6 Unsigned short Track Position

The value in this field informs the Target

Controller of the location of the device on the track in relation to the ‘HOME’ position “0 = ‘HOME’ position (0 – default).

0 – 1000 (meters)

VARIABLE

TYPE

DEFINITION COMMENTS

7 8-bit Enumeration Device Type

The value in this field informs the Target

Controller of what type of PD it is in communication with.

0 - default

1 – Stationary Infantry Target (SIT)

2 – Moving Infantry Target (MIT)

3 – Stationary Armor Target (SAT) Light

4 – Stationary Armor Target (SAT) Heavy

5 – Moving Armor Target (MAT)

2.4.13 Hit Sensor Status

The Hit Sensor Status is received in the acknowledge message from the PD to inform the Target

Controller as to what parameters and/or positions set for the onboard hit sensor and to inform the

Target Controller that a hit has occurred. For targets that support multi-zone hit detection, all of these fields except Hit Count and Reaction shall represent the global settings across all hit detection zones.

Table XXIX. Hit Sensor Status

1 Unsigned Short Hit Count

The value in this field represents the number of hits registered by the hit sensor since the last reset. For targets that support multi-zone hit detection, this field shall always be 0. (0 – default)

0 – 64

2 8-bit enumeration ON/OFF

The value in this field represents what setting was selected for the hit sensor to begin sensing hits.

0 – Off (default)

1 – On Immediately

2 – On at Commanded Position

3 – Off at Commanded Position

When the “On Immediately” setting is active, the target shall only report hits that are detected when the target is exposed or when it is transitioning from concealed to exposed. All other hits shall be ignored and not reported in status.

3 8-bit enumeration Reaction The value in this field informs the

Target Controller what reaction was set

Variable Type Definition Comments for the target to perform upon Kill (Hit

Count >= Hits to Kill). For targets that support multi-zone hit detection, this field shall always be 0.

0 – Fall (default)

1 – Kill

2 – Stop

3 – Fall and Stop

4 – Bob

4 Unsigned Short Hits to Kill The value in this field informs the

Target Controller of the current setting for ‘hits to kill’ (1 – default). For targets that support multi-zone hit detection, this field represents the cumulative hits to kill across all zones.

1 – 64

5 Unsigned Short Sensitivity This value will inform the Target

Controller the setting of the sensitivity for the hit sensor to record a hit. A value of 1 is least sensitive, 15 is most sensitive. By default, a PD shall set its sensitivity to a value that will reliably sense hits from commonly used ammunition in nominal weather conditions. A PD shall retain its current sensitivity when power cycled. .

1 – 15

6 8-bit enumeration Mode The value in this field informs the

Target Controller as to what mode the

PD is in for detecting hits.

0 – NCHS

1 – Single (default)

2 – Burst

7 Unsigned Short Burst Separation The value in this field informs the

Target Controller of what time separation between object impacts on the target face that was select when in the “Burst’ mode. (250 – default)

100 – 10000 milliseconds

2.4.14 Extended Status

The extended status contains additional status values that were not present in earlier versions of the FASIT PD ICD. These fields were added to the end of the PD Status message in order to facilitate backward compatibility.

Table XXX. Extended Status

1 Boolean Thermal On/Off

Indicates if the thermal representation is turned on or off. 0 = Off, 1 = On.

2 Boolean Aux1 On/Off

Indicates if auxiliary device 1 is turned on or off. 0 = Off, 1 = On.

2.4.15 MILES Record

The MILES Record is sent in the command message from the Target Controller to inform the PD as to what parameters are desired for the MILES shootback device. It is also included in the PD

Status message to inform the Target Controller what parameters are set I n the PD for the shootback device.

The codes shown in this table are from PMT 90-S002J, Multiple Integrated Laser Engagement

System (MILES) Communication Code (MCC) Standard, dated 19 January 2005. In the event of a discrepancy between the MCC and this ICD, the latest…