RAK19713 WisLink RAK4630 Troubleshooting & FAQs
Troubleshooting
Device Detection Failure
There are several things you can check if the device is not detected:
- Ensure the device is properly inserted into the slot. Insert it at an angle, then press it flat into the connector. Secure it with screws to keep it in place.
- Verify the system detects the device. If not detected, the issue may be with the slot (no USB interface) or the device.
> sudo dmesg -w
...
[140523.363323] usb 1-1.1: USB disconnect, device number 12
[140527.658064] usb 1-1.1: new full-speed USB device number 13 using xhci_hcd
[140527.782157] usb 1-1.1: New USB device found, idVendor=239a, idProduct=8029, bcdDevice= 1.00
[140527.782170] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[140527.782177] usb 1-1.1: Product: WisCore RAK4631 Board
[140527.782182] usb 1-1.1: Manufacturer: RAKwireless
[140527.782187] usb 1-1.1: SerialNumber: 5B6C816B55A14444
[140527.830054] cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device
...
Press [Ctrl+C] to exit the log stream.
Permission Error
If the udev rules are configured correctly, permissions should be set to 0x0666. This allows all users to access the device.
Check if the device appears in the USB subsystem. Look for RAK4631 and take note of its VID and PID values.
rak@rakpios:~ $ lsusb | grep RAK4631
Bus 001 Device 013: ID 239a:8029 Adafruit WisCore RAK4631 Board
If the VID and PID differ, update the udev rules accordingly.
No AT Command Response
The RAK19713 uses default firmware with an AT command interface. If the device is not new or the firmware was changed, reflash the original firmware to restore this feature. Refer to the RAK19713 Firmware & Flashing guide for detailed instructions.
Device Setup and Usage
How to find the device port?
With udev rules configured, the device appears as /dev/rak19713 in the filesystem.
This file is a symbolic link to the actual device node (for example, /dev/ttyACM0).
Why use udev rules?
udev rules map the device port to a stable identifier such as /dev/rak19713 and configure access permissions.
Without udev rules:
- The device may appear as
/dev/ttyACM0(which can change between reboots) - Access may require membership in the
dialoutgroup
How to send AT commands?
Once the device is ready and the port is known, use a serial terminal at 115200 baud.
Example: picocom -b 115200 /dev/rak19713
Refer to the RUI3 AT Command Manual
Product Capabilities
Is this a gateway module?
No, this is a LoRa node module. It can operate in LoRaWAN networks or mesh networks such as Meshtastic.
Does it support Linux?
Yes. It provides an AT command interface by default, compatible with Linux and other operating systems that support USB CDC-ACM.
Can it run Meshtastic?
Yes. It uses the same RAK4630 module as the WisMesh Pocket.
USB vs UART?
USB is recommended for reliability and ease of use across most hosts. UART is suitable for SBC integrations.
