Meteorcomm® and ITCNet® are registered trademarks of Meteorcomm LLC and may not be used without
express written permission of Meteorcomm LLC. By downloading, using, or referring to this document or any of
the information contained herein, you acknowledge and agree:
Ownership
This document and the information contained herein are the sole and exclusive property of Meteorcomm LLC
(“MCC”). Except for a limited review right, you obtain no rights in or to the document, its contents, or any
related intellectual property. MCC may, upon written notice, terminate your internal review of this document
and, upon such notice, you will return the original of this document to MCC together with the originals and all
copies of all documents in your possession or under your control that refer or relate to it.
Limited Use and Non-Disclosure
This document contains information that is considered proprietary to MCC. It is protected by copyright, trade
secret, and other applicable laws. This document may not be transmitted, distributed, duplicated, or used,
including, without limitation, the information contained herein, in whole or in part, except as agreed under
separate written agreement with MCC.
Disclaimer of Warranty
This document and all information contained herein or otherwise provided by MCC, and all intellectual property
rights therein, are provided on an “as is” basis. MCC makes no warranties of any kind with respect thereto and
expressly disclaims all warranties of any kind, whether express, implied, or statutory, including but not limited
to warranties of merchantability, fitness for a particular purpose, title, non-infringement, accuracy,
completeness, interference with quiet enjoyment, system integration, or warranties arising from course of
dealing and usage of trade practice.
Assumption of Risk
You are responsible for conducting your own independent assessment of the information contained in this
document (including without limitation schematic symbols, footprints, and layer definitions) and for confirming
its accuracy. You may not rely on the information contained herein, and you agree to validate all such
information by using your own technical experts. Accordingly, you agree to assume sole responsibility for your
review, use of, or reliance on the information contained in this document. MCC assumes no responsibility for,
and you unconditionally and irrevocably release and discharge MCC and its affiliates and their respective
officers, directors, and employees (“MCC Parties”) from, any and all loss, claim, damage, or other liability
associated with or arising from your use of any of the information contained in this document.
Limitation of Liability
In no event shall MCC or the MCC parties be liable for any indirect, incidental, exemplary, special, punitive or
treble, or consequential damages or losses, whether such liability is based on contract, warranty, tort
(including negligence), product liability, or otherwise, regardless as to whether they have notice as to any such
claims.
Hazardous Uses
None of the information contained in this document may be used in connection with the design, manufacture,
or use of any equipment or software intended for use in any fail-safe applications; or any other application
where a failure may result in loss of human life, or personal injury, property damage or have a financial impact;
or in connection with any nuclear facility or activity; or shipment or handling of any hazardous, ultra-
hazardous, or similar materials (“Hazardous Uses”). MCC disclaims all liability of every kind for any Hazardous
Uses, and you release MCC and the MCC Parties from, and shall indemnify MCC and the MCC Parties against,
any such liability, including, but not limited to, any such liability arising from MCC’s negligence.Document
This manual outlines the operation of the MCC-545C Packet Data Radio
through software revision 6.87.
The MCC-545C Packet Data Radio is used in MCC’s FleetTrak™ network.
This chapter briefly describes this network application; refer also to
Appendix F for a complete discussion of MCC Network Interoperability.
In addition to information and instructions for line of sight applications,
this manual also contains information regarding meteor burst master
and remote station installation and refers to antennas used in those
installations that apply to use of the MCC-545B or other MCC models.
Please refer to the tables in the MCC-545C RF Energy Exposure Guide
for lists of antenna types suitable for use in vertically-polarized line
of sight applications of the MCC-545C.
Each MCC-545C features rugged construction and is packaged in a
stainless steel, weather-resistant enclosure that measures 10.6"L x
4.0"W x 2.42"H and weighs 3.5 pounds, as shown in Figure 1.1.
The MCC-545C radio is frequency synthesized and uses a GMSK
modulation scheme with selectable data rates, as shown below.
Model No. Modulation Data rate
MCC-545C
The MCC-545C has an embedded 32-bit controller for managing all the
network functions associated with a packet switched data network and
for interfacing to a variety of peripheral devices. In addition, it has a
built-in test capability that automatically monitors the operating
integrity of the unit at all times. This feature also eliminates the need
for any special test equipment during the installation phase. A laptop,
palmtop, or equivalent is required to initialize and operate the MCC545C packet radio.
The FleetTrak™ network is used for applications that require the
position of mobile resources to be reported in real-time and at varying
update rates. The FleetTrak network is shown in Figure 1.2.
Figure 2: FleetTrak™ network diagram
ELOS RF NETWORK
M
MB
M
M
R
MMM
M
R
RB
DATA
B
NETWORK
B
BASE STATION
R
REPEATER STATION
M
REMOTE STATION (FIXED OR MOBILE)
DATA CENTER
OR
HOST
CLIENT’S
CLIENT’S
OFFICES
OFFICES
OTHER
CLIENTS
The FleetTrak™ network is comprised of Base Stations, Repeaters, and
Remote Stations. The MCC-545C can be programmed to operate as any
of these three distinct station types. The FleetTrak™ network is used for
position reporting in mobile applications (AVL), fixed site data
collection (SCADA), and messaging.
The FleetTrak™ network operates line-of-sight using groundwave and
uses an LOS protocol for channel access. In an LOS network, there is
always an RF connection path between adjacent stations, and stations
transmit data whenever they have something to send. These
transmissions use CSMA (carrier sense multiple access) to gain channel
access and to prevent RF signal collisions.
The range of communication by groundwave is primarily determined by
diffraction around the curvature of the earth, atmospheric diffraction,
and tropospheric propagation. These ranges are successfully extended
by MCC from 50-100 miles through the use of robust protocols, sensitive
receivers, and short packetized messages.
There are 5 major sections in this manual, plus a number of appendices:
Section 2.0 RF Safety and Regulatory Information
This section provides important information regarding antenna
installations and means to safely limit exposure to RF radiation.
Section 3.0 Description
This section provides both a physical description and a functional
description of each module in an MCC-545C. The detailed technical
specifications are provided for each printed circuit board assembly
(PCA), as well as the organization of the unit’s computer memory.
Section 4.0 Installation
This section covers site selection and general installation guidelines,
including instructions for cabling, antenna and power source
connections. Power up procedures, initialization and functional test
procedures are described that should be performed prior to placing the
MCC-545C on-line within the network.
Section 5.0 Operation
This section describes all the operating procedures for the MCC-545C.
All commands and operational parameters are described for data
collection, supervisory control, messaging, and interpreting system
operational statistics. It also contains a list of all MCC-545C commands.
The MCC-545C contains three printed circuit board assemblies as shown
in Figure 2.2.
3.2.1 Microprocessor
The low-power 32-bit microprocessor controller performs the radio
control, link, and network protocol functions. This assembly also
contains a digital signal processor (DSP) and digital-to-analog converter
(DAC) for generating the in-phase (I) and quadrature-phase (Q) base
band signals for generating the GMSK RF signal.
3.2.2 Transceiver
The selectable-rate transceiver uses a vector phase modulator (+13DBm
output) and frequency synthesizers to produce 9.6 kbps.
3.2.3 Power Amplifier
Note: The nominal RF power amplifier rating of the MCC-545C is 100W
or 50 dBm. The output power is calibrated at the factory at the
expected operating frequency. Measured power values may vary up to 1
dB from rated power, up to 51 dBm or 125W over the frequency range
of the radio.
The multi-stage power amplifier includes a 2 watt, 2-stage preamplifier;
a 100 watt, solid-state, 2-stage power amplifier; and a power switch.
A 12-channel GPS receiver may be mounted on the processor board as
an optional subassembly.
All components are soldered in place using surface mount technology.
As an option, the boards can be conformal coated with an acrylic
encapsulate that contains a tropicalizing, anti-fungal agent to provide
additional protection against moisture and contamination.
The microprocessor is a Motorola-based, embedded processor located
on a single PCB that contains:
• 512K x 16 of non-volatile flash memory for program storage
• 512K x 16 of non-volatile flash memory for parameter storage
• 1024K x 8 of static RAM for data storage (optionally 2048K x 8)
• 3 External RS-232 I/O ports
• Internal TTL GPS port
• Transmitter communication port
• Receiver communication port
• 10-bit 11 channel A/D converter (6 channels are available for
external sensors)
• Real-time clock
• Power fail detection circuitry
• Digital Signal Processor with D/A converters
• 6 Optically isolated digital inputs
• 2 Form C Relay Outputs with a current rating of 2 amps
All I/O ports are RS-232 compatible and can be programmed to adapt to
various customer protocols. The DATA port contains full flow control
hardware lines.
The A/D converter measures TX forward and reverse power, battery voltage, antenna noise voltage,
transmitter board temperature, and 6 channels of 0-5V external sensor inputs. In –03 or later versions the
internal nickel metal hydride battery (3.6V) can also be read.
An internal lithium ion battery is used to maintain the internal real time
clock and battery backed RAM. This battery operates the clock in a
power down state for a period of approximately 6 months. This battery
should be removed if the unit is stored for extended periods of time.
In -03 or later versions of the units, the lithium ion battery has been
replaced with a rechargeable nickel metal hydride battery. This battery
is located at the rear of the unit with Velcro. (You have to open the
rear lid to get access to it.) A short jumper is used to connect the
battery to the processor board. This jumper should be removed if the
unit is stored for long periods of time (longer than 2 months). The
battery must be connected before the unit will start operating.
3.4 Transceiver
The transceiver assembly contains a receiver, transmit and receive
frequency synthesizers, and a modulator. The MCC-545C receiver and
modulator support 9.6 kbps Gaussian Minimum Shift Keying (GMSK).
GMSK Receiver
• Input bandpass filter (37-50 MHz )
• RF amplifier (17 dB)
• Low pass image filter (Fc=50 MHz)
• Mixer
• IF amplifiers and filters (10.7 MHz)
• Noise blanker
• Mixer, 2nd IF filter and amplifier (100 kHz), and RSSI circuit
• Phase lock loop frequency discriminator
• GMSK bit detector and clock generator
Synthesizer (1st and 2nd local oscillator and transmit oscillator)
•Rx 1st local oscillator phase lock loop (47.7-60.7 MHz output, 10
kHz steps limited to 53.7 – 56.7 MHz in FCC ID: BIB54505003-01)
• Rx 2nd local oscillator phase lock loop (10.6 MHz)
• PIC Microcontroller
GMSK Modulator
• DSP digital baseband GMSK generator
• I and Q DACs
• I/Q Vector Phase Modulator (GMSK)
• Pre amplifier (+13 dBm output)
All components are mounted on an 8.5" by 3.5" two-sided printed circuit
board. All components are surface mounted.
3.5 Pre-Amp, Final Power Amp, and Power Control
This board contains two low-level amplifiers that amplify the +13 dBm
(10 mW) signal from the modulator to the 2 watts required by the final
power amplifier. A special power switch is used to control the rise and
fall times of the RF power output. A duty cycle limiter circuit limits the
duty cycle of the power amplifier to 16%. A temperature sensor is also
located on this board for monitoring the internal temperature of the
MCC-545C. This temperature reading may be transmitted to the Host for
maintenance purposes.
The 100 watt power amplifier is mounted inside an aluminum enclosure
to provide RF shielding between the low level phase lock loop
synthesizers and the high power output. This board contains a T/R
switch for half-duplex operation, a harmonic low pass filter, and a dual
directional coupler for power level control. The coupler measures
forward and reverse power. If the VSWR exceeds 3.0:1 the power
amplifier automatically shuts down. The power amplifier’s parameters
are also transmitted to the Host for maintenance purposes.
A switching regulator power supply provides 5.7 volts for the processor
and transceiver boards.
512K x 16 non-volatile Flash memory
1024K x 8 static RAM (optional 2048K x
8)
545C Operations Manual
System Reset, Momentary
Switches: SW1
3.7 Memory Organization
The MCC-545C has three types of memory:
3.7.1 Program Memory (PM)
The Program memory is non-volatile Flash (512K x 16). It contains the
MBNET200 image software, bootstrap, configuration, and application
software. These programs are installed at the MCC facilities at the time
of shipment. The information stored in the Program memory is referred
to as “factory defaults”.
3.7.2 Parameter Memory (CPM)
The Parameter memory is non-volatile Flash (512K x 16). It contains the
configuration data for the unit such as the customer number, the serial
number and ID of the MCC-545C, and the authorized FCC frequencies it
may use. This information is normally programmed into the unit prior to
shipment. The Script files are also stored in Parameter memory, either
at the MCC facilities or on site.
3.7.3 Data Memory (RAM)
The Data memory is volatile RAM (1024K x 8) and has battery backup.
Date, time, executable programs, command parameters, and program
dynamic data (messages, data, position, etc.) are all stored in RAM
during normal operations. As an option, the Data memory may be
expanded to 2048K x 8.
During normal operation, the MCC-545C software uses the data and
configuration parameters stored in RAM. If the data information in RAM
is lost or corrupted, for whatever reason, the configuration parameters
can be retrieved from Parameter memory. This ensures uninterrupted
operation.
The RAM contents will be lost under the following conditions:
• The Boot command is issued.
• The Reset button (SW1) is depressed. (Remove the rear panel to
locate SW 1.)
•The internal backup battery fails or is disconnected. (In -02 units,
remove jumper JP1 while the external power is turned off to the
unit. In -03 or later units, remove connector J1.)
•The watchdog timer initiates a restart.
The software will detect these events and will recopy the parameters
and configuration values from Parameter memory back into RAM when
operation is resumed.
If the contents of Parameter memory become invalid the unit will revert
to the factory defaults in Program memory.
3.8 Front Panel LEDs
The two LEDs on the front panel provide the operator with a quick
assessment of the unit’s operational status.
3.0:1
Transmit power is normal but VSWR is
greater than 3.0:1
Transmit power is off or below normal
4. INSTALLATION
Site selection and general installation guidelines are provided in this
section, including instructions for cabling, antenna and power source
connections. Power up procedures, initialization and functional test
procedures are described that should be performed prior to placing the
MCC-545C on-line within the network.
4.1 Site Selection
There are 5 important factors to consider in selecting an optimum site:
1. External noise/interference
2. DC power source
3. Horizon angle
4. Antenna type
5. Antenna height
4.1.1 External Noise/Interference
Noise and signal interference can reduce the performance of the MCC545C. The most common sources of noise and interference are as
follows:
The information bandwidthofthesystemislessthan25kHz,therefore,
a very narrow bandwidthantennamaybeusedwhenoperatingona
Inatwo
must be wideenoughtoaccommodatebothfrequencies
antenna must providea50ohmload
frequencies are used:TX=45.90MHzandRX=44.20MHz
Bandwidth of the antennausedis1.7MHz.
Always consult withMCC’sen
any questions arisewithrespecttoantennaselection.
Assembly instructionsareincludedwitheachantenna
these for proper assemblyforallantennaelements.
DCN
All Rights Reserved. Proprietary and Confidential. Do
frequency network the bandwidthofthe
In the U.S. CONUS Network,two
The
gineering department for assistancewhen
Pleasereferto
Figure 7
Figure 8: 3-
single frequency.
antenna
. The
.
.
.
02/10/2012
24
Prerelease
00001789-A
545C Operations Manual
3.0 .211
3.4
1.8 .425
12.6
1.2 .870
20.1
.48 .500
15.0
.26 .875
33.0
100
150
200
250
300
350
400
450
500
550
600
650
700
750
800
850
900
950
1000
4.1.5 Antenna Height
The height of the antenna should be optimized as a function of the
distance between the Remote Station and the Master Station. A plot of
optimum antenna height versus range is shown in Figure 3.3.
Figure 9: Remote station antenna height for meteor burst
100
95
90
85
80
75
70
65
60
55
50
45
40
35
Antenna Height (ft)
30
25
20
15
10
5
0
Best Antenna Height
4
0
M
h
The antenna cable length must be kept as short as possible to minimize
line losses. Try to maintain a line loss between the antenna and the
MCC-545C to less than 2 dB.
A table of cable loss (at 50 MHz) for various types of co-ax cables is
given in Table 3.1 for reference.
4.1.6 Human Exposure To Radio Frequency Electromagnetic Fields
For fixed applications, antenna gains and mounting techniques can vary
depending on the application. Antennas suitable for use with the MCC545C are listed in the MCC-545C RF Energy Exposure Guide. It includes
details on the human to antenna separation requirements for specific
fixed and mobile antennas with various gains.
Always disable the transmitter when working on the antenna and/or coax cable.
4.2 Equipment Installation
The MCC-545C operates over a temperature range from -30°C to +60°C
and is housed in a stainless steel enclosure that can be used in a wide
range of applications.
4.2.1 Mobile Applications
Mobile applications can include vehicles, aircraft, vessels, and
locomotives. Each application may require a different type of antenna.
For example, a 3' base-loaded ¼-wave whip is generally a good solution
for vehicles. Low profile antennas, vertically polarized, are required for
locomotives. 10' ¼-wave whips are generally used for vessels; these
antennas should be designed for operation in maritime environments.
Refer to the MCC-545C RF Energy Exposure Guide for more antenna
information and means to limit RF exposure. MCC’s engineering services
department can be contacted for specific recommendations.
For vehicle installations, the MCC-545C may be mounted in any
convenient location (e.g., in the trunk, under the seat, or in the engine
compartment).
Refer to Appendix E for a list of example equipment components
required for an MCC-545C used in a typical mobile application.
The case of the MCC-545C itself is not waterproof, and a NEMA
waterproof enclosure is recommended for outdoor installations. To
ensure proper operation, shielded cable is recommended for all
connectors. Also, use adequate strain relief on all cables and a
weatherproof seal at the entry point of the enclosure.
A typical Remote Station data collection installation is shown in Figure
3.4.
Refer to Appendix E for a list of example equipment components
required for an MCC-545C used in a typical data collection application.
Figure 10: Typical remote station with 3-element YAGI antenna
There are a maximum of four cable connections to be made to the MCC545C, as shown in Figure 3.5. These connections are used for both
mobile and fixed site applications.
Figure 11: MCC-545C cable connections
DC Power
The MCC-545C requires a power source that can deliver up to 25 amps
of pulsed power (100 msec) out of a +12 VDC to +14VDC power source.
The 25 amp power demand will cause a voltage drop to occur at the
transmitter input, resulting in reduced transmit power, unless the
power cable to the source is sized appropriately. MCC recommends
using two #16 AWG wires for both the power and ground, with a cable
length that does not exceed 10 feet. If a longer cable is required use
#14 AWG. MCC provides a standard 6-foot power cable with lugs for
connecting to a 3/8" battery post.
The 44 pin I/O connectoronthefrontpanelincludesthreeRS
and one Sensorport
out these four portsasshowninFigure
545C OperationsManual
Proprietary and Confidential. Do Not Distribu
223maybe
Use a large diametercable(RG
Refer to Section 3.1.5forproper
MCC provides a standard cable harnessthatbreaks
Figure 12: MCC
transmission.
VHF Antenna
cable length.
545C power connector pins
.
.
. RG-
-
used.
panel.
I/O Port
ional)
-232 ports
.
13:
02/10/2012
Prerelease
DCN 00001789-A
29
545C Operations Manual
Figure 13: MCC-545C I/O port cable
Operator Port
The Operator Port is normally connected to a local operator terminal.
Use a standard RS-232 cable with a 9-pin male D connector. Normally,
only 3 wires (pins 2, 3 and 5) are required when connecting to the
operator port. The port is wired to support handshaking where required
such as when using a modem.
Data Port
The Data Port may be used for connecting to a data logger, GPS
receiver or other serial input device. Use a standard RS-232 cable with a
9-pin male D connector. Refer to Section 4.5 for more information on
interfacing to data loggers or other serial input devices.
drop at the input connectorduringtransmissionshouldbelessthan2VDC
for proper operationoftheunit.Verifythisduringthe
Procedure in Section3.4.
DCN
All Rights Reserved. Proprietary and Confidential. Do
545C, check all connections
3.2.3 forcabling
Disconnect the antenna cable until all stepsinSection
installed,to
based terminal
545C is programmed with the f
no
ASCII
none
545C by applying +12VDC to the power connector.
transmits, it will draw up to 20 amps; therefore,
OperationalTest
4.3 Power-
Important:
between the MCC-
instructions.
4.3.1
the Operator Port
-
Caution
XTermW
XTermW is an MCC windows-
. The
4.3.2
Baud rate
Data bits
Stop bit
Power up the MCC
Note:
-
ollowing
02/10/2012
34
Prerelease
00001789-A
545C Operations Manual
When power applied is initially applied to the MCC-545C, or after a
software boot or hardware reset, the following message will be
displayed:
545C PACKET DATA RADIO
(c) Copyright 2005 Meteor Communications Corp.
All Rights Reserved
S/W Part Number* P1079-00-00 Version* 6.87 09/29/05
* Part Number, Version Number, and date vary according to a particular
radio’s firmware.
At this time all configuration data is loaded from Program Memory into
RAM. This data will remain in RAM and on all subsequent power-cycle
sequences the following message will be displayed:
01/23/04 16:54:10 POWER SHUTDOWN/FAIL OCCURRED.
02/02/04 12:54:44 POWER HAS BEEN RESTORED... RESUMING OPERATION.
+
This is the type of message that should be displayed when you first
apply power to the unit during a field installation, and for each
subsequent power cycle of the radio.
If the greeting message is not displayed, then the RAM contents may
have been lost under one of the conditions described in Section 2.4 and
the proper script file must be re-entered into the MCC-545C using
XTermW. (Refer to Sections 3.3.3.5 and 4.2.7 and Appendix C for more
information on using script files.)
4.3.3 Initialization Procedures
The following initialization procedures should now be performed in the
order they are given below.
Verify Device Type
The MCC-545C must be programmed to operate as a particular device
type, such as Remote Station, Repeater, or Base, depending on your
network configuration. The device type is normally set at the factory
prior to shipment to ensure proper integration with your network.
Refer to Section 3.1 forreducingsitenoiseconditions.
An overall figure of meritforthelinkperformanceistheXMITtoACKratio.
If this ratio is 3:1 or lower,theoverallperformancewi
This completes the initializationandpower
The unitisnowreadyforoperation.
Refer to Chapter4fordetailedoperatinginstructions.
DCN
All Rights Reserved. Proprietary and Confidential. Do
rf resets
Station.
This should be greater than 80watts.
This should be less than 5 watts.
This shouldbe
This will normally be the
120.
er are low, the transmittermaybe
110 dBm),theunit
ll be verygood.
up sequence of the MCC
where: xxxx=
yyyy=
zzzz=
aaaa =
bbbb=
ccc=
ddd=
eee=
Note:
voltage
-fwd pwr-rev v-bat det-
-545C.
.
.
.
VDC.
dBm.
–
02/10/2012
40
will still perfo
–115 dBm (for example, -
-
-545C.
Prerelease
00001789-A
545C Operations Manual
5. OPERATIONS
This chapter covers the basic operating procedures for the MCC-545C as
it is used in the FleetTrak™ network. The MCC-545C is programmed
through the use of Script Files that contain the specific system
parameters for operating in various modes. A script file is loaded into
the MCC-545C at the MCC facilities prior to shipment. Script files may
also be loaded and/or modified at the customer’s site. (Refer to Section
4.2.7 and Appendix C for more information on Script Files.)
The last section of this chapter provides a summary of all MCC-545C
commands; printouts from frequently-used commands are included in
Appendix A.
It is assumed at this point that the appropriate script file has already
been loaded into the unit, as part of the installation procedures
outlined in Section 3.3, and that the unit is configured properly and
operational within its network. This chapter describes the various
commands that are available to the operator for modifying the station
configuration parameters to accommodate specific applications, sending
and receiving messages, and interfacing to peripheral devices for
position reporting and data collection.
5.1 Getting Started
5.1.1 XTermW Terminal Emulator
XTermW is a windows-based terminal emulation program supplied by
MCC. It is designed for interfacing with a wide variety of MCC products.
All commands, script files, etc., can be entered into the MCC-545C
using XTermW. The last section in this chapter contains a list of all valid
MCC-545C commands.
XTermW can also be used to create log files of MCC-545C operations.
Refer to the XTermW documentation supplied with the program.
Whether using XTermW, another terminal emulator, or a hardware
terminal, you must program the operator terminal to use the same
configuration parameters as the MCC-545C Operator Port. The Operator
Port of the MCC-545C has the following factory default configuration:
Baud rate
Data bits
Stop bit
Parity
Protocol
Flow control
5.1.2 HELP Command
Entering HELP [ENTER] displays all of the commands used in the
operation and maintenance of the MCC-545C. To obtain descriptive
information about a particular command and how it is used by the MCC545C, enter the command type. For example: HELP, ASSIGN [ENTER].
Refer to the last section of this chapter for a complete list of MCC-545C
commands.
5.1.3 Role-Based Operations
The role that the MCC-545C plays in a communications network
determines how it should be configured. There are three basic roles
that an MCC-545C can be used in, depending on the network type:
•LOS Network consisting of Base and Repeater Stations, and
Remote/Mobile units; Base Stations do not communicate with each
other in this type of network. This is a typical FleetTrak™ network.
•LOS Network consisting of one or more Master Stations and Remote
Stations (either fixed position or mobile units); Master Stations can
communicate with each other in this type of network. This is a
typical DataNet network.
•Meteor Burst network consisting of a single Master Station
communicating with Remote Stations in fixed positions; Remote
Stations do not communicate with each other in this type of
network. This is a typical Meteor Burst network.
Table 4.1 shows the roles for which an MCC-545C can be configured; this is just an overview of the general commands
needed for each role. The MCC-545C is not normally used in a Meteor Burst-only type of network.
Appendix F contains a description of the interoperability of all three types of MCC networks.
Table 6: Role-based operations
LOS Network
Base and Repeater Stations
Remote/Mobile units
ROLE,LOS
DEVICE,BASE
DEVICE,REPEATER,id (which Base or Repeater to report to)
DEVICE,REMOTE
For Base/Repeaters:
ID,master id
For Remotes:
ID,remote id, master
id,AUTO
P,t (idle probe rate – typically t=20
seconds for Base and Repeaters; set
t=OFF for Remotes in an LOS network)
BASE,low id,hi id (typically 2-230 –
used as a switch that turns the
Base/Repeater mode on)
CONNECT, master id1, master id2
(limits which Master(s) a Remote Station
can communicate with)
SNP,NDOWN,2,10 (Remotes switch to
LOS Network
Multiple Master Stations
Remote Stations (fixed or mobile)
ROLE,LOS ROLE,TRANSPOND
DEVICE,MASTER
DEVICE,REMOTE
ID,master id
For Remotes:
ID,remote id, master id
Meteor Burst Network
Single Master Station
Remote Stations (fixed)
DEVICE,REMOTE
ID,master id
For Remotes (single Master):
ID,remote id, master id
For Remotes (multiple Masters):
ID,remote id,1,MULTI,INIT
P,t
seconds for Base and Repeaters; set
t=OFF for Remotes in an LOS network)
BASE,OFF
CONNECT, master id1, master id2
(limits which Master(s) a Remote Station
or Master Station can communicate with)
Every MCC unit is programmed at the factory with a 16-bit unit ID. This
allows up to 65,536 unique ID numbers per network. Type the command ID
and press [ENTER] to display the unit ID number on the operator terminal.
In some cases this number will be “locked” and cannot be changed in the
field; you can type LOCK to determine if the ID is locked or not.
Under some circumstances the ID may have to be changed on-site. It can
only be done if the ID is not locked. In that event, this action must be
coordinated with both MCC and your System Administrator. Failure to do so
may result in data or messages being misrouted or lost. In addition, the
network topography and statistics will receive incorrect data that will
impair network performance.
To change the ID, enter the following command:
ID,nnnnn,mmmm{,aaaaa},INIT
where:nnnnnn =
mmmm =
aaaaa =
Obtain the proper Master Station assignment and select mode from your
System Administrator. The MCC-545C will save this ID and will use it
whenever the unit is powered up or reset.
Mode Description
PREF
SNP command). After NDOWN period unit connects to the Master Station
that it has received the most syncs from. In this mode the unit can communicate with only one Master at a time.
AUTO
switches to another Master Station. It will stay with that Master Station as
long as it can communicate with it. In this mode the unit can
communicate with only one Master at a time. This is the standard
mode for FleetTrak™ networks.
parameters, using thescriptfile(refertoSection4.2.7).
System Time andDate
545C has itsowninternalclock
its clock to the nearestsecondeitherwithitsass
own internal GPS receiver(ifavailable)
TIMESYNC,source
DCN
All Rights Reserved. Proprietary and Confidential. DoNotDistribute.
Master Station
.
In thismodethe
specific network or system ID, an assettracking
periodically it can synchronize
igned MasterStationorits
Enter the following command:
.
This is the
Mode Description
FIXED
the
MULTI
Station.
ID,nnnnn,1,M
ID,aaaaa
Customer ID
The MCC-
number, or other
Factory Default Parameters
mmmm
. This is
-
5.1.5
Note:
case, you need to
The MCC-
LOCKED before typing
–
.
02/10/2012
46
Prerelease
00001789-A
545C Operations Manual
where: source = ON(sync with Master Station)
= GPS(sync using internal GPS)
= OFF(uses internal clock only)
If required, the MCC-545C’s internal date and time can be initialized by
entering the following commands:
DATE, mm/dd/yy
TIME, hh:mm{:ss}
The Master Station receives the correct date and time from either its Host
or an RTCM broadcast. The Master Station then periodically broadcasts this
date and time information to all Remotes for synchronizing their internal
clocks.
The date and time of day maintained in the MCC-520B Master Station is
transmitted to all Remote Stations between the times of 00:10:00 and
00:50:00 of each day, time keeping all units in a network on the same time
reference. If the time of day received at a Remote Station differs by more
than two minutes from the internal Remote clock, the Remote will set its
clock to the received time of day.
To properly manage time, each Master Station and Remote Station must
know how its own time zone relates to UTC and the system time. This
relationship is established by relating its time zone to known reference
points. UTC is always referenced to GMT; however, system time can be
referenced to any desired time zone.
The time zone offset is defined with the following command:
TIME ZONE, UTC offset, local time offset
Always set “UTC offset” to 0; the “local time offset” should be set to the
Remote Station’s time zone offset (+/- TZ) from the Master Station time
zone.
5.1.6 System Memory
The MCC-545C is designed to operate unattended in a variety of
environments where power may be applied continuously or intermittently.
The goal is for the unit to continue to operate without loss of messages,
data, or configuration, even if power is randomly turned on and off.
Therefore the software is designed to operate continuously, to save all
operational information when power is off, and to resume operation from
that point when power is restored.
To support this design, the MCC-545C has three types of memory:
1. Program Memory (PM)
2. Random Access Memory (RAM)
3. Configuration Parameter (CPM)
The PM is non-volatile flash memory that has been programmed with the
MCC-545C’s operational software. This software contains the initial values
of all operational parameters. The values are referred to as the “factory
defaults” because they are programmed into the MCC-545C operating
system software at the factory. The PM can only be modified by replacing
the operating system using the flash download. (Consult XTermW manual to
learn how to download a new flash into the PM.)
The RAM contains all the dynamic data for the MCC-545C. All data logger
data, positional data, and messages entered into the MCC-545C are stored
in RAM. Also, all command parameters are stored in RAM. But RAM is
volatile and can only retain information while power is applied. Turning off
or disconnecting power will cause all RAM information to be lost. To
prevent this, a small internal NiCad or Ni Metal Hydride battery (internal to
the unit) is used to maintain power to the RAM when external power is off.
During normal operation, the MCC-545C software operates from the data
and the parameters that are stored in RAM. Unfortunately, there are
always situations when the RAM data may be lost or corrupted due to total
discharge of the battery, software crash or operator error. Since we do not
want to lose our configuration data during these situations, we have a third
type of memory.
The third type of memory, CPM, is also nonvolatile flash memory and
retains data even when power is removed. The MCC-545C retains a copy of
all the programmed configuration parameters in CPM. The MCC-545C will
write configuration parameters, that have been entered from the operator
port, into CPM when the SAVE command is entered. Only values that have
changed are written into CPM. Whenever the unit radio ID is changed the
MCC-545C will automatically SAVE the configuration. A validation checksum
to application, thereforerefertoyoursystemsmanualorconsultyour
r forcorrectsettings.
545C OperationsManual
DCN
.
These will be lost if the internalbattery
It will not be lost if the
icating to theunitfroma
From this starting point, the user can programthe
As soon as the parameters are enteredtheytake
y loadinga
It is alsopossibleto
.
Refer to the last sectionofthis
545C to operate correctly in your network,itmustbe
Configuration requirements will vary fromapplication
pointer.
When the MCC-
effect.
-545C to verify the data in CPM is correct
.
.
.
.
If the
the
.
5.2
Caution:
systems manage
.
This section
.
te list of commands.
-
.
02/10/2012
Prerelease
Proprietary and Confidential. Do Not Distribute.
00001789-A
49
545C Operations Manual
5.2.1 Configuring the MCC-545C
Configuration parameters include the unit ID, the Master Station
assignment, I/O port functions and baud rates, transmit and receive
parameters and network parameters. Parameters or operational states set
by these commands are retained and will determine the way in which the
MCC-545C will interact with other equipment at the site and with the
communications network.
Most configuration parameters can be viewed with the CONFIG, ASSIGN,
SNP, and CR10X commands. You should use these commands to verify that
the configuration is correct. If it is not correct, use the appropriate
command(s) to correct the configuration, and then enter the SAVE
command to write the configuration parameters into the Configuration
Parameter Memory (CPM) for non-volatile storage.
The software normally executes using the data and parameters stored in
RAM. When the unit is turned off, or power is disconnected, the RAM
information will be maintained by battery backup. When main power is
restored the unit continues operation from RAM. When this happens, you
will see the following message on the Operator Port. (See Section 3.3 for
details.)
POWER SHUTDOWN/FAIL OCCURRED
POWER HAS BEEN RESTORED... RESUMING OPERATION
The RAM contents will be lost under the following conditions:
• The boot command is issued.
• The Reset button (SW1) is pressed.
• The internal battery backup is disconnected.
• The internal battery fails or is discharged.
• The software crashes and restarts.
The software will detect these events and will then recopy the
configuration values from CPM back into RAM when operation is resumed.
The software will revert to the factory settings contained in the PM if the
contents of the CPM become invalid.
The user should beware that it is possible to “get in trouble” using the
configuration process. For example, assume you accidentally set the
protocol for the operator port to MSC. If you do not have the ability to
interface using MSC protocol you will immediately lose contact with the
MCC-545C. You will no longer be able to issue commands. Power cycling
will not help either because your change will be retained in RAM, even
through power cycling. However, you can always recover by removing the
lid on the MCC-545C and pressing the Reset button (SW1). This will reboot
and restore the CPM settings.
Alternatively, assume you want to change the operator port to MSC. You
connect in ASCII protocol, command the change to MSC protocol, then
switch your PC to also use MSC protocol. Operation resumes and all is well.
But do not forget to do a SAVE. If the software ever reboots, it will revert
back to ASCII. And remember, once you do the SAVE you are committed to
MSC protocol. The Reset button now reboots to MSC and there is no easy
way back to the factory default settings. You will need an MSC capability to
command a change back to ASCII.
5.2.2 Setting frequencies
The MCC-545C is programmed at the factory with the authorized
frequencies to be used in your network. These frequencies are stored in
Parameter memory and cannot be changed.
You can display TX and RX frequencies by entering the following command:
FREQUENCIES
This shows you the active or “primary” TX and RX frequency pair, plus up
to 9 additional frequency pairs for channels that may be programmed at
the factory.
parameters, first reviewthediscussioninthissection,thenusethe
following commandstochangetothedesir
{,pname,value}
where “pname” is thenetworkparameterand“value”isalimitdependent
The “pname”parametersareasfollows:
live inminutes(defaultis120minutes);thisisthetimelimit
for a message to reach
545C OperationsManual
DCN
-
power mode or not.
operate as either a Remote Station or as aMaster
DEVICE,MASTER
) command is used inboth
Before you choose to changethese
its destination before it is deleted fromthequeue.
5.2.9
Selecting MCC-
The MCCStation.
For normal MCC-
For MCC-
Note:
device type.”
-545C commands are available when
Selecting Network Parameters
The
are set on power-
SNP
on “pname”.
TTL
– Time-to-
02/10/2012
SNP
-of-sight operations.
.
ed settings:
Prerelease
Proprietary and Confidential. Do Not Distribute.
00001789-A
57
545C Operations Manual
The time-to-live parameter input is truncated to a 10-minute boun¬da¬ry.
If you enter 60 through 69, the TTL for the next message will be 60
minutes. A resultant value of 0 (parameter range 0 – 9) means the message
will never time out.
TTR
– Time-to-retransmit in minutes (default is 30 minutes); i.e., the
message is retransmitted if it has not reached its destination within this
time frame.
NUP
– Neighbor-up threshold (default is 2 acquisitions); the number of times
a Station must hear from another Station within a one minute time interval
before it becomes a neighbor.
NDOWN
,xx,yy – Neighbor-down threshold in “xx” minutes (default is 120
minutes), and “yy” is the number of times a Station attempts to
communicate with a neighbor before attempting to talk to another Station;
if there is no communication with a neighboring Station within the set
time, the route to that neighbor is ignored. Setting NDOWN to 0 maintains
the routing to the neighbor indefinitely.
RDOWN
– Remote-down threshold in minutes (default is 2 minutes); if there
is no communication with a Remote Station within the set time, the
Remote is declared down and is removed from the Remote table. Setting
RDOWN to 0 keeps a Remote defined indefinitely.
OTL
– Outstanding text limit (default is 20 texts); the number of messages a
Station is allowed to send to another Station without an end-to-end
acknowledgment.
CONNP
(Master Station operation only) – Connectivity message precedence
(default is 1 precedence); information on changes in the connectivity table
is given highest precedence (automatic feature).
ETEAP
– End-to-end ACK message precedence (default is 2 precedence);
the acknowledgment of a message when it reaches its final destination is
given highest precedence.
HTO
– History file timeout in minutes (default is 5 minutes); maintains
(Master Station operation only) – Text message packet size in
segments (default is 32 segments).
FLOODP
(Master Station operation only) – Partial “flooding” precedence
level (default is A precedence). Messages of this precedence level and
above are transmitted over all routes of minimum length; messages below
this precedence are not sent over all minimum length routes, but are sent
only over the routes where the shortest transmit queues exist.
MBHOP
– meteor burst link hop weight (default is 1 hop). Defines the
number of network hops to associate with a meteor burst Master Station
link when determining the minimum path to use in routing a message.
MBHOP should be set high enough to prevent a meteor burst Master Station
link to be chosen over a line-of-sight Remote to Remote link in a network
that is predominantly line-of-sight.
INF
(Master Station operation only) – Infinity hop count (default is 8 hops).
Defines the width of the network in hops plus one to determine when
connectivity to a node is broken. Should be as low as possible to minimize
auto-connectivity traffic in the network, but large enough to not
erroneously flag nodes as being offline.
RELAY
(Master Station operation only) – Relay function specification
(default is ON). Specifies whether the MCC-545C should act like a Remote
Station in terms of relay functionality (i.e., does not share connectivity
table with other Master Stations).
DATAP
– Priority of data reports initiated at the MCC-545C (default is Y
precedence). When used in any data collection network, this setting
defines the precedence of data reports generated asynchronously by the
equipment itself. Typically, it should be lower than operator entered
messages and commands.
Message accountability guarantees that text messages get delivered to
their proper destinations within an allotted time. Data reports, position
reports, and remote commands/responses donot get this guarantee. They
get only one chance to get through the network.
Networks can have units go offline for various reasons; local noise can
interfere with RF links, congestion can slow throughput to a crawl, RF link
bit errors can cause segments of a message to get lost, etc. The more
complex a network is, the more chances there are to be problems.
Messages entered at each source unit specify a time-to-live (TTL); this time
is the maximum time to attempt to deliver it. If it is not delivered in this
time, the operator at the source unit is informed so something can be done
about it. The time-to-retry (TTR) is the number of minutes between
attempts to deliver the message. Once a message is sent, it goes through
the network one hop at a time and can get blocked at some point if the
connectivity changes suddenly. The retry attempts are separated to allow
network changes to settle out and establish alternate routes. When a
message is received by a destination, an end-to-end-acknowledgement
(ETE) is sent from the destination back to the source to stop any more
retries and let the operator know the message was received.
The maximum message size is determined by the text length (TEXTL)
setting. A message packet can consist of up to 3570 characters and is
further subdivided into segments. Each message is uniquely identified so it
can be tracked through the network and the ETE can be sent for each
individual message. The message ID consists of the originator ID (16 bits)
and message serial number (8 bits). Serial numbers range from 1 to 255 and
are assigned in round-robin order. Each message is then split into 14-byte
segments which are in sequence from 0 to 255. The segments allow the
message to be transmitted a little at a time over short meteor bursts. The
segment sequence numbers are used by the RF link software to identify
which ones are acknowledged and to indicate where to resume on each
burst.
The first segment (sequence number 0) is the message header and contains
all the network overhead (originator ID, message serial number, priority,
I/O port entered on, message type, number of destinations, number of
segments, time to live, retry count, multi-packet message serial number,
packet sequence number, total number of packets and first destination ID
code). If the message has only one destination, segment 1 is the start of
the actual text. If there are multiple destinations, segment(s) 1, . . . n
contain the remaining destination codes, 7 destination codes per segment.
The text starts on the next segment after the last destination code.
Network Connectivity Tables
SNP,NUP
SNP,NDOWN
SNP,RDOWN
Network connectivity tables are automatically created and updated each
time a Master detects a new neighbor unit or times out an existing unit.
The NUP parameter gives the number of transmissions that must be
received in one minute to declare a new neighbor. The NDOWN parameter
gives the number of minutes with no receptions to time out a Master
neighbor. The RDOWN parameter gives the number of minutes to time out
a Remote neighbor. Setting NDOWN or RDOWN to “0” disables the feature
(i.e., never declare neighbors down). The NDOWN parameter can also be
set for the number of times a Station attempts to communicate with a
neighbor before attempting to talk to another Station.
Congestion Control
SNP,OTL
The OTL parameter specifies the maximum number of messages that will
be transmitted while waiting for ETEs. Limiting messages, as cars are
limited to entering the freeway at rush hour, tends to reduce congestion
and memory buffer usage in the network and reduce the number of retries
that happen as a result. Sending messages one at a time does not take
advantage of the overlap caused by the ETE needing to come back through
the network and does not take advantage of an occasional large burst that
can significantly improve throughput.
The priority of network control messages should be set higher than the
data traffic. This setting makes sense if you realize that messages can not
get delivered as fast if the network connectivity is incorrect. Certain
applications may have reasons for altering these values but any revision to
the default priority scheme should be implemented carefully.
History Timeout
Hop Count
SNP,HTO
History timeout for duplicate filtering
As each message is received by a unit, the originator ID and message serial
number are retained in a history table. The HTO parameter specifies how
long to retain each entry. Each received message ID is compared to this
table and if the message was previously received and has not timed out, it
is considered a duplicate message. The ETE is sent to the originator if it is a
text message type but the duplicates are not output to the I/O ports.
Duplicates happen due to network connectivity changes and retries.
SNP,INF
Infinity hop count
The INF parameter specifies the maximum width of a network in hops + 1.
If this parameter is set lower that the actual network width, units will be
declared offline when they are not. If the number is set too high, extra
connectivity packets are exchanged when a unit goes offline and the
system looks for alternate routes.
SNP,MBHOP
Meteor burst link hop weight
The MBHOP parameter defines the number of network hops to associate
with a meteor burst Master Station link when determining the minimum
path to use in routing a message. This parameter should be set high enough
to prevent a meteor burst Master Station link to be picked over a line-ofsight Remote to Remote link in a generally line-of-sight network.
Message Relay
SNP,RELAY
Enable/disable Master’s ability to relay messages for
The MCC-545C, when configured as a Master Station, reports all of its
neighbor connectivity to its neighbors when SNP,RELAY is set to ON. If it is
set to OFF, it does not report any neighbor connectivity. The OFF setting
keeps neighbor units from finding alternate network paths through that
node. This option should be left ON unless there is a very good reason to
have it OFF for some specific customer requirement.
Selecting the Burst Monitor
The MCC-545C has a unique meteor burst monitoring capability that allows
monitoring the number of characters received, the RF signal level and
other parameters on each reception.
To turn on the burst monitor and to record statistics on a meteor burst
link, type:
MON{,d{,r}}
The two optional parameters are designed to limit the printout. The burst
monitor generates two or three lines of printout for every burst. This could
conceivably create hundreds of pages of printout a day in a network
environment. The first parameter is the duration character count limit.
Only meteors lasting long enough to deliver “d” characters will be
monitored. The second parameter is the received character count limit; if
at least “r” characters are received on the burst, a monitor line will be
generated. The default values are 100 for “d” and 1 for “r”. For example,
to limit the printout, but still receive some maintenance benefit from the
monitor, enter:
545C Operations Manual
MON,500,100
This will limit the printout to meteors that have a duration character count
greater than 500, or a received character count greater than 100. These
parameters may be adjusted as desired.
The command MONOFF turns off the burst monitor.
Controlling the Hourly Statistics Report
By default, an hourly statistics report is generated on the maintenance
terminal port on the hour. This report consists of the same statistic reports
generated by the BINS, MEM, and STAT commands.
The hourly report can be disabled by entering the command:
The hourly report can be re-enabled by entering the command:
HOURLIES,ON
5.3 Sending and Receiving Messages
The MCC-545C is a packet data radio and therefore enables an operator to
send and receive messages to all units within the FleetTrak™ network.
The messages may be entered from an operator terminal that is connected
to the OPERATOR PORT of the MCC-545C. There are three basic message
types:
1. Free-form text messages
2. Canned messages
3. Commands
The general format for all messages is shown below:
MESSAGE,p,dest1,dest2,...dest n
where: p = any priority level from A (highest) to Z (lowest).
dest n
= numerical ID of the station(s) to which the
message will be routed.
The message text is then entered and edited in the Text Edit Buffer. They
are then transferred to one or more Tx Queue buffers for transmission to
the designated destinations.
Figure 14 depicts the general flow of messages within the MCC-545C
software and the various commands associated with each step in the
process.
The following operations are explained in this section:
Section Operations
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.3.7
4.3.8
5.3.1 Entering and Deleting Messages
All messages are composed and edited in the Text Edit Buffer. Messages
may be up to 3,570 characters in length. When composing the message you
must press [ENTER] at the end of each 80 character line.
There is a default destination programmed into the MCC-545C during the
installation and initialization of the unit when it is first brought on-line in
the network. If a message is not given a specific destination it will be sent
to the default destination only.
To enter a message:
1. Type MESSAGE. The operator terminal responds with ENTER TEXT.
The MCC-545C will now be in Compose-and-Edit mode (as opposed to
normal Command-Line Entry mode).
2. Enter a message up to 3,570 characters in length, pressing [ENTER]
at the end of each 80 character line.
3. Press the [ESC] key. The message is transferred to a Transmit queue
and will be automatically transmitted to the default destination at a
priority level R.
The following messageisdisplayedontheoperatorterminal:
MessageNo:
ROUTINGname:
If you wish to sendamessagetomultipledestinations,andatadifferent
priority level, type:
,p,dest1,dest2,...destn
If you also wanttosendthe
must enter its stationnumericalIDasoneofthedestinationparameters
(“dest1”, “dest2”, etc.)asspecifiedabove.
There are three otherspecialeditingfunctionsthatmaybeused:
To RetransmitthePreviouslyE
To retransmit a previouslyenteredmessage,simplypressthe[ESC]key
after the operator terminalprints
The previousmessageenteredintotheTextEditBufferisthen
sent to the destination
To Revise thePreviouslyEnteredMessage
To revise a previouslyenteredmessage,press[CTRL]
prompt to reviseapreviouslyenteredmessageortorecoverfroman
The
at the end of the message
To Delete a Message
To delete a messageafterithasbeenplacedintheTx Queue,type:
ID
sss
545C OperationsManual
DCN
= any priority level from A (highest) toZ(lowest).
ID of the stations to whichthe
message to your default destination,you
and before anyotherkeyis
MESSAGE
after the
previous message is displayed, with thecursorplaced
You may now resume editing the message.
hh:mm:ss
hh:mm:ss
MESSAGE
where:
dest n
Note:
1.
name:ss,nnnn
sss
TXT
sss/nn
chars,
TO:
nnn
segments
name
p
= numerical
message is routed.
ntered Message
pressed.
command.
2.
TEXT
aborted session.
3.
DELMSG,ID:sss
where:
ENTER TEXT
s that are now designated in the
.
= numerical station ID
= message serial number
T
ENTER
02/10/2012
Prerelease
Proprietary and Confidential. Do Not Distribute.
00001789-A
67
545C Operations Manual
Dele
tes the last character entered.
Prints the current line of text on the next line down.
Performs a fixed tab function
Removes the current line from the edit buffer.
Performs a carriage return and line feed.
Performs a
carriage return and line feed.
Removes the current line from the edit buffer and places
Prints the contents of the edit buffer & puts cursor at the
Erases the entire
contents of the edit buffer.
Aborts the edit mode and returns to the command mode.
Leaves text edit mode and queues the message for
The operator terminal displays the date and time, followed by MESSAGE DELETED.
5.3.2 Editing Messages
The following editing functions may be used from the keyboard while the
message is in the Text Edit Buffer.
Key Function
[DEL]
[CTRL]R
[CTRL]I
\
[ENTER]
[LF]
[CTRL]X
the cursor at the end of the previous line.
[CTRL]T
end of text.
[CTRL]D
[CTRK]A
A “+” indicates the command mode.
[ESC]
transmission.
5.3.3 Sending Messages
Messages are automatically stored for transmission with the [ESC] key. Each
message is placed in the Tx Queue according to its assigned priority.
Messages of equal priority are placed in the Tx Queue in the order received
from the Text Edit Buffer.
The following display appears on the operator terminal as the MCC-545C
stores and routes a message:
Messages are transmitted in packets and are routed to their destination in a
Store-and-Forward manner, using the most efficient routing within the
packet switched network. The originating station receives an
acknowledgement (ACK) if the message has been received successfully by
the first routing station.
mm/dd/yy hh:mm:ss TXTMSG ACK name:sss, xxxx CHARS FROM name
When the entire message has been delivered to its final destination, the
operator terminal displays an end-to-end acknowledgement:
hh:mm:ss END-TO-END ACK OF name:sss FROM name
If the end-to-end ACK is not received within the specified time-to-live
limit, the MCC-545C purges the message from the Tx Queue and displays
the following message:
hh:mm:ss MESSAGE TIME-TO-LIVE EXPIRED, MSG.NO:sss, DESTN: name
You must then re-enter the message. Continued failure to successfully
transmit a message indicates that something may be wrong with the
equipment or the link (e.g., excessive noise interference).
5.3.4 Sending Commands
Commands may be sent to any station within the network. The entry of a
command is similar to the MESSAGE command described in Section 4.3.1.
REMCMD,R,dest1,dest2,...destn
where: R = priority level
The operator is then prompted to enter the text of the command using the
message editor. Once the command is entered, press the [ESC] key to send
the command. The operator terminal will display:
All Rights Reserved. Proprietary and Confidential. DoNotDistribute.
still in an operational FleetTrak™ or MeteorBurst
g out. Use the
messages may beplacedinto
You may either send an edited textmessageora
= message length from 1 to 3000 characters
= total number of canned messages togenerate
Additional canned messages are
5.3.5
Important:
ing!
-
CANMSGOFF
The MCC-
. In
.
CANMSG
where:
= neighboring station ID
mmmm
= minimum queue depth from 1 to 25
(maximum of 10,000)
.
02/10/2012
70
Prerelease
00001789-A
545C Operations Manual
If the Total parameter was entered, the canned message mode stops when
the desired number of messages has been transmitted.
To enter an edited canned message, enter:
CANMSG,id
where “id” is the neighboring station’s ID. After composing your message
press the [ESC] key. The MCC-545C automatically routes up to 25 copies of
the canned message to the destination station.
Each canned message is acknowledged by the selected neighboring station.
No end-to-end acknowledgements are received for canned messages.
To manually terminate the mode, enter:
CANMSG OFF,id
Canned messages are normally not printed at the destination station. To
print canned messages as they are received, enter:
CANMSG MODE,PRINT
To turn off the print mode, enter:
CANMSG MODE,NO PRINT
5.3.6 Receiving Messages
When a new message is received, it is announced by the following display:
hh:mm:ss RECEIVING name:sss TXT sss/nn FROM name ROUTED TO: name
The MCC-545C then generates an acknowledgement of the message packet
and transmits the ACK to the neighbor from whom the message was
received:
hh:mm:ss TXTMSG ACK name:sss, nnnn CHARS FROM name
When the destination MCC-545C receives a complete message, it displays
the following message:
All Rights Reserved. Proprietary and Confidential. DoNotDistribute.
or printed unless theyarebeing
end acknowledgement is received for a message,itis
For example,
transmit queues for neighbor
5.3.7
where “
name:sss
Queue.
enter:
SMS{,id}
where:
Note: Once an end-
= station ID
-
5.3.8
Queue name
TXQ
(Transmit
Queue)
RXQ
(Receive
Queue)
To examine
SHOW TXQ
TXQ,006
006.
eue.
or
SHOW RXQ,id
.
SHOW
02/10/2012
72
Prerelease
00001789-A
545C Operations Manual
To delete the contents of the transmit and receive queues, you must
specify the exact queue by entering a station name:
FLUSH TXQ,id or FLUSH RXQ,id
For each message deleted, the terminal displays:
id:sss unlinked {and deleted}
The “and deleted” text appears only if the message is not present in
another queue. When all messages have been deleted, the terminal
displays:
queue flushed
To delete a specific message, enter:
DEL MSG,id:sss
The terminal displays:
Message deleted
To delete all messages from all queues, enter:
FLUSH MSG
For each message deleted, the terminal displays:
id:sss deleted
Entering the FLUSH MSG command deletes all messages in all queues for
every node of the network, including connectivity and end-to-end
acknowledgment messages.
5.4 GPS Position Reporting
The MCC-545C automatically transmits position reports derived from either
an external GPS receiver or from its own internal GPS receiver. The
appropriate script file must be loaded into the MCC-545C that allows it to
interface to the protocol used by a particular GPS. The NMEA 0183 Version
2.0 protocol is used in this section for descriptive purposes only. Please
consult MCC regarding script files for other protocols.
The MCC-545C will accept either a TTL or an RS-232 input from a GPS
receiver. The internal GPS uses the TTL interface and its output is
internally routed to the processor board assembly. If an external GPS is
used it may be connected to either the AUX port or the Data port using the
RS-232 interface.
5.4.1 Position Reporting Commands
The following commands are normally in a script file and are used for
configuring the MCC-545C for position reporting.
Command Description
ASSIGN,POS,p,GPS
SETBAUD,POS,4800,N,8,1
POS,nn,TEXT,NMEA
POS,LOCAL,nn
p
= Selects the desired port:
2
= External AUX, RS-232
3
= Internal TTL
nn
4800
= Baud rate
N
= Parity
8
= Data Bits
1
= Stop Bit
report to the system host.
TEXT
= Binary Text
NEMA
= Protocol type
Note: Each time a report is transmitted to the Host it
may also be sent to one of the local ports.
nn
sent to a local port.
Note: This feature is used when more frequent position
reports are desired on a local operator terminal than
are being sent to the Host.
MBNET200 (ELOS protocol) may be used to broadcast differential correction
data to all Remote Stations in the network. This eliminates the need for
having a differential GPS receiver at each MCC-545C mobile unit.
Differential beacon receivers are installed at base or repeater stations
only. The base stations then transmit the RTCM correction data at periodic
intervals to all repeaters and mobiles.
The ASSIGN and SETBAUD commands are used to configure the base stations
to use a beacon receiver.
Command Description
ASSIGN,POS,p,RTCM,nn
SETBAUD,POS,4800,N,8,1
A remote station will automatically receive and process the RTCM
correction data. No other configuration commands are required.
5.4.3 GPS Report Formats
There are two position report formats used. The POS format is the basic
report and has latitude, longitude, speed, heading and altitude. The POSS
format includes all the information above but also has a 16-bit status word
and an 8-bit code for appending canned messages. An example of each type
of format is shown in Figure 4.2.
P = Port number, normally AUX port (2)
is used.
Nn = The interval, in seconds, that the
RTCM error correction data is
transmitted. A value of 20 seconds
provides reasonable accuracy.
The Status bit field is application dependent and is normally defined by the
user. For non-maritime applications speed is converted from knots to MPH
on the operator’s display.
The GPS status bits define if the GPS receiver is locked and the accuracy of
the data.
Standard V1 accuracy will be about ±10 meters. V2 accuracy will normally
be ±2 meters and is dependent on the RTCM broadcast rate and the
distance between the mobile and the nearest base station.
5.4.4 GPS Receiver Setup
The setup procedure for a GPS receiver is generally different for each
manufacturer’s type. Connect a laptop or PC to the GPS receiver for
entering the desired sentences and update interval. A NMEA type GPS must
be configured as follows:
Type of sentence Update interval Status
GPRMC
GPGGA
GPVTG
1 second
1 second
1 second
The TRACE command may be used to verify correct GPS operation:
TRACE,ON,GPS
All characters received will be displayed on the Operator Port, including
sentence types. Verification that the position report is being transmitted at
the desired POS,nn interval may also be observed.
To disable the display output, enter:
TRACE,OFF
5.4.5 Position Reporting in Subnets
The SUBNET command assigns a subnet code number from 1-255. The code
number is maintained in the locked configuration parameter list along with
the serial number, customer number and frequency table. The command
formats are:
After entering a subnetnumberandalltheotherconfigurationitems,ent
to lockthecurrentsetting.
commandisusedinconjunctionwiththe
command to limit thepositionreportsthatcanbereceivedtoonlythose
transmitted by otherunitswiththesamesubnetcodeoranyBaseor
SUBNET
The default settingis
Messages and remotecommandsare
sent to or receivedfromanyotherunit.
$PENTM,ON
format reports, whichwillincludethe16
replacestheMCC
$PENTM,ON
Supervisory ControlandDataAcquisition
545C is designedtoperformasupervisorycontrolanddata
acquisition (SCADA)functionusingoneofthreemodes
External Data Loggers
Direct Mode Protocol
This section coversthesethreem
operations, includingdefiningDataRelays,the
545C’sinternalsensorvalues,anddetailsonthe
data logger devicedrivers.
A limited SCADA capabilityisbuiltinfo
logger capability isnotrequired
DCN
All Rights Reserved. Proprietary and Confidential. DoNotDistribute.
$PENTM,ON
, then the unit can receive all positionreports.
limited to the subnetandcanbe
command must be entered to enablethePOSS
SUBNETID
545C’s “normal” canned message.)Using
precludes the use of canned messagemode.
odes, plus more advanced SCADA
command,how
r those applications whenafulldata
The following capability is provided:
LOCK,CONFIG
The SUBNET
er
5.5
Repeater. If
Important: The
(The SUBNET IDSUBNET and
The MCC-
Sensor I/O Port
is OFF
OFF.
not
-bit status and 8-bit
.
-
:
to read the MCC-
5.5.1 Sensor Port
02/10/2012
78
PASSTHRU
GENERIC
.
Prerelease
00001789-A
545C Operations Manual
• 4 optically isolated inputs for discrete ON/OFF functions
• 6 analog voltage inputs (0 to 5V)
• 2 SPDT Form C relay outputs
In addition,±12VDC is supplied for sensor power and a +5V reference
voltage for sensor excitation is available.
The Sensor port interface is a 25-pin male D connector. The connector
pinouts and their respective functions are shown below.
The analog voltages are routed to a 10-bit analog-to-digital converter (ADC)
which provides a resolution of +/-.1% and an accuracy over temperature of
±0.5%.
The serial data streammayoriginatefromadatalogger,messagedevice,
or any peripheral thathasanRS
DIRECT MODE
networks, especiallywithexternaldataloggers.
operationissimilartoa“terminalserver”onPCEthernet
The MCC
on one of its ports (Operator,Data,orAUX),packetizesthedatainto
message segmentsandtransmitsittooneormoredest
Thethroughputratewillbedependentonchannel
availability at the timeoftransmission.
protocolisgeneralinnatureandallowstheconnecting
equipment at the sourceanddestinationtomanageallerrorco
messageacknowledgementprotocolcanalsobeusedasan
option to ensure reliabilityofmessagedelivery
selected using the
ASSIGN,DTA,1,DIRECT,30
This command woulds
with a 30 second timeoutconnection
independently andoperatesimultaneously.
A connection betweentheexternalequipmentandtheMCC
ing a “connect string.”Thetransferthenbeginsandcontinuesuntilthe
connection is terminated
assumed to exist andthedataisthenautomaticallyroutedthroughthe
network to the destinationequipment
connection: a permanentconnectionoranadhocconnection.
The permanent connectionismadebysettingtheconnectstring
keeps the port openatalltimesandallcharactersreceivedwill
tomatically be transmitted
port and the connectiondoesnotterminate
received from the destinationwillberoutedtothelocalportforprinting.
DCN
All Rights Reserved. Proprietary and Confidential. DoNotDistribute.
protocol can also be used in Meteor Burst
545C will accept any stream of unformattedcharacters
inationaddressesin
command, as shown in this example:
protocolmode
Any, or all, ports can besetup
545Cismade
The proper connections at the destinationare
here are two ways toestablisha
A connect string is not requiredtoopenthe
Likewise, all characters
-232 interface.
Note: The
DIRECT MODE
Networks.
the CSMA mode.
The DIRECT
FleetTrak
-
. The DIRECT
ASSIGN
et up DATA port 1 to use the DIRECT
.
ntrol. The
protocol is
Connection Management
us
Permanent Connection
au
02/10/2012
82
-
.
. T
OFF. This
.
.
Prerelease
00001789-A
Ad Hoc Connection
A connect string from 1 to 19 characters is used to open a connection on an
ad hoc basis. The connection will remain open for as long as characters are
being received or the connection times-out, whichever occurs first. Once
the connection times-out it must be reestablished.
If the connect string is unknown, the command ANY will open the
connection for any string of characters.
Connect Response
A connect response string may be enabled so that the peripheral device
initiating the message will receive confirmation that the connection has
been made. If the connect response string is turned OFF then no response
will be sent when the connection is made.
Message Management
A message may be as long as 3,500 characters. Each message is assigned a
sequence number and is broken up into a number of packets. A message
header is inserted into each message ahead of the first data character.
545C Operations Manual
where:
$DIR,p,m,s,n
p
= the assigned port to which the message is directed.
m = the message sequence number from 1-2554
s = the packet sequence number in a multi-packet message
n = total number of packets in a message
A message will be appended with either a terminator character or a
maximum character count. The message will be terminated by either one
of these characters or the “time-out” whichever occurs first.
Shorter messages are normally contained in a single packet with the s,n
parameters set for 1,1. Longer messages will have several packets
contained within the same message number “m”. The “s” parameter for
each packet will be incremented but the “n” parameter will be set to 0.
The true “n” value is only transmitted with the last packet in the message.
For example, for a 3 packet message the s,n and m parameters will be as
follows:
Messages may be transmitted from one to four destinations. When a
DIRECT message is received at the destination MCC-545C, it will be routed
to the assigned port(s) (Operator, Data or AUX). There are two types of
connections that may be used: point-to-point and multi-point-to-singlepoint.
Point-to-Point
In the point-to-point mode the destination MCC-545C must also be preprogrammed in the DIRECT mode. When the message is received at the
destinations, the $DIR,p,m,s,n header will be removed from the message
and the message will be routed to the same port that was used at the
source. That is, messages that were originated on Port 1 must also be
routed to Port 1 at the destination.
1 1 0
1 2 0
1 3 3
The destination unit can respond with its own character stream back to the
source. This provides a direct point-to-point, bi-directional channel
between the two stations. The embedded ETE acknowledgement in the
ELOS protocol may be used for ensuring message delivery.
Multi-Point-to-Single-Point
Many remotes can be set up to operate in the DIRECT mode, all routing
their data to a common destination (base station or Host). The destination
station does not have to be pre-programmed in the DIRECT mode as in the
point-to-point case. The destination station will treat the message as it
would for any other text message, using one of the many available port
protocols. The message header, $DIR,p,m,s,n, is retained with the message
so that the destination station will know how to format a return message to
the source station. In this manner, the Host can send response packets to
all sources by appropriately formatting the message header.
Various options may be set up in the MCC-545C using the command DIRECT
with the parameters shown in the following list. Each command is briefly
described below:
Command List:
DIRECT
DIRECT, p, CONNECT STRING, OFF
DIRECT, p, CONNECT STRING, ANY
DIRECT, p, CONNECT STRING, connect-text-string
DIRECT, p, CONNECT RESPONSE, OFF
DIRECT, p, CONNECT RESPONSE, response-text-string
DIRECT, p, PACKET TIMEOUT, decimal-timeout-ticks
DIRECT, p, PACKET TERMINATOR, OFF
DIRECT, p, PACKET TERMINATOR, decimal-char-code
DIRECT, p, MAX PACKET, length
DIRECT, p, ETE, ON
DIRECT, p, ETE, OFF
Command Detailed Descriptions:
DIRECT
When used without any parameters the current port settings will be
displayed
Disables the connect string option. The MCC-545C will not expect a
connect string and will stay connected all the time.
DIRECT, p, CONNECT STRING, connect-text-string
Defines a text string of up to 19 characters that is output by the external
equipment to establish a connection with the MCC-545C DIRECT port
task. The MCC-545C will receive the connect string and output the
connect response string if one is defined.
DIRECT, p, CONNECT STRING, ANY
Defines that any unspecified text string will be acceptable to establish a
connection.
DIRECT, p, CONNECT RESPONSE, OFF
Disables the response string option.
DIRECT, p, CONNECT RESPONSE, response-text-string
Defines a text string to be output by the MCC-545C to the external
equipment to confirm a connection has been established.
DIRECT, p, PACKET TIMEOUT, decimal-timeout-ticks
Defines the timeout period in 1/16 second clock increments that marks
the end of a packet. After each character of the packet is received the
timer is reset. After the last character has been received and the
timeout passed, the characters received will be placed in a message and
queued for transmission.
DIRECT, p, PACKET TERMINATOR, OFF
Disables packet termination using a specified character code.
DIRECT, p, PACKET TERMINATOR, decimal-char-code
Enables packet termination when the given character code is received.
For example, using a carriage return to terminate each packet will
transmit each line of input as a separate message. The decimal code for
carriage return is 13. The decimal code for linefeed is 10.
Defines the maximum length of a message. As characters are received
they are filled into a buffer and when the maximum size is reached a
new message is transmitted. The longest message that can be used by
the MCC-545C is 3,500 characters.
DIRECT, p, ETE, ON
Defines the “reliable” type of message delivery. The source unit will
retain each transmitted message and periodically retry them until the
destination unit receives them and sends an end-to-endacknowledgement for each message. It is possible for messages to be
delivered out of sequence when a retry has occurred causing duplicate
messages. These duplicate messages will be filtered out.
DIRECT, p, ETE, OFF
Disables the “reliable” type of message delivery. The source unit will
not retain each transmitted message for retries. Each message will be
deleted as soon as transmitted. It will be the responsibility of any
receiving equipment to manage the message reliability. If any message
gets lost in the RF network, then all characters in that message will be
lost.
5.5.4 Defining Data Relays
The ambient noise conditions at a remote station site may sometimes be
excessive and a poor communication path to the Master Station will result
particularly if the remote station is operating in a meteor burst mode. To
overcome this problem, another MCC-545C may be placed in a nearby quiet
location and used as relay station between the MCC-545C at the noisy site
and its master station. When used as a relay, the MCC-545C will
concentrate the data reports it receives from one or more neighboring
remote sites and forwards the data to the Master Station.
When used in the relay mode, the MCC-545C must be defined as a Master
Station. The relay will then receive MCC-550C sensor data GROUP reports
(see MCC-550C Operations Manual), repackage them and forward them to
the Master Station. A relay can handle a total of sixteen GROUP reports.
These reports can be in any combination; i.e., four groups from each of
four Remote units, one group from each of sixteen Remote units or any
combination in between. Substitution tables must be established in both
the relay unit and also at the Master Station to manage the relay function.
When a designated GROUP report is received at the relay, it will substitute
its own ID and group number in the report as defined in its substitution
table and forward the data to a MCC-520B Master Station using the MCC550C RF format rather than the standard MCC-545C message format. When
the relayed data is received at the MCC-520B it reconstructs the original
data report based on its own substitution table and route the report as
required.
The following command is used to define the entries in the substitution
table for a relay unit:
SUBST,relay_id,relay_group,remote_id,remote_group
where:
relay_group =
remote_id =
relay_id =
remote_group
originating Remote unit
5.5.5 I/O Port PASSTHRU
The PASSTHRU command allows a bi-directional connection to be made
between the different I/O ports of the MCC-545C. This will allow the
operator to configure one port to be connected to another port in a direct
ASCII mode where any characters coming in on one port will go out on the
other port, and vise-versa. For example: the command PASSTHRU,1,2
allows characters entered on port 1 to go out port 2, and characters
received on port 2 will go out port 1. There can be from 0 to 2 different
pass-through connections defined at any time. All ports given in a passthrough connection must be assigned to some protocol and baud rate
before entering the PASSTHRU command. An error will be displayed if they
are not.
Data coming in from a passed-through port will not be passed to the
assigned protocol driver and will be sent out the “other” port of the
connection.
The connection can be turned off by entering PASSTHRU,OFF,n where “n”
is either port in the connection. In addition either port in a pass-through
connection can output the string PASSTHRU,OFF to close its own
connection. The first method can be used from the operator port to close a
connection of other ports. The second method is used by the operator port
if it is one of the ports in the pass-through connection.
If port 1 is assigned to a CR10X driver, and port 0 is the operator port, then
the command PASSTHRU,0,1 allows the operator port to be connected
directly to the CR10X. One can then use XTermW or PC208 to talk to the
CR10X via the operator port without re-connecting cables.
5.5.6 Internal Sensor Values
The new MCC-545C -03 and later radios have the capability to read a
number of internal sensor values. These include:
• Internal temperature of the MCC-545C unit
• Internal rechargeable battery level
• External battery levels (loaded and unloaded)
These sensor values can be read using the EVENT command – refer to
Section 4.6.8 for details on how to program the MCC-545C to read these
values.
5.5.7 Generic Data Logger
The MCC-545 family of RF Modems includes a set of device drivers for its
serial ports. These have been customized for various external devices,
depending on the device requirements. The SDATA command allows a
simple text-based interface to send data groups to the MCC-545C for
transmission to the master. Any customer who can configure their data
report to meet this format can interface their data logger with no change
in the MCC-545C software. From 1 to 16 groups can be input, and there can
be from 1 to 16 sensors per group. Each sensor data value is formatted into
a 16-bit binary value for transmission, then converted to engineering units
by the Data Center or Host software.
Some date loggers have a complex and non-configurable interface protocol,
and cannot meet any of the currently implemented protocols, but they can
output data reports on a serial port as if it were connected to a line
printer. The GENERIC data logger driver has been created for this type of
interface. Some things can be setup by user commands to configure the
report parsing, within a limited set of constraints, and allow the MCC-545C
to create SDATA type messages from the ASCII text reports.
The following sections describe what can be done to adapt the MCC-545C
to a variety of report formats.
Typical Report Formats
A typical report printed by a data logger has one line, or a set of lines for
each report. There are usually two types, single-line reports, and multipleline reports. An example of each type would be as shown below:
Note that the report ends with carriage return and linefeed characters, and
may or may not display a date and/or time. The data fields are usually
separated by blanks, and the data values may or may not contain a sign or
decimal point. The line is usually output by the data logger as the report is
placed into the devices' memory in real-time. There is no provision for
error checking, but if the serial port cable is wired correctly with shielding,
etc., it may be reliable enough.