Scanning for local or remote nodes

When the Workbench is started, the Nodes list contains the recent nodes list. The Nodes list will be empty the first time the Workbench is started after it is installed. To connect to nodes and access the node's features, the Workbench must first scan for the node.

  • For local nodes, this is usually done using the node's IP address for nodes that are on the same LAN as the computer running the Workbench.
  • For remote nodes, this is done using the Workbench's TR50 connection to the IoT Portal, and then the IoT Portal's TR50 connection to the remote node.
  • The Node Scanner window can remain open up while scanning for nodes multiple times or while you do other work in the Workbench.

Scanning a node to access its resources

Each node's configuration settings and application definitions are contained in internal database files on the node. The Workbench uses a Scan function to locate the node in the network. The Workbench then uses a connect function to log on to the node using the user name and password supplied by the user of the Workbench.
When configuration settings or application definitions are changed, they are updated and stored in the internal database files on the node.
The Workbench does not have an online and offline mode concept or a concept of storing a node's settings and definitions in files on the computer that is running the Workbench.
The runtime products do have Backing up and Restoring a node's configuration and item definition Exporting a project or trigger features that are described in their sections.