Module Configuration for H2-SERIO

Topic: DMD0451

Help File Version: 2.9.4.37

Module Configuration for H2-SERIO and H2-SERIO-4 Modules

When a Do-more CPU powers up and detects a new H2-SERIO or H2-SERIO-4 module it will automatically create a new module configuration. Clicking the Edit Config button in the Module Configuration utility will open the following dialog where the default configuration can be changed.

The Module Configuration's Name will become a Do-more Device, be careful to choose a meaningful and unique name. Module names follow Nickname RulesNicknames 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..

The Port A / B / C Name will become a Do-more device, be careful to choose a meaningful and unique name.

Mode selects the functional mode for each of the serial ports on the SERIO / SERIO-4 module. Each Serial Port mode selection has an associated device that is specific to that mode; changing the mode will cause the underlying device to be deleted and / or created as needed.

Changing the Mode selection can have a significant impact on the System Configuration; to minimize unintended conflicts, any changes that are made will not be committed until the 'OK' or Apply' button is clicked. After selecting the Mode for a port, click the Apply button to commit that selection. At that point the programmer can click the Device Settings... button for that port to configure the Baud Rate, Parity, Station Address, etc., for that individual port.

Port Settings - each of the following selections will have the same Port Settings group where the serial port's hardware configuration is set. The group contains the following parameters:

Baud Rate : 115200, 57600, 38400, 19200, 9600, 4800, 2400, 1200, 300
Data Bits : 7, 8
Stop Bits : 1, 2
Parity : None, Odd, Even
Transmit Control specifies when data will be transmitted

Unconditional means data will be transmitted as soon as it reaches the output buffer
Wait for CTS means data will be transmitted when the CTS line is asserted
Delayed 5ms, Delayed 50ms, Delayed 250ms, Delayed 500ms means that after data reaches the output buffer, the RTS line will be asserted, and the transmitting of the data will be delayed by the selected number of milliseconds.

RTS Control selects how the RTS line will operate

Follows Transmitter means the RTS line is under the control of the transmitter
Manual allows programmatic control of the RTS line through the struct member IntSerial.RTS.
Off forces the RTS line to always be OFF
On forces the RTS line to always be ON

Select the Do-more Protocol (for Programming, HMIs, etc.) option to have the serial port operate as a programming port for the Do-more Designer programming software, or when using this port with a C-More panel that is using the "Automationdirect Do-more Serial" protocol.

Device Name displays the logical name of the serial port Device. Devices that connect with the Do-more protocol will have access to all of the memory blocks in the Do-more CPU.

Select the K-Sequence Server (Emulate DirectLOGIC PLCs) option to connect a third-party device that communicates via K-Sequence protocol. K-Sequence is a proprietary protocol used by Automationdirect (Koyo) hardware.

K-Sequence Protocol Settings are used when this device responds to K-Sequence Client requests:

Station is the ID of the K-Sequence Server Device, this can be any constant from 1 to 90.

Devices that connect with the K-Sequence protocol will only have access to the following blocks of memory (these blocks are numbered in octal):

Block Name	Description	Default Range
DLX	Inputs	DLX0 - DLX777
DLY	Outputs	DLY0 - DLY777
DLC	Control Relays	DLC0 - DLC777
DLV	V-Memory	DLV0 - DLV3777
Note: The size of the memory blocks available to the K-Sequence driver can be changed in the Memory Configuration.

Select the Modbus RTU Server (Slave) option to allow a third-party device that communicates via Modbus/RTU protocol to connect to the serial port.

Modbus Protocol Settings are used when this Device responds to Modbus/RTU Client requests:

Unit ID is the Unit ID of the Modbus/RTU Server Device, this can be any constant from 0 to 255.

Devices that connect with the Modbus/RTU protocol will only have access to the following blocks of memory (these blocks are numbered in decimal):

Block Name	Description	Default Range
MI	Modbus Inputs	MI1 - MI1023
MC	Modbus Control Relays	MC1 - MC1023
MIR	Modbus Input Registers	MIR1 - MIR2047
MHR	Modbus Holding Registers	MHR1 - MHR2047
Note: The first address in each of these memory blocks is offset 0, but the Modbus protocol does not support access to the first address of these memory blocks. Note: The size of the memory blocks available to the Modbus/RTU driver can be changed in the Memory Configuration.

The Modbus/RTU Server (Slave) supports the following function codes:

Function Code	Description
1	Read Coils
2	Read Discrete Inputs
3	Read Holding Registers
4	Read input Registers
5	Write Single Coil
6	Write Single Register
7	Read Exception Status
15	Write Multiple Coils
16	Write Multiple Registers
22	Mask Write Register

Select the Modbus RTU Client (Master) option to allow the serial port to be used by the Modbus Network Read (MRX) and the Modbus Network Write (MWX) instructions.

Modbus Protocol Settings are used when this Device generates Modbus/RTU Client requests:

Timeout is how many milliseconds should the instruction wait for the remote Modbus RTU Server to respond, this can be any constant from 0 to 32767.

Retries is how many times should the instruction retry the communication with the remote Modbus RTU Server, this can be any constant from 0 to 255.

Inter-packet Delay is the amount of time (in microseconds) that will be placed between the Modbus RTU packets as they are sent. This can be any constant between 0 and 65535. The inter-packet delay creates the required "dead time" on the wire that Modbus uses to frame a packet. The Modbus specification requires this value to be a minimum of 3.5 characters times (based on baud rate). If the value entered is smaller than the required time, the Modbus RTU Client will use the minimum required time instead of the value that is entered. If the value entered is larger than the required time, the value entered will be used.

Use this formula to calculate the inter-packet delay (in microseconds) based on baud rate:
( 3.5 * (number of bits in a character / baud rate) ) * 1,000,000

For example: using a 10-bit character (1 start bit, 8 data bits, no parity bit, and 1 stop bit) at 19200 baud:
( 3.5 ( 10 / 19200 ) ) * 1,000,000 = 1823 microseconds

Select the Program Control (Uses STREAMIN / STREAMOUT for ASCII and Custom Protocols) option to allow the on-board serial port to be used by the Stream In Data from Device (STREAMIN) and Stream Out Data to Device (STREAMOUT) instructions for sending and receiving ASCII data, or implementing custom protocols. Once configured this way the STREAMIN and STREAMOUT instructions will have the option of selecting the @IntSerial as a target Device.

Device Name is the name of the on-board serial port. To change the device's name use the Device Configuration dialog.

Module Configuration for H2-SERIO and H2-SERIO-4 Modules

See Also: