RAK2461 WisNode Bridge IO Lite Quick Start Guide

Prerequisite

Before going through each and every step in the installation guide of the WisNode Bridge IO Lite, make sure to prepare the necessary items listed below:

Hardware

1. RAK2461 WisNode Bridge IO Lite
2. USB Type-C configuration cable
3. Gateway in range
4. A Windows/macOS/Linux Computer

Software

IO.Box Desktop is a software application that will allow you to configure the devices from the RAK24XX series. You can download the application from here:

• Windows
• Linux (coming soon)
• Mac (coming soon)

Package Inclusions

Variant for Wall Mounting

Figure 1: RAK2461 Package Inclusions 1

• One (1) RAK2461 WisNode Bridge IO Lite (RS485-DIx4-DOx1 or RS485-DOx4)
• One (1) Screw Kit
• One (1) LoRa Antenna
• One (1) Power Adapter
• One (1) USB Cable (Type C to Type A)
• One (1) 4-Pin Terminal Block
• Two (2) 8-Pin Terminal Block

Variant for DIN Rail Mounting

Figure 1: RAK2461 Package Inclusions 2

• One (1) RAK2461 WisNode Bridge IO Lite (RS485-DIx4-DOx1 or RS485-DOx4)
• One (1) DIN rail Mounting Kit
• One (1) LoRa Antenna
• One (1) Power Adapter
• One (1) USB Cable (Type C to Type A)
• One (1) 4-Pin Terminal Block
• Two (2) 8-Pin Terminal Block

Installation

RAK2461 allows for two installation methods: wall mounting and DIN rail installation.

Wall Mounting

1. Drill the wall corresponding to the device dimensions and insert the anchors in the holes.

Figure 1: Hole drilling

2. Fix the device to the wall with two tapping screws.

Figure 1: Wall mounting

DIN Rail Mounting

1. Attach the DIN rail mounting clip on the device with two M3*6 countersink screws.

Figure 1: Attaching the clip

2. Mount the device to the DIN rail.

Figure 1: DIN rail mounting

Connect the RAK2461 to the Device

In this section, we will demonstrate how to use different interfaces on the RAK2461 to connect devices.

NOTE

For connecting to other devices, read their specific documentation carefully and connect accordingly.

RS485 Sensor Application

In this section, the RK520-02 Soil Moisture, Temperature and Electrical Conductivity Sensor will be used as an example.

1. Connect the sensor device to the RAK2461.

Figure 1: Data interface connection

Here are the basic communication parameters of the RK520-02 sensor:

Parameter	Definition
Format	8-bit binary
Data bit	8-bit
Parity	No
Stop bit	1
Error checking	CRC
Baud rate	9600

Digital Input Sensor Application

In this section, the DH-ARD631-50 Outdoor Active PIR sensor will be used as an example.

1. Have two devices, one transmitter and one receiver.
2. The transmitter's POWER(1/2) is connected to the Vout and GND of the bridge.
3. The receiver's POWER(2/3) is connected to the 12V_Out and GND of the bridge.
4. The receiver's ALARM(5/6) is connected to the DI4 COM and DI4 IN of the bridge.

Figure 1: Sensor to Bridge wiring

Digital Output for Switching Application

1. You can connect any module or device to the port of the Digital Output as long as it operates on the recommended voltage rating.

Figure 1: Wiring

Power On the RAK2461

1. The RAK2461 device can be powered either by:

• 9-24 V_DC input
• USB type-C

The USB type-C port of the device can be used for configuration. Powering the device from the type-C port will not provide power to the sensor connected to Vout but only to the device itself. To power the device and sensor, you should use the 9-24 V_DC input of the RAK2461.

Figure 1: Power interface connection

Connect the RAK2461 to the IO.Box

1. Download and open the IO.Box application.

2. Connect the RAK2461 to a computer using the USB type-C cable.

   NOTE

   • Note that this will work for the LoRaWAN configuration, but when configuring the sensor you would need to connect the 9-24 V_DC power supply in order to provide power to the sensor itself.
   • Make sure that the USB type-C cable that you are using supports data transfer and no other serial software is connected to the COM port that RAK2461 uses.

3. Click Connect Device in the IO.Box console.

Figure 1: IOBox get started

If an error occurs that shows no device detected, here are some possible causes for that and how to fix it:

• Double-check the quality of the USB cable and if the correct COM port is used.
• Check if other terminal software is active and still connected to the RAK2461.

Figure 1: No device error

4. On the IO.Box dashboard screen, you can see information about the devices connected to the PC in the form of a list of connected devices with device models and EUIs. Choose the device that you wish to configure via the Connect button next to it.

