DLINK+
Users Manual
SLC Doc Number 13278
Spectra Lux Corporation
12335 134th Court NE
Redmond, WA 98052
USA
Tel: (425) 823-1801
Fax: (425) 823-4517
Email: info@spectralux.com
RESTRICTION ON USE, PUBLICATION, OR DISCLOSURE OF PROPRIETARY INFORMATION
This document contains information proprietary to Spectra Lux Corporation, or to a third party to which
Spectra Lux Corporation may have a legal obligation to protect such information from unauthorized
disclosure, use, or duplication. Any disclosure, use, or duplication of this document or of any of the
information contained herein for other than the specific purpose for which it was disclosed is expressly
prohibited, except as Spectra Lux Corporation may otherwise agree in writing.
Preparer:
Date:
Engineer:
Date:
Product Manager:
Date:
Quality Manager:
Date:
Document Number: 5630-5101-A00
Rev. B
11/13/03
CHANGE RECORD
Paragraph
Description Of Change
Initial release
Approval/
Date
Revision
1 Introduction
This document establishes one part of the baseline of configuration data for the Spectra Lux Corporation
product called Dlink+. This product was originally co-developed under the Pentar name “CMS-1000”. In
October of 2003, Pentar Systems Inc. and Spectra Lux Corporation dissolved their team, and agreed that
each company should proceed to develop the future of the product individually.
TSO approval was granted for the product prior to the decision to separate the programs. Spectra Lux
Corporation is therefore establishing a certification package based on the previous documentation.
Appendix A of this document contains Pentar document 5630-5101-A00, Rev A. This certification
baseline document allows us to establish an SLC numbering system for documentation of future
differences between the Dlink+ product and the CMS-1000 product.
Please refer to Spectra Lux Corporation document 13258, “Configuration Description Document” for a
table that describes correspondence of all Spectra Lux Corporation documents to Pentar Documents.
2 Appendix A
See the attached document for Pentar 5630-5101-A00, Rev A.
CMS-1000
Communication Management System
Users Manual
19820 North Creek Parkway, Suite 102
Bothell, WA 98011
USA
Tel: (425) 424-3370
Fax: (425) 424-3380
Email: techsupport@pentar.com
RESTRICTION ON USE, PUBLICATION, OR DISCLOSURE OF PROPRIETARY INFORMATION
This document contains information proprietary to PENTAR Avionics, or to a third party to which PENTAR
Avionics may have a legal obligation to protect such information from unauthorized disclosure, use, or
duplication. Any disclosure, use, or duplication of this document or of any of the information contained
herein for other than the specific purpose for which it was disclosed is expressly prohibited, except as
PENTAR Avionics may otherwise agree in writing.
Preparer:
Date:
Engineer:
Date:
Product Manager:
Date:
Quality Manager:
Date:
CMS-1000
Users Manual
CHANGE RECORD
Paragraph
Description Of Change
Approval/
Date
Revision
All
Initial release
L. Thorpe
1/18/02
Footers
Changed rev to A and date to 12/20/02
A. Pickrell
12/10/02
All
Corrected various minor spelling and grammar errors
2.1
Added sentence about options GPS connector
2.1 and
subsections
Changed Appendix A references to be a pin assignment table
instead of a reference to page 2 of a system assembly drawing
Appendix A
Changed Appendix A to contain pin assignment tables instead of
a system assembly drawing.
Footers
Changed rev to B, date to 11/13/03, and corrected footer
document numbers after title page and Change record
A. Pickrell
11/13/03
2.1
Added note that software is certified to DO178B level D.
5630-5101-A00
Rev. B
Users Manual
CONTENTS
SCOPE................................................................................................................................................... 1
1.1
1.2
System Overview............................................................................................................................ 1
Overview of Manual Contents ........................................................................................................ 1
INSTALLATION..................................................................................................................................... 2
2.1
General ........................................................................................................................................... 2
2.1.1
11 Pin Connector..................................................................................................................... 2
2.1.2
61 Pin Connector..................................................................................................................... 3
CONFIGURING THE CMS-1000........................................................................................................... 6
3.1
Downloading a configuration .......................................................................................................... 6
3.2
Editing a configuration .................................................................................................................... 6
3.3
Downloading a database ................................................................................................................ 6
3.3.1
Database Compiler.................................................................................................................. 7
3.4
The database.................................................................................................................................. 8
3.4.1
Menu Definitions...................................................................................................................... 8
Line select commands (L1 – L6, R1 – R6) .......................................................................................... 14
3.4.2
User Functions ...................................................................................................................... 15
3.4.3
ACARS Message Formats (SEND function) ......................................................................... 17
3.4.4
Receive ACARS Message (RECV function) ......................................................................... 18
3.4.5
User Variable Definitions....................................................................................................... 19
3.4.6
The Message Loops..............................................................................................................22
3.4.7
The User Function Keys Functions ....................................................................................... 24
OPERATING THE CMS-1000 ............................................................................................................. 27
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12
4.13
4.14
User Function Keys ...................................................................................................................... 27
Line Select Keys ........................................................................................................................... 28
The Arrow Keys ............................................................................................................................ 29
The CLEAR key ............................................................................................................................ 29
The ENTER key............................................................................................................................ 29
The DEL key. ................................................................................................................................ 29
The Return Key............................................................................................................................. 29
The +/- key.................................................................................................................................... 29
The Shift Key ................................................................................................................................ 29
Typing Keys. ............................................................................................................................. 29
System Reset............................................................................................................................ 30
MSG Lamp ................................................................................................................................ 30
FAIL Lamp................................................................................................................................. 30
TEMP Lamp .............................................................................................................................. 30
MAINTAINING THE CMS-1000 .......................................................................................................... 31
5.1
Equipment Limitations .................................................................................................................. 31
5.1.1
Liquid Spills ........................................................................................................................... 31
5.1.2
Temperature Extremes.......................................................................................................... 31
5.1.3
Power and Ground ................................................................................................................ 31
5.1.4
Signal Connections ............................................................................................................... 31
5.1.5
Shields................................................................................................................................... 31
5.2
Expected Modes of Failure........................................................................................................... 32
5.3
Repair and Troubleshooting Information ...................................................................................... 32
APPENDIX A: CMS-1000 REAR CONNECTOR PIN ASSIGNMENTS ................................................ A-1
5630-5101-A00
Rev. B
ii
Users Manual
3 SCOPE
This Manual provides a user with information about the installation and use of the Pentar, CMS-1000
Communications System Unit.
3.1 System Overview
The PENTAR CMS-1000 provides ACARS message capability by integrating the functionality of three
ARINC devices into one, cockpit mounted Line Replaceable Unit (LRU). The three ARINC devices are:
1.
ARINC 724B Communications Management Unit (CMU)
2.
ARINC 750 VHF Data Link (VDL) Radio
3.
ARINC 739 Multi-purpose Control Display Unit (MCDU)
The CMS-1000 sends and receives free text messages and ACARS messages to support end-to-end
Aircraft Operational Control (AOC) communications over the ACARS data link.
The CMS-1000 works in conjunction with a device called the “Personality Module”. The personality
module is a serial EEPROM that houses the unit’s database. When the unit is powered ON, the unit
reads the database in the personality module into FLASH memory internal to the CMS-1000. The
database determines the structure of the unit’s menus and the default, ACARS message set. The
personality module is cable wrapped to one of the unit’s mating connector’s cable. The personality
module has a pigtail of four wires. These wires are inserted into the associated mating connector per
section 2 below.
Any CMS-1000 that is connected to a given personality module will operate with the same menu and
message set.
3.2 Overview of Manual Contents
The information that follows provides the user with information about how to:
1.
Install the CMS-1000 (Section 2)
2.
Configure the CMS-1000 (Section 3)
3.
Operate the CMS-1000 (Section 4)
4.
Maintain the CMS-1000 (Section 5)
This document further contains information about CMS-1000 equipment limitations (section 6)
5630-5101-A00
Rev. B
Users Manual
4 Installation
4.1 General
The CMS-1000 is designed to fit into a standard, 5.75” by 4.5” Dzus rail mounting slot. There are two
military, circular connectors (one 11 pin connector and one 61 pin connector), and one RF TNC connector
mounted to the rear of the unit. A second RF TNC connector may also be mounted to the rear of the unit
for an optional GPS receiver antenna connection. These connectors provide all input/output connections
to the CMS-1000.
Note: The CMS-1000 software is certified according to RTCA DO-178B level D.
4.1.1 11 Pin Connector
The 11 pin connector on the rear of the CMS-1000 mates with a MS3476L18-11S connector. This
connector uses #16 sized socket crimp contacts (M39029/5-116). Refer to appendix A for the wiring
table.
The 11 pin connector has two purposes :
1.
Provide power and ground to the unit.
Non-essential, 28 Vdc aircraft power is routed to the connector. This power is provided using one or two
16 AWG wires. The wires are terminated with the MS39029/5-116 contacts. The contacts are inserted
into the connector’s “A” and/or “L” positions. A 7.5 amp circuit breaker should be used for protection.
The 28 Vdc return (ground) is provided using one 16 AWG wire. The wire is terminated with the
MS39029/5-116 contact. The contact is inserted into the connector’s “B” position.
The aircraft’s 5 Vdc dimmer bus is routed to the connector. This provides a reference for the unit’s
keyboard and annunciator dimming circuitry. Keyboard and annunciator lighting power is provided by the
unit’s internal power supply (derived from the 28 Vdc input). All front panel lighting is accomplished by
using LEDs. The CMS-1000’s internal circuitry monitors the 5 Vdc dimming bus, and adjusts the LED
power so that the front panel lighting dims relative to the dimming bus. The 5 Vdc dimmer bus connection
is provided by using one 16 AWG wire, terminated with a M39029/5-116 contact, inserted into the
connector’s “G” location. The 5 Vdc dimmer bus common connection is provided by using one 16 AWG
wire, terminated with a MS39029/5-116 contact, inserted into the connector’s “H” position.
2.
Provide the personality module connections.
The four personality module wires are terminated with #16 sized socket crimp contacts (M39029/5-116).
The four personality module wires are labeled: “CLK”, “DATA”, “3.3V” and “GND”. The “CLK contact is
inserted into the connector’s “C” position. The “DATA” contact is inserted into the connector’s “D”
position. The “3.3V” contact is inserted into either the “E” or “F” position (either will work). The “GND”
contact is inserted into the “J” position.
5630-5101-A00
Rev. B
Users Manual
4.1.2 61 Pin Connector
The 61 pin connector on the rear of the CMS-1000 mates with a MS3476L24-61S connector. This
connector uses #20 sized socket crimp contacts (M39029/5-115). Refer to appendix A for the wiring
table.
The 61 pin connector provides the unit’s signal interfaces. These interfaces can be grouped into the
following groups:
4.1.2.1
1.
ARINC429 Bus Connections
2.
IEEE RS232 Bus Connections
3.
IEEE RS422 Bus Connection
4.
Ethernet Connection
5.
Discrete Connections
6.
Ground Connections
7.
Spares
ARINC429 Bus Connections
The unit supports up to six ARINC429 input channels and up to two ARINC429 transmit channels. It is
expected that the transmit channels will support ARINC740/744 printers and possible interface with an
ARINC619 device. The transmit channels should not be used to provide data from the CMS-1000 to
aircraft data buses used for flight control, navigation, or any bus that has a criticality of greater than level
D.
To provide an ARINC429 input to the unit’s ARINC429 channel 2, connect a Transmit negative (T-)
connection from an ARINC429 bus to the Receive negative (-) connection in the MS3476L24-61S
connector. The connection is provided by crimping a M39029/5-115 contact to the aircrafts ARINC429 Tsignal wire and inserting the contact in position “FF” of the connector. Also connect the aircraft’s Transmit
positive (T+) to the unit’s Receive positive (R+) in the same manner but insert the contact into connector
position ”EE”. Using the same procedure, connect the aircraft’s Receive positive and Receive negative
wires to the unit’s Transmit positive and Transmit negative by using the connector positions “P” and “R”
respectively. The aircraft’s two transmit wires should be a #20 shielded twisted pair (STP), as should be
the two receive wires. The shields of each of the STPs should be connected to the unit’s ground
reference. This can be accomplished by terminating the shields to a #20 wire, crimp a M39029/5-115
contact to the wire and inserting the contact into one of the unit’s 11 ground positions. The shield
grounding can also be accomplished by terminating the shields to the mating connector’s shell. It is
important to make the length of the terminations as short as possible.
The above procedure can be used to connect any of the ARINC429 channels. Use the table in Appendix
A as the guide for placement of the signals into the connector.
4.1.2.2
IEEE RS232 Bus Connections
The unit supports up to two RS232 channels. It is expected that the channels will support printers or
other non-essential peripherals. The channels should not be used to provide data from the CMS-1000 to
aircraft data buses used for flight control, navigation, or any bus that has a criticality of greater than level
D.
To provide a RS232 input to the unit’s RS232 channel 1, connect a Transmit connection from an RS232
bus to the Receive connection in the MS3476L24-61S connector. The connection is provided by crimping
a M39029/5-115 contact to the aircrafts RS232 Transmit signal wire and inserting the contact in position
“c” of the connector. Also connect the aircraft’s RS232 Receive channel to the unit’s Transmit channel in
the same manner but insert the contact into connector position ”b”. The aircraft’s RS232 wires should be
5630-5101-A00
Rev. B
Users Manual
a #20 shielded twisted pair (STP). The shield of the STPs should be connected to the unit’s ground
reference. This can be accomplished by terminating the shield to a #20 wire, crimp a M39029/5-115
contact to the wire and inserting the contact into one of the unit’s 11 ground positions. The shield
grounding can also be accomplished by terminating the shield to the mating connector’s shell. It is
important to make the length of the terminations as short as possible.
The above procedure can be used to connect the other RS232 channel. Use the table in Appendix A as
the guide for placement of the signals into the connector.
4.1.2.3
IEEE RS422 Bus Connections
The unit supports one RS422 channel. It is expected that the channel will support printers or other nonessential peripherals. The channel should not be used to provide data from the CMS-1000 to aircraft
data buses used for flight control, navigation, or any bus that has a criticality of greater than level D.
To provide a RS422 input to the unit’s RS422 channel, connect a Transmit negative (T-) connection from
an aircraft RS422 bus to the Receive negative (-) connection in the MS3476L24-61S connector. The
connection is provided by crimping a M39029/5-115 contact to the aircraft’s RS422 T- signal wire and
inserting the contact in position “w” of the connector. Also connect the aircraft’s Transmit positive (T+) to
the unit’s Receive positive (R+) in the same manner but insert the contact into connector position ”v”.
Using the same procedure, connect the aircraft’s Receive positive and Receive negative wires to the
unit’s Transmit positive and Transmit negative by using the connector positions “t” and “u” respectively.
The aircraft’s two transmit wires should be a #20 shielded twisted pair (STP), as should be the two
receive wires. The shields of each of the STPs should be connected to the unit’s ground reference. This
can be accomplished by terminating the shields to a #20 wire, crimp a M39029/5-115 contact to the wire
and inserting the contact into one of the unit’s 11 ground positions. The shield grounding can also be
accomplished by terminating the shields to the mating connector’s shell. It is important to make the
length of the terminations as short as possible.
4.1.2.4
Ethernet Connection
The unit supports one Ethernet connection. This connection is used during manufacturing to test and
configure the unit. If this connection is routed to a connector on the aircraft, a laptop loader tool can be
connected and the unit can be tested and configured in place. If not, the unit must be un-installed to
configure and test via the Ethernet port. (Note: The CMS-1000 can be configured using the maintenance
menu capabilities, but, a password must be entered to allow this to happen).
The Ethernet connection could also be routed to a non-essential peripheral (such as a cabin server) and
the CMS-1000 can be configured to supply such a peripheral information as configured via the Ethernet
port.
To provide an Ethernet input to the unit’s Ethernet channel, connect a Transmit negative (T-) connection
from an aircraft Ethernet bus to the Receive negative (-) connection in the MS3476L24-61S connector.
The connection is provided by crimping a M39029/5-115 contact to the aircraft’s T- signal wire and
inserting the contact in position “E” of the connector. Also connect the aircraft’s Transmit positive (T+) to
the unit’s Receive positive (R+) in the same manner but insert the contact into connector position ”D”.
Using the same procedure, connect the aircraft’s Receive positive and Receive negative wires to the
unit’s Transmit positive and Transmit negative by using the connector positions “B” and “C” respectively.
The aircraft’s two transmit wires should be a #20 shielded twisted pair (STP), as should be the two
receive wires. The shields of each of the STPs should be connected to the unit’s ground reference. This
can be accomplished by terminating the shields to a #20 wire, crimp a M39029/5-115 contact to the wire
and inserting the contact into one of the unit’s 11 ground positions. The shield grounding can also be
accomplished by terminating the shields to the mating connector’s shell. It is important to make the
length of the terminations as short as possible.
5630-5101-A00
Rev. B
Users Manual
4.1.2.5
Discrete Connections
The CMS-1000 provides for up to 12 discrete connections. Four are ground active inputs, four are
ground active outputs (sinking up to 300 mamps), and four are configurable to be either active high
outputs (sourcing up to 200 mamps each, but the total sourced amperage needs to be 400 mamps or
less) or as ground active inputs. The configurable inputs are configured at the PCA level as directed by
the customer (hence, they are not configurable in the field).
A ground active input discrete is for providing the CMS-1000 with aircraft status (for example, ON-OFFOUT-IN, or OOOI). An aircraft input discrete is connected to a CMS-1000 input discrete via a #20 wire,
crimped with a M39029/5-115 contact and inserted into the appropriate connector position per the table in
appendix A. The CMS-1000 input discretes are internally pulled up to 28 VDC through a 15 kohm
resistor. When the signal is grounded, the CMS-1000 detects that the discrete is ACTIVE. Any input
discrete can be associated with the issuance of a given message and/or an advisory in the CMS-1000
display as determined by the customer. The association is accomplished via configuring the personality
module’s database.
A ground active output can be used to drive an annunciator, chime, or similar device (not to exceed 300
mamps). The CMS-1000 ground active output discrete is connected to the aircraft discrete via a #20
wire, crimped with a M39029/5-115 contact and inserted into the appropriate connector position per the
table in appendix A. The CMS-1000 ground active output is normally a floating, open circuit. The CMS1000 changes the state of the output discrete by internally grounding the discrete through a low side
driver circuit that can sink up to 300 mamps. Any output discrete can be associated with the issuance of
a given event in the CMS-1000 as determined by the customer. The association is accomplished via
configuring the personality module’s database.
An active high active output can be used to drive an annunciator, chime, or similar device (not to exceed
200 mamps, with the total of all sourced current less than or equal to 400 mamps). The CMS-1000
active high output discrete is connected to the aircraft discrete via a #20 wire, crimped with a M39029/5115 contact and inserted into the appropriate connector position per the table in appendix A. The CMS1000 active high output is normally a floating, open circuit. The CMS-1000 changes the state of the
output discrete by internally connecting 28 Vdc to the discrete via a high side driver circuit. Any output
discrete can be associated with the issuance of a given event in the CMS-1000 as determined by the
customer. The association is accomplished via configuring the personality module’s database.
4.1.2.6
Ground Connections
The CMS-1000 internally connects all ground connections that are available at the unit’s input/output
connector. These connections can be used for grounding shields and/or chassis ground connections.
These connections should not be attached to sources of voltage or significant noise. Use #20 wire with
the MS39029/5-115 contacts.
4.1.2.7
Spares
There are several pins that are categorized SPARE. These pins are not used for any aircraft function.
They should either be left floating, or grounded.
5630-5101-A00
Rev. B
Users Manual
5 Configuring the CMS-1000
The CMS1000 contains a default configuration and database that provides basic functionality when the
personality module is either missing or invalid. The configuration can be modified by downloading a
configuration using the laptop loader or manually using the configuration editor menus.
5.1 Downloading a configuration
The configuration file is a text file that can be modified by any text editor (Windows notepad is a good
choice). It is in the form of an initialization file (.INI) with comments describing each field. The initial
section of the file has the header “[Aircraft]”. CAUTION: This is the only section the user should modify as
changing fields in other sections may prevent the CMS1000 from operating correctly.
To download the configuration to the CMS1000 you must connect the laptop loader to the CMS1000
Ethernet port. Start CMSTest and wait for the title bar to indicate that “CMSTest is connected to CMS”.
Press the “Write Config” button and select the desired configuration file. The file will be downloaded and
written to the personality module. The CMS1000 will automatically reboot.
5.2 Editing a configuration
On the CMS1000 display select the CONFIG menu. Note that the path to get to the CONFIG menu may
change depending on the user database. In the CONFIG menu select “USER EDIT” to edit the user
fields or “SYS EDIT” to edit the system fields (editing the system fields is NOT recommended for the
user). After modifying any desired fields press the return key or RETURN LSK. The confirmation menu is
displayed. The selection field defaults to YES. Pressing the LSK cycles the selection to NO, to CANCEL,
and back to YES. Pressing the return key or RETURN LSK accepts the selection. If YES is selected the
password menu is displayed next. Type the appropriate password (default is “USER00” for the user
config and “PENTAR” for the system config). Press ENTER to enter the password. The configuration will
be written to the personality module and the CMS1000 will automatically reboot.
5.3 Downloading a database
The database file is a pair of text files that can be modified by any text editor (Windows notepad is a good
choice). The database is a simple, specialized, language for specifying MENUs, variables, ACARS
message contents, etc. The syntax for the database language is in the sections following. It is divided
into two files that we call the CORE and USER databases. The core database is always named
CMS1000_core_db.txt and contains all the CMS system critical definitions of variables, functions, and
ACARS messages and can only be modified by Pentar. It is protected by a special check code that
allows any modifications to be detected by the compiler. If the core database is modified the compiler will
display an error message and refuse to compile the database. The user database is completely defined
by the user. Several of the core functions can be replaced in the user database to customize the
functionality of the CMS as noted in the syntax sections below.
After modifying a database it must be compiled with CMSComp then downloaded with CMSTest on the
laptop loader.
5630-5101-A00
Rev. B
Users Manual
5.3.1 Database Compiler
To compile the database run CMSComp.exe, press the “Select File” button and select the desired user
database file, then press the “Start Compile” button. The compiler will automatically verify integrity of the
core database, compile it then compile the user database. The status and any errors will be displayed in
the “Compiler Status” window.
The resulting compiled database will always be saved in
“C:\CMS1000\CMS1000.DB”.
5630-5101-A00
Rev. B
Users Manual
To download the database to the CMS1000 you must connect the laptop loader to the CMS1000 Ethernet
port. Start CMSTest and wait for the title bar to indicate that “CMSTest is connected to CMS”. Press the
“Write DB” and the database will be downloaded and written to the personality module. The CMS1000
will automatically reboot.
5.4 The database
The database contains definitions for menus, functions that can be invoked from menus, ACARS
message formats, user variable definitions, and the message loops.
5.4.1 Menu Definitions
The menu definitions consist of:
•
The text to place on a screen, its format, and where it is placed. Since the CMS DU emulates a
standard 14 line ARINC 739 display all 12 text lines are used in the database definition. The DU itself
divides it up into two pages (see below).
•
The function to perform when a line select key (LSK) is pressed while a particular menu is being
displayed.
5630-5101-A00
Rev. B
Users Manual
Example:
ACARS MAIN MENU
L1
- - R1
MSGS RCVD> - R2
REPORTS> - R3
REQUESTS> - R4
MISC MENU> - R5
ADVISORY
XXXXXX - R6
T0
T1
T2
T3
T4
T5
T6
T7
T8
T9
T10
T11
T12
SCRATCH PAD
Figure 4.2-1 Example ACARS Main Menu
ACARS MAIN MENU
L1
- - R1
MSGS RCVD> - R2
REPORTS> - R3
A/B
T0
T1
T2
T3
T4
T5
T6
SCRATCH PAD
NEXT
Figure 4.2-2 Example ACARS Split Main Menu (A screen)
ACARS MAIN MENU
L4
- - R4
MISC MENU> - R5
ADVISORY
XXXXXX - R6
NEXT
T0
T7
T8
T9
T10
T11
T12
SCRATCH PAD
Figure 4.2-3 Example ACARS Split Main Menu (B screen)
5630-5101-A00
Rev. B
Users Manual
This menu could be defined as follows.
MENU= defines the name of the menu function and defaults to the title. The default title defined in the
MENU= command can be overridden using the T0 (T zero) command (see below). A menu name (or
function, send, or variable name) cannot contain spaces, tabs, or commas.
L1 through 6 and R1 through 6 define the functions that the left and right line select keys (LSK) perform
when pressed. In this sample each LSK (except R6) calls a different menu. The name of the menu is
used for the display text unless otherwise specified (see UTC_MENU). The appropriate < or > is
automatically added to the menu name to create the display text. If the LSK calls a function or sends a
message the * is added to the display text. R6 is connected to the ADVISORY variable.
The T11 line creates the title for the ADVISORY variable. Traditionally titles other than the main title are
in the small font hence the lower case “s” in the first character position.
MENU=MAIN_MENU
T0 “ACARS MAIN MENU”
T11 “s
ADVISORY”
L1 MENU PREFLIGHT
L2 MENU ENROUTE
L3 MENU POSTFLIGHT
L4 MENU UTC_MENU “UTC TIME”
L5 MENU MAINT MENU
R1 MENU FLT_LOG “FLT LOG”
R2 MENU MSGS_RCVD “MSGS RCVD”
R3 MENU REPORTS
R4 MENU REQUESTS
R5 MENU MISC_MENU “MISC MENU”
R6 VAR ADVISORY
END MENU
5630-5101-A00
Rev. B
10
Users Manual
Second Example:
INIT DATA
FLT NO
NNNN
DEPT
AAAA
ETD
HHMM
GW
NNNNN
DATE
NN
DEST
AAAA
ETE
HHMM
MSG BUFFER
[RECEIVE]
L1
- R1
L2
L3
L4
L5
AUTO_INIT* - R5
L6
- ). AUTO_INIT contains statements to set the variables used in the display to
the current value of other user variables (presumably variables extracted from 429 or discrete inputs –
see User Variable Definitions) and a constant then redisplays the INIT_DATA menu. (Note: when the
same menu is redisplayed or reselected the data on the menu is updated but the menu is not added
again to the call stack).
The SELECT command displays the current selection of a variable from its selection list (see User
Variable Definitions). It is identified with the “[“ and “]” around the variable contents. Each press of its
LSK selects the next item in the selection list in a circular fashion.
INIT_DATA has 4 pages. The NEXT and PREV commands link the pages together. They are accessed
using the NEXT/PREV LSK key. INIT_DATA_2 shows an example of a text line including a variable to
display and specifying the underline font for the variable contents.
Another way to create multiple page menus is with the PAGES and ITEMS commands. See the example
of the MESSAGE menu below that displays the current ACARS message buffer. The PAGES are set to
zero to tell the CMS to figure out how many pages this message will require based on the number of
ITEMS per page and use that number as the max on the display. The @MSG special function knows
which page it is on to display the appropriate data. MESSAGE also shows an example of the DELETE
command to delete the current ACARS message from the buffer and the PRINT command to print the
contents of the current message when a printer is attached to the CMS.
5630-5101-A00
Rev. B
11
Users Manual
MENU=INIT_DATA
NEXT INIT_DATA_2
PREV INIT_DATA_4
T0 “INIT DATA”
T1 “sFLT NO
DATE”
T3 “sDEPT
DEST”
T5 “sETD
ETE”
T7 “sGW
MSG BUFFER”
L1 VAR FLT_NUMBER
L2 VAR DEP_AIRPORT
L3 VAR EST_TIME_DEP
L4 VAR GROSS_WEIGHT
L6 RETURN
R1 VAR DATE
R2 VAR DEST_AIRPORT
R3 VAR EST_TIME_EXIT
R4 SELECT MSG_BUFFER
R5 FUNC AUTO_INIT
R6 FUNC TOGGLE_FLT_NUM “TOGGLE FN”
END MENU
FUNC=AUTO_INIT
SET FLT_NUMBER
SET DEP_AIRPORT
SET EST_TIME_DEP
SET GROSS_WEIGHT
SET DATE
SET DEST_AIRPORT
SET EST_TIME_EXIT
MENU INIT_DATA
RETURN
END FUNC
FROM
FROM
FROM
FROM
FLT_NO
DEPARTURE_AP
ETD
12345
FROM DAY
FROM DESTINATION_AP
FROM ETE
MENU=INIT_DATA_2
NEXT INIT_DATA_3
PREV INIT_DATA
T0 “INIT DATA 2”
T2 “ACARS BUFFER=u”, MSG_BUFFER,”u!”
L3 RETURN
END MENU
MENU=INIT_DATA_3
NEXT INIT_DATA_4
PREV INIT_DATA_2
T0 “INIT DATA 3”
L3 RETURN
END MENU
MENU=INIT_DATA_4
NEXT INIT_DATA
PREV INIT_DATA_3
T0 “INIT DATA 4”
L3 RETURN
END MENU
5630-5101-A00
Rev. B
12
Users Manual
MENU=MESSAGE
PAGES 0
ITEMS 9
T0 "s",@MSG(T,0)
T1 @MSG(L,1)
T2 @MSG(L,2)
T3 @MSG(L,3)
T4 @MSG(L,4)
T5 @MSG(L,5)
T6 @MSG(L,6)
T7 @MSG(L,7)
T8 @MSG(L,8)
T9 @MSG(L,9)
L5 DELETE
R5 PRINT
L6 RETURN
END MENU
A note about updating personality module data and the PASSWORD command: When a password is
attached to a menu it is only used in conjunction to updating the personality module. When one or more
variables are modified whose source is the personality module the variables are held in temporary
storage. When returning from the menu that they were modified in the CMS verifies that it is on the
ground (personality module changes are not allowed in air). Then a menu will be displayed confirming
changes to the personality module. The user selects YES or NO and presses RETURN. Finally a
password menu is displayed. The user enters the password then presses the ENTER key (this is
intentionally changed from the RETURN key used to exit other menus). The user is allowed three
attempts to enter a correct password. If the aircraft is in air or the user answers NO to the confirmation or
cannot enter a correct password in three attempts the personality module changes will be discarded and
the original values will be used. Otherwise, the data will be written to the personality module and the
CMS will restart.
5.4.1.1
Formal Syntax
