Skip to Content
Last modified by Karry Zhuang on 2025/07/03 11:59
From version 150.1
edited by Karry Zhuang
on 2024/05/09 18:01
Change comment: There is no comment for this version
To version 151.2
edited by Karry Zhuang
on 2024/05/10 09:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -307,96 +307,12 @@
307 307  
308 308  = (% title="Click and drag to resize" %)3. Get Sensor Data.(%%) =
309 309  
310 -== (% title="Click and drag to resize" %)3.1 Get Digital Reading After Calibration(%%) ==
311 311  
312 -This section shows an example for how to join the [[TheThingsNetwork>>url:https://www.thethingsnetwork.org/]] LoRaWAN IoT server. Usages with other LoRaWAN IoT servers are of similar procedure.
311 +== (% title="Click and drag to resize" %)3.1 Get Image and show in PC(%%) ==
313 313  
314 -
315 -Assume the DLOS8 is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. We need to add the AIS Sensor device in TTN V3 portal. 
316 -
317 -**Step 1**:  Create a device in TTN V3 with the OTAA keys from AIS Sensor.
318 -
319 -Each AIS Sensor is shipped with a sticker with the default DEV EUI as below:
320 -
321 -[[image:image-20240430155056-2.png||height="207" width="450"]]
322 -
323 -Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
324 -
325 -Add APP EUI in the application.
326 -
327 -choose to create the device manually.
328 -
329 -Add APP KEY and DEV EUI
330 -
331 -[[image:image-20240430155117-3.png||height="544" width="563"]]
332 -
333 -[[image:image-20240430154736-1.png||height="414" width="658"]]
334 -
335 -
336 -**Default mode OTAA**
337 -
338 -[[image:image-20240430155302-4.png||height="630" width="453"]]
339 -
340 -**Step 2**:  Use ACT button to activate LHT52 and it will auto join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel.
341 -
342 -=== 3.1.1 Uplink Payload (Fport~=2) ===
343 -
344 -The uplink payload includes totally 14 bytes. Uplink packets use FPORT=2 and (% style="color:#4472c4" %)**every 20 minutes**(%%) send one uplink by default.
345 -
346 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:370px" %)
347 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**Size(bytes)(% style="display:none" %) (%%)**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)2|=(% style="width: 80px;background-color:#4F81BD;color:white" %)4|=(% style="width: 80px;background-color:#4F81BD;color:white" %)4|=(% style="width: 60px;background-color:#4F81BD;color:white" %)4
348 -|(% style="width:99px" %)Value|(% style="width:62px" %)BAT|sysTimeCurrent|Integer|Decimal
349 -
350 -[[image:1714374026505-898.png||height="200" width="736"]]
351 -
352 -Payload Example（FPort=2）：(% style="background-color:yellow" %)**0D 32 66 29 AF E0 00 00 00 02 00 05 E3 B0**
353 -
354 -=== 3.1.2 BAT- Battery information ===
355 -
356 -These two bytes of BAT include the battery state and the actual voltage.
357 -
358 -**Ex**：0x0B32 = 3378mV
359 -
360 -=== 3.1.3 sysTimeCurrent ===
361 -
362 -These four bytes contain the year, month, day, hour, minute, and second of the time.
363 -
364 -AI Sensor use Unix TimeStamp format based on
365 -
366 -[[image:1714374373681-339.png||height="81" width="527"]]
367 -
368 -Users can get this time from the link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
369 -
370 -Below is the converter example
371 -
372 -**Ex**：6629AFE0=2024-04-25 01:20:32
373 -
374 -[[image:1714374389825-148.png||height="313" width="428"]][[image:1714374398047-940.png||height="214" width="508"]]
375 -
376 -So, we can use AT+TIMESTAMP=1714012723 or downlink 6629C233 to set the current time 2024 – April ~-~- 25 Thursday 02:38:41
377 -
378 -=== 3.1.4 Integer ===
379 -
380 -These four bytes display the integers in the digital wheel face
381 -
382 -[[image:1714374445395-196.png]]
383 -
384 -Read table integer：0x00000002=2
385 -
386 -=== 3.1.5 Decimal ===
387 -
388 -These four bytes display decimals on the digital wheel.
389 -
390 -[[image:1714374493101-914.png]]
391 -
392 -Read table decimals：0x005E3B0/1000000= 0.385968
393 -
394 -
395 -== (% title="Click and drag to resize" %)3.2 Get Image and show in PC(%%) ==
396 -
397 397  To get the AIS current image on the PC, you can  connect AIS to your PC with TTL to send commands through the serial port to obtain relevant data packets.
398 398  
399 -=== (% id="cke_bm_3839S" style="display:none" %) (%%)3.2.1 The image date are obtained by serial port ===
315 +=== (% id="cke_bm_3839S" style="display:none" %) (%%)3.1.1 The image date are obtained by serial port ===
400 400  
401 401  Select the corresponding baud rate and serial port number through the serial port tool, select HEX display and HEX send, and continuously receive data from the AIS Sensor
402 402  
... ... @@ -407,7 +407,7 @@
407 407  [[image:1714985711524-251.png||height="140" width="526"]]
408 408  
409 409  
410 -=== 3.2.2 Combined image ===
326 +=== 3.1.2 Combined image ===
411 411  
412 412  Once all the data has been uploaded to the TTN platform, the subsequent step involves concatenating each packet in sequential order and saving it into a new TXT file. It is important to note that the first 8 bytes of each packet should be removed before concatenation.
413 413  
... ... @@ -440,154 +440,4 @@
440 440  === ===
441 441  
442 442  
443 -= 4. Configure AIS Sensor using AT commands =
444 -
445 -== 4.1 Configure Methods ==
446 -
447 -
448 - configure method:
449 -
450 -* AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
451 -* AT Command via UART Connection : See [[UART Connection>>http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]].
452 -* LoRaWAN Downlink.  Instruction for different platforms: See [[IoT LoRaWAN Server>>http://wiki.dragino.com/xwiki/bin/view/Main/]] section.
453 -
454 -== 4.2 General Commands ==
455 -
456 -
457 -These commands are to configure:
458 -
459 -* General system settings like: uplink interval.
460 -* LoRaWAN protocol & radio related command.
461 -
462 -They are same for all Dragino Devices which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki:
463 -
464 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
465 -
466 -== 4.3 Commands special design for AIS Sensor ==
467 -
468 -=== 4.3.1 Change Uplink Interval ===
469 -
470 -
471 -Feature: Change LoRaWAN End Node Transmit Interval.
472 -
473 -
474 -(% style="color:blue" %)**AT Command: AT+TDC**
475 -
476 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:727.222px" %)
477 -|(% style="background-color:#4f81bd; color:white; width:165px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:227px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:329px" %)**Response**
478 -|(% style="width:165px" %)AT+TDC=?|(% style="width:227px" %)Show current transmit Interval|(% style="width:329px" %)30000(((
479 -OK
480 -
481 -the interval is 30000ms = 30s
482 -)))
483 -|(% style="width:165px" %)AT+TDC=60000|(% style="width:227px" %)Set Transmit Interval|(% style="width:329px" %)OK(((
484 -Set transmit interval to 60000ms = 60 seconds
485 -)))
486 -
487 -(((
488 -(% style="color:blue" %)**Downlink Command: 0x01**
489 -
490 -Format: Command Code (0x01) followed by 3 bytes time value.
491 -)))
492 -
493 -(((
494 -If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
495 -)))
496 -
497 -* **Example 1**: Downlink Payload:** 0100001E**  ~/~/ Set Transmit Interval (TDC) = 30 seconds
498 -
499 -* **Example 2**: Downlink Payload:** 0100003C**  ~/~/ Set Transmit Interval (TDC) = 60 seconds
500 -
501 -(% style="display:none" %) (%%)
502 -
503 -== 4.3.2 Request the server to send an ACK ==
504 -
505 -
506 -(% style="color:blue" %)**AT Command: AT+PNACKMD**
507 -
508 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:889px" %)
509 -|(% style="background-color:#4f81bd; color:white; width:160px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:627px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Response**
510 -|(% style="width:160px" %)AT+PNACKMD=1|(% style="width:627px" %)If the node uploads the ACK as confirm, it will request the server to send an ACK. If the server ack is not received, the node will upload the packets that have not received the ACK the next time it receives the ACK|(% style="width:100px" %)1(((
511 -OK
512 -)))
513 -|(% style="width:160px" %)AT+PNACKMD=0|(% style="width:627px" %)off request the server to send an ACK|(% style="width:100px" %)(((
514 -0
515 -OK
516 -)))
517 -
518 -(% style="display:none" %) (%%) (% style="color:blue" %)**Downlink Command: 0x34**
519 -
520 -0X34 01  ~/~/Same As AT+PNACKMD=1
521 -
522 -0x34 00  ~/~/Same As AT+PNACKMD=0
523 -
524 -
525 -=== 4.3.3 Set Interrupt Mode ===
526 -
527 -
528 -Feature, Set Interrupt mode for GPIO_EXIT.
529 -
530 -(% style="color:blue" %)**AT Command: AT+INTMOD1,AT+INTMOD2,AT+INTMOD3**
531 -
532 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
533 -|=(% 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**
534 -|(% style="width:154px" %)AT+INTMOD1=?|(% style="width:196px" %)Show current interrupt mode|(% style="width:157px" %)(((
535 -0
536 -OK
537 -the mode is 0 =Disable Interrupt
538 -)))
539 -|(% style="width:154px" %)AT+INTMOD1=2|(% style="width:196px" %)(((
540 -Set Transmit Interval
541 -0. (Disable Interrupt),
542 -~1. (Trigger by rising and falling edge)
543 -2. (Trigger by falling edge)
544 -3. (Trigger by rising edge)
545 -)))|(% style="width:157px" %)OK
546 -|(% style="width:154px" %)AT+INTMOD2=3|(% style="width:196px" %)Set Transmit Interval
547 -0. (Disable Interrupt),
548 -~1. (Trigger by rising and falling edge)
549 -2. (Trigger by falling edge)
550 -3. (Trigger by rising edge)|(% style="width:157px" %)OK
551 -
552 -(% style="color:blue" %)**Downlink Command: 0x06**
553 -
554 -Format: Command Code (0x06) followed by 3 bytes.
555 -
556 -This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
557 -
558 -* Example 1: Downlink Payload: 06000000  **~-~-->**  AT+INTMOD1=0
559 -* Example 2: Downlink Payload: 06000003  **~-~-->**  AT+INTMOD1=3
560 -* Example 3: Downlink Payload: 06000102  **~-~-->**  AT+INTMOD2=2
561 -
562 -=== ===
563 -
564 -=== 4.3.4 Clock logging (Since firmware version v1.2.1) ===
565 -
566 -
567 -Sometimes when we deploy lots of end nodes in field. We want all sensors sample data at the same time, and upload these data together for analyze. In such case, we can use clock loging feature.
568 -
569 -We can use this command to set the start time of data recording and the time interval to meet the requirements of the specific collection time of data.
570 -
571 -* (% style="color:blue" %)**AT Command:**(%%)** (% style="color:#037691" %)AT+CLOCKLOG=a,b,c,d(%%)**
572 -
573 -(% style="color:#037691" %)**a: **(%%)**0:** Disable Clock logging.  ** 1: **Enable Clock Logging
574 -
575 -(% style="color:#037691" %)**b: **(%%)Specify First sampling start second: range **(0 ~~ 3599, 65535)   ** ~/~/ (% style="color:red" %)**Note:**(%%)** **If parameter b is set to 65535, the log period starts after the node accesses the network and sends packets.
576 -
577 -(% style="color:#037691" %)**c: **(%%)Specify the sampling interval: range **(0 ~~ 255 minutes)**
578 -
579 -(% style="color:#037691" %)**d:**(%%)How many entries should be uplink on every TDC **(max 32)**
580 -
581 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SPH01-NB_NB-IoT_Soil_pH_Sensor_User_Manual/WebHome/image-20240315141254-1.png?rev=1.1||alt="image-20240315141254-1.png"]]
582 -
583 -**Example:**
584 -
585 -**AT+CLOCKLOG=1,65535,1,5**
586 -
587 -After the node sends the first packet, data is recorded to the memory at intervals of 1 minute. For each TDC uplink, the uplink load will include: battery information + the last 5 memory records (payload + timestamp).
588 -
589 -(% class="wikigeneratedid" %)
590 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TS01-NB_NB-IoT_Tilting_Sensor_User_Manual/WebHome/image-20240316163501-1.png?width=1064&height=517&rev=1.1||alt="image-20240316163501-1.png"]]
591 -
592 -(% class="wikigeneratedid" %)
593 -(% style="color:red" %)**Note: Users need to synchronize the server time before configuring this command. If the server time is not synchronized before this command is configured, the command takes effect only after the node is reset.**
359 += =