Overview
Channels are created and configured to handle specific communication protocols and drivers. 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.
On this page:
Configuration Workflow
Isn't the following content addressed in the previous 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. |
Creating and Managing Device Channels
Device channels 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 Devices → Channels.
Click New item...
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
Device Channel Creation Settings | |
|---|---|
Field/Column | Description |
Channel Name | Enter a name for the channel. |
Protocol | Select the protocol this channel uses. |
Description | Enter a description for this channel. |
We need to standarize the way tables are presented. Follow the approach used in Historian Tags
For more information about the configuration for common protocols and interfaces, click Help at the top of the tab inside FrameworX.
To edit device channels:
Breake it into secttion with headers.
Go to Devices → Channels.
To add or remove a column (visualization only), 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.
Device Channel Configuration Properties | |
|---|---|
Field/Column | Description |
ProtocolOptions | Configure the options for this protocol. Protocol options depend on the selected protocol. Check each documentation to guide you. |
Interface | Select the interface type for this channel. Serial - Use to configure the serial parameters for RS232/485 networks. MultiSerial - Use for configurations with multiple RS-232 ports. TCPIP - Use for Ethernet or wireless networks. |
Settings | Configure the settings for this channel. The available values depend on the interface the channel is using. For a serial interface, typically keep the defaults. For a MultiSerial interface, enter the number of RS-232 ports to use in the Ports field. AcceptUnsolicited - Accept unsolicited input from the slave. ListeningPort - TCP port where the slave device is connected (default is 502). NodeConnection - Number of parallel requests sent to each node (asynchronous communication). MaxSimultaneousConnections - Maximum number of concurrent connections. ShareNodeSameIP - Several slaves are connected to a single IP address. For example, RS485/Ethernet Converters. UseSingleThread - Use a single thread for the same IP nodes. UsePingToCheckConnection - Check for connection before sending a packet. The settings here must match the settings on the slave device. |
Timeout | Configure the timeout options for this channel. Typically, keep the default value. |
InitialState | Select the initial state for this channel. Enabled: the channel is loaded and execution starts when the project starts. Disabled: the channel is loaded, but does not starts execution going the disabled state. Remote: the channel is local in a remote Computer defined that the Remote Settings. See more information at Remote Channels. Reserved: the channel is not loaded, it acts as the channel was temporarily deleted from the project. |
Remote Settings | Set the primary IP and backup IP to configure the remote computer where this channel will run |
Driver Version | The version of the current driver being used. |
Restarting the channels:
Use tittles
It is possible to restart the Channel of the device module via script. That way, you don't have to shut down the entire system.
In Scripts > Classes, create a class using the follow code:
Device.Channel.XXXX.Stop()
Device.Channel.XXX.Start()
Note: The "XXXX" refers to the name of the Channel being used.
You can create a Task or Expression to call this class when needed, you can also do it in other ways that don't use the class. You can configure a button to perform this task in a screen, as example.
You can also learn how to configure Remote Channels here.
In this section: