LoRaWAN products

LoRaWAN Gateways & Field Devices

Bring RS232, RS485 and field I/O into your LoRaWAN network. Choose the gateway, end device and server configuration for your equipment.

Get Selection Advice Find Your Model

Gateway-based networking with a local or external Network Server.

Y501-L and Y511-L indoor gateway enclosure

Y501-L / Y511-LIndoor gateways

Y502-LSerial DTU

Y503-222-LI/O RTU

Choose your hardware

Start with what you need to connect.

Choose a gateway for the network, then a serial or I/O end device for the equipment. Already have a LoRaWAN network? Start with the field devices.

Build the network

Two indoor gateways. Choose the software around your server and application.

Indoor gateway

Y501-L

Forward LoRaWAN packets to an external Network Server. Local NS/AS is a software option.

Ethernet, Wi-Fi, RS485; optional 4G

View Y501-L Ask about this model

Indoor edge gateway

Y511-L

Decode payloads locally and map data to Modbus registers with the local NS/AS software option.

Ethernet, Wi-Fi, RS485; optional 4G

View Y511-L Ask about this model

Connect field equipment

Serial data or direct signals. Match the end device to the equipment interface.

Serial DTU end device

Y502-L

Poll serial equipment or carry serial frames over LoRaWAN. No onboard I/O channels.

1 isolated RS485 + 1 isolated RS232

View Y502-L Ask about this model

I/O RTU end device

Y503-222-L

Collect field contacts and analog signals, with voltage-output commands via LoRaWAN.

1 isolated RS485, 2 DI, 2 voltage DO, 1 AV + 1 AI

View Y503-222-L Ask about this model

Gateway images show the shared enclosure design. Antennas, connectors and hardware options depend on the ordered configuration.

From equipment to application

How the LoRaWAN system connects.

The end device collects your data. The gateway forwards radio packets. The Network Server manages device sessions, and the application interprets the payload.

Serial equipment connects to Y502-L via RS232 or RS485. Contacts and analog signals connect to Y503-222-L. Both send LoRaWAN traffic to a Y501-L or Y511-L gateway, then to an external Network Server and application. — External-server uplink path shown. Dashed arrows are LoRaWAN; solid arrows are wired or IP connections. Downlinks follow the reverse path, subject to device-class and regional limits.

Two wired paths: serial equipment to Y502-L, and contacts or analog signals to Y503-222-L. Both connect over LoRaWAN to Y501-L or Y511-L, followed by an external Network Server and application. — External-server uplink path shown. Dashed arrows are LoRaWAN; solid arrows are wired or IP connections. Downlinks follow the reverse path, subject to device-class and regional limits.

Using a local server?

The optional local NS/AS runs the Network Server and Application Server on the gateway. Those software services remain separate from the gateway’s radio-forwarding role.

Application integration

Where will your data be processed?

Use an existing Network Server, or specify the local NS/AS software option. Your server interface determines the configuration.

Y501-L or Y511-L

Forward packets to your Network Server.

Use Ethernet or Wi-Fi backhaul, with 4G available as an order option. Match the gateway forwarding interface and regional channel plan to the server.

Register end devices with their OTAA or ABP activation settings.
Configure the payload decoder and application delivery on the server.
Test uplinks and any required downlink commands with the installed equipment.

Y502-L and Y503-222-L support LoRaWAN 1.0.3 and Class A/C. Confirm compatibility with the selected server and region.

Read the gateway setup guide

Optional gateway software

Process device data on the gateway.

Local NS/AS is available for Y501-L and Y511-L. Choose Y511-L when the project needs JavaScript payload processing or Modbus TCP/RTU register mapping.

Application delivery: MQTT, HTTP, TCP or WebSocket, according to software configuration and supported message direction.
PLC / Modbus access: Y511-L can expose mapped end-device registers. Match the register map, byte order and scaling; measurements may come from an earlier uplink.

HTTP delivery covers uplinks, acknowledgements and gateway status; it is not a bidirectional control API. TCP framing and downlink mapping need application-specific integration.

Read the Y511-L integration manual

Equipment connections

Put the interface to work.

Typical configurations to discuss for your project. Equipment protocols, payloads and control behavior still need to be matched.

01 / SERIAL DATA

Read meters and serial instruments.

Y502-L polls Modbus RTU equipment or carries custom RS232/RS485 frames. Use it when the measurement already exists in a serial device.

See the serial DTU

02 / FIELD SIGNALS

Collect contacts and analog measurements.

Y503-222-L provides 2 DI, one 0–10 V input and one 4–20 mA input. Its two outputs switch supply voltage, not dry relay contacts.

See the I/O RTU

03 / EXISTING SYSTEMS

Bring device data into your application.

Use the Network Server’s application delivery, or Y511-L local-service interfaces and Modbus mapping. Check data age before using mapped values.

Compare integration paths

Before you specify

Three checks for a working deployment.

Match the regional plan, data traffic and equipment behavior before choosing the final configuration.

Match the radio region.

Node, gateway and Network Server must use a matching plan and channel group. Specify the installation country and AS923 sub-plan where applicable.

Frequency plans by model

Y501-L · Y511-L · Y502-L: CN470, EU433, EU868, AU915, IN865, AS923, RU864, US915
Y503-222-L: CN470, EU433, EU868, AU915, AS923, US915

Availability depends on the ordered variant. A listed frequency plan is not a certification or deployment approval.

Size the network for traffic.

Both gateways offer 8 RX / 1 TX or 16 RX / 2 TX configurations. Channel count is not a node-capacity rating.

Reporting interval, payload size, airtime, interference and downlink traffic determine usable capacity.

Class A or Class C?

Class A receives downlinks after an uplink. Class C keeps reception available more often. Neither guarantees fixed command latency; regional limits and network scheduling still apply.

Check wiring and control behavior.

All four models use 9–28 VDC power. Match serial settings and signal types; size the supply for the device and connected loads.

Y503-222-L has fixed AV/AI terminals and no analog output. Its DO voltage follows the supply.

Planning remote outputs?

Confirm output ratings, startup and communication-loss behavior, and independent local protection. Test the complete command and equipment-response path before unattended operation.

Technical resources

The details behind your selection.

Check electrical ratings in the specification, then use the manual for wiring, activation and configuration.

Y501-L

Y511-L

Y502-L

Y503-222-L

FAQ

Questions about LoRaWAN architecture, interfaces and product selection.

Looking for direct private LoRa I/O?

How is LoRaWAN different from Wireless I/O Modules?

LoRaWAN products use a LoRaWAN network with a gateway and Network Server. Y401, Y402 and Y403 Wireless I/O products use a private LoRa link for direct signal transfer. Choose the architecture before selecting the hardware.

Compare private LoRa Wireless I/O

Does a LoRaWAN gateway replace the Network Server?

Y501-L normally forwards radio packets to an external Network Server. Local Network Server / Application Server (NS/AS) software is available as an option for installations that need these services on the gateway.

Can Y511-L connect to an existing HTTP or TCP server?

With local NS/AS enabled, Y511-L supports HTTP uplink, acknowledgement and gateway-status delivery, and a TCP client connection to an application server. Match message fields, payload encoding, authentication and TCP framing. Downlink control needs a supported interface and application adaptation; HTTP delivery is not a bidirectional control API.

Can LoRaWAN guarantee an immediate output response?

LoRaWAN does not guarantee a fixed response time. Class A end devices receive downlinks in windows after an uplink. Class C provides more receive opportunities, but radio conditions, regional limits, gateway scheduling and server processing still affect delivery. Validate the application timing and use appropriate independent local protection.

Are the Y503-222-L outputs dry relay contacts?

No. Y503-222-L has voltage outputs that follow the RTU supply voltage. Check load voltage, current, wiring and protection against the specification before connecting equipment. Its analog inputs are one fixed 0–10 V AV channel and one fixed 4–20 mA AI channel; there is no analog output.

What information is needed to select a frequency plan?

Provide the installation country, regional plan and channel group, including the AS923 sub-plan where applicable. Match the node, gateway and Network Server configuration. Frequency availability varies by model, so confirm the exact variant before ordering.

Product selection

What do you want to connect?

Tell us your installation country and the equipment or signals. We’ll help choose the end device, gateway and server configuration. No model number needed.

If known, add your node count, reporting interval and existing server. Please leave device keys and passwords out of your message.