Y511-L LoRaWAN Indoor Edge Gateway User Manual

• Y511-L Specification

Applicable configurations: Y511-L, 8-channel or 16-channel

Contents

1. Product Scope
2. Safety and Preparation
3. Hardware Installation
4. First Access and Basic Settings
5. LoRaWAN and Network Service Configuration
6. Edge Application Integration
7. End-Device Commissioning
8. Verification and Handover
9. Maintenance and Upgrade
10. Troubleshooting

1. Product Scope

Y511-L forwards LoRaWAN traffic to a remote Network Server or runs optional local Network Server (NS) and Application Server (AS) services. The local-service configuration supports MQTT, HTTP, TCP, WebSocket, JavaScript data processing, and Modbus TCP/RTU integration.

Configuration	Receive channels	Downlink channels
8-channel	8	1
16-channel	16	2

Channel count describes concurrent radio paths. Device capacity also depends on packet airtime, reporting intervals, and downlink traffic.

2. Safety and Preparation

2.1 Safety Notes

• Use a regulated DC 9 to 28 V supply; DC 12 V is typical.
• Attach the LoRa antennas before applying power. Do not operate the radio with an open antenna connector.
• Install the gateway indoors in a dry, ventilated location, away from heat, water, and strong electromagnetic interference.
• Disconnect power before changing wiring, the SIM card, the RS485 wiring, or the installation position.
• Use antennas, a power adapter, and a cellular module suitable for the supplied hardware variant.
• Review JavaScript scripts and application routes before enabling them on a production network.
• Do not interrupt power during a firmware upgrade or configuration recovery.

2.2 Prepare Before Installation

• Y511-L gateway and the supplied mounting hardware
• LoRa and Wi-Fi antennas; 4G antenna if ordered
• Regulated DC 12 V / 2 A supply, or an equivalent supply within the specified voltage and power limits
• Ethernet cable, Wi-Fi access, or an activated standard SIM card for the selected backhaul
• A computer or tablet on the gateway LAN for initial setup
• Network Server or local NS/AS plan
• End-device identifiers and keys
• Application broker, HTTP endpoint, TCP/WebSocket endpoint, or Modbus register map, as applicable

Check the gateway label and order details for its frequency plan and channel count. Use a plan supported by the supplied hardware, as listed in Section 5.1.

3. Hardware Installation

3.1 Mount the Gateway

1. Inspect the enclosure, connectors, and antenna and power cables for shipping damage.
2. Fit the supplied DIN-rail or wall-mount bracket.
3. Keep the gateway accessible for configuration, log checks, and service.
4. Connect the enclosure earth terminal according to the site grounding design. Use one DC source; the jack and power terminals are connected in parallel.
5. Mount the LoRa antenna high and clear of obstructions, large metal surfaces, and high-power radio equipment.

3.2 Connect the Antennas and Backhaul

1. Attach the specified antennas to the required LoRa RX/TX connectors. Use the antenna count and connections specified for the channel and duplex hardware.
2. Attach the Wi-Fi antenna and, on 4G units, the cellular antenna.
3. For 4G, insert the SIM card with power off.
4. Connect Ethernet, or prepare the local Wi-Fi network.
5. For Modbus RTU, wire RS485 A/B using the site drawing and check polarity.
6. Apply DC power after checking the antennas and network wiring.

The cellular module, antenna connector, and SIM slot apply to 4G units. Obtain an activated SIM unless the order includes one. Follow the unit labels for connector positions on 8-channel and 16-channel hardware.

3.3 Power-On Check

Indicator	Startup check
Power	Steady indicates power; open the management interface to check startup.
LoRa	Steady indicates radio startup; check server connectivity separately.
Wi-Fi / 4G	Shows the corresponding interface status; verify its IP connection.

Wait for startup to finish before changing settings.

4. First Access and Basic Settings

4.1 Connect to the Configuration Interface

1. Use Ethernet or the gateway Wi-Fi access point for initial local setup. Follow the supplied network settings.
2. For DHCP, find the gateway lease in the router. For a static address, put the computer on the same subnet.
3. Open the supplied management URL in a browser, including the port if specified.
4. Sign in with the supplied credentials and change the initial password before production use.

4.2 Set Basic Network Parameters

• DHCP or static Ethernet address
• Default gateway and DNS servers
• Wi-Fi AP or STA parameters when Wi-Fi is used
• 4G APN and SIM parameters when 4G is used
• Time zone and time synchronization, when available
• Management access policy and password

