Summary

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

Details

Page properties

Content

...	...	@@ -97,6 +97,9 @@
97	97	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
98	98	* Tracking: max: 38mA
99	99
	100	+
	101	+
	102	+
100	100	== 1.3  Features ==
101	101
102	102
...	...	@@ -115,6 +115,9 @@
115	115	* Tri-color LED, Alarm button
116	116	* Datalog
117	117
	121	+
	122	+
	123	+
118	118	== 1.4  Applications ==
119	119
120	120
...	...	@@ -121,6 +121,9 @@
121	121	* Logistics and Supply Chain Management
122	122	* Human tracking
123	123
	130	+
	131	+
	132	+
124	124	= 2.1 Use TrackerD =
125	125
126	126
...	...	@@ -183,8 +183,9 @@
183	183	(% 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.
184	184
185	185
186		-== 2.3 Positioning Mode(SMOD) ==
	195	+== 2.3  Positioning Mode(SMOD) ==
187	187
	197	+
188	188	Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
189	189
190	190	* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
...	...	@@ -194,12 +194,13 @@
194	194	Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
195	195
196	196
197		-== 2.3 Uplink Payload ==
198	198
	208	+== 2.4  Uplink Payload ==
199	199
200		-=== 2.3.1 Uplink FPORT~=5, Device Status ===
201	201
	211	+=== 2.4.1 Uplink FPORT~=5, Device Status ===
202	202
	213	+
203	203	Uplink the device configures with FPORT=5. Once LGT92 Joined the network, it will uplink this message to the server. After first uplink, LHT52 will uplink Device Status every 12 hours.
204	204
205	205
...	...	@@ -248,7 +248,7 @@
248	248
249	249
250	250
251		-=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
	262	+=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
252	252
253	253
254	254	User can use **AT+SMOD=1,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, please note that 15 bytes won't work on DR0 on US915/AU915 frequency band.
...	...	@@ -348,7 +348,7 @@
348	348
349	349
350	350
351		-=== 2.3.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
	362	+=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
352	352
353	353
354	354	The default uplink payload includes totally 11 bytes. The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
...	...	@@ -362,22 +362,21 @@
362	362	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
363	363	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
364	364
365		-
366	366	(% class="wikigeneratedid" %)
367	367	[[image:1665301687277-443.png]]
368	368
369	369
370	370
371		-=== 2.3.4  Uplink FPORT~=4, History GNSS Positioning ===
	381	+=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
372	372
373	373
374	374	Set [[PNACKMD=1>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-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.
375	375
376	376
377		-**Note for this mode:**
	387	+(% style="color:red" %)**Note for this mode:**
378	378
379	379	* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
380		-* b) TrackerD will send data in **CONFIRMED Mode** when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
	390	+* b) TrackerD will send data in (% style="color:blue" %)**CONFIRMED Mode**(%%) when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
381	381
382	382	The payload is 15 bytes, as below.
383	383
...	...	@@ -385,13 +385,13 @@
385	385	|=(% scope="row" %)(((
386	386	**Size(bytes)**
387	387	)))|4|4|2|1|1|1|1|1
388		-|=**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|[[Year>>path:#Alarm]]|Month|Day|Hous|Min|[[Sen>>path:#Pitch]]
	398	+|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
389	389
390	390	[[image:1665301786397-168.png]]
391	391
392	392
393	393
394		-=== 2.3.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
	404	+=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
395	395
396	396
397	397	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
...	...	@@ -421,7 +421,7 @@
421	421	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
422	422	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
423	423
424		-=== 2.3.5 Add Payload format in TTN V3 ===
	434	+=== 2.4.5 Add Payload format in TTN V3 ===
425	425
426	426
427	427	In TTN V3, use can add a custom payload so it shows friendly.
...	...	@@ -441,7 +441,7 @@
441	441
442	442
443	443
444		-== 2.4 Integrate with Datacake ==
	454	+== 2.5 Integrate with Datacake ==
445	445
446	446
447	447	(((
...	...	@@ -457,7 +457,7 @@
457	457
458	458
459	459
460		-== 2.5 Integrate with Tago ==
	470	+== 2.6 Integrate with Tago ==
461	461
462	462
463	463	(((
...	...	@@ -473,11 +473,11 @@
473	473
474	474
475	475
476		-== 2.6 Datalog Feature ==
	486	+== 2.7 Datalog Feature ==
477	477
478	478	total 273 entries,by default disable
479	479
480		-== 2.6 Alarm Mode ==
	490	+== 2.8 Alarm Mode ==
481	481
482	482
483	483	(((
...	...	@@ -503,13 +503,13 @@
503	503
504	504
505	505
506		-== 2.7 Transport Mode ==
	516	+== 2.9 Transport Mode ==
507	507
508	508
509	509	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.
510	510
511	511
512		-== 2.8 LED Status ==
	522	+== 2.10 LED Status ==
513	513
514	514
515	515	(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
...	...	@@ -526,7 +526,7 @@
526	526	|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
527	527	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
528	528
529		-== 2.9 Button Function ==
	539	+== 2.11 Button Function ==
530	530
531	531
532	532	(% style="color:blue" %)**RESET button:**
...	...	@@ -547,7 +547,7 @@
547	547	|(% 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
548	548	|(% 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.
549	549
550		-== 2.10 USB Port Function ==
	560	+== 2.12 USB Port Function ==
551	551
552	552
553	553	The USB interface of TrackerD has below functions: