MOXA 5435 Series Protocol Gateways User Manual

: July 11, 2024
: MOXA

Table of Contents

MOXA 5435 Series Protocol Gateways
Product Information
Product Usage Instructions
FAQs
Introduction
Getting Started
Web Console Configuration and Troubleshooting
Protocol Settings
Local Log Settings
Security
Maintenance
CIP Objects of EtherNetIP
Common Service List
References
Read User Manual Online (PDF format)
Download This Manual (PDF format)

MOXA 5435 Series Protocol Gateways

Product Information

Specifications:

Product Name: MGate 5135/5435 Series
Power Input: 12 to 48 VDC
Network Interface: 10/100M Ethernet port
Supported Devices: Modbus serial devices

Product Usage Instructions

1. Connecting the Power:

Connect the 12 to 48 VDC power line or DIN-rail power supply to the MGate’s power terminal block.
Tighten the screws on both sides of the terminal block.
Turn on the power source.

Note: The unit does not have an on/off switch. It automatically turns on when it receives power. The PWR LED on the top panel will glow to show that the unit is receiving power.

2. Connecting Serial Devices:

The MGate supports Modbus serial devices. Before connecting or removing the serial connection, ensure the power is turned off.

3. Connecting to a Network:

Connect one end of the Ethernet cable to the MGate’s 10/100M Ethernet port and the other end to the Ethernet network.

4. Installing DSU Software:

If you do not know the MGate gateway’s IP address, use an Ethernet cable to connect the host PC and MGate gateway directly.
Download the Device Search Utility (DSU) from Moxa’s website.
Locate and run the setup program to install DSU following the on-screen instructions.

FAQs

Q: How can I find the default IP address of the MGate gateway?
- A: The default IP address is 192.168.127.254. You can use the Device Search Utility (DSU) to detect the MGate gateways on your network.

MGate 5135/5435 Series User Manual
Version 1.2, July 2024 www.moxa.com/products
© 2024 Moxa Inc. All rights reserved.

MGate 5135/5435 Series User Manual
The software described in this manual is furnished under a license agreement and may be used only in accordance with the terms of that agreement.
Copyright Notice
© 2024 Moxa Inc. All rights reserved.
Trademarks
The MOXA logo is a registered trademark of Moxa Inc. All other trademarks or registered marks in this manual belong to their respective manufacturers.
Disclaimer
· Information in this document is subject to change without notice and does not represent a commitment on the part of Moxa.
· Moxa provides this document as is, without warranty of any kind, either expressed or implied, including, but not limited to, its particular purpose. Moxa reserves the right to make improvements and/or changes to this manual, or to the products and/or the programs described in this manual, at any time.
· Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes no responsibility for its use, or for any infringements on the rights of third parties that may result from its use.
· This product might include unintentional technical or typographical errors. Changes are periodically made to the information herein to correct such errors, and these changes are incorporated into new editions of the publication.
Technical Support Contact Information
www.moxa.com/support

Introduction

The MGate 5135/5435 gateways are 1- and 4-port industrial Ethernet gateways, with the former for Modbus RTU/ASCII/TCP and the latter for EtherNet/IP network communications. To integrate existing Modbus devices onto an EtherNet/IP network, use the MGate 5135/5435 gateway as a Modbus client to collect data and exchange data with EtherNet/IP host. All models are protected by a rugged and compact metal housing, are DIN-rail mountable, and offer built-in serial isolation. The rugged design is suitable for industrial applications such as factory automation, power, oil and gas, water and wastewater, and other process automation industries.

MGate 5135/5435 Series User Manual

5

Getting Started

Connecting the Power
The unit can be powered by connecting a power source to the terminal block:
1. Connect the 12 to 48 VDC power line or DIN-rail power supply to the MGate’s power terminal block. 2. Tighten the screws on both sides of the terminal block. 3. Turn on the power source.
Note that the unit does not have an on/off switch. It automatically turns on when it receives power. The PWR LED on the top panel will glow to show that the unit is receiving power. For power terminal block pin assignments, refer to the Quick Installation Guide, Power Input and Relay Output Pinout section.
Connecting Serial Devices
The MGate supports Modbus serial devices. Before connecting or removing the serial connection, first make sure the power is turned off. For the serial port pin assignments, refer to the Quick Installation Guide, Pin Assignments section.
Connecting to a Network
Connect one end of the Ethernet cable to the MGate’s 10/100M Ethernet port and the other end of the cable to the Ethernet network. The MGate will show a valid connection to the Ethernet in the following ways:
· The Ethernet LED maintains a solid green color when connected to a 100 Mbps Ethernet network. · The Ethernet LED maintains a solid orange color when connected to a 10 Mbps Ethernet network. · The Ethernet LED will flash when Ethernet packets are being transmitted or received.
Installing DSU Software
If you do not know the MGate gateway’s IP address when setting it up for the first time (default IP is 192.168.127.254); use an Ethernet cable to connect the host PC and MGate gateway directly. If you connect the gateway and host PC through the same Ethernet switch, make sure there is no router between them. You can then use the Device Search Utility (DSU) to detect the MGate gateways on your network. You can download DSU from Moxa’s website: www.moxa.com.
The following instructions explain how to install the DSU, a utility to search for MGate units on a network.
1. Locate and run the following setup program to begin the installation process: dsusetup[Version]Build[DateTime].exe This version might be named dsu_setup_Ver2.x_Build_xxxxxxxx.exe
2. The Welcome window will greet you. Click Next to continue. 3. When the Select Destination Location window appears, click Next to continue. You may change the
destination directory by first clicking on Browse…. 4. When the Select Additional Tasks window appears, click Next to continue. You may select Create a
desktop icon if you would like a shortcut to the DSU on your desktop. 5. Click Install to copy the software files. 6. A progress bar will appear. The procedure should take only a few seconds to complete. 7. A message will show the DSU has been successfully installed. You may choose to run it immediately by
selecting Launch DSU. 8. You may also open the DSU through Start > Programs > MOXA > DSU.

MGate 5135/5435 Series User Manual

6

The DSU window should appear as shown below. Click Search and a new Search window will pop up.
Log In to the Web Console
Use the Web console to configure the MGate through Ethernet or verify the MGate’s status. Use a web browser, such as Google Chrome to connect to the MGate, using the HTTPS protocol. When the MGate gateway appears on the DSU device list, select the gateway and right-click the mouse button to open a web console to configure the gateway. On the login page, create an account name and set a password that is at least 8 characters long when you log in for the first time. Or if you have already an account, log in with your account name and password. If you change the MGate’s IP and other related network settings, click SAVE, and the MGate will reboot.

microSD
The MGate provides users with an easy way to back up, copy, replace, or deploy. The MGate is equipped with a microSD card slot. Users can plug in a microSD card to back up data, including the system configuration settings.
First time use of a new microSD card with the MGate gateway
1. Format the microSD card as FAT file system through a PC. 2. Power off the MGate and insert the microSD card (ensure that the microSD card is empty). 3. Power on the MGate. The default settings will be copied to the microSD card. 4. Manually configure the MGate via web console, and all the stored changes will be copied to the microSD
card for synchronization.
First time use of a microSD card containing a configuration file with the MGate gateway
1. Power off the MGate and insert the microSD card. 2. Power on the MGate. 3. The configuration file stored in the microSD card will automatically be copied to the MGate.

