Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Nodes are the devices or PLCs on the network with which you communicate. They can be both  individual devices or groups of devices, and each Each device connected to the system is mapped to a Device Node.  Each node contains one or more Point adressesPoints.  This This page explains how to create nodes and also how to import them from various sources.

On this page:

Table of Contents
maxLevel3
stylenone


Configuring Device

Creating

Nodes

To create a new node, follow these steps:

  1. Access Devices → Nodes.
  2. Click the plus icon to add a new node.
  3. Select a channel to associate the node, and fill in its name and description.
  4. Click Ok.

Image Modified

After completing the above steps, the Node is created. 

You can configure and existing node by double-clicking The node is now created. To configure it, in the list double click the property you want to edit on the row corresponding to the channel you want to modify. 

Info

If the column Remote settings column is not visible on the grid, enable it by right-clicking the grid header, and selecting it from the list.

corresponding row.

DeviceNode Table Columns

The following table describes each available property you can configure when editing a nodeNode:

Column

Description

Name

Enter a name for the node. The system lets you know if the name is not valid.

Name of the Node.

Channel

The Device Channel for this Node

Channel

Select the channel for this node

. For more information about the configuration for common protocols, click Help at the top of the tab.

Primary Station

PrimaryStation

Enter the

The information required to access the primary

node

Node, based on the protocol selected.

Backup Station

BackupStation

The required information

Enter the information required, based on the protocol,

to access the backup

node

Node. When the

backupstation

backup station is defined, and a communication failure occurs on the primary station, the system automatically attempts to establish communication with the backup station.

Sync Date

SyncDate

Date

The date that the import was done

(read only field)

. 

Sync Station

SyncStation

Information about the station where the import was done Station IP, Port and Slot

(read only field)

.

Sync Settings

SyncSettings

Information about the settings used by the system to import the file

(read only field)

. 

Description

Enter a description

Description for this

node

Node.



Importing Nodes from PLC Addresses

When creating the communication nodes and point addresses, there is no need to retype those addresses if they are already defined in some other data source. Currently, Tatsoft supports the following methods to automatically import remote data configuration:

  • You can copy and paste the contents of a table from Excel. The tables can have different columns or order, as long you include the TITLE of the column in the copy and paste operations. The system will put the data in the expected columns, even if the order is different in the source and target tables.

  • You can import the data from CSV files.

  • For Rockwell ControlLogix devices, you can import from L5k definition files.

  • You can use various Import Wizards from many data sources

  • For OSIsoft® PI database, there is a FactoryStudio version to share definitions.

  • A programming API is available that can populate the tables from code, even from runtime execution when it is necessary.

If your PLC or Field Device has an open database of file with the available addresses, and you would like to have a tied integration with that configuration and addresses, contact us, as we have programming interfaces to allow that just like we did with the OPC datasources.

For more information, visit Import Tag Wizards.

Importing from an OPC Server

Importing data from an OPC server allows for efficient and streamlined integration with industrial automation systems. By creating an OPC communication node and selecting the "Import" option, FactoryStudio automatically creates tags and communication points based on the information available from the OPC server. This functionality simplifies the configuration and maintenance of the project, optimizing the data integration process. To learn more about importing data from an OPC server, please visit Import Tag Wizards - OPC Server.

Importing from an OPCXmIDA

The Importing from OPCXmIDA tutorial guides you through the process of configuring a Kepware server and a client, establishing an efficient OPC connection between the two systems. By following the steps outlined in the tutorial, you can create and configure devices, tags, and OPCxmIDA communication nodes in both Kepware and our software. Additionally, the tutorial covers how to change the visibility property of the tags to ensure proper communication between the OPC server and client. For detailed, step-by-step information on importing from OPCXmIDA, please visit Tutorial - Importing from an OPCXmIDA

Importing from Excel

Additionally, you can simplify the creation of communication Nodes with various methods for automatic data configuration import.

Read more about Importing PLC AddressesThe import and export of tags and PLC addresses is streamlined due to its integration with Excel, as the software extensively utilizes tables in various features. By creating a table in Excel with the required columns, such as TagName, Type, and Address, you can copy and paste the data directly into platform. The software ensures the accurate assignment of data to the corresponding columns, even if the column order is different. After the first import, the system stores your settings, making it easy to synchronize previously imported addresses and new addresses. For more detailed information on the import and export process of tags, visit Import Tag Wizards -Importing from Excel.


In this section:

Page Tree
root@parent
spacesV10

...