Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 54.1
edited by Edwin Chen
on 2022/10/06 18:13
Change comment: Uploaded new attachment "image-20221006181357-2.png", version {1}
To version 71.1
edited by Edwin Chen
on 2022/10/09 23:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -186,42 +186,93 @@
186 186  (% 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.
187 187  
188 188  
189 -= 2.3 Positioning Mode(SMOD) =
190 190  
191 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get GPS location info.
192 -* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
193 -* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.
190 +== 2.3  Positioning Mode(SMOD) ==
194 194  
195 -User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
196 196  
193 +Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
197 197  
195 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
196 +* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
197 +* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
198 198  
199 -== 2.3 Uplink Payload ==
199 +Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
200 200  
201 201  
202 -=== 2.3.1 Uplink FPORT~=5, Device Status ===
203 203  
203 +== 2.4  Uplink Payload ==
204 204  
205 205  
206 -=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
206 +=== 2.4.1 Uplink FPORT~=5, Device Status ===
207 207  
208 208  
209 -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. )
209 +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.
210 210  
211 211  
212 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
213 +|=(% scope="row" style="width: 108px;" %)**Size(bytes)**|=(% style="width: 82px;" %)**1**|=(% style="width: 83px;" %)**2**|=(% style="width: 94px;" %)**1**|=(% style="width: 84px;" %)**1**|=(% style="width: 44px;" %)2|=(% style="width: 63px;" %)**2**|=(% style="width: 60px;" %)1
214 +|=(% 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
215 +
216 +[[image:1665301570342-765.png]]
217 +
218 +
219 +Example Payload (FPort=5):  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT52%20-%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220621105116-11.png?rev=1.1||alt="image-20220621105116-11.png"]]
220 +
221 +**Sensor Model**: For TrackerD, this value is 0x13.
222 +
223 +**Firmware Version**: 0x0100, Means: v1.0.0 version.
224 +
225 +**Frequency Band**:
226 +
227 +*0x01: EU868
228 +
229 +*0x02: US915
230 +
231 +*0x03: IN865
232 +
233 +*0x04: AU915
234 +
235 +*0x05: KZ865
236 +
237 +*0x06: RU864
238 +
239 +*0x07: AS923
240 +
241 +*0x08: AS923-1
242 +
243 +*0x09: AS923-2
244 +
245 +*0x0a: AS923-3
246 +
247 +**Sub-Band**: value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
248 +
249 +**BAT**: shows the battery voltage for TrackerD.
250 +
251 +Ex1: 0x0B3A = 2874mV
252 +
253 +Use can also get the Device Status uplink through the downlink command:
254 +
255 +
256 +
257 +=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
258 +
259 +
260 +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.
261 +
262 +
212 212  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
213 213  |=(% scope="row" style="width: 50px;" %)(((
214 214  **Size(bytes)**
215 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
216 -2(optional)
266 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
267 +2
217 217  )))|(% style="width:87px" %)(((
218 -2(optional)
269 +2
219 219  )))
220 220  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
221 221  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
222 -)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
273 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
223 223  
224 -[[image:1664501958445-288.png]]
275 +[[image:1665301636888-168.png]]
225 225  
226 226  
227 227  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -230,11 +230,15 @@
230 230  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
231 231  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
232 232  
284 +==== ====
285 +
286 +==== ====
287 +
233 233  ==== (% style="color:blue" %)**FLAG:**(%%) ====
234 234  
235 235  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
236 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
237 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 
291 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
292 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
238 238  
239 239  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
240 240  
... ... @@ -249,17 +249,14 @@
249 249  
250 250  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.
251 251  
252 -2.  In firmware version v1.5, Roll & Pitch is disabled by default.
307 +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:
253 253  
254 -3.  When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
255 255  
256 -
257 257  [[image:1664502116362-706.png]]
258 258  
259 259  
313 +3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
260 260  
261 -4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
262 -
263 263  [[image:1664502166010-515.png]]
264 264  
265 265  
... ... @@ -269,12 +269,13 @@
269 269  Example:  0x4B & 0x40 >> 6 = 0x01
270 270  
271 271  
324 +
272 272  ==== (% style="color:blue" %)**BAT:**(%%) ====
273 273  
274 274  Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
275 275  
276 276  (((
277 -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: \
330 +The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
278 278  )))
279 279  
280 280  * > 4.0v :  80% ~~ 100%
... ... @@ -286,7 +286,6 @@
286 286  
287 287  ==== (% style="color:blue" %)**LON:**(%%) ====
288 288  
289 -
290 290  Enable/Disable LED activity for uplink
291 291  
292 292  (((
... ... @@ -309,15 +309,51 @@
309 309  
310 310  
311 311  
312 -=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
364 +=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
313 313  
314 314  
367 +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)
315 315  
316 -=== 2.3.4 BLE positioning Payload(Fport2) ===
317 317  
370 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
371 +|=(% scope="row" style="width: 50px;" %)(((
372 +**Size(bytes)**
373 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
374 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
375 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
376 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
318 318  
319 -Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
378 +(% class="wikigeneratedid" %)
379 +[[image:1665301687277-443.png]]
320 320  
381 +
382 +
383 +=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
384 +
385 +
386 +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.
387 +
388 +
389 +(% style="color:red" %)**Note for this mode:**
390 +
391 +* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
392 +* 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.
393 +
394 +The payload is 15 bytes, as below.
395 +
396 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
397 +|=(% scope="row" %)(((
398 +**Size(bytes)**
399 +)))|4|4|2|1|1|1|1|1
400 +|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
401 +
402 +[[image:image-20221009160309-2.png]]
403 +
404 +
405 +
406 +=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
407 +
408 +
321 321  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
322 322  |=(% scope="row" style="width: 60px;" %)(((
323 323  **Size(bytes)**
... ... @@ -346,9 +346,10 @@
346 346  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
347 347  
348 348  
349 -=== 2.3.5 Add Payload format in TTN V3 ===
350 350  
438 +=== 2.4.6  Add Payload format in TTN V3 ===
351 351  
440 +
352 352  In TTN V3, use can add a custom payload so it shows friendly.
353 353  
354 354  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
... ... @@ -366,7 +366,7 @@
366 366  
367 367  
368 368  
369 -== 2.4 Integrate with Datacake ==
458 +== 2.5 Integrate with Datacake ==
370 370  
371 371  
372 372  (((
... ... @@ -382,7 +382,7 @@
382 382  
383 383  
384 384  
385 -== 2.5 Integrate with Tago ==
474 +== 2.6 Integrate with Tago ==
386 386  
387 387  
388 388  (((
... ... @@ -398,9 +398,24 @@
398 398  
399 399  
400 400  
401 -== 2.6 Alarm Mode ==
490 +== 2.7  Datalog Feature ==
402 402  
403 403  
493 +total 273 entries,by default disable
494 +
495 +
496 +Example use case.
497 +
498 +[[image:image-20221009234703-2.png]]
499 +
500 +
501 +[[image:image-20221009234629-1.png||height="441" width="652"]]
502 +
503 +
504 +
505 +== 2.8 Alarm Mode ==
506 +
507 +
404 404  (((
405 405  User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
406 406  )))
... ... @@ -424,13 +424,16 @@
424 424  
425 425  
426 426  
427 -== 2.7 Sports Mode ==
531 +== 2.9 Transport Mode ==
428 428  
429 429  
534 +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.
430 430  
431 -== 2.8 LED Status ==
432 432  
433 433  
538 +== 2.10 LED Status ==
539 +
540 +
434 434  (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
435 435  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
436 436  |(% style="width:157px" %)**Power On**|(% style="width:271px" %)(% style="color:blue" %)**BLUE, **(% style="color:red" %)**RED , **(% style="color:green" %)**Green** flash once|(% style="width:202px" %)N/A
... ... @@ -446,9 +446,10 @@
446 446  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
447 447  
448 448  
449 -== 2.9 Button Function ==
450 450  
557 +== 2.11 Button Function ==
451 451  
559 +
452 452  (% style="color:blue" %)**RESET button:**
453 453  
454 454  [[image:1664502835802-546.png]]
... ... @@ -468,9 +468,10 @@
468 468  |(% 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.
469 469  
470 470  
471 -== 2.10 USB Port Function ==
472 472  
580 +== 2.12 USB Port Function ==
473 473  
582 +
474 474  The USB interface of TrackerD has below functions:
475 475  
476 476  * Power on the device
... ... @@ -479,6 +479,7 @@
479 479  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
480 480  
481 481  
591 +
482 482  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
483 483  
484 484  
... ... @@ -551,16 +551,16 @@
551 551  
552 552  
553 553  
554 -=== 3.2.3 Set Sports Mode Packet transmission interval ===
664 +=== 3.2.3 Set Transport Mode Packet transmission interval ===
555 555  
556 556  
557 -Set sports packet transmit interval
667 +Set Transport Mode packet transmit interval
558 558  
559 559  * (% style="color:blue" %)**AT Command:**
560 560  
561 561  (% style="color:#037691" %)**AT+MTDC=xx. **
562 562  
563 -Example:  AT+MTDC=300000  **~-~->    ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
673 +Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
564 564  
565 565  
566 566  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
... ... @@ -600,16 +600,16 @@
600 600  
601 601  
602 602  
603 -=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
713 +=== 3.2.6 Disable/Enable Transport Mode ===
604 604  
605 605  
606 -User can use this feature to check and set thread hole of movement detect
716 +Users can use this feature to enable/disable Transport Mode.
607 607  
608 608  * (% style="color:blue" %)**AT Command:**
609 609  
610 610  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
611 611  
612 -Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
722 +Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
613 613  
614 614  
615 615  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
... ... @@ -621,23 +621,30 @@
621 621  === 3.2.7 Set Positioning Mode ===
622 622  
623 623  
624 -SMOD define the how TrackerD scan and uplink date.
734 +SMOD define the how TrackerD scan and uplink data:
625 625  
626 -GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
627 627  
628 -BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
737 +* (% style="color:blue" %)**AT Command:**
629 629  
630 -GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
739 +(% style="color:#037691" %)**AT+SMOD=aa,bb**
631 631  
632 -运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
741 +(% style="color:#037691" %)** aa:**
633 633  
743 +* (% style="color:#037691" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
744 +* (% style="color:#037691" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
745 +* (% style="color:#037691" %)**3: GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning
634 634  
747 +(% style="color:#037691" %)**bb:**
635 635  
636 -* (% style="color:blue" %)**AT Command:**
749 +(% style="color:#037691" %)** if aa = 1: **
637 637  
638 -(% style="color:#037691" %)**AT+SMOD=xx. **
751 +* (% style="color:#037691" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
752 +* (% style="color:#037691" %)**1 :**(%%)  GPS +BAT State
639 639  
754 +(% style="color:#037691" %)** if aa = 2: **
640 640  
756 +* (% style="color:#037691" %)**3 :  **(%%)(iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
757 +
641 641   **Example:**
642 642  
643 643   AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
... ... @@ -644,7 +644,7 @@
644 644  
645 645   AT+ SMOD =1,1    **~-~->**  GPS +BAT State
646 646  
647 - AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
764 + AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
648 648  
649 649  
650 650  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
... ... @@ -675,7 +675,7 @@
675 675  
676 676  
677 677  
678 -=== 3.3.9 Set PDOP value for GPS fix accuracy ===
795 +=== 3.2.9 Set PDOP value for GPS fix accuracy ===
679 679  
680 680  
681 681  PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.
... ... @@ -798,6 +798,7 @@
798 798  [[image:1664503635019-941.png]]
799 799  
800 800  
918 +
801 801  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
802 802  
803 803  [[image:1664503715811-892.png]]
... ... @@ -880,6 +880,7 @@
880 880  * (% style="color:red" %)**US915**(%%): Default frequency band US915
881 881  
882 882  
1001 +
883 883  = 9.  Packing Info =
884 884  
885 885  
1665301570342-765.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.6 KB
Content
1665301636888-168.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +36.6 KB
Content
1665301687277-443.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.6 KB
Content
1665301786397-168.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.6 KB
Content
image-20221009160220-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +46.4 KB
Content
image-20221009160309-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +57.2 KB
Content
image-20221009234629-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +222.9 KB
Content
image-20221009234703-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +136.4 KB
Content