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 is an indoor LoRaWAN gateway for radio collection, Network Server connectivity, and edge data integration. It forwards traffic to a remote Network Server or provides local NS/AS services when the ordered configuration includes them.

Y511-L also supports application integration through MQTT, HTTP, TCP, or WebSocket, JavaScript-based data processing, and Modbus TCP/RTU integration on compatible configurations.

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

The channel count describes radio concurrency. It is not a fixed limit on the number of end devices.

2. Safety and Preparation

2.1 Safety Notes

• Read this manual before installation and keep it available for commissioning and maintenance.
• Use a regulated DC supply within 9 to 28 V; DC 12 V is the typical supply.
• Connect the LoRa antenna before applying power. Do not operate the radio with an open antenna connector.
• Install the gateway indoors in a dry, ventilated location away from excessive heat, water, and strong electromagnetic interference.
• Disconnect power before changing wiring, the SIM card, the RS485 wiring, or the installation position.
• Use only the antennas, power adapter, and cellular configuration approved for the ordered 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

Prepare the following items:

• Y511-L gateway and the supplied mounting hardware
• LoRa antenna and any ordered Wi-Fi or 4G antennas
• 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, according to the selected backhaul
• A computer or tablet on the same local network for the first configuration
• 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

Before powering the gateway, confirm the ordered frequency plan and channel configuration. The default plan is CN470. Supported plans are CN470, EU433, EU868, AU915, IN865, AS923, RU864, and US915.

3. Hardware Installation

3.1 Mount the Gateway

1. Check the enclosure, connectors, antenna cable, and power cable for shipping damage.
2. Install the supplied DIN-rail or wall-mount bracket as appropriate for the site.
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. Keep the LoRa antenna as high and unobstructed as practical. Avoid placing it directly beside large metal surfaces or high-power radio equipment.

3.2 Connect the Antennas and Backhaul

1. Connect the specified LoRa antennas to all required radio connectors. Antenna count and RX/TX connections depend on the channel and duplex configuration.
2. Connect the Wi-Fi antenna. Connect the 4G antenna only when the ordered configuration includes 4G.
3. Insert the SIM card while the gateway is powered off when using 4G.
4. Connect Ethernet, or prepare the local Wi-Fi network.
5. Connect RS485 A/B only when Modbus RTU is included in the deployment. Confirm the A/B polarity and the site wiring diagram.
6. Connect the DC supply only after the antenna and required network connections are ready.

Ethernet, Wi-Fi, and RS485 are standard interfaces. The cellular module, antenna, and SIM slot apply only to 4G configurations. Obtain an activated SIM separately unless it is included in the order. Connector names and the connector arrangement differ between 8-channel and 16-channel configurations; follow the labels on the delivered unit.

3.3 Power-On Check

After power-on:

• A steady Power indicator confirms power; check the management interface to verify startup.
• A steady LoRa indicator confirms radio startup. It does not confirm a connection to the Network Server.
• The Wi-Fi indicator shows startup status; the 4G indicator shows cellular status on 4G configurations. Verify the IP connection separately.

Allow the gateway to complete startup before changing configuration.

4. First Access and Basic Settings

4.1 Connect to the Configuration Interface

1. Connect a computer through Ethernet or the gateway Wi-Fi access point using the delivery instructions. Use local access for initial setup.
2. Use the management address and network mode in the delivery record. If Ethernet uses DHCP, find its lease in the router. For a static address, place the computer on the same subnet.
3. Open the complete management URL from the delivery record, including its port where specified, in a current Web browser.
4. Sign in with the credentials supplied through the secure delivery channel.
5. Change the initial password before connecting the gateway to a production network.

The management address, user name, and password are deployment-specific and delivered through the approved secure channel.

4.2 Set Basic Network Parameters

Configure the parameters required by the site:

• 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 changes and restart only when the interface requests a restart. Reconnect to the new address after the restart.

5. LoRaWAN and Network Service Configuration

5.1 Select the Radio Variant

Set the frequency plan that matches the ordered hardware and the local regulatory requirement:

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

Then confirm:

• 8-channel or 16-channel radio configuration
• Half- or full-duplex hardware and the required antenna connections
• End-device LoRaWAN version and Class A/C profile in the Network Server
• Transmit power and channel group allowed for the selected region

