Introduction
In this guide, we'll explore how to effectively utilize we’ll explore concepts when utilizing the Devices module in FrameworX for seamless communication and data exchange with field devices. We'll cover the essentials of configuring communication protocols, managing channels, nodes, and points, and provide tips for troubleshooting common issues.We’ll present the typical configuration workflow and links to related topics in the documentation.
On this page:
| Table of Contents | ||
|---|---|---|
|
Design Concepts
Objective
By the end of this guide, you will understand how to create a connection with a Device using its native protocol, or open standards such as OPC or MQTT, and how to use that data in Displays or other modules.
Prerequisites
Basic understanding of FrameworX platform.
Familiarity with Field Devices.
The following main concepts are key when setup the devices Communication.
Protocols Selection
.
Organizing Channels and Nodes
Using Access Types
The concept of Server Tags and Client Tags is explained in the section <>>>>.
Essentially, the Client Tags will hold all the Operations (Displays Client Users). As much as possible, you should leverage the built-in Client.DataContext properties and the built tools to persist users configuration.
Step-by-Step InstructionsConfiguration Workflow
Creating Device Channels
Navigate to Devices → Protocols
Select the Protocol that supports the connection if you Device and press Create New Channel
Go to Devices → Channels to Customize Protocols Options, if needed. The Protocol Options is dependent on the protocol, use the Help button to go open the online documentation of the protocol you are using.
Defining Nodes and Stations:
Go to Devices → Nodes
Use the Plus button to create a new Node, selecting the Channel (and consequently the Protocol) that device shall use.
Define the contents for PrimaryStation, which is the physical network address of the device you want to connect with.
Mapping Tags to the Device Addresses
- Go To Devices → Points to map Tags in your solution to valued within your field Device
The key columns to setup are the TagName, the Node (that identifies the device), and the Address. Each device has its syntax for the address, but the concept of address applies to all protocols.
Use the column AccessType to define if you want the tag and the device be connected with Read, Write or both Read and Write modes.
- Custom behavior can be defined extending the AccessTypes.
Tips and Best Practices
<Refer to Devices UserGuide section on that
Troubleshooting
- <Refer to Devices UserGuide section on that
Additional Resources
FrameworX User Guide for detailed information on system capabilities.
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|