To monitor the communication status of each individual node in an IGSS installation, we recommend that you create a node status object. 7T recommends that you create a separate diagram showing your PLC network. You will thus get a quick overview of the communication status for all PLCs.
If the node status alarm occurs, the corresponding PLC icon will blink with the alarm color and the communication alarm will occur as an error code in the Value field of the Alarm module.
Example: Node status object for the Generic TCP/IP driver (ID 34)
In the procedure below we define a node status object to monitor a PLC (node no. 0) which uses the Generic TCP/IP driver.
We use a rectangular field which is shown on top of the PLC icon. You can, however, freely choose any descriptor (graphical display) for a node status object.
Node.[Station ID].[Driver ID].[Node number]
where:
Node
must always be the first part of the object name.[Station
ID] is the ID for the IGSS station. A server or an ordinary
operator station (without PLC connections) will always get ID 0. However,
each operator station running a distributed driver will be allocated a
unique number starting with ID 1.[Driver
ID] is the unique ID of the PLC driver used. Find
the driver ID here (Web link). or alternatively start the System Configuration program and find the
ID in the dialog box where you add a new driver.Node
number] is the node number you have assigned to the PLC
in System ConfigurationNode.0.34.0
will monitor node number 0 defined for the Generic TCP/IP Driver (Driver
ID = 34) on a server or ordinary operator station (Station ID = 0)."Communication error on node 0";
when finished click OK.