5. On the main menu to the left, choose LoRaWAN to configure the LoRaWAN settings as needed. Do not forget to click Save below the changes.

• Device Status: Indicates the device’s connection status to the LoRaWAN network.

  • Red: The device is not connected to the LoRaWAN network.

  • Green: The device has successfully joined the LoRaWAN network.

• Device EUI: The unique identifier of the device.

• Region: Specifies the LoRaWAN frequency band used by the device. In this document, US915 is selected.

• Sub-band: Select the specific frequency sub-band based on the region's frequency plan. For US915, sub-bands 8–15 and 65 are selected.

• Public Network Mode: Determines whether standard LoRaWAN public network parameters are used. Enabled in this document.

• Join Mode: Defines how the device joins the LoRaWAN network. OTAA (Over-The-Air Activation) is selected.

• Class: The type of LoRaWAN communication used by the device. Select Class C.

• Application EUI: The application identifier for the device. Ensure it matches the Application EUI configured in the LoRa network server.

• Application Key: The security key for device-server encryption and authentication. Ensure it matches the Application key in the LoRa network server.

• Confirmed Mode: Message acknowledgment mode. Enabled in this document.

• ADR: Enable Adaptive Data Rate allowing the network server to control the data rate for your device. Enabled in this document.

Figure 1: LoRaWAN tab

Interface Configuration

This section shows the interface configuration references for different applications.

RS485 Interface

RS485 Interface Configuration

1. Go to the System tab from the main menu. Enable the DC12 V Output. Note that the power output interface connected to the example sensor is enabled here. Please enable the power output interface that your sensor is actually connected to.

Figure 1: Enable the power output

2. Go to the RS485 tab from the main menu and configure the interface according to the sensor/device you are connecting to. Do not forget to save your changes. In this tab, you will find:

• Baudrate: Select the communication speed for the RS485 interface, measured in bits per second. Choose a rate that matches your device's requirements.
• Databits: Select the number of data bits for each character in the RS485 communication. Typically, options include 7 or 8 bits, depending on your device's protocol requirements.
• Stopbits: Select the number of stop bits used in the RS485 communication. Common options are 1 or 2, depending on your device's data transmission protocol.
• Parity: Select the parity setting for the RS485 interface. Options typically include None for no parity, Even for even parity, or Odd for odd parity. Choose based on your device's communication requirements.

Figure 1: RS485 interface configuration

Add Modbus Poll Task

This section shows how to create a polling task with an integer data type. If you need to create a polling task with a raw binary data type, refer to (Optional) Add a Raw Data in Binary Poll Task.

1. In the Modbus Poll Task menu click +Add for a new poll. You will see the Polling Task parameters that need to be configured.

Figure 1: Add poll task

2. Fill in the relevant fields according to the specific sensor's datasheet. Here we create a temperature polling task as an example.

Figure 1: Add temperature polling task

• Channel ID: Enter the identifier for the polling task. This ID is included in the device’s uplink data to indicate the task.
• Name: Custom name, length: 4-15.
• Device Address: The Modbus slave address in decimal format. Range: 1-254.
• Function Code: The Modbus function code defines this poll's operation.
• Register Address: The address of the register that you wish to access in hexadecimal format.
• Quantity: The number of register addresses that you want to access.
• Data Type: The data type of the Modbus response.
• Scale: To adjust the raw data from the Modbus response to the desired units. For example, to convert kilograms to grams set the scale to X1000.
• Sensor Type: Choose the unit of the data obtained from the Modbus slave device.
• Interval: The frequency at which the device sends Modbus requests (polling period). Range: 5 to 86400 seconds. The default value 60 is used.
• Enable: Enable or disable this polling task.
• Request: Displays the Modbus command generated based on the settings you've selected above. This command will be used to communicate with the Modbus device.
• Response: Displays the response received from the Modbus slave device.
• Value: Shows the parsed value extracted from the Response, based on the configuration above.
• Uplink Data: Displays the data payload format that will be sent to the server, based on the configuration above.

3. Before saving the task click Check for automatic validation.
4. Save the polling task.
5. Create moisture and EC polling tasks in the same way.

Figure 1: Add moisture polling task

Figure 1: Add EC polling task

Figure 1: Created polling tasks

(Optional) Add a Raw Data in Binary Poll Task

1. In the Modbus Poll Task menu click +Add for a new poll. You will see the Polling Task parameters that need to be configured.

Figure 1: Add poll task

2. Fill in the relevant fields according to the specific sensor's datasheet. Here we create a temperature polling task as an example.

Figure 1: Add temperature polling task

