Comtrol IOLM Modbus TCP User Manual

Download

Modbus/TCP

Reference Manual

Trademark Notices

Document Number: 2000590 Rev. A

Microsoft and Windows are registered trademarks of Microsoft Corporation.

Other product names mentioned herein may be trademarks and/or registered trademarks of their respective owners.

Comtrol Corporation makes no representations or warranties with regard to the contents of this document or to the suitability of the Comtrol product for any particular purpose. Specifications subject to change without notice. Some software or features may not be available at the time of publication. Contact your reseller for current product information.

Chapter 1. Modbus/TCP Interface ......................................................................................7

1.1. Modbus Function Codes........................................................................................................................ 8

1.2. Modbus Address Definitions ................................................................................................................ 8

1.3. Multiple Port Process Data (PDI and PDO) Access via Modbus TCP...................................... 10

Chapter 2. IO-Link Port Configuration...........................................................................13

2.1. IO-Link Settings Configuration Page .............................................................................................. 13

2.1.1. Editing IO-Link Settings................................................................................................................ 14

2.1.2. IO-Link Settings Parameters......................................................................................................... 14

2.2. Modbus/TCP Settings Configuration Page.....................................................................................15

2.2.1. Editing Modbus/TCP Settings........................................................................................................ 16

2.2.2. Modbus/TCP Settings Parameters................................................................................................. 16

Chapter 3. Using the Diagnostics Pages .........................................................................19

3.1. IO-Link Port Diagnostics .................................................................................................................... 19

3.2. Modbus/TCP Diagnostics .................................................................................................................... 22

Chapter 4. Troubleshooting and Technical Support ...................................................25

4.1. Troubleshooting.................................................................................................................................... 25

4.2. Contacting Technical Support .......................................................................................................... 26

4.3. Using Log Files...................................................................................................................................... 27

4.3.1. View a Log File ............................................................................................................................... 27

4.3.2. Clear a Log File............................................................................................................................... 28

4.3.3. Export a Log File ............................................................................................................................ 28

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Table of Contents - 3

Table of Contents

4 - Table of Contents IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

Chapter 1. Modbus/TCP Interface

The IO-Link Master provides a slave-mode Modbus/TCP interface that provides:

• Read access to the PDI and PDO data blocks for each IO-Link port

• Write access to the PDO data block for each IO-Link port

• Write access to send SPDU requests to each IO-Link port

• Read access to SPDU responses from each IO-Link port

• Read access to the Port Information Block for each IO-Link port

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 1. Modbus/TCP Interface - 7

Modbus Function Codes

1.1. Modbus Function Codes

This table shows the supported Modbus function codes.

Message Type Function Code Maximum Message Size

Read Holding Registers 3 250 Bytes (125 Words)

Write Single Register 6 2 bytes (1 Word)

Write Multiple Registers 16 (10 hex) 246 Bytes (123 Words)

