Page History

Purpose Key Concepts

The Device Module facilitates seamless communication and data exchange with various field devices and industrial protocols, simplifying system architecture and enhancing connectivity. The configuration of the Devices module is performed on the sections: Protocols, Channels, Nodes, Points, and AccessType.

Protocols

Protocols are the rules governing the communication between devices. FactoryStudio supports a variety of communication protocols, both native and OPC-based. The selection of Protocols to use in your specific Project is on the Project Explorer, at Devices → Protocols.

Channels

The Device Module uses Channels to establish connections with field devices. Each channel is defined by a specific protocol driver and connection type, such as RS-232 or TCP/IP. Channels allow the module to access multiple devices (such as PLCs) using the defined protocol and interface. The configuration of Channels is on the Project Explorer, at Devices → Channels.

Nodes

Each device connected to the system through channels is called a Node. Nodes can be individual devices or groups of devices. Each node contains one or more Points. The configuration of Nodes is on the Project Explorer, at Devices → Nodes.

Points

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 Project configuration.

AccessType

Each Point is associated with an AccessType, which defines the rules for reading and writing values for that Point, such as the polling rate, whether a read is performed on startup, and whether you write values to that Point. The AccessType allows users to configure how clients can access data points in the system.

How the Device Module Operates

The typical configuration workflow for the Device Module has the following sequence:

Managing Channels and Nodes

Channels are responsible for managing communication protocols and drivers, while Nodes handle multiple threads pointing to the configured Channels. Understanding the relationship between Channels and Nodes is essential for efficient data exchange.

• Channels: Execute processes based on communication protocols and drivers, configuring the required protocol or driver for a specific device.
• Nodes: Perform multiple threads pointing to the Channels, ensuring efficient data exchange and minimizing latency.

Channels are created and configured to handle specific communication protocols and drivers. Nodes, in turn, manage multiple threads pointing to these Channels. This multi-threaded approach ensures efficient data exchange and reduces latency, allowing the system to scale and handle numerous devices simultaneously.

To create channels:

• Go to Edit → Devices → Channels.
• Click Create New.
• The Create New Channel window displays.
• Enter or select information, as needed.
• Click OK. The channel is added as a new row in the table

To edit device channels:

• Go to Edit → Devices → Channels.
• To add or remove a column, right-click the column heading area and select or deselect columns.
• Edit the fields on the row corresponding to the channel you want to modify.

Creating Nodes

Nodes are the devices or PLCs on the network that you communicate with. You can enter the settings for your nodes as usual through the Engineering Workspace. You can also import settings from an OPC server or from another data source. See "Importing PLC Addresses" below.

To configure nodes:

• Go to Edit → Devices → Nodes.

• Enter or select information, as needed.

• To add or remove a column, right-click the column heading area and select or deselect columns.

Organizing the Points with AcessTypes

Points are groups that point to Nodes and are responsible for transferring information between configured devices and FactoryStudio. AccessTypes are used to define the specific methods for reading and writing data point values at specific moments using polling. The number of data points you can configure is related to both the ProductModel that is configured for the project and your software license. This approach allows for optimized data exchange and minimizes latency.

• Points: Groups pointing to Nodes, responsible for transferring information between configured devices and FactoryStudio.
• AccessTypes: Define specific methods for reading and writing data point values at specific moments using polling.

To configure data points:

• Go to Devices → Points.

• You can copy and paste tags from the Tag → Objects.

• Enter or select information, as needed.

• To add or remove a column, right-click the column heading area and select or deselect columns.

  
  

Access Types Configuration

Access types define the specific methods for reading and writing the values of each data point. This could be the polling rate, whether or not a read is performed on startup, and whether or not unsolicited input is accepted. FactoryStudio comes with a few predefined access types that you can use, or you can create your own.

To configure access types:

• Go to Devices → AccessTypes.

• Do one of the following:

• To edit an existing access type, double-click a field.

