Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From version 113.7
edited by Xiaoling
on 2022/11/09 17:02
on 2022/11/09 17:02
Change comment:
There is no comment for this version
To version 143.1
edited by Bei Jinggeng
on 2022/11/22 10:04
on 2022/11/22 10:04
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 13 added, 0 removed)
- image-20221116111844-1.png
- image-20221116111844-2.png
- image-20221116111844-3.png
- image-20221116111844-4.png
- image-20221116111844-5.png
- image-20221118104359-1.png
- image-20221118105220-2.png
- image-20221118105249-3.png
- image-20221118105402-4.png
- image-20221122100004-1.png
- image-20221122100004-2.png
- image-20221122100004-3.png
- image-20221122100004-4.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Bei - Content
-
... ... @@ -176,9 +176,13 @@ 176 176 177 177 178 178 179 -(% style="color:blue" %)**Step 2**:(%%) ower on TrackerD byusingtheonboardswitch.179 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 180 180 181 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]] 181 181 183 +[[image:1664502835802-546.png]] 184 + 185 + 182 182 (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server. 183 183 184 184 ... ... @@ -478,7 +478,7 @@ 478 478 * (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 479 479 * (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 480 480 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 481 -* (% style="color:#037691" %)**MINOR:** (%%)The M AJOR485 +* (% style="color:#037691" %)**MINOR:** (%%)The MINOR from the strongest iBeacon. 482 482 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 483 483 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 484 484 ... ... @@ -636,8 +636,6 @@ 636 636 |(% style="width:135px" %)Exit Alarm Mode|(% style="width:220px" %)Fast press the (% style="color:red" %)**RED** (%%)button 10 times|(% style="width:265px" %)Exit Alarm Mode 637 637 |(% style="width:135px" %)Enter Deep Sleep Mode|(% style="width:220px" %)Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|(% style="width:265px" %)This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy. 638 638 639 - 640 - 641 641 == 2.12 USB Port Function == 642 642 643 643 ... ... @@ -1036,16 +1036,16 @@ 1036 1036 1037 1037 boot_app0.bin @0e000 1038 1038 1039 - ESP_LORA-eeprom-class.bin @ 0x100001041 +US915.bin @ 0x10000(Select the bin file of the frequency band you need) 1040 1040 1041 1041 1042 -[[image:1 664503593459-435.png]]1044 +[[image:image-20221118105220-2.png]] 1043 1043 1044 1044 1045 1045 1046 1046 After upgrade finish, it will show finish as below: 1047 1047 1048 -[[image: 1664503611848-385.png]]1050 +[[image:image-20221118105402-4.png]] 1049 1049 1050 1050 1051 1051 ... ... @@ -1189,7 +1189,35 @@ 1189 1189 [[image:image-20221102140801-6.png]] 1190 1190 1191 1191 1194 +== 7.4 How to modify source code to compile different frequency band bin file? == 1192 1192 1196 + 1197 +(% class="box infomessage" %) 1198 +((( 1199 +(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings. 1200 +See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]] 1201 +))) 1202 + 1203 +1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file. 1204 + 1205 +[[image:image-20221116111844-1.png||height="227" width="782"]] 1206 + 1207 +2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except). 1208 + 1209 +[[image:image-20221116111844-2.png||height="262" width="781"]] 1210 + 1211 +3.Compile the AS923_JP band, please refer to the intention shown 1212 + 1213 +[[image:image-20221116111844-3.png||height="338" width="746"]] 1214 + 1215 +4.In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below. 1216 + 1217 +[[image:image-20221116111844-4.png||height="641" width="739"]] 1218 + 1219 +[[image:image-20221116111844-5.png||height="551" width="708"]] 1220 + 1221 + 1222 + 1193 1193 = 8 Trouble Shooting = 1194 1194 1195 1195 ... ... @@ -1211,18 +1211,84 @@ 1211 1211 1212 1212 1213 1213 1214 -== 8.3 Thereason why it hasbeenrestarted afterupgrading(V.1.4.1)==1244 +== 8.3 Problem after Upgrading Firmware == 1215 1215 1246 +=== 8.3.1 Continue Restart after upgrading === 1216 1216 1248 + 1217 1217 ((( 1218 1218 If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure 1219 1219 ))) 1220 1220 1221 1221 1222 -[[image:image-202211 07145243-1.png||height="695" width="443"]]1254 +[[image:image-20221118105249-3.png]] 1223 1223 1224 1224 1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1225 1225 1259 +It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 1260 + 1261 + 1262 +==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ==== 1263 + 1264 +[[image:image-20221122100004-1.png||height="497" width="534"]] 1265 + 1266 + Figure 1 1267 + 1268 + [[image:image-20221122100004-2.png||height="619" width="389"]] 1269 + 1270 + Figure 2 1271 + 1272 +After the upgrade is completed, enter AT+CFG as shown in the figure below. 1273 + 1274 +[[image:image-20221122100004-3.png]] 1275 + 1276 +Please AT+FDR, and then enter the following instructions by the information on the label 1277 + 1278 +AT+DEUI=70B3D57ED0053981 1279 + 1280 +AT+APPEUI=D23345667BCBCCAF 1281 + 1282 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1 1283 + 1284 +AT+DADDR=260b4dce 1285 + 1286 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d 1287 + 1288 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 1289 + 1290 + 1291 + 1292 +==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ==== 1293 + 1294 +[[image:image-20221122100004-4.png]] 1295 + 1296 +== == 1297 + 1298 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1299 + 1300 +Please download version 1.4.2 again 1301 + 1302 + 1303 +((( 1304 +== 8.5 How to deal with unsuccessful GPS positioning? == 1305 + 1306 +1) Make Sure the device is in Open Area where can see the sky. 1307 +2) Set PDOP to a higher value. 1308 + 1309 + AT+PDOP=2(can be positioned precisely.) 1310 + 1311 + AT+PDOP=7(Quickly locate in open spaces) 1312 + 1313 + AT+PDOP=14.7(Positioning can be acquired in complex environments) 1314 + 1315 +Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP 1316 +))) 1317 + 1318 + 1319 +== == 1320 + 1321 + 1226 1226 = 9. Order Info = 1227 1227 1228 1228 ... ... @@ -1263,5 +1263,3 @@ 1263 1263 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1264 1264 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1265 1265 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1266 - 1267 -
- image-20221116111844-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.8 KB - Content
- image-20221116111844-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.6 KB - Content
- image-20221116111844-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +37.0 KB - Content
- image-20221116111844-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +96.8 KB - Content
- image-20221116111844-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.0 KB - Content
- image-20221118104359-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +38.0 KB - Content
- image-20221118105220-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.2 KB - Content
- image-20221118105249-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.2 KB - Content
- image-20221118105402-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.7 KB - Content
- image-20221122100004-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +18.0 KB - Content
- image-20221122100004-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +127.2 KB - Content
- image-20221122100004-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +12.5 KB - Content
- image-20221122100004-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.3 KB - Content