MANDRIL logo

MANDRIL - Tracks - Auto-Analysis: Powerful spreadsheeting and graph plotting tools

Decoding

MANDRIL is multi-link compatible, with the capability to decode messages from several link types. The input to MANDRIL is a data file containing the recorded messages or data blocks. A wide range of different file formats (> 50) can be handled depending on terminal type, link type and the source of recording. Messages are decoded into a spreadsheet format for ease of analysis via a rich feature set of spreadsheet functions and graph plotting.

Data link and terminal types handled include:

Link 16 (TADIL J)

Link 11 (TADIL A)

Link 11B (TADIL B)

VMF

MIDS LVT

JTIDS Class 2

URC-138

A message sheet from a MANDRIL decode

The Message Analysis Component of MANDRIL decodes the recorded messages and puts the results into custom spreadsheets. Filters can be applied e.g. by time slice, by Source Track Number or by message type. Each spreadsheet provides a decode of each message or data block type with output in readable English format (i.e. using field value names rather than numbers. In this form the data can be analysed further using the powerful built-in Excel tools.

Platform System Analysis

In addition to decoding Link messages, MANDRIL can be used to analyse Data Transfer Blocks (DTBs) recorded on internal system interfaces, e.g. within a terminal or on host-to-terminal interfaces. The data formats obtained from the platform interface definition specifications are built into the tool’s database of block formats. Since data block types may be embedded within each other, the data is analysed in a hierarchical way. E.g. message blocks may be contained within Terminal Output Messages (TOMs).

Thus the TOM blocks are decoded into their own sheet and the embedded message blocks decoded into message sheets. To assist navigation among the sheets, Hyperlinks are automatically added linking the TOM blocks to their associated messages. The decoded data acquires a Web-like structure, which will be familiar to most users and whose advantages for rapid searching through a mass of data is well known.

Message and DTB Statistics

Graphical representations of a data file’s content may be produced rapidly using the statistics tool. The user may select from a range of analysis criteria (message type, DTB type, source track number, Link type, time of day, etc.) and a one- or two-dimensional frequency analysis is performed without fully decoding the data. This tool is often used in order to screen a file for content before selection of decode filters and full analysis of the data.

Hyperlinks for navigation between block decodes
Wide range of data input formats
Numerical and graphical output formats
Message formats are easily updated and extended
Graph plotting wizard with pre-defined graph types

Statistical Analysis by message type and STN

Drawing Graphs and Trails

Graphical representations of the analysed data may be produced rapidly using the Graphs Wizard. The wizard guides the user through the selection of fields for plotting and automatically produces a plot of the selected fields. The type of graph plotted is chosen from the fields selected and can be one of a number of types, including:

Plot of one field against time for each TN as a separate series
Plot of two fields against time on the same chart with separate axes
Plots of track position against a background map for each TN (Track History Trails)

For example, the user may plot a graph of Time Quality against time for each platform, which will quickly reveal any degradations and changes of Net Time Reference that may have occurred. Geodetic Position Quality and Altitude may be plotted on the same chart to determine any altitude effects on quality. A track history plot shows the evolution of track positions over time, and can be used for example to highlight registration or sensor errors in the reported tracks. For those graphs where multiple TNs are plotted simultaneously, the wizard allows the user to quickly select the TNs that will appear.

GPQ and Altitude from PPLI Data

Track History Trails

Track History Trails

Decodable File Formats

MANDRIL is capable of decoding a wide range of file formats which result from the different terminal types and recording devices used to capture link data. The following tables list the current capability, which is being continually extended.

JTIDS Class 2
Input Format And Default Extension	Description
Messages Only .smm, .l16	This format consists of binary fixed-length records. Files in this format can be made by using the ‘Write Message’ function of MANDRIL, with a file containing DTBs or another message file as input. Can contain Link 16, Link 11 or IJMS messages. They can also be obtained from other authorities (e.g. files in this format are produced by the UK’s MIDAS utilities – Link 16 only).
F3 DRP Quick Look Hex .con, .out	Data Recording Program (DRP) conversion of the Data Transfer Block (DTB) output from the Class 2 terminal Tape Recording Support Device (TSRD) port into a hex format (Quick Look Hex)
Class 2 TSRD Recording .jtids, .jti, *.tsrd	The format of the data recorded to 9-track tape by the TSRD device. It is a binary format consisting of records of up to 1920 16-bit words. Each record contains a number of buffers delimited by ‘EEBA’ words, and each buffer contains a number of DTBs delimited by ‘CAFE’ markers.
Class 2 JITS .trd, .jits	The format of the data recorded to 9-track tape or DAT by the JITS device. It is a binary format similar to the Class 2 TSRD Recording format. MANDRIL will read both DAT and 9-track formats, allowing for the differences between them. The DRP program can also produce Quick-Look Hex format files from JITS recordings.
F3 CAT (DRPX) *.txt	Quick Look Hex subjected to further reduction using the DRPX program for use in the DERA AT&E Tornado analysis tool, PC CAT. Comma-delimited hexadecimal ASCII.
E-3 AQ Table .dat, .txt	This is the format of the E-3 TDP output files produced from an AORTA recording of the E-3 JTIDS Input/Output Buffers. It is a text file which contains a header for each AQ table followed by a number of records containing the buffer contents. Each record consists of 32-bit words as hexadecimal ASCII text. MANDRIL decodes these files by producing an intermediate file in TIMTOM text format, which is described below. The intermediate file can be saved.
E-3 SWATE	E-3 AQ Table data in SWATE format
E-3 TIMTOM Text *.tt	Data derived from E-3 TDP output (AORTA recorded AQ data tables) and processed MANDRIL. The TIMTOM format is a text format which can be read by a text editor, and contains the TIMs and TOMs as sets of comma-delimited 32-bit words in ASCII hexadecimal.
JSAF Replay Format *.rep	JTIDS Support Analysis Facility (F3 Ground based System) fixed length binary recorded data. Contains J-Series messages only.
Gateway E-3 *.edx	Gateway E-3 recordings recorded on the Gateway PC. Binary format containing E-3 TIMs and TOMs only and is decoded by MANDRIL exactly like the E-3 TIMTOM format.
Gateway Backbone *.gdx	The Gateway Backbone recordings recorded on the Gateway PC. Binary format containing data blocks passed on the Gateway backbone between host sites, including SIMPLE Link 16 blocks, DIS PDUs, etc.
Gateway MUX .mdx, .sdx, *.mce	Gateway recordings containing 1553 MUX bus TIMs and TOMs
Message Text *.cas	Contains J-series messages as hexadecimal ASCII text. Each message occupies one line of the file with spaces delimiting the message words. This format can be edited directly with a text editor. It can be used to create ‘one-off’ message files by typing the data in directly.
MLST3 *.dx	Northrop-Grumman MLST3 recorded data extraction format, recorded with the scenario generator facility of MULTOTS. (J-series and M-series messages only)
Link 11 *.l11	MIDAS Link 11 recordings
IJMS *.ijm	MIDAS IJMS recordings
MIDAS MUX (UKADGE) *.mux	MIDAS MUX recording from UKADGE terminal
MIDAS Initialisation *.int	Terminal Initialisation data as hexadecimal text for each Initialisation block.
LION *.csv	Link Interoperability Network recordings. Comma-separated variable text file containing message records. Each record contains a SIMPLE message block in Gateway Network Interface Frame format.
TJHS *.dx	TADIL J Host Simulator recordings containing NAVY/MCE TIMs/TOMs from 1553 bus
DTSS *.dx	Data Test Set Simulator 1553 bus recordings
LMS-16 *.dx	Single Link MULTOTS 1553 bus recordings
PASS 3200/1000 Archive *.arc	PASS 3200/1000 Archive files are created using the archive recording function of the SBS Technologies’ PASS 3200 or PASS 1000 1553 Bus Analyser. This is a binary format containing the status, command, data, and other words passing on the 1553 bus to which the bus analyser is attached
PBA-2000 *.prc	PBA-2000 Recording files are created using the recording function of the AIM PBA-2000 1553 Bus Analyser. This is a binary format containing the status, command, data, and other words passing on the 1553 bus to which the bus analyser is attached
DLP Recording *.txt	Recordings of DLP DTBs taken from the E-3 SDLP facility

MIDS LVT
Input Format And Default Extension	Description
Messages Only .smm, .l16	This format consists of binary fixed-length records. Files in this format can be made by using the ‘Write Message’ function of MANDRIL, with a file containing DTBs or another message file as input. Can contain Link 16, Link 11 or IJMS messages. They can also be obtained from other authorities (e.g. files in this format are produced by the UK’s MIDAS utilities – Link 16 only).
Recording Data Format *.rcd	For full Terminal DTB recordings, which are normally taken on the DAT Tape Recorder attached to the MIS workstation, the file stripped off the tape by the appropriate utility is in DAT Recording Data Format. This is a binary format containing buffers, packets and Data Blocks delimited by ‘CAFE’ markers.
DRP Quick-Look Hex Dump *.dmp	The Recording files can be processed by the DRP utility to produce a Quick-Look hex dump. This is a text file containing each word of each selected DTB as a hexadecimal string.
PASS 3200/1000 Archive *.arc	PASS 3200/1000 Archive files are created using the archive recording function of the SBS Technologies’ PASS 3200 or PASS 1000 1553 Bus Analyser. This is a binary format containing the status, command, data, and other words passing on the 1553 bus to which the bus analyser is attached
PBA-2000 *.prc	PBA-2000 Recording files are created using the recording function of the AIM PBA-2000 1553 Bus Analyser. This is a binary format containing the status, command, data, and other words passing on the 1553 bus to which the bus analyser is attached
SNIFFER *.cap	Capture files containing TCP/IP data packets recorded from an Ethernet bus. Libpcap format (binary).
TIGER/MLST3 Data Extraction *.dx	TIGER/MLST3 format files are the files created using the scenario generator of the TIGER or MULTOTS MLST3 in data extraction format.
Gateway Backbone *.gdx	The Gateway Backbone recordings recorded on the Gateway PC. Binary format containing data blocks passed on the Gateway backbone between host sites, including Gateway Link 16 blocks, DIS PDUs, etc.
Initialisation Data Load *.idl	Initialisation Data Load format is a binary file format containing a complete set of Initialisation Data to be loaded into a terminal. The file contains 128 blocks of 32 16-bit Initialisation Words as a binary stream. MANDRIL decodes these files by producing an intermediate file containing FIM03 DTBs in DRP Quick-Look format, described above. The user is given the option to save the intermediate file or not.
TIGER Initialisation *.mnf	Initialisation Data Load output by TIGER (binary format)
MIS Initialisation	Initialisation Data Load output by the MIS (text format)
Link 11 *.l11	MIDAS Link 11 recordings

URC-138
Input Format And Default Extension	Description
Messages Only .smm, .l16	This format consists of binary fixed-length records. Files in this format can be made by using the ‘Write Message’ function of MANDRIL, with a file containing DTBs or another message file as input. Can contain Link 16, Link 11 or IJMS messages. They can also be obtained from other authorities (e.g. files in this format are produced by the UK’s MIDAS utilities – Link 16 only).
STAFF *.sff	The STAFF format is the format of the data recorded on the Terrington or IDAS recorder attached to the 1553 host-to-terminal bus. It is a binary format consisting of variable-length records each of which contains the data for one TIM or TOM on the bus, together with the Command and Status words and header data for that TIM or TOM.
Support Port TSRD Recording *.dat	The TSRD format is the format of the data recorded to DAT tape or local hard drive by the Support Recorder. It is a binary format consisting of records of up to 1920 16-bit words. Each record contains a number of buffers delimited by ‘EEBA’ words, and each buffer contains a number of DTBs delimited by ‘CAFE’ markers.
MUX Recording *.mux	The MUX format is the format of the data recorded by the MUX Simulator or output from the DC Data Crunch Test Tool. It is a text format consisting of records of hexadecimal ASCII strings representing the contents of the (15,4) MUX DTBs.
Link 11 *.l11	MIDAS Link 11 recordings. Binary format.
SHISP *.j??	SHAR Initialisation Peripheral Files. These files are in binary format containing terminal Initialisation Data Blocks or Core Computer Data. MANDRIL will decode only the terminal Initialisation Data Files.
PBA-2000 *.prc	PBA-2000 Recording files are created using the recording function of the AIM PBA-2000 1553 Bus Analyser. This is a binary format containing the status, command, data, and other words passing on the 1553 bus to which the bus analyser is attached
PASS 3200/1000 Archive *.arc	PASS 3200/1000 Archive files are created using the archive recording function of the SBS Technologies’ PASS 3200 or PASS 1000 1553 Bus Analyser. This is a binary format containing the status, command, data, and other words passing on the 1553 bus to which the bus analyser is attached
MIDAS MUX (URC-138) *.mux	MIDAS MUX recording from URC-138 terminal
MIDAS Initialisation *.int	Terminal Initialisation data as hexadecimal text for each Initialisation block.