Johnson Controls 300 Series Manual page 59

Network Control Module 300 Series Technical Bulletin
3. Test the download procedure with a known, good cable
(particularly check the N1 connections) and a known, good
ARCNET card.
4. Inspect the error logs (see Step 4, in previous section).
5. There may be software issues preventing the download. Here are
some things to consider:
• If the database is one that previously uploaded, but does not
now download, an UNDDL of the database provides a small
amount of cross-checking and can determine if any of the
object databases (but not most feature databases) is flawed.
UNDDL also determines if a database even exists for the NCM
(for example, the user uploaded to a different OWS and the
current one does not have a database). If UNDDL finds an
error, edit the .UND file; renaming and recompiling it may fix
the database.
• If the database was modified after an upload (DDL incremental
or Graphic Programming Language [GPL]), a heavily loaded
NCM may fail due to lack of memory.
• If DDL or GPL was aborted (CNTRL C, PC reboot) during
execution, the database is corrupted and a recompile is
necessary to create a good database.
• A DDL recompile necessitates retranslating of GPL processes
and a recompile of JC-BASIC.
• If using CS objects, the correct model files must exist on the
OWS.
Network-Related Field Checks
Follow these steps for network-related field checks:
1. After confirming the proper node address, test the NCM's ability
to communicate over the N1 LAN. Transmit (XMIT) and Receive
(RECV) LEDs should respond to activity. (Also see
N1 End-of-Line Termination Notes in the Related Commissioning
Problems section.)
2. Next, for a Standard Functionality NCM, verify that the device is
being polled on the N2 Bus. This is evident if the XMIT LED
lights, which indicates that the NCM is sending a poll.
Notes: The S2 Migration and JC/85 Gateway networks connect to a
Metasys system via the RS-232 port. For those networks, see the field
checks in the Troubleshooting section.
59