Download Model 3012 Mobile Data Terminal

Model 3012 Service Manual
Functional Description
The Pyramid Communications Model 3012 is a microprocessor controlled MSK status reporter capable of
signalling the dispatcher with 10 individual status indications plus emergency. By pressing one of the 10 status keys
on the front panel, the vehicle number, console routing information and new status are automatically sent via two
way radio to the dispatch console. The base equipment will automatically respond with the proper acknowledgment
and the mobile unit will update the display to the current status. The model 3012 will monitor the channel for activity
or properly acquire a voice channel (if installed on a trunking system) before transmitting its message. The model
3012 will also automatically retry its message if the acknowledgment from the base is not received within 20 seconds.
There are multiple pseudo-random delays incorporated in order to prevent multiple units from transmitting at the
same time. The number of retries and PTT delay are PC programmable.
The base equipment may also selectively call a mobile or group of mobiles, interrogate a mobile for its current
status, honk a vehicle horn (or group of vehicles), or reassign a mobile to a different console all without the
intervention of the mobile user.
The model 3012 also has GPS Automatic Vehicle Location and extensive text messaging capabilities. Refer
to pages 5 and 6 for a complete description.
The model 3012 is completely programmable for all operating parameters via IBM compatible PC; see page
13 for programming details.
The model 3012 also has a built in self test for diagnostics and alignment which can be accessed through the
front panel keyboard without any tools. All internal adjustments are accessible by removing the right hand side
panel. All alignment and testing can be done in the vehicle with minimum effort.
Status Reporting:
When the mobile user presses one of the 9 status buttons, the display will blink the new status request and display
"Sending..." in the upper portion of the screen. The model 3012 will monitor the channel for activity and will hold
off sending its message until the channel is clear. While waiting to transmit, the display will continue to show the
"Sending..." status until the channel is clear for transmission, or the unit times out. If unable to transmit within 60
seconds, the user will get an error indication (3 beeps) and the display will return to the previous current status.
If the channel is clear for transmission of the status message, the model 3012 will key the radio for the PTT delay
time (conventional operation) then send the message. On trunking systems, the model 3012 will key the radio while
monitor the radio’s transmitter for an on-air condition. If it does not see the radio transmit at all (system is busy
for instance) it will retry every 5 seconds until successful or time out (60 seconds). When it detects that the radio
is transmitting, it will continue to monitor the on-air line until the transmitter has remained on the air long enough
to indicate it has acquired a voice channel. After successful acquisition of a voice channel, it will send its status
request.
After a status request is sent, it will monitor the channel for the proper acknowledgment. If it does not receive
the ack message from the base within 20 seconds, it will repeat the above sequence until the number of retries expires,
or it is successful. If successful, the new status will revert from blinking to normal text and the previous status will
change to inverse text. If unsuccessful, the display will remain at the previous status, and the user will hear the 3
error beeps.
The model 3012 will save the last current status in E2PROM, so the unit will always come on in the last status
that was selected before power off.
If the user presses the Dispatch Request key (0), the model 3012 will send out the proper message sequence as
above, but the base is not required to automatically respond, so the display will revert to the previous status as soon
as the unit successfully transmits the request. If unable to send the request (60 second time out) the user will get
the 3 error beeps as above.
Page 3