Last modified by Xiaoling on 2025/04/07 17:16
<
From version < 19.3 >
edited by Xiaoling
on 2022/09/30 09:23
To version < 19.2 >
edited by Xiaoling
on 2022/09/30 09:12
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -120,15 +120,15 @@
120 120  
121 121  
122 122  
123 -= 2.1 Use TrackerD =
123 +1. Use TrackerD
124 +11. How it works?
124 124  
125 -== 2.1 How it works? ==
126 126  
127 -
128 128  TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
129 129  
130 130  
131 -== 2.2 Quick guide to connect to LoRaWAN server ==
130 +1.
131 +11. Quick guide to connect to LoRaWAN server
132 132  
133 133  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.
134 134  
... ... @@ -138,7 +138,7 @@
138 138  
139 139  The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3:
140 140  
141 -**(% style="color:blue" %)Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
141 +**Step 1**: Create a device in TTN V3 with the OTAA keys from TrackerD.
142 142  
143 143  Each TrackerD is shipped with a sticker with the default device EUI as below:
144 144  
... ... @@ -168,13 +168,13 @@
168 168  
169 169  
170 170  
171 -**(% style="color:blue" %)Step 2**:(%%) Power on TrackerD by using the on board switch.
171 +**Step 2**: Power on TrackerD by using the on board switch.
172 172  
173 173  
174 -**(% 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.
174 +**Step 3:** TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
175 175  
176 176  
177 -**(% style="color:blue" %)Positioning Mode(SMOD):**
177 +**Positioning Mode(SMOD):**
178 178  
179 179  * **GPS ONLY(Factory Settings): **only get GPS location info.
180 180  * **BLE ONLY: **Only obtain iBeacon info via BLE. Design for Indoor tracking.
... ... @@ -183,14 +183,19 @@
183 183  User can switch modes by [[changing SMOD>>path:#Positioning_Mode]].
184 184  
185 185  
186 -== 2.3 Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- ==
186 +1.
187 +11. Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~-
187 187  
188 188  
189 -=== 2.3.1 Uplink FPORT=5, Device Status ===
190 +1.
191 +11.
192 +111. Uplink FPORT=5, Device Status
190 190  
191 191  
192 192  
193 -=== 2.3.2 Uplink FPORT= , Realtime GNSS Positioning ===
196 +1.
197 +11.
198 +111. Uplink FPORT= , Realtime GNSS Positioning
194 194  
195 195  The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won’t work on DR0 on US915/AU915 frequency band. )
196 196  
... ... @@ -282,11 +282,15 @@
282 282  
283 283  
284 284  
285 -=== 2.3.3 Uplink FPORT= , History GNSS Positioning ===
290 +1.
291 +11.
292 +111. Uplink FPORT= , History GNSS Positioning
286 286  
287 287  
288 288  
289 -=== 2.3.4 BLE positioning Payload(Fport=2) ===
296 +1.
297 +11.
298 +111. BLE positioning Payload(Fport=2)
290 290  
291 291  Different MODE has different payload:
292 292  
... ... @@ -332,9 +332,10 @@
332 332  * **RSSI**: The RSSI from the strongest iBeacon.
333 333  
334 334  
344 +1.
345 +11.
346 +111. Add Payload format in TTN V3
335 335  
336 -=== 2.3.5 Add Payload format in TTN V3 ===
337 -
338 338  In TTN V3, use can add a custom payload so it shows friendly.
339 339  
340 340  In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
... ... @@ -352,7 +352,8 @@
352 352  
353 353  
354 354  
355 -== 2.4 Integrate with Datacake ==
365 +1.
366 +11. Integrate with Datacake
356 356  
357 357  
358 358  After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
... ... @@ -362,7 +362,8 @@
362 362  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
363 363  
364 364  
365 -== 2.5 Integrate with Tago ==
376 +1.
377 +11. Integrate with Tago
366 366  
367 367  
368 368  After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
... ... @@ -374,7 +374,8 @@
374 374  
375 375  
376 376  
377 -== 2.6 Alarm Mode ==
389 +1.
390 +11. Alarm Mode
378 378  
379 379  
380 380  User can push the **RED button** by more than 5 seconds to enter Alarm Mode.
... ... @@ -391,11 +391,13 @@
391 391  When exit alarm mode, **RED LED** will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.
392 392  
393 393  
394 -== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
407 +1.
408 +11. Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--
395 395  
396 396  
397 397  
398 -== 2.8 LED Status ==
412 +1.
413 +11. LED Status
399 399  
400 400  
401 401  |**Event**|**Action**|**AT+LON to control on/off**
... ... @@ -415,7 +415,8 @@
415 415  
416 416  
417 417  
418 -== 2.9 Button Function ==
433 +1.
434 +11. Button Function
419 419  
420 420  **RESET button:**
421 421  
... ... @@ -436,7 +436,8 @@
436 436  
437 437  
438 438  
439 -== 2.10 USB Port Function ==
455 +1.
456 +11. USB Port Function
440 440  
441 441  The USB interface of TrackerD has below functions:
442 442  
... ... @@ -449,7 +449,7 @@
449 449  
450 450  
451 451  
452 -= 3. Configure TrackerD via AT command or LoRaWAN downlink =
469 +1. Configure TrackerD via AT command or LoRaWAN downlink
453 453  
454 454  
455 455  User can configure TrackerD via AT Command or LoRaWAN Downlink.
... ... @@ -457,7 +457,8 @@
457 457  LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]]
458 458  
459 459  
460 -== 3.1 Access AT Command ==
477 +1.
478 +11. Access AT Command
461 461  
462 462  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. ...
463 463  
... ... @@ -476,10 +476,13 @@
476 476  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
477 477  
478 478  
479 -== 3.2 Command Set ==
497 +1.
498 +11. Command Set
480 480  
481 481  
482 -=== 3.2.1 Set Transmit Interval ===
501 +1.
502 +11.
503 +111. Set Transmit Interval
483 483  
484 484  Set device uplink interval.
485 485  
... ... @@ -495,7 +495,9 @@
495 495  0x01 00 01 2C     ~/~/ Same as AT+TDC=300000
496 496  
497 497  
498 -=== 3.2.2 Set Alarm Packet transmission interval ===
519 +1.
520 +11.
521 +111. Set Alarm Packet transmission interval
499 499  
500 500  Set alarm packet transmit interval
501 501  

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0