Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)

Last modified by Xiaoling on 2023/12/27 09:15

From 145.1 to 144.1 From 157.1 to 156.1

From version 156.1

edited by Bei Jinggeng
on 2022/11/28 10:29

Change comment: Uploaded new attachment "image-20221128102938-1.png", version {1}

To version 145.1

edited by Edwin Chen
on 2022/11/22 12:21

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- image-20221128102938-1.png

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Bei
++XWiki.Edwin

Content

@@ -1,5 +1,5 @@
  (% style="text-align:center" %)
--[[image:1664505654417-133.png||_mstalt="293696"]]
++[[image:1664505654417-133.png]]
@@ -31,12 +31,15 @@
  (((
  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
  )))
++)))
  (((
  TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
++
++
  )))
--[[image:1664499921684-770.png||_mstalt="298194"]]
++[[image:1664499921684-770.png]]
  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
@@ -92,8 +92,6 @@
  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
  * Tracking: max: 38mA
--
--
  == 1.3  Features ==
@@ -112,8 +112,6 @@
  * Tri-color LED, Alarm button
  * Datalog
--
--
  == 1.4  Applications ==
@@ -120,8 +120,6 @@
  * Logistics and Supply Chain Management
  * Human tracking
--
--
  = 2.  Use TrackerD =
  == 2.1  How it works? ==
@@ -136,7 +136,7 @@
  Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example.
--[[image:1664501652064-326.png||_mstalt="293306"]]
++[[image:1664501652064-326.png]]
@@ -148,7 +148,7 @@
  Each TrackerD is shipped with a sticker with the default device EUI as below:
--[[image:1664501677253-891.png||_mstalt="296569"]]
++[[image:1664501677253-891.png]]
  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
@@ -157,14 +157,14 @@
  **__Add APP EUI in the application:__**
--[[image:1664501711466-918.png||_mstalt="295828"]]
++[[image:1664501711466-918.png]]
--[[image:1664501721248-725.png||_mstalt="294450"]]
++[[image:1664501721248-725.png]]
--[[image:1664501734705-405.png||_mstalt="293306"]]
++[[image:1664501734705-405.png]]
@@ -171,15 +171,15 @@
  **__Add APP KEY and DEV EUI:__**
--[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
++[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
--(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
++(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
--[[image:1664502835802-546.png||_mstalt="295061"]]
++[[image:1664502835802-546.png]]
  (% 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.
@@ -211,7 +211,7 @@
  |=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
  |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
--[[image:1665301570342-765.png||_mstalt="294580"]]
++[[image:1665301570342-765.png]]
  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
@@ -278,7 +278,7 @@
  (% style="color:red" %)**      1: ** (%%)  BLE Positioning with Strongest iBeacon
--(% _mstmutation="1" style="color:red" %)**      2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)
++(% style="color:red" %)**      2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)
  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
@@ -287,8 +287,6 @@
  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
  |=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
--
--
  === 2.4.2  Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
@@ -307,7 +307,7 @@
  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
--[[image:1665301636888-168.png||_mstalt="298012"]]
++[[image:1665301636888-168.png]]
  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
@@ -337,12 +337,12 @@
 .  In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
--[[image:1664502116362-706.png||_mstalt="293306"]]
++[[image:1664502116362-706.png]]
 .  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
--[[image:1664502166010-515.png||_mstalt="291395"]]
++[[image:1664502166010-515.png]]
@@ -365,8 +365,6 @@
  * 3.40v ~~ 3.69v:   20% ~~ 40%
  * < 3.39v:             0~~20%
--
--
  ==== (% style="color:blue" %)**MOD:**(%%) ====
  **Example: ** (0x60>>6) & 0x3f =1
@@ -422,13 +422,13 @@
  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
  (% class="wikigeneratedid" %)
--[[image:1665301687277-443.png||_mstalt="296140"]]
++[[image:1665301687277-443.png]]
  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
--Set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
++Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
  (% style="color:red" %)**Note for this mode:**
@@ -445,7 +445,7 @@
  )))|4|4|2|1|1|1|1|1
  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
--[[image:image-20221009160309-2.png||_mstalt="429312"]]
++[[image:image-20221009160309-2.png]]
  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
@@ -472,7 +472,7 @@
  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
--[[image:1664502425687-834.png||_mstalt="296738"]]
++[[image:1664502425687-834.png]]
  * (% style="color:#037691" %)**BAT: **  (%%)     Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
