Wiki source code of SE0X-CB/CS -- NB-IoT/LTE-M Soil Moisture & EC Sensor Transmitter User Manual
Last modified by Xiaoling on 2025/07/16 11:58
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | [[image:image-20250118092740-4.png||data-xwiki-image-style-alignment="center"]] | ||
| 2 | |||
| 3 | |||
| 4 | |||
| 5 | |||
| 6 | |||
| 7 | |||
| 8 | |||
| 9 | **Table of Contents :** | ||
| 10 | |||
| 11 | {{toc/}} | ||
| 12 | |||
| 13 | |||
| 14 | |||
| 15 | |||
| 16 | |||
| 17 | |||
| 18 | = 1. Introduction = | ||
| 19 | |||
| 20 | == 1.1 What is SE0X-CB/CS NB-IoT/LTE-M Soil Moisture & EC Sensor == | ||
| 21 | |||
| 22 | |||
| 23 | The Dragino SE0X-CB/CS is a (% style="color:blue" %)**NB-IoT/LTE-M Soil Moisture & EC Sensor**(%%) for Agri-IoT with up to 4 sensor probes. It is designed to measure the (% style="color:blue" %)**soil moisture of saline-alkali soil and loamy soil**(%%). The soil sensor uses (% style="color:blue" %)**FDR method**(%%) to calculate the soil moisture with the compensation from soil temperature and conductivity. It also has been calibrated in factory for Mineral soil type. | ||
| 24 | |||
| 25 | It detects (% style="color:blue" %)**Soil Moisture**(%%), (% style="color:blue" %)**Soil Temperature**(%%) and (% style="color:blue" %)**Soil Conductivity**(%%), and then upload to IoT server via NB-IoT or CAT-M1 network. | ||
| 26 | |||
| 27 | SE0X-CB/CS supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP, MQTTs or CoAP**(%%) for different application requirement. and Support Uplinks to various IoT Servers. | ||
| 28 | |||
| 29 | SE0X-CB/CS (% style="color:blue" %)**supports BLE configure**(%%) and (% style="color:blue" %)**wireless OTA update**(%%) which make user easy to use. | ||
| 30 | |||
| 31 | SE0X-CB/CS is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery **(%%)or (% style="color:blue" %)**solar powered + Li-ion battery**(%%), it is designed for long-term use up to several years. | ||
| 32 | |||
| 33 | [[image:image-20250416170943-1.jpeg]] | ||
| 34 | |||
| 35 | |||
| 36 | == 1.2 Features == | ||
| 37 | |||
| 38 | |||
| 39 | * For -NB Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 | ||
| 40 | * For -CB Bands: B1/B2/B3/B4/B5/B8/B12/B13~/~/B18/B19/B20/B25/B28/B66/B71/B85 | ||
| 41 | * CAT-M1 / LTE-M Bands: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 | ||
| 42 | * Ultra-low power consumption | ||
| 43 | * Up to 4 external sensor probes, probe length: 3.5 meters | ||
| 44 | * Monitor Soil Moisture | ||
| 45 | * Monitor Soil Temperature | ||
| 46 | * Monitor Soil Conductivity | ||
| 47 | * IP66 Waterproof Enclosure | ||
| 48 | * Multiply Sampling and one uplink | ||
| 49 | * Uplink via MQTT, MQTTs, TCP, UDP or CoAP | ||
| 50 | * GNSS for Location Report | ||
| 51 | * Support Bluetooth v5.1 remote configure and update firmware | ||
| 52 | * Uplink on periodically | ||
| 53 | * Downlink to change configure | ||
| 54 | * 8500mAh Li/SOCl2 Battery (SE0X-CB) | ||
| 55 | * Solar panel + 3000mAh Li-ion battery (SE0X-CS) | ||
| 56 | * Nano SIM card slot for NB-IoT SIM | ||
| 57 | |||
| 58 | (% style="color:blue" %)**Common DC Characteristics:** | ||
| 59 | |||
| 60 | * Supply Voltage: Built-in Battery , 2.6v ~~ 3.6v | ||
| 61 | * Operating Temperature: -40 ~~ 85°C | ||
| 62 | |||
| 63 | (% style="color:blue" %)**Soil Moisture:** | ||
| 64 | |||
| 65 | * Range: 0-100.00 V/V % | ||
| 66 | * Resolution: 0.01 V/V % | ||
| 67 | * Accuracy: ±3% (0-53%)V/V %, ±5% (>53%) V/V % | ||
| 68 | * Measure Method: FDR , with temperature &EC compensate | ||
| 69 | |||
| 70 | (% style="color:blue" %)**Soil Temperature** | ||
| 71 | |||
| 72 | * Range: -40.00℃～85.00℃ | ||
| 73 | * Resolution: 0.01℃ | ||
| 74 | * Accuracy: -10℃～50℃:<0.3℃ ,All other: <0.6℃ | ||
| 75 | * Measure Method: RTD, and calibrate | ||
| 76 | |||
| 77 | (% style="color:blue" %)**Soil Conductivity** | ||
| 78 | |||
| 79 | * Range: 0-20000 uS/cm(25℃)(0-20.0EC) | ||
| 80 | * Resolution: 1 uS/cm | ||
| 81 | * Accuracy: 2%FS | ||
| 82 | * Measure Method: Conductivity , with temperature compensate | ||
| 83 | |||
| 84 | (% style="color:blue" %)**NB-IoT Spec:** | ||
| 85 | |||
| 86 | (% style="color:#037691" %)**NB-IoT Module: BG95-NGFF** | ||
| 87 | |||
| 88 | (% style="color:#037691" %)**Support Bands:** | ||
| 89 | |||
| 90 | * B1 @H-FDD: 2100MHz | ||
| 91 | * B2 @H-FDD: 1900MHz | ||
| 92 | * B3 @H-FDD: 1800MHz | ||
| 93 | * B4 @H-FDD: 2100MHz | ||
| 94 | * B5 @H-FDD: 860MHz | ||
| 95 | * B8 @H-FDD: 900MHz | ||
| 96 | * B12 @H-FDD: 720MHz | ||
| 97 | * B13 @H-FDD: 740MHz | ||
| 98 | * B17 @H-FDD: 730MHz | ||
| 99 | * B18 @H-FDD: 870MHz | ||
| 100 | * B19 @H-FDD: 870MHz | ||
| 101 | * B20 @H-FDD: 790MHz | ||
| 102 | * B25 @H-FDD: 1900MHz | ||
| 103 | * B28 @H-FDD: 750MHz | ||
| 104 | * B66 @H-FDD: 2000MHz | ||
| 105 | * B70 @H-FDD: 2000MHz | ||
| 106 | * B85 @H-FDD: 700MHz | ||
| 107 | |||
| 108 | (% style="color:blue" %)**Battery:** | ||
| 109 | |||
| 110 | * Li/SOCI2 un-chargeable battery | ||
| 111 | * Capacity: 8500mAh | ||
| 112 | * Self-Discharge: <1% / Year @ 25°C | ||
| 113 | * Max continuously current: 130mA | ||
| 114 | * Max boost current: 2A, 1 second | ||
| 115 | |||
| 116 | (% style="color:blue" %)**Power Consumption** | ||
| 117 | |||
| 118 | * Sleep Mode: 5uA @ 3.3v | ||
| 119 | * LoRa Transmit Mode: 125mA @ 20dBm, 82mA @ 14dBm | ||
| 120 | |||
| 121 | == 1.4 Applications == | ||
| 122 | |||
| 123 | |||
| 124 | * Smart Agriculture | ||
| 125 | |||
| 126 | == 1.5 Sleep mode and working mode == | ||
| 127 | |||
| 128 | |||
| 129 | (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any NB-IoT/CAT-M1 activate. This mode is used for storage and shipping to save battery life. | ||
| 130 | |||
| 131 | (% style="color:blue" %)**Working Mode:**(%%) In this mode, Sensor will work as NB-IoT Sensor to Join NB-IoT 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. | ||
| 132 | |||
| 133 | |||
| 134 | == 1.6 Button & LEDs == | ||
| 135 | |||
| 136 | |||
| 137 | [[image:image-20250416171038-2.jpeg]] | ||
| 138 | |||
| 139 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
| 140 | |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 226px;background-color:#4F81BD;color:white" %)**Action** | ||
| 141 | |[[image:1749525630809-686.png]] 1~~3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
| 142 | If sensor has already attached to NB-IoT/CAT-M1 network, sensor will send an uplink packet, (% style="color:blue" %)**blue led**(%%) will blink once. | ||
| 143 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
| 144 | ))) | ||
| 145 | |[[image:1749525632333-486.png]] >3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
| 146 | (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to attach NB-IoT/CAT-M1 network. | ||
| 147 | Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device attach NB-IoT/CAT-M1 network or not. | ||
| 148 | ))) | ||
| 149 | |[[image:1749525641774-971.png]] x5|(% 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. | ||
| 150 | |||
| 151 | (% style="color:red" %)**Note: When the device is executing a program, the buttons may become invalid. It is best to press the buttons after the device has completed the program execution.** | ||
| 152 | |||
| 153 | |||
| 154 | == 1.7 BLE connection == | ||
| 155 | |||
| 156 | |||
| 157 | SE0X-CB/CS support BLE remote configure and firmware update. | ||
| 158 | |||
| 159 | BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case: | ||
| 160 | |||
| 161 | * Press button to send an uplink | ||
| 162 | * Press button to active device. | ||
| 163 | * Device Power on or reset. | ||
| 164 | |||
| 165 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
| 166 | |||
| 167 | |||
| 168 | == 1.8 Pin Definitions == | ||
| 169 | |||
| 170 | [[image:image-20250218141409-1.png||height="434" width="707"]] | ||
| 171 | |||
| 172 | === 1.8.1 Jumper JP2 === | ||
| 173 | |||
| 174 | |||
| 175 | Power on Device when put this jumper. | ||
| 176 | |||
| 177 | |||
| 178 | === 1.8.2 BOOT MODE / SW1 === | ||
| 179 | |||
| 180 | |||
| 181 | **1)** (% style="color:blue" %)**ISP:**(%%) upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. | ||
| 182 | |||
| 183 | **2)** (% style="color:blue" %)**Flash:**(%%) work mode, device starts to work and send out console output for further debug | ||
| 184 | |||
| 185 | |||
| 186 | === 1.8.3 Reset Button === | ||
| 187 | |||
| 188 | |||
| 189 | Press to reboot the device. | ||
| 190 | |||
| 191 | |||
| 192 | === 1.8.4 SIM Card Direction === | ||
| 193 | |||
| 194 | |||
| 195 | See this link. [[How to insert SIM Card>>https://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H2.AttachNetwork]]. | ||
| 196 | |||
| 197 | |||
| 198 | == 1.9 Mechanical == | ||
| 199 | |||
| 200 | === 1.9.1 for CB version === | ||
| 201 | |||
| 202 | (% style="color:blue" %)**Main Device Dimension:** | ||
| 203 | |||
| 204 | [[image:image-20250118094401-6.png]] | ||
| 205 | |||
| 206 | |||
| 207 | (% style="color:blue" %)**Probe Dimension:** | ||
| 208 | |||
| 209 | [[image:image-20250331153423-1.jpeg]] | ||
| 210 | |||
| 211 | |||
| 212 | === 1.9.2 for CS version === | ||
| 213 | |||
| 214 | |||
| 215 | [[image:image-20250331153444-2.jpeg]] | ||
| 216 | |||
| 217 | |||
| 218 | === 1.9.3 for sensor cable === | ||
| 219 | |||
| 220 | (% style="color:blue" %)**Cable size:** | ||
| 221 | |||
| 222 | Total cable length: 3500mm, deviation ±30mm | ||
| 223 | |||
| 224 | [[image:1751702941319-628.png]] | ||
| 225 | |||
| 226 | |||
| 227 | == 1.10 Installation in Soil == | ||
| 228 | |||
| 229 | |||
| 230 | (% style="color:blue" %)**Measurement the soil surface** | ||
| 231 | |||
| 232 | [[image:image-20250331153503-3.jpeg]] | ||
| 233 | |||
| 234 | Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. | ||
| 235 | |||
| 236 | |||
| 237 | [[image:image-20250331153512-4.jpeg]] | ||
| 238 | |||
| 239 | Dig a hole with diameter > 20CM. | ||
| 240 | |||
| 241 | Horizontal insert the probe to the soil and fill the hole for long term measurement. | ||
| 242 | |||
| 243 | |||
| 244 | = 2. Use SE0X-CB/CS to communicate with IoT Server = | ||
| 245 | |||
| 246 | == 2.1 Send data to IoT server via NB-IoT network == | ||
| 247 | |||
| 248 | |||
| 249 | The SE0X-CB/CS is equipped with a NB-IoT module, the pre-loaded firmware in SE0X-CB/CS will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by SE0X-CB/CS. | ||
| 250 | |||
| 251 | Below shows the network structure: | ||
| 252 | |||
| 253 | (% style="display:none" %) (%%) [[image:image-20250120150934-2.png]] | ||
| 254 | |||
| 255 | |||
| 256 | There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1T**(%%) version of SE0X-CB/CS. | ||
| 257 | |||
| 258 | |||
| 259 | (% style="color:blue" %)**GE Version**(%%): This version doesn't include SIM card or point to any IoT server. User needs to use AT Commands to configure below two steps to set SE0X-CB/CS send data to IoT server. | ||
| 260 | |||
| 261 | * Install NB-IoT SIM card and configure APN. See instruction of [[Attach Network>>https://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H2.AttachNetwork]]. | ||
| 262 | |||
| 263 | * Set up sensor to point to IoT Server. See instruction of [[Configure to Connect Different Servers>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.Configuretoconnecttodifferentservers]]. | ||
| 264 | |||
| 265 | Below shows result of different server as a glance. | ||
| 266 | |||
| 267 | (% border="1" cellspacing="4" style="width:515px" %) | ||
| 268 | |(% style="background-color:#4f81bd; color:white; width:100px" %)**Servers**|(% style="background-color:#4f81bd; color:white; width:300px" %)**Dash Board**|(% style="background-color:#4f81bd; color:white; width:115px" %)**Comments** | ||
| 269 | |(% style="width:127px" %)[[Node-Red>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.5A0Node-RedA028viaA0MQTT29]]|(% style="width:385px" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE02-NB_NB-IoT_Soil_Moisture%26EC_Sensor_User_Manual/WebHome/image-20230819113244-8.png?width=367&height=183&rev=1.1||alt="image-20230819113244-8.png"]]((( | ||
| 270 | |||
| 271 | )))|(% style="width:170px" %) | ||
| 272 | |(% style="width:127px" %)[[DataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]]|(% style="width:385px" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE02-NB_NB-IoT_Soil_Moisture%26EC_Sensor_User_Manual/WebHome/image-20230819113244-9.png?width=367&height=119&rev=1.1||alt="image-20230819113244-9.png"]]((( | ||
| 273 | |||
| 274 | )))|(% style="width:170px" %) | ||
| 275 | |(% style="width:127px" %)[[Tago.IO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.7A0Tago.ioA028viaA0MQTT29]]|(% style="width:385px" %) |(% style="width:170px" %) | ||
| 276 | |(% style="width:127px" %)[[General UDP>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.1GeneralA0UDPA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %) | ||
| 277 | |(% style="width:127px" %)[[General MQTT>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.2GeneralA0MQTTA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %) | ||
| 278 | |(% style="width:127px" %)[[ThingSpeak>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.3A0ThingSpeakA028viaA0MQTT29]]|(% style="width:385px" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE02-NB_NB-IoT_Soil_Moisture%26EC_Sensor_User_Manual/WebHome/image-20230819113244-10.png?width=367&height=104&rev=1.1||alt="image-20230819113244-10.png"]]((( | ||
| 279 | |||
| 280 | )))|(% style="width:170px" %) | ||
| 281 | |(% style="width:127px" %)[[ThingsBoard>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.6A0ThingsBoard.CloudA028viaA0MQTT29]]|(% style="width:385px" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE02-NB_NB-IoT_Soil_Moisture%26EC_Sensor_User_Manual/WebHome/image-20230819113244-11.png?width=367&height=141&rev=1.1||alt="image-20230819113244-11.png"]]((( | ||
| 282 | |||
| 283 | ))) | ||
| 284 | |||
| 285 | (% style="color:blue" %)**1T Version**(%%): This version has 1NCE SIM card pre-installed and configure to send value to ThingsEye. User Just need to select the sensor type in ThingsEyeand Activate SE0X-CB/CS and user will be able to see data in ThingsEye. See here for [[ThingsEye Config Instruction>>url:https://wiki.thingseye.io/xwiki/bin/view/Main/]]. | ||
| 286 | |||
| 287 | |||
| 288 | === (% style="color:blue" %)**Soil Sensor Address Configuration**(%%) === | ||
| 289 | |||
| 290 | All soil sensors are shipped with (% style="color:#037691" %)**default address 0x01**(%%). | ||
| 291 | |||
| 292 | Do not use the same address repeatedly on the same node, otherwise the data will conflict, so if you connect more than 1 sensor to the SE0X-CB/CS node, you need to follow the steps below to change the address (supported addresses: **01-04**): | ||
| 293 | |||
| 294 | **Step 1**: Keep the default address **01** for the **first sensor**. No modification or operation is required. | ||
| 295 | |||
| 296 | **Step 2**: Connect the **second sensor**, and change its address to **02**. | ||
| 297 | |||
| 298 | **Step 3**:** **Disconnect the second sensor, connect the** third sensor**, and change its address to **03**. | ||
| 299 | |||
| 300 | **Step 3**: Repeat Step 3 to assign address **04** to the **fourth sensor**. | ||
| 301 | |||
| 302 | |||
| 303 | **For details, see [[Configure Methods>>||anchor="H3.1ConfigureMethods"]] in 3.1 and [[Command Description>>||anchor="H3.22Settingthesensoraddress"]] in 3.22.** | ||
| 304 | |||
| 305 | (% style="color:blue" %)**Connection:** | ||
| 306 | |||
| 307 | * Wiring during sensor operation: | ||
| 308 | |||
| 309 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE0X-LB--LoRaWAN_Soil_Moisture%26EC_Sensor_Transmitter_User_Manual/WebHome/image-20250414091358-1.jpeg?width=549&height=287&rev=1.1||alt="image-20250414091358-1.jpeg" height="287" width="549"]] | ||
| 310 | |||
| 311 | * Wiring when changing the sensor address: | ||
| 312 | |||
| 313 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE0X-LB--LoRaWAN_Soil_Moisture%26EC_Sensor_Transmitter_User_Manual/WebHome/image-20250414092154-2.jpeg?width=548&height=303&rev=1.1||alt="image-20250414092154-2.jpeg" height="303" width="548"]] | ||
| 314 | |||
| 315 | (% style="color:red" %)**Note: The yellow wire is only used when the address of the sensor is modified. After the address of the sensor is successfully modified, please disconnect the yellow cable and use tape to isolate the wire core to prevent the yellow wire from touching the motherboard element and causing a short circuit.** | ||
| 316 | |||
| 317 | |||
| 318 | == 2.2 Payload Types == | ||
| 319 | |||
| 320 | |||
| 321 | To meet different server requirement, SE0X-CB/CS supports different payload type. | ||
| 322 | |||
| 323 | **Includes:** | ||
| 324 | |||
| 325 | * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5) | ||
| 326 | |||
| 327 | * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0) | ||
| 328 | |||
| 329 | * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1) | ||
| 330 | |||
| 331 | * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3) | ||
| 332 | |||
| 333 | User can specify the payload type when choose the connection protocol. Example: | ||
| 334 | |||
| 335 | (% style="color:#037691" %)**AT+PRO=1,0** (%%) ~/~/ Use COAP Connection & hex Payload | ||
| 336 | |||
| 337 | (% style="color:#037691" %)**AT+PRO=1,5** (%%) ~/~/ Use COAP Connection & Json Payload | ||
| 338 | |||
| 339 | (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload | ||
| 340 | |||
| 341 | (% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload | ||
| 342 | |||
| 343 | (% style="color:#037691" %)**AT+PRO=3,0** (%%) ~/~/ Use MQTT Connection & hex Payload | ||
| 344 | |||
| 345 | (% style="color:#037691" %)**AT+PRO=3,5** (%%) ~/~/ Use MQTT Connection & Json Payload | ||
| 346 | |||
| 347 | (% style="color:#037691" %)**AT+PRO=4,0** (%%) ~/~/ Use TCP Connection & hex Payload | ||
| 348 | |||
| 349 | (% style="color:#037691" %)**AT+PRO=4,5** (%%) ~/~/ Use TCP Connection & Json Payload | ||
| 350 | |||
| 351 | |||
| 352 | === 2.2.1 General Json Format(Type~=5) === | ||
| 353 | |||
| 354 | |||
| 355 | ==== 2.2.1.1 AT+CFGMOD~=0(Default Mode) ==== | ||
| 356 | |||
| 357 | |||
| 358 | This is the General Json Format. As below: | ||
| 359 | |||
| 360 | (% style="color:#4472c4" %)**{"IMEI":"868508065605159","IMSI":"454312901015184","Model":"SE0X-CB","interrupt":0,"interrupt_level":0,"battery":3.22,"signal":17,"sensor_flag":"1111","water_soil1":40.32,"temp_soil1":19.33,"conduct_soil1":6716,"water_soil2":40.21,"temp_soil2":19.64,"conduct_soil2":6507,"water_soil3":36.35,"temp_soil3":19.67,"conduct_soil3":5858,"water_soil4":8.70,"temp_soil4":19.39,"conduct_soil4":2984,"time":"2025-01-20T08:01:12Z","latitude":0.000000,"longitude":0.000000,"gps_time":"1970-01-01T00:00:00Z"}** | ||
| 361 | |||
| 362 | [[image:image-20250120163312-3.png]] | ||
| 363 | |||
| 364 | |||
| 365 | (% style="color:red" %)**Notice, from above payload:** | ||
| 366 | |||
| 367 | * interrupt, interrupt_level, battery, signal, sensor_flag, water_soil1, temp_soil1, conduct_soil1, water_soil2, emp_soil2, conduct_soil2, water_soil3, temp_soil3, onduct_soil3, water_soil4, temp_soil4, | ||
| 368 | |||
| 369 | conduct_soil4, time, Latitude, Longitude & gps_time are the value at uplink time. | ||
| 370 | |||
| 371 | |||
| 372 | ==== 2.2.1.2 AT+CFGMOD~=1(Original value) ==== | ||
| 373 | |||
| 374 | |||
| 375 | This is the General Json Format. As below: | ||
| 376 | |||
| 377 | (% style="color:#4472c4" %)**{"IMEI":"868508065605159","IMSI":"454312901015184","Model":"SE0X-CB","interrupt":0,"interrupt_level":0,"battery":3.23,"signal":16,"sensor_flag":"1111","Soil_dielectric_constant1":24.2,"raw_water_soil1":4854,"raw_conduct_soil1":17217,"Soil_dielectric_constant2":28.8,"raw_water_soil2":5130,"raw_conduct_soil2":18958,"Soil_dielectric_constant3":19.5,"raw_water_soil3":4630,"raw_conduct_soil3":17580,"Soil_dielectric_constant4":1.0,"raw_water_soil4":2607,"raw_conduct_soil4":262,"time":"2025-01-20T10:06:27Z","latitude":0.000000,"longitude":0.000000,"gps_time":"1970-01-01T00:00:00Z"}** | ||
| 378 | |||
| 379 | [[image:image-20250120180757-15.png]] | ||
| 380 | |||
| 381 | (% style="color:red" %)**Notice, from above payload:** | ||
| 382 | |||
| 383 | * interrupt, interrupt_level, battery, signal, sensor_flag, Soil_dielectric_constant1, raw_water_soil1, raw_conduct_soil1, Soil_dielectric_constant2, raw_water_soil2, raw_conduct_soil2, | ||
| 384 | |||
| 385 | Soil_dielectric_constant3, raw_water_soil3, raw_conduct_soil3, Soil_dielectric_constant4, raw_water_soil4, raw_conduct_soil4, time, Latitude, Longitude & gps_timeare the value at uplink time. | ||
| 386 | |||
| 387 | |||
| 388 | === 2.2.2 HEX format Payload(Type~=0) === | ||
| 389 | |||
| 390 | |||
| 391 | ==== 2.2.2.1 AT+CFGMOD~=0(Default Mode) ==== | ||
| 392 | |||
| 393 | This is the HEX Format. As below: | ||
| 394 | |||
| 395 | (% style="color:#4472c4" %)**f868508065605159f45431290101518469640ccd170000000f0ee207961a09106c07b7190b0e3d07b91914034c07ac0b94678e0ae2000000000000000000000000** | ||
| 396 | |||
| 397 | [[image:image-20250120182441-17.png]] | ||
| 398 | |||
| 399 | If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. | ||
| 400 | |||
| 401 | [[image:image-20250120164039-4.png]] | ||
| 402 | |||
| 403 | |||
| 404 | (% style="color:blue" %)**Device ID(f+IMEI):**(%%)** **f868508065605159 =868508065605159 | ||
| 405 | |||
| 406 | (% style="color:blue" %)**SIM Card ID(f+IMSI):**(%%)** **f454312901015184 =454312901015184 | ||
| 407 | |||
| 408 | |||
| 409 | (% style="color:blue" %)**Version:** | ||
| 410 | |||
| 411 | These bytes include the hardware and software version. | ||
| 412 | |||
| 413 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x69 for SE0X-CB/CS | ||
| 414 | |||
| 415 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0 | ||
| 416 | |||
| 417 | |||
| 418 | (% style="color:blue" %)**BAT (Battery Info):** | ||
| 419 | |||
| 420 | Ex1: 0x0CD1 = 3281mV | ||
| 421 | |||
| 422 | |||
| 423 | (% style="color:blue" %)**Signal Strength:** | ||
| 424 | |||
| 425 | NB-IoT Network signal Strength. | ||
| 426 | |||
| 427 | **Ex1: 0x17 = 23** | ||
| 428 | |||
| 429 | **0** -113dBm or less | ||
| 430 | |||
| 431 | **1** -111dBm | ||
| 432 | |||
| 433 | **2...30** -109dBm... -53dBm | ||
| 434 | |||
| 435 | **31** -51dBm or greater | ||
| 436 | |||
| 437 | **99** Not known or not detectable | ||
| 438 | |||
| 439 | |||
| 440 | (% style="color:blue" %)**MOD** | ||
| 441 | |||
| 442 | This data field shows the current working mode. | ||
| 443 | |||
| 444 | **Ex1:** 0x00 default mode. | ||
| 445 | |||
| 446 | **Ex2: **0x01 original mode. | ||
| 447 | |||
| 448 | |||
| 449 | (% style="color:blue" %)**Interrupt** | ||
| 450 | |||
| 451 | This data field shows if this packet is generated by interrupt or not. | ||
| 452 | |||
| 453 | **Example:** | ||
| 454 | |||
| 455 | If byte[0]&0x01=0x00 : Normal uplink packet. | ||
| 456 | |||
| 457 | If byte[0]&0x01=0x01 : Interrupt Uplink Packet. | ||
| 458 | |||
| 459 | |||
| 460 | (% style="color:blue" %)**Interrupt_level:** | ||
| 461 | |||
| 462 | This byte shows whether the interrupt is triggered by a high or low level. | ||
| 463 | |||
| 464 | **Ex1:** 0x00 Interrupt triggered by falling edge (low level) | ||
| 465 | |||
| 466 | **Ex2: **0x01 Interrupt triggered by rising edge (high level) | ||
| 467 | |||
| 468 | |||
| 469 | (% style="color:blue" %)**Sensor_flag** | ||
| 470 | |||
| 471 | Displays whether sensors are connected. | ||
| 472 | |||
| 473 | **0:** Sensor connection not detected. | ||
| 474 | |||
| 475 | **1:** Sensor connection detected. | ||
| 476 | |||
| 477 | **For example,** s_flag=1111,.Represents recognition to four sensors. | ||
| 478 | |||
| 479 | Counting from left to right, | ||
| 480 | |||
| 481 | The first number represents the **01** address sensor, | ||
| 482 | |||
| 483 | The second number represents the **02** address sensor; | ||
| 484 | |||
| 485 | The third number represents the **03** address sensor; | ||
| 486 | |||
| 487 | The fourth number represents the **04** address sensor. | ||
| 488 | |||
| 489 | |||
| 490 | (% style="color:blue" %)**Soil Moisture ** | ||
| 491 | |||
| 492 | ((( | ||
| 493 | Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil. | ||
| 494 | ))) | ||
| 495 | |||
| 496 | ((( | ||
| 497 | For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is (% style="color:blue" %)**05DC(H) = 1500(D) /100 = 15%.** | ||
| 498 | ))) | ||
| 499 | |||
| 500 | |||
| 501 | (% style="color:blue" %)**Soil Temperature ** | ||
| 502 | |||
| 503 | ((( | ||
| 504 | Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is 0x09 0xEC, the temperature content in the soil is | ||
| 505 | ))) | ||
| 506 | |||
| 507 | ((( | ||
| 508 | **Example**: | ||
| 509 | ))) | ||
| 510 | |||
| 511 | ((( | ||
| 512 | If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C | ||
| 513 | ))) | ||
| 514 | |||
| 515 | ((( | ||
| 516 | If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C | ||
| 517 | ))) | ||
| 518 | |||
| 519 | |||
| 520 | (% style="color:blue" %)**Soil Conductivity (EC) ** | ||
| 521 | |||
| 522 | ((( | ||
| 523 | Obtain (% style="color:blue" %)**__soluble salt concentration__**(%%) in soil or (% style="color:blue" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:blue" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000). | ||
| 524 | ))) | ||
| 525 | |||
| 526 | ((( | ||
| 527 | For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. | ||
| 528 | ))) | ||
| 529 | |||
| 530 | ((( | ||
| 531 | Generally, the EC value of irrigation water is less than 800uS / cm. | ||
| 532 | ))) | ||
| 533 | |||
| 534 | |||
| 535 | (% style="color:blue" %)**TimeStamp: ** | ||
| 536 | |||
| 537 | Unit TimeStamp Example: 678B1740(H) = 1737168704(D) | ||
| 538 | |||
| 539 | Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]]) to get the time. | ||
| 540 | |||
| 541 | |||
| 542 | (% style="color:blue" %)**Latitude:** | ||
| 543 | |||
| 544 | EX1:** **0x00000000 ~/~/ Locating fails or is not enabled. | ||
| 545 | |||
| 546 | EX2:** **0x015a771e(H)=22705950(D)=22.705950 | ||
| 547 | |||
| 548 | |||
| 549 | (% style="color:blue" %)**Longitude:** | ||
| 550 | |||
| 551 | EX1:** **0x00000000 ~/~/ Locating fails or is not enabled. | ||
| 552 | |||
| 553 | EX2:** **0x114242500(H)=114242500(D)=114.242500 | ||
| 554 | |||
| 555 | |||
| 556 | (% style="color:blue" %)**GPS_Timestamp:** | ||
| 557 | |||
| 558 | EX1: 0x00000000 ~/~/ The value is "1970-01-01T00:00:00Z" in JSON format. The initial GPS time is not refreshed if GPS positioning is disabled or fails. | ||
| 559 | |||
| 560 | EX2: 0x6682595d =1719818589 = 2024-07-01 15:23:09 | ||
| 561 | |||
| 562 | |||
| 563 | ==== 2.2.2.2 AT+CFGMOD~=1(Original value) ==== | ||
| 564 | |||
| 565 | This is the HEX Format. As below: | ||
| 566 | |||
| 567 | (% style="color:#4472c4" %)**f868508065605159f45431290101518469640ccd110100000f00f312f74dc20120140b4a8200c312134d12000a0a2f0106678e2139000000000000000000000000** | ||
| 568 | |||
| 569 | [[image:image-20250120182922-18.png]] | ||
| 570 | |||
| 571 | If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. | ||
| 572 | |||
| 573 | [[image:image-20250120181405-16.png]] | ||
| 574 | |||
| 575 | |||
| 576 | === 2.2.3 ThingsBoard Payload(Type~=3) === | ||
| 577 | |||
| 578 | |||
| 579 | ==== 2.2.3.1 AT+CFGMOD~=0(Default Mode) ==== | ||
| 580 | |||
| 581 | (% style="color:#4472c4" %)**{ | ||
| 582 | "IMEI": "868508065605159", | ||
| 583 | "IMSI": "454312901015184", | ||
| 584 | "Model": "SE0X-CB", | ||
| 585 | "interrupt": 0, | ||
| 586 | "interrupt_level": 0, | ||
| 587 | "battery": 3.27, | ||
| 588 | "signal": 21, | ||
| 589 | "sensor_flag": "1111", | ||
| 590 | "water_soil1": 39.07, | ||
| 591 | "temp_soil1": 19.51, | ||
| 592 | "conduct_soil1": 7301, | ||
| 593 | "water_soil2": 42.33, | ||
| 594 | "temp_soil2": 19.85, | ||
| 595 | "conduct_soil2": 6361, | ||
| 596 | "water_soil3": 36.5, | ||
| 597 | "temp_soil3": 19.81, | ||
| 598 | "conduct_soil3": 6783, | ||
| 599 | "water_soil4": 7.28, | ||
| 600 | "temp_soil4": 19.41, | ||
| 601 | "conduct_soil4": 2839, | ||
| 602 | "time": "2025-01-20T09:01:13Z", | ||
| 603 | "latitude": 0, | ||
| 604 | "longitude": 0, | ||
| 605 | "gps_time": "1970-01-01T00:00:00Z" | ||
| 606 | }** | ||
| 607 | |||
| 608 | [[image:image-20250120170747-6.png]] | ||
| 609 | |||
| 610 | |||
| 611 | ==== 2.2.3.2 AT+CFGMOD~=1(Original value) ==== | ||
| 612 | |||
| 613 | |||
| 614 | (% style="color:#4472c4" %)**{ | ||
| 615 | "IMEI": "868508065605159", | ||
| 616 | "IMSI": "454312901015184", | ||
| 617 | "Model": "SE0X-CB", | ||
| 618 | "interrupt": 0, | ||
| 619 | "interrupt_level": 0, | ||
| 620 | "battery": 3.23, | ||
| 621 | "signal": 17, | ||
| 622 | "sensor_flag": "1111", | ||
| 623 | "Soil_dielectric_constant1": 24.2, | ||
| 624 | "raw_water_soil1": 4852, | ||
| 625 | "raw_conduct_soil1": 22367, | ||
| 626 | "Soil_dielectric_constant2": 28.8, | ||
| 627 | "raw_water_soil2": 5130, | ||
| 628 | "raw_conduct_soil2": 18293, | ||
| 629 | "Soil_dielectric_constant3": 19.5, | ||
| 630 | "raw_water_soil3": 4631, | ||
| 631 | "raw_conduct_soil3": 15702, | ||
| 632 | "Soil_dielectric_constant4": 1, | ||
| 633 | "raw_water_soil4": 2614, | ||
| 634 | "raw_conduct_soil4": 283, | ||
| 635 | "time": "2025-01-20T10:00:57Z", | ||
| 636 | "latitude": 0, | ||
| 637 | "longitude": 0, | ||
| 638 | "gps_time": "1970-01-01T00:00:00Z" | ||
| 639 | }** | ||
| 640 | |||
| 641 | [[image:image-20250120180435-14.png]] | ||
| 642 | |||
| 643 | |||
| 644 | === 2.2.4 ThingSpeak Payload(Type~=1) === | ||
| 645 | |||
| 646 | |||
| 647 | This payload meets ThingSpeak platform requirement. | ||
| 648 | |||
| 649 | ThingSpeak only supports a maximum of 8 field charts per channel, so the sample screenshot contains only 8 fields charts. | ||
| 650 | |||
| 651 | |||
| 652 | ==== 2.2.4.1 AT+CFGMOD~=0(Default Mode) ==== | ||
| 653 | |||
| 654 | |||
| 655 | (% style="color:#4472c4" %)**field1=Battery value&field2=Signal value&field3=latitude value&field4=longitude value&field5=water_soil1 value&field6=temp_soil1 value&field7=conduct_soil1 value&field8=water_soil2 value** | ||
| 656 | |||
| 657 | [[image:image-20250120172417-9.png]] | ||
| 658 | |||
| 659 | [[image:image-20250120172439-10.png]] | ||
| 660 | |||
| 661 | |||
| 662 | ==== 2.2.4.2 AT+CFGMOD~=1(Original value) ==== | ||
| 663 | |||
| 664 | |||
| 665 | (% style="color:#4472c4" %)**field1=Battery value&field2=Signal value&field3=latitude value&field4=longitude value&field5=Soil_dielectric_constant1 value&field6=raw_water_soil1 value&field7=raw_conduct_soil1 value&field8=Soil_dielectric_constant2 value** | ||
| 666 | |||
| 667 | [[image:image-20250120174208-11.png]] | ||
| 668 | |||
| 669 | [[image:image-20250120174216-12.png]] | ||
| 670 | |||
| 671 | |||
| 672 | = 3. Configure SE0X-CB/CS = | ||
| 673 | |||
| 674 | == 3.1 Configure Methods == | ||
| 675 | |||
| 676 | |||
| 677 | SE0X-CB/CS supports below configure method: | ||
| 678 | |||
| 679 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
| 680 | |||
| 681 | * 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]]. | ||
| 682 | |||
| 683 | == 3.2 Serial Access Password == | ||
| 684 | |||
| 685 | |||
| 686 | After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window. | ||
| 687 | |||
| 688 | The label on the box of the node will print the initial password: AT+PIN=**xxxxxx**, and directly use the six-digit password to access the AT instruction window. | ||
| 689 | |||
| 690 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-NB%2C-NS_RS485%2CUART_to_NB-IoT_Converter_User_Manual/WebHome/image-20250226165815-1.png?rev=1.1||alt="image-20250226165815-1.png"]] | ||
| 691 | |||
| 692 | |||
| 693 | If you need to change the password, use **AT+PWORD=**xxxxxx (6 characters), -CB nodes only support lowercase letters. | ||
| 694 | |||
| 695 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-CB_NB-IoTLTE-M_Sensor_Node_User_Manual/WebHome/image-20240826180321-2.png?rev=1.1||alt="image-20240826180321-2.png"]] | ||
| 696 | |||
| 697 | |||
| 698 | (% style="color:red" %)**Note: After entering the command, you need to add a line break, and you can also set automatic line breaks in the Bluetooth tool or UART connection tool.** | ||
| 699 | |||
| 700 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-CB_NB-IoTLTE-M_Sensor_Node_User_Manual/WebHome/image-20240826180330-3.png?rev=1.1||alt="image-20240826180330-3.png"]] | ||
| 701 | |||
| 702 | |||
| 703 | == 3.3 AT Commands Set == | ||
| 704 | |||
| 705 | |||
| 706 | AT+<CMD>? : Help on <CMD> | ||
| 707 | |||
| 708 | AT+<CMD> : Run <CMD> | ||
| 709 | |||
| 710 | AT+<CMD>=<value> : Set the value | ||
| 711 | |||
| 712 | AT+<CMD>=? : Get the value | ||
| 713 | |||
| 714 | |||
| 715 | (% style="color:blue" %)**General Commands** | ||
| 716 | |||
| 717 | AT+MODEL : Get module information | ||
| 718 | |||
| 719 | ATZ : Trig a reset of the MCU | ||
| 720 | |||
| 721 | AT+CFGMOD : Working mode selection | ||
| 722 | |||
| 723 | AT+DEUI : Get or set the Device ID | ||
| 724 | |||
| 725 | AT+SERVADDR: Get or Set the Server address | ||
| 726 | |||
| 727 | AT+TDC : Get or set the application data transmission interval in s | ||
| 728 | |||
| 729 | AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising) | ||
| 730 | |||
| 731 | AT+APN : Get or set the APN | ||
| 732 | |||
| 733 | AT+5VT : Get or Set extend the time of 5V power | ||
| 734 | |||
| 735 | AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP) | ||
| 736 | |||
| 737 | AT+RXDL : Get or Set the receiving time | ||
| 738 | |||
| 739 | AT+GETSENSORVALUE : Returns the current sensor measurement | ||
| 740 | |||
| 741 | AT+DNSCFG : Get or Set DNS Server | ||
| 742 | |||
| 743 | AT+CSQTIME : Get or Set the time to join the network | ||
| 744 | |||
| 745 | AT+GDNS : Get or Set the DNS | ||
| 746 | |||
| 747 | AT+SLEEP : Get or Set the sleep mode | ||
| 748 | |||
| 749 | AT+IPTYPE : Set the IPv4 or IPv6 | ||
| 750 | |||
| 751 | AT+QSW : Power on and power off BG95 module | ||
| 752 | |||
| 753 | AT+QBAND: Get or set Frequency Band | ||
| 754 | |||
| 755 | AT+IOTMOD: Configure Network Category to be Searched for under LTE RAT | ||
| 756 | |||
| 757 | AT+DOWNTE: Get or set the conversion between the standard version and 1T version downlinks | ||
| 758 | |||
| 759 | AT+MADD: Change the sensor address to 0x01, 0x02, 0x03, 0x04 | ||
| 760 | |||
| 761 | |||
| 762 | (% style="color:blue" %)**MQTT Management** | ||
| 763 | |||
| 764 | AT+CLIENT : Get or Set the MQTT clientID | ||
| 765 | |||
| 766 | AT+UNAME : Get or Set the MQTT Username | ||
| 767 | |||
| 768 | AT+PWD : Get or Set the MQTT password | ||
| 769 | |||
| 770 | AT+PUBTOPIC: Get or set MQTT publishing topic | ||
| 771 | |||
| 772 | AT+SUBTOPIC: Get or set MQTT subscription topic | ||
| 773 | |||
| 774 | AT+MQOS : Set the QoS level of MQTT | ||
| 775 | |||
| 776 | AT+TLSMOD : Get or Set the TLS mode | ||
| 777 | |||
| 778 | |||
| 779 | (% style="color:blue" %)**COAP Management** | ||
| 780 | |||
| 781 | AT+URI1: Get or set CoAP option 1 | ||
| 782 | |||
| 783 | AT+URI2: Get or set CoAP option 2 | ||
| 784 | |||
| 785 | AT+URI3: Get or set CoAP option 3 | ||
| 786 | |||
| 787 | AT+URI4: Get or set CoAP option 4 | ||
| 788 | |||
| 789 | AT+URI5: Get or set CoAP option 5 | ||
| 790 | |||
| 791 | AT+URI6: Get or set CoAP option 6 | ||
| 792 | |||
| 793 | AT+URI7: Get or set CoAP option 7 | ||
| 794 | |||
| 795 | AT+URI8: Get or set CoAP option 8 | ||
| 796 | |||
| 797 | |||
| 798 | (% style="color:blue" %)**GPS** | ||
| 799 | |||
| 800 | AT+GNSST : Extend the time to turn on GNSS | ||
| 801 | |||
| 802 | AT+GPS : Turn off and on GPS | ||
| 803 | |||
| 804 | AT+GTDC : Get or set GPS positioning interval in units of h | ||
| 805 | |||
| 806 | |||
| 807 | (% style="color:blue" %)**Information** | ||
| 808 | |||
| 809 | AT+FDR1 : Reset parameters to factory default values except for passwords | ||
| 810 | |||
| 811 | AT+FDR : Reset Parameters to Factory Default | ||
| 812 | |||
| 813 | AT+CFG : Print all settings | ||
| 814 | |||
| 815 | AT+PWORD : Get or set the System password | ||
| 816 | |||
| 817 | AT+LDATA : Get the last upload data | ||
| 818 | |||
| 819 | AT+GETLOG : Print serial port logs | ||
| 820 | |||
| 821 | |||
| 822 | == 3.4 Test Uplink and Change Update Interval == | ||
| 823 | |||
| 824 | |||
| 825 | By default, Sensor will send uplinks **every 2 hours.** | ||
| 826 | |||
| 827 | User can use below commands to change the uplink interval. | ||
| 828 | |||
| 829 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TDC** (%%) | ||
| 830 | |||
| 831 | Example: AT+TDC=7200 ~/~/ Set Update Interval to 7200 seconds | ||
| 832 | |||
| 833 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x01** | ||
| 834 | |||
| 835 | Format: Command Code (0x01) followed by 3 bytes. | ||
| 836 | |||
| 837 | Example: 12 hours= 43200 seconds 43200(D)=0xA8C0(H) | ||
| 838 | |||
| 839 | Downlink Payload: **01 00 A8 C0** ~/~/ AT+TDC=43200, Set Update Interval to 12 hours. | ||
| 840 | |||
| 841 | (% style="color:red" %)**Note: User can also push the button for more than 1 second to activate an uplink.** | ||
| 842 | |||
| 843 | |||
| 844 | == 3.5 Working mode selection == | ||
| 845 | |||
| 846 | |||
| 847 | Feature: Working mode selection. | ||
| 848 | |||
| 849 | (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+CFGMOD** | ||
| 850 | |||
| 851 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:470px" %) | ||
| 852 | |=(% style="width: 191px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 279px; background-color: rgb(79, 129, 189); color: white;" %)**Function** | ||
| 853 | |(% style="width:191px" %)AT+CFGMOD=0|(% style="width:277px" %)((( | ||
| 854 | Set the operating mode to the default mode | ||
| 855 | ))) | ||
| 856 | |(% style="width:191px" %)AT+CFGMOD=1|(% style="width:277px" %)Setting the operating mode to the original mode | ||
| 857 | |||
| 858 | (% style="color:blue" %)**Downlink Command: **(% style="color:#037691" %)**0x02** | ||
| 859 | |||
| 860 | * Downlink command: 02 01 ~/~/ Equal to AT+CFGMOD=0 | ||
| 861 | * Downlink command: 02 02 ~/~/ Equal to AT+CFGMOD=1 | ||
| 862 | |||
| 863 | == 3.6 Set the receiving time == | ||
| 864 | |||
| 865 | |||
| 866 | Feature: Extend the receiving time | ||
| 867 | |||
| 868 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+RXDL** | ||
| 869 | |||
| 870 | Example: AT+RXDL=1000 ~/~/ Set the receiving time delay to 1000ms | ||
| 871 | |||
| 872 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x03** | ||
| 873 | |||
| 874 | Format: Command Code (0x03) followed by 3 bytes. | ||
| 875 | |||
| 876 | Example: Downlink Payload: **03 00 03 E8 **~/~/ AT+RXDL=1000 | ||
| 877 | |||
| 878 | |||
| 879 | == 3.7 Reset == | ||
| 880 | |||
| 881 | |||
| 882 | Feature: Trig a reset of the MCU. | ||
| 883 | |||
| 884 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**ATZ** | ||
| 885 | |||
| 886 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x04FF** | ||
| 887 | |||
| 888 | |||
| 889 | == 3.8 +5V == | ||
| 890 | |||
| 891 | |||
| 892 | Feature: Set extend the time of 5V power. | ||
| 893 | |||
| 894 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+5VT** | ||
| 895 | |||
| 896 | Example: AT+5VT=2000 ~/~/ Set extend the time of 5V power to 2000 ms | ||
| 897 | |||
| 898 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x05** | ||
| 899 | |||
| 900 | Format: Command Code (0x05) followed by 3 bytes. | ||
| 901 | |||
| 902 | Example: Downlink Payload: **05 00 07 D0 **~/~/ AT+5VT=2000 | ||
| 903 | |||
| 904 | |||
| 905 | == 3.9 Trigger an uplink by external interrupt == | ||
| 906 | |||
| 907 | |||
| 908 | SE0X-CB/CS has an external trigger interrupt function. Users can use the GPIO_EXTI pin to trigger the upload of data packets. | ||
| 909 | |||
| 910 | (% style="color:blue" %)**AT command:** | ||
| 911 | |||
| 912 | * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode | ||
| 913 | |||
| 914 | * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt | ||
| 915 | |||
| 916 | * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge | ||
| 917 | |||
| 918 | * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge | ||
| 919 | |||
| 920 | * (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge | ||
| 921 | |||
| 922 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x06** | ||
| 923 | |||
| 924 | Format: Command Code (0x06) followed by 3 bytes. | ||
| 925 | |||
| 926 | Example1: Downlink Payload: **06 00 00 01 **~/~/ AT+INTMOD=1 | ||
| 927 | |||
| 928 | Example2: Downlink Payload: **06 00 00 03 **~/~/ AT+INTMOD=3 | ||
| 929 | |||
| 930 | |||
| 931 | == 3.10 Set the QoS level == | ||
| 932 | |||
| 933 | |||
| 934 | This command is used to set the QoS level of **MQTT**. | ||
| 935 | |||
| 936 | (% style="color:blue" %)**AT command:** | ||
| 937 | |||
| 938 | * (% style="color:#037691" %)**AT+MQOS=xx**(%%)** **~/~/ 0~~2 | ||
| 939 | |||
| 940 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x07(%%)** | ||
| 941 | |||
| 942 | Format: Command Code (0x07) followed by 1 byte. | ||
| 943 | |||
| 944 | **Ex1:** Downlink payload: **0x0700** ~/~/ AT+MQOS=0 | ||
| 945 | |||
| 946 | **Ex2:** Downlink payload: **0x0701** ~/~/ AT+MQOS=1 | ||
| 947 | |||
| 948 | |||
| 949 | == 3.11 Set the TLS mode == | ||
| 950 | |||
| 951 | |||
| 952 | Refer to this link ([[MQTT Connection to send data to Tago.io>>https://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.8A0Tago.ioA028viaA0MQTT29]])to use the TLS mode. | ||
| 953 | |||
| 954 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TLSMOD** | ||
| 955 | |||
| 956 | **Example 1: ** AT+TLSMOD=0,0 ~/~/ Disable TLS Mode. | ||
| 957 | |||
| 958 | **Example 2:** AT+TLSMOD=1,0 ~/~/ No authentication | ||
| 959 | |||
| 960 | AT+TLSMOD=1,1 ~/~/ Perform server authentication | ||
| 961 | |||
| 962 | AT+TLSMOD=1,2 ~/~/ Perform server and client authentication if requested by the remote server | ||
| 963 | |||
| 964 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x09(%%)** | ||
| 965 | |||
| 966 | Format: Command Code (0x09) followed by 2 bytes. | ||
| 967 | |||
| 968 | Example1: Downlink Payload: **09 00 00 **~/~/ AT+TLSMOD=0,0 | ||
| 969 | |||
| 970 | Example2: Downlink Payload: **09 01 02 **~/~/ AT+TLSMOD=1,2 | ||
| 971 | |||
| 972 | |||
| 973 | == 3.12 Set GNSS open time == | ||
| 974 | |||
| 975 | |||
| 976 | Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated. | ||
| 977 | |||
| 978 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST** | ||
| 979 | |||
| 980 | Example: AT+GNSST=30 ~/~/ Set the GPS positioning time to 30 seconds | ||
| 981 | |||
| 982 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)** | ||
| 983 | |||
| 984 | Format: Command Code (0x10) followed by 2 bytes. | ||
| 985 | |||
| 986 | Example: Downlink Payload: **10 00 1E **~/~/ AT+GNSST=30 | ||
| 987 | |||
| 988 | |||
| 989 | == 3.13 Turn on/off GPS == | ||
| 990 | |||
| 991 | |||
| 992 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS** | ||
| 993 | |||
| 994 | **Ex1: **AT+GPS=0 ~/~/ Turn off GPS | ||
| 995 | |||
| 996 | **Ex2: **AT+GPS=1 ~/~/ Turn on GPS | ||
| 997 | |||
| 998 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)** | ||
| 999 | |||
| 1000 | Format: Command Code (0x11) followed by 1 byte. | ||
| 1001 | |||
| 1002 | Example: Downlink Payload: **11 01 **~/~/ AT+GPS=1 | ||
| 1003 | |||
| 1004 | |||
| 1005 | == 3.14 Set GPS positioning interval == | ||
| 1006 | |||
| 1007 | |||
| 1008 | Feature: Set GPS positioning interval (unit: hour). | ||
| 1009 | |||
| 1010 | When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation. | ||
| 1011 | |||
| 1012 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC** | ||
| 1013 | |||
| 1014 | Example: AT+GTDC=24 ~/~/ Set the GPS positioning interval to 24h. | ||
| 1015 | |||
| 1016 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)** | ||
| 1017 | |||
| 1018 | Format: Command Code (0x12) followed by 3 bytes. | ||
| 1019 | |||
| 1020 | Example: 24 hours: 24(D)=0x18(H) | ||
| 1021 | |||
| 1022 | Downlink Payload: **12 00 00 18 **~/~/ AT+GTDC=24 | ||
| 1023 | |||
| 1024 | |||
| 1025 | == 3.15 Set the search network time == | ||
| 1026 | |||
| 1027 | |||
| 1028 | Feature: Get or Set the time to join the network(unit: minutes). | ||
| 1029 | |||
| 1030 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+CSQTIME** | ||
| 1031 | |||
| 1032 | Example: AT+CSQTIME=10 ~/~/ Set the search time to 10 minutes. | ||
| 1033 | |||
| 1034 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x13(%%)** | ||
| 1035 | |||
| 1036 | Format: Command Code (0x13) followed by 1 byte. | ||
| 1037 | |||
| 1038 | Example: Downlink Payload: **13 0A **~/~/ AT+CSQTIME=10 | ||
| 1039 | |||
| 1040 | |||
| 1041 | == 3.16 Set the IPv4 or IPv6 == | ||
| 1042 | |||
| 1043 | |||
| 1044 | This command is used to set IP version. | ||
| 1045 | |||
| 1046 | (% style="color:blue" %)**AT Command: ** | ||
| 1047 | |||
| 1048 | * (% style="color:#037691" %)**AT+IPTYPE=1**(%%)** **~/~/ IPv4 | ||
| 1049 | * (% style="color:#037691" %)**AT+IPTYPE=2**(%%)** **~/~/ IPv6 | ||
| 1050 | |||
| 1051 | == 3.17 Configure Network Category to be Searched for under LTE RAT. == | ||
| 1052 | |||
| 1053 | |||
| 1054 | (% style="color:blue" %)**AT Command:**(%%)** (% style="color:#037691" %)AT+IOTMOD=xx(%%)** | ||
| 1055 | |||
| 1056 | (% style="color:#037691" %)**xx:**(%%)** 0:** eMTC | ||
| 1057 | |||
| 1058 | **1:** NB-IoT | ||
| 1059 | |||
| 1060 | **2:** eMTC and NB-IoT | ||
| 1061 | |||
| 1062 | |||
| 1063 | == 3.18 Factory data reset == | ||
| 1064 | |||
| 1065 | |||
| 1066 | Two different restore factory Settings configurations. | ||
| 1067 | |||
| 1068 | (% style="color:blue" %)**AT command:** | ||
| 1069 | |||
| 1070 | * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default. | ||
| 1071 | * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values **except for passwords**. | ||
| 1072 | |||
| 1073 | == 3.19 Set CoAP option == | ||
| 1074 | |||
| 1075 | |||
| 1076 | Feature: Set CoAP option, follow this link to set up the CoaP protocol. | ||
| 1077 | |||
| 1078 | (% style="color:blue" %)**AT command: **(% style="color:#037691; font-weight:bold" %)**AT+URI1~~AT+URI8** | ||
| 1079 | |||
| 1080 | (% style="color:#037691; font-weight:bold" %)**AT+URI1=11,"i"**(%%)** **~/~/ "i/" indicates that the endpoint supports observation mode. In -CB products, fixed setting AT+URI1=11,"i" | ||
| 1081 | |||
| 1082 | (% style="color:#037691; font-weight:bold" %)**AT+URI2=11,"CoAP endpoint URl"**(%%)** **~/~/ 11 is a fixed parameter. | ||
| 1083 | |||
| 1084 | **Example: ** i/13a35fbe-9515-6e55-36e8-081fb6aacf86 | ||
| 1085 | |||
| 1086 | AT+URI1=11,"i" | ||
| 1087 | |||
| 1088 | AT+URI2=11,"13a35fbe-9515-6e55-36e8-081fb6aacf86" | ||
| 1089 | |||
| 1090 | ~-~-> If multiple groups of CoAP endpoint urls: | ||
| 1091 | |||
| 1092 | AT+URI3=11,"i" | ||
| 1093 | |||
| 1094 | AT+URI4=11,"CoAP endpoint URl" | ||
| 1095 | |||
| 1096 | This command sets the connection parameters of the COAP. | ||
| 1097 | |||
| 1098 | |||
| 1099 | == 3.20 Power on / power off BG95 module == | ||
| 1100 | |||
| 1101 | |||
| 1102 | This command is used to power on and power off BG95 module. | ||
| 1103 | |||
| 1104 | * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+QSW(%%)** | ||
| 1105 | |||
| 1106 | The module is powered on after the command is sent for the first time, and powered off after the command is sent again. | ||
| 1107 | |||
| 1108 | [[image:image-20240619155719-1.png||height="644" width="811"]] | ||
| 1109 | |||
| 1110 | |||
| 1111 | == 3.21 Uplink log query == | ||
| 1112 | |||
| 1113 | |||
| 1114 | * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+GETLOG(%%)** | ||
| 1115 | |||
| 1116 | This command can be used to query upstream logs of data packets. | ||
| 1117 | |||
| 1118 | [[image:image-20250120102551-1.png]] | ||
| 1119 | |||
| 1120 | |||
| 1121 | == 3.22 Setting the sensor address == | ||
| 1122 | |||
| 1123 | |||
| 1124 | Function:Change the sensor address to 0x01, 0x02, 0x03, 0x04 | ||
| 1125 | |||
| 1126 | (% style="color:red" %)**(Note:When setting the address of the sensor, you need to connect the device individually for each one, and when modifying the address, you can't connect more than one sensor at the same time, otherwise it will be impossible to modify it, and when modifying it, you need to connect the yellow wire to VBAT_OUT, and after modifying it, you need to disconnect it.)** | ||
| 1127 | |||
| 1128 | (% style="color:blue" %)**AT Command: AT+MADD** | ||
| 1129 | |||
| 1130 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
| 1131 | |=(% 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** | ||
| 1132 | |(% style="width:154px" %)AT+MADD=1|(% style="width:196px" %)Set sensor address to 01|(% style="width:157px" %)((( | ||
| 1133 | Successfully modified sensor address to 0x01 | ||
| 1134 | |||
| 1135 | |||
| 1136 | OK | ||
| 1137 | ))) | ||
| 1138 | |(% style="width:154px" %)AT+MADD=2|(% style="width:196px" %)Set sensor address to 02|(% style="width:157px" %)((( | ||
| 1139 | Successfully modified sensor address to 0x02 | ||
| 1140 | |||
| 1141 | |||
| 1142 | OK | ||
| 1143 | ))) | ||
| 1144 | |||
| 1145 | (% style="color:blue" %)**Downlink Command:** | ||
| 1146 | |||
| 1147 | No downlink command for this feature. | ||
| 1148 | |||
| 1149 | |||
| 1150 | == 3.23 Domain name resolution settings == | ||
| 1151 | |||
| 1152 | |||
| 1153 | Feature: Set dynamic domain name resolution IP. | ||
| 1154 | |||
| 1155 | (% style="color:blue" %)**AT command: AT+BKDNS** | ||
| 1156 | |||
| 1157 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
| 1158 | |=(% style="width: 138px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 229px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation** | ||
| 1159 | |(% style="width:134px" %)((( | ||
| 1160 | AT+BKDNS=? | ||
| 1161 | )))|(% style="width:143px" %)Get current Settings|(% style="width:606px" %)((( | ||
| 1162 | 0,0,NULL (default) | ||
| 1163 | OK | ||
| 1164 | ))) | ||
| 1165 | |(% colspan="1" rowspan="3" style="width:134px" %)((( | ||
| 1166 | |||
| 1167 | |||
| 1168 | |||
| 1169 | |||
| 1170 | |||
| 1171 | |||
| 1172 | |||
| 1173 | |||
| 1174 | |||
| 1175 | |||
| 1176 | |||
| 1177 | AT+BKDNS=a,b,c | ||
| 1178 | )))|(% style="width:143px" %)((( | ||
| 1179 | **a**: Enable/Disable dynamic domain name resolution. | ||
| 1180 | )))|(% style="width:606px" %)**1**: Disable dynamic domain name update. The ip address will be saved after the domain name is resolved, if the next domain name resolution fails, the last saved ip address will be used. | ||
| 1181 | **2**: Enable dynamic domain name update. The ip address will be saved after domain name resolution, if the next domain name resolution fails, the last saved ip address will be used, and the domain name resolution will be updated regularly according to the time set by the customer. | ||
| 1182 | |(% style="width:143px" %)**b**: Set the time to update the domain name resolution at regular intervals.|(% style="width:606px" %)((( | ||
| 1183 | Unit: hour | ||
| 1184 | ))) | ||
| 1185 | |(% style="width:143px" %)((( | ||
| 1186 | **c**: Set the IP address manually. | ||
| 1187 | )))|(% style="width:606px" %)((( | ||
| 1188 | The format is the same as AT+SERVADDR. | ||
| 1189 | If domain name resolution fails, this ip address will be used directly, if domain name resolution succeeds, parameter c will be updated to the successfully resolved IP address. | ||
| 1190 | ))) | ||
| 1191 | |||
| 1192 | **Example:** | ||
| 1193 | |||
| 1194 | * AT+BKDNS=1,0 ~/~/ Dynamic domain name resolution is disabled. | ||
| 1195 | * AT+BKDNS=2,1 ~/~/ The dynamic domain name resolution function is enabled and the automatic update time is set to 1 hour. | ||
| 1196 | * AT+BKDNS=2,4,3.69.98.183,1883 ~/~/ The dynamic domain name resolution function is enabled and the automatic update time is set to 4 hour, and manually set the ip address, if the domain name failed to resolve, it will directly use this ip to communicate. When the next domain name resolution is successful, it will be updated to the ip address of the successful resolution. | ||
| 1197 | |||
| 1198 | (% style="color:blue" %)**Downlink Command: ** | ||
| 1199 | |||
| 1200 | No downlink commands for feature | ||
| 1201 | |||
| 1202 | |||
| 1203 | == 3.24 Set the downlink debugging mode == | ||
| 1204 | |||
| 1205 | |||
| 1206 | Feature: Set the conversion between the standard version and 1T version downlinks. | ||
| 1207 | |||
| 1208 | (% style="color:blue" %)**AT command: AT+DOWNTE** | ||
| 1209 | |||
| 1210 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
| 1211 | |=(% style="width: 134px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 233px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation** | ||
| 1212 | |(% style="width:134px" %)AT+DOWNTE=?|(% style="width:143px" %)Get current Settings|(% style="width:229px" %)((( | ||
| 1213 | 0,0 (default) | ||
| 1214 | |||
| 1215 | OK | ||
| 1216 | ))) | ||
| 1217 | |(% colspan="1" rowspan="2" style="width:134px" %)((( | ||
| 1218 | |||
| 1219 | |||
| 1220 | |||
| 1221 | |||
| 1222 | AT+DOWNTE=a,b | ||
| 1223 | )))|(% style="width:143px" %)**a**: Set the conversion between the downlink of the standard version and 1T version|(% style="width:229px" %)((( | ||
| 1224 | **0**: Set the downlink of the standard version. | ||
| 1225 | **1**: Set the downlink of the 1T version(ThingsEye platform) | ||
| 1226 | ))) | ||
| 1227 | |(% style="width:143px" %)**b**: Enable/Disable downlink debugging|(% style="width:229px" %)((( | ||
| 1228 | **0**: Disable downlink debugging mode. | ||
| 1229 | **1**: Enable downlink debugging mode, users can see the original downlink reception. | ||
| 1230 | ))) | ||
| 1231 | |||
| 1232 | **Example:** | ||
| 1233 | |||
| 1234 | * AT+DOWNTE=0,1 ~/~/ Set to standard version downlink, and enable downlink debugging. | ||
| 1235 | * AT+DOWNTE=1,1 ~/~/ Set to 1T version downlink, and enable downlink debugging. | ||
| 1236 | |||
| 1237 | (% style="color:blue" %)**Downlink Command: ** | ||
| 1238 | |||
| 1239 | No downlink commands for feature | ||
| 1240 | |||
| 1241 | |||
| 1242 | == 3.25 Domain name resolution settings(Since firmware v1.1.1) == | ||
| 1243 | |||
| 1244 | |||
| 1245 | Feature: Set static DNS resolution IP address. | ||
| 1246 | |||
| 1247 | (% style="color:blue" %)**AT command: AT+BKDNS** | ||
| 1248 | |||
| 1249 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
| 1250 | |=(% style="width: 138px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 229px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation** | ||
| 1251 | |(% style="width:134px" %)((( | ||
| 1252 | AT+BKDNS=? | ||
| 1253 | )))|(% style="width:143px" %)Get current Settings|(% style="width:606px" %)((( | ||
| 1254 | 1,0,NULL (default) | ||
| 1255 | OK | ||
| 1256 | ))) | ||
| 1257 | |(% colspan="1" rowspan="3" style="width:134px" %)((( | ||
| 1258 | |||
| 1259 | |||
| 1260 | |||
| 1261 | |||
| 1262 | |||
| 1263 | |||
| 1264 | AT+BKDNS=a,b,c | ||
| 1265 | )))|(% style="width:143px" %)((( | ||
| 1266 | **a**: Enable/Disable static DNS resolution. | ||
| 1267 | )))|(% style="width:606px" %)((( | ||
| 1268 | **0:** Disable static DNS resolution | ||
| 1269 | |||
| 1270 | **1**: Enable static DNS resolution. The ip address will be saved after the domain name is resolved, if the next domain name resolution fails, the last saved ip address will be used. | ||
| 1271 | ))) | ||
| 1272 | |(% style="width:143px" %)**b**: Meaningless.|(% style="width:606px" %)((( | ||
| 1273 | Set to **0**. | ||
| 1274 | ))) | ||
| 1275 | |(% style="width:143px" %)((( | ||
| 1276 | **c**: Set the IP address manually. | ||
| 1277 | )))|(% style="width:606px" %)((( | ||
| 1278 | The format is the same as AT+SERVADDR. | ||
| 1279 | If domain name resolution fails, this ip address will be used directly, if domain name resolution succeeds, parameter c will be updated to the successfully resolved IP address. | ||
| 1280 | ))) | ||
| 1281 | |||
| 1282 | **Example:** | ||
| 1283 | |||
| 1284 | * AT+BKDNS=0,0,NULL ~/~/Disable static DNS resolution. | ||
| 1285 | * AT+BKDNS=1,0,NULL ~/~/ Enable static DNS resolution. | ||
| 1286 | * AT+BKDNS=1,0,3.69.98.183,1883 ~/~/Enable static DNS resolution, if domain name resolution succeeds, the node uses the ip address successfully resolved and saves it to parameter c. If the domain name resolution fails, use the manually set ip address: 3.69.98.183 for communication. | ||
| 1287 | |||
| 1288 | (% style="color:blue" %)**Downlink Command: ** | ||
| 1289 | |||
| 1290 | No downlink commands for feature. | ||
| 1291 | |||
| 1292 | |||
| 1293 | = 4. Battery & Power Consumption = | ||
| 1294 | |||
| 1295 | |||
| 1296 | SE0X-CB use ER26500 + SPC1520 battery pack and SE0X-NS use 3000mAh Recharable Battery with Solar Panel. See below link for detail information about the battery info and how to replace. | ||
| 1297 | |||
| 1298 | [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
| 1299 | |||
| 1300 | |||
| 1301 | = 5. Firmware update = | ||
| 1302 | |||
| 1303 | User can change device firmware to: | ||
| 1304 | |||
| 1305 | * Update with new features. | ||
| 1306 | |||
| 1307 | * Fix bugs. | ||
| 1308 | |||
| 1309 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/scl/fo/ka61pfdm62yev2xnzj1mv/AEVi2bMMldXjJDemncPxaHg?rlkey=6jab77v39cig7af9c96g4vg7y&st=bxtrnxr5&dl=0]]** | ||
| 1310 | |||
| 1311 | Methods to Update Firmware: | ||
| 1312 | |||
| 1313 | * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]]. | ||
| 1314 | |||
| 1315 | * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**. | ||
| 1316 | |||
| 1317 | ((( | ||
| 1318 | |||
| 1319 | ))) | ||
| 1320 | |||
| 1321 | = 6. FAQ = | ||
| 1322 | |||
| 1323 | == 6.1 AT Commands input doesn't work == | ||
| 1324 | |||
| 1325 | |||
| 1326 | In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. | ||
| 1327 | |||
| 1328 | |||
| 1329 | == 6.2 Can I calibrate SE0X-CB/CS to different soil types? == | ||
| 1330 | |||
| 1331 | |||
| 1332 | SE0X-CB/CS can be used to measure EC/Moisture in different type of soil event concrete. | ||
| 1333 | |||
| 1334 | ((( | ||
| 1335 | SE0X-CB/CS is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20230522.pdf]]. | ||
| 1336 | ))) | ||
| 1337 | |||
| 1338 | |||
| 1339 | = 7. Order Info = | ||
| 1340 | |||
| 1341 | |||
| 1342 | **Part Number: (% style="color:blue" %)SE0X-CB/CS-XX (%%)** | ||
| 1343 | |||
| 1344 | (% style="color:red" %)**XX**(%%): | ||
| 1345 | |||
| 1346 | * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card) | ||
| 1347 | |||
| 1348 | * (% style="color:#037691" %)**1T**(%%): with 1NCE * 10 years 500MB SIM card and Pre-configure to ThingsEye server | ||
| 1349 | |||
| 1350 | = 8. Packing Info = | ||
| 1351 | |||
| 1352 | |||
| 1353 | (% style="color:#037691" %)**Package Includes**: | ||
| 1354 | |||
| 1355 | * SE0X-CB/CS NB-IoT Soil Moisture & EC Sensor Transmitter | ||
| 1356 | |||
| 1357 | * External antenna x 1 | ||
| 1358 | |||
| 1359 | (% style="color:#037691" %)**Dimension and weight**: | ||
| 1360 | |||
| 1361 | * Device Size: cm | ||
| 1362 | |||
| 1363 | * Device Weight: g | ||
| 1364 | |||
| 1365 | * Package Size / pcs : cm | ||
| 1366 | |||
| 1367 | * Weight / pcs : g | ||
| 1368 | |||
| 1369 | = 9. Support = | ||
| 1370 | |||
| 1371 | |||
| 1372 | * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. | ||
| 1373 | |||
| 1374 | * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]]. |