Successfully Detected Nodes

When the Configuration Editor goes online and detects nodes, successfully detected nodes look the same as they do when offline, i.e. their name is displayed in black text with a white background.

The following picture shows a Unidrive SP with an SM-Applications option in slot 1 which have both been successfully detected when going online on a CT-RTU network. Note the online status shown in the status bar at the bottom of the Configuration Editor.

New Node

When the Configuration Editor goes online and detects nodes, nodes which were not previously present in the project are shown with a yellow background.

The following picture shows a Unidrive SP which has been successfully detected but a new SM-Applications option has been detected in slot 1. Note the online status shown in the status bar at the bottom of the Configuration Editor.

To work with the newly detected node, e.g. to view or modify its user program or write a program for downloading to the node, the node must be added into the project. See Adding Detected Nodes for more information.

Nodes Not Found

When the Configuration Editor goes online and detects nodes, any nodes which are present in the currently open project but which cannot be found when searching online are shown with a red background.

The following picture shows a Unidrive SP and SM-Application option in slot 1 which have been successfully detected. However, the option in slot 2 has not been detected. Note the online status shown in the status bar at the bottom of the Configuration Editor.

Messages indicating which nodes cannot be found are output to the Log pane of the Output Window as shown in the above picture. A further example is shown below.

In this example the SM-Applications in slot 1 has not been found since although an SM-Applications in slot 1 was found when going online, it cannot be matched to the one in the project because it has a different CTNet node address.

If a node is not detected there are a number of ways to correct the differences between the project and the real network of drives.

1. If no nodes are found, check that the PC is on the correct network and has the correct baud rate settings etc.

2. Delete the node from the project.

3. Amend the properties of the node to match that of the actual node. For example in the second example above the node properties could be changed so that the SM-Applications CTNet node address matches that of the actual option.

4. Ensure that the actual drive is powered on and has the correct node address (and in the case of SM-Applications, the correct CTNet network/ token ring ID).

5. Ignore the differences and continue to work with the nodes which have been correctly detected.