Write: 242 bytes (121 Words

Read/Write Holder Registers 23 (17 hex)

Read: 246 bytes (123 Words)

1.2. Modbus Address Definitions

The address definitions for Modbus/TCP interface are shown in the following table.

Multiple

Port PDI

Data

Block(s)

Port

Specific

PDI Data

Block

Multiple

Port PDO

Data

Block(s)

Port

Specific

PDO Data

Block

Receive

SPDU

Response

Transmit

SPDU

Request

Vendor

Name

IO-Link Port 1IO-Link Port 2IO-Link Port 3IO-Link Port

999 (Base 0)

1000 (Base 1)

1000 (Base 0)

1001 (Base 1)

1049 (Base 0)

1050 (Base 1)

1050 (Base 0)

1051 (Base 1)

1100 (Base 0) 1101 (Base 1)

1300 (Base 0)

1301 (Base 1)

Port Information Block (Continuous Block) 232 Words

1500 (Base 0)

1501 (Base 1)

1999 (Base 0)

2000 (Base 1)

2000 (Base 0)

2001 (Base 1)

2049 (Base 0)

2050 (Base 1)

2050 (Base 0)

2051 (Base 1)

2100 (Base 0)

2101 (Base 1)

2300 (Base 0)

2301 (Base 1)

2500 (Base 0)

2501 (Base 1)

2999 (Base 0)

3000 (Base 1)

3000 (Base 0)

3001 (Base 1)

3049 (Base 0)

3050 (Base 1)

3050 (Base 0)

3051 (Base 1)

3100 (Base 0)

3101 (Base 1)

3300 (Base 0)

3301 (Base 1)

3500 (Base 0)

3501 (Base 1)

3999 (Base 0)

4000 (Base 1)

4000 (Base 0)

4001 (Base 1)

4049 (Base 0)

4050 (Base 1)

4050 (Base 0)

4051 (Base 1)

4100 (Base 0)

4101 (Base 1)

4300 (Base 0)

4301 (Base 1)

4500 (Base 0)

4501 (Base 1)

Access Length

Read-

Only

Read-

Only

Read/ Write

Read-

Only

Write-

Only

Read-

Only

Configurable

per port (s)

Configurable

per port

Configurable

per port(s)

Configurable

per port

4 to 125 Words

4 to 123 Words

64 Chars

32 Words

8 - Chapter 1. Modbus/TCP Interface IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

Modbus Address Definitions

Vendor

Text

Product

Name

Product Id

Product

Text

Serial

Number

Hardware

Revision

Firmware

Revision

Device PDI

Length

Device

PDO

Length

IO-Link Port 1IO-Link Port 2IO-Link Port 3IO-Link Port

1532 (Base 0)

1533 (Base 1)

1564 (Base 0)

1565 (Base 1)

1596 (Base 0)

1597 (Base 1)

1628 (Base 0)

1629 (Base 1)

1660 (Base 0)

1661 (Base 1)

1668 (Base 0)

1669 (Base 1)

1700 (Base 0)

1701 (Base 1)

1732 (Base 0)

1733 (Base 1)

1733 (Base 0)

1734 (Base 1)

2532 (Base 0)

2533 (Base 1)

2564 (Base 0)

2565 (Base 1)

2596 (Base 0)

2597 (Base 1)

2628 (Base 0)

2629 (Base 1)

2660 (Base 0)

2661 (Base 1)

2668 (Base 0)

2669 (Base 1)

2700 (Base 0)

2701 (Base 1)

2732 (Base 0)

2733 (Base 1)

2733 (Base 0)

2734 (Base 1)

3532 (Base 0)

3533 (Base 1)

3564 (Base 0)

3565 (Base 1)

3596 (Base 0)

3597 (Base 1)

3628 (Base 0)

3629 (Base 1)

3660 (Base 0)

3661 (Base 1)

3668 (Base 0)

3669 (Base 1)

3700 (Base 0)

3701 (Base 1)

3732 (Base 0)

3733 (Base 1)

3733 (Base 0)

3734 (Base 1)

4532 (Base 0)

4533 (Base 1)

4564 (Base 0)

4565 (Base 1)

4596 (Base 0)

4597 (Base 1)

4628 (Base 0)

4629 (Base 1)

4660 (Base 0)

4661 (Base 1)

4668 (Base 0)

4669 (Base 1)

4700 (Base 0)

4701 (Base 1)

4732 (Base 0)

4733 (Base 1)

4733 (Base 0)

4734 (Base 1)

Access Length

Read-

Only

Read-

Only

Read-

Only

Read-

Only

Read-

Only

Read-

Only

Read-

Only

Read-

Only

Read-

Only

64 Chars

32 Words

64 Chars

32 Words

64 Chars

32 Words

64 Chars

32 Words

16 Chars

8 Words

64 Chars

32 Words

64 Chars

32 Words

1 Word

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 1. Modbus/TCP Interface - 9

Multiple Port Process Data (PDI and PDO) Access via Modbus TCP

1.3. Multiple Port Process Data (PDI and PDO) Access via Modbus TCP

The process data has been grouped together in order to minimize the number of Modbus messages required to interface to the IO-Link master. The PDI and PDO data for multiple ports can be received or transmitted by one message.

Read

(Input)

Process

Data

Input

Read

(Input)

Process

Data

Output

Modbus Holding

Address (Base 1)

1000

(Port 1)

2000

(Port 2)

3000

(Port 3)

4000

(Port 4)

1050

(Port 1)

2050

(Port 2)

3050

(Port 3)

4050

(Port 4)

Controller

Port 1 Access

Read

(Input)

Write

(Output)

Controller

Port 2 Access

Read

(Input)

(Output)

Write

Controller

Port 3 Access

Read

(Input)

(Output)

Write

Controller

Port 4 Access

Read

(Input)

(Output)

Write

1050

(Port 1)

Write

(Output)

Process

Data

Output

10 - Chapter 1. Modbus/TCP Interface IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

2050

(Port 2)

3050

(Port 3)

4050

(Port 4)

Multiple Port Process Data (PDI and PDO) Access via Modbus TCP

Modbus Read/Write Access where:

• All PDI data can be read with one Modbus Read Holding Registers message.

• All PDO data can be read with one Modbus Read Holding Registers read message.

• All PDO data can be written with one Modbus Write Holding Registers message.

• Controller Read access:

- The PDI data from one or more ports may be read with one message. (i.e.: If addressing port 1, at address 1000, ports one to four may be read in one message.)

- The PDO data from one or more ports may be read with one message. (i.e.: If addressing port 1, at address 1050, ports one to four may be read in one message.)

- Partial PDI and PDO data reads are allowed.

- The length of the Read message can range from 1 to the total, configured PDI or PDO length for all ports starting at the addressed port.

• Controller Write (Output) access:

- Only PDO data may be written.

- The PDO data for one or more ports may be written with one Write Holding Registers message.

- Partial PDO data writes are not allowed.

- The length of the Write message must be equal to the total of the configured PDO lengths for all ports to be written. The one exception is that the data length of the last port to be written must be equal to or greater than the device PDO length for that port.

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 1. Modbus/TCP Interface - 11

Multiple Port Process Data (PDI and PDO) Access via Modbus TCP

12 - Chapter 1. Modbus/TCP Interface IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

Chapter 2. IO-Link Port Configuration

This section discusses port configuration, which includes these topics:

• 2.1. IO-Link Settings Configuration Page

• 2.2. Modbus/TCP Settings Configuration Page on Page 15

Note: The IO-Link Master may work out of the box for ControlLogix PLCs.

2.1. IO-Link Settings Configuration Page

Use the IO-Link Settings page to configure IO-Link port characteristics for the IO-Link Master.

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 2. IO-Link Port Configuration - 13

Editing IO-Link Settings

2.1.1. Editing IO-Link Settings

You can use this procedure to configure IO-Link characteristics for each port. The following table or help system provides information about each option.

1. If necessary, open the IO-Link Master web interface with your web browser using the IP address or through PortVision DX.

2. Click Configuration in the menu bar, which by default loads the IO-Link Settings page.

3. Click the EDIT button for the port that you want to configure.

4. Make appropriate selections for the IO-Link device that you will connect to that port. You can use the help system if you require definitions or values for the options or 2.1.2.

IO-Link Settings Parameters on Page

14.

5. Click the SAVE button.

6. Repeat for each port that requires configuration changes.

2.1.2. IO-Link Settings Parameters

The IO-Link Settings configuration page supports the following options.

IO-LINK SETTINGS Page

User defined port or device description.

Port Name

Port Mode

Default: IO-Link

Invert IO

Default: False

Minimum Cycle Time

Default: 4

• Standard ASCII characters

• Max length = 80 characters

Selected IO-Link Port Mode. Valid settings are:

• Reset

•IO-Link

• Digital In

• Digital Out

If enabled and the Port Mode is Digital In or Digital Out, inverts the I/O value.

0= False (Disabled - Do not invert IO)

1= True (Enabled - Invert IO)

Note: Does not affect the Auxiliary Input.

The minimum, or fastest, cycle time that the IO-Link device may operate at. The valid range is 4-65535 ms.

14 - Chapter 2. IO-Link Port Configuration IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

Modbus/TCP Settings Configuration Page

2.2. Modbus/TCP Settings Configuration Page

You can use the Modbus/TCP Settings page to configure Modbus/TCP with the IO-Link Master.

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 2. IO-Link Port Configuration - 15

Editing Modbus/TCP Settings

2.2.1. Editing Modbus/TCP Settings

1. If necessary, open the IO-Link Master web interface with your web browser using the IP address.

2. Click Configuration in the menu bar.

3. Click the MODBUS/TCP SETTINGS submenu.

4. Click the EDIT button for the port that you want to configure.

5. Make appropriate selections for the IO-Link device that you will connect to that port. You can use the help system if you require definitions or values for the options or 2.2.2. Page 16.

6. Scroll to the top of the page and click the SAVE button. Make sure that the port now displays the EDIT button. If it displays the SAVE and CANCEL buttons, that means that one of the parameters contains an incorrect

value. If necessary, scroll down the page, make the needed corrections, and click SAVE.

Modbus/TCP Settings Parameters on

2.2.2. Modbus/TCP Settings Parameters

The following table illustrates the Modbus/TCP Settings page.

Modbus/TCP Settings Page

The time that the IO-Link Master’s Modbus/TCP interface waits for

ISDU Response Timeout

Default = 20 seconds

Process Data Settings

PDI Data Block Size

Default: 36-bytes

PDI Byte-Swap Method

Default: No byte-swap

a response to an ISDU request. The timeout needs to set long enough to allow all commands within the ISDU request to be processed.

Valid range: 1-10,000 seconds

The configurable PDI data block length. Optional lengths are:

• 4-bytes (header only)

• 8-bytes (4 bytes data)

• 16-bytes (12 bytes data)

• 24-bytes (20 bytes data)

• 36-bytes (32 bytes data)

If enabled, the IO-Link Master swaps the data bytes in word (2 byte) format or dword (4 byte) format. Options include:

• No byte-swap – data passed through as received

• Word (16-bit) byte-swap – data is byte-swapped in word format

• Dword (32-bit) byte-swap – data is byte-swapped in dword format

Note: Because both IO-Link and Modbus/TCP use big-endian byte

ordering, byte swapping typically is not required for word and dword data.

Byte swapping is most commonly required when receiving byte (8-bit) data and it is desired to place the first data byte in the least significant byte position of the holding register. For these cases, word (16 bit) byte-swap is typically used.

16 - Chapter 2. IO-Link Port Configuration IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

Modbus/TCP Settings Page (Continued)

PDO Data Block Size

Default: 32-bytes

PDO Byte-Swap Method

Default: No byte-swap

Append PDO to PDI Data

Default: False

Clear Event Code in PDO Block

Default: False

Clear Event Code After Hold Time

Default: True

Modbus/TCP Settings Parameters

The configurable PDO data block length. Optional lengths are:

Event code not included:

• 4-bytes = 2 data words

• 8-bytes = 4 data words

• 16-bytes = 8 data words

• 24-bytes = 12 data words

• 32-bytes = 16 data words

• 34-bytes = 16 data words, 1 pad word

Event code included:

• 4-bytes = event code word, 1 data word

• 8-bytes = event code word, 3 data words

• 16-bytes = event code word, 7 data words

• 24-bytes = event code word, 11 data words

• 32-bytes = event code word, 15 data words

• 34-bytes = event code word, 16 data words

If enabled, the IO-Link Master swaps the data bytes in word (2 byte) format or dword (4 byte) format. Options include:

• No byte-swap – data passed through as received

• Word (16-bit) byte-swap – data is byte-swapped in word format

• Dword (32-bit) byte-swap – data is byte-swapped in dword format

Note: Because both IO-Link and Modbus/TCP use big-endian byte

ordering, byte swapping typically is not required for word and dword data.

Byte swapping is most commonly required when sending byte (8-bit) data to the IO-Link device and it is desired to send the least significant byte of the holding register first. For these cases, word (16 bit) byte-swap is typically used.

If selected, the IO-Link Master appends any PDO data to the end of the PDI data.

• False = Do not append PDO data

• True = Append PDO data

If enabled, the IO-Link Master expects the first word of the PDO block to be used for event code handling.

Value s are:

• True = expect event code

• False = no event code, expect only PDO data

If enabled, the IO-Link Master clears any event code reported in the PDI data block after the Event Active Hold Time.

Value s are:

• True = clear event code after hold time

•False = do not clear event code after hold time

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 2. IO-Link Port Configuration - 17

Modbus/TCP Settings Parameters

Event Active Hold Time

Default: 1000 ms

Clear Event Hold Time

Default: 500 ms

Transfer Mode Settings

Slave Mode Device ID

Default: 1

PDI Receive Mode(s)

Default: Slave

PDO Transmit Mode

Default: Slave

Modbus/TCP Settings Page (Continued)

If Clear Event Code After Hold Time is enabled, the time period an event code is reported in the PDI block before it is cleared.

Valid range: 1-65535

Valid Units are:

• ms (milliseconds)

• sec (seconds)

• min (minutes)

•hours

•days

Once an event code has been cleared, the time an event code stays cleared in the PDI block before another event code can be reported.

• Valid range: 1-65535

• Valid Units:

• ms (milliseconds)

• sec (seconds)

• min (minutes)

•hours

•days

The Modbus Device ID used to access this IO-Link port.

Range: 1-247

Determines which PDI Receive (To PLC) Modes are enabled.

The selectable modes is Slave.

Note: Not selecting slave mode disables Modbus/TCP access to the

PDI data block.

Selectable Modes are:

• Disabled

•Slave

18 - Chapter 2. IO-Link Port Configuration IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

Chapter 3. Using the Diagnostics Pages

This section provides information about the following Diagnostics web pages.

• 3.1. IO-Link Port Diagnostics

• 3.2. Modbus/TCP Diagnostics on Page 22

3.1. IO-Link Port Diagnostics

The IO-Link Diagnostics page may be useful when trying to troubleshoot port issues related to IO-Link configuration.

Note: This image does not illustrate the complete Diagnostics page.

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 3. Using the Diagnostics Pages - 19

IO-Link Port Diagnostics

The following table provides information about the IO-Link Diagnostics page.

IO-Link Diagnostics

Displays the active device mode:

• Reset = The port is configured to disable all functionality.

Port Mode

• IO-Link = The port is configured to IO-Link mode.

• Digital In = The port is configured to operate as a digital input.

• Digital Out = The port is configured to operate as a digital output.

Displays the port status:

• Inactive = The port is in active state. Typically, this indicates that the device is either not attached or not detected.

• Initializing = The port is in the process of initializing.

Port Status

• Operational = The port is operational and, if in IO-Link mode, communications to the IO-Link device has been established.

• PDI Valid = The PDI data is now valid.

• Fault = The port has detected a fault and is unable to re-establish communications.

Device Vendor Name Displays the Device Vendor Name as stored in ISDU Index 16.

Device Product Name The Device Product Name as stored in ISDU Index 18.

Device Serial Number The Device Serial Number as stored in ISDU Index 21.

Device Hardware The Device Hardware Version as stored in ISDU Index 22.

Device Firmware The Device Firmware Version as stored in ISDU Index 23.

Device IO-Link Version The supported Device IO-Link Version as stored in ISDU Index 0.

Auxiliary Bit Status The current status of the auxiliary bit as received on Pin 2 of the IO-Link port.

Last Rx PDI Data (MS Byte First)

The last Rx PDI data as received from the IO-Link device.

Device PDO Data Length The supported Device PDO Data Length, in bytes, as stored in ISDU Index 0.

Lost PDO Controller(s) Errors

The number of times that the PDO controller(s) were present and then lost connection.

PDO Data Valid Status of PDO data being received from controller(s).

Device PDI Data Length The supported Device PDI Data Length, in bytes, as stored in ISDU Index 0.

PDI Data Valid Current status of PDI data as received from the IO-Link device.

Last Tx PDO Data The last Tx PDO data.

Time Since Initialization The time since the last port initialization.

Lost Communication Count

The number of times that communication has been lost to the IO-Link device.

Initialization Attempts The number of times the IO-Link port was initialized.

Initialization Errors The number of port initialization errors that occurred.

Process Data Errors The number of process data errors the port received.

Process Data Retries The number of process data retries the port performed.

Internal Communication Errors

Device Communication Errors

The number of IO-Link Master internal communication errors that occurred on this port.

The number of device specific communication errors that occurred.

20 - Chapter 3. Using the Diagnostics Pages IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

IO-Link Port Diagnostics

IO-Link Diagnostics (Continued)

ISDU Read Cmd Attempts The number of read ISDU command attempts.

ISDU Read Cmd Errors The number of read ISDU command errors.

Minimum ISDU Read Cmd Resp Time

Maximum ISDU Read Cmd Resp Time

Average ISDU Read Cmd Resp Time

Average ISDU Read Cmd Byte Time

ISDU Write Cmd Attempts

The minimum, or shortest, read ISDU command response time.

The maximum, or longest, read ISDU command response time.

The average ISDU read command response time.

The average per-byte read ISDU command response time.

The number of write ISDU command attempts.

ISDU Write Cmd Errors The number of write ISDU command errors.

Minimum ISDU Write Cmd Resp Time

Maximum ISDU Write Cmd Resp Time

Average ISDU Write Cmd Resp Time

Average ISDU Write Cmd Byte Time

The minimum, or shortest, write ISDU command response time.

The maximum, or longest, write ISDU command response time.

The average ISDU write command response time.

The average per-byte ISDU write command response time.

Total Events The total number of events that were received on this port.

First Events Up to the first, or oldest, three events that were received on this port.

Last Events Up to the last, or most recent, three events that were received on this port.

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 3. Using the Diagnostics Pages - 21

Modbus/TCP Diagnostics

3.2. Modbus/TCP Diagnostics

The Modbus/TCP Diagnostics page may be useful when trying to troubleshoot Modbus/TCP communications or port issues related to Modbus/TCP configuration.

The following table provides information about the Modbus/TCP Diagnostics page.

Modbus/TCP Diagnostics

Active Connections Displays the current number of active Modbus/TCP connections.

Messages Received from Masters

Displays the number of Modbus messages received from Modbus/TCP Masters.

Responses Sent to Masters Displays the number of Modbus responses sent to Modbus/TCP Masters.

Broadcasts Received Displays the number of broadcast Modbus/TCP messages received.

Invalid Message Length Errors

Displays the number of Modbus messages received with incorrect length fields.

Displays the number of invalid message data errors. These errors occur

Invalid Message Data Errors

when the IO-Link Master receives a message that cannot be performed due to invalid data.

22 - Chapter 3. Using the Diagnostics Pages IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

Modbus/TCP Diagnostics (Continued)

Modbus/TCP Diagnostics

Invalid Message Address Errors

Displays the number of invalid message address errors. These errors occur when the IO-Link Master receives a message that cannot be performed due to an invalid address.

Displays the number of unknown device ID errors. These errors occur when

Unknown Device ID Errors

the IO-Link Master receives a message that is addressed to a device ID other than the configured Slave Mode Device ID.

Displays the number of invalid message protocol type errors. These errors

Invalid Protocol Type Errors

occur when the IO-Link Master receives a Modbus/TCP message that specifies a non-Modbus protocol..

Unsupported Function Code Errors

Displays the number of invalid Modbus function code errors. These errors occur when the IO-Link Master receives a message that cannot be performed due to an unsupported Modbus function code.

Displays the number of improper configuration errors. These errors occur

Configuration Errors

when the IO-Link Master receives a message that cannot be performed due to an invalid configuration.

No Available Connection Errors

Displays the number of Modbus/TCP connection attempts that were rejected due to no available connections. This occurs when the number of Modbus/TCP connections has reached the limit.

Displays the number of system resource errors. These errors indicate a system error on the IO-Link such as operating system errors or full

System Resource Errors

message queues. These errors typically occur when the PLC(s) are sending messages to the IO-Link Master faster than the IO-Link Master can process them.

First Error String Text description of the first error that occurred.

Last Error String Text description of the last error that occurred.

Modbus/TCP Port Specific Diagnostics

Active PDO Controller(s)

Lists the controller interface(s) type, (Class 1 or Class 3), and IP address that are controlling the PDO data.

Displays the number of PDO write messages that were dropped due to any of the following:

• The port is configured in IO-Link mode:

PDO Writes to Offline or Read-Only Ports

- There is no device connected to the port.

- The IO-Link device is off-line.

- The IO-Link device does not support PDO data.

• The PDO Transmit Mode (To PLC) is disabled.

• The port is configured in Digital Input mode.

ISDU Request Msgs From PLC(s)

ISDU Invalid Requests

Displays the number of ISDU request messages received from the PLC(s) or other controllers. These request messages may contain one or multiple ISDU commands.

Displays the number of ISDU requests received over Modbus/TCP with one or more invalid commands.

Displays the number of ISDU requests received over Modbus/TCP when the IO-Link port was offline. This can occur when:

ISDU Requests When Port Offline

• The IO-Link port is initializing, such as after start-up.

• There is no IO-Link device attached to the port.

• The IO-Link device is not responding.

• Communication to the IO-Link device has been lost.

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 3. Using the Diagnostics Pages - 23

Modbus/TCP Diagnostics

Modbus/TCP Diagnostics (Continued)

Valid ISDU Responses From Port

ISDU Response Timeouts

Displays the number of valid ISDU response messages returned from the IO-Link port interface and available to the PLC(s). The response messages contain results to the ISDU command(s) received in the request message.

Displays the number of ISDU requests that did not receive a response within the configured ISDU Response Timeout.

Displays the number of unexpected ISDU responses. Unexpected responses

Unexpected ISDU Responses

may occur when an ISDU response is received after the ISDU request has timed out. This typically requires setting the ISDU Response Timeout to a longer value.

Maximum ISDU Request Msg Response Time

Average ISDU Request Msg Response Time

Minimum ISDU Request Msg Response Time

Displays the maximum time period required to process all commands within an ISDU request message. The response is not available until all ISDU command(s) contained in the request have been processed.

Displays the average time period required to process the ISDU request message(s). The response is not available until all ISDU command(s) contained in the request have been processed.

Displays the minimum time period required to process all commands within an ISDU request message. The response is not available until all ISDU command(s) contained in the request have been processed.

ISDU Read Commands Displays the number of ISDU read commands received over Modbus/TCP.

ISDU Write Commands Displays the number of ISDU write commands received over Modbus/TCP.

ISDU NOP Commands

Displays the number of ISDU NOP (no operation) commands received over Modbus/TCP.

24 - Chapter 3. Using the Diagnostics Pages IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

Chapter 4. Troubleshooting and Technical Support

This section provides the following information:

• 4.1. Troubleshooting

• 4.2. Contacting Technical Support on Page 26

• 4.3. Using Log Files on Page 27

4.1. Troubleshooting

Before contacting Technical Support, you may want to try the following:

• Open the IO-Link Master web interface and review the following web pages:

- IO-Link Diagnostics

- EtherNet/IP Diagnostics

- Modbus/TCP Diagnostics

• Reboot the IO-Link Master

• Verify that you are using the correct types of cables on the correct connectors and that all cables are connected securely.

• Check to make sure LEDs are not reporting an issue usingIO-Link Master 4-EIP User Guide

• Verify that the network IP address, subnet mask, and gateway are correct and appropriate for the network. Make sure that the IP address programmed into the IO-Link Master matches the unique reserved IP configured address assigned by the system administrator.

• If using DHCP, the host system needs to provide the subnet mask. The gateway is optional and is not required for a purely local network.

• Verify that the Ethernet hub and any other network devices between the system and the IO-Link Master are powered up and operating.

• If you have a spare IO-Link Master, try replacing the IO-Link Master.

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 4. Troubleshooting and Technical Support - 25

Contacting Technical Support

4.2. Contacting Technical Support

You may want to access the Help/SUPPORT page when you call Technical Support, as they may request the information displayed on the SUPPORT page.

Comtrol Technical Support is available from 8:00AM to 6:00PM (CST), Monday through Friday, excluding major USA holidays.

Contact Information

Phone 763.957.6000

Downloads ftp://ftp.comtrol.com/html/default.htm

Web Site http://www.comtrol.com

26 - Chapter 4. Troubleshooting and Technical Support IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

Using Log Files

4.3. Using Log Files

Log files are available in the IO-Link Master web page. The IO-Link Master provides four different log files that you can view, export, or clear:

• Syslog (system log) displays line-by-line activity records.

• dmesg displays Linux kernel messages.

• top displays which programs are using most of the memory and CPU.

• ps displays the running programs

• All log files start up automatically during the startup cycle. Each log file has a size limit of 100KB.

Note: Typically, log files are intended to be used by Technical Support in the event there is a problem.

You can use the following procedures to:

• 4.3.1. View a Log File on Page 27

• 4.3.2. Clear a Log File on Page 28

• 4.3.3. Export a Log File on Page 28

4.3.1. View a Log File

Use this procedure to view a log file.

1. Open the IO-Link Master web interface using one of these method:

• From PortVision DX, highlight the IO-Link Master and click the Webpage button or right-click the IO-

Link Master in the Device List pane and click Webpage.

• Open your browser and enter the IP address of the IO-Link Master.

2. Click Advanced and then LOG FILES.

3. Select the log file type from the drop-list.

4. Optionally, click the REFRESH button to get the latest information.

5. Optionally, export

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 4. Troubleshooting and Technical Support - 27

the log file.

Clear a Log File

4.3.2. Clear a Log File

Use this procedure to clear a log file.

1. Open the IO-Link Master web interface using one of these method:

• From PortVision DX, highlight the IO-Link Master and click the Webpage button or right-click the IOLink Master in the Device List pane and click Webpage.

• Open your browser and enter the IP address of the IO-Link Master.

2. Click Advanced and then LOG FILES.

3. Optionally, export

4. Select the log file type from the drop-list.

5. Click the CLEAR button.

the log file.

The log file automatically starts logging the latest information.

4.3.3. Export a Log File

Use the following procedure to export a log file.

1. Open the IO-Link Master web interface using one of these method:

• From PortVision DX, highlight the IO-Link Master and click the Webpage button or right-click the IOLink Master in the Device List pane and click Webpage.

• Open your browser and enter the IP address of the IO-Link Master.

2. Click Advanced and then LOG FILES.

3. Select the log file type from the drop-list.

4. Click the EXPORT button.

28 - Chapter 4. Troubleshooting and Technical Support IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

Export a Log File

5. Click the Save button drop-list and click Save to save it to your user folder or Save as to browse to or create

a new folder in which to place the log file.

6. Depending on your operating system, you may need to close the pop-up window.

IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A Chapter 4. Troubleshooting and Technical Support - 29

Export a Log File

30 - Chapter 4. Troubleshooting and Technical Support IO-Link Master Modbus/TCP Reference Manual: 2000590 Rev. A

Comtrol IOLM Modbus TCP User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Table of Contents

Chapter 1. Modbus/TCP Interface

1.1. Modbus Function Codes

1.2. Modbus Address Definitions

1.3. Multiple Port Process Data (PDI and PDO) Access via Modbus TCP

Chapter 2. IO-Link Port Configuration

2.1. IO-Link Settings Configuration Page

2.1.1. Editing IO-Link Settings

2.1.2. IO-Link Settings Parameters

2.2. Modbus/TCP Settings Configuration Page

2.2.1. Editing Modbus/TCP Settings

2.2.2. Modbus/TCP Settings Parameters

Chapter 3. Using the Diagnostics Pages

3.1. IO-Link Port Diagnostics

3.2. Modbus/TCP Diagnostics

Chapter 4. Troubleshooting and Technical Support

4.1. Troubleshooting

4.2. Contacting Technical Support

4.3. Using Log Files

4.3.1. View a Log File

4.3.2. Clear a Log File

4.3.3. Export a Log File