MGate 5135/5435 Series User Manual

7

Duplicating current configurations to another MGate gateway
1. Power off the MGate and insert a new microSD card. 2. Power on the MGate. 3. The configuration will be copied from the MGate to the microSD card. 4. Power off the MGate and insert the microSD card to the other MGate. 5. Power on the second MGate. 6. The configuration file stored in the microSD card will automatically be copied to the MGate.
Malfunctioning MGate replacement
1. Replace the malfunctioning MGate with a new MGate. 2. Insert the microSD card into the new MGate. 3. Power on the MGate. 4. The configuration file stored on the microSD card will automatically be copied to the MGate.
microSD card writing failure
The following circumstances may cause the microSD card to experience a writing failure:
1. The microSD card has less than 20 Mbytes of free space remaining. 2. The microSD card is write-protected. 3. The file system is corrupted. 4. The microSD card is damaged.
The MGate will stop working in case of the above events, accompanied by a flashing Ready LED and beeping alarm. When you replace the MGate gateway’s microSD card, the microSD card will synchronize the configurations stored on the MGate gateway. Note that the replacement microSD card should not contain any configuration files on it; otherwise, the out-of-date configuration will copy to the MGate device.

MGate 5135/5435 Series User Manual

8

Web Console Configuration and Troubleshooting

This chapter provides a quick overview of how to configure the MGate 5135/5435 by web console.
System Dashboard
This page gives a system dashboard of the MGate 5135/5435 gateway.
You can change your password or log out using the options on the top-right corner of the page.

MGate 5135/5435 Series User Manual

9

System Settings

System Settings–General Settings
On this page, you can change the name of the device and time settings.

System Settings

Parameter

Value

Host Name

Alphanumeric string

Description

Alphanumeric string

Description Enter a name that can help you uniquely identify the device. For example, you can include the name and function of the device. (optional) You can include additional description about the device such as function and location.

Time Settings
The MGate has a built-in real-time clock for time-calibration functions. Functions such as logs use the realtime clock to add the timestamp to messages.

ATTENTION
First-time users should select the time zone first. The console will display the actual time in your time zone relative to the GMT. If you would like to change the real-time clock, select Local time. MGate’s firmware will change the GMT time according to the Time Zone setting.

MGate 5135/5435 Series User Manual

10

Parameter

Value

Time zone

User-selectable time zone

Daylight saving Enable

time

Disable

Manual

Sync Mode

Auto

Description Shows the current time zone selected and allows change to a different time zone. Enable and set up the daylight saving time; or, disable daylight saving time. Use this setting to manually adjust the time (1900/1/12037/12/31) or sync with the browser time Specify the IP or domain of the time server to sync with (E.g., 192.168.1.1 or time.stdtime.gov.tw). This optional field specifies the IP address or domain name of the time server on your network. The module supports SNTP (RFC-1769) for automatic time calibration. The MGate will request the time information from the specified time server per the set configured time.

MGate 5135/5435 Series User Manual

11

System Settings–Network Settings
You can change the IP Configuration, IP Address, Netmask, Default Gateway, and DNS settings on the Network Settings page.

Parameter

Value

Description

The Switch mode allows users to install the device with daisy-

chain topology.

The Dual IP mode allows the gateway to have two different IP

LAN Mode

Switch, Dual IP, Redundant LAN

addresses, each with distinct netmask and gateway settings. The IP addresses can have the same MAC address. The Redundant LAN mode allows users to use the same IP

address on both Ethernet ports. The default active LAN port is

ETH1 after bootup. If the active LAN link is down, the device

will automatically switch to the backup LAN ETH2.

Select Static IP if you are using a fixed IP address. Select the

IP Configuration DHCP, Static IP

DHCP option if you want the IP address to be dynamically

assigned.

IP Address

192.168.127.254 (or other 32-bit number) The IP Address identifies the server on the TCP/IP network.

MGate 5135/5435 Series User Manual

12

Parameter

Value

Description

Netmask

255.255.255.0 Identifies the server as belonging to a Class A, B, or C network.
(or other 32-bit number)

Gateway

0.0.0.0

The IP address of the router that provides network access

(or other 32-bit number) outside the server’s LAN.

Preferred DNS Server

0.0.0.0 (or other 32-bit number)

The IP address of the primary domain name server.

Alternative DNS 0.0.0.0

The IP address of the secondary domain name server.

Server

(or other 32-bit number)

System Settings–Serial Settings
The serial interface supports RS-232, RS-422, and RS-485 interfaces. You must configure the baudrate, parity, data bits, and stop bits before using the serial interface for the Modbus RTU/ASCII protocol. Incorrect settings will cause communication failures.

MGate 5135/5435 Series User Manual

13

Click the “pen” icon to configure serial port parameters, such as the interface, baudrate, terminator, and pull-up/pull-down resistor.

Parameter Alias
Interface
Terminator Pull-up and Pulldown Resistor Baudrate
Parity Data Bits Stop Bits

Value

Description

Alphanumeric

Allows you to define an alias to a port for easier identification.

string

Max. 16 characters.

RS-232, RS-422,

RS-485 2-wire,

RS-485 4-wire

Default is none, which means the terminator is disabled. Try to

120, None

enable the 120 when the communication has issues, especailly

for long distance communication.

1k, 150k

Default value is 150 k. Set the value depending on the system requirements.

300 bps to

The baudrate value can be also self-defined if it is between 300

921600 bps

bps to 921600 bps.

None, Odd,

Even, Mark,

Space

5, 6, 7, 8

1, 2

MGate 5135/5435 Series User Manual

14

Parameter FIFO

Value Enable, Disable

Description The internal buffer of UART. Disabling FIFO can reduce the latency time when receiving data from serial communications, but this will also slow down the throughput.

RTS Toggle
The RTS Toggle function is available only in the RS-232 mode. This flow- control mechanism is achieved by toggling the RTS pin in the transmission direction through a software setting. Data is transmitted after the RTS pin is toggled ON for the specified time interval. After the data transmission is finished, the RTS pin will toggle OFF for the specified time interval automatically.

Parameter Flow Control (only for RS232 mode) RTS on delay RTS off delay

Value None, RTS/CTS, RTS Toggle 0 to 100 ms 0 to 100 ms

Description The RTS Toggle will turn off RTS signal when there is no data to be sent. If there is data to be sent, the RTS toggle will turn on the RTS signal before a data transmission and off after the transmission is completed. Only available for the RS-232 mode to implement the RTS Toggle function. Only available for the RS-232 mode to implement the RTS Toggle function.

System Settings–SNMP Settings

System Settings–SNMP Settings–SNMP Agent

Parameters Version Contact
Location

Description The SNMP version; the MGate supports SNMP V1, V2c, and V3. The optional contact information usually includes an emergency contact name and telephone number. The location information. This string is usually set to the street address where the MGate is physically located.

MGate 5135/5435 Series User Manual

15

Parameters Read Only Community
Read/Write Community Minimum Authentication/Privacy Password Length

Description A text password mechanism that is used to weakly authenticate queries to agents of managed network devices. A text password mechanism that is used to weakly authenticate changes to agents of managed network devices.
Minimum Authentication/Privacy Password Length must be between 8 and 64.

