Changes for page End Device AT Commands and Downlink Command
Last modified by kai on 2024/09/06 10:00
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.ting - Content
-
... ... @@ -21,7 +21,7 @@ 21 21 = 2. How to use AT Commands or Downlink command = 22 22 23 23 24 -* **AT Command** : See Devices User Manual for how to connect to device via USB TTL adapter and use. The user manual can be found in each product page of [[Dragino OfficialWebsite>>url:http://www.dragino.com/]]24 +* **AT Command** : See Devices User Manual for how to connect to device via USB TTL adapter and use. The user manual can be found in each product page of **[[Dragino Products User Manual>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/]]**. 25 25 26 26 * **LoRaWAN Downlink Command**: The gateway transfer downlink command in HEX format. This page shows the Downlink Command In HEX format. Please note some LoRaWAN servers use base64 as downlink code so user need to convert HEX to Base64 and use. Below are references for how to use downlink command: 27 27 ** Use HEX format to send a downlink: [[TTN v3>>Notes for TTN]] ... ... @@ -225,11 +225,11 @@ 225 225 (% style="color:blue" %)**Downlink Command: 0x26 (Valid in 006 stack)** 226 226 227 227 ((( 228 - DownlinkFormat: 0x26228 +Format: Command Code (0x26) followed by 1 byte. 229 229 ))) 230 230 231 231 ((( 232 -Device will reply with firmware version info, device info. frequency band info. detail please check device user manual. Total 5 bytes Example: If device is of firmware version 1.1.0 Upload: xx ~-~- yy ~-~- zz ~-~- 110 total 5 bytes 232 +If the downlink payload=**2601, **Device will reply with firmware version info, device info. frequency band info. detail please check device user manual. Total 5 bytes Example: If device is of firmware version 1.1.0 Upload: xx ~-~- yy ~-~- zz ~-~- 110 total 5 bytes( FPort= 5 usually). 233 233 ))) 234 234 235 235 ((( ... ... @@ -438,7 +438,7 @@ 438 438 439 439 (% style="color:blue" %)**Downlink Command: 0x05** 440 440 441 -Format: Command Code (0x05) followed by 2bytesmode value.441 +Format: Command Code (0x05) followed by 1 byte mode value. 442 442 443 443 If the downlink payload=0501, it means set end node to use confirm mode, while type code is 05. 444 444 ... ... @@ -485,7 +485,7 @@ 485 485 486 486 (% style="color:blue" %)**Downlink Command: 0x05** 487 487 488 -Format: Command Code (0x05) followed by 2bytes mode value.488 +Format: Command Code (0x05) followed by 3 bytes mode value. 489 489 490 490 If the downlink payload=05010101, it means set end node to use confirm mode, while type code is 05. 491 491 ... ... @@ -604,7 +604,7 @@ 604 604 605 605 (% style="display:none" %) (%%) 606 606 607 -== 6.8 Send Text Data == 607 +== 6.8 Send Text Data(Note: The format of this command of LA66 is subject to the manual) == 608 608 609 609 610 610 Feature: Send Text Data<port:data>. ... ... @@ -621,7 +621,7 @@ 621 621 622 622 (% style="display:none" %) (%%) 623 623 624 -== 6.9 Send Hexadecimal Data == 624 +== 6.9 Send Hexadecimal Data(Note: The format of this command of LA66 is subject to the manual) == 625 625 626 626 627 627 Feature: Send hexadecimal data along with the application port. ... ... @@ -926,7 +926,7 @@ 926 926 == 7.14 Transmit Power == 927 927 928 928 929 -Feature: Get or Set the Transmit Power(0-5, MAX:0, MIN:5, according to LoRaWAN Spec, or 40=10dB, 41 = 11dB, …, 50 = 20dB which is out of LoRaWAN spec. ) 929 +Feature: Get or Set the Transmit Power(0-5, MAX:0, MIN:5, according to LoRaWAN Spec, or 40=10dBm, 41 = 11dBm, …, 50 = 20dBm which is out of LoRaWAN spec. ) 930 930 931 931 (% style="color:red" %)**Notice: Transmit Power might be changed by ADR from LoRaWAN server. So manually change TXP also remember to set AT+ADR=0 in sensor** 932 932 ... ... @@ -1216,6 +1216,7 @@ 1216 1216 AT+DDETECT=<Flag>,<ACK_Timout_1>,<ACK_Timout_2> (Default Value: AT+DDETECT=1,1440,2880) 1217 1217 1218 1218 * ACK_Timout_1: Unit: min 1219 + 1219 1219 * ACK_Timout_2: Unit: min 1220 1220 1221 1221 (% border="1" style="background-color:#f2f2f2; width:562px" %) ... ... @@ -1257,30 +1257,40 @@ 1257 1257 * **Example 1:** Downlink Payload: 320105A00B40 ~/~/ Set AT+DDETECT=1,1440,2880 1258 1258 1259 1259 * 1260 -** 0x01 : Flag 1261 -** 0x05A0: ACK_Timout_1 : 1440minutes (24 hours) 1262 -** 0x0B40: ACK_Timout_2 : 2880minutes (48 hours) 1263 -** **Explain**: Enable Online Detect, if end node doesn't receive any downlink within ACK_Timout_1( 1440 minutes or 24 hours). End node will use confirmed uplink to send packets during ACK_Timout_1 (the 24th hour) to ACK_Timout_2 ( the 48th hour). If from the 24th to 48th hour, end node got an downlink from server, it will switch back to unconfirmed uplink. end node will restart ACK_Timout_1. If from the 24th to 48th hour, end node still not got any downlink, means device doesn't get ACK from server within last 48 hours. Device will process rejoin, rejoin request interval is AT+RJTDC period. For AU915/ US915, device will use the sub-band used for last join. 1261 +** 0x01** : Flag** 1264 1264 1263 + **0x05A0 **: ACK_Timout_1 : 1440minutes (24 hours) 1264 + 1265 + **0x0B40 **: ACK_Timout_2 : 2880minutes (48 hours) 1266 + 1267 +* **Explain**: Enable Online Detect, if end node doesn't receive any downlink within ACK_Timout_1( 1440 minutes or 24 hours). End node will use confirmed uplink to send packets during ACK_Timout_1 (the 24th hour) to ACK_Timout_2 ( the 48th hour). If from the 24th to 48th hour, end node got an downlink from server, it will switch back to unconfirmed uplink. end node will restart ACK_Timout_1. If from the 24th to 48th hour, end node still not got any downlink, means device doesn't get ACK from server within last 48 hours. Device will process rejoin, rejoin request interval is AT+RJTDC period. For AU915/ US915, device will use the sub-band used for last join. 1268 + 1265 1265 (% style="display:none" %) (%%) 1266 1266 1267 1267 == 7.26 Request the server to send an ACK == 1268 1268 1269 1269 1274 +Feature: Mode for sending data for which acknowledgment was not received. LoraWAN Network Server(eg. The Things NetWork/ChirpStack/AWS/...). 1275 + 1270 1270 (% style="color:blue" %)**AT Command: AT+PNACKMD** 1271 1271 1272 1272 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:889px" %) 1273 1273 |(% style="background-color:#4f81bd; color:white; width:160px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:627px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Response** 1274 -|(% style="width:160px" %)AT+PNACKMD=1|(% style="width:627px" %)If the node uploads the ACK as confirm, it will request the server to send an ACK. If theserver ack is not received, the node will upload the packets that have not received the ACK the next time it receives the ACK|(% style="width:100px" %)1(((1280 +|(% style="width:160px" %)AT+PNACKMD=1|(% style="width:627px" %)If the node uploads the ACK as confirm, it will request the LoraWAN Network Server to send an ACK. If the LoraWAN Network Server ack is not received, the node will upload the packets that have not received the ACK the next time it receives the ACK|(% style="width:100px" %)1((( 1275 1275 OK 1276 1276 ))) 1277 -|(% style="width:160px" %)AT+PNACKMD=0|(% style="width:627px" %)off request the server to send an ACK|(% style="width:100px" %)(((1283 +|(% style="width:160px" %)AT+PNACKMD=0|(% style="width:627px" %)off request the LoraWAN Network Server to send an ACK|(% style="width:100px" %)((( 1278 1278 0 1279 1279 OK 1280 1280 ))) 1281 1281 1282 -(% style="display:none" %) (%%) 1288 +(% style="display:none" %) (%%) (% style="color:blue" %)**Downlink Command: 0x34** 1283 1283 1290 +0X34 01 ~/~/Same As AT+PNACKMD=1 1291 + 1292 +0x34 00 ~/~/Same As AT+PNACKMD=0 1293 + 1294 + 1284 1284 == 7.27 Adjust network rejoining interval == 1285 1285 1286 1286