User's Manual

545C Operations Manual

02/10/2012 Prerelease DCN 00001789-A

• Transmitting vehicle collision reports

• Transmitting canned message reports.

• Defining sensor data (SDATA) groups

• Transmitting sensor data (SDATA) reports

• Setting or clearing the MDP Status Bits

• Setting or clearing and testing 5 timers

• Testing GPS status as a discrete input

• Testing Network status as a discrete input

• Setting or clearing and testing counters

• Setting or clearing and testing 2 high-speed counters

• Outputting pulses and square waves (pulse modulation)

• Reading and counting pulse inputs

• Max, Min, Average or other real-time signal computations

The position, marker drop, collision and canned message reports created

conform to the FleetTrak standard. In addition other status bits can be set

or cleared individually. Up to 16 data report groups can be defined for

SDATA formatted data report generation.

The MCC-545C event monitor reads discrete and analog inputs and

evaluates them with respect to event definitions in the event table. It can

look for discrete input signals going persistently high or low, and for analog

signals persistently exceeding or under running thresholds.

5.6.2 Event Definition

An “event” occurs when some input signal or timer changes its state. You

can think of a state as being “on” or “off”, “1” or “0”, “true” or “false”.

When the state changes, an “action” can then be taken. Once the signal

has changed state and the action performed, it will not take further action

until the state changes again to prevent a continuous string of actions. For

example, if a switch is turned “on”, the lights come on and stay on. They

don’t continually go on,on,on… Once the switch is turned off, the lights

can go off, and then they are ready to be turned on again, etc.

There are three classes of events: Reset, Immediate and Scanned. Scanned

events subdivide into discrete I/O events and analog input events. These

are defined in the following paragraphs.