Read-only and Read/write Access Control

You can define usernames, passwords, and authentication parameters in SNMP for two levels of access control: read-only and read/write. The access level is indicated in the value of the Authority field. For example, Read-only authentication mode allows you to configure the authentication mode for read- only access, whereas Read/Write authentication mode allows you to configure the authentication mode for read/write access. For each level of access, you may configure the following:

Parameters Account Name Authority
Authentication Type
Privacy Type

Value
Read Only Read/Write Disable (Default) MD5 SHA1 SHA-224 SHA-256 SHA-384 SHA-512 Disable (Default) DES-CBC AES-128

Description The username for which the access level is being defined. The level of access allowed
Use this field to select MD5 or SHA as the method of password encryption for the specified level of access, or to disable authentication.
Use this field to enable or disable data encryption for the specified level of access. If you enable a privacy type, please also configure the privacy password.

MGate 5135/5435 Series User Manual

16

If you need to change the SNMP Account settings created previously, click on the button on right of the configured SNMP item to change settings, such as Authentication Type, or Privacy Type.

Parameters
Max Authentication Failure
Each Authentication Failure Timeout (min)
Account Disabled Time Interval (min)

Value 1 to 10 (default 5) 1 to 1440 (default 10)
1 to 60 (default 10)

Description Specifies a maximum number of authentication failures. If this number is exceeded, the MGate will disable SNMPv3. Specifies a timeout period when enabling the Timeout for authentication failure function When the number of authentication failures exceeds the value set in Max Authentication Failure Times, the MGate will disable the SNMPv3 for Account Disabled Time Interval.

MGate 5135/5435 Series User Manual

17

System Settings–SNMP Settings–SNMP Trap
Set up the SNMP trap server to send the trap events, such as warning messages. Configure the SNMP trap server by inputting the server’s IP or domain name.

Parameters Server IP Port
Trap Version

Description SNMP server IP address or domain name; the maximum number of trap servers is 2 SNMP server IP Port. Disable SNMPv1 SNMPv2c SNMPv3

MGate 5135/5435 Series User Manual

18

Protocol Settings

Protocol Settings–Modbus Client Settings
You can manage Modbus devices and their Modbus command tables on this page.
The MGate supports csv file import/export for Modbus settings, it is easy to use when you back up the settings or during installation stage.
Click TCP or the serial port column to set up the Modbus device. Configure the basic setting for Modbus TCP by clicking the icon next to the Operation Mode: TCP.

MGate 5135/5435 Series User Manual

19

Parameter Value

Default

Initial delay 0 to 30000 ms 0

Maximum

0 to 5

3

Retry

Response Timeout

10 to 120000 ms 1000

Description Some Modbus servers/slaves may take more time to boot up than other devices. In some environments, this may cause the entire system to experience repeated exceptions during the initial boot-up. After booting up, you can force the MGate to wait before sending the first request with the Initial Delay setting. This is used to configure how many times the MGate will try to communicate with the Modbus server/slave when the Modbus command times out. Based on the Modbus standard, the device manufacturer defines the time a server/slave device takes to respond to a request. A Modbus client/master can be configured to wait a certain amount of time for a server/slave’s response. If no response is received within the specified time, the client/master will disregard the request and continue operation. This allows the Modbus system to continue the operation even if a server/slave device is disconnected or faulty. On the MGate, the Response timeout field is used to configure how long the gateway will wait for a response from a Modbus server/slave. Refer to your device manufacturer’s documentation to manually set the response timeout.

Add the Modbus device by clicking the ADD DEVICE button

MGate 5135/5435 Series User Manual

20

Step 1: Add Modbus device information

Parameter Device Name
Slave IP

Value Alphanumeric string 0.0.0.0 to 255.255.255.255

Slave Port

1 to 65535

Slave ID

1 to 255

Default
0.0.0.0 502 1

Description Max. 32 characters.
The IP address of a remote server/slave device.
The TCP port number of a remote server/slave device. The Modbus server/slave ID.

MGate 5135/5435 Series User Manual

21

Step 2: Add Modbus commands

Parameter

Value

Default

Command Name Alphanumeric string

1 Read Coils

2 Read Discrete Inputs

3 Read Holding Registers

4 Read Inputs Registers

5 Write Single Coil

Function

6 Write Single Register

15 Write Multiple Coils

16 Write Multiple

Registers

23 Read/Write Multiple

Registers

Trigger

Cyclic Data Change Disable

