The RAKwireless Unified Interface V3 (RUI3) is designed to help IoT developers make their IoT products faster. It is compatible with RAK LPWAN modules and supports the standard AT Commands and the Binary Mode. The Binary mode is an improved version of the AT command with its efficient byte-array-based protocol and implementation of checksum. RUI3 also allows you to create your own custom firmware using RUI3 APIs that are compatible with popular IDEs like Arduino and Visual Studio. With custom firmware, you will not need any external host microcontroller or microprocessor, which can save you cost, circuit board space, and current consumption.
RUI3 v4.2.3 Release Note
Supported Hardware:
- STM32: RAK3172, RAK3172-SiP, RAK3172LP-SiP, RAK3172-T, RAK11160
- nrf52: RAK4631, RAK3401
- Apollo3: RAK11720
LoRaWAN and LoRa P2P API calls have been separated in two different classes since RUI3 v4.1.1..
| Old | New | Comment |
|---|---|---|
api.lorawan.pXXX | api.lora.XXX | All LoRa P2P API calls change. |
api.lorawan.registerPyyy | api.lora.registerPyyy | All LoRa P2P callback register API calls change. |
api.lorawan.nwm.set(1) | api.lorawan.nwm.set() | Set device to LoRaWAN mode. |
api.lorawan.nwm.set(0) | api.lora.nwm.set() | Set device to LoRa P2P mode. |
Fixed
| Daily Build No. / Bug No. | Description |
|---|---|
| RUI-1118 | [RUI3 v4.2.0] [RUI3 V4.1.1] [RAK3172] [RAK3172-SiP] CHANGE_ATCMD_PERM does not work. |
| RUI-1148 | [RUI3 v4.2.2] First uplink fCnt is 1, LoRaWAN spec says first fCnt should be 0. |
| RUI-1149 | [RUI3 v4.2.2 & v4.2.3] Confirmed packets with RUI3 API are not working as expected. |
| RUI-1150 | [RUI3 v4.2.2] RAK3172 modules become permanently stuck in AT_BUSY_ERROR. |
| RUI-1157 | [RUI3 v4.2.3 RAK4630] If LoRaWAN is disabled, the compilation of any code throws error about undefined variable. |
