Overview
Points are individual items that can be read or written from/to nodes. They can be registers, I/O values, or variables residing in field devices (nodes). Each Point is bound to a specific Tag in the Solution configuration.
On this page:
Configuration Workflow
This content is available in other page
The typical configuration workflow for the Device Module has the following sequence:
Device Module Configuration Workflow | ||
|---|---|---|
Action | Where | Comments |
Create Channels | Devices → Channels | Identify the required field devices and protocols the project requires, create channels accordingly. |
Create Nodes | Devices → Nodes | Identify the Network addresses and relevant information to all stations and devices that need connectivity. Learn more at Devices Nodes. |
Map Tags to Point addresses | Devices → Points | Optionally, you can Copy Tags from Excel/CSV from Excel or execute Import Wizards. Learn more at Device Points. |
Create or Customize AccessTypes | Devices → AccessTypes | Optionally, you can optimize the communication, grouping Points with similar requirements to the same AccessType. Learn more at AccessType. |
Adding and Editing Points
Data Points define specific values for each node that can be accessed using tags. The number of data points you can configure is related to both the ProductModel that is configured for the project and your software license.
We shouldn't use this configuration to present a list of steps. Fix
To configure data points:
Go to Devices → Points.
You can copy and paste tags from the Unified Namespace → Tags.
Enter or select information, as needed.
To add or remove a column (visualization only), right-click the column heading area and select or deselect columns.
Points Configuration Properties | |
|---|---|
Field/Column | Description |
TagName | Enter a tag name or click "..." to select a tag. You can also create a new tag. |
Node | Select the node for this data point. |
Address | Enter the register address which is based on the PLC and protocol for this data point and tag. |
DataType | Select the data type you want to use. Most protocols should use the native option. When native is used, the protocol will automatically handle the data conversion. Selecting a different data type overrides the defaults. Some options may not be applicable to the selected node. Make sure you know the applicable data types. |
Modifiers | If the PLC uses a different byte order, select the options you want. You can change the position bit, byte, Word, or Dword of the data that is communicated. |
AccessType | Select the access type for this data point. You can define and configure the access types. See Access Types below. |
Scaling | If you want to manipulate the tag value, select the options you want. When the data is read in the Equation option:
|
| Label | A text that represents a label to the point |
Dynamic Configuration Points > Address
Convert this content to a new section and improve the description and images.
The example below shows how to configure a dynamic Address using a MQTT telegram, for example:
/topic/gateway/data:
/topic/gatewayX/data
/topic/gatewayY/data
/topic/gatewayZ/data:
In other words: /topic/@Tag.gateway/data:
You can create a standard point in Devices>Points, with Tag name, node, and Address
You can use the following code to change the Address for the desired point:
string error;
DataTable dt_DevicePoints = TK.ProjectDB.GetDataTable("EditDevicesPoints", "TagName='Tag.Tag01.Velocidade'");
DataRow[] rows = new DataRow[1];
rows[0] = dt_DevicePoints.Rows[0];
@Info.Trace(rows[0]["Address"].ToString());
rows[0]["Address"] = "Group01/"+@Tag.Gateway+"/Device01";
@Info.Trace(rows[0]["Address"].ToString());
rows[0].AcceptChanges();
TK.ProjectDB.UpdateDataRows("EditDevicesPoints", rows, out error);
if (String.IsNullOrEmpty(error) == false)
{
@Info.Trace("Error changing tag address: " + error);
}
else
{
@Info.Trace("Applying Devices Changes - begin");
TK.ProjectDB.ApplyProjectChanges();
@Info.Trace("OK!");
}
In the second line when using the code DataTable dt_DevicePoints = TK.ProjectDB.GetDataTable("EditDevicesPoints", "TagName='Tag.Tag01.Velocity'"); the first parameter refers to the table you want to obtain, in this case, it would be the Points, in the second parameter it would be the TagName column and the tag configured in Points, in this example the tag: Tag.Tag01.Velocidade.
In the line where the code rows[0]["Address"] = "Group01/"+@Tag.Gateway+"/Device01"; is where you choose the new desired address, in this case @Tag.Gateway which is a string type tag will receive different names and make this substitution.
To internally update this Address you need the following code: TK.ProjectDB.UpdateDataRows("EditDevicesPoints", rows, out error); If no error occurs in the update, you can apply the change to the project using the code: TK.ProjectDB.ApplyProjectChanges(); from this moment on your Address is configured with the new value previously entered.
Importing PLC Addresses
The content exist in another page. What's the best page for this content?
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.
Tutorial - 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
The 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: