Summary

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

Details

Page properties

Content

...	...	@@ -201,10 +201,10 @@
201	201
202	202	=== 2.3.1 Uplink FPORT~=5, Device Status ===
203	203
204		-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	+Uplink the device configures with FPORT=5. Once LHT52 Joined the network, it will uplink this message to the server. After first uplink, LHT52 will uplink Device Status every 12 hours.
205	205
206		-|=(% style="width: 150px;" %)**Size (bytes)**|=(% style="width: 233px;" %)**1**|=(% style="width: 150px;" %)**2**|=(% style="width: 164px;" %)**1**|=(% style="width: 215px;" %)**1**|=(% style="width: 94px;" %)2|=(% style="width: 516px;" %)**2**|=(% style="width: 516px;" %)1
207		-|(% style="width:150px" %)**Value**|(% style="width:233px" %)Sensor Model|(% style="width:150px" %)Firmware Version|(% style="width:164px" %)Frequency Band|(% style="width:215px" %)Sub-band|(% style="width:94px" %)BAT|(% style="width:516px" %)SMOD|(% style="width:516px" %)Status
	206	+|=**Size (bytes)**|=**1**|=**2**|=**1**|=**1**|=**2**
	207	+|**Value**|Sensor Model|Firmware Version|Frequency Band|Sub-band|BAT
208	208
209	209	[[image:image-20221006181357-2.png]]
210	210
...	...	@@ -245,23 +245,23 @@
245	245	Use can also get the Device Status uplink through the downlink command:
246	246
247	247
248		-=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
	248	+=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning ===
249	249
250	250
251		-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.
	251	+The default uplink payload includes totally 11 bytes. (User can use AT+SMOD=1,0 to enable uploading on-board Temperature and humidity value, and total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. )
252	252
253	253
254	254	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
255	255	|=(% scope="row" style="width: 50px;" %)(((
256	256	**Size(bytes)**
257		-)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
258		-2
	257	+)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
	258	+2(optional)
259	259	)))|(% style="width:87px" %)(((
260		-2
	260	+2(optional)
261	261	)))
262	262	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
263	263	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
264		-)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
	264	+)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
265	265
266	266	[[image:1664501958445-288.png]]
267	267
...	...	@@ -275,8 +275,8 @@
275	275	==== (% style="color:blue" %)**FLAG:**(%%) ====
276	276
277	277	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
278		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
279		-|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
	278	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
	279	+|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version
280	280
281	281	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
282	282
...	...	@@ -286,19 +286,19 @@
286	286	* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
287	287	* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
288	288
289		-
290	290	(% style="color:red" %)**Important note:**
291	291
292	292	1.  When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF.
293	293
294		-2.  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:
	293	+2.  When enable 9-axis motion sensor, 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:
295	295
296	296
297	297	[[image:1664502116362-706.png]]
298	298
299	299
300		-3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
301	301
	300	+4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
	301	+
302	302	[[image:1664502166010-515.png]]
303	303
304	304
...	...	@@ -313,7 +313,7 @@
313	313	Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
314	314
315	315	(((
316		-The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
	316	+The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
317	317	)))
318	318
319	319	* > 4.0v :  80% ~~ 100%
...	...	@@ -322,7 +322,6 @@
322	322	* 3.40v ~~ 3.69v:  20% ~~ 40%
323	323	* < 3.39v:  0~~20%
324	324
325		-
326	326	==== (% style="color:blue" %)**LON:**(%%) ====
327	327
328	328	Enable/Disable LED activity for uplink
...	...	@@ -346,37 +346,16 @@
346	346	011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
347	347
348	348
349		-=== 2.3.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
350	350
351		-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)
	349	+=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
352	352
353	353
354		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
355		-|=(% scope="row" style="width: 50px;" %)(((
356		-**Size(bytes)**
357		-)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
358		-|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
359		-[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
360		-)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
361	361
	353	+=== 2.3.4 BLE positioning Payload(Fport2) ===
362	362
363	363
364		-=== 2.3.4  Uplink FPORT~=4, History GNSS Positioning ===
	356	+Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
365	365
366		-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.
367		-
368		-**Note for this mode:**
369		-
370		-* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
371		-* 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.
372		-
373		-The payload is 15 bytes, as below.
374		-
375		-
376		-
377		-=== 2.3.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
378		-
379		-
380	380	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
381	381	|=(% scope="row" style="width: 60px;" %)(((
382	382	**Size(bytes)**
...	...	@@ -660,16 +660,16 @@
660	660
661	661
662	662
663		-=== 3.2.6 Disable/Enable Transport Mode ===
	641	+=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
664	664
665	665
666		-Users can use this feature to enable/disable Transport Mode.
	644	+User can use this feature to check and set thread hole of movement detect
667	667
668	668	* (% style="color:blue" %)**AT Command:**
669	669
670	670	(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
671	671
672		-Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
	650	+Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
673	673
674	674
675	675	* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**