@@ -483,8 +483,6 @@
  * (% style="color:#037691" %)**Measured Power: ** (%%)   The Measured Power from the strongest iBeacon.
  * (% style="color:#037691" %)**RSSI:  **    (%%) The RSSI from the strongest iBeacon.
--
--
  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
@@ -500,7 +500,7 @@
  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
  (% class="wikigeneratedid" %)
--[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
++[[image:1667288597595-714.png||height="212" width="1151"]]
  * (% style="color:#037691" %)**BAT: **  (%%)    Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
@@ -507,8 +507,6 @@
  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
--
--
  === 2.4.7  Add Payload format in TTN V3 ===
@@ -517,7 +517,7 @@
  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
--[[image:1664502649601-895.png||_mstalt="296985"]]
++[[image:1664502649601-895.png]]
@@ -527,7 +527,7 @@
  Save the change the uplink message will be parsed. As below:
--[[image:1664502676891-606.png||_mstalt="296673"]]
++[[image:1664502676891-606.png]]
  == 2.5  Integrate with Datacake ==
@@ -538,7 +538,7 @@
  Instruction is here:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]
--[[image:1664502695771-538.png||_mstalt="297349"]]
++[[image:1664502695771-538.png]]
  == 2.6  Integrate with Tago ==
@@ -549,7 +549,7 @@
  Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget]]
--[[image:1664502715371-321.png||_mstalt="292162"]]
++[[image:1664502715371-321.png]]
  == 2.7  Datalog Feature ==
@@ -557,14 +557,14 @@
  total 273 entries,by default,
--User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
++User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
  Example use case.
