Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -120,15 +120,15 @@
120	120
121	121
122	122
123		-1. Use TrackerD
124		-11. How it works?
	123	+= 2.1 Use TrackerD =
125	125
	125	+== 2.1 How it works? ==
126	126
	127	+
127	127	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.
128	128
129	129
130		-1.
131		-11. Quick guide to connect to LoRaWAN server
	131	+== 2.2 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		-**Step 1**: Create a device in TTN V3 with the OTAA keys from TrackerD.
	141	+**(% style="color:blue" %)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		-**Step 2**: Power on TrackerD by using the on board switch.
	171	+**(% style="color:blue" %)Step 2**:(%%) Power on TrackerD by using the on board switch.
172	172
173	173
174		-**Step 3:** TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
	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.
175	175
176	176
177		-**Positioning Mode(SMOD):**
	177	+**(% style="color:blue" %)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,19 +183,14 @@
183	183	User can switch modes by [[changing SMOD>>path:#Positioning_Mode]].
184	184
185	185
186		-1.
187		-11. Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~-
	186	+== 2.3 Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- ==
188	188
189	189
190		-1.
191		-11.
192		-111. Uplink FPORT=5, Device Status
	189	+=== 2.3.1 Uplink FPORT=5, Device Status ===
193	193
194	194
195	195
196		-1.
197		-11.
198		-111. Uplink FPORT= , Realtime GNSS Positioning
	193	+=== 2.3.2 Uplink FPORT= , Realtime GNSS Positioning ===
199	199
200	200	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. )
201	201
...	...	@@ -287,15 +287,11 @@
287	287
288	288
289	289
290		-1.
291		-11.
292		-111. Uplink FPORT= , History GNSS Positioning
	285	+=== 2.3.3 Uplink FPORT= , History GNSS Positioning ===
293	293
294	294
295	295
296		-1.
297		-11.
298		-111. BLE positioning Payload(Fport=2)
	289	+=== 2.3.4 BLE positioning Payload(Fport=2) ===
299	299
300	300	Different MODE has different payload:
301	301
...	...	@@ -341,10 +341,9 @@
341	341	* **RSSI**: The RSSI from the strongest iBeacon.
342	342
343	343
344		-1.
345		-11.
346		-111. Add Payload format in TTN V3
347	347
	336	+=== 2.3.5 Add Payload format in TTN V3 ===
	337	+
348	348	In TTN V3, use can add a custom payload so it shows friendly.
349	349
350	350	In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
...	...	@@ -362,8 +362,7 @@
362	362
363	363
364	364
365		-1.
366		-11. Integrate with Datacake
	355	+== 2.4 Integrate with Datacake ==
367	367
368	368
369	369	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.
...	...	@@ -373,8 +373,7 @@
373	373	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
374	374
375	375
376		-1.
377		-11. Integrate with Tago
	365	+== 2.5 Integrate with Tago ==
378	378
379	379
380	380	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.
...	...	@@ -386,8 +386,7 @@
386	386
387	387
388	388
389		-1.
390		-11. Alarm Mode
	377	+== 2.6 Alarm Mode ==
391	391
392	392
393	393	User can push the **RED button** by more than 5 seconds to enter Alarm Mode.
...	...	@@ -404,13 +404,11 @@
404	404	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.
405	405
406	406
407		-1.
408		-11. Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--
	394	+== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
409	409
410	410
411	411
412		-1.
413		-11. LED Status
	398	+== 2.8 LED Status ==
414	414
415	415
416	416	|**Event**|**Action**|**AT+LON to control on/off**
...	...	@@ -430,8 +430,7 @@
430	430
431	431
432	432
433		-1.
434		-11. Button Function
	418	+== 2.9 Button Function ==
435	435
436	436	**RESET button:**
437	437
...	...	@@ -452,8 +452,7 @@
452	452
453	453
454	454
455		-1.
456		-11. USB Port Function
	439	+== 2.10 USB Port Function ==
457	457
458	458	The USB interface of TrackerD has below functions:
459	459
...	...	@@ -466,7 +466,7 @@
466	466
467	467
468	468
469		-1. Configure TrackerD via AT command or LoRaWAN downlink
	452	+= 3. Configure TrackerD via AT command or LoRaWAN downlink =
470	470
471	471
472	472	User can configure TrackerD via AT Command or LoRaWAN Downlink.
...	...	@@ -474,8 +474,7 @@
474	474	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]]
475	475
476	476
477		-1.
478		-11. Access AT Command
	460	+== 3.1 Access AT Command ==
479	479
480	480	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. ...
481	481
...	...	@@ -494,13 +494,10 @@
494	494	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
495	495
496	496
497		-1.
498		-11. Command Set
	479	+== 3.2 Command Set ==
499	499
500	500
501		-1.
502		-11.
503		-111. Set Transmit Interval
	482	+=== 3.2.1 Set Transmit Interval ===
504	504
505	505	Set device uplink interval.
506	506
...	...	@@ -516,9 +516,7 @@
516	516	0x01 00 01 2C     ~/~/ Same as AT+TDC=300000
517	517
518	518
519		-1.
520		-11.
521		-111. Set Alarm Packet transmission interval
	498	+=== 3.2.2 Set Alarm Packet transmission interval ===
522	522
523	523	Set alarm packet transmit interval
524	524