in this forum Time request in join ABP mode I was successful in updating the date and time in ABP mode through the private network that I installed at the company where I work, without any modifications to the Arduino code. But the public network has not yet been successful.
To try to resolve the problem, I followed the suggestions presented in the topic and the problem continues. The reason for the failure to update the time is the uplinks that are failing, any suggestions to resolve the problem or any topic that addresses this issue?
Hi @douglas_nascimento ,
On the public network server, were you able to do all the suggested things on the original thread? Like were you able to disable frame counter checks?
Also, maybe you can test the connection first via AT commands before the Arduino code just to isolate that it is not related to the custom code.
sorry for the delay in responding. The following image is the device configuration.
the Arduino serial logs, first on the private network and then using the public network, I provided as much information as possible about the device parameters. The country I am in is Brazil and the public network sub-band is 1.
//private network
10:34:14.739 → ATZ
10:34:14.739 →
10:34:14.939 → RAKwireless RAK3172
10:34:14.972 → ------------------------------------------------------
10:34:14.972 → Version: RUI_4.0.6_RAK3172-E
10:34:14.972 → Current Work Mode: LoRaWAN.
10:34:18.904 → AT+NJM=0
10:34:18.904 →
OK
10:34:36.384 → AT+ADR=?
10:34:36.384 →
AT+ADR=0
10:34:36.384 → OK
10:34:51.534 → AT+CLASS=?
10:34:51.534 →
AT+CLASS=A
10:34:51.534 → OK
10:35:00.229 → AT+DR=?
10:35:00.229 →
AT+DR=2
10:35:00.229 → OK
10:35:19.739 → AT+NJM=0
10:35:19.739 →
OK
10:35:36.836 → AT+CFM=?
10:35:36.836 →
AT+CFM=1
10:35:36.836 → OK
10:35:48.791 → AT+NWKSKEY=?
10:35:48.791 →
AT+NWKSKEY=23 ************ E4C9D9B36AE2946A00
10:35:48.791 → OK
10:35:59.442 → AT+APPSKEY=?
10:35:59.442 →
AT+APPSKEY=92 ************ 3CF8D0F3AA92461B13
10:35:59.442 → OK
10:36:10.194 → AT+DEVADDR=?
10:36:10.228 →
AT+DEVADDR=01 **** 47
10:36:10.228 → OK
10:36:31.308 → AT+DEVEUI=?
10:36:31.308 →
AT+DEVEUI=AC ************ A0
10:36:31.308 → OK
10:36:46.893 → AT+MASK=?
10:36:46.893 →
AT+MASK=0001
10:36:46.893 → OK
10:37:00.009 → AT+PNM=?
10:37:00.009 →
AT+PNM=1
10:37:00.009 → OK
10:37:23.714 → AT+CFS=?
10:37:23.714 →
AT+CFS=0
10:37:23.714 → OK
10:37:42.136 → AT+JN1DL=?
10:37:42.136 →
AT+JN1DL=5
10:37:42.136 → OK
10:37:45.869 → AT+JN2DL=?
10:37:45.869 →
AT+JN2DL=6
10:37:45.869 → OK
10:37:55.198 → AT+RX1DL=?
10:37:55.198 →
AT+RX1DL=1
10:37:55.198 → OK
10:38:03.527 → AT+RX2DL=?
10:38:03.527 →
AT+RX2DL=2
10:38:03.527 → OK
10:39:21.730 → AT+RX2DR=?
10:39:21.730 →
AT+RX2DR=8
10:39:21.730 → OK
10:39:31.782 → AT+RX2FQ=?
10:39:31.782 →
AT+RX2FQ=923300000
10:39:31.782 → OK
10:39:39.139 → AT+TXP=?
10:39:39.139 →
AT+TXP=0
10:39:39.139 → OK
10:39:57.464 → AT+DCS=?
10:39:57.464 →
AT+DCS=1
10:39:57.464 → OK
10:40:24.271 → AT+BAND=?
10:40:24.271 →
AT+BAND=6
10:40:24.271 → OK
10:41:16.364 → AT+TIMEREQ=1
10:41:16.364 →
OK
10:42:15.306 → AT+SEND=1:1212
10:42:15.306 →
OK
10:42:16.706 → +EVT:SEND_CONFIRMED_OK
10:42:16.706 → +EVT:TIMEREQ_OK
10:42:27.406 → AT+SEND=1:1212
10:42:27.406 →
OK
10:42:28.806 → +EVT:SEND_CONFIRMED_OK
10:42:55.256 → AT+TIMEREQ=1
10:42:55.256 →
OK
10:42:59.490 → AT+SEND=1:1212
10:42:59.490 →
OK
10:43:00.923 → +EVT:SEND_CONFIRMED_OK
10:43:00.923 → +EVT:TIMEREQ_OK
10:45:22.991 → AT+SEND=1:1212
10:45:22.991 →
OK
10:45:24.389 → +EVT:SEND_CONFIRMED_OK
10:48:34.647 → AT+SEND=1:1212
10:48:34.647 →
OK
10:48:36.080 → +EVT:SEND_CONFIRMED_OK
//public network
10:50:57.064 → AT+NWKSKEY=ca ************ 4d2818c26da792248e
10:50:57.064 →
OK
10:51:13.713 → AT+APPSKEY=e9 ************ fd000bffa01c221337
10:51:13.713 →
OK
10:51:30.858 → AT+DEVADDR=8b **** 81
10:51:30.858 →
OK
10:51:34.723 → AT+TIMEREQ=1
10:51:34.723 →
OK
10:51:39.390 → AT+SEND=1:1212
10:51:39.390 →
OK
10:51:56.596 → +EVT:SEND_CONFIRMED_FAILED(4)
10:51:56.596 → +EVT:TIMEREQ_FAILED
10:52:04.956 → AT+SEND=1:11
10:52:04.956 →
OK
10:52:23.361 → +EVT:SEND_CONFIRMED_FAILED(4)
After connecting to the private network and then to the public network, the following message appears on the server (before, no warning log was reported by the server) :
{
“params”: {
“message”: “Uplink message with repeated counter received.”,
“code”: “counter_error”
},
“meta”: {
“network”: “358b679dd88d47948f6e108677b4b79a”,
“packet_hash”: “2c3792e98c0b71a99d6aaccd7d1dcaf6”,
“application”: “0000000000000000”,
“device_addr”: “8b ****81”,
“time”: 1698073654.226,
“device”: “ac ************a0”,
“packet_id”: “a461804c7ee4e53e5815cd714d5ededd”,
“gateway”: “b0fd0b70010f0000”
},
“type”: “warning”
}
Hi @douglas_nascimento ,
It appears that the public network you have supports LA915 Frequency Band.
It will be supported by the next version of RUI3 - v4.1.0.
I will send you a message to have early access and see if it will connect.
Ok, I’ll be waiting.