Y501-L LoRaWAN Indoor Gateway User Manual

• Y501-L Specification

Applicable configurations: Y501-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 Backhaul Configuration
6. End Device and Network Server Commissioning
7. Verification
8. Maintenance and Upgrade
9. Troubleshooting

1. Product Scope

Y501-L is an indoor LoRaWAN gateway for collecting LoRaWAN traffic and forwarding it to a Network Server. With the ordered software configuration, it also provides local network-service and application-service functions.

The product is available in two radio 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, or the installation position.
• Use only the antennas, power adapter, and cellular configuration approved for the ordered variant.
• Do not interrupt power during a firmware upgrade or configuration recovery.

2.2 Prepare Before Installation

Prepare the following items:

• Y501-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 information and the LoRaWAN end-device credentials

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 and status checks.
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 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 Backhaul 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 Select the Forwarding Mode

Use the mode specified by the deployment design:

• Remote Network Server mode: forward gateway traffic to the project Network Server through the configured gateway protocol and endpoint.
• Local service mode: use the local NS/AS functions only when the ordered configuration includes them and the site requires local processing.

For remote forwarding, configure the endpoint, port, authentication, and encryption settings supplied by the Network Server administrator.

For MQTT forwarding, use a gateway transport supported by the Network Server, including its message format and topics. An application MQTT broker alone does not replace a LoRaWAN Network Server. Configure TLS only where supported by both the gateway firmware and the endpoint.

The standard RS485 port requires compatible local-service software for Modbus data access. Confirm the gateway slave address, supported function codes, register allocation, byte order, and scaling before connecting a PLC. Do not assume packet-forwarding firmware polls RS485 instruments.

5.3 Save and Observe the Status

1. Save the radio and backhaul settings.
2. Restart only if requested by the configuration interface.
3. Confirm that the gateway has a valid network address.
4. Confirm that the forwarding status changes to connected or healthy.
5. Review the event or system log for authentication, DNS, time, or regional-configuration errors.

6. End Device and Network Server Commissioning

6.1 Register the Gateway

In remote Network Server mode:

1. Create or select the gateway record in the Network Server.
2. Enter the gateway identifier shown on the delivered unit or in the gateway information page.
3. Apply the gateway protocol, endpoint, and security settings required by the server.
4. Confirm that the server receives gateway status or traffic updates.

6.2 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.

6.3 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 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. Test a downlink only after the uplink path is stable.

Use one end device for the first test. Add the remaining devices after the basic path is confirmed.

7. Verification

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

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.
• 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, gateway registration, uplink, and downlink again.
• Restore factory settings only after recording the current configuration and confirming that site access is available afterward.

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 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.
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.

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