Hardware Reference Manual
MCU500 Mobile Locator/Control Unit
16
Revision 1.01
100-00191
socket are nearest the middle of the PCB.
e.
Check the settings of jumper JP5 for the correct size/type of device.
g.
Re-assemble the case.
5.3 Trouble shooting
The following notes are provided to aid trouble shooting and should be read in
conjunction with the software/firmware documentation.
5.3.1 No response from the MCU500
Is the PWR (power on) LED lit? If not check that:
a)
that the power cable is connected
b)
that the power supply is present (eg. fuse not blown)
c)
that the ignition sense line goes on (mor than 3V) to power up the unit
If the PWR LED is lit check that:
d)
the cable between the MCU500 and radio/transceiver device is attached
5.3.2 Unit unable to send location updates
Check that the GPS antenna is plugged in. Check that after approximately 20
seconds from turning the power on that the NAV (Naviating) LED flashes on/off
once per second.
If the NAV light remains off then there is a problem with the GPS antenna cable
or the antenna itself - replace and re-test.
If the unit has been unused for an extended period (several weeks) the almanac
data may not be valid which will cause the unit to wait to download a new version
of the system almanac. Almanac download takes approximately 12.5-15 minutes
to achieve given good coverage (view to the sky). This situation may occur when
first installing MCU500 units into vehicles.
5.3.3 Unit not correctly programmed
The MCU500 stores user configuration (its personality) in non-volatile memory.
The configuration must be valid for the unit to function correctly. If, at power up,
the unit’s configuration is found to be incorrect (ie. missing or corrupt) the SVC
led flashes indicating that the unit requires programming.