Poll Interval (this will show up when user select trigger mode `cyclic’)

100 to 1200000 ms

1000

Description Max. 32 characters.
When a message is sent from a client to a server device, the function code field tells the server what kind of action to perform.
Disable: The command was never sent Cyclic: The command is sent cyclically at the interval specified in the Poll Interval parameter. Data change: A command is issued when a change in data is detected. Polling intervals are in milliseconds. Since the module sends all requests in turns, the actual polling interval also depends on the number of requests in the queue and their parameters. The range is from 100 to 1,200,000 ms.

MGate 5135/5435 Series User Manual

22

Parameter

Value

Default

Endian Swap

None Byte Word Byte and Word

None

Read Starting Address
Read Quantity
Write Starting Address Write Quantity

0 to 65535

0

Read Coils: 1 to 2000

Read Discrete Inputs: 1 to

2000

Read Inputs Registers: 1 to

125

10

Read Holding Registers: 1 to

125

Read/Write Multiple Registers:

1 to 125

0 to 65535

0

Write Multiple Coils: 1 to 1968

Write Multiple Registers:

1 to 123

1

Read/Write Multiple Registers:

1 to 123

Keep latest data Fault Protection Clear all data bits to 0
Set to user defined value

User-defined Value (This will show up when you select Fault 00 to FF (Hex) Protection mode as Set to user defined value’) Fault Timeout (This will show up when you select Fault Protection 1 to 86400 ms mode asSet to user defined value’)

00 00 3600

Tag Type

raw, boolean, int16, int32,

int64, uint16, uint32,

raw

uint64, float, double, string

Description Data Byte Swapping None: Don’t need to swap Byte: 0x0A, 0x0B, 0x0C, 0x0D becomes 0x0B, 0x0A, 0x0D, 0x0C Word: 0x0A, 0x0B, 0x0C, 0x0D becomes 0x0C, 0x0D, 0x0A, 0x0B. Byte and Word: 0x0A, 0x0B, 0x0C, 0x0D becomes 0x0D, 0x0C, 0x0B, 0x0A.
Modbus register address.

Specifying how many items to read.

Modbus register address.
Specifying how many items to write into.
If the MGate’s connection to the other side in a server mode fails, the gateway cannot receive data, but the gateway will continuously send output data to the Modbus device. To avoid problems in this case, the MGate can be configured to react in one of the following three ways: Keep the latest data, clear data to zero, set the data bits to user-defined values.
The user-defined values to write into the data bits when the Set to user defined value option is selected.

Defines the communication timeout for the opposite side (in a server role).

Specifying the tag data type. The default is raw

for fast multiple data mapping.
For other data types, user could also scale the
resource data. There are two types:
· Slope-intercept: tag value = (source value * slope) +offset
· Point-slope: tag value = target min + (source value –

target max. – target min.

source min) * (

)

source max. – source min.

MGate 5135/5435 Series User Manual

23

Step 3: Quick review result, click DONE to finish
If you already have backed up a frequently used meter profile, just import or export one Modbus device CSV file.

MGate 5135/5435 Series User Manual

24

Follow the same steps for Modbus RTU/ASCII basic settings and devices settings in serial port.

Parameters
Inter-frame delay (only for Modbus RTU)

Description Defines the time interval between an RTU response and the next RTU request. The system will automatically determine the delay time of the data frame transmission from the server device to the upstream. When the baudrate is lower than 19200 bps, the default is 3.5 character time. When the baudrate is larger than 19200 bps, the MGate uses a predefined fixed value that is not user-configurable. This function solves the issue when some devices can’t handle the RTU requests that quickly, so the MGate opens to user-defined values. You may choose to set the delay time manually by unchecking this option. The value range is 10 to 500 ms.
How to calculate Modbus character time? E.g., if the baudrate is 9600 bps, 1 character time is about 1 ms. In a serial frame (11 bits, including start bit, data, parity bit, and stop bit), 9600 bps approximately equals to 960 characters/s, so transmitting one character needs about 1/960 = 1 ms.

MGate 5135/5435 Series User Manual

25

Parameters
Inter-character timeout (only for Modbus RTU)

Description The time interval between characters in one frame. When the serial side of the MGate receives one character, and the next one comes after the “inter-character timeout” defined, the frame will be discarded because of timeout.
The system will automatically determine the timeout interval between characters for Modbus devices. When the baudrate is lower than 19200 bps, the default is 1.5 character time. When the baudrate is larger than 19200 bps, MGate uses a predefined fixed value that is not user-configurable. You may choose to set the timeout interval manually by unchecking this option. The value range is 10 to 500 ms.

After configuring all Modbus TCP or Modbus RTU/ASCII settings, please remember to click GO TO APPLY SETTING and press the APPLY button at the bottom right- hand side corner.

MGate 5135/5435 Series User Manual

26

Protocol Settings–EtherNet/IP Adapter Settings
You can configure the EtherNet/IP adapter setting on this page.
Click EDIT to adjust the EtherNet/IP basic settings.

Parameter

Value

Encapsulation

0 to 3600, (0

inactivity timeout for disable)

(sec)

Default 120

Description Unit: second If there is no data exchange in for a while, the Ethernet/IP connection will be disconnected.

MGate 5135/5435 Series User Manual

27

Click on the Connection button to add O -T and T-O data. Click EDIT in the connection column to adjust the connection parameters

MGate 5135/5435 Series User Manual

28

Parameter

Value

Name

O->T connection point T->O connection point O->T (Output) data size (bytes)

1 to 2147483647 1 to 2147483647
0 to 496

T->O (Input) data size (bytes) 0 to 496

Default Connection[x] 100 110 0
0

Description Name for connection. For example, Connection1 EtherNet/IP connection instance EtherNet/IP connection instance Unit: byte O->T: Originator to Target Unit: byte T->O: Target to Originator

Add Tags for O->T and T-O. Notice that the tags must be created in Modbus Client. Click DONE on finishing the selection. The selection sequence will also decide the sequence in the EtherNet/IP data frame.

The selected tags will display in the data mapping column by default with byte offset. You may adjust the offset in the EtherNet/IP IO data frame manually.

MGate 5135/5435 Series User Manual

29

Diagnostics
Diagnostics–Protocol Diagnostics
Diagnostics–Protocol Diagnostics–Modbus RTU/ASCII Diagnostic
The MGate provides status information for Modbus RTU/ASCII/TCP, EtherNet/IP troubleshooting. Verify data or packet counters to make sure the communications are running smoothly.

MGate 5135/5435 Series User Manual

30

Diagnostics–Protocol Diagnostics-Modbus TCP Diagnostics Diagnostics–Protocol Diagnostics-EtherNet/IP Diagnostics

MGate 5135/5435 Series User Manual

31

Diagnostics–Protocol Traffic
Diagnostics–Protocol Traffic-Modbus RTU/ASCII Traffic
To troubleshoot efficiently, the MGate provides a traffic monitoring function that can capture communication traffic for all protocols. These logs present the data in an intelligent, easy-to-understand format with clearly designated fields, including source, destination, function code, and data. Save the complete log in a file by clicking EXPORT csv file.
Diagnostics–Protocol Traffic-Modbus TCP Traffic
Diagnostics–Event Log
Diagnostics–Event Log-Log View
You can review and export all event information in the event log.

MGate 5135/5435 Series User Manual

32

Diagnostics–Event Log-Policy Settings
The event policy settings enable the MGate to record important events, which can be recorded in the Remote Log to Syslog server and Local Log, which will be stored with up to 10,000 events in the MGate.
The MGate can also send email alerts, SNMP Trap messages, or open/close the circuit of the relay output when a selected event was triggered.
You can filter events for easy reading or expand by clicking the category, such as System. Tick or untick the events if you want to log it and select which channels you want to use by clicking the channel name. After changing the settings, please remember to SAVE it.

Event Group System Network Security
Maintenance
Modbus EtherNet/IP

Description Start system, User trigger reboot, Power input failure, NTP update failure IP conflict, DHCP get IP/renew, IP changed, Ethernet link down Clear event log, Login success, Login failure, Account/group changed, Password reached lifetime, SSL certificate import, Syslog certificate import Firmware upgrade success, Firmware upgrade failure, Configuration import success, Configuration import failure, Configuration export, Configuration changed, Load factory default Server connected, Server disconnected, Command recovered, Command fail Adapter connected; Adapter disconnected

Local Log Settings

MGate 5135/5435 Series User Manual

33

Local Log Settings

Description

Overwrites the oldest event log Event Log Overwrite Policy Stops recording event log

Capacity Threshold (%) When the log amount exceeds the warning

Warning By

SNMP Trap Email

Remote Log Settings

MGate 5135/5435 Series User Manual

34

Remote Log Settings Syslog Server IP Syslog Server port TLS Authentication
SNMP Trap Settings

Description IP address of a server that will record the log data 514 Enable TLS authentication. Notice TLS files must be uploaded for a successful connection.

Email Settings

Parameters

Description

Mail Server (SMTP) The mail server’s domain name or IP address.

Port

The mail server’s IP port.

TLS

Security

STARTTLS

Connection

STARTTLS-None

None

MGate 5135/5435 Series User Manual

35

Parameters Username Password From (Email address) To (Email address, separated by semicolon)

Description This field is for your mail server’s username, if required. This field is for your mail server’s password, if required. Email address from which automatic email warnings will be sent.
Email addresses to which automatic email warnings will be sent.

Diagnostics–Tag View
This page displays the tag live value generated by field devices and updates the values periodically. It is an easy and useful tool if you want to check whether the MGate receives the correct data from field devices. The gateway timestamp shows the time data was updated to the tag.

You can write a value to the Modbus via Direct Write Value to test the communication with Modbus device.

MGate 5135/5435 Series User Manual

36

Diagnostics–Network Connections
You can see network-related information, including protocol, address, and state.
Diagnostics–Ping
This network testing function is available only in the web console. The MGate gateway will send an ICMP packet through the network to a specified host, and the result can be viewed on the web console immediately.

MGate 5135/5435 Series User Manual

37

Diagnostics–LLDP
You can see LLDP related information, including Port, Neighbor ID, Neighbor Port, Neigh Port Description, and Neighbor System. Also, you can adjust the transmit interval for LLDP by clicking the EDIT button.
After clicking EDIT, if you need to enable or disable LLDP service, click on the “Service” hyperlink or navigate to Security > Service page to enable/disable it.

MGate 5135/5435 Series User Manual

38

Security

Security–Account Management
Security–Account Management–Accounts
Only the Administrator group can create or edit accounts for user management. Click CREATE to add new accounts. Click the dot icon to edit the account.

Parameters Group

Value
Administrator, Operator, Guest

Description Users can change the password for different accounts. The MGate provides three build-in account groups: administrator, operator and guest. Administrator account can access all settings. Operator accounts can access most settings, except security categories. Guest account can only view the overview page. You can create your own group for account management.

MGate 5135/5435 Series User Manual

39

Security–Account Management–Groups
Three MGate build-in types of groups are shown; you can also create your own group by clicking CREATE.

MGate 5135/5435 Series User Manual

40

Parameters

Value

Basic Information

No display

Access Permissions Read only

Read write

Description Includes Name and Description for the new Group. Corresponding to the configuration menu on the left-hand side of the web console, you can select different permissions for a new group. Displays will not show the page on the right-hand side menu.

Security–Account Management–Password Policy

Parameter

Value

Password Minimum Length 8 to 128

Password Complexity Strength

Check

Password Lifetime Setting

90 to 180 days

Description The minimum password length Select how the MGate checks the password’s strength Set the password’s lifetime period.

MGate 5135/5435 Series User Manual

41

Security–Service

Parameter HTTP Service

Value Enable/Disable

HTTPS Service

Enable/Disable

Ping Service

Enable/Disable

SD Card

Enable/Disable

SNMP Agent Service Enable/Disable

LLDP Service

Enable/Disable

Reset button disable Always enable and

after 60 sec

disable after 60 sec.

Description To enhance security, all HTTP requests will redirect to HTTPS when the HTTP service is enabled. You can also disable the HTTP service. Disabling this service will disable the web console and search utility connections, thus cutting off access to the configuration settings. To re-enable the HTTPS communication, reset to the factory default settings via the hardware Reset button. Disabling this service will block ping requests from other devices. Disabling this service will deactivate the SD card function for backup and restore configuration files. Enable or disable SNMP agent function. Enable or disable LLDP function. The MGate provides a Reset button to load factory default settings. For enhanced security, users can disable this function. In the disabled mode, the MGate will still enable the Reset button for 60 seconds after bootup just in case you really need to reset the device.

MGate 5135/5435 Series User Manual

42

Security–Allow List
These settings are used to restrict access to the MGate by the IP address. Only IP addresses on the list will be allowed to access the device. Notice the restriction includes configuration and protocol conversion.

MGate 5135/5435 Series User Manual

43

Security–DoS Defense
Users can select from several options to enable DoS Defense in order to fend off cybersecurity attacks. A denial-of-service (DoS) attack is an attempt to make a machine or a network resource unavailable. Users can select from the following options to counter DoS attacks.

MGate 5135/5435 Series User Manual

44

Security–Login Policy
Login Message
You can input a message for Login or for Login authentication failure messages.
Login Lockout

Parameter Max Failure Retry Times
Reset Period (min)
Lockout Time(min)

Value
1 to 10 (default 5)
1 to 1440 (default 10) 1 to 60 (default 10)

Description You can specify the maximum number of failure retries. If retry times are exceeded, the MGate will lock out for that account login. You can specify the reset period time when enabling the “reset the login failure counter” function When the number of login failures exceeds the threshold, the MGate will lock out for a period.

MGate 5135/5435 Series User Manual

45

Login Session

Parameter Maximum login users for HTTP+HTTPS Auto logout setting (min.)

Value 1 to 10 (default 5) 1 to 1440 (default 1440)

Description The number of users that can access the MGate at the same time.
Sets the auto logout period.

Security–Certificate Management
Use this function to load the Ethernet SSL certificate. You can import or delete SSL certificate/key files. This function is only available for the web console.

MGate 5135/5435 Series User Manual

46

Maintenance

Maintenance–Configuration Import/Export
There are three main reasons for using the Import and Export functions:
· Applying the same configuration to multiple units. The Import/Export configuration function is a convenient way to apply the same settings to units at different sites. You can export the configuration as a file and then import the configuration file onto other units.
· Backing up configurations for system recovery. The export function allows you to export configuration files that can be imported onto other gateways to restore malfunctioning systems within minutes.
Troubleshooting. Exported configuration files help administrators to identify system problems that provide useful information for Moxa’s Technical Service Team when maintenance visits are requested.
For cybersecurity reason, you can export configuration file with an authentication key, length from 8 to 16 characters. If the key to the imported configuration file differs from the key to the exported file, the import process will fail.

MGate 5135/5435 Series User Manual

47

Maintenance–Firmware Upgrade
Firmware updates for the MGate are available on the Moxa website. After you have downloaded the new firmware onto your PC, you can use the web console to write it onto your MGate. Select the desired unit from the list in the web console and click Submit to begin the process.
ATTENTION
DO NOT turn off the MGate power before the firmware upgrade process is completed. The MGate will erase the old firmware to make room for the new firmware to flash memory. If you power off the MGate and end the progress, the flash memory will contain corrupted firmware, and the MGate will fail to boot. If this happens, contact Moxa RMA services.
Maintenance–Load Factory Default
To clear all the settings on the unit, use the Load Factory Default to reset the unit to its initial factory default values.
ATTENTION
Load Default will completely reset the configuration of the unit, and all the parameters you have saved will be discarded. Do not use this function unless you are sure you want to completely reset your unit.

MGate 5135/5435 Series User Manual

48

Restart
You can reboot the MGate by clicking the RESTART button.
ATTENTION
Unsaved configuration files will be discarded during a reboot.
Status Monitoring
The Status Monitoring function provides status information of field devices when the MGate is being used as a Modbus client. If a Modbus device fails or a cable comes loose, the gateway will not be able to receive upto-date data from the Modbus device. The out-of-date data will be stored in the gateway’s memory and will be retrieved by the client (e.g., PLC), which is not aware that the server/slave device is not providing up-todate data. To handle this situation, the MGate provides a warning mechanism to report the list of server/slave devices that are still “alive” through the Status Monitoring function. The MGate automatically creates a status tag when a Modbus device is created. This tag is used to show the connection status (valid or invalid) of the Modbus server device. To monitor the status of the status tag, you can convert this tag to the northbound protocol and read for the northbound SCADA/device. Or, you can check the tag status on MGate’s web, the Tag View page. To perform the status tag monitoring from your northbound protocol, go to the northbound protocol’s page (for example, the EtherNet/IP adapter page), click Add Tags, select Modbus serial master as the tag provider, and select the “status” tag. MGate will automatically add a mapping from this Modbus tag to the other protocol.

The highest significant bit shows the status. 1 is invalid, 0 is valid.

MGate 5135/5435 Series User Manual

49

4. Network Management Tool (MXstudio)
Moxa’s MXstudio industrial network management suite includes tools such as MXconfig and MXview. MXconfig is for industrial network configuration; MXview is for industrial management software. The MXstudio suite in the MGate includes MXconfig and MXview, which are used for the mass configuration of network devices and monitoring network topology, respectively. The following functions are supported: When you discover a Moxa product that has not been integrated into the MXview or MXconfig, you may not be able to retrieve the product information from MXview or MXconfig. To solve this, you can download the plugin file from the Moxa MGate product website and then import/install the plugin into MXview or MXconfig. After importing/installing the plugin files, the MGate products can be supported by MXview/MXconfig. Please refer to the Moxa MGate product website to download plugin files: http://www.moxa.com. For more detailed functions such as supported functions on MXview/MXconfig, please refer to the Tech Note: Configuring and Monitoring with MXview One/MXview and MXconfig.

MGate 5135/5435 Series User Manual

50

A. SNMP Agents with MIB II and RS-232Like Groups

The MGate has built-in Simple Network Management Protocol (SNMP) agent software that supports SNMP Trap, RFC1317 and RS-232-like groups, and RFC 1213 MIB-II.

RFC1213 MIB-II Supported SNMP Variables

System MIB sysDescr sysObjectID sysUpTime sysContact sysName sysLocation sysServices

Interfaces MIB ifNumber ifIndex ifDescr ifType ifMtu ifSpeed ifPhysAddress ifAdminStatus ifOperStatus ifLastChange ifInOctets ifInUcastPkts ifInNUcastPkts ifInDiscards ifInErrors ifInUnknownProtos ifOutOctets ifOutUcastPkts ifOutNUcastPkts ifOutDiscards ifOutErrors ifOutQLen ifSpecific

IP MIB ipForwarding ipDefaultTTL ipInReceives ipInHdrErrors ipInAddrErrors ipForwDatagrams ipInUnknownProtos ipInDiscards ipInDelivers ipOutRequests ipOutDiscards ipOutNoRoutes ipReasmTimeout ipReasmReqds ipReasmOKs ipReasmFails ipFragOKs ipFragFails ipFragCreates ipAdEntAddr ipAdEntIfIndex ipAdEntNetMask ipAdEntBcastAddr ipAdEntReasmMaxSize ipRouteDest ipRouteIfIndex ipRouteMetric1 ipRouteMetric2 ipRouteMetric3 ipRouteMetric4 ipRouteNextHop ipRouteType ipRouteProto ipRouteAge ipRouteMask ipRouteMetric5 ipRouteInfo ipNetToMediaIfIndex ipNetToMediaPhysAddress ipNetToMediaNetAddress ipNetToMediaType ipRoutingDiscards

ICMP MIB icmpInMsgs icmpInErrors icmpInDestUnreachs icmpInTimeExcds icmpInParmProbs icmpInSrcQuenchs icmpInRedirects icmpInEchos icmpInEchoReps icmpInTimestamps icmpTimestampReps icmpInAddrMasks icmpInAddrMaskReps icmpOutMsgs icmpOutErrors icmpOutDestUnreachs icmpOutTimeExcds icmpOutParmProbs icmpOutSrcQuenchs icmpOutRedirects icmpOutEchos icmpOutEchoReps icmpOutTimestamps icmpOutTimestampReps icmpOutAddrMasks icmpOutAddrMaskReps

MGate 5135/5435 Series User Manual

51

Address Translation MIB atIfIndex atPhysAddress atNetAddress

TCP MIB
tcpRtoAlgorithm tcpRtoMin tcpRtoMax tcpMaxConn tcpActiveOpens tcpPassiveOpens tcpAttemptFails tcpEstabResets tcpCurrEstab tcpInSegs tcpOutSegs tcpRetransSegs tcpConnState tcpConnLocalAddress tcpConnLocalPort tcpConnRemAddress tcpConnRemPort tcpInErrs tcpOutRsts

UDP MIB
udpInDatagrams udpNoPorts udpInErrors udpOutDatagrams udpLocalAddress udpLocalPort

SNMP MIB
snmpInPkts snmpOutPkts snmpInBadVersions snmpInBadCommunityNames snmpInBadCommunityUses snmpInASNParseErrs snmpInTooBigs snmpInNoSuchNames snmpInBadValues snmpInReadOnlys snmpInGenErrs snmpInTotalReqVars snmpInTotalSetVars snmpInGetRequests snmpInGetNexts snmpInSetRequests snmpInGetResponses snmpInTraps snmpOutTooBigs snmpOutNoSuchNames snmpOutBadValues snmpOutGenErrs snmpOutGetRequests snmpOutGetNexts snmpOutSetRequests snmpOutGetResponses snmpOutTraps snmpEnableAuthenTraps snmpSilentDrops snmpProxyDrops

RFC1317 RS-232-Like Groups

RS-232 MIB rs232Number rs232PortIndex rs232PortType rs232PortInSigNumber rs232PortOutSigNumber rs232PortInSpeed rs232PortOutSpeed

Async Port MIB rs232AsyncPortIndex rs232AsyncPortBits rs232AsyncPortStopBits rs232AsyncPortParity

Input Signal MIB rs232InSigPortIndex rs232InSigName rs232InSigState

Output Signal MIB rs232OutSigPortIndex rs232OutSigName rs232OutSigState

MGate 5135/5435 Series User Manual

52

CIP Objects of EtherNetIP

Several communication objects are defined in Common Industrial Protocol (CIP). Moxa’s MGate supports the following objects for PLCs and SCADA systems to monitor:
· Identity Object · TCP/IP Interface Object · Ethernet Link Object · Assembly Object · Message Router Object · Connection Manager Object · Port Object
The attributes and services of the above objects that supported are introduced in the table below, including the access rules for each attribute. To understand the details of each attribute of the standard objects, refer to the official documents of CIP introduction (Vol. 1) and the EtherNet/IP Adaptation of CIP (Vol. 2).

Identity Object
The Class code of Identity object is 0x01 (Defined in CIP Vol1, 5-2).
There is one instance of this object in our product. It stores the information of the production and the device. The following tables summarize the class attributes and the instance attributes.

Class Attribute List

Attr

ID

Access Rule

1

Get

2

Get

3

Get

6

Get

7

Get

Name Revision Max Instance
Number of Instances Maximum ID Number Class Attributes Maximum ID Number Instance Attributes

Data Type Description

UINT (16) UINT (16) UINT (16) UINT (16)
UINT (16)

Revision of this object Maximum instance number of an object currently created at this class level of the device Number of object instances currently created in this class level of the device. The attribute ID number of the last class attribute of the class definition implemented in the device The attribute ID number of the last instance attribute of the class definition implemented in the device

Instance Attribute List

Attr

ID

Access Rule

1

Get

2

Get

3

Get

4

Get

5

Get

6

Get

7

Get

Name Vendor ID Device Type Product Code
Revision
Status Serial Number Product Name

(Struct.) Data Type Description

Major Minor

UINT (16) UINT (16) UINT (16) (Struct.) USINT (8) USINT (8) WORD (16) UDINT (32) SHORT_ STRING

991, the vendor ID of Moxa. 0 x 0C, “Communications Adapter” Please refer to Product Code Table. The version of the Identity object The structure member, major The structure member, minor. Not used The serial number of each device
The product name in human-readable format

MGate 5135/5435 Series User Manual

53

Access Attr ID
Rule

15

Get/Set

17

Get/Set

Name

(Struct.) Data Type

Assigned Name

STRINGI

Geographic Location

STRINGI

Description
The assigned MGate name, for example: Same as the server name set in the basic settings. By default, it is “MGate xxxx_xx” (xxxx_xx represents the product series number and serial number). The assigned MGate location Same as the server location set in the basic settings. By default, it is blank.

The Identity Object Instance supports the following CIP Common services:

Common Service List

Service Code 0x01 0x0E 0x10 0x05

Implementation

Class Instance

Service Name
Get_Attributes_All Get_Attribute_Single Set_Attribute_Single Reset

Description
Returns the contents of all attributes of the class Used to read an object instance attribute Used to write an object instance attribute Invokes the reset service for the device

Product Code 0x1036 0x1038

Model Name MGate 5135 MGate 5435

TCP/IP Interface Object
The Class code of TCP/IP Interface object is 0xf5 (Defined in CIP Vol2, 5-3). There is one instance of this object.
The following tables summarize the attributes of this object.

Class Attribute List

Attr

ID

Access Rule

1

Get

2

Get

3

Get

6

Get

7

Get

Name Revision Max Instance
Number of Instances Maximum ID Number Class Attributes Maximum ID Number Instance Attributes

Data Type Description

UINT (16) UINT (16) UINT (16) UINT (16)
UINT (16)

Revision of this object Maximum instance number of an object currently created at this class level of the device Number of object instances currently created in this class level of the device. The attribute ID number of the last class attribute of the class definition implemented in the device The attribute ID number of the last instance attribute of the class definition implemented in the device

Instance Attribute List

Attr

ID

Access Rule

Name

(Struct.)

1

Get

Status

Data Type Description

Interface status

0 = The Interface Configuration attribute has

DWORD

(32)

not been configured. 1 = The Interface Configuration

attribute

contains valid configuration got from BOOTP,

DHCP or non-volatile storage.

MGate 5135/5435 Series User Manual

54

Access Attr ID
Rule

2

Get

3

Get/Set

4

Get

5

Get/Set

6

Get/Set

Name

(Struct.)

Data Type Description

Interface capability flags Bit map of capability

flags:

Configurati on Capability

Bit 0: BOOTP Client DWORD (32) Bit 1: DNS Client
Bit 2: DHCP Client

Bit 3: DHCP-DNS Update

Bit 4: Configuration Settable

Interface control flags Bit map of control

flags:

Bit 0 to 3: Startup Configuration

Configurati on Control

· 0 = The device shall use the interface

configuration values previously stored

DWORD (32)

(for example, in non-volatile memory or via hardware witches).

· 1 = The device shall obtain its interface

configuration values via BOOTP.

· 2 = The device shall obtain its interface

configuration values via DHCP upon start-

up.

· 3 to15 = Reserved.

(Struct.)

Path to physical link object

Physical Link Path Size

UINT (16) Size of Path

Object

Path

Padded EPATH

Logical segments identifying the physical link object

(Struct.)

TCP/IP network interface configuration

IP Address

UDINT (32) The device’s IP address

Interface Configurati on

Network Mask Gateway Address Name Server

UDINT (32) UDINT (32) UDINT (32)

The device’s network mask Default gateway address Primary name server

Name Server2 UDINT (32) Secondary name server

Domain Name STRING

Defauult domain name

Host Name

STRING

Host name

The TCP/IP Object Instance supports the following CIP Common services:

Common Service List

Service Code 0x01 0x0E 0x10

Implementation

Class Instance

Service Name
Get_Attributes_All Get_Attribute_Single Set_Attribute_Single

Description
Returns the contents of all attributes of the class Used to read an object instance attribute Used to change an object instance attribute

Ethernet Link Object
The Class code of Ethernet Link object is 0xf6 (Defined in CIP Vol2, 5-4). For each MGate Ethernet port, there is an instance of this class. The following table shows the mapping of instance number and the MGate Ethernet port number.

MGate 5135/5435 Series User Manual

55

Instance Number 0 1 2

Mapping to
Ethernet Link class 1st MGate Ethernet port 2nd MGate Ethernet port

The following tables summarize the attributes of the Ethernet Link object.

There are some vendor specific attributes in the table (Starting from attribute Id 100).

Class Attribute List

Access Attr ID Rule

1

Get

2

Get

3

Get

6

Get

7

Get

Name Revision Max Instance
Number of Instances Maximum ID Number Class Attributes Maximum ID Number Instance Attributes

Data Type Description

UINT (16) UINT (16) UINT (16) UINT (16)
UINT (16)

Revision of this object Maximum instance number of an object currently created at this class level of the device The number of object instances currently created in this class level of the device. The attribute ID number of the last class attribute of the class definition implemented in the device The attribute ID number of the last instance attribute of the class definition implemented in the device

Instance attribute list

Access Attr ID
Rule

1

Get

2

Get

3

Get

Name
Interface Speed Interface Flags Physical Address

Interface

4

Get

Counters

5

Get

Media Counters

(Struct.)

Data Type Description

UDINT (32)

Interface speed currently in use (Speed in Mbps, e.g., 0, 10, 100, 1000, etc.)

DWORD (32) Refer to the Interface Flags table.

In Octets In Ucast Packets In Nucast Packets
In Discards
In Errors
Out Octets Out Ucast Packets Out Nucast Packets Out Discards Out Errors
Alignment Errors
FCS Errors
Single Collisions

ARRAY of 6 USINT(8) (Struct.) UDINT (32)

MAC layer address (The System MAC address). Counters relevant to the receipt of packets. Octets received on the interface.

UDINT (32) Unicast packets received on the interface.

UDINT (32) UDINT (32) UDINT (32) UDINT (32)

Non-unicast packets received on the interface. Inbound packets received on the interface but are discarded. Inbound packets that contain errors (does not include In Discards). Octets sent on the interface.

UDINT (32) Unicast packets sent on the interface.

UDINT (32) Non-unicast packets sent on the interface.

UDINT (32) UDINT (32) (Struct.) UDINT (32)
UDINT (32)
UDINT (32)

Discarded outbound packets. Outbound packets that contain errors.
Received frames that are not an integral number of octets in length. Received frames that do not pass the FCS check. Successfully transmitted frames which experienced exactly one collision.

MGate 5135/5435 Series User Manual

56

Access

Attr ID

Name

Rule

Interface

6

Get/Set

Control

10

Get

Interface Label

11

Get

Interface Capability

(Struct.)

Data Type Description

Multiple Collisions

Successfully transmitted frames which UDINT (32)
experienced more than one collision.

SQE Test Errors

UDINT (32)

The number of times the SQE test error message is generated.

Deferred Transmissi

ons

UDINT

(32)

Frames for which first transmission attempt is delayed because the medium is busy.

The number of times a collision is detected

Late Collisions UDINT (32) later than 512 bit times into the transmission

of a packet.

Excessive Collisions

UDINT (32)

Frames for which transmission fails due to excessive collisions.

MAC Transmit Errors

UDINT (32)

Frames for which transmission fails due to an internal MAC sublayer transmit error.

Carrier Sense Errors

UDINT (32)

Times that the carrier sense condition was lost or never asserted when attempting to transmit a frame.

Frame Too Long

UDINT (32)

Received frames that exceed the maximum permitted frame size.

MAC Receive Errors

UDINT (32)

Frames for which reception on an interface fails because of an internal MAC sublayer receive error.

(Struct.)

Configuration for physical interface.

Bit 0: Auto-Negotiate

Control Bits

· Value 0: Force · Value 1: Auto-Nego WORD (16) Bit 1: Half/Full Duplex

· Value 0: half duplex · Value 1: full duplex Bit 2 to 15: Reserved, all zero

Forced Interface Speed

UINT (16)

Speed at which the interface shall be forced to operate.

SHORT_ STRING

Human readable identification

(Struct.)

Indicates the capabilities of the interface

Interface capabilities, other than Capability Bits DWORD (32) speed/duplex

(Struct.)

Indicates speed/duplex pairs supported in the Interface Control attribute

USINT (8)

Speed/Duplex Options

(Array Struct.)

Speed/Duplex Array Count Speed/Duplex Array

UINT (16) Interface Speed

USINT (8) Interface Duplex Mode

Interface Flags

Bit(s) Called

0

Link Status

1

Half/Full Duplex

Definition 0 indicates an inactive link; 1 indicates an active link. 0 indicates half duplex; 1 indicates full duplex.

MGate 5135/5435 Series User Manual

57

Bit(s) Called

2-4

Negotiation Status

5

Manual Setting Requires Reset

6

Local Hardware Fault

7~31 Reserved.

Definition Indicates the status of link auto-negotiation 0 = Auto-negotiation in progress. 1 = Auto-negotiation and speed detection failed. Using default values for speed and duplex. Default values are product-dependent; recommended defaults are 10Mbps and half duplex. 2 = Auto negotiation failed but detected speed. The duplex was defaulted. Default value is product-dependent; recommended default is half duplex. 3 = Successfully negotiated speed and duplex. 4 = Auto-negotiation not attempted. Forced speed and duplex. 0 indicates the interface can activate changes to link parameters (autonegotiate, duplex mode, interface speed) automatically. 1 indicates the device requires a Reset service be issued to its Identity Object for the changes to take effect. 0 indicates the interface detects no local hardware fault; 1 indicates a local hardware fault is detected. The meaning of this is product- specific. For example, an AUI/MII interface might detect no transceiver attached, or a radio modem might detect no antenna attached. In contrast to the soft, possibly self-correcting nature of the Link Status being inactive, this is assumed a hard-fault requiring user intervention. Shall be set to zero

The Ethernet Link Object Instance supports the following CIP common services:

Common Service List

Service Code 0x0E 0x10

Implementation

Class Instance

Service Name
Get_Attribute_Single Set_Attribute_Single

Description
Used to read an object instance attribute Used to change an object instance attribute

Assembly Object

The Moxa MGate supports static assembly object for CIP I/O messaging. The Class code is 0x04 (Defined in CIP Vol 1, 5-5).

There are three instances of this object as the following.

Input Output Configuration

Instance Number MGate 5135: 4 MGate 5435: 8 MGate 5135: 4 MGate 5435: 8 1

Size (bytes) MGate 5135: 1984 MGate 5435: 3968 MGate 5135: 1984 MGate 5435: 3968 0

The Input means the data is produced by MGate, which includes the information and status report to the originator for monitoring. The Output means the data is generated by the originator (remote host) and is consumed by MGate.

Class Attribute List

Attr

ID

Access Rule

1

Get

Name Revision

Data Type Description UINT (16) Revision of this object

Instance Attribute List

Access

Attr ID

Name

Rule

3

Get/Set Data

(Struct.)

Data Type Description

Array of BYTE

The implicit messaging content

MGate 5135/5435 Series User Manual

58

Access Attr ID
Rule

4

Get

Name Size

(Struct.)

Data Type Description UINT (16) Number of bytes in Attr. 3

Common Service List

Service Code 0x0E

Implementation

Class Instance

Service Name Get_Attribute_Single

Description Used to read an object instance attribute

Message Router Object
The object within a node that distributes messaging requests to the appropriate application objects. The supported messaging connections are as the following:
· Explicit Messaging · Unconnected Messaging · Implicit messaging
When using the UCMM to establish an explicit messaging connection, the target application object is the Message Router object (Class Code 2).

Class Attribute List

Attr

ID

Access Rule

1

Get

Name Revision

Data Type Description UINT (16) Revision of this object

Instance Attribute List

Attr

ID

Access Rule

Name

(Struct.)

1

Get

Object_list Number

Classes

Number

2

Get

Available

3

Get

Number Active

Active

4

Get

Connections

Data Type Description

(Struct.)
UINT (16)
Array of UINT (16)

A list of supported objects The number of supported classes in the classes array
List of supported class codes

UINT (16) Maximum number of connections supported

UINT (16)
Array of UINT (16)

Number of connections currently used by system components A list of the connection IDs of the currently active connections

Common Service List

Service Code 0x0E

Implementation

Class Instance

Service Name Get_Attribute_Single

Description Used to read an object instance attribute

Connection Manager Object
The Connection Manager Class allocates and manages the internal resources associated with both I/O and Explicit Messaging connections.
The class code is 0x06. There is one instance of this object.

MGate 5135/5435 Series User Manual

59

The supported connection trigger type is cyclic and change of state. The instance attribute list is introduced as the following.

Class Attribute List

Attr

ID

Access Rule

1

Get

Name Revision

Data Type Description UINT (16) Revision of this object

Common Service List

Service Code 0x0e 0x4E 0x54

Implementation Class Instance

Service Name
Get_Attribute_Single Forward_Close Forward_Open

Description
Returns the contents of the specified attribute Closes a connection Opens a connection

Port Object
The port object represents the underlying interface of CIP which is EtherNet/IP. The class code is 0xf4. There is one instance of this object.
The instance attribute “Port Type” identifies the CIP adaptation.

Class Attribute List

Access Attr ID
Rule

1

Get

2

Get

3

Get

8

Get

9

Get

Name Revision

(Struct.)

Max Instance

Number of Instances

Entry Port

Port Instance

Info

Port Type

Port Number

Data Type Description

UINT (16)
UINT (16)
UINT (16)
UINT (16)
(Array of Struct.) UINT (16) UINT (16)

Revision of this object Maximum instance number of an object currently created in this class level of the device Number of object instances currently created at this class level of the device. The attribute ID number of the last class attribute of the class definition implemented in the device
Enumerates the type of port CIP port number associated with this port

Instance Attribute List

Access

Attr ID

Name

Rule

1

Get

Port Type

(Struct.)

2

Get

Port Number

Path Length

3

Get

Link Object

Link Path

4

Get

Port Name

Data Type Description

UINT (16)
UINT (16)
(Struct.) UINT (16) Padded EPATH
SHORT_ STRI NG

Enumerates the type of port. 4 = EtherNet/IP. CIP port number associated with this port. (Value 1 is reserved for internal product use)
Number of 16-bit words in the following path. Logical path segments that identify the object for this port. String which names the physical network port. The maximum number of characters in the string is 64.

MGate 5135/5435 Series User Manual

60

Access

Attr ID

Name

Rule

(Struct.)

Node

7

Get

Address

10