• Channel ID: Enter the identifier for the polling task. This ID is included in the device’s uplink data to indicate the task.
• Name: Custom name, length: 4-15.
• Device Address: The Modbus slave address in decimal format. Range: 1-254.
• Function Code: The Modbus function code defines this poll's operation.
• Register Address: The address of the register that you wish to access in hexadecimal format.
• Quantity: The number of register addresses that you want to access.
• Data Type: The data type of the Modbus response.
• Sensor Type: Choose the unit of the data obtained from the Modbus slave device.
• Interval: The frequency at which the device sends Modbus requests (polling period). Range: 5 to 86400 seconds. The default value 60 is used.
• Enable: Enable or disable this polling task.
• Request: Displays the Modbus command generated based on the settings you've selected above. This command will be used to communicate with the Modbus device.
• Response: Displays the response received from the Modbus slave device.
• Value: This shows the data extracted from the Modbus Response is parsed according to the above configuration.
• Uplink Data: Displays the data payload format that will be sent to the server, based on the configuration above.

3. Before saving the task click Check for automatic validation.
4. Save the polling task.
5. Create moisture and EC polling tasks in the same way.

Figure 1: Add moisture polling task

Figure 1: Add EC polling task

Figure 1: Created polling tasks

Digital Input Interface

1. Go to the System tab from the main menu.

2. Enable the DC Vout Output and the DC 12 V Output power outputs. Note that the power output interface connected to the example sensor is enabled here. Please enable the power output interface that your sensor is actually connected to.

Figure 1: Enable the power outputs

3. Go to the DI/DO tab. After enabling DI4 and reloading, you will see the input state enabled.

• Port ID: Identifies the physical DI port, corresponding one-to-one with the Bridge I/O hardware interface. Automatically assigned by the system and cannot be modified.

• Channel ID: Uniquely identifies the input channel within the system for data reporting and logical processing. Automatically assigned by the system and cannot be modified. Used in LoRaWAN or system data frames.

• Debounce: Prevents false triggering due to mechanical switch bouncing. Sets the signal stabilization time. Only signals stable beyond this duration are considered valid inputs. The Debounce is set to 50 ms.

• Interval (s): Specifies the frequency at which the device polls and reports the digital input state. Range: 5 to 86400 seconds. The default value 60 is used.

• Enable: enable/disable the channel. Controls whether the input channel participates in polling and data reporting. Monitoring occurs only when enabled. Default: disabled.

• Input State: Shows the real-time input level status (high or low) of the port. The status updates in real-time when a valid signal is input from the external device. Read-only.

Figure 1: Enable DI4

Digital Output Interface

1. Go to the DI/DO tab from the main menu.

• Port ID: Identifies the physical DO port, corresponding one-to-one with the Bridge I/O hardware interface. Automatically assigned by the system and cannot be modified.

• Channel ID: Uniquely identifies the output channel within the system for command issuance and status tracking. Automatically assigned by the system and cannot be modified. Used as an address identifier in control commands or data frames.

• Output State: Controls the output level (high or low) of the port for controlling external devices. The state changes according to system or user commands. Writable parameter.

• Interval (s): Specifies the frequency at which the device polls and reports the digital output state. Range: 5 to 86400 seconds. The default value 60 is used.

• Enable: enable/disable the output channel. The Output State takes effect only when enabled. Default: disabled.

2. When the output state is enabled, the left bulb is supplied. When it is disabled, the right bulb is supplied.

Figure 1: Output state

3. Enable the Enable button to activate the polling task for this digital output port and report the current state of the port.

Connect the RAK2461 to LoRa Network Server

This section provides you with operation guidance for connecting the RAK2461 to different LoRaWAN network servers.

Built-in Network Server

In this section, the RAK2461 Bridge Lite IO will be connected to an RAKwireless gateway. For the gateway, the built-in LNS will be used.

Set-up the Built-in Network Server

1. Start by accessing the gateway. Refer to the appropriate WisGateOS 2 user manual depending on the gateway you are using:
   • WisGateOS 2 for Edge/SoHo Gateways
   • WisGateOS 2 for X Industrial Gateways

Figure 1: WisGateOS 2 login page

2. Once logged in, head to the LoRa menu.

Figure 1: LoRa page

3. By default, the gateway works as a Built-In Network Server. If not, switch the Work mode to Built-in network server.

Adding Application

1. Once the gateway is in Built-in network server mode, head to the Applications tab.

Figure 1: Create Application in the Built-In Network Server

2. Click the Add application button or add one now link to add a new application. On the new page, fill in the following information:

Figure 1: Adding application

• Application name: type a name for the application.
• Application description: optionally you can write a description of the application.
• Application Type: from the drop-down menu select the type of application.
• Unified Application key: all devices will use the same application key. Selecting this option pops up an Application Key field. This value needs to be consistent with the value from the end device. You can type your application key there or use the Autogenerate button to generate one.

Figure 1: Unified application key

The Auto Add Device switch activates the Application EUI field. The device will be automatically added to the application after the application EUI and key verification.

Figure 1: Auto add device

• Separate Application keys: each device will have its own application key. The key is added when registering the device.
• Payload type: from the drop-down, select CayenneLPP payload type and turn on the Only forward data object feature.

3. Once set, click Save application to add the application.
4. After the application is added, head to the End devices tab. The devices should automatically register upon join request if you are using the Auto Add Device feature. If that’s not the case, click the Add end device button. On the End device information page fill in the following information:

Figure 1: Successfully created application

• Activation Mode: choose the activation mode of your device.
  • OTAA
  • ABP: This mode pops up two additional fields:
    • Application Session Key
    • Network Session Key
• End device (group) name: the name of the device.
• End device description (optional): optionally, you can add a description for the device.
• Class: the class of the device.
• Frame Counter width: the width of the frame counter. Leave it as default.
• LoRaWAN MAC Version: the LoRaWAN MAC version.

Adding the Device

1. Once everything is set, click Add end devices to go to the page and add the device.

2. On the Adding end devices page, type the device EUI at the End Device EUI (main) and click Add to “End Devices list”.

Figure 1: Adding end device

• If the EUI is correct, the device will show in the End devices list.

• If the EUI is not correct, the devices will show in the End devices with an error.

3. Once the device is added to the End devices list click Add end devices. Confirm you are adding the device.

Figure 1: Confirmation message for adding a device

4. After the device has successfully joined the LNS, you will see the LoRaWAN status in the IO.Box console toggles as activated. You might need to refresh the page.

Figure 1: Device is online

Figure 1: LoRaWAN status

Wait a while and you will see the uplink data from the LoRaWAN network.

The following is an example of RS485 application uplink data. The format of the uplink message would be as follows:

01 + 67(tem) + 00cb(Hex) 20.5(Dec) 20.5℃ 02 + 70(RH) + 0124(Hex) 292(Dec) 29.2%

03 + 7f(EC) + 0000dea8(Hex) 57000(Dec) 57.000us/cm

Figure 1: Uplink data

The Things Network (TTN)

Gateway Configuration

Registering the Gateway

1. Log in first and head on to TTNv3 website. If you already have a TTN account, you can use your The Things ID credentials to log in.

Figure 1: Login

2. To register a commercial gateway, choose Gateways tab. Click +Register gateway.

Figure 1: Add a gateway

3. In the Gateway EUI field, type the EUI of the gateway. Click on Confirm. The gateway's EUI can be found either on the sticker on the casing or by going to the Dashboard > Overview page via the Web UI. Instructions on how to access your gateway via Web UI can be found in the product's Quick Start Guide.

Figure 1: Add gateway EUI

4. After typing the EUI, click on Confirm. Additional fields will pop up. Fill in the following information:

• Gateway ID: This will be the unique ID of your gateway in the Network. An ID based on the EUI is automatically generated. You can change it if you need. Note that the ID must contain only lowercase letters, numbers, and dashes (-).
• Gateway name: Optionally, you can type a name for your gateway.
• Frequency plan: The frequency plan used by the gateway.

Figure 1: Configure parameters

5. To register your gateway, click Register gateway.

Figure 1: Successfully added a gateway

Generating the Token

1. To generate a key file, click API keys in the left navigation of the registered gateway.

2. On the API keys page, choose +Add API key.

Figure 1: API key page

3. In the Name field, type the name of your key (for example - mykey). Choose Grant individual rights and select Link as Gateway to a Gateway for traffic exchange, i.e. write uplink and read downlink.

Figure 1: Generate an API key

4. To generate the key, choose Create API key. The following window will pop up, telling you to copy the key you just generated.

Figure 1: Copying the generated key

warning

Copy the key and save it in a .txt file (or other), because you won’t be able to view or copy your key after that.

5. Click I have copied the key to proceed.

Configuring the Gateway

1. To configure the gateway, access it via the Web UI. To learn how to do that, refer to the Quick Start Guide.
2. Navigate to LoRa > Configuration. Configure the following parameters and save.

Figure 1: Configure the gateway parameters

• Basics Station Server Type: For server type, choose LNS Server.
• Server URL: This is the link to The Things Stack server. Note that, for this tutorial, the gateway is connected to the European cluster. For Europe fill in the following:

wss://eu1.cloud.thethings.network

• Server Port: The LNS Server uses port 8887. Type in 8887.

• Authentication Mode: Choose TLS server authentication and Client token. When selected, the Trust (CA Certificate) and Client token fields will show up.

• Trust (CA Certificate): For trust, upload the Let’s Encrypt ISRG ROOT X1 Trust certificate by clicking choose file. The file with the certificate can be downloaded directly .

• Client Token: This is the generated API key.

3. To save the changes, click Save Changes. If everything is set correctly, you can see the gateway is connected to TTNv3.

Figure 1: Successful connection

RAK2461 Configuration

IO.Box supports creating applications and automatically adding node devices to the TTN network server.

Creating Application

1. Navigate to the Integration > Onboard to The Things Stack Server to create a device profile, then click OK.

Figure 1: Application list

2. Click Create New to create a TheThingsStack Server and configure the following parameters.

Figure 1: Create a TheThingsStack Server

• Name: The name of TheThingsStack Server.

• Server Address: The ThingsStack Server address. In this case, it is eu1.cloud.thethings.network. The default port is 1884.

• User ID: Your User ID, which can be obtained from Profile settings > Edit profile.

• API Key: Your personal API key. You can create one by following the steps below.

  1. To create a personal API key, go to Home > User settings > API keys in the left-hand sidebar and click +Add API key.

  2. Enter a Name for your key, set the Expiry date, select rights that you want to grant and then press Create API Key.

     Figure 1: Create API key

  3. You will see a screen that shows your newly created API Key. You now can copy it in your clipboard by pressing the copy button. After saving the key in a safe place, press I have copied the key. You will not be able to see this key again in the future, and if you lose it, you can create a new one by following this same procedure.

     Figure 1: Copy API key

3. Click Create to save the configuration.

Figure 1: Created server

4. Click the created server, then click Create New to create an application.

Figure 1: Create an application

5. The newly created application will appear at the top of the list based on the creation time.

Figure 1: Create an application

Adding the device

1. Click the newly created application. In the Add New The Things Stack Server dialog, click OK to confirm the registered device information.

Figure 1: Register the device

2. After the device is created successfully, you can view the added device in the TTN.

Figure 1: Added device in the TTN

3. To activate the device, click Apply.

Figure 1: Active the device

4. After a successful Apply, the device in the TTN is activated and receives data as shown in Figure 62.

Figure 1: Device is online

Figure 1: Data details

You will also see the LoRaWAN activation status in the IO.Box console enabled.

Figure 1: LoRaWAN status

ChirpStack

This guide will show you how to connect the RAK2461 to a ChirpStack network server. In this tutorial, the ChirpStack v4 network server is used as an example.

Gateway configuration

Registering the Gateway

1. To register the gateway in the ChirpStack network server, access the ChirpStack UI. To do that, open a web browser and type the server address of the ChirpStack with port 9480.

<IP address of ChirpStack>:9480

2. Login using the following credentials:

   • Username/email: admin

   • Password: admin

Figure 1: ChirpStack login page

3. On the left pane, head to Gateways.

Figure 1: Gateway list

4. To register one, click Add gateway.

5. In the General menu, you need to set the gateway parameters.

Figure 1: Registering the gateway

• Name: Unique name for the gateway on the network server. The name may only contain words, numbers, and dashes.

• Description: A brief description of the gateway.

• Gateway ID (EUI64): The Extended Unique Identifier (EUI) of the gateway. The EUI is in the Dashboard > Overview of the gateway Web UI.

• Stats interval (secs): The expected interval in seconds in which the gateway sends its statistics.

6. Click Submit. You will see the registered gateway in the Gateway list.

Figure 1: Registered gateway

Configuring the Gateway

In this section, you will configure the gateway’s packet forwarder to send data to the ChirpStack Gateway Bridge.

1. To configure the gateway, access it via the Web UI. To learn how to do that, refer to the Quick Start Guide.
2. Navigate to LoRa > Configuration. Configure the following parameters and save.

Figure 1: Configure gateway parameters

• Work mode: Packet forwarder.

• Protocol: Semtech UDP GWMP Protocol.

• Server address: Your ChirpStack server IP address.

• Server Port: The default port is 9470. If the UDP port enabled on your ChirpStack server is not 9470, this value should be consistent with the UDP port enabled on the server.

3. Click Save changes to save the changes.

4. If everything is set correctly, the gateway will display as online. You can click the gateway name to inspect the gateway traffic.

Figure 1: Registered gateway

RAK2461 Configuration

IO.Box supports creating applications and automatically adding node devices to the ChirpStack server.

Creating Application

1. Navigate to the Integration tab and choose the Onboard to ChirpStack Server to create a device profile. Click OK.

Figure 1: Create a device profile

2. Click Create New to create a ChirpStack Server and configure the following parameters.

