Changes for page SPH01-LB -- LoRaWAN Soil pH Sensor User Manual

Last modified by Xiaoling on 2024/01/15 09:36

From version < 62.7 >

edited by Xiaoling
on 2023/05/30 10:50

To version < 62.9 >

edited by Xiaoling
on 2023/05/30 10:59

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -93,7 +93,7 @@
  (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as LoRaWAN Sensor to Join LoRaWAN network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode.
--== 1.5 Button & LEDs ==
++== 1.6 Button & LEDs ==
  [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]]
@@ -112,7 +112,7 @@
  )))
  |(% style="width:167px" %)Fast press ACT 5 times.|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode.
--== 1.6 BLE connection ==
++== 1.7 BLE connection ==
  CPL03-LB support BLE remote configure.
@@ -127,12 +127,12 @@
  If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.
--== 1.7 Pin Definitions ==
++== 1.8 Pin Definitions ==
  [[image:image-20230523174230-1.png]]
--== 1.8 Mechanical ==
++== 1.9 Mechanical ==
  [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675143884058-338.png]]
@@ -277,7 +277,7 @@
  === 2.3.2 Sensor Configuration, FPORT~=4 ===
--CPL01 will only send this command after getting the downlink command (0x26 02) from the server.
++CPL03-LB will only send this command after getting the downlink command (0x26 02) from the server.
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
  |(% colspan="6" style="background-color:#d9e2f3; color:#0070c0; width:504px" %)**Sensor Configuration FPORT=4**
@@ -299,11 +299,11 @@
  )))
  (((
--(% style="color:blue" %)** If Disalarm = 1**(%%), CPL01 will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many disconnect/connect event, and platform only care about the total number of pulse.
++(% style="color:blue" %)** If Disalarm = 1**(%%), CPL03-LB will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many disconnect/connect event, and platform only care about the total number of pulse.
  )))
  (((
--(% style="color:blue" %)** If Disalarm = 0**(%%), CPL01 will send uplink at every TDC periodically.
++(% style="color:blue" %)** If Disalarm = 0**(%%), CPL03-LB will send uplink at every TDC periodically.
  )))
@@ -341,7 +341,7 @@
  (((
  (((
--CPL01 will send this uplink **after** Device Status once join the LoRaWAN network successfully. And CPL01 will:
++CPL03-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And CPL03-LB will:
  )))
  )))
@@ -537,7 +537,7 @@
  (((
--CPL01 stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.4DatalogFeature"]].
++CPL03-LB stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.4DatalogFeature"]].
  )))
  (((
@@ -545,7 +545,7 @@
  )))
  * (((
--Each data entry is 11 bytes and has the same structure as [[Real-Time open/close status>>||anchor="H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2"]], to save airtime and battery, CPL01 will send max bytes according to the current DR and Frequency bands.
++Each data entry is 11 bytes and has the same structure as [[Real-Time open/close status>>||anchor="H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2"]], to save airtime and battery, CPL03-LB will send max bytes according to the current DR and Frequency bands.
  )))
  (((
@@ -569,7 +569,7 @@
  )))
  (((
--If CPL01 doesn't have any data in the polling time. It will uplink 11 bytes of 0
++If CPL03-LB doesn't have any data in the polling time. It will uplink 11 bytes of 0
  )))
@@ -659,19 +659,19 @@
  == 2.5 Datalog Feature ==
--Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, S31x-LB will store the reading for future retrieving purposes.
++Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, CPL03-LB will store the reading for future retrieving purposes.
  === 2.5.1 Ways to get datalog via LoRaWAN ===
--Set [[PNACKMD=1>>||anchor="H2.5.4DatalogUplinkpayload28FPORT3D329"]], S31x-LB will wait for ACK for every uplink, when there is no LoRaWAN network,S31x-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.
++Set [[PNACKMD=1>>||anchor="H2.5.4DatalogUplinkpayload28FPORT3D329"]], CPL03-LB will wait for ACK for every uplink, when there is no LoRaWAN network,CPL03-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.
  * (((
--a) S31x-LB will do an ACK check for data records sending to make sure every data arrive server.
++a) CPL03-LB will do an ACK check for data records sending to make sure every data arrive server.
  )))
  * (((
--b) S31x-LB will send data in **CONFIRMED Mode** when PNACKMD=1, but S31x-LB 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 S31x-LB gets a ACK, S31x-LB will consider there is a network connection and resend all NONE-ACK messages.
++b) CPL03-LB will send data in **CONFIRMED Mode** when PNACKMD=1, but CPL03-LB 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 CPL03-LB gets a ACK, CPL03-LB will consider there is a network connection and resend all NONE-ACK messages.
  )))
  Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
@@ -682,7 +682,7 @@
  === 2.5.2 Unix TimeStamp ===
--S31x-LB uses Unix TimeStamp format based on
++CPL03-LB uses Unix TimeStamp format based on
  [[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-20220523001219-11.png?width=627&height=97&rev=1.1||alt="图片-20220523001219-11.png" height="97" width="627"]]
@@ -701,7 +701,7 @@
  User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
--Once S31x-LB Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to S31x-LB. If S31x-LB fails to get the time from the server, S31x-LB will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
++Once CPL03-LB Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to CPL03-LB. If CPL03-LB fails to get the time from the server, CPL03-LB will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
  (% 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.**
@@ -730,7 +730,7 @@
  )))
  (((
--Uplink Internal =5s，means CPL01 will send one packet every 5s. range 5~~255s.
++Uplink Internal =5s，means CPL03-LB will send one packet every 5s. range 5~~255s.
  )))
@@ -737,17 +737,17 @@
  == 2.7 Frequency Plans ==
--The S31x-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.
++The CPL03-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.
  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]]
--= 3. Configure S31x-LB =
++= 3. Configure CPL03-LB =
  == 3.1 Configure Methods ==
--S31x-LB supports below configure method:
++CPL03-LB supports below configure method:
  * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
  * 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]].
@@ -907,7 +907,7 @@
  )))
  (((
--(% style="color:blue" %)**AT+TTRIG=1,30**(%%)   ~-~-> When the **Keep Status** change from connect to disconnect, and device remains in disconnect status for more than 30 seconds. CPL01 will send an uplink packet, the [[Alarm bit>>||anchor="H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2"]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
++(% style="color:blue" %)**AT+TTRIG=1,30**(%%)   ~-~-> When the **Keep Status** change from connect to disconnect, and device remains in disconnect status for more than 30 seconds. CPL03-LB will send an uplink packet, the [[Alarm bit>>||anchor="H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2"]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
  )))
  (((

Changes for page SPH01-LB -- LoRaWAN Soil pH Sensor User Manual

Summary

Details

Applications

Navigation