Appearance
Y501-L LoRaWAN Indoor Gateway User Manual
Applicable configurations:
Y501-L, 8-channel or 16-channel
Contents
- Product Scope
- Safety and Preparation
- Hardware Installation
- First Access and Basic Settings
- LoRaWAN and Backhaul Configuration
- End Device and Network Server Commissioning
- Verification
- Maintenance and Upgrade
- Troubleshooting
1. Product Scope
Y501-L forwards LoRaWAN traffic to an external Network Server. Optional local Network Server (NS) and Application Server (AS) software runs device sessions and application services on the gateway.
| 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 Vsupply; 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, or the installation position.
- Use antennas, a power adapter, and a cellular module suitable for the supplied hardware variant.
- Do not interrupt power during a firmware upgrade or configuration recovery.
2.2 Prepare Before Installation
- Y501-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 information and the LoRaWAN end-device credentials
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
- Inspect the enclosure, connectors, and antenna and power cables for shipping damage.
- Fit the supplied DIN-rail or wall-mount bracket.
- Keep the gateway accessible for configuration and status checks.
- Connect the enclosure earth terminal according to the site grounding design. Use one DC source; the jack and power terminals are connected in parallel.
- Mount the LoRa antenna high and clear of obstructions, large metal surfaces, and high-power radio equipment.
3.2 Connect the Antennas and Backhaul
- Attach the specified antennas to the required LoRa RX/TX connectors. Use the antenna count and connections specified for the channel and duplex hardware.
- Attach the Wi-Fi antenna and, on 4G units, the cellular antenna.
- For 4G, insert the SIM card with power off.
- Connect Ethernet, or prepare the local Wi-Fi network.
- 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
- Use Ethernet or the gateway Wi-Fi access point for initial local setup. Follow the supplied network settings.
- For DHCP, find the gateway lease in the router. For a static address, put the computer on the same subnet.
- Open the supplied management URL in a browser, including the port if specified.
- 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 Backhaul 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 Select the Forwarding Mode
- Remote Network Server: forward traffic using the server's gateway protocol and endpoint.
- Local NS/AS: run network and application services on the gateway with the required software option.
For remote forwarding, enter the endpoint, port, authentication, and encryption settings supplied by the server administrator.
For MQTT forwarding, use the Network Server's gateway message format and topics. An application broker still requires a Network Server. Enable TLS when both the gateway firmware and endpoint support it.
RS485 Modbus data access requires compatible local-service software. Before PLC integration, obtain the gateway role, slave address, function codes, register map, byte order, and scaling. Packet forwarding does not establish support for polling RS485 instruments.
5.3 Save and Observe the Status
- Save the radio and backhaul settings.
- Restart if the interface prompts you.
- Read the gateway network address and check that it is valid for the LAN.
- Look for a connected or healthy forwarding status.
- Inspect the logs for authentication, DNS, time, or regional-setting errors.
6. End Device and Network Server Commissioning
6.1 Register the Gateway
In remote Network Server mode:
- Create or select the gateway record in the Network Server.
- Enter the gateway identifier shown on the delivered unit or in the gateway information page.
- Apply the gateway protocol, endpoint, and security settings required by the server.
- Look for gateway status or traffic updates in the server.
6.2 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.
6.3 Check the First Join and Uplink
- Power or reset one end device.
- 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.
- Verify uplink reception in the Network Server.
- Inspect RSSI, SNR, frequency, and data rate in the radio records, then verify session and frame-counter acceptance in the server.
- Test a downlink only after the uplink path is stable.
Add other devices after the first device completes the uplink and downlink tests.
7. Verification
| 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 |
| Gateway registration | The Network Server shows the gateway as connected or receiving traffic |
| End-device join | At least one test device joins or establishes its configured session |
| Uplink | Application data reaches the expected application or data service |
| Downlink | A permitted test downlink reaches the end device |
| Logs | No unresolved authentication, DNS, time, or RF errors remain |
Record the final gateway address, frequency plan, channel configuration, software version, and responsible administrator in the project handover record. Store keys and passwords in the project credential store.
8. Maintenance and Upgrade
- Back up the gateway configuration before changing radio, network, or forwarding parameters.
- Keep firmware, configuration backups, and commissioning records associated with the gateway identifier.
- Use a firmware package supplied for the exact Y501-L configuration.
- Maintain power and network access, and keep the browser open until the upgrade finishes.
- After an upgrade, verify the backhaul, radio plan, gateway registration, uplink, and downlink again.
- Before a factory reset, back up settings and check that you have the network details and credentials needed to restore access.
9. 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. |
| Gateway is online but no uplink arrives | Check frequency plan, channel group, gateway registration, end-device keys, antenna connection, and server status. |
| 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, 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