• To create a new access type, click Create New.

• Enter or select information, as needed.

Handling Read and Write events

In a SCADA system, handling read and write events is crucial for the efficient exchange of data between the HMI, PLCs, and other devices. FactoryStudio facilitates these events by allowing users to configure access types, which define the specific methods for reading and writing the values of each data point. The access types can be configured to determine the polling rate, specify whether a read is performed on startup, and decide whether unsolicited input is accepted.

Configuring the Device Module

The Device Module in FactoryStudio plays a central role in managing communication between the HMI and devices in an industrial automation system. To ensure seamless integration and optimal performance, it is essential to properly configure the Device Module. This includes selecting the appropriate communication protocol, creating and managing device channels, and defining device nodes and points.

Communication Protocol Selection

FactoryStudio supports a wide range of communication protocols to facilitate interaction between the HMI and various industrial devices. To select the appropriate protocol for your system, consider factors such as compatibility with the devices in your network, data transfer speed, reliability, and security requirements. Once you have determined the most suitable protocol, configure it within the Device Module to establish communication between the HMI and devices.

Protocol Comparison: Native vs OPC

What are the benefits of supplying native protocols interfaces to PLCs, instead of just use OPC client and rely on external OPC server to get the date?

Some PLCs are using OPC UA as their native built-in protocol, certainly this question does apply to them, but to other equipments using proprietary protocols. 

There are many scenarios when the native driver is more beneficial. Let us explore some of them:

Higher Performance

Instead of a direct connection, invariably adding one more application in the middle cause additional lag time. Further, the AccessTypes and the ability of parles execution (multi-threading) available in the Device Module allows optimized configuration not available in most OPC servers.

Cost Reduction

Most of the native drivers are included at no charge. The exceptions when there is a cost, it is typically quite smaller than the OPC server cost.

The OPC server still needs to use the Native Protocol Addresses

One misleading argument to use OPC is to hide the PLC address from the configuration. The reason it is misleading is that you need to use the native PLC address to setup the configuration of the OPC server anyway; you just duplicated the work load.  

The exception here is if the OPC Server is already installed and serving multiple applications. In this case, the connection using the OPC Client to the centralized OPC server is recommended.

Another good option is to leverage the OPC Server included in the Module device for the Edge application. In this case, the project connects with the field device with the native protocol, still enabling its OPC Server functionality, so other applications can use the built OPC Server in the FrameworX to access the data. 

Easier Field Maintenance and Deployment 

As explained on the previous item, if the OPC Server was not in its place, adding one more "middle-man" is just stressing the deployment and maintenance procedures.

Improved technical support  

Two points for potential failure or misconfigurations, and two independent suppliers, typically do not compare with a single environment and centralized support.

Available Communication drivers

Creating and Managing Device Channels

Device channels in FactoryStudio are the pathways for communication between the HMI and the devices in the system. To create and manage channels, follow these steps:

To create channels:

• Go to Edit → Devices → Channels.

• Click Create New.

• The Create New Channel window displays.

• Enter or select information, as needed.

• Click OK. The channel is added as a new row in the table

To edit device channels:

• Go to Edit → Devices → Channels.

• To add or remove a column, right-click the column heading area and select or deselect columns.

• Edit the fields on the row corresponding to the channel you want to modify.

By properly configuring the Device Module, selecting the right communication protocol, and effectively managing device channels, you can ensure a robust and efficient industrial automation system using FactoryStudio as your HMI/SCADA solution.

Defining Device Nodes

Creating Nodes

Nodes are the devices or PLCs on the network that you communicate with. You can enter the settings for your nodes as usual through the Engineering Workspace. You can also import settings from an OPC server or from another data source. 

To configure nodes:

• Go to Edit → Devices → Nodes.

• Enter or select information, as needed.

• To add or remove a column, right-click the column heading area and select or deselect columns.

Adding and Editing Device Points

