AT+TIMEREQ not working for AWS \ LoRiot

adityakoparkar · January 19, 2023, 8:23pm

Hi,
I work for an agrotech company called Farmx. We are currently using RAK3172 module in one of our products.
Firmware version of RA3172 is 1.0.4
We wish to maintain time on the end device and so for that it is critical that we have the AT+TIMEREQ working.
I referred to the online document written by Carl and implemented this feature on our end.
But what we have noticed is that sometimes this feature simply doesn’t work.

I send the AT+TIMEREQ command to the RAK module and follow that by an uplink message. But for the uplink message I see +EVT:SEND CONFIRMED OK but I never see the +EVT: TIMEREQ OK message.

If I send the AT+LTIME=? command after this I receive : 00h10m39s on 01/01/1970

Can anyone please help me understand what might be going wrong. I have seen this feature work flawlessly with LoRiot before.
I am attaching the logs from my end node for reference.

TRAK001: Sending LoRa (async) Cmd: AT+TIMEREQ=1
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
TRAK001: Sending LoRa (async) Cmd: AT+USEND=11:1:2:0104040102010000
LORA004: Sent WB message
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
FRAK001: Rec’ed from RAK(cnt=24): +EVT:SEND CONFIRMED OK
TRAK001: Sending LoRa (async) Cmd: AT+LTIME=?
FRAK001: Rec’ed from RAK(cnt=31): LTIME:00h10m16s on 01/01/1970

carlrowan · January 20, 2023, 4:47am

Hi @adityakoparkar ,

Will it be possible to get some logs from the network server if it really indeed sent UTC via downlink?

As for the RAK3172, the legacy firmware 1.0.4 is now halted on development. All firmware support will be now on RUI3 so another think you can try is to update your firmware to RUI3 and see if your deployment will improve.

adityakoparkar · January 20, 2023, 10:22pm

Hi Carl,
Today I modified the setup to use the RAK7249 GW.
My end node uses RAK3172 and the LNS is provided by AWS.

I am able to see the logs in the LoRaWAN packet logger. I am attaching the image of the logs.
You can see in the RAK GW logs that there are uplink and downlinks. But I don’t see any MAC messages indicating that the timereq message was sent.

In the serial logs you can see that the AT+TIMEREQ command was sent and the mcu received ‘OK’ from the RAK module.

Following are the logs capture on the serial terminal from my end node. You can clearly see the AT commands and the sequence in which they are being sent.

Logs from end node :

RAK001: Sending LoRa (async) Cmd: AT+JOIN=1:0:8:0
LORA005: Sent Join Cmd
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
FRAK001: Rec’ed from RAK(cnt=13): +EVT:JOINED
LORA001: Joining response: joined(0)
LORA002: Join succeeded
LORA006: Sent Get Network Status Cmd
TRAK001: Sending LoRa (async) Cmd: AT+NJS=?
FRAK001: Rec’ed from RAK(cnt=3): 1
TRAK001: Sending LoRa (async) Cmd: AT+TIMEREQ=1
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
TRAK001: Sending LoRa (async) Cmd: AT+USEND=11:1:2:0104040102010000
LORA004: Sent WB message
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
FRAK001: Rec’ed from RAK(cnt=24): +EVT:SEND CONFIRMED OK
TRAK001: Sending LoRa (async) Cmd: AT+LINKCHECK=1
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
TRAK001: Sending LoRa (async) Cmd: AT+TIMEREQ=1
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
TRAK001: Sending LoRa (async) Cmd: AT+USEND=11:1:2:0104040102010000
LORA004: Sent WB message
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
FRAK001: Rec’ed from RAK(cnt=24): +EVT:SEND CONFIRMED OK
FRAK001: Rec’ed from RAK(cnt=28): +EVT:RX_1, RSSI -36, SNR 7
FRAK001: Rec’ed from RAK(cnt=14): +EVT:UNICAST
FRAK001: Rec’ed from RAK(cnt=36): +EVT:21:dfd4f550000200000084030000
LORA015: Rec’ed delayed valve control: Aact=d4, Ato=80, Awn=2, Bact=f5, Bto=0, Bwn=0, VWL=0, VWH=0
TRAK001: Sending LoRa (async) Cmd: AT+LINKCHECK=1
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
TRAK001: Sending LoRa (async) Cmd: AT+LTIME=?
FRAK001: Rec’ed from RAK(cnt=31): LTIME:00h00m19s on 01/01/1970
SYS021: Entering the Low Power Sys on. lowPowerModeFlag: 1, peripheralInitFlag: 1, nfcCmdRecFlag: 0
FRAK001: Rec’ed from RAK(cnt=2):
FRAK001: Rec’ed from RAK(cnt=4): OK
SYS022: Uptime: 0, epoch : 1358288095

carlrowan · January 23, 2023, 1:52am

Hi @adityakoparkar ,

Can you please confirm if the LoRaWAN specification version used by your AWS LNS is 1.0.3 and above? Lower than that LoRaWAN version will not support TIMEREQ command.