When Gateway is operating in properly by connecting to WiFi Network (Client + AP mode) and LED status are not showing as per the documentation.
Fireware Version: 1.1.2_RAK rRAK-b5615257b
Here is status of LEDs which are misleading.
Breathing LED - RED colour
PWR LED - Working as expected
LoRa LED - Not lidding at all. But, I could see my LoRa device is joined and able to send the data to TTN
WLAN LED - LED is always off - But connected to Wireless Network as client and able to connect to TTN
LTE LED - Continue to flashing - But, Multi WAN should use WiFi not the LTE as I have not connected Ethernet.
Also I am seeing this error in system logs
Tue Oct 12 09:21:28 2021 user.warn basicstation[5531]: [LOG:WARN] LoRa modulation error: 0
Tue Oct 12 09:21:28 2021 user.notice basicstation[5531]: [LOG:NOTI] Invalid DataRate value : 8
Tue Oct 12 09:21:28 2021 user.notice basicstation[5531]: [LOG:NOTI] Invalid DataRate value : 9
Tue Oct 12 09:21:28 2021 user.notice basicstation[5531]: [LOG:NOTI] Invalid DataRate value : 10
Tue Oct 12 09:21:28 2021 user.notice basicstation[5531]: [LOG:NOTI] Invalid DataRate value : 11
Tue Oct 12 09:21:28 2021 user.notice basicstation[5531]: [LOG:NOTI] Invalid DataRate value : 12
Tue Oct 12 09:21:28 2021 user.notice basicstation[5531]: [LOG:NOTI] Invalid DataRate value : 13
Tue Oct 12 09:21:28 2021 user.notice basicstation[5531]: [LOG:NOTI] Invalid DataRate value : 14
Tue Oct 12 09:21:28 2021 user.notice basicstation[5531]: [LOG:NOTI] Invalid DataRate value : 15
Could you please advise as bit confusing or anything wrong in the product.
Hello, I am having a similar problem with RAK7268C firmwawre 1.2.3_RAK rRAK-a6e14b0
GW is connected over LTE to AWS IoT core using basics station. LED is breathing red indicating there is a problem, however the LoRa node is joined and sending unconfirmed uplinks to AWS and received in AWS console. RAK system log shows the following errors:
Wed Jan 19 14:38:17 2022 user.warn basicstation[10682]: [S2E:WARN] Unknown field in dnmsg - ignored: regionid
Wed Jan 19 14:38:21 2022 user.err basicstation[10682]: [S2E:ERRO] ::0 diid=39348 [ant#0] - radio is not emitting frame - abandoning TX, trying alternative
Wed Jan 19 14:38:21 2022 user.warn basicstation[10682]: [S2E:WARN] ::0 diid=39348 [ant#0] - unable to place frame
Wed Jan 19 14:38:55 2022 user.warn basicstation[10682]: [S2E:WARN] Unknown field in dnmsg - ignored: regionid
Wed Jan 19 14:39:29 2022 user.warn basicstation[10682]: [S2E:WARN] Unknown field in dnmsg - ignored: regionid
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
Wed Jan 19 14:41:10 2022 user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0
I always see many LoRa modulation errors…
Do I need to adjust the settings in AWS so I don’t get these errors?
Hi @Nikola - I upgraded to the latest available firmware for my RAK7268C (using LTE, running “1.3.1_RAK b71”), and I’m experiencing similar issues to those mentioned above. Specifically:
LED is breathing red when connected to AWS IoT (confirmed on the AWS console)
multiple consecutive “user.warn basicstation[10682]: [LOG:WARN] LoRa modulation error: 0” messages in the gateway log
uplink messages missing from AWS despite being confirmed on the gateway log