--[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
++[[image:image-20221009234703-2.png||height="328" width="899"]]
--[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
++[[image:image-20221009234629-1.png||height="390" width="577"]]
  == 2.8  Alarm Mode ==
@@ -597,12 +597,7 @@
  In Transport Mode, TrackerD will check if there is motion. If there is no motion, device will send uplinks every 20 minutes. If there is motion, device will send uplink every 5 minutes.
--* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
--* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
--* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
--
--
  == 2.10  LED Status ==
@@ -620,14 +620,12 @@
  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
--
--
  == 2.11  Button Function ==
  (% style="color:blue" %)**RESET button:**
--[[image:1664502835802-546.png||_mstalt="295061"]]
++[[image:1664502835802-546.png]]
  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
@@ -634,7 +634,7 @@
  (% style="color:red" %)**RED button:**
--[[image:1664502854406-763.png||_mstalt="295568"]]
++[[image:1664502854406-763.png]]
  (% border="1" style="background-color:#ffffcc; width:510px" %)
@@ -643,8 +643,6 @@
  |(% 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
  |(% 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.
--
--
  == 2.12  USB Port Function ==
@@ -655,8 +655,6 @@
  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
--
--
  = 3.  Configure TrackerD via AT command or LoRaWAN downlink =
@@ -671,21 +671,22 @@
  TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below.
--[[image:1664502999401-486.png||_mstalt="296985"]]
++[[image:1664502999401-486.png]]
  In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
--[[image:1664503022490-662.png||_mstalt="293332"]]
++[[image:1664503022490-662.png]]
--[[image:1664503035713-500.png||_mstalt="291096"]]
++[[image:1664503035713-500.png]]
--[[image:1664503047675-651.png||_mstalt="295386"]]
++[[image:1664503047675-651.png]]
++
  == 3.2  Command Set ==
  === 3.2.1  Set Transmit Interval ===
@@ -811,9 +811,9 @@
  (% style="color:#037691" %)**cc:   **
--* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
++* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
--* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
++* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))
  (% style="color:blue" %)**Example:**
@@ -876,9 +876,8 @@
--=== 3.2.10  Disable/Enable the confirmation mode ===
++**Disable/Enable the confirmation mode**
--
  * (% style="color:blue" %)**AT Command:**
  (% style="color:#037691" %)**AT+CFM=xx**
@@ -896,7 +896,7 @@
  (% style="color:#037691" %)**0x05 01 **(%%)         ~/~/  Same as AT+CFM=1
--=== 3.2.11  Auto Send None-ACK messages ===
++=== 3.2.10  Auto Send None-ACK messages ===
  TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
@@ -914,10 +914,10 @@
  * (% style="color:blue" %)**Downlink Command: 0x34**
--Example: 0x34 01     ~/~/  Same as AT+PNACKMD=1
++Example: 0x3401     ~/~/  Same as AT+PNACKMD=1
--=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
++=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
  BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
@@ -926,16 +926,16 @@
  (% style="color:blue" %)**AT Command:**
--     (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%)  ~/~/ Set BLEMASK = 123456
++     (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%)  ~/~/ Set BLEMASK = 123456
--     (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%)             ~/~/ disable BLEMASK
++     (% style="color:#037691" %)**AT+BLEMASK=0**  (%%)             ~/~/ disable BLEMASK
  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
--Example:  0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
++Example:  0xB2010203040506    ~/~/ Set BLEMASK to 123456
--=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
++=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
  WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
@@ -944,16 +944,16 @@
  (% style="color:blue" %)**AT Command:**
--     (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
++     (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
--     (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%)        ~/~/ disable WiFiMASK
++     (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%)        ~/~/ disable WiFiMASK
  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
--Example:  0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
++Example:  0xB3010203040506    ~/~/ Set WiFiMASK to 123456
--=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
++=== 3.2.13  Disable/Enable Information printing（Since firmware 1.4.1） ===
  Users can use this feature to enable/disable Information printing.
@@ -964,7 +964,7 @@
  \\Example:  AT+SHOWID=1   ~-~->    Enable Information printing.
--=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
++=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
@@ -979,26 +979,6 @@
  Example: 0x24 01 ~/~/ Same as AT+CHE=1
--=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
--
--User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
--
--(% style="color:blue" %)**AT Command:**
--
--(% style="color:#037691" %)**AT+PT=xx**
--
-- Example:
--
--  AT+PT=14    ~-~->    Set to detect car motion.
--
--  AT+PT=41   ~-~->    set to detect walk motion.
--
--
--(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
--0xB4 14          ~/~/  Same as AT+PT=14
--
--
--
  = 4.  Setting for Different Scenarios =
@@ -1031,10 +1031,10 @@
  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
--[[image:1664503563660-578.png||_mstalt="296777"]]
++[[image:1664503563660-578.png]]
--[[image:1664503574618-659.png||_mstalt="297986"]]
++[[image:1664503574618-659.png]]
@@ -1050,13 +1050,13 @@
  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
--[[image:image-20221118105220-2.png||_mstalt="426608"]]
++[[image:image-20221118105220-2.png]]
  After upgrade finish, it will show finish as below:
--[[image:image-20221118105402-4.png||_mstalt="427986"]]
++[[image:image-20221118105402-4.png]]
@@ -1072,23 +1072,23 @@
  Install IDE on PC, open and click (% style="color:#037691" %)**File ~-~-> Preference**,(%%) add the following URL:  [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]
--[[image:1664503635019-941.png||_mstalt="294658"]]
++[[image:1664503635019-941.png]]
  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
--[[image:1664503715811-892.png||_mstalt="295698"]]
++[[image:1664503715811-892.png]]
  (% id="cke_bm_4554S" style="display:none" %) (%%)Find the path of SP32 installation, find the file as shown in Figure 1, and change the SPI pin to the shown in Figure 2.
--[[image:image-20221024105643-1.png||_mstalt="428129"]]
++[[image:image-20221024105643-1.png]]
  **~                                                                                Figure1**
--[[image:image-20221024105643-2.png||_mstalt="428493"]]
++[[image:image-20221024105643-2.png]]
                                                                                     **Figure2**
@@ -1098,7 +1098,7 @@
  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
--[[image:1664503752288-974.png||_mstalt="298194"]]
++[[image:1664503752288-974.png]]
  == 6.2  Source Code ==
@@ -1106,19 +1106,19 @@
  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
--[[image:1664503794261-827.png||_mstalt="296387"]]
++[[image:1664503794261-827.png]]
  * (% style="color:blue" %)**Click to upload**
--[[image:1664503808294-336.png||_mstalt="295711"]]
++[[image:1664503808294-336.png]]
  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
--[[image:1664503824081-592.png||_mstalt="294918"]]  [[image:1664503831430-500.png||_mstalt="290784"]]
++[[image:1664503824081-592.png]]  [[image:1664503831430-500.png]]
  = 7.  FAQ =
@@ -1132,7 +1132,7 @@
  == 7.2  What is the pin mapping for the USB program cable? ==
--[[image:1664499635206-262.png||_mstalt="295360"]]
++[[image:1664499635206-262.png]]
@@ -1147,8 +1147,6 @@
  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
--
--
  == 7.3  Notes on using different serial port tools for TrackerD ==
  === 7.3.1  Serial port utility ===
@@ -1159,13 +1159,13 @@
  Need to adjust the data stream to RTS/CTS on physical restart.
  (% class="wikigeneratedid" %)
--[[image:image-20221102140621-1.png||_mstalt="425672"]]
++[[image:image-20221102140621-1.png]]
  When using AT commands, the data flow needs to be adjusted to XON/XOFF
--[[image:image-20221102140638-2.png||_mstalt="428727"]]
++[[image:image-20221102140638-2.png]]
  === 7.3.2  SecureCRT ===
@@ -1174,22 +1174,22 @@
  The default command window of SecureCRT is not displayed. Entering a command requires a complete input of the entire command. You can open the command window in the view.
--[[image:image-20221102140704-3.png||_mstalt="427076"]]
++[[image:image-20221102140704-3.png]]
--[[image:image-20221102140712-4.png||_mstalt="427089"]]
++[[image:image-20221102140712-4.png]]
  === 7.3.3  PUTTY ===
--[[image:image-20221102140748-5.png||_mstalt="430456"]]
++[[image:image-20221102140748-5.png]]
  Since putty does not have a command window, you need to fill in the complete command externally, and then copy it to putty.The information copied outside can be pasted by right-clicking the mouse in putty.
--[[image:image-20221102140801-6.png||_mstalt="427466"]]
++[[image:image-20221102140801-6.png]]
  == 7.4 How to modify source code to compile different frequency band bin file? ==
@@ -1204,7 +1204,7 @@
  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
--[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
++[[image:image-20221116111844-1.png||height="227" width="782"]]
@@ -1211,7 +1211,7 @@
  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
--[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
++[[image:image-20221116111844-2.png||height="262" width="781"]]
@@ -1218,7 +1218,7 @@
  **3. Compile the AS923_JP band, please refer to the intention shown**
--[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
++[[image:image-20221116111844-3.png||height="338" width="746"]]
@@ -1225,10 +1225,10 @@
  **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.**
--[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
++[[image:image-20221116111844-4.png||height="641" width="739"]]
--[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
++[[image:image-20221116111844-5.png||height="551" width="708"]]
  = 8  Trouble Shooting =
@@ -1237,7 +1237,7 @@
  (((
--Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**AT+INTWK=1**(%%)), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
++Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
  )))
@@ -1251,69 +1251,50 @@
  == 8.3  Problem after Upgrading Firmware ==
--=== 8.3.1  "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
++=== 8.3.1 Continue Restart after upgrading ===
--**Error Output**
--
--
--[[image:image-20221122100004-4.png||_mstalt="424606"]]
--
--
  (((
--Some partition is missed during upgrade, please upgrade below four files as example:
--
--[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
++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
  )))
--=== 8.3.2  TrackerD's led light is always GREEN on after upgrading ===
++[[image:image-20221118105249-3.png]]
--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
++=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
--=== 8.3.3  "flash read err" after upgrade firmware ===
++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
++=== 8.3.3 "flash read err" after upgrade firmware ===
++
  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
++[[image:image-20221122100004-1.png||height="497" width="534"]]
--[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
--
  User need to upgrade again with below four files to solve this issue.
-- [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
++ [[image:image-20221122100004-2.png||height="619" width="389"]]
                                         **Figure 2**
--=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
++=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
--
  User might erase the entire flash include keys and default settings which cause this issue.
--After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
++After the upgrade is completed, enter AT+CFG as shown in the figure below.
++[[image:image-20221122100004-3.png]]
--[[image:image-20221122100004-3.png||_mstalt="424242"]]
++Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
--Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
++Example:
--After AT+FDR. please set
--
--* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
--
--* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
--
--**Example:**
--
--AT+PDOP=7.00
--
--AT+FTIME=180
--
  AT+DEUI=70B3D57ED0053981
  AT+APPEUI=D23345667BCBCCAF
@@ -1327,6 +1327,13 @@
  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
++
++=== 8.3.4  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 ===
++
++
++[[image:image-20221122100004-4.png]]
++
++
  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
@@ -1340,11 +1340,11 @@
 )   Set PDOP to a higher value.
--* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
++*    (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
--* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
++*    (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
--* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
++*    (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
  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
@@ -1370,8 +1370,6 @@
  * (% style="color:red" %)**US915**(%%): Default frequency band US915
--
--
  = 10.  Packing Info =
@@ -1387,8 +1387,6 @@
  * Weight: 50g
--
--
  = 11.  Support =
@@ -1396,8 +1396,6 @@
  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
--
--
  = 12.  Reference =
@@ -1406,4 +1406,3 @@
  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
--)))

image-20221128102938-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-41.3 KB

Content