Hanover DG3 - 4. Troubleshooting; 4.1 Overview; 4.1.1 No display or backlight on controller; 4.1.2 No communication or required information not displayed on signs

DG3 Controller – Installation and Operation
Manual
540846-3 page 44 of 64 25/09/2015
Troubleshooting
Overview
This section lists the more common queries that occur with the DG3 controller. The controller is not
intended for disassembly by the user. Hanover should be consulted (please refer to section 4.3 Hanover
Technical Support) if a solution cannot be found by means of altering settings manually or via the Helen
software as described below.
Section
Issue
4.1.1
No display or backlight on controller
4.1.2
No communication or required information not displayed on signs
4.1.3
List will not load into DG3 controller
4.1.4
DG3 loads list correctly but shows 'Bad Destination or Bad Route'
4.1.5
Sign test function
4.1.6
Information code on controller screen shows '??'
4.1.7
Advert code on controller screen shows '??'
4.1.8
On-screen response erratic when using keypad
4.1.9
Faults not listed here
No display or backlight on controller
No.
Description
Refer to section
1
Check that pins 1 and 10 on the mini fit connector are wired
correctly by making sure the pins are pushed in securely into
the connector and that the required voltage is present
Appendix A: 18-way mini fit
connector
No communication or required information not displayed on signs
No.
Description
Refer to section
1
Check that the comms are wired correctly (pin 11 = red (+)
and pin 2 = black (-)) by making sure the pins are pushed in
securely into the connector
Appendix A: 18-way mini fit
connector
2
Check all other cables and connections
3
Run the signs test to check that power and communications
are reaching each sign.
When DG3 shows 'Testing…' as shown, a test pattern should
be visible on the signs:
 If visible, the destination list loaded is possibly not
compatible with the sign system on the vehicle. Check that
the Helen database file has been configured correctly
 If not visible, then there is probably a hardware /
communications problem
3.5.2 Running the signs test
4.1.5 Sign test function
4
A sign status check can also be run
3.5.1 Status options