Device points define specific values for each node that can be accessed using tags. Configuring data points is crucial for monitoring and controlling various aspects of the industrial automation system. The number of data points you can configure is related to both the ProductModel that is configured for the project and your software license. To add and edit device points, follow these steps:

To configure data points:

• Go to Devices → Points.

• You can copy and paste tags from the Tag → Objects.

• Enter or select information, as needed.

• To add or remove a column, right-click the column heading area and select or deselect columns.

Importing PLC addresses in FactoryStudio enables efficient integration of devices and communication points, using sources such as Excel, CSV files, L5k files, and other options.

Customizing the Pre-defined AccessTypes

FactoryStudio comes with several pre-defined access types that define the specific methods for reading and writing the values of each data point. To further optimize data exchange, users can customize these access types as needed. To customize pre-defined access types:

To configure access types:

• Go to Devices → AccessTypes.

• Do one of the following:

• To edit an existing access type, double-click a field.

• To create a new access type, click Create New.

• Enter or select information, as needed.

Device Configuration Tutorial

The Device Configuration Tutorial provides a detailed guide to configuring the Modbus and OPC interfaces, along with the essential concepts that apply to all communication drivers. This tutorial demonstrates how to define multiple protocol interfaces using the abstraction layers, such as Channels and Nodes, provided by the FactoryStudio. You will learn the differences in syntax for the STATION and ADDRESS fields when using various protocols, as well as the configuration and testing procedures that remain consistent across all communication interfaces.

The tutorial includes an overview of device configuration features in FactoryStudio, which enable users to configure and manage industrial automation devices such as PLCs, HMIs, sensors, actuators, and others. It offers a user-friendly graphical interface for adding, removing, and configuring these devices in an automation project. You will also explore how to configure communication parameters and tags for each device, ensuring reliable and accurate communication between devices and the automation control system.

The page covers various topics such as Modbus Master, Modbus with multi-serial interfaces, Modbus on TCP/IP networks, OPC Client, importing settings from an OPC Server, importing PLC addresses and external tag definitions, and using diagnostic tools like Property Watch, Trace Window, and Module Information. This comprehensive guide will help you to effectively configure devices in your industrial automation projects, resulting in safe and efficient operations.

Working with the Device Module

The Device Module in FactoryStudio is an essential component that enables seamless communication between the HMI and various devices in the industrial automation system, such as PLCs and other equipment. To maximize the potential of this module, it is crucial to understand its features and capabilities in-depth.

Runtime Execution

During runtime execution, the Device Module manages all aspects of communication between the HMI and the devices in the industrial automation system. This includes establishing and maintaining connections, handling read and write requests, and processing data quality and device status information. Proper configuration and optimization of the Device Module are critical for ensuring seamless data exchange, minimal latency, and optimal system performance. The Device Module supports a wide range of communication protocols, making it adaptable to diverse devices and systems.

Devices and TagProviders Distinctions

In FactoryStudio, devices represent the physical equipment in the system, while TagProviders are the logical entities that store and manage tag information. Understanding the distinction between these two components is essential for effective system configuration and management. By clearly separating the responsibilities of these components, FactoryStudio promotes modularity, simplifies configuration, and enables users to build scalable and maintainable solutions.

Using Data Quality on Displays

Data quality is a critical aspect of any HMI/SCADA system, as it ensures that operators receive reliable and accurate information about the process. FactoryStudio allows users to incorporate data quality on displays to provide a visual representation of data reliability, enabling operators to make well-informed decisions. This allows operators to identify potential issues and take appropriate action to maintain system performance and safety. (Add dica to Tooltip options)

Device

Module Runtime Attributes

The Device namespace is the entry point for all objects related to the device module.
For general information on namespace and object concepts, go to the section Objects and Attributes.

The Device.Channel object lists all of the configured channels and their runtime properties.

The Device.Node object lists all of the configured nodes and their runtime properties.

