This document provides instructions for checking the operating status of an SCU PLC using the SCU. It outlines 4 steps: 1) opening CoDeSys project on the SCU, 2) locating the nodesearch variable, 3) initiating a nodesearch, and 4) interpreting the results of the nodesearch to determine status of nodes found on CAN1. The nodesearch returns status codes for each node to indicate if a node was found and matches its expected ID. It also identifies the first found node that is not configured and not optional, as well as the first missing node.
This document provides instructions for checking the operating status of an SCU PLC using the SCU. It outlines 4 steps: 1) opening CoDeSys project on the SCU, 2) locating the nodesearch variable, 3) initiating a nodesearch, and 4) interpreting the results of the nodesearch to determine status of nodes found on CAN1. The nodesearch returns status codes for each node to indicate if a node was found and matches its expected ID. It also identifies the first found node that is not configured and not optional, as well as the first missing node.
This document provides instructions for checking the operating status of an SCU PLC using the SCU. It outlines 4 steps: 1) opening CoDeSys project on the SCU, 2) locating the nodesearch variable, 3) initiating a nodesearch, and 4) interpreting the results of the nodesearch to determine status of nodes found on CAN1. The nodesearch returns status codes for each node to indicate if a node was found and matches its expected ID. It also identifies the first found node that is not configured and not optional, as well as the first missing node.
b) In the folder “Global Variables” there is an object called “Global_status” where the nodesearch variable is located 3) Initiate the nodesearch
a) Locate the variable g_ManualStartNodeSearch and set
it to TRUE b) The variable g_NodeSearchStatus turns to ”Started” and when g_NodeSearchStatus turns to ”Done” (after approximately 20 seconds) the node search is done c) See the next slide for how to interpret the result of the nodesearch 4) Result From the Nodesearch
a) In the same object there is a structure called
NodesFound, this contains all nodes found on CAN1 with Status as below. Status (Value) Status Meaning 0 No node found 1 Node is found but not expected to be on the network with this nodeID 2 Node is missing 3 Node is found and has correct nodeID b) There is also three variables listed for your convienience: Variable Status Meaning g_First_Found_ID NodeID of the first found node that is not configured and not optional g_First_Found_Type Devicetype of the above node g_First_Missing_ID NodeID of the first missing node