Phoenix Contact GW MODBUS TCP/ASCII 1E/1DB9 User Manual
  1. Manuals
  2. Brands
  3. Phoenix Contact Manuals
  4. Media Converter
  5. GW MODBUS TCP/ASCII 1E/1DB9
  6. User manual

Phoenix Contact GW MODBUS TCP/ASCII 1E/1DB9 User Manual

Protocol converter for serial data (raw/ascii) to modbus tcp
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Protocol converter for serial data
(RAW/ASCII) to Modbus TCP
User manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the GW MODBUS TCP/ASCII 1E/1DB9 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Phoenix Contact GW MODBUS TCP/ASCII 1E/1DB9

Summary of Contents for Phoenix Contact GW MODBUS TCP/ASCII 1E/1DB9

  • Page 1 Protocol converter for serial data (RAW/ASCII) to Modbus TCP User manual...

  • Page 2: Gw Modbus Tcp/Ascii 1E/1Db9

    User manual Protocol converter for serial data (RAW/ASCII) to Modbus TCP 2017-06-16 Revision: This user manual is valid for: Designation Order No. GW MODBUS TCP/ASCII 1E/1DB9 2702768 GW MODBUS TCP/ASCII 1E/2DB9 2702769 GW MODBUS TCP/ASCII 2E/2DB9 2702770 GW MODBUS TCP/ASCII 2E/4DB9...
  • Page 3 How to contact us Internet Up-to-date information on Phoenix Contact products and our Terms and Conditions can be found on the Internet at: phoenixcontact.com Make sure you always use the latest documentation.
  • Page 4 The receipt of technical documentation (in particular user documentation) does not constitute any further duty on the part of Phoenix Contact to furnish information on modifications to products and/or technical documentation. You are responsible to verify the suipageility and intended use of the products in your specific application, in particular with regard to observing the applicable standards and regulations.

  • Page 5: Table Of Contents

    3.9.3 Serial logs .................... 40 3.9.4 Ethernet logs ..................41 3.10 Maintenance......................42 3.10.1 Passwords ................... 42 3.10.2 Restore defaults ................... 43 3.10.3 Log files ....................43 3.10.4 Configuration files ................44 3.10.5 Update firmware .................. 45 3749_en_B PHOENIX CONTACT...
  • Page 6 Hardware reset ..................55 5.1.2 Software reset ..................55 LEDs........................55 Modbus addressing ........................57 Modbus memory map for Raw/ASCII data ............57 Sequence numbers ..................... 60 Appendixes..........................61 List of figures ...................... 61 List of tables ....................... 63 PHOENIX CONTACT 3749_en_B...

  • Page 7: Description

    Ethernet ports to fit any application. This user manual is valid for: Table 1-1 GW MODBUS TCP/ASCII...types Type Description Order No. GW MODBUS TCP/ASCII 1E/1DB9 2702768 GW MODBUS TCP/ASCII 1E/2DB9 2702769 GW MODBUS TCP/ASCII 2E/2DB9 2702770...

  • Page 8: Structure

    GW MODBUS TCP/ASCII... Structure GW MODBUS TCP/ASCII 1E/1DB9 The GW MODBUS TCP/ASCII 1E/1DB9 features one Ethernet port and one RS- 232/422/485 serial port with a D-SUB 9 connector. Figure 1-1 GW MODBUS TCP/ASCII 1E/1DB9 Table 1-2 GW MODBUS TCP/ASCII 1E/1DB9 structure...

  • Page 9: Gw Modbus Tcp/Ascii 1E/2Db9

    GW MODBUS TCP/ASCII 1E/2DB9 Table 1-3 GW MODBUS TCP/ASCII 1E/2DB9 structure Item Description Power connector P1 D-SUB 9 connector Ethernet port (RJ45) P2 D-SUB 9 connector Status LED Ethernet activity status LED Ethernet link status LED Reset button 3749_en_B PHOENIX CONTACT...

  • Page 10: Gw Modbus Tcp/Ascii 2E/2Db9

    Power connector P1 D-SUB 9 connector Ethernet link status LED E2 Ethernet port (RJ45) Ethernet activity status LED P2 D-SUB 9 connector Status LED Ethernet activity status LED E1 Ethernet port (RJ45) Ethernet link status LED Reset button PHOENIX CONTACT 3749_en_B...

  • Page 11: Gw Modbus Tcp/Ascii 2E/4Db9

    Ethernet link status LED E2 Ethernet port (RJ45) Ethernet activity status LED P4 D-SUB 9 connector P2 D-SUB 9 connector Status LED Ethernet activity status LED E1 Ethernet port (RJ45) Ethernet link status LED Reset button P1 D-SUB 9 connector 3749_en_B PHOENIX CONTACT...
  • Page 12 GW MODBUS TCP/ASCII... PHOENIX CONTACT 3749_en_B...

  • Page 13: Installation

    Hold the device by the housing cover and carefully push the device toward the mounting surface (B). After the foot is snapped onto the DIN rail, verify that it is attached securely. Figure 2-1 DIN rail mounting 3749_en_B PHOENIX CONTACT...
  • Page 14 Use a suitable screwdriver to release the locking mechanism (A) on the snap-on foot of the device. Hold onto the device by the housing cover and carefully tilt it upward (B). Remove the device from the DIN rail (C). Figure 2-2 DIN rail removal PHOENIX CONTACT 3749_en_B...

  • Page 15: Data Interfaces

    No. 2799474). The cable is an interface cable with 1:1 connected contacts. Table 2-1 D-SUB 9 to RS-232 pin out GW MODBUS End device TCP/ASCII... RS-232 D-SUB 9 D-SUB 9 D-SUB 25 D-SUB 25 (DCE) (DTE) (DCE) (DTE) 1, 6 6, 8 3749_en_B PHOENIX CONTACT...

  • Page 16: Connecting The Rs-422 Cable

    Fit this bus cable with a termination network at the two furthest points of the RS-485 network. The termination resistors are integrated in the GW MODBUS TCP/ASCII... and can be switched on through the web-based management interface. PHOENIX CONTACT 3749_en_B...

  • Page 17: Connecting The Ethernet Cable

    (PCs) is subject to the 5-4-3 rule of repeater placement on the network: – Five segments connected on the network. – Four repeaters. – Three segments of the fiber segments can have stations connected. The other two segments must be inter-repeater link segments with no stations connected. 3749_en_B PHOENIX CONTACT...

  • Page 18: Connecting The Power Supply

    The GW MODBUS TCP/ASCII... is powered using a +24 V DC SELV power supply. The power supply is connected by way of COMBICON plug-in screw terminal blocks (24 V and 0 V). Figure 2-4 Single power supply connection Figure 2-5 Redundant power supply connection PHOENIX CONTACT 3749_en_B...

  • Page 19: Configuration And Startup

    Set the IP address of the connected PC to the sub-network of the GW MODBUS TCP/ASCII...: for example, IP = 192.168.254.10, sub-network = 255.255.255.0. Open a web browser and enter the IP address of the GW MODBUS TCP/ASCII... in the “Address” field (default = 192.168.254.254). Figure 3-1 “Login” screen 3749_en_B PHOENIX CONTACT...

  • Page 20: Home Screen

    Figure 3-2 “Home” screen Advanced settings can be accessed through the menu at the top of the screen. Click the “Home” button in the upper left corner of the web-based management interface to go to the “Home” screen. PHOENIX CONTACT 3749_en_B...

  • Page 21: General Settings

    Device Name: Enter a name for the device. The field accepts up to 16 characters. Contact: Enter the name of a contact person, group, or department responsible for this device. The field accepts up to 16 characters. Click the “Apply Changes” button to save the configuration. 3749_en_B PHOENIX CONTACT...

  • Page 22: Lan Settings

    If using static IP addresses, click the “Manual address assignment” button and enter the appropriate information in the various fields. MAC Address: the MAC Address of the GW MODBUS TCP/ASCII... is displayed. Click the “Apply Changes” button to save the configuration. PHOENIX CONTACT 3749_en_B...

  • Page 23: Security

    TCP ports. If a GW MODBUS TCP/ASCII... serial port configuration is set up to open (as a client) a TCP connection to another server device, the GW MODBUS TCP/ASCII... also uses this certificate to identify itself as an SSL client if requested by the server. 3749_en_B PHOENIX CONTACT...

  • Page 24: Serial Settings

    SSL/TLS connections that use DH encryption during handshaking. All GW MODBUS TCP/ASCII... units are shipped from the factory with identical configurations. They all have the identical, self-signed, Phoenix Contact Server RSA Certificates, Server RSA Keys, and Server DH Keys.

  • Page 25: Port Configuration

    Modbus ASCII master to the serial port. This can be used, for instance, if the GW MODBUS TCP/ASCII... module (versions with multiple serial ports) has a Raw/ASCII device on one serial port to access the Raw/ASCII data using a Modbus ASCII master on another serial port. 3749_en_B PHOENIX CONTACT...

  • Page 26: Raw/Ascii Connection

    In the “ASCII Configuration” group, specify the conversion settings. Figure 3-9 “Raw/ASCII Configuration” group The GW MODBUS TCP/ASCII... modules can be configured to detect serial packet delimiters used for the identification of a raw data packet. PHOENIX CONTACT 3749_en_B...
  • Page 27 Byte 2 - Specifies the character that represents the second STX byte. The GW – MODBUS TCP/ASCII... adds this byte only if the length is two bytes. Specify a value between 0 and FF in decimal format. 3749_en_B PHOENIX CONTACT...
  • Page 28 TCP Connection sets all responses to be returned to the same TCP connection from which the original command was received. TCP Connection is typically required when multiple controllers are communicating from the same PLC or computer. PHOENIX CONTACT 3749_en_B...

  • Page 29: Modbus Configuration" Page

    Enable byte swap to PLC: When enabled, the GW MODBUS TCP/ASCII... transmits – the most significant byte (MSB) of a WORD first. The least significant byte (LSB) is transmitted first, if this is not checked. 3749_en_B PHOENIX CONTACT...
  • Page 30 Modbus TCP slave, thereby reducing network traffic and latency. However, not all Modbus TCP slaves support maximum sized Modbus messages; therefore, this setting must be tested to ensure operability. PHOENIX CONTACT 3749_en_B...
  • Page 31 The address is base 1; therefore, if the register address scheme starts at 40000, enter 40001 (required). Only enter the register address without the leading 4xxxx, for example enter 1 for 40001 or 250 for 40250. 3749_en_B PHOENIX CONTACT...

  • Page 32: Socket Settings

    Configuration tab. The number of Ethernet TCP/IP connections supported by the GW MODBUS TCP/ASCII... is equal to the number of serial ports on the device, but the TCP/IP connections are not directly linked to a particular serial port. PHOENIX CONTACT 3749_en_B...

  • Page 33: Socket Settings

    Enable: This must be checked to use the port as a socket. – – Listen: Check the “Listen” check box so that the GW MODBUS TCP/ASCII... listens for incoming TCP/IP socket connections on the port number specified in the On port field. 3749_en_B PHOENIX CONTACT...

  • Page 34: Raw/Ascii Configuration

    On the “Raw/ASCII Configuration” page, configure the settings that control the conversion of Raw/ASCII TCP/IP data to Modbus. Figure 3-14 “Raw/ASCII Configuration” page The GW MODBUS TCP/ASCII... modules can be configured to detect serial packet delimiters used for the identification of a raw data packet. PHOENIX CONTACT 3749_en_B...
  • Page 35 0 and FF in hexadecimal format. Byte 2: Specifies the character that represents the second STX byte. The GW – MODBUS TCP/ASCII... adds this byte only if the length is two bytes. Specify a value between 0 and FF in decimal format. 3749_en_B PHOENIX CONTACT...
  • Page 36 TCP Connection sets all responses to be returned to the same TCP connection from which the original command was received. TCP Connection is typically required when multiple controllers are communicating from the same PLC or computer. PHOENIX CONTACT 3749_en_B...

  • Page 37: Modbus Configuration" Page

    Enable byte swap to PLC: When enabled, the GW MODBUS TCP/ASCII... – transmits the most significant byte (MSB) of a WORD first. The least significant byte (LSB) is transmitted first, if this is not checked. 3749_en_B PHOENIX CONTACT...
  • Page 38 Modbus TCP slave, thereby reducing network traffic and latency. However, not all Modbus TCP slaves support maximum sized Modbus messages; therefore, this setting must be tested to ensure operability. PHOENIX CONTACT 3749_en_B...
  • Page 39 The address is base 1; therefore, if the register address scheme starts at 40000, enter 40001 (required). Only enter the register address without the leading 4xxxx, for example enter 1 for 40001 or 250 for 40250. 3749_en_B PHOENIX CONTACT...

  • Page 40: Diagnostics

    Rx Byte Count: The number of bytes received by the serial port of the GW MODBUS – TCP/ASCII..Rx Packet Count: The number of packets received by the serial port of the GW – MODBUS TCP/ASCII..– Parity Error Count: The number of received serial packets dropped due to parity errors. PHOENIX CONTACT 3749_en_B...
  • Page 41 Command/Response Mode Response Discards: Displays the number of – Command/Response mode responses that were discarded because either the connection to the controller was closed or the response timed out after the Age Time had been reached. 3749_en_B PHOENIX CONTACT...

  • Page 42: Plc Interface

    Invalid Request Protocol Types: The number of messages received with invalid protocol errors. This occurs when a message is received with a protocol other than the Modbus protocol value of zero. Unsupported Modbus Function Codes: The number of messages received with – unsupported function codes. PHOENIX CONTACT 3749_en_B...
  • Page 43 PLC to the Ethernet device when the device was offline. – First Error Description: Text description of the first error that occurred. – Last Error Description: Text description of the last or most recent error that occurred. 3749_en_B PHOENIX CONTACT...

  • Page 44: Serial Logs

    <data> - Data packet received. For Modbus slave data, all data bytes are shown in hex (xxh) format. For Raw/ASCII and Modbus/ASCII data, ASCII characters are displayed as characters. Non-ASCII data is displayed in hex (xxh) format PHOENIX CONTACT 3749_en_B...

  • Page 45: Ethernet Logs

    <data> - Data packet received. For Modbus slave data, all data bytes are shown in hex (xxh) format. For Raw/ASCII and Modbus/ASCII data, ASCII characters are displayed as characters. Non-ASCII data is displayed in hex (xxh) format 3749_en_B PHOENIX CONTACT...

  • Page 46: Maintenance

    Password: admin The “Password” field is case sensitive. The user name is fixed and cannot be modified. Enter the current password and the new password (twice) in the appropriate fields. Click the “Apply Changes” button to save changes. PHOENIX CONTACT 3749_en_B...

  • Page 47: Restore Defaults

    3.10.3 Log files To view log files: From the “Device Maintenance” page, click the “Log Files” tab to review the log files of the device, which can be used for advanced troubleshooting. Figure 3-22 “Log Files” page 3749_en_B PHOENIX CONTACT...

  • Page 48: Configuration Files

    To load a configuration file to a GW MODBUS TCP/ASCII..., click the “Browse” button to open a dialog box and browse to the configuration file location on the PC. After selecting the appropriate configuration file, enter the password for the file and click the “Load Configuration” button. PHOENIX CONTACT 3749_en_B...

  • Page 49: Update Firmware

    Click the “Apply Changes” button to install the firmware. NOTE: Ensure that a reliable power connection is available during the firmware update. Do not restart the module or disconnect the Ethernet cable during this process When firmware is updated, the device configuration is maintained. 3749_en_B PHOENIX CONTACT...
  • Page 50 GW MODBUS TCP/ASCII... PHOENIX CONTACT 3749_en_B...

  • Page 51: Gw Modbus Tcp/Ascii

    Modbus TCP client by enabling the Strip RX STX/ETX Chars option. The Modbus Message Settings may be left as default and this application functions normally; however, adjust the “Max packet size” to ensure the correct barcode length (12 digits) is captured. 3749_en_B PHOENIX CONTACT...

  • Page 52: Modbus Tcp Client Configuration

    (12 digits) is captured. Each character of a barcode is transmitted as the hex value of the ASCII character. Therefore, a 12 digit barcode is at least 12 bytes long, not including any STX or ETX characters. PHOENIX CONTACT 3749_en_B...

  • Page 53: Modbus Tcp Server Configuration

    Modbus TCP server by enabling the Strip RX STX/ETX Chars option. The Modbus Message Settings may be left as default and this application functions normally; however, adjust the maximum packet size to ensure the correct barcode length (12 digits) is captured. 3749_en_B PHOENIX CONTACT...

  • Page 54: Modbus Rtu Master Configuration

    Enter the TCP port the barcode scanner connects to in the “On Port” field and set the “Connect” to Always. This example uses port 8000. c) Configure the remaining TCP Interface Configuration settings, if sending information to the Ethernet barcode scanner. PHOENIX CONTACT 3749_en_B...

  • Page 55: Modbus Rtu Master Configuration

    Enter the TCP port the barcode scanner connects to in the “On Port” field, and set the “Connect” to Always. This example uses port 8000. c) Configure the remaining TCP Interface Configuration settings if sending information to the Ethernet barcode scanner. 3749_en_B PHOENIX CONTACT...

  • Page 56: Modbus Tcp Client Configuration

    Configure the TCP/IP barcode scanner IP address to a unique address within the same subnet as the GW MODBUS TCP/ASCII... and the Modbus TCP client (see Figure 3-4). Configure the TCP/IP barcode scanner to connect the IP address of the GW MODBUS TCP/ASCII... on port 8000. PHOENIX CONTACT 3749_en_B...

  • Page 57: Tcp/Ip Barcode Scanner To Modbus Tcp Server

    GW MODBUS TCP/ASCII... begins writing data to the 40000 register of the Modbus TCP server. c) Enter the delay between Modbus write commands in the “Update Rate field”. d) If sending information from the Modbus TCP server to the serial barcode scanner, update the appropriate “Poll PLC” settings. 3749_en_B PHOENIX CONTACT...

  • Page 58: Modbus Tcp Server Configuration

    Packet length (UINT) 0x0E 41002 0x0230 0x02 Begin message 0x30 Barcode value 41003 0x3132 0x31 0x32 41004 0x3334 0x33 0x34 41005 0x3536 0x35 0x36 41006 0x3738 0x37 0x38 41007 0x5A7A 0x5A 0x7A 41008 0x3509 0x35 0x09 End message PHOENIX CONTACT 3749_en_B...

  • Page 59: Troubleshooting

    An internal error is indicated by three flashes every five seconds. Green Link LED. On indicates Ethernet network is connected. Yellow Activity LED. Flashing indicates data transfer activity. LEDs on Ethernet ports are not labeled. See Section 1.1, “Structure” for LED locations. 3749_en_B PHOENIX CONTACT...
  • Page 60 GW MODBUS TCP/ASCII... PHOENIX CONTACT 3749_en_B...

  • Page 61: Modbus Addressing

    Read/Write number Transmit sequence 41300 42300 43300 44300 – Read/Write number Transmit packet 41301 42301 43301 44301 – Read/Write length Transmit message 41302-41424 42302-42424 43302-43424 44302-44424 – Read/Write Transmit sequence 41556 42556 43556 44556 UINT Read number 3749_en_B PHOENIX CONTACT...
  • Page 62 Registers must be read as a block. Reading individual registers will result in a Modbus exception. Registers must be written and read as a block. Writing or reading individual registers will result in a Modbus exception. Any holding registers that are not used to hold payload data are set to 0. PHOENIX CONTACT 3749_en_B...
  • Page 63 Such invalid responses could result of any or all of the following: – Invalid CRC – Invalid returned function code – Invalid unit identifier – Duplicate Identifier Modbus/RTU device timeouts The number of messages that timed out waiting for a response from a Modbus/RTU device on this port. 3749_en_B PHOENIX CONTACT...

  • Page 64: Sequence Numbers

    GW MODBUS TCP/ASCII... in the Transmit Data message. Access to these sequence numbers are provided primarily for initialization purposes at the start of the PLC program to initialize the sequence numbers on the PLC, GW MODBUS TCP/ASCII..., or both. PHOENIX CONTACT 3749_en_B...

  • Page 65: Appendixes

    A Appendixes List of figures Section 1 Figure 1-1: GW MODBUS TCP/ASCII 1E/1DB9 ............ 4 Figure 1-2: GW MODBUS TCP/ASCII 1E/2DB9 ............. 5 Figure 1-3: GW MODBUS TCP/ASCII 2E/2DB9 ............. 6 Figure 1-4: GW MODBUS TCP/ASCII 2E/4DB9 ............ 7 Section 2 Figure 2-1: DIN rail mounting ..................
  • Page 66 “Restore Defaults” page ..............43 Figure 3-22: “Log Files” page .................. 43 Figure 3-23: “Config Files” page ................44 Figure 3-24: “Update Firmware” page ..............45 Section 4 Figure 4-1: Barcode scanner to Modbus connections ........... 47 PHOENIX CONTACT 3749_en_B...

  • Page 67: B 2 List Of Tables

    List of tables Section 1 Table 1-1: GW MODBUS TCP/ASCII...types............3 Table 1-2: GW MODBUS TCP/ASCII 1E/1DB9 structure ........4 Table 1-3: GW MODBUS TCP/ASCII 1E/2DB9 structure ........5 Table 1-4: GW MODBUS TCP/ASCII 2E/2DB9 structure ........6 Table 1-5: GW MODBUS TCP/ASCII 2E/4DB9 structure ........
  • Page 68 GW MODBUS TCP/ASCII... PHOENIX CONTACT 3749_en_B...

This manual is also suitable for:

Gw modbus tcp/ascii 1e/2db9Gw modbus tcp/ascii 2e/2db9Gw modbus tcp/ascii 2e/4db9270276827027692702770 ... Show all

Table of Contents