The Device.AccessType object lists the defined access types and has options to execute synchronous calls on reading and writing to the device. 

The following tag properties are updated based on the device module:

Programming reference on runtime objects

See Namespaces Reference for the complete list of properties and available methods.

Troubleshooting and Best

Practices

Table of Contents
maxLevel 4 minLevel 3 include #

Using the Built-In Diagnostics tools

The Platform has three Built-in Tools for diagnostics, PropertyWatch, TraceWindow and ModuleInformation. For information on those tools in general go to < acho que Execute Startup diagnostics), for specific information on levering its usage on Device Module diagnostics got o <Chilld Tag Diagnostics)

Common #Issues and Solutions

#Issue ControlLogix PLC Type

In the PLC Address Import section under Devices > Points, it is important to ensure that the correct protocol option is selected when connecting ControlLogix PLCs. In some cases, the default option "Model OTHERS" may not work correctly, and it may be necessary to select a specific model, such as "Model 1756-L8X". If you encounter issues with a ControlLogix Channel not sending or receiving values, try changing the protocol option to the specific model and test the communication.

#issue Importing L5K from ControlLogix

In the PLC Address Import section under Devices > Points, it is important to ensure that the path and file name are correct when importing L5K files using the "From Filename" or "From Device" options. In some cases, the "From Device" option may fail, and it may be necessary to use the "From Filename" option with the L5K file to make it work correctly.

Best Practices and #Recommendations

#Recommendation -

Troubleshooting and implementing best practices are essential for ensuring the smooth operation of your industrial automation system using FactoryStudio. By addressing common issues and following recommended guidelines, you can enhance system performance, maintain reliability, and minimize downtime.

In the PLC Address Import section under Devices > Points, it is important to ensure that the correct protocol option is selected when connecting ControlLogix PLCs. In some cases, the default option "Model OTHERS" may not work correctly, and it may be necessary to select a specific model, such as "Model 1756-L8X". If you encounter issues with a ControlLogix Channel not sending or receiving values, try changing the protocol option to the specific model and test the communication.

In the PLC Address Import section under Devices > Points, it is important to ensure that the path and file name are correct when importing L5K files using the "From Filename" or "From Device" options. In some cases, the "From Device" option may fail, and it may be necessary to use the "From Filename" option with the L5K file to make it work correctly.

Common Issues and Solutions

Communication Failures: If your system experiences communication failures between the HMI and devices, check the configuration of channels, nodes, and points. Ensure that device settings, such as IP addresses and communication protocols, are correct. Additionally, verify that the Device Module is running and that there are no errors in the communication logs.

Data Quality Issues: When encountering data quality issues, such as stale data or inaccurate values, review the configuration of access types and polling rates. Adjusting these settings may improve data quality and ensure reliable information is displayed on the HMI.

Importing PLC Addresses: If you experience issues importing PLC addresses, verify that the source file format and contents are correct. Also, ensure that the appropriate import method is selected in FactoryStudio, such as importing from Excel spreadsheets, CSV files, or L5K definition files.

Best Practices and Recommendations

System Design: Plan and design your industrial automation system with scalability and maintainability in mind. Use a modular approach, separating responsibilities between devices, TagProviders, and other modules. This promotes efficient workflows and simplifies system management.

#Recommendation - Documentation: Keep thorough documentation of your system, including device configurations, communication settings, and customizations. This will help with troubleshooting, maintenance, and future system upgrades.

#Recommendation - Training: Ensure that operators and maintenance personnel are well-trained in using FactoryStudio and understand the specific configurations of your system. This will enable them to identify and resolve issues efficiently, minimizing system downtime.

#Recommendation - Regular Maintenance and Updates: Schedule regular maintenance for your system, including software updates, hardware inspections, and performance assessments. This proactive approach will help to identify potential issues before they escalate, ensuring the reliability and performance of your industrial automation system.

In this section...