Changes for page Notes for Actility
Last modified by Bei Jinggeng on 2023/05/10 10:18
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Actility ThingPark Enterprise1 +Notes for Actility - Content
-
... ... @@ -28,7 +28,7 @@ 28 28 29 29 == 2.2 Step 1. Add Gateway == 30 30 31 -[[image: https://wiki.dragino.com/images/thumb/e/e5/Add_gateway_1.png/600px-Add_gateway_1.png||height="300" width="600"]]31 +[[image:image-20220524163104-1.png]] 32 32 33 33 Add Gateway_1 34 34 ... ... @@ -36,10 +36,10 @@ 36 36 37 37 (% class="box" %) 38 38 ((( 39 - 1.Model ~-~->Choose the Model 40 - 2.Name ~-~->Custom 41 - 3.LRR-UUID 42 - 4.RF Region 39 + 1.Model **~-~->** Choose the Model 40 + 2.Name **~-~->** Custom 41 + 3.LRR-UUID **~-~->** Enter 0061C0-Gateway EUI ,Such as:0016C0-A840411E96744150 42 + 4.RF Region **~-~->** Choose the frequency 43 43 ))) 44 44 45 45 [[image:https://wiki.dragino.com/images/thumb/4/4b/Add_gateway_2.png/600px-Add_gateway_2.png||height="432" width="600"]] ... ... @@ -106,10 +106,14 @@ 106 106 107 107 Recore Log 108 108 109 - 110 - 109 +((( 111 111 The reason of fail to join Actility is that our end node use RX2DR=3 for join. this is the default setting for TTN and many LoRaWAN servers. 111 +))) 112 112 113 +((( 113 113 The Actility use RX2DR=0 for Join, when Actility sends a Join Accept, due to RX2DR different, the end node can not receive the Join Accept message from Actility so keep joining. 115 +))) 114 114 117 +((( 115 115 Some of End Nodes already support the change on RX2DR for OTAA join, in this case, use need to write AT+RX2DR=0. Please contact Dragino support for more info if the product doesn't support it. 119 +)))
- image-20220524163104-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +33.2 KB - Content