Check Orientation is correct
No Picture
Check physical connections. Broken or incorrectly configured video cables, damages plugs and faulty transmission
equipment will prevent pictures being displayed.
Is correct coax output in use. The standard cable has two coax conductors, labelled 1 and 2. No picture is present on
Coax No.2 for single camera models, this is used only on two-camera types. Only Coax No.1 should be connected on single
camera models.
Thermal camera switching
Thermal imager models can switch images between the two coax outputs, both showing at all times. If one output is missing
a picture, check if switching-over the cameras results in a change. The camera switching is operated by preset override Call
Preset No.204 (or No.7 if overrides in default state – Refer Appendix 1).
No telemetry/control
Correct protocol set at both ends. Check that the controller and PTZ unit are both set to use the same command protocol.
This is shown on the start-up screen when unit is re-powered. (e.g. Protocol: PelcoD 9600 8N1 f
Check correct Address/ID. Confirm camera is at expected address value. This is shown on the start-up screen when unit is
re-powered. (e.g. Cam: 001s)
Check Correct Baud Check that the controller and PTZ unit are both set to use the same Baud rate. This is shown on the
start-up screen when unit is re-powered. (e.g. 9600)
Ensure unit rebooted after Communications changed. The PTZ unit must be rebooted (or power Off/On) for these
changes to take effect.
Wire orientation (Data-A/B) The RS-485 telemetry wires are the Blue/Yellow or Blue/Green (depending on cable version)
twisted-pair conductors in the multicore cable.
Check and test that the correct wires are to the correct controller terminals. ( Not all equipment manufacturers use the same
A/B or +/- designation).
No Preset- Override Functions
Does Preset 2 recall to a position. Record a position in to Preset Position 2. Does Recall Preset Position 2 moving to a
location when instigated? This indicates preset overrides have been moved to a non-default value.(Refer Appendix 1). Try
Recall Preset Position 199 (if controller allows this) .
Check new value in controller range. If the preset functions have been moved to new positions, check that the new values
are within the range of the controller.
Try all functions Menu, Wipe, Mono functions should all be called in case the symptom is specific to particular function(s) If
the controller allows use the fixed range preset calls (199-210) (refer operator guide)
Wiper not stopping.
Check for latched controller. Check controller does not send repeated wiper instructions. Some systems latch-on their
wiper controls resulting in repeated calls to the camera to start wiper actions.
2) Confirm cycle ends. Confirm that WIPE caption appears and clears from screen. This indicates that the cycle intends to
stop and is not receiving repeated instructions.
Wiper not starting.
Check wiper preset. If wiper action is being commanded with a Preset Override call – check that the Menu Preset is as
expected. Wiper action is two values higher (e.g. Menu=2, Wiper=4).
Check command is received. Confirm that the instruction to start the wiper action has been received and processed. The
WIPE caption will be displayed as the software starts the wiper's sequence. If no caption shows then the action has not been
received and recognised.
Wiper boss depressed. Check that the wiper arm has not been pushed inwards in to the camera face-plate. If pressed
inwards the boss can cause the mechanism to jam, stopping the wipe action and resulting in motor failure. Pull the wiper arm
assembly forwards (hook finger under arm beside boss) to ease it away from the faceplate.