Save the settings and restart if prompted. Reopen the interface at its new address.

5. LoRaWAN and Network Service Configuration

5.1 Select the Radio Variant

Select a frequency plan supported by the hardware and permitted in the installation region:

Plan	Status
CN470	Default
EU433	Supported variant
EU868	Supported variant
AU915	Supported variant
IN865	Supported variant
AS923	Supported variant
RU864	Supported variant
US915	Supported variant

Check the channel count, duplex hardware, and antenna connections against the order. Set transmit power and the channel group within regional limits.

Match receive channels with the end-device channel mask and Network Server plan, including the AS923 sub-plan. Configure activation keys, LoRaWAN version, and Class A/C in the server device profile. Use the hardware-supported plans even if the menu lists other options.

5.2 Choose Remote or Local Network Services

Remote Network Server Mode

A separate Network Server manages gateway registration and device sessions in this mode.

1. Configure the gateway forwarding protocol and remote endpoint.
2. Enter the authentication and encryption settings supplied by the server administrator.
3. Register the gateway identifier in the Network Server.
4. Look for gateway status or traffic updates in the Network Server.

Store endpoint settings, credentials, topics, and certificates in the project configuration store.

Local NS/AS Mode

Local NS/AS requires the corresponding software option.

1. Enable the local Network Server and application service in the gateway interface.
2. Create the application or device group supported by the delivered interface.
3. Register the gateway and end devices in the local service.
4. Configure device activation, keys, application routing, and data retention as required.
5. Test local uplinks and downlinks before adding external application systems.

Assign each device session to one Network Server unless the deployment supports shared session ownership.

5.3 Save and Observe the Status

1. Save the radio and network-service settings.
2. Restart if the interface prompts you.
3. Read the gateway network address and check that it is valid for the LAN.
4. Check the selected service for a healthy connection.
5. Inspect the logs for authentication, DNS, time, or regional-setting errors.

6. Edge Application Integration

6.1 MQTT, HTTP, TCP, and WebSocket

Configure gateway application routes with local NS/AS software. For remote packet forwarding, set the application routes on the external server. Obtain endpoint settings and the payload schema from the application owner.

Interface	Typical use	Commissioning checks
MQTT	Publish uplinks and receive application downlinks	Broker connection, client identity, authentication, topic permissions, and TLS
HTTP	Push supported uplink, acknowledgement, and gateway-status messages	URL, method, authentication, response code, and timeout; use a supported separate path for downlinks
TCP	Gateway client connects to an application TCP server	Address, port, framing, keepalive, and reconnect behavior
WebSocket	Maintain a bidirectional application session	URL, authentication, heartbeat, reconnect, and message schema

MQTT, TCP, and WebSocket carry application downlinks. The documented API uses MQTT for device-list requests/responses and join events. Check the installed firmware's message support when choosing a protocol. Gateway MQTT transport and application MQTT use different message formats.

Test with a captured message to check JSON field names and case, payload encoding, and topic prefixes. Enable TLS where supported. Verify command execution from device status or the equipment; a LoRaWAN acknowledgement confirms frame reception.

6.2 JavaScript Data Processing

JavaScript scripts support:

• Decoding or encoding application payloads
• Converting uplink data to the application schema
• Adapting downlink data before radio transmission
• Scheduled data acquisition
• Local control rules triggered by device events

1. Define the input fields, output fields, units, and error behavior.
2. Test the script with representative uplink and downlink payloads.
3. Review the script for unexpected network access, uncontrolled loops, and accidental credential exposure.
4. Enable the script for one test device or application first.
5. Check the transformed data and edge logs before expanding the rule to production devices.

Version scripts with the gateway configuration backup.

6.3 Modbus TCP and Modbus RTU

The gateway maps LoRaWAN data to virtual Modbus holding registers. A PLC or supervisory system reads the gateway as a Modbus client/master; the gateway is the server/slave. This interface exposes mapped wireless data rather than polling instruments on RS485.

1. Enable the Modbus TCP or Modbus RTU processor in the application data-flow settings. Menu names depend on firmware and interface language.
2. For TCP, set the listening port and start the listener. For RTU, connect RS485 A/B and match the PLC serial settings; the documented initial setting is 9600 bps, 8 data bits, no parity, and 1 stop bit.
3. Create a mapping script that decodes the end-device uplink into holding registers. Define signedness, register width, byte order, scaling, units, and stale-data handling.
4. Bind the script to the corresponding end device and assign a unique Unit ID / slave address accepted by both systems. Use separate mappings for different payload formats.
5. Read a known register from the PLC or a test master using function 03. Compare it with the latest decoded uplink and check the client's address convention.
6. Enable register writes only if the script maps them to a downlink. Test one write with a safe load and verify execution at the end device.

