Skip to Content
Last modified by Mengting Qiu on 2023/12/14 11:15
From version 85.1
edited by Saxer Lin
on 2023/07/15 11:46
Change comment: There is no comment for this version
To version 93.1
edited by Saxer Lin
on 2023/08/05 10:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -130,7 +130,7 @@
130 130  
131 131  
132 132  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
133 -|=(% style="width: 167px;background-color:#D9E2F3;color:#0070C0" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 225px;background-color:#D9E2F3;color:#0070C0" %)**Action**
133 +|=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 225px;background-color:#4F81BD;color:white" %)**Action**
134 134  |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
135 135  If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.
136 136  Meanwhile, BLE module will be active and user can connect via BLE to configure device.
... ... @@ -242,27 +242,29 @@
242 242  
243 243  == 2.3 ​Uplink Payload ==
244 244  
245 -
246 246  === 2.3.1 Device Status, FPORT~=5 ===
247 247  
247 +
248 248  Users can use the downlink command(**0x26 01**) to ask LDS12-LB to send device configure detail, include device configure status. LDS12-LB will uplink a payload via FPort=5 to server.
249 249  
250 250  The Payload format is as below.
251 251  
252 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:529px" %)
253 -|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)(((
252 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
253 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
254 254  **Size(bytes)**
255 -)))|=(% style="width: 110px; background-color: rgb(79, 129, 189); color: white;" %)**1**|=(% style="width: 48px; background-color: rgb(79, 129, 189); color: white;" %)**2**|=(% style="background-color: rgb(79, 129, 189); color: white; width: 94px;" %)**1**|=(% style="background-color: rgb(79, 129, 189); color: white; width: 91px;" %)**1**|=(% style="background-color: rgb(79, 129, 189); color: white; width: 60px;" %)**2**
255 +)))|=(% style="width: 100px; background-color: #4F81BD;color:white;" %)**1**|=(% style="width: 100px; background-color: #4F81BD;color:white;" %)**2**|=(% style="background-color: #4F81BD;color:white; width: 100px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 100px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 50px;" %)**2**
256 256  |(% style="width:62.5px" %)Value|(% style="width:110px" %)Sensor Model|(% style="width:48px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:91px" %)Sub-band|(% style="width:60px" %)BAT
257 257  
258 258  Example parse in TTNv3
259 259  
260 -**Sensor Model**: For LDS12-LB, this value is 0x24
260 +[[image:image-20230805103904-1.png||height="131" width="711"]]
261 261  
262 -**Firmware Version**: 0x0100, Means: v1.0.0 version
262 +(% style="color:blue" %)**Sensor Model**(%%): For LDS12-LB, this value is 0x24
263 263  
264 -**Frequency Band**:
264 +(% style="color:blue" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
265 265  
266 +(% style="color:blue" %)**Frequency Band**:
267 +
266 266  0x01: EU868
267 267  
268 268  0x02: US915
... ... @@ -291,7 +291,7 @@
291 291  
292 292  0x0e: MA869
293 293  
294 -**Sub-Band**:
296 +(% style="color:blue" %)**Sub-Band**:
295 295  
296 296  AU915 and US915:value 0x00 ~~ 0x08
297 297  
... ... @@ -299,7 +299,7 @@
299 299  
300 300  Other Bands: Always 0x00
301 301  
302 -**Battery Info**:
304 +(% style="color:blue" %)**Battery Info**:
303 303  
304 304  Check the battery voltage.
305 305  
... ... @@ -308,36 +308,33 @@
308 308  Ex2: 0x0B49 = 2889mV
309 309  
310 310  
311 -=== 2.3.2 Device Status, FPORT~=5 ===
313 +=== 2.3.2 Uplink Payload, FPORT~=2 ===
312 312  
313 -(((
314 -LDS12-LB will uplink payload via LoRaWAN with below payload format: 
315 -)))
316 316  
317 317  (((
318 -Uplink payload includes in total 11 bytes.
319 -)))
317 +LDS12-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS12-LB will:
320 320  
321 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:670px" %)
322 -|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)(((
323 -**Size(bytes)**
324 -)))|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color: rgb(79, 129, 189); color: white; width: 122px;" %)**1**|=(% style="background-color: rgb(79, 129, 189); color: white; width: 54px;" %)**1**|=(% style="background-color: rgb(79, 129, 189); color: white; width: 96px;" %)**1**
325 -|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1BatteryInfo"]]|(% style="width:62.5px" %)(((
326 -[[Temperature DS18B20>>||anchor="H2.3.2DS18B20Temperaturesensor"]]
327 -)))|[[Distance>>||anchor="H2.3.3Distance"]]|[[Distance signal strength>>||anchor="H2.3.4Distancesignalstrength"]]|(% style="width:122px" %)(((
328 -[[Interrupt flag>>||anchor="H2.3.5InterruptPin"]]
319 +periodically send this uplink every 20 minutes, this interval [[can be changed>>https://111]].
329 329  
330 -&
321 +Uplink Payload totals 11 bytes.
322 +)))
331 331  
332 -[[Interrupt_level>>||anchor="H2.3.5InterruptPin"]]
333 -)))|(% style="width:54px" %)[[LiDAR temp>>||anchor="H2.3.6LiDARtemp"]]|(% style="width:96px" %)(((
334 -[[Message Type>>||anchor="H2.3.7MessageType"]]
324 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
325 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
326 +**Size(bytes)**
327 +)))|=(% style="width: 30px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 70px;background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white; width: 80px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 70px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 70px;" %)**1**
328 +|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)[[BAT>>||anchor="HBatteryInfo"]]|(% style="width:62.5px" %)(((
329 +[[Temperature DS18B20>>||anchor="HDS18B20Temperaturesensor"]]
330 +)))|[[Distance>>||anchor="HDistance"]]|[[Distance signal strength>>||anchor="HDistancesignalstrength"]]|(% style="width:122px" %)(((
331 +[[Interrupt flag & Interrupt_level>>||anchor="HInterruptPin26A0InterruptLevel"]]
332 +)))|(% style="width:54px" %)[[LiDAR temp>>||anchor="HLiDARtemp"]]|(% style="width:96px" %)(((
333 +[[Message Type>>||anchor="HMessageType"]]
335 335  )))
336 336  
337 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654833689380-972.png?rev=1.1||alt="1654833689380-972.png"]]
336 +[[image:image-20230805104104-2.png||height="136" width="754"]]
338 338  
339 339  
340 -=== 2.3.2.a Battery Info ===
339 +==== (% style="color:blue" %)**Battery Info**(%%) ====
341 341  
342 342  
343 343  Check the battery voltage for LDS12-LB.
... ... @@ -347,7 +347,7 @@
347 347  Ex2: 0x0B49 = 2889mV
348 348  
349 349  
350 -=== 2.3.2.b DS18B20 Temperature sensor ===
349 +==== (% style="color:blue" %)**DS18B20 Temperature sensor**(%%) ====
351 351  
352 352  
353 353  This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
... ... @@ -360,7 +360,7 @@
360 360  If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
361 361  
362 362  
363 -=== 2.3.2.c Distance ===
362 +==== (% style="color:blue" %)**Distance**(%%) ====
364 364  
365 365  
366 366  Represents the distance value of the measurement output, the default unit is cm, and the value range parsed as a decimal number is 0-1200. In actual use, when the signal strength value Strength.
... ... @@ -371,7 +371,7 @@
371 371  If the data you get from the register is 0x0B 0xEA, the distance between the sensor and the measured object is 0BEA(H) = 3050 (D)/10 = 305cm.
372 372  
373 373  
374 -=== 2.3.2.d Distance signal strength ===
373 +==== (% style="color:blue" %)**Distance signal strength**(%%) ====
375 375  
376 376  
377 377  Refers to the signal strength, the default output value will be between 0-65535. When the distance measurement gear is fixed, the farther the distance measurement is, the lower the signal strength; the lower the target reflectivity, the lower the signal strength. When Strength is greater than 100 and not equal to 65535, the measured value of Dist is considered credible.
... ... @@ -384,7 +384,7 @@
384 384  Customers can judge whether they need to adjust the environment based on the signal strength.
385 385  
386 386  
387 -=== 2.3.2.e Interrupt Pin & Interrupt Level ===
386 +==== (% style="color:blue" %)**Interrupt Pin & Interrupt Level**(%%) ====
388 388  
389 389  
390 390  This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.3.2SetInterruptMode"]] for the hardware and software set up.
... ... @@ -398,7 +398,7 @@
398 398  0x01: Interrupt Uplink Packet.
399 399  
400 400  
401 -=== 2.3.2.f LiDAR temp ===
400 +==== (% style="color:blue" %)**LiDAR temp**(%%) ====
402 402  
403 403  
404 404  Characterize the internal temperature value of the sensor.
... ... @@ -408,7 +408,7 @@
408 408  If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
409 409  
410 410  
411 -=== 2.3.2.g Message Type ===
410 +==== (% style="color:blue" %)**Message Type**(%%) ====
412 412  
413 413  
414 414  (((
... ... @@ -425,7 +425,7 @@
425 425  |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.ConfigureLDS12-LB"]]
426 426  
427 427  
428 -=== 2.3.8 Decode payload in The Things Network ===
427 +=== 2.3.3 Decode payload in The Things Network ===
429 429  
430 430  
431 431  While using TTN network, you can add the payload format to decode the payload.
... ... @@ -442,15 +442,9 @@
442 442  )))
443 443  
444 444  
445 -== 2.4 Uplink Interval ==
444 +== 2.4 ​Show Data in DataCake IoT Server ==
446 446  
447 447  
448 -The LDS12-LB by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>||anchor="H3.3.1SetTransmitIntervalTime"]]
449 -
450 -
451 -== 2.5 ​Show Data in DataCake IoT Server ==
452 -
453 -
454 454  (((
455 455  [[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps:
456 456  )))
... ... @@ -483,13 +483,13 @@
483 483  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS75%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/image-20220610165129-11.png?width=1088&height=595&rev=1.1||alt="image-20220610165129-11.png"]]
484 484  
485 485  
486 -== 2.6 Datalog Feature ==
479 +== 2.5 Datalog Feature ==
487 487  
488 488  
489 489  Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LDS12-LB will store the reading for future retrieving purposes.
490 490  
491 491  
492 -=== 2.6.1 Ways to get datalog via LoRaWAN ===
485 +=== 2.5.1 Ways to get datalog via LoRaWAN ===
493 493  
494 494  
495 495  Set PNACKMD=1, LDS12-LB will wait for ACK for every uplink, when there is no LoRaWAN network,LDS12-LB 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.
... ... @@ -506,7 +506,7 @@
506 506  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220703111700-2.png?width=1119&height=381&rev=1.1||alt="图片-20220703111700-2.png" height="381" width="1119"]]
507 507  
508 508  
509 -=== 2.6.2 Unix TimeStamp ===
502 +=== 2.5.2 Unix TimeStamp ===
510 510  
511 511  
512 512  LDS12-LB uses Unix TimeStamp format based on
... ... @@ -523,7 +523,7 @@
523 523  So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
524 524  
525 525  
526 -=== 2.6.3 Set Device Time ===
519 +=== 2.5.3 Set Device Time ===
527 527  
528 528  
529 529  User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
... ... @@ -533,13 +533,13 @@
533 533  (% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.**
534 534  
535 535  
536 -=== 2.6.4 Poll sensor value ===
529 +=== 2.5.4 Poll sensor value ===
537 537  
538 538  
539 539  Users can poll sensor values based on timestamps. Below is the downlink command.
540 540  
541 541  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:425.818px" %)
542 -|(% colspan="4" style="background-color:#d9e2f3; color:#0070c0; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
535 +|(% colspan="4" style="background-color:#4f81bd; color:white; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
543 543  |(% style="width:58px" %)**1byte**|(% style="width:127px" %)**4bytes**|(% style="width:124px" %)**4bytes**|(% style="width:114px" %)**1byte**
544 544  |(% style="width:58px" %)31|(% style="width:127px" %)Timestamp start|(% style="width:124px" %)Timestamp end|(% style="width:114px" %)Uplink Interval
545 545  
... ... @@ -560,7 +560,7 @@
560 560  )))
561 561  
562 562  
563 -== 2.7 Frequency Plans ==
556 +== 2.6 Frequency Plans ==
564 564  
565 565  
566 566  The LDS12-LB uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
... ... @@ -568,9 +568,9 @@
568 568  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]]
569 569  
570 570  
571 -== 2.8 LiDAR ToF Measurement ==
564 +== 2.7 LiDAR ToF Measurement ==
572 572  
573 -=== 2.8.1 Principle of Distance Measurement ===
566 +=== 2.7.1 Principle of Distance Measurement ===
574 574  
575 575  
576 576  The LiDAR probe is based on TOF, namely, Time of Flight principle. To be specific, the product emits modulation wave of near infrared ray on a periodic basis, which will be reflected after contacting object. The product obtains the time of flight by measuring round-trip phase difference and then calculates relative range between the product and the detection object, as shown below.
... ... @@ -578,7 +578,7 @@
578 578  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831757579-263.png?rev=1.1||alt="1654831757579-263.png"]]
579 579  
580 580  
581 -=== 2.8.2 Distance Measurement Characteristics ===
574 +=== 2.7.2 Distance Measurement Characteristics ===
582 582  
583 583  
584 584  With optimization of light path and algorithm, The LiDAR probe has minimized influence from external environment on distance measurement performance. Despite that, the range of distance measurement may still be affected by the environment illumination intensity and the reflectivity of detection object. As shown in below:
... ... @@ -616,7 +616,7 @@
616 616  )))
617 617  
618 618  
619 -=== 2.8.3 Notice of usage ===
612 +=== 2.7.3 Notice of usage ===
620 620  
621 621  
622 622  Possible invalid /wrong reading for LiDAR ToF tech:
... ... @@ -627,7 +627,7 @@
627 627  * The sensor window is made by Acrylic. Don't touch it with alcohol material. This will destroy the sensor window.
628 628  
629 629  
630 -=== 2.8.4  Reflectivity of different objects ===
623 +=== 2.7.4  Reflectivity of different objects ===
631 631  
632 632  
633 633  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %)
... ... @@ -768,83 +768,34 @@
768 768  * Example 2: Downlink Payload: 06000003  ~/~/  Set the interrupt mode to rising edge trigger
769 769  
770 770  
771 -=== 3.3.3 Get Firmware Version Info ===
764 +=== 3.3.3  Set Power Output Duration ===
772 772  
766 +Control the output duration 3V3 . Before each sampling, device will
773 773  
774 -Feature: use downlink to get firmware version.
768 +~1. first enable the power output to external sensor,
775 775  
776 -(% style="color:blue" %)**Downlink Command: 0x26**
770 +2. keep it on as per duration, read sensor value and construct uplink payload
777 777  
778 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:492px" %)
779 -|(% style="background-color:#4f81bd; color:white; width:191px" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white; width:57px" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:91px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:153px" %)**Downlink payload size(bytes)**
780 -|(% style="width:191px" %)Get Firmware Version Info|(% style="width:57px" %)Any|(% style="width:91px" %)26|(% style="width:151px" %)2
772 +3. final, close the power output.
781 781  
782 -* Reply to the confirmation package: 26 01
783 -* Reply to non-confirmed packet: 26 00
774 +(% style="color:blue" %)**AT Command: AT+3V3T**
784 784  
785 -Device will send an uplink after got this downlink command. With below payload:
776 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
777 +|=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 197px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Response**
778 +|(% style="width:154px" %)AT+3V3T=?|(% style="width:196px" %)Show 3V3 open time.|(% style="width:157px" %)0 (default)
779 +OK
780 +|(% style="width:154px" %)AT+3V3T=1000|(% style="width:196px" %)Close after a delay of 1000 milliseconds.|(% style="width:157px" %)OK
781 +|(% style="width:154px" %)AT+3V3T=0|(% style="width:196px" %)Always turn on the power supply of 3V3 pin.|(% style="width:157px" %)OK
786 786  
787 -Configures info payload:
783 +(% style="color:blue" %)**Downlink Command: 0x07**(%%)
784 +Format: Command Code (0x07) followed by 3 bytes.
788 788  
789 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
790 -|=(% style="background-color:#4F81BD;color:white" %)(((
791 -**Size(bytes)**
792 -)))|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**5**|=(% style="background-color:#4F81BD;color:white" %)**1**
793 -|**Value**|Software Type|(((
794 -Frequency Band
795 -)))|Sub-band|(((
796 -Firmware Version
797 -)))|Sensor Type|Reserve|(((
798 -[[Message Type>>||anchor="H2.3.7MessageType"]]
799 -Always 0x02
800 -)))
786 +The first byte is 01,the second and third bytes are the time to turn on.
801 801  
802 -(% style="color:#037691" %)**Software Type**(%%): Always 0x03 for LLDS12
788 +* Example 1: Downlink Payload: 07 01 00 00  **~-~-->**  AT+3V3T=0
789 +* Example 2: Downlink Payload: 07 01 01 F4  **~-~-->**  AT+3V3T=500
803 803  
804 -(% style="color:#037691" %)**Frequency Band**:
805 805  
806 -0x01: EU868
807 -
808 -0x02: US915
809 -
810 -0x03: IN865
811 -
812 -0x04: AU915
813 -
814 -0x05: KZ865
815 -
816 -0x06: RU864
817 -
818 -0x07: AS923
819 -
820 -0x08: AS923-1
821 -
822 -0x09: AS923-2
823 -
824 -0xa0: AS923-3
825 -
826 -
827 -(% style="color:#037691" %)**Sub-Band**(%%): value 0x00 ~~ 0x08
828 -
829 -(% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
830 -
831 -(% style="color:#037691" %)**Sensor Type**:
832 -
833 -0x01: LSE01
834 -
835 -0x02: LDDS75
836 -
837 -0x03: LDDS20
838 -
839 -0x04: LLMS01
840 -
841 -0x05: LSPH01
842 -
843 -0x06: LSNPK01
844 -
845 -0x07: LLDS12
846 -
847 -
848 848  = 4. Battery & Power Consumption =
849 849  
850 850  
image-20230805103904-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Saxer
Size
... ... @@ -1,0 +1,1 @@
1 +46.9 KB
Content
image-20230805104104-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Saxer
Size
... ... @@ -1,0 +1,1 @@
1 +46.3 KB
Content