Network Control Module 300 Series Technical Bulletin 73
Error/Condition
(Cont.)
Problem Solution
NCM300/350
periodically fails and
locks up during
global download in
the NC Direct mode.
Wrong cable configuration causing
problems with certain signals
between the modem and PC. The
requirements changed at Metasys
Release 8.0.
Use the appropriate OWS to NCM RS232
Port cables from the figures in the NCM
Cable Guidelines section of this document
rather than standard null modem cables.
Unable to
communicate to NCM
through Port 3.
The baud has changed. This can be
caused by NCM reset or operator
intervention.
Use NCSETUP for Windows via N1 to reset
the baud.
Metasys Release 9.0 contains an automatic
baud detection feature, which eliminates this
problem. This feature is enabled in the
Metasys.ini file as described in the Running
NCSETUP Direct Connect without Knowing
the Network Name section of the NCSETUP
for Windows Technical Bulletin
(LIT-6360251d).
Pressing Reload
button does not
reload code and data.
Situation can occur at Release 8.0 if
an Ethernet card is used as an N1
interface.
Disconnect battery and cycle power to
cause a Cold Start reset. Reconnect battery
when download is complete.
Unrecoverable NCM
resets
May be caused by problems in the
software application code.
Analyze the NCM error log for software error
messages.
May be caused by hardware
component failures, power supply
failures, solder joint, and/or
connection problems.
If all other corrections in this document have
failed, unit must be returned to the factory.
May be caused by noise or remote
NT or DT lines.
Add EOL resistors.
NCM fails after power
cycle and will not
come online.
NOVRAM failure, LED3 (DS5)
blinks, or NCSETUP Error 199
Replace SIMM, or use WNCSETUP to
update flash, or upgrade SIMM to flash.
Random NCM
ARCNET reboots,
NCM Error 3
Intermittent TC6245 ARCNET card Replace ARCNET card.
To Next Page
Loading...
Need help?
General