Register reads return stored measurements rather than triggering a new wireless acquisition. Set a freshness timeout from the reporting interval. Verify writes at the end device; a Modbus response alone does not prove output operation.

Record the Unit IDs, register map, serial or TCP settings, script version, and verification results in the integration document.

7. End-Device Commissioning

7.1 Register LoRaWAN End Devices

Activation	Device credentials
OTAA	DevEUI, JoinEUI/AppEUI, and keys required by the selected LoRaWAN version, including AppKey
ABP	DevAddr and the session keys required by the Network Server

Apply the activation settings to the end device and its server record.

7.2 Check the First Join and Uplink

1. Power or reset one end device.
2. For OTAA, look for a successful join. For ABP, check that the server accepts an uplink with the provisioned session; ABP has no join exchange.
3. Verify uplink reception in the local or remote Network Server.
4. Inspect RSSI, SNR, frequency, and data rate in the radio records, then verify session and frame-counter acceptance in the server.
5. Check the application interface or Modbus map for the decoded value.
6. Test a downlink only after the uplink path is stable.

Add devices and application routes after the first device passes the complete data and control test.

8. Verification and Handover

Check	Expected result
Power	Gateway starts without repeated rebooting
Backhaul	Ethernet, Wi-Fi, or 4G obtains the expected network state
Radio	The selected plan and channel configuration are displayed correctly
Network service	The local or remote service shows a healthy gateway connection
End-device join	At least one test device joins or establishes its configured session
Uplink	Application data reaches the expected application, API, or Modbus register
Downlink	A permitted test downlink reaches the end device
Edge rule	JavaScript processing or local linkage produces the expected result, if enabled
Logs	No unresolved authentication, DNS, time, application, or RF errors remain

Record the final gateway address, frequency plan, channel configuration, software version, service mode, application routes, and responsible administrator in the project handover record. Store keys and passwords in the project credential store.

9. Maintenance and Upgrade

• Back up the gateway configuration, application routes, register maps, and JavaScript scripts before changing the system.
• Keep firmware, configuration backups, scripts, and commissioning records associated with the gateway identifier.
• Use a firmware package supplied for the exact Y511-L configuration.
• Maintain power and network access, and keep the browser open until the upgrade finishes.
• After an upgrade, verify the backhaul, radio plan, service mode, uplink, downlink, application route, and Modbus integration again.
• Before a factory reset, back up settings and check that you have the network details and credentials needed to restore access.

10. Troubleshooting

Symptom	Checks and corrective action
No power indicator	Check DC polarity, supply voltage, connector seating, and the ordered power source.
Cannot open the web interface	Check the subnet, DHCP lease, Ethernet or Wi-Fi link, and gateway address. Back up settings and arrange local access before a reset.
4G does not connect	Check SIM activation, APN, antenna connection, coverage, and whether the ordered cellular variant matches the local operator.
Remote service is offline	Check endpoint reachability, DNS, time synchronization, credentials, certificates, firewall rules, and server status.
Local service does not receive data	Check local NS/AS ownership, gateway and device registration, frequency plan, keys, and application routing.
Uplink arrives but application data is wrong	Check the JavaScript input format, byte order, scaling, units, port mapping, and the application schema.
Modbus values are wrong or unavailable	Check RS485 A/B wiring, serial parameters, slave address, register map, byte order, and read/write permission.
Uplink arrives but downlink fails	Check end-device class, downlink timing, channel compatibility, gateway transmit status, and regional duty-cycle or power limits.
Frequent link loss	Check antenna placement, interference, power stability, time synchronization, and gateway or server logs.
Configuration was changed but has no effect	Save the configuration, restart when requested, and verify that the running status reflects the saved values.

For support, provide the model configuration, frequency plan, service mode, software version, gateway identifier, time of failure, and a redacted log. Exclude passwords, device keys, and private server credentials.

---

YenGear
Hunan YenGear Tech Co., Ltd.
Room 21014, Building 1, Fudi Xingguang Tiandi, Yingxin Road, Yuhua District, Changsha, Hunan, China
[email protected] · www.yengear.com