Qel M-CONTROLLER II - 10 Troubleshooting Hints

M-Controller II System Operation Manual - 36 -
84350-201-001 Rev C
10 Troubleshooting Hints
M-Controller has advanced features and functions. Before assuming that unexpected behavior is caused by
a system defect or breakdown, the operator should use this manual to become thoroughly familiar with
M-Controller operation. This troubleshooting guide is intended as an aid in identifying the cause of
unexpected behavior and determining whether the behavior is due to normal operation or an internal or
external problem.
Identify the symptom or unexpected behavior you are observing from the SYMPTOMS listed in the table. A
PROBABLE CAUSE is provided, and a suggested SOLUTION is proposed including references to manual
sections that provide information that may be of assistance.
SYMPTOMS PROBABLE CAUSE SUGGESTED SOLUTION
LCD Display does not come on
 No power supply
 LCD has problem
 Program has crashed
 Check power / ground connections
 Change LCD
 Reprogram
M-View reports “M-Controller is
offline”
 M-Controller is not
turned on
 M-Controller is working
in Menu Mode.
 USB driver is
recognized
 Turn on M-Controller
 Exit Menu mode to Monitoring
mode
 Check M-Controller is connected
properly. Remove USB cable and
plug it back again
M-Controller reports “Vote no
Sensor!” or “AV no Sensor!”
 No sensor was assigned
to the output (relay or
analog output)
 Assign sensor to the output
M-Controller reports “Sensor
Offline” or “Relay Offline”
 Comm setting is wrong
 Connection is wrong
 Remote Device is in
Fault
 End-of-line matching
resistors are not
properly set.
 Check if the remote sensor baud
rate is 4800 bps
 Check connection between M-
Controller and Digital Sensor and
M-Relay. Make sure all have
power on and no shorts or opens in
wiring. Be certain that polarity for
RS-485 connections is correct. A-
A and B-B
 Examine remote devices
 Review end-of-line resistor
settings
RS-485 Sensor Port
or Modbus Port
RX/TX LED constantly ON
 RS-485 bus connection
has a problem
 RS-485 driver chip is
damaged
 Disconnect the cable to isolate the
problem
 Replace RS-485 driver chip