Topic: DMD0248 Device Configuration |
|
Devices are pre-configured interfaces that provide programmatic access to system resources. Additional user configuration of the devices, for example baud rates for serial ports, is provided for in this dialog. Some devices are automatically created - for example @UserLog and @DMLogger - and although they are listed here, they cannot be deleted or edited. The Device Name column displays the current name of the device, it is this name that is referenced in the instructions that target the Device.
The Type column displays the driver type used for the Device. '(Setup only)' is used to denote Devices that are data servers, that is, they are NOT used as target device in instructions.
The Configuration column displays the current configuration for the Device. 'No configuration required' is used to denote Devices that have a fixed configuration.
The Heap Item column displays the Heap Item that is used for programmatic access to the Device.
|
|
Add a New DeviceThe three buttons at the right allow the programmer to modify the current system Configuration by adding, or deleting, or editing Device configurations.
Click the New Device button to invoke the Add Device dialog to create one of the following Devices:
Click the Edit Device button to open the edit dialog for the currently highlighted Device.
Click the Delete Device to open deletes the currently highlighted Device.
|
|
On-board Ethernet Port (@IntEthernet)
Device Name is the logical name assigned to the Internal Ethernet Device. Device Names can consists of 1 to 16 alphanumeric characters and must follow Nickname Rules Nicknames can be 1 to 16 characters in length and consist of any combination of alphanumeric characters and underscores ('_', 'a-z', 'A-Z', 0-9), no spaces or punctuation marks are allowed, and must begin with a letter or an underscore..
RX/WX Settings are configuration
settings used when this Device is used in a DirectLOGIC
Read Network (DLRX) or a DirectLOGIC
Write Network (DLWX) instruction:
|
|
Internal Modbus TCP Client (@IntModbusTCPClient)
Device Name is the logical name assigned to the Modbus TCP Client Device. Device Names can consists of 1 to 16 alphanumeric characters and must follow Nickname Rules Nicknames can be 1 to 16 characters in length and consist of any combination of alphanumeric characters and underscores ('_', 'a-z', 'A-Z', 0-9), no spaces or punctuation marks are allowed, and must begin with a letter or an underscore..
Modbus Protocol Settings are configuration
settings used when this Device is used in a Modbus
Network Read (MRX) or Modbus
Network Write (MWX) instruction:
Note: There is an additional internal timeout in the TCP stack of 15 seconds that only comes into play if the target TCP Server / Slave is missing from
the network. This internal timeout is used when the TCP connection is being established, which must happen before the Modbus layer transaction can occur.
This internal timeout value cannot be changed. The Timeout, Retries and Inactivity Timeout parameters specified here are all associated with the Modbus
layer (not the TCP layer) and have no effect on the TCP layer timeout.
|
|
On-board Serial Port (@IntSerial) and H2-SERIO or H2-SERIO-4 ModuleAll of the Serial Port Devices in a Do-more PLC have a common Port Settings section with the following configuration options. These serial port configuration can be examined at runtime with the Read Device Register (DEVREAD) instruction, and the configuration can be changed at runtime through the Write Device Register (DEVWRITE) instruction.
Device Name displays the logical name of the serial port Device. Device Names can consists of 1 to 16 alphanumeric characters and must follow Nickname Rules Nicknames can be 1 to 16 characters in length and consist of any combination of alphanumeric characters and underscores ('_', 'a-z', 'A-Z', 0-9), no spaces or punctuation marks are allowed, and must begin with a letter or an underscore..
Port Settings select the hardware-specific settings for the specified Serial Port:
|
|
Serial Port as KSequence ServerWhen the module configuration selects the On-board Serial Port or a port on the H2-SERIO or H2-SERIO-4 as a K Sequence Server, the additional Device configuration option is available:
K Sequence Protocol Settings are configuration settings used when this Device responds to K Sequence Client requests:
|
|
Serial Port as Modbus RTU ClientWhen the module configuration selects the On-board Serial Port or a port on the H2-SERIO or H2-SERIO-4 as a Modbus RTU Client, the additional Device configuration options are available:
Modbus Protocol Settings are configuration settings used when this Device is used in a Modbus Network Read (MRX) or Modbus Network Write (MWX) instruction:
|
|
Serial Port as Modbus RTU ServerWhen the module configuration selects the On-board Serial Port or a port on the H2-SERIO or H2-SERIO-4 as a Modbus RTU Server, the additional Device configuration option is available:
Modbus Protocol Settings : configuration settings used when this Device responds to Modbus RTU Client requests:
|
|
MQTT Client (IoT) DeviceBRX PLCs with on-board Ethernet Ports can connect to one or more MQTT Brokers, and once connected, these PLCs can publish messages to the Brokers and subscribe to messages from the Brokers. The parameters required to create a connection to a Broker is managed by an MQTT Client (IoT) device.
There is no limit to the number of MQTTPUB instructions that can use a single MQTT Client device, but each MQTT Client device can only provide a subscription space for 100 active topics spread across a maximum of 10 MQTTSUB instructions, for example 2 enabled instruction with 50 Topics each, or 10 enabled instructions with 10 Topics each. To subscribe to more than 100 Topics, create multiple MQTT Client devices to the same MQTT Broker.
Device Name is the name given to the MQTT Client device that will be referenced in IoT Publish MQTT Topics (MQTTPUB) and IoT Subscribe to MQTT Topics (MQTTSUB) instructions. Device Names can consists of 1 to 16 alphanumeric characters and must follow Nickname Rules Nicknames can be 1 to 16 characters in length and consist of any combination of alphanumeric characters and underscores ('_', 'a-z', 'A-Z', 0-9), no spaces or punctuation marks are allowed, and must begin with a letter or an underscore..
MQTT Server Address selects how the connection to the MQTT Broker will be established.
Other Settings
Enable Account Authentication is used if the MQTT Broker requires authentication before it will accept messages.
Last Will and TestamentBecause MQTT is often used on unreliable networks, the Last Will and Testament (LWT) feature is used in MQTT to notify other clients about a client that disconnects in a less than graceful manner. Each client can specify its Last Will message (a normal MQTT message with Topic, Payload, and , Retain flag) when connecting to a Broker. The Broker will store the message until it detects that the client has disconnected ungracefully. If the client disconnect abruptly, the Broker sends the message to all clients that are subscribed to the Topic which was specified in the Last Will message. The stored Last Will message will be discarded if a client disconnects gracefully.
According to the MQTT 3.1.1 specification the Broker will distribute the LWT of a client in the following cases:
Enable Will to specify a Topic and a Payload that will be published as the Last Will and Testament for this MQTT Broker Device specify the following:
MQTT Client IDThe Client Identifier is a 64 byte string that uniquely identifies each MQTT client. Each identifier must be unique to only one connected client at a time. The identifier must contain only characters valid in a queue manager name. Within these constraints, you are able to use any identification string. The MQTT Client Device automatically generates a Client ID using the MAC address of the BRX CPU's Ethernet port that is used during the connection process.
Enable User Specified Client ID to supersede the automatically generated Client ID with one provided by the user.
|
|
SMTP Client DeviceThe Add / Edit SMTP Client Settings dialog is used to create the required connection from the Do-more CPU to an SMTP server which will allow the CPU to send Email. The information required to configure any SMTP Client connection is always going to be specific to the installation. It is up to the programmer to locate the required information. The Send Email (EMAIL) instruction will use this SMTP Client to send Email.
Device Name is the name given to the SMTP Client that will be referenced in Send Email (EMAIL) instructions. Device Names can consists of 1 to 16 alphanumeric characters and must follow Nickname Rules Nicknames can be 1 to 16 characters in length and consist of any combination of alphanumeric characters and underscores ('_', 'a-z', 'A-Z', 0-9), no spaces or punctuation marks are allowed, and must begin with a letter or an underscore..
Note: the Email instruction in Do-more Technology v2.2 and later can perform a DNS name resolution internally, that is, they can use the DNS protocol to resolve a name of an SMTP server to its IP address when the Email instruction is executed . This also means the SMTP Client can be configured to establish an encrypted connections to Email servers and optionally require trust certificate validation. The EMail instruction in Do-more Technology versions previous to v2.2 do not have this internal DNS capability. This means the SMTP Client must contain the IP address of the SMTP server, not the name of the SMTP server.
SMTP Server Address selects how the connection to the SMTP server will be established.
Security (only available on BRX platform) options are used when establishing an encrypted connection to a secure SMTP server instead of a plain-text connection to an unsecured Port 25 server.
Note: using SSL / TLS encryption is a very CPU intensive operation because of the math involved. Because the CPU must keep the PLC's scan time in check, the SSL encoding is processed as a time-slicing event, meaning that only a portion of each scan time is used to work on the encryption; this prevents the scan time from exceeding the watchdog timer. Processing the encryption can take several seconds depending on the number of security certificates that must be processed and the amount of data being transferred.
The amount of time the CPU allots to processing TLS transactions on each scan is called the TLS Timeslice. This value can be changed on the CPU page of the System Configuration. Increasing this value can allow the TLS process to complete sooner, but at the cost of increasing the PLC's scan time. The Default TLS Timeslice value will be used by the TLS encryption engine each time the PLC powers up and goes into RUN mode. RUN-mode changes to this value can be made by changing the value in $TLSTimeslice (DST68).
Other Settings
Authentication is used if the SMTP server requires authentication before it will accept an Email from the Do-more CPU, select one of the following methods:
Clicking the Test settings and verify server credentials button will attempt to establish a connection to the specified SMTP Server using the options and parameters that have been selected. This step is required if the SMTP Client will use Certificate Validation.
This verification work is done by Do-more Designer - not the PLC - but it will mimic the work the PLC will do when it attempts to send Email using this SMTP Client. The Help text for the Send Email (EMAIL) instruction has a section detailing how to use Do-More Logger to debug SMTP connection issues from the PLC's perspective.
|
|
TCP Client DeviceDefines a client-side TCP socket for general purpose TCP/IP networking, which is useful in cases where the Do-more CPU needs to send or receive data through a custom streaming protocol. TCP Client devices are only available if the Do-more CPU has an on-board Ethernet port. TCP Client devices require no configuration, they can create connections to TCP Server devices, but cannot accept connections from other TCP clients. Connections to TCP Servers are created through the Open TCP Connection (OPENTCP) instruction.
The TCP Client device is NOT the correct choice for connecting to servers that are using Modbus/TCP protocol, those clients should be using the Modbus/TCP Client device as described above.
Device Name is the name to give the TCP Client. This is the name that will be referenced in the OPENTCP instruction. Device Names can consists of 1 to 16 alphanumeric characters and must follow Nickname Rules Nicknames can be 1 to 16 characters in length and consist of any combination of alphanumeric characters and underscores ('_', 'a-z', 'A-Z', 0-9), no spaces or punctuation marks are allowed, and must begin with a letter or an underscore..
|
|
TCP Server DeviceDefines a server-side TCP socket for general purpose TCP/IP networking, which is useful in cases where the Do-more CPU needs to send or receive data through a custom streaming protocol. The TCP Server Device creates the required device driver that is used by the TCPLISTEN - Start Listening on TCP Port instruction.
TCP Server devices are only available if the Do-more CPU has an on-board Ethernet port. TCP Server devices are configured with a local port number, which defines the 'listening' port. TCP Server devices can accept connections from a single TCP Client, and upon accepting the client connection, will invoke a Program code-block specified for the 'connected' state, and a different Program code-block when the TCP connection is lost.
The TCP Server device is NOT the correct choice for allowing connections from devices that are using Modbus/TCP protocol, those clients should be connecting to the built-n Modbus/TCP Server .
The Device Name specified here will be in the list of Devices that can be selected in the TCPLISTEN instructions. Device Names can consists of 1 to 16 alphanumeric characters and must follow Nickname Rules Nicknames can be 1 to 16 characters in length and consist of any combination of alphanumeric characters and underscores ('_', 'a-z', 'A-Z', 0-9), no spaces or punctuation marks are allowed, and must begin with a letter or an underscore..
TCP Port is the TCP port number to list on. This can be any decimal constant in the range of 1 to 65535 except port number 28784 which is already used by the Do-more CPU. |
|
UDP Connection DeviceThe UDP Connection Device creates a UDP socket for general purpose Ethernet networking, useful in cases where the CPU needs to send or receive data through a custom packet-style protocol. UDP Connections are used by the Input Data from Packet Device (PACKETIN) and Output UDP to Packet Device (PACKETOUT) instructions. UDP Connections can only be created on Do-more CPUs which have an on-board Ethernet port.
The Device Name specified here will be in the list of Devices that can be selected in the PACKETIN and PACKETOUT instructions. Device Names can consists of 1 to 16 alphanumeric characters and must follow Nickname Rules Nicknames can be 1 to 16 characters in length and consist of any combination of alphanumeric characters and underscores ('_', 'a-z', 'A-Z', 0-9), no spaces or punctuation marks are allowed, and must begin with a letter or an underscore..
UDP Port : this UDP Connection will "listen" for UDP packets that the Do-more CPU receives that have this port number. This can be any decimal constant in the range of 1 to 65535 except for port number 28784 (0x7070) which is already used by the Do-more CPU. Each UDP Connection must have a unique port number.
|
|
Do-more EtherNet Peer-to-Peer ClientThe Do-more Ethernet Peer-to-Peer Device creates the required device driver that is used by the Do-more Network Read (RX) and Do-more Network Write (WX) instructions.
The Device Name shown here will be in the list of Devices that can be selected in the RX and WX instructions. This name cannot be changed.
DMPP Protocol Settings
|
|
EtherNet/IP Explicit Message ClientThe EtherNet/IP Explicit Message Client creates the required device driver that is used by the Send EtherNet/IP Message (EIPMSG) instruction.
The Device Name shown here will be in the list of Devices that can be selected in the EtherNet/IP Explicit Message Client. This name cannot be changed.
EtherNet/IP Protocol Settings
|
|
FTP Client DeviceThe FTP Client creates the required device driver that is used by the Retrieve File From Remote (FTPGET) and Send File To Remote (FTPPUT) instructions.
Note: remember the Network Message Viewer (Do-more Logger) utility is a great tool to help diagnose FTP Client connection problems.
The Device Name specified here will be in the list of Devices that can be selected in the FTPGET and FTPPUT instructions. Device Names can consists of 1 to 16 alphanumeric characters and must follow Nickname Rules Nicknames can be 1 to 16 characters in length and consist of any combination of alphanumeric characters and underscores ('_', 'a-z', 'A-Z', 0-9), no spaces or punctuation marks are allowed, and must begin with a letter or an underscore..
FTP Server Address selects how the connection to the FTP server will be established:
Account Information : a connection to an FTP server can require either a Username and Password, or the server will allow an anonymous login:
Other Settings
|
|
See Also:
Device Configuration
|
|
Related Topics:
DEVREAD - Read Device Register
DEVWRITE - Write Device Register
|
|