Last modified by Xiaoling on 2025/04/27 16:48

From version 51.32
edited by Xiaoling
on 2022/09/30 16:48
Change comment: There is no comment for this version
To version 69.1
edited by Edwin Chen
on 2022/10/09 23:46
Change comment: Uploaded new attachment "image-20221009234629-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -61,13 +61,11 @@
61 61  * EEPROM: 520 KB
62 62  * Clock Speed: 32Mhz
63 63  
64 -
65 65  (% style="color:blue" %)**Common DC Characteristics:**
66 66  
67 67  * Supply Voltage: 5V via USB port or Internal li-on battery
68 68  * Operating Temperature: -40 ~~ 60°C
69 69  
70 -
71 71  (% style="color:blue" %)**LoRa Spec:**
72 72  
73 73  * Frequency Range,
... ... @@ -89,12 +89,10 @@
89 89  * Packet engine up to 256 bytes with CRC.
90 90  * LoRaWAN 1.0.3 Specification
91 91  
92 -
93 93  (% style="color:blue" %)**Battery:**
94 94  
95 95  * 1000mA Li-on Battery power (for model TrackerD)
96 96  
97 -
98 98  (% style="color:blue" %)**Power Consumption**
99 99  
100 100  * Sleeping Mode: 200uA
... ... @@ -193,42 +193,93 @@
193 193  (% 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.
194 194  
195 195  
196 -(% style="color:blue" %)**Positioning Mode(SMOD):**
197 197  
198 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get GPS location info.
199 -* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
200 -* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.
193 +== 2.3  Positioning Mode(SMOD) ==
201 201  
202 -User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
203 203  
196 +Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
204 204  
198 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
199 +* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
200 +* (% 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.
205 205  
206 -== 2.3 Uplink Payload ==
202 +Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
207 207  
208 208  
209 -=== 2.3.1 Uplink FPORT~=5, Device Status ===
210 210  
206 +== 2.4  Uplink Payload ==
211 211  
212 212  
213 -=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
209 +=== 2.4.1 Uplink FPORT~=5, Device Status ===
214 214  
215 215  
216 -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. )
212 +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.
217 217  
218 218  
215 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
216 +|=(% 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
217 +|=(% 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
218 +
219 +[[image:1665301570342-765.png]]
220 +
221 +
222 +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"]]
223 +
224 +**Sensor Model**: For TrackerD, this value is 0x13.
225 +
226 +**Firmware Version**: 0x0100, Means: v1.0.0 version.
227 +
228 +**Frequency Band**:
229 +
230 +*0x01: EU868
231 +
232 +*0x02: US915
233 +
234 +*0x03: IN865
235 +
236 +*0x04: AU915
237 +
238 +*0x05: KZ865
239 +
240 +*0x06: RU864
241 +
242 +*0x07: AS923
243 +
244 +*0x08: AS923-1
245 +
246 +*0x09: AS923-2
247 +
248 +*0x0a: AS923-3
249 +
250 +**Sub-Band**: value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
251 +
252 +**BAT**: shows the battery voltage for TrackerD.
253 +
254 +Ex1: 0x0B3A = 2874mV
255 +
256 +Use can also get the Device Status uplink through the downlink command:
257 +
258 +
259 +
260 +=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
261 +
262 +
263 +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.
264 +
265 +
219 219  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
220 220  |=(% scope="row" style="width: 50px;" %)(((
221 221  **Size(bytes)**
222 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
223 -2(optional)
269 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
270 +2
224 224  )))|(% style="width:87px" %)(((
225 -2(optional)
272 +2
226 226  )))
227 227  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
228 228  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
229 -)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
276 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
230 230  
231 -[[image:1664501958445-288.png]]
278 +[[image:1665301636888-168.png]]
232 232  
233 233  
234 234  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -237,11 +237,17 @@
237 237  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
238 238  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
239 239  
287 +(% class="wikigeneratedid" %)
288 +==== ====
289 +
290 +(% class="wikigeneratedid" %)
291 +==== ====
292 +
240 240  ==== (% style="color:blue" %)**FLAG:**(%%) ====
241 241  
242 242  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
243 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
244 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 
296 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
297 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
245 245  
246 246  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
247 247  
... ... @@ -257,17 +257,14 @@
257 257  
258 258  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.
259 259  
260 -2.  In firmware version v1.5, Roll & Pitch is disabled by default.
313 +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:
261 261  
262 -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:
263 263  
264 -
265 265  [[image:1664502116362-706.png]]
266 266  
267 267  
319 +3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
268 268  
269 -4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
270 -
271 271  [[image:1664502166010-515.png]]
272 272  
273 273  
... ... @@ -277,12 +277,13 @@
277 277  Example:  0x4B & 0x40 >> 6 = 0x01
278 278  
279 279  
330 +
280 280  ==== (% style="color:blue" %)**BAT:**(%%) ====
281 281  
282 282  Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
283 283  
284 284  (((
285 -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: \
336 +The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
286 286  )))
287 287  
288 288  * > 4.0v :  80% ~~ 100%
... ... @@ -295,7 +295,6 @@
295 295  
296 296  ==== (% style="color:blue" %)**LON:**(%%) ====
297 297  
298 -
299 299  Enable/Disable LED activity for uplink
300 300  
301 301  (((
... ... @@ -318,15 +318,51 @@
318 318  
319 319  
320 320  
321 -=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
371 +=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
322 322  
323 323  
374 +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)
324 324  
325 -=== 2.3.4 BLE positioning Payload(Fport2) ===
326 326  
377 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
378 +|=(% scope="row" style="width: 50px;" %)(((
379 +**Size(bytes)**
380 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
381 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
382 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
383 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
327 327  
328 -Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
385 +(% class="wikigeneratedid" %)
386 +[[image:1665301687277-443.png]]
329 329  
388 +
389 +
390 +=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
391 +
392 +
393 +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.
394 +
395 +
396 +(% style="color:red" %)**Note for this mode:**
397 +
398 +* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
399 +* 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.
400 +
401 +The payload is 15 bytes, as below.
402 +
403 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
404 +|=(% scope="row" %)(((
405 +**Size(bytes)**
406 +)))|4|4|2|1|1|1|1|1
407 +|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
408 +
409 +[[image:image-20221009160309-2.png]]
410 +
411 +
412 +
413 +=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
414 +
415 +
330 330  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
331 331  |=(% scope="row" style="width: 60px;" %)(((
332 332  **Size(bytes)**
... ... @@ -356,9 +356,10 @@
356 356  
357 357  
358 358  
359 -=== 2.3.5 Add Payload format in TTN V3 ===
360 360  
446 +=== 2.4.6  Add Payload format in TTN V3 ===
361 361  
448 +
362 362  In TTN V3, use can add a custom payload so it shows friendly.
363 363  
364 364  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
... ... @@ -376,7 +376,7 @@
376 376  
377 377  
378 378  
379 -== 2.4 Integrate with Datacake ==
466 +== 2.5 Integrate with Datacake ==
380 380  
381 381  
382 382  (((
... ... @@ -392,7 +392,7 @@
392 392  
393 393  
394 394  
395 -== 2.5 Integrate with Tago ==
482 +== 2.6 Integrate with Tago ==
396 396  
397 397  
398 398  (((
... ... @@ -408,9 +408,16 @@
408 408  
409 409  
410 410  
411 -== 2.6 Alarm Mode ==
498 +== 2. Datalog Feature ==
412 412  
413 413  
501 +total 273 entries,by default disable
502 +
503 +
504 +
505 +== 2.8 Alarm Mode ==
506 +
507 +
414 414  (((
415 415  User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
416 416  )))
... ... @@ -434,13 +434,16 @@
434 434  
435 435  
436 436  
437 -== 2.7 Sports Mode ==
531 +== 2.9 Transport Mode ==
438 438  
439 439  
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.
440 440  
441 -== 2.8 LED Status ==
442 442  
443 443  
538 +== 2.10 LED Status ==
539 +
540 +
444 444  (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
445 445  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
446 446  |(% 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
... ... @@ -457,9 +457,10 @@
457 457  
458 458  
459 459  
460 -== 2.9 Button Function ==
461 461  
558 +== 2.11 Button Function ==
462 462  
560 +
463 463  (% style="color:blue" %)**RESET button:**
464 464  
465 465  [[image:1664502835802-546.png]]
... ... @@ -480,9 +480,10 @@
480 480  
481 481  
482 482  
483 -== 2.10 USB Port Function ==
484 484  
582 +== 2.12 USB Port Function ==
485 485  
584 +
486 486  The USB interface of TrackerD has below functions:
487 487  
488 488  * Power on the device
... ... @@ -492,6 +492,7 @@
492 492  
493 493  
494 494  
594 +
495 495  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
496 496  
497 497  
... ... @@ -564,16 +564,16 @@
564 564  
565 565  
566 566  
567 -=== 3.2.3 Set Sports Mode Packet transmission interval ===
667 +=== 3.2.3 Set Transport Mode Packet transmission interval ===
568 568  
569 569  
570 -Set sports packet transmit interval
670 +Set Transport Mode packet transmit interval
571 571  
572 572  * (% style="color:blue" %)**AT Command:**
573 573  
574 574  (% style="color:#037691" %)**AT+MTDC=xx. **
575 575  
576 -Example:  AT+MTDC=300000  **~-~->    ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
676 +Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
577 577  
578 578  
579 579  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
... ... @@ -613,16 +613,16 @@
613 613  
614 614  
615 615  
616 -=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
716 +=== 3.2.6 Disable/Enable Transport Mode ===
617 617  
618 618  
619 -User can use this feature to check and set thread hole of movement detect
719 +Users can use this feature to enable/disable Transport Mode.
620 620  
621 621  * (% style="color:blue" %)**AT Command:**
622 622  
623 623  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
624 624  
625 -Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
725 +Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
626 626  
627 627  
628 628  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
... ... @@ -634,23 +634,30 @@
634 634  === 3.2.7 Set Positioning Mode ===
635 635  
636 636  
637 -SMOD define the how TrackerD scan and uplink date.
737 +SMOD define the how TrackerD scan and uplink data:
638 638  
639 -GPS室外定位模式:  设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。
640 640  
641 -BLE室内定位模式:  设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。
740 +* (% style="color:blue" %)**AT Command:**
642 642  
643 -GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。
742 +(% style="color:#037691" %)**AT+SMOD=aa,bb**
644 644  
645 -运动模式:  设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。
744 +(% style="color:#037691" %)** aa:**
646 646  
746 +* (% style="color:#037691" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
747 +* (% style="color:#037691" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
748 +* (% 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
647 647  
750 +(% style="color:#037691" %)**bb:**
648 648  
649 -* (% style="color:blue" %)**AT Command:**
752 +(% style="color:#037691" %)** if aa = 1: **
650 650  
651 -(% style="color:#037691" %)**AT+SMOD=xx. **
754 +* (% style="color:#037691" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
755 +* (% style="color:#037691" %)**1 :**(%%)  GPS +BAT State
652 652  
757 +(% style="color:#037691" %)** if aa = 2: **
653 653  
759 +* (% style="color:#037691" %)**3 :  **(%%)(iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
760 +
654 654   **Example:**
655 655  
656 656   AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
... ... @@ -657,7 +657,7 @@
657 657  
658 658   AT+ SMOD =1,1    **~-~->**  GPS +BAT State
659 659  
660 - AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
767 + AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
661 661  
662 662  
663 663  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
... ... @@ -688,7 +688,7 @@
688 688  
689 689  
690 690  
691 -=== 3.3.9 Set PDOP value for GPS fix accuracy ===
798 +=== 3.2.9 Set PDOP value for GPS fix accuracy ===
692 692  
693 693  
694 694  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.
... ... @@ -811,6 +811,7 @@
811 811  [[image:1664503635019-941.png]]
812 812  
813 813  
921 +
814 814  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
815 815  
816 816  [[image:1664503715811-892.png]]
... ... @@ -895,6 +895,7 @@
895 895  
896 896  
897 897  
1006 +
898 898  = 9.  Packing Info =
899 899  
900 900  
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-20221006181316-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +17.7 KB
Content
image-20221006181357-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +88.0 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