Match the gateway receive channels to the end-device channel mask and the Network Server plan. For AS923, also match the sub-plan. A menu option does not establish hardware support. Activation keys and device class belong to the end-device record in the local or remote Network Server, not to the packet-forwarding radio settings.

5.2 Choose Remote or Local Network Services

Use the mode specified by the deployment design.

Remote Network Server Mode

Use this mode when a separate Network Server manages gateway registration, device sessions, joins, keys, and applications.

1. Configure the gateway forwarding protocol and remote endpoint.
2. Configure authentication and encryption values supplied by the server administrator.
3. Register the gateway identifier in the Network Server.
4. Confirm that the Network Server receives gateway status or traffic updates.

The endpoint, port, credentials, topic names, and certificates are project-specific. Keep them in the approved secure configuration record.

Local NS/AS Mode

Use this mode only when the ordered configuration includes local NS/AS services.

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. Confirm local uplink and downlink operation before connecting external application systems.

Do not enable both local and remote ownership of the same device session unless the deployment design explicitly supports that topology.

5.3 Save and Observe the Status

1. Save the radio and network-service settings.
2. Restart only if requested by the configuration interface.
3. Confirm that the gateway has a valid network address.
4. Confirm that the selected remote or local service reports a healthy state.
5. Review the event or system log for authentication, DNS, time, or regional-configuration errors.

6. Edge Application Integration

6.1 MQTT, HTTP, TCP, and WebSocket

These application interfaces use the local NS/AS configuration. In remote packet-forwarding mode, configure application integration 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

The documented downlink paths are MQTT, TCP, and WebSocket. Device-list request/response and join events use MQTT in the reviewed API. Confirm the message support of the delivered firmware before selecting a protocol. Gateway MQTT transport and application MQTT use different message contracts.

Use a test endpoint first. Verify exact JSON field names, case, payload encoding, and topic prefixes against a captured message. Use TLS where the chosen interface supports it. A LoRaWAN acknowledgement confirms frame reception; verify command execution from device status or the controlled equipment.

6.2 JavaScript Data Processing

Y511-L uses JavaScript scripts for functions such as:

• Decoding or encoding application payloads
• Transforming uplink data into the project schema
• Adapting downlink data before radio transmission
• Scheduled data acquisition
• Local linkage between device events and edge actions

Configuration steps:

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.

Keep a versioned copy of every script with the corresponding gateway configuration backup.

6.3 Modbus TCP and Modbus RTU

The gateway exposes LoRaWAN data as virtual Modbus holding registers. The PLC or supervisory system acts as the Modbus client/master; the gateway acts as the server/slave. This mapped-data interface is distinct from polling instruments connected directly to 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. From the PLC or a test master, read a known register using function 03. Compare it with the latest decoded uplink and confirm the address convention used by the client.
6. Configure register writes only if the mapping script defines the resulting downlink. Test one write with a safe load and confirm execution at the end device.

A successful register read can return the last stored measurement; it does not force a new LoRaWAN acquisition. Set a freshness timeout based on the reporting interval. Likewise, a successful write response does not prove that a wireless output has switched.

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

For OTAA devices, prepare the device identifiers and keys required by the selected LoRaWAN version, such as DevEUI, JoinEUI/AppEUI, and AppKey.

For ABP devices, prepare the DevAddr and session keys required by the Network Server.

Use the same regional plan, channel group, and LoRaWAN settings consistently across the gateway, Network Server, and end devices.

7.2 Check the First Join and Uplink

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

Use one end device and one application route for the first test. Add the remaining devices and routes after the complete path is confirmed.

8. Verification and Handover

Complete this checklist before 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. Keep keys and passwords in the approved secure system.

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.
• Keep stable power during an upgrade; do not close the browser or disconnect the network unless the upgrade procedure says it is complete.
• After an upgrade, verify the backhaul, radio plan, service mode, uplink, downlink, application route, and Modbus integration again.
• Restore factory settings only after recording the current configuration and confirming that site access is available afterward.

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 local subnet, DHCP lease, Ethernet or Wi-Fi link, and the gateway address. Use reset only with authorization.
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.

If the issue remains, 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