Skip to Content
Last modified by Karry Zhuang on 2025/07/03 11:59
From version 146.1
edited by Karry Zhuang
on 2024/05/06 17:34
Change comment: There is no comment for this version
To version 142.1
edited by Karry Zhuang
on 2024/04/30 17:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -396,7 +396,7 @@
396 396  
397 397  To get the AIS current image on the PC, you can issue commands through TTN or connect AIS to your PC with TTL to send commands through the serial port to obtain relevant data packets.
398 398  
399 -=== 3.2.1 The image date are obtained by TTN ===
399 +=== 3.2.1 The image packets are obtained by TTN ===
400 400  
401 401  Make sure that node ACK is on: AT+PNACKMD=1 or 34 01
402 402  
... ... @@ -494,144 +494,13 @@
494 494  
495 495  [[image:1714467134950-189.png]]
496 496  
497 -=== 3.2.2 The image date are obtained by serial port ===
497 +=== 3.2.2 Get the current image packet by connecting the AUC USB TTL adapters for AIS Sensors to the AIS Sensor. ===
498 498  
499 499  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
500 500  
501 -[[image:1714985699187-406.png||height="277" width="536"]]
502 502  
503 503  In the serial port to send data C0 5A 00 00 00 00 04, and then send C0 5A 00 00 00 00 09, AIS Sensor will send a real-time image of the data packet, and then stop sending. Start with FFD8 and put it in TXT file
504 504  
505 -[[image:1714985711524-251.png||height="140" width="526"]]
506 506  
507 507  Then follow the instructions in 3.2.1.6 to get the image from AIS Sensor.
508 508  
509 -
510 -= 4. Configure AIS Sensor using AT commands =
511 -
512 -== 4.1 System Management Commands ==
513 -
514 -=== 4.1.1 Change Uplink Interval ===
515 -
516 -
517 -Feature: Change LoRaWAN End Node Transmit Interval.
518 -
519 -
520 -(% style="color:blue" %)**AT Command: AT+TDC**
521 -
522 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:727.222px" %)
523 -|(% 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**
524 -|(% style="width:165px" %)AT+TDC=?|(% style="width:227px" %)Show current transmit Interval|(% style="width:329px" %)30000(((
525 -OK
526 -
527 -the interval is 30000ms = 30s
528 -)))
529 -|(% style="width:165px" %)AT+TDC=60000|(% style="width:227px" %)Set Transmit Interval|(% style="width:329px" %)OK(((
530 -Set transmit interval to 60000ms = 60 seconds
531 -)))
532 -
533 -(((
534 -(% style="color:blue" %)**Downlink Command: 0x01**
535 -
536 -Format: Command Code (0x01) followed by 3 bytes time value.
537 -)))
538 -
539 -(((
540 -If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
541 -)))
542 -
543 -* **Example 1**: Downlink Payload:** 0100001E**  ~/~/ Set Transmit Interval (TDC) = 30 seconds
544 -
545 -* **Example 2**: Downlink Payload:** 0100003C**  ~/~/ Set Transmit Interval (TDC) = 60 seconds
546 -
547 -(% style="display:none" %) (%%)
548 -
549 -== 4.1.2 Request the server to send an ACK ==
550 -
551 -
552 -(% style="color:blue" %)**AT Command: AT+PNACKMD**
553 -
554 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:889px" %)
555 -|(% 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**
556 -|(% 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(((
557 -OK
558 -)))
559 -|(% style="width:160px" %)AT+PNACKMD=0|(% style="width:627px" %)off request the server to send an ACK|(% style="width:100px" %)(((
560 -0
561 -OK
562 -)))
563 -
564 -(% style="display:none" %) (%%) (% style="color:blue" %)**Downlink Command: 0x34**
565 -
566 -0X34 01  ~/~/Same As AT+PNACKMD=1
567 -
568 -0x34 00  ~/~/Same As AT+PNACKMD=0
569 -
570 -
571 -=== 4.1.3 Set Interrupt Mode ===
572 -
573 -
574 -Feature, Set Interrupt mode for GPIO_EXIT.
575 -
576 -(% style="color:blue" %)**AT Command: AT+INTMOD1,AT+INTMOD2,AT+INTMOD3**
577 -
578 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
579 -|=(% 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**
580 -|(% style="width:154px" %)AT+INTMOD1=?|(% style="width:196px" %)Show current interrupt mode|(% style="width:157px" %)(((
581 -0
582 -OK
583 -the mode is 0 =Disable Interrupt
584 -)))
585 -|(% style="width:154px" %)AT+INTMOD1=2|(% style="width:196px" %)(((
586 -Set Transmit Interval
587 -0. (Disable Interrupt),
588 -~1. (Trigger by rising and falling edge)
589 -2. (Trigger by falling edge)
590 -3. (Trigger by rising edge)
591 -)))|(% style="width:157px" %)OK
592 -|(% style="width:154px" %)AT+INTMOD2=3|(% style="width:196px" %)Set Transmit Interval
593 -0. (Disable Interrupt),
594 -~1. (Trigger by rising and falling edge)
595 -2. (Trigger by falling edge)
596 -3. (Trigger by rising edge)|(% style="width:157px" %)OK
597 -
598 -(% style="color:blue" %)**Downlink Command: 0x06**
599 -
600 -Format: Command Code (0x06) followed by 3 bytes.
601 -
602 -This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
603 -
604 -* Example 1: Downlink Payload: 06000000  **~-~-->**  AT+INTMOD1=0
605 -* Example 2: Downlink Payload: 06000003  **~-~-->**  AT+INTMOD1=3
606 -* Example 3: Downlink Payload: 06000102  **~-~-->**  AT+INTMOD2=2
607 -
608 -== 2.13 Clock logging (Since firmware version v1.2.1) ==
609 -
610 -
611 -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.
612 -
613 -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.
614 -
615 -* (% style="color:blue" %)**AT Command:**(%%)** (% style="color:#037691" %)AT+CLOCKLOG=a,b,c,d(%%)**
616 -
617 -(% style="color:#037691" %)**a: **(%%)**0:** Disable Clock logging.  ** 1: **Enable Clock Logging
618 -
619 -(% 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.
620 -
621 -(% style="color:#037691" %)**c: **(%%)Specify the sampling interval: range **(0 ~~ 255 minutes)**
622 -
623 -(% style="color:#037691" %)**d:**(%%)How many entries should be uplink on every TDC **(max 32)**
624 -
625 -[[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"]]
626 -
627 -**Example:**
628 -
629 -**AT+CLOCKLOG=1,65535,1,5**
630 -
631 -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).
632 -
633 -(% class="wikigeneratedid" %)
634 -[[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"]]
635 -
636 -(% class="wikigeneratedid" %)
637 -(% 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.**
1714985699187-406.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.karry
Size
... ... @@ -1,1 +1,0 @@
1 -84.5 KB
Content
1714985711524-251.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.karry
Size
... ... @@ -1,1 +1,0 @@
1 -204.6 KB
Content