YenGear

Appearance

Y201-R Technical Manual ​

Y201-R

Y201-R Specification

Contents ​

  1. Overview
  2. Default Access Information
  3. Quick Configuration Flow
  4. Web UI Overview
  5. Socket and Protocol Configuration
  6. Modbus Gateway
  7. Registration Packets and Heartbeats
  8. Typical Debug Examples
  9. Troubleshooting

1. Overview ​

Y201-R is a data terminal for bidirectional transfer between serial and Ethernet networks. It supports RS485, RS232, or TTL serial access together with RJ45 Ethernet. Parameters can be configured through the Web UI, and communication links can be established through Socket A and B using TCP, UDP, HTTP, or MQTT.

ItemDescription
Core CapabilityBidirectional transfer between serial data and Ethernet data
Serial InterfaceRS485 / RS232 / TTL, depending on SKU
Network ProtocolsTCP / UDP / HTTP client / MQTT client
Configuration EntryBrowser-based Web UI
Extended FunctionModbus RTU to Modbus TCP gateway

2. Default Access Information ​

ItemDefault
Management Address192.168.10.8
Usernameadmin
Passwordadmin

Before access, set the PC NIC to the same subnet as the device and make sure the subnet mask and default gateway match.

3. Quick Configuration Flow ​

Recommended sequence:

  1. Power on the device and connect the PC and the device with an Ethernet cable.
  2. Change the PC NIC to the same subnet as the device.
  3. Open 192.168.10.8 in a browser and log in.
  4. Configure network parameters, static IP or DHCP.
  5. Configure serial parameters to match the field device.
  6. Configure the required Socket protocol, TCP, UDP, HTTP, or MQTT.
  7. Enable the Modbus gateway, registration packet, and heartbeat as needed.
  8. Save the parameters and reboot the device.
  9. Verify communication with a host-side tool or cloud platform.

4. Web UI Overview ​

The Y201-R Web UI mainly includes the following pages:

  • Status: Shows current runtime status and connection status
  • System: Configures device network settings, system parameters, and reboot operations
  • Port: Configures serial parameters, Socket parameters, Modbus gateway, registration packet, and heartbeat

Engineering recommendations:

  • Save parameters immediately after changing critical settings.
  • Reboot after changing network or protocol settings.
  • During initial debugging, start with TCP or UDP and switch to HTTP or MQTT after the link is verified.

5. Socket and Protocol Configuration ​

5.1 Socket Capability ​

ChannelSupported Protocols
Socket ATCP server / TCP client / UDP server / UDP client / HTTP client / MQTT client
Socket BTCP client / UDP server / UDP client

5.2 TCP Server ​

  • The device listens on a local port and waits for TCP clients.
  • Each TCP server can support up to 8 concurrent clients.
  • Serial data can be forwarded to all online clients.

5.3 TCP Client ​

  • The device actively connects to the target server address and port.
  • If the connection fails, it reconnects automatically with about a 1 s interval.
  • This mode is suitable when the cloud platform or center acts as the server.

5.4 UDP Server ​

  • Binds a local port and receives data from multiple clients.
  • The default send target is the most recently communicating client.
  • This mode is suitable for local debugging and lightweight data exchange.

5.5 UDP Client ​

  • The target IP and port are fixed.
  • A fixed local port is recommended so that return packets from the peer remain stable.

5.6 HTTP Client ​

Supports HTTP 1.0 / 1.1 and GET / POST / AUTO:

  • GET: Serial data triggers a GET request as URL content
  • POST: Serial data is sent as the request body to a preset URL
  • AUTO: Request method and parameters are selected flexibly through the packet header mechanism

5.7 MQTT Client ​

  • After the connection is established, the device can subscribe to a preset topic and publish data to a preset topic automatically.
  • Supports QoS0 / QoS1 / QoS2.
  • Supports both standard MQTT and Alibaba Cloud MQTT format.

QoS selection suggestions:

  • QoS0: Lowest latency, packet loss allowed
  • QoS1: Balanced reliability and latency
  • QoS2: Highest reliability with the highest overhead

6. Modbus Gateway ​

6.1 Function Description ​

The Modbus gateway is disabled by default:

  • Disabled: Transparent transfer between serial port and Ethernet
  • Enabled: Performs Modbus RTU to Modbus TCP protocol conversion

6.2 Usage Recommendations ​

  • Enable it when the host uses Modbus TCP and the field device uses Modbus RTU.
  • Leave it disabled if only raw serial transparent transmission is required.
  • If uncertain, validate both modes during debugging.

7. Registration Packets and Heartbeats ​

7.1 Registration Packet ​

The registration packet is used to report device identity to the server proactively when communication is established.

ModeDescription
FIRSTSent once at first transmission, for TCP client after each successful connection and for UDP client after the network comes up
EVERYPrepends the registration header to every data transmission
ALLFIRST + EVERY

7.2 Heartbeat Packet ​

Heartbeats are used for keepalive and link monitoring.

  • Network heartbeat supports TCP and UDP client modes
  • Serial heartbeat is independent of network mode
  • Heartbeats pause while the device is in AT command state

8. Typical Debug Examples ​

8.1 TCP Server Debug, Device as Server ​

  1. Set the target Socket on the Port page to TCPServer.
  2. Configure the local listening port, for example 8010.
  3. Save and reboot.
  4. Use a host-side network tool in TCP client mode and connect to the device IP and port.
  5. Send serial data and verify that it is forwarded to the host.

8.2 TCP Client Debug, Device as Client ​

  1. Set the target Socket on the Port page to TCPClient.
  2. Enter the host or server address and port.
  3. Save and reboot, then observe the device establishing the connection automatically.
  4. Check the connection on the server and test bidirectional data transfer.

8.3 UDP Server and UDP Client Debug ​

  • UDP Server: Use a host-side UDP client to send data to the local port on the device
  • UDP Client: The device sends data to a fixed target IP and port, while the host runs a UDP server to receive it

8.4 HTTP and MQTT Debug Suggestions ​

  • First verify the serial path with TCP or UDP.
  • Then configure HTTP or MQTT server parameters.
  • For MQTT, start with QoS0 for quick connectivity, then move to QoS1 or QoS2 based on reliability requirements.

9. Troubleshooting ​

SymptomPossible CauseRecommended Action
Web UI cannot be openedThe PC and device are not on the same subnetCheck NIC IP settings and verify access to 192.168.10.8
Login failsUsername or password is incorrectUse default admin/admin or confirm whether the credentials were changed
Serial data exists but no Ethernet dataThe Socket is not connectedCheck Socket mode, target address, port, and connection state
TCP client cannot connectServer address or port is wrong, or blocked by firewallVerify address and port, and allow the required firewall rules
UDP packets cannot be returnedLocal port is not fixed or the target settings are wrongFix the local port and verify the peer IP and port
Modbus communication failsIncorrect gateway mode selectionSwitch the Modbus gateway according to the host protocol
No data on cloud platformHTTP or MQTT settings are wrongCheck server address, credentials, topic, and QoS
Parameters do not take effect after rebootParameters were not saved or the device was not rebootedSave the configuration and reboot the device before verifying
  • Manufacturer: Hunan YenGear Tech Co., Ltd.
  • Address: Room 21014, Building 1, Fudi Xingguang Tiandi, Yingxin Road, Yuhua District, Changsha, Hunan, China
  • Email: hi@yengear.com
  • Website: www.yengear.com