Figure 1: Create a ChirpStack Server

• Name: The name of ChirpStack server.

• Server Address: The ChirpStack server address. The default port is 9480.

• Auth Method: Password or API Key. Here we use API key.

• API Key: ChirpStack server API key. You can create one by following the steps below.

  1. To create a personal API key, go to Network Server > API keys in the left-hand sidebar and click Add API key.

  2. Enter a Name for your key and then press Submit.

     Figure 1: Create API key

  3. You will see the newly created API Key. Copy the key and save it in a safe place, press Back. You will not be able to see this key again in the future, and if you lose it, you can create a new one by following this same procedure.

     Figure 1: Copy API key

• Tenant: ChirpStack.

3. Click Create to save the configuration.

Figure 1: Created server

4. Click the created server, then click Create New to create an application.

Figure 1: Create an application

5. The newly created application will appear at the top of the list based on the creation time.

Figure 1: Create an application

Adding the device

1. Click the newly created application. In the Register End Device to Chirpstack dialog, click Create to confirm the registered device information.

Figure 1: Register the device

2. After the device is created successfully, you can view the added device in the ChirpStack.

Figure 1: Added device in the ChirpStack

3. To activate the device, click Apply.

Figure 1: Active the device

4. After a successful Apply, the device in the ChirpStack is activated and receives data.

Figure 1: Device is online

Figure 1: Data details

You will also see the LoRaWAN activation status in the IO.Box console enabled.

Figure 1: LoRaWAN status

Remote Device Configuration via LoRaWAN Downlink

The Bridge IO device can be configured remotely through LoRaWAN downlink commands. This method allows you to modify parameters for the RS485 (Modbus), Digital Input (DI), and Digital Output (DO) interfaces, enabling control of connected peripheral devices such as sensors and actuators.

NOTE

The FPort for configuration commands must be set to 10, except for toggling a DO channel's output state (ON/OFF), which requires FPort 1.

General Command Format

All configuration downlinks follow this structure:

[Channel ID] [Command Code] [Payload]

Command Code Breakdown

The Command Code is a single hexadecimal byte where each bit group defines a specific action. Please refer to the following table for details.

Bit Position	Function	Value & Meaning
Bit 7	Get/Set	0: Get (Read parameters) 1: Set (Write parameters)
Bits 3-6	Channel Type	0: DI (Digital Input) 1: DO (Digital Output) 7: Modbus (RS485 interface)
Bit 2	Enable/Disable	0: Disable  1: Enable
Bits 0-1	Parameter Mode	00: Combined (Configure all parameters together) 01: Individual (Configure parameters individually)

Command Example

Combined Setting Example

A typical combined write command looks like this:

01 BC 01 03 00 00 00 01 04 3D CC CC CD 67 00 00 00 3C

• 01: Channel ID. Corresponds to the channel number shown in the device management interface.

• BC: Command Code. To understand it, convert BC (hex) to binary: 1011 1100.

  • Bit 7 = 1 → Set (Write command)

  • Bits 3-6 = 0111 (decimal 7) → Modbus channel

  • Bit 2 = 1 → Enable the channel

  • Bits 0-1 = 00 → Combined parameter mode

• 01 03 00 00 00 01 04 3D CC CC CD 67 00 00 00 3C: The Payload containing the specific configuration parameters for the channel.

Individual Setting Example

A typical individual write command looks like this:

01 BD 07 00 00 02 58

• 01: Channel ID.

• BD: Command Code. To understand it, convert BD (hex) to binary: 1011 1101.

  • Bit 7 = 1 → Set (Write command)

  • Bits 3-6 = 0111 (decimal 7) → Modbus channel

  • Bit 2 = 1 → Enable the channel

  • Bits 0-1 = 01 → Individual parameter mode

• 07 00 00 02 58: Payload. Contains the specific parameter being modified and its corresponding value.

  • 07 → Parameter ID (Interval)

  • 00 00 02 58 → Interval value = 600 seconds

Command Payload Specification

RS485 (Modbus) Configuration

You can use LoRaWAN downlinks to remotely add a Modbus poll task or modify the parameters of an existing task.

Write Command Example: 01 BC 01 03 00 00 00 01 04 3D CC CC CD 67 00 00 00 3C

Command Structure Breakdown

• 01: Channel ID

• BC: Command Code (Indicates a Set/Write command for configuring an enabled Modbus channel in Combined Parameter Mode)

• Payload:

  • 01: Device Address = 1

  • 03: Function Code = 3 (Read Holding Register)

  • 00 00: Register Address = 0

  • 00 01: Quantity = 1

  • 04: Data Type = INT16_BE - Integer (16bit) - Big-Endian

  • 3D CC CC CD: Scale Factor = 0.1

  • 67: Sensor Type = 0x67 (103, Temperature)

  • 00 00 00 3C: Interval = 60 seconds (0x3C)

