Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesRUI3 is RAKwireless’s firmware-development and device-management ecosystem for supported RAK IoT products—not a universal IoT programming standard. It lets developers build custom firmware using Arduino-compatible APIs and familiar development environments, while AT commands and WisToolBox provide related ways to configure or control devices.
What is RUI3?
RAKwireless describes RUI3 as “a unified programming interface developed by RAKwireless, primarily designed for IoT scenarios.” In practice, it is a vendor-specific interface and open-source SDK for customizing compatible RAK products. The vendor overview describes Arduino-compatible APIs and support for development in Arduino IDE, Visual Studio Code, and Visual Studio. See RAKwireless’s RUI3 overview.
RUI3 documentation covers Arduino functions, system functions, LoRaWAN, BLE, NFC, and One Wire Serial. RAKwireless also describes connectivity options that include LoRaWAN, LoRa point-to-point (P2P), BLE, and LTE/NB-IoT. These are capabilities across the ecosystem, not a promise that every API or radio is available on every board. Check the feature list for the exact target.
How RUI3 differs from AT commands and WisToolBox
These are related parts of the RAKwireless ecosystem, but they do different jobs. With RUI3 APIs, you write custom firmware that runs on a supported device. With AT commands, a host or user sends commands through the device’s command interface to control or configure it. WisToolBox is a vendor tool for device management, configuration, commands, and firmware distribution. RAKwireless explains WisToolBox here.
#1 Best Overall
- ESP32-WROVER-IE module
- ESP32-D0WD-V3 chip
- 8 MB flash + 8 MB PSRAMM
- IPEX antenna
For example, RUI3 API calls can set LoRaWAN credentials for OTAA or ABP join modes. The credentials and regional radio parameters still need to match the network and the device’s supported band. If you are using an AT-command workflow rather than writing device firmware, follow the command documentation for your device and firmware version.
How to get started with RUI3
- Select a supported target. Choose the exact module or board and confirm its RUI3 compatibility, radio band, firmware compatibility, memory, and required peripherals. The vendor’s Arduino board-support listing names products including RAK3172, RAK3172 EVB, and RAK3172-SiP.
- Install the development environment and board support. Follow RAKwireless’s current setup instructions for your target and chosen IDE. The vendor overview names Arduino IDE, Visual Studio Code, and Visual Studio; installation details can vary by release. Confirm you are installing the RUI3 package appropriate to the hardware rather than assuming every RAK board uses the same package.
- Use the matching API guide and example. Start with an example for your board and RUI3 version, then adapt it. The RUI3 API getting-started guide covers custom firmware and LoRaWAN credential configuration.
- Build a small application and verify target-specific features. Test the APIs and peripherals available on your selected device. Configure network credentials and regional LoRaWAN settings where relevant; do not copy settings from a different radio region or module without checking compatibility.
- Choose the right field workflow. For host-driven control, use the matching AT-command documentation. For configuration or firmware distribution, check whether WisToolBox currently supports your specific device and intended workflow.
Choosing hardware for an RUI3 project
There is no universally best RUI3 board: the right choice depends on how much integration you need and what the application must do. A bare module such as the RAK3172 can be suitable for a product design, but a project may need a carrier board, power arrangement, antenna, and serial or debug access. An evaluation board is generally a more direct route for development. A WisBlock Core or kit can suit modular sensor experiments, provided the exact components and RUI3 support fit the project.
Rank #2
- V4F processor, up to 144MHz system dominant frequency
- Support single cycle multiplication and hardware division, support hardware floating point operation (FPU) 64KB SRAM, 256KB Flash
- Power supply voltage: 2.5/3.3 V, GPIO unit independent power supply
- Multiple low power consumption modes: sleep, stop, standby
- Power on/off reset, programmable voltage detector
| Hardware route | Useful when | Check before choosing |
|---|---|---|
| Bare module | You are integrating a module into a custom design. | Carrier board, power, antenna, serial/debug access, supported radio band, and available memory and peripherals. |
| Evaluation board | You want a development-oriented way to work with a supported module. | Exact RUI3 compatibility, included accessories, radio region, and retailer listing details. |
| WisBlock Core or kit | You want to assemble a modular sensor experiment. | Core and module compatibility, required sensors, target-specific examples, and firmware support. |
Before ordering, verify the precise SKU and included accessories against the vendor’s current product information. Retail listings and bundled components can vary.
Check RUI3 versions before copying examples or commands
RUI3 documentation and examples can be version- and target-specific. RAKwireless’s best-practice repository says its examples require RUI3 V4.2.1, warns that older releases lack some functionality, and notes that some RAK3172 examples need code-size reductions because of limited flash and RAM. Those caveats apply to the examples and hardware discussed there; they should not be generalized to every RUI3 product.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- Onboard EPM240T100C5 chip；Onboard JTAG interface；Onboard 50 MHZ active crystal
- With one programmable LED
- With 5V to 3.3 V chip AMS1117-3.3
- 5V power supply with switch
- All IO are led out；Board size：5CM * 7CM
The RAK3172 migration guide documents differences between older non-RUI firmware and RUI3. In that migration context, it reports 115200 baud as the RUI3 default. Confirm the firmware version and relevant guide before reusing older commands or code. V4.2.1 is the version required by the repository’s examples, not evidence of the latest RUI3 release.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Can I use Arduino IDE with RUI3?
Yes. RAKwireless documents Arduino-compatible APIs and an Arduino board-support package for supported hardware. Install the package and follow the setup instructions for your exact target and RUI3 version.
How do I program a RAK3172 with RUI3?
Use the RUI3 board support and API example that match your RAK3172 hardware and firmware version. Check memory limits and the target’s radio and peripheral capabilities before adapting code.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
