Johnson Controls 300 Series Manual page 62

62 Network Control Module 300 Series Technical Bulletin
If Port 4 has failed, see the Network Terminal Technical Bulletin
(LIT-636012) for further troubleshooting.
WNCSETUP Field Checks
One reason that an NCM appears not to function properly is that the
NCSETUP for Windows software version used to configure it is not
appropriate to the version of Metasys software loaded in the NCM.
An NCM300 requires Metasys Release 6.0 (or later) software. An
NCM350 requires Metasys Release 8.0 or later. NCSETUP
for Windows is contained within the Metasys Person-Machine
Interface (PMI) software. On the Help menu of NCSETUP for
Windows, click About for version and copyright information.
Failing to use corresponding WNCSETUP and Metasys software
versions may result in these symptoms:
• Files do not download from the configuring PC to the NCM.
• Files do not upload from the NCM to the PC.
• The NCM does not talk on the N1 LAN.
• The NCM runs out of acquired memory.
• The NCM continuously reboots or reboots on its own.
If these symptoms appear, rerun WNCSETUP after ensuring that the
correct Metasys release software (including its corresponding
WNCSETUP version) has been loaded onto the hard disk, and that no
other version of WNCSETUP is accessed. Refer to the NCSETUP for
Windows Technical Bulletin (LIT-6360251d).
Downloading NCMs across Ethernet/Ethernet to ARCNET
Network with a Router
NCMs with firmware prior to 8.02 flash ROM running on an Ethernet
or Ethernet to ARCNET network may experience download failures.
During download, NCM response messages are lost over the Ethernet.
The OWS concludes that the NCM is not receiving data, tries to
download two more times, then fails the download.
Workarounds include the following:
• If you have an Ethernet to ARCNET network, leave the archive
OWS on the ARCNET side of the network.
• Disconnect or segment your Ethernet nodes from the customer's
network (the load on the customer's network brings the problem to
the surface).