You can enter the read command 01 38 in the LoRaWAN Downlink server to retrieve the current parameter configuration payload.

Digital Input (DI) Configuration

You can use LoRaWAN downlinks to remotely modify DI parameters and change the channel state.

Write Command Example: CA 84 00 00 01 F4 00 00 02 58

Command Structure Breakdown

• CA: Channel ID

• 84: Command Code (Indicates a Set/Write command for configuring a Digital Input channel)

• Payload:

  • 00 00 01 F4: Debounce Time = 500 ms

  • 00 00 02 58: Report Interval = 600 seconds

You can enter the read command CA 00 in the LoRaWAN Downlink server to retrieve the current parameter configuration payload.

Digital Output (DO) Configuration

You can use LoRaWAN downlinks to remotely configure Digital Output (DO) channels, modify their parameters, and change the output state.

Write Command Example: D1 8C 00 00 02 58

Command Structure Breakdown

• D1: Channel ID

• 8C: Command Code (Write configuration for DO channel)

• Payload:

  • 00 00 02 58: Report Interval = 600 seconds

You can enter the read command D1 08 in the LoRaWAN Downlink server to retrieve the current parameter configuration payload.

NOTE

• To change the Interval value, the command must be sent with FPort set to 10.

• To change the output state (turn ON/OFF), the command must be sent with FPort set to 1 using one of the following specific commands:

  • D1 01 00 – Turn OFF the output

  • D1 01 01 – Turn ON the output

LoRaWAN Downlink Server Configuration

Before configuring LoRaWAN downlinks, ensure that your RAK2461 is connected to a LoRa Network Server and is actively communicating on the network.

Built-in Network Server

1. Log in to your gateway's web management interface.

2. Go to LoRa > Applications > End devices > Downlink.

3. On the Downlink page, configure the following and click Send to transmit the command.

   • Frame Confirmation: Enable.

   • FPort: Set to 10.

   • HEX Bytes: Enter the hexadecimal configuration command without any spaces (see examples below).

RS485 (Modbus) Configuration

Remotely change the data type of the Modbus Poll Task for Channel ID 1 to UINT16_BE - Unsigned Integer (16bit) - Big-Endian.

1. In the HEX Bytes field, enter the command 01BC010300000001063DCCCCCD670000003C.

Figure 1: LoRaWAN Downlink built in

2. Verify that the data type for RS485 Channel ID 1 has been updated to UINT16_BE.

Figure 1: Modbus Poll Task

Digital Input (DI) Configuration

Remotely set Debounce to 500 ms and Interval (s) to 600 seconds for Channel ID 202.

1. In the HEX Bytes field, enter the command CA84000001F400000258.

Figure 1: LoRaWAN Downlink built in

2. Confirm that the parameters for DI Channel ID 202 show Debounce to 500 ms and Interval to 600 seconds.

Figure 1: DI status

Digital Output (DO) Configuration

Remotely set the Interval to 600 seconds for Channel ID 209.

1. In the HEX Bytes field, enter the command D18C00000258.

Figure 1: LoRaWAN Downlink built in

2. Verify that the Interval for DO Channel ID 209 is now set to 600.

Figure 1: DO status

The Things Network (TTN)

1. Log in to the TTN Console.

2. Select your Application and the target End Device.

3. Navigate to the Messaging > Schedule downlink tab, configure the parameters, and click Schedule downlink to send the command.

   • Insert Mode: Replace downlink queue

   • FPort: 10

   • Payload type: Bytes

   • Payload: Enter the hexadecimal configuration command (see examples below).

   • Confirmed downlink: ✔ Check this box.

RS485 (Modbus) Configuration

Remotely change the data type of the Modbus Poll Task for Channel ID 1 to UINT16_BE - Unsigned Integer (16bit) - Big-Endian.

1. In the Payload field, enter the hexadecimal command 01BC010300000001063DCCCCCD670000003C and click Schedule downlink.

Figure 1: LoRaWAN Downlink TTN

2. Verify the change in your device's RS485 configuration for Channel ID 1.

Figure 1: Modbus Poll Task

3. Check the Live data tab in the TTN server to view the acknowledgment message returned by the device.

Figure 1: TTN confirmed

Digital Input (DI) Configuration

Remotely configure the Debounce to 500 ms and the Interval to 600 seconds for Digital Input Channel ID 202.

1. In the Payload field, enter the hexadecimal command CA84000001F400000258 and then click Schedule downlink.

Figure 1: LoRaWAN Downlink TTN

2. Verify in your device's DI configuration that the Debounce and Interval for Channel ID 202 are set to 500 and 600, respectively.

Figure 1: DI status

3. Check the Live data tab in the TTN server to view the acknowledgment message returned by the device.

Figure 1: TTN confirmed

Digital Output (DO) Configuration

Remotely set the Interval to 600 seconds for Digital Output Channel ID 209.

1. In the Payload field, enter the hexadecimal command D18C00000258 and click Schedule downlink.

Figure 1: LoRaWAN Downlink TTN

2. Verify in your device's DO configuration that the Interval for Channel ID 209 is now set to 600.

Figure 1: DO status

3. Check the Live data tab in the TTN server to view the acknowledgment message returned by the device.

Figure 1: TTN confirmed

ChirpStack

1. Log in to the ChirpStack Network Server.

   <IP address of ChirpStack>:9480

2. In the left navigation pane, go to Applications, select your target application, and then choose the specific end device.

3. Navigate to the device's Queue tab, configure the downlink parameters, and click Enqueue to send the command.

   • Confirmed: Enable.
   • FPort: Set to 10.
   • HEX: Enter the hexadecimal configuration command (see examples below).

RS485 (Modbus) Configuration

Remotely change the data type of the Modbus Poll Task for Channel ID 1 to UINT16_BE - Unsigned Integer (16bit) - Big-Endian.

1. In the HEX input field, enter the command 01BC010300000001063DCCCCCD670000003C and click Enqueue.

Figure 1: LoRaWAN Downlink ChirpStack

2. Verify in your device's RS485 configuration that the data type for Channel ID 1 has been updated to UINT16_BE.

Figure 1: Modbus Poll Task

3. Check the Events tab in the ChirpStack server to view the acknowledgment message returned by the device.

Figure 1: ChirpStack confirmed

Digital Input (DI) Configuration

Remotely set Debounce to 500 ms and Interval to 600 seconds for Digital Input Channel ID 202.

1. In the HEX input field, enter the command CA84000001F400000258 and click Enqueue.

Figure 1: LoRaWAN Downlink ChirpStack

2. Verify in your device's DI configuration that for Channel ID 202, Debounce is set to 500 and Interval is set to 600.

Figure 1: DI status

3. Check the Events tab in the ChirpStack server to view the acknowledgment message returned by the device.

Figure 1: ChirpStack confirmed

Digital Output (DO) Configuration

 Remotely set the Interval to 600 seconds for Digital Output Channel ID 209.

1. In the HEX input field, enter the command D18C00000258 and click Enqueue.

Figure 1: LoRaWAN Downlink ChirpStack

2. Verify in your device's DO configuration that the Interval for Channel ID 209 is set to 600.

Figure 1: DO status

3. Check the Events tab in the ChirpStack server to view the acknowledgment message returned by the device.

Figure 1: ChirpStack confirmed

System

From the main menu of IO.Box, go to the System tab to find device information for the RAK2461 as well as power output toggles and firmware update options.

Device Version Information

Figure 1: Device version information

• Hardware Version: Displays the specific version of the device’s hardware.
• Firmware Version: Displays the device's firmware version.
• Device EUI: Displays the unique identifier assigned by the manufacturer.
• Device Model: Displays the specific model name or number of the device.
• Serial Number: Displays the device’s serial number of the device.
• Device Type: Indicates the category or classification of the device, defining its interface types and functionalities. For detailed specifications refer to the device’s model information.
• Frequency Band: The device’s frequency band.

Power Output

Figure 1: Power output

• DC Vout Output: Toggle to enable or disable the Vout power output. When enabled, Vout passes through the same voltage as the Vin input.
• DC 12V Output: Toggle to enable or disable the 12V_Out power output. When enabled, it provides a 12 V / 0.5 A power output.
• DC 5V Output: Toggle to enable or disable the 5V_Out power output. When enabled, it provides a 5 V / 0.5 A power output.

System Reset & Firmware Upgrade

Figure 1: System reset & firmware upgrade

Reboot

1. Simply press the Reboot button.

Figure 1: Reboot button

2. After clicking OK, the device will reboot and disconnect from the IO.Box application.

Factory Reset

1. To restore the device to factory settings, press the Reset to Factory button.

Figure 1: Reset Button

2. After clicking OK, the device will be restored to factory settings.

Firmware Update

1. Download the latest firmware of the RAK2461.
2. Click Firmware Upgrade and select the firmware file.
3. Confirm the firmware information and then click Upgrade. Wait for the procedure to finish.

Figure 1: Confirm the firmware information

Figure 1: Upgrading procedure

Figure 1: Successful upgrade