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. The software platform establishes Channels to manage communication using protocols. A DeviceChannel object encapsulates a selected Protocol and its configuration settings. The Channel is the next step of the Device Module configuration, mapping the stations of PLCs or devices in a field network, and allowing the selection of the protocol settings that will be used with each device.
On this page:
Table of Contents maxLevel 3 style none
Configuring Device Channels
Device channels Channels are the pathways for communication between the HMI and the devices in the system. The sections below describe how to create and edit device channels Device Channels on the platform in more detail.
Creating
A Newand Editing a Device Channel
To create a new channel, follow these steps:
- Access Devices → Channels.
- Click on the plus iconNew Channel or Plus button.
- Choose a Protocol and fill in the Channel Name and Description fields. The next section on this page table at the end of this section describes each option available.
- Click OK
The following table describes each available property you can configure when creating a channel:
Field
Description
Channel Name
Name for the channel.
Protocol
The protocol the channel will use.
Description
Description for the channel.
- .
To configure or
Editing A Channel
To edit an existing channel, follow these steps
- Access Devices → Channels.
- Double-click the property you wish to edit on the row corresponding to the channel you want to modify.
- Edit the property fields.
Device Channel Properties
The following table describes each available property you can configure when editing a channel:
Field | Description | ||
|---|---|---|---|
Protocol Options | Defines the options for this protocol. The options depend on the selected protocol, check . Check each protocol documentation to guide you. | ||
Interface | Defines the interface type for this channel. Serial: Use this option to configure the serial parameters for RS232/485 networks. Multi Serial: Use this for configurations with multiple RS-232 ports. TCPIP: Use for Ethernet or wireless networks. | ||
Settings | Defines the settings for this channel. The available values will depend on the interface the channel is using. For a serial interface, typically keep the defaults. For a Multi Serial interface, enter the number of RS-232 ports to use in the Ports field. Node Connection: The number of parallel requests sent to each node (asynchronous communication). Accept Unsolicited: Allow to accept unsolicited input from the slave. Listening Port: The TCP port where the slave device is connected (default is 502). Node Connection: The number of parallel requests sent to each node (asynchronous communication). Max Simultaneous Connections: The maximum number of concurrent connections. Share Node Same IP: Several slaves are connected to a single IP address. For example, RS485/Ethernet Converters. Use Single Thread: Use a single thread for the same IP nodes. Use Ping To Check Connection: Check for connection before sending a packet.
| ||
Timeout | Defines the timeout options for this channel. Typically, keep the default value. | ||
InitialState | Defines the initial state for this channel, the states can be as follows: 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 atSee Remote Channels page. Reserved: The channel is not loaded, it acts as the channel was temporarily deleted from the project. | ||
Remote SettingsRemoteSettings | Defines the primary IP and backup IP to configure the remote computer where this channel will run. | ||
Driver VersionDriverVersion | Defines the version of the current driver being used. |
Restarting channels
Working with Channel
Stop and Start Commands
After creating a solution, you may face issues that compromise the communication with the field device. In such moments, instead of restarting the entire system, you may solve the problem by restarting the channel. You can perform such tasks using scripts, avoiding shutting 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. To do so, follow these steps:
- Access Scripts → Classes
Create a new class using the following C# code :below, where "XXXX" refers to the name of the channel.
The "XXXX" refers to the name of the used channel.Code Block language c# @Device.Channel.XXXX.Stop() @Device.Channel.XXXX.Start()
You can create a Task or Expression to call this class when needed and also do it in other ways that don't use the class. You can also learn how to configure Remote Channels here.
See the Remote Channels page for more information.
| Code Block | ||
|---|---|---|
| ||
public void Stop()
{
@Device.Channel.ControlLogix.Stop(10);
} |
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|
...