Wiki source code of WSC2-C -- Weather Station Kit User Manual
Last modified by Mengting Qiu on 2025/03/14 16:57
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | (% style="text-align:center" %) | ||
| 4 | [[image:image-20240707214707-1.png||height="476" width="570"]] | ||
| 5 | |||
| 6 | |||
| 7 | |||
| 8 | |||
| 9 | |||
| 10 | |||
| 11 | |||
| 12 | **Table of Contents:** | ||
| 13 | |||
| 14 | {{toc/}} | ||
| 15 | |||
| 16 | |||
| 17 | |||
| 18 | |||
| 19 | |||
| 20 | |||
| 21 | |||
| 22 | |||
| 23 | |||
| 24 | = 1. Introduction = | ||
| 25 | |||
| 26 | == 1.1 Overview == | ||
| 27 | |||
| 28 | |||
| 29 | The Dragino (% style="color:blue" %)**Weather Station Kit**(%%) is designed for **measuring atmospheric conditions** to provide information for weather forecasts and to study the weather and climate. | ||
| 30 | |||
| 31 | The Weather Station Kit includes (% style="color:blue" %)**a NB transmitter WSC2-C, a 9 in 1 Weather Station WSS-09 and a Rain Gauge WSS-08**. | ||
| 32 | |||
| 33 | (% style="color:blue" %)**Please note that the WSC2-C only includes the transmitter, and the 9 in 1 Weather Station WSS-09 and Rain Gauge WSS-08 need to be purchased separately.** | ||
| 34 | |||
| 35 | The 9 in 1 weather station kit can measure below values: (% style="color:blue" %)**Wind Speed, Wind Direction, Temperature, Humidity, Air Pressure, Illumination, PM2.5, PM10, Noise & Rain Gauge**(%%). | ||
| 36 | |||
| 37 | The NB transmitter use RS485 interface to communicate with the 9 in 1 weather station. It can also connect (% style="color:blue" %)**3rd party RS485 sensors**(%%) to measure more environment data. It also has a pulse counting input which can be used to connect (% style="color:blue" %)**tipping bucket Rain Gauge**(%%). | ||
| 38 | |||
| 39 | WSC2-C 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. | ||
| 40 | |||
| 41 | *make sure you have NB-IoT or CAT-M1 coverage locally. | ||
| 42 | |||
| 43 | |||
| 44 | == 1.2 Features & Spec for WSC2-C Transmitter == | ||
| 45 | |||
| 46 | |||
| 47 | * For -NB Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 | ||
| 48 | * For -CB Bands: B1/B2/B3/B4/B5/B8/B12/B13~/~/B18/B19/B20/B25/B28/B66/B71/B85 | ||
| 49 | * CAT-M1 / LTE-M Bands: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 | ||
| 50 | * Ultra-low power consumption | ||
| 51 | * Support WSS09 9 in 1 Sensors: Wind Speed, Wind Direction, Temperature, Humidity, Air Pressure, Illumination, PM2.5, PM10, Noise & Rain Gauge | ||
| 52 | * RS485 Interface for 3rd party Sensors | ||
| 53 | * Support WSS08 optical Rain Gauge or tipping bucket Rain Gauge | ||
| 54 | * Support Bluetooth v5.1 remote configure and update firmware | ||
| 55 | * Support wireless OTA update firmware | ||
| 56 | * AT Commands to change parameters | ||
| 57 | * Uplink on periodically | ||
| 58 | * Downlink to change configure | ||
| 59 | * IP66 Waterproof Enclosure | ||
| 60 | * 1000mAh Rechargeable Li-ion Battery | ||
| 61 | * Input and Recharge power: 12v | ||
| 62 | * Nano SIM card slot for NB-IoT SIM | ||
| 63 | |||
| 64 | == 1.3 Specification for WSS-09 9 in 1 weather sensors == | ||
| 65 | |||
| 66 | [[image:image-20240708092247-1.png]] | ||
| 67 | |||
| 68 | More Detail: [[WSS09-1 Manual.>>doc:Main.Agriculture & Weather Stations.WebHome||anchor="H1.WSS099in1WeatherStationSensor"]] | ||
| 69 | |||
| 70 | |||
| 71 | (% style="color:blue" %)**Wind Speed:** | ||
| 72 | |||
| 73 | * Range: 0~~60m/s | ||
| 74 | * Accuracy: ±(0.2m/s±0.02*v)(v : the wind speed) | ||
| 75 | * Ultrasonic measurement,no start wind strength needed | ||
| 76 | |||
| 77 | (% style="color:blue" %)**Wind Direction:** | ||
| 78 | |||
| 79 | * Range: 0~~3599 | ||
| 80 | * Accuracy: +3° | ||
| 81 | * Ultrasonic measurement,no start wind strength needed | ||
| 82 | * Built-in electronic compass. No need to consider installation direction | ||
| 83 | |||
| 84 | (% style="color:blue" %)**Temperature:** | ||
| 85 | |||
| 86 | * Range: -40°C ~~ +80°C | ||
| 87 | * Accuracy: +0.5°C | ||
| 88 | |||
| 89 | (% style="color:blue" %)**Humidity:** | ||
| 90 | |||
| 91 | * Range: 0 ~~ 99% RH | ||
| 92 | * Accuracy Tolerance : Typ +3% RH | ||
| 93 | |||
| 94 | (% style="color:blue" %)**Air Pressure:** | ||
| 95 | |||
| 96 | * Accuracy: ±0.15kPa@25°C 101kPa | ||
| 97 | * Range: 0~~120kPa | ||
| 98 | |||
| 99 | (% style="color:blue" %)**Noise:** | ||
| 100 | |||
| 101 | * Range: 30dB~~120dB | ||
| 102 | * Accuracy: +0.5dB | ||
| 103 | |||
| 104 | (% style="color:blue" %)**PM2.5:** | ||
| 105 | |||
| 106 | * Range: 0~~1000ug/m3 | ||
| 107 | * Accuracy: ±3%FS | ||
| 108 | * Resolution: 1ug/m3 | ||
| 109 | |||
| 110 | (% style="color:blue" %)**PM10:** | ||
| 111 | |||
| 112 | * Range: 0~~1000ug/m3 | ||
| 113 | * Accuracy: +3%FS | ||
| 114 | * Resolution: 1ug/m3 | ||
| 115 | |||
| 116 | (% style="color:blue" %)**llumination:** | ||
| 117 | |||
| 118 | * Range: 0~~200k Lux | ||
| 119 | * Accuracy: +7%(25 °C) | ||
| 120 | |||
| 121 | == 1.4 Specification for WSS-08 Optical Rain Guage == | ||
| 122 | |||
| 123 | [[image:image-20240707215336-2.png||height="159" width="218"]] | ||
| 124 | |||
| 125 | * Input Power: 9~~30 VDC | ||
| 126 | * Sense diameter: 6cm | ||
| 127 | * Pulse Output | ||
| 128 | |||
| 129 | More Detail: [[WSS-08 Manual.>>doc:Main.Agriculture & Weather Stations.WebHome||anchor="H2.WSS08OpticalRangeGuage"]] | ||
| 130 | |||
| 131 | = 2. How to use = | ||
| 132 | |||
| 133 | == 2.1 Installation == | ||
| 134 | |||
| 135 | |||
| 136 | Below is an installation example for the weather station. Field installation example can be found at [[Appendix I: Field Installation Photo.>>||anchor="H12.AppendixI:FieldInstallationPhoto"]] | ||
| 137 | |||
| 138 | [[image:image-20250116134451-1.jpeg||height="482" width="1016"]] | ||
| 139 | |||
| 140 | |||
| 141 | (% style="color:blue" %)** Wiring:** | ||
| 142 | |||
| 143 | 1. WSC2-C and sensors all powered by solar power via MPPT | ||
| 144 | 1. WSC2-C Weather Station Kit already include 9 sensors. | ||
| 145 | 1. Possible to add optional 3rd sensors to measure more parameter | ||
| 146 | |||
| 147 | (% style="color:red" %)**Notice 1:** | ||
| 148 | |||
| 149 | * All weather sensors and WSC2-C are powered by MPPT solar recharge controller. MPPT is connected to solar panel and storage battery. | ||
| 150 | * Weather sensors won't work if solar panel and storage battery fails. | ||
| 151 | |||
| 152 | (% style="color:red" %)**Notice 2:** | ||
| 153 | |||
| 154 | Due to shipment and importation limitation, user is better to purchase below parts locally: | ||
| 155 | |||
| 156 | * Solar Panel | ||
| 157 | * Storage Battery | ||
| 158 | * MPPT Solar Recharger | ||
| 159 | * Cabinet. | ||
| 160 | |||
| 161 | == 2.2 Send data to IoT server via NB-IoT network == | ||
| 162 | |||
| 163 | |||
| 164 | ((( | ||
| 165 | The WSC2-C is equipped with a NB-IoT module, the pre-loaded firmware in WSC2-C 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 WSC2-C. | ||
| 166 | ))) | ||
| 167 | |||
| 168 | |||
| 169 | Below shows the network structure: | ||
| 170 | |||
| 171 | [[image:image-20250116134502-2.jpeg||height="477" width="1005"]] | ||
| 172 | |||
| 173 | There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1T**(%%) version of WSC2-C. | ||
| 174 | |||
| 175 | |||
| 176 | (% 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 WSC2-C send data to IoT server. | ||
| 177 | |||
| 178 | * Install NB-IoT SIM card and configure APN. See instruction of [[Attach Network>>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/#H2.AttachNetwork]]. | ||
| 179 | |||
| 180 | * 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]]. | ||
| 181 | |||
| 182 | Below shows result of different server as a glance. | ||
| 183 | |||
| 184 | (% border="1" cellspacing="3" style="width:515px" %) | ||
| 185 | |(% 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** | ||
| 186 | |(% 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" %)((( | ||
| 187 | [[image:image-20250113195417-4.png]] | ||
| 188 | )))|(% style="width:170px" %) | ||
| 189 | |(% 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" %)((( | ||
| 190 | [[image:image-20250113195357-3.png]] | ||
| 191 | )))|(% style="width:170px" %) | ||
| 192 | |(% 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" %)[[image:image-20250113195545-5.png]]|(% style="width:170px" %) | ||
| 193 | |(% 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" %) | ||
| 194 | |(% 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" %) | ||
| 195 | |(% 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" %)((( | ||
| 196 | [[image:image-20250113195349-2.png]] | ||
| 197 | )))|(% style="width:170px" %) | ||
| 198 | |(% 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" %)((( | ||
| 199 | [[image:image-20250113195339-1.png]] | ||
| 200 | )))|(% style="width:170px" %) | ||
| 201 | |||
| 202 | (% 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 WSC2-C 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/]]. | ||
| 203 | |||
| 204 | |||
| 205 | == 2.3 Payload Types == | ||
| 206 | |||
| 207 | |||
| 208 | To meet different server requirement, WSC2-C supports different payload type. | ||
| 209 | |||
| 210 | **Includes:** | ||
| 211 | |||
| 212 | * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5) | ||
| 213 | |||
| 214 | * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0) | ||
| 215 | |||
| 216 | * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1) | ||
| 217 | |||
| 218 | * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3) | ||
| 219 | |||
| 220 | User can specify the payload type when choose the connection protocol. Example: | ||
| 221 | |||
| 222 | |||
| 223 | (% style="color:#037691" %)**AT+PRO=1,0** (%%) ~/~/ Use COAP Connection & hex Payload | ||
| 224 | |||
| 225 | (% style="color:#037691" %)**AT+PRO=1,5** (%%) ~/~/ Use COAP Connection & Json Payload | ||
| 226 | |||
| 227 | (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload | ||
| 228 | |||
| 229 | (% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload | ||
| 230 | |||
| 231 | (% style="color:#037691" %)**AT+PRO=3,0** (%%) ~/~/ Use MQTT Connection & hex Payload | ||
| 232 | |||
| 233 | (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload | ||
| 234 | |||
| 235 | (% style="color:#037691" %)**AT+PRO=4,0** (%%) ~/~/ Use TCP Connection & hex Payload | ||
| 236 | |||
| 237 | (% style="color:#037691" %)**AT+PRO=4,5 ** (%%) ~/~/ Use TCP Connection & Json Payload | ||
| 238 | |||
| 239 | **Since firmware V1.1.0**, (% style="color:#4472c4" %)**IMSI**(%%) has been added to payload. | ||
| 240 | |||
| 241 | |||
| 242 | === 2.3.1 General Json Format(Type~=5) === | ||
| 243 | |||
| 244 | This is the **PMMOD=1** generic Json format. It is shown below: | ||
| 245 | |||
| 246 | (% style="color:#4472c4" %)**{"IMEI":"868508065628110","IMSI":"460240210507481","Model":"WSC2-C","payload_ver":0,"rain_count":120.00,"wind_speed":0.58,"wind_level":1,"wind_direction":3,"wind_angel":136,"humidity":43.1,"temperature":21.0,"voise":52.1,"PM2_5":41,"PM10":58,"pressure":101.8,"illumination":650,"interrupt":0,"interrupt_level":0,"battery":3.27,"signal":27,"time":"2025-01-18T01:22:56Z","latitude":0.000000,"longitude":0.000000,"gps_time":"2025-01-18T01:07:06Z"}** | ||
| 247 | |||
| 248 | [[image:image-20250118092344-2.png]] | ||
| 249 | |||
| 250 | |||
| 251 | This is the **PMMOD=0** generic Json format. It is shown below: | ||
| 252 | |||
| 253 | (% style="color:#4472c4" %)**{"IMEI":"868508065628110","IMSI":"460240210507481","Model":"WSC2-C","payload_ver":1,"rain_count":120.00,"wind_speed":0.27,"wind_level":1,"wind_direction":5,"wind_angel":229,"humidity":38.5,"temperature":24.1,"voise":62.4,"CO2":34,"pressure":101.1,"illumination":646,"interrupt":0,"interrupt_level":0,"battery":3.33,"signal":28,"time":"2025-01-20T05:37:16Z","latitude":0.000000,"longitude":0.000000,"gps_time":"2025-01-20T04:01:08Z"}** | ||
| 254 | |||
| 255 | [[image:image-20250120133930-1.png]] | ||
| 256 | |||
| 257 | |||
| 258 | (% style="color:red" %)**Notice, from above payload:** | ||
| 259 | |||
| 260 | If set to **PMMOD=1**, the following data will be uploaded: | ||
| 261 | |||
| 262 | * BAT,Singal,Mod,Interrupt,Interrupt_level,payload_ver,exit_count,wind_speed,wind_level,wind_direction,wind_angel, humidity,temperature,voise,PM2_5,PM10,pressure,illumination,flag,DIY Sensors(A1~~A4),Timestamp | ||
| 263 | |||
| 264 | If set to **PMMOD=0**, the following data will be uploaded | ||
| 265 | |||
| 266 | * BAT,Singal,Mod,Interrupt,Interrupt_level,payload_ver,exit_count,wind_speed,wind_level,wind_direction,wind_angel, humidity,temperature,voise,PM2_5,PM10,pressure,illumination,flag,DIY Sensors(A1~~A4),Timestamp | ||
| 267 | |||
| 268 | === 2.3.2 HEX format Payload(Type~=0) === | ||
| 269 | |||
| 270 | ==== a. This is the hex format of PMMOD~=1. ==== | ||
| 271 | |||
| 272 | (% class="wikigeneratedid" %) | ||
| 273 | It is shown below: | ||
| 274 | |||
| 275 | (% style="color:#4472c4" %)**f868508065628110f4602402105074816e6e0cbc1a01000001000004b00016000100060110017000e402330023003203f90000028a810aa20352fc30678b19740000000000000000678b098f** | ||
| 276 | |||
| 277 | [[image:image-20250118113309-6.png]] | ||
| 278 | |||
| 279 | [[image:image-20250118113344-7.png]] | ||
| 280 | |||
| 281 | (% style="color:blue" %)**Version:** | ||
| 282 | |||
| 283 | These bytes include the hardware and software version. | ||
| 284 | |||
| 285 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x6e for WSC2-C | ||
| 286 | |||
| 287 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x6e=110, means firmware version 1.1.0 | ||
| 288 | |||
| 289 | |||
| 290 | (% style="color:blue" %)**BAT (Battery Info):** | ||
| 291 | |||
| 292 | Ex1: 0x0cbc = 3260mV/1000= 3.260V | ||
| 293 | |||
| 294 | |||
| 295 | (% style="color:blue" %)**Signal Strength:** | ||
| 296 | |||
| 297 | NB-IoT Network signal Strength. | ||
| 298 | |||
| 299 | **Ex1: 0x1a = 26** | ||
| 300 | |||
| 301 | **0** -113dBm or less | ||
| 302 | |||
| 303 | **1** -111dBm | ||
| 304 | |||
| 305 | **2...30** -109dBm... -53dBm | ||
| 306 | |||
| 307 | **31** -51dBm or greater | ||
| 308 | |||
| 309 | **99** Not known or not detectable | ||
| 310 | |||
| 311 | |||
| 312 | (% style="color:blue" %)**Interrupt:** | ||
| 313 | |||
| 314 | This data field shows if this packet is generated by interrupt or not. | ||
| 315 | |||
| 316 | **Example:** | ||
| 317 | |||
| 318 | If byte[0]&0x01=0x00 : Normal uplink packet. | ||
| 319 | |||
| 320 | If byte[0]&0x01=0x01 : Interrupt Uplink Packet. | ||
| 321 | |||
| 322 | |||
| 323 | (% style="color:blue" %)**Interrupt_level:** | ||
| 324 | |||
| 325 | This byte shows whether the interrupt is triggered by a high or low level. | ||
| 326 | |||
| 327 | **Ex1:** 0x00 Interrupt triggered by falling edge (low level) | ||
| 328 | |||
| 329 | **Ex2: **0x01 Interrupt triggered by rising edge (high level) | ||
| 330 | |||
| 331 | |||
| 332 | (% style="color:blue" %)**payload_ver: ** | ||
| 333 | |||
| 334 | The payload version number is used to parse different decodes. | ||
| 335 | |||
| 336 | **Ex2: **0x01 Payload decoding version v1.0.0 | ||
| 337 | |||
| 338 | |||
| 339 | (% style="color:blue" %)**exit_count: ** | ||
| 340 | |||
| 341 | Converted to rainfall based on the number of interruptions, | ||
| 342 | |||
| 343 | **Ex1:** | ||
| 344 | |||
| 345 | bytes[54]&0x0F(hex) / bytes[55](hex) = 0x81&0x0F / 0x0a = 1 / 10=0.1mm((% style="color:red" %)**Note:Calculate the accuracy of the trigger one time to 0.1mm**(%%)) | ||
| 346 | |||
| 347 | bytes[10] | bytes[13] / 0.1mm = 0x000004b0(hex) * 0.1 = 1200(dec) * 0.1 = 120mm((% style="color:red" %)**Note:Use exit_count x precision = rainfall**(%%)) | ||
| 348 | |||
| 349 | |||
| 350 | (% style="color:blue" %)**wind_speed:** | ||
| 351 | |||
| 352 | Ex1: 0x0016(hex) / 100 = 22(dec) / 100 = 0.22m/s | ||
| 353 | |||
| 354 | |||
| 355 | (% style="color:blue" %)**wind_level:** | ||
| 356 | |||
| 357 | Ex1: 0x0001(hex) = 1(dec) | ||
| 358 | |||
| 359 | |||
| 360 | (% style="color:blue" %)**wind_direction:** | ||
| 361 | |||
| 362 | Ex1: 0x0006(hex) = 6(dec) | ||
| 363 | |||
| 364 | (% style="color:red" %)**Note: 0 for due north, increasing clockwise, 2 for due east** | ||
| 365 | |||
| 366 | |||
| 367 | (% style="color:blue" %)**wind_angel:** | ||
| 368 | |||
| 369 | Ex1: 0x0110(hex) = 272(dec) | ||
| 370 | |||
| 371 | (% style="color:red" %)**Note: Calculation: 0° clockwise increase in degrees for due north, 90° for due east** | ||
| 372 | |||
| 373 | |||
| 374 | (% style="color:blue" %)**Humidity: ** | ||
| 375 | |||
| 376 | Ex1: :0170(H)=368(D) Value: 368 / 10=36.8, So 36.8% | ||
| 377 | |||
| 378 | |||
| 379 | (% style="color:blue" %)**Temperature:** | ||
| 380 | |||
| 381 | If payload is: 00e4H: (00e4 & 8000 == 0), temp = 00e4H /10 = 22.8 degree | ||
| 382 | |||
| 383 | If payload is: FF3FH : (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. | ||
| 384 | |||
| 385 | (FF3F & 8000: Judge whether the highest bit is 1, when the highest bit is 1, it is negative) | ||
| 386 | |||
| 387 | |||
| 388 | (% style="color:blue" %)**Voise:** | ||
| 389 | |||
| 390 | Ex1:0x0233(H) = 563(D) Value: 563/10=56.3, So 56.3dB/y | ||
| 391 | |||
| 392 | |||
| 393 | (% style="color:blue" %)**PM2_5(CO2):** | ||
| 394 | |||
| 395 | Ex1: 0x0023(H) = 35(D) | ||
| 396 | |||
| 397 | |||
| 398 | (% style="color:blue" %)**PM10:** | ||
| 399 | |||
| 400 | Ex1: 0x0032(H) = 50(D) | ||
| 401 | |||
| 402 | |||
| 403 | (% style="color:blue" %)**Pressure:** | ||
| 404 | |||
| 405 | Ex1: 0x03f9(H) = 1017(D) Value: 1017/10= 101.7, So 101.7kPa | ||
| 406 | |||
| 407 | |||
| 408 | (% style="color:blue" %)**illumination:** | ||
| 409 | |||
| 410 | Ex1: 0x0000028a(H) = 650(D) Lux | ||
| 411 | |||
| 412 | |||
| 413 | (% style="color:blue" %)**Flag:** | ||
| 414 | |||
| 415 | (% style="color:#037691" %)**Higher byte:** | ||
| 416 | |||
| 417 | s_flag: (0x81>>6)&0x01= 000**1 **, A value of 1 for the last value means that the sensor has been recognized, and 0 means that, the sensor has not been recognized. | ||
| 418 | |||
| 419 | i_flag: (0x81>>5)&0x01 = 000**1 **, A last value of 1 means that the interrupt has been triggered, and 0 means that the interrupt has not been triggered. | ||
| 420 | |||
| 421 | (% style="color:#037691" %)**Low byte:** | ||
| 422 | |||
| 423 | Ext:0x0a = 10/100=0.1, This represents 0.1mm of rainfall per trigger conversion. | ||
| 424 | |||
| 425 | |||
| 426 | (% style="color:blue" %)**DIY Sensors(A1~~A4)** | ||
| 427 | |||
| 428 | Ex1: 0xa203fafc1e | ||
| 429 | |||
| 430 | **a2** : 485 Sensor Address | ||
| 431 | |||
| 432 | **03**: The sensor returns a total of 3 bytes | ||
| 433 | |||
| 434 | **fafc1e**: Hexadecimal data returned from sensor acquisition | ||
| 435 | |||
| 436 | (% style="color:red" %)**Note: **(%%)DIY sensor data needs to be set up before it has to go up with the device. (Setup reference link: [[Reference Links>>https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/WSC2-C--Weather_Station_Kit_User_Manual/#H3.3.3AddorDeleteRS485Sensor]]) | ||
| 437 | |||
| 438 | |||
| 439 | (% style="color:blue" %)**TimeStamp: ** | ||
| 440 | |||
| 441 | Unit TimeStamp Example: 678b098f(H) = 1737165199(D) | ||
| 442 | |||
| 443 | Put the decimal value into this link(https:~/~/www.epochconverter.com/) to get the time. | ||
| 444 | |||
| 445 | |||
| 446 | (% style="color:blue" %)**Latitude:** | ||
| 447 | |||
| 448 | **Example: **0x015A7A7A(H)=22706810(D)=22.706810 | ||
| 449 | |||
| 450 | |||
| 451 | (% style="color:blue" %)**Longitude:** | ||
| 452 | |||
| 453 | **Example: **0x06CF33CE(H)=114242510(D)=114.242510 | ||
| 454 | |||
| 455 | |||
| 456 | (% style="color:blue" %)**GPS Timestamp:** | ||
| 457 | |||
| 458 | Unit TimeStamp Example: 678b098f(H) = 1737165199(D) | ||
| 459 | |||
| 460 | Put the decimal value into this link(https:~/~/www.epochconverter.com/) to get the time. | ||
| 461 | |||
| 462 | |||
| 463 | |||
| 464 | ==== b. This is the hex format of PMMOD~=0. ==== | ||
| 465 | |||
| 466 | (% class="wikigeneratedid" %) | ||
| 467 | It is shown below: | ||
| 468 | |||
| 469 | (% style="color:#4472c4" %)**f868508065628110f4602402105074816e6e0d131c01000001000004b000110000000500dc01f000da01eb002f03f600000286010aa203fafc1e678dae100000000000000000678dad17** | ||
| 470 | |||
| 471 | [[image:image-20250120100524-2.png]] | ||
| 472 | |||
| 473 | [[image:image-20250120100538-3.png]] | ||
| 474 | |||
| 475 | (% style="color:blue" %)**Version:** | ||
| 476 | |||
| 477 | These bytes include the hardware and software version. | ||
| 478 | |||
| 479 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x3e for WSC2-C | ||
| 480 | |||
| 481 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x6e=110, means firmware version 1.1.0 | ||
| 482 | |||
| 483 | |||
| 484 | (% style="color:blue" %)**BAT (Battery Info):** | ||
| 485 | |||
| 486 | Ex1: 0x0d13 = 3347mV/1000= 3.347V | ||
| 487 | |||
| 488 | |||
| 489 | (% style="color:blue" %)**Signal Strength:** | ||
| 490 | |||
| 491 | NB-IoT Network signal Strength. | ||
| 492 | |||
| 493 | **Ex1: 0x1c = 28** | ||
| 494 | |||
| 495 | **0** -113dBm or less | ||
| 496 | |||
| 497 | **1** -111dBm | ||
| 498 | |||
| 499 | **2...30** -109dBm... -53dBm | ||
| 500 | |||
| 501 | **31** -51dBm or greater | ||
| 502 | |||
| 503 | **99** Not known or not detectable | ||
| 504 | |||
| 505 | |||
| 506 | (% style="color:blue" %)**Interrupt:** | ||
| 507 | |||
| 508 | This data field shows if this packet is generated by interrupt or not. | ||
| 509 | |||
| 510 | **Example:** | ||
| 511 | |||
| 512 | If byte[0]&0x01=0x00 : Normal uplink packet. | ||
| 513 | |||
| 514 | If byte[0]&0x01=0x01 : Interrupt Uplink Packet. | ||
| 515 | |||
| 516 | |||
| 517 | (% style="color:blue" %)**Interrupt_level:** | ||
| 518 | |||
| 519 | This byte shows whether the interrupt is triggered by a high or low level. | ||
| 520 | |||
| 521 | **Ex1:** 0x00 Interrupt triggered by falling edge (low level) | ||
| 522 | |||
| 523 | **Ex2: **0x01 Interrupt triggered by rising edge (high level) | ||
| 524 | |||
| 525 | |||
| 526 | (% style="color:blue" %)**payload_ver: ** | ||
| 527 | |||
| 528 | The payload version number is used to parse different decodes. | ||
| 529 | |||
| 530 | **Ex2: **0x01 Payload decoding version v1.0.0 | ||
| 531 | |||
| 532 | |||
| 533 | (% style="color:blue" %)**exit_count: ** | ||
| 534 | |||
| 535 | Converted to rainfall based on the number of interruptions, | ||
| 536 | |||
| 537 | **Ex1:** | ||
| 538 | |||
| 539 | bytes[54]&0x0F(hex) / bytes[55](hex) = 0x81&0x0F / 0x0a = 1 / 10=0.1mm((% style="color:red" %)**Note:Calculate the accuracy of the trigger one time to 0.1mm**(%%)) | ||
| 540 | |||
| 541 | bytes[10] | bytes[13] / 0.1mm = 0x 000004b0(hex) * 0.1 = 1200(dec) * 0.1 = 120mm((% style="color:red" %)**Note:Use exit_count x precision = rainfall**(%%)) | ||
| 542 | |||
| 543 | |||
| 544 | (% style="color:blue" %)**wind_speed:** | ||
| 545 | |||
| 546 | Ex1: 0x0011(hex) / 100 = 17(dec) / 100 = 0.17m/s | ||
| 547 | |||
| 548 | |||
| 549 | (% style="color:blue" %)**wind_level:** | ||
| 550 | |||
| 551 | Ex1: 0x0000(hex) = 0(dec) | ||
| 552 | |||
| 553 | |||
| 554 | (% style="color:blue" %)**wind_direction:** | ||
| 555 | |||
| 556 | Ex1: 0x0005(hex) = 5(dec) | ||
| 557 | |||
| 558 | (% style="color:red" %)**Note: 0 for due north, increasing clockwise, 2 for due east** | ||
| 559 | |||
| 560 | |||
| 561 | (% style="color:blue" %)**wind_angel:** | ||
| 562 | |||
| 563 | Ex1: 0x00dc(hex) = 220(dec) | ||
| 564 | |||
| 565 | (% style="color:red" %)**Note: Calculation: 0° clockwise increase in degrees for due north, 90° for due east** | ||
| 566 | |||
| 567 | |||
| 568 | (% style="color:blue" %)**Humidity: ** | ||
| 569 | |||
| 570 | Ex1: 0x01f0(H)=496(D) Value: 496 / 10=49.6, So 49.6% | ||
| 571 | |||
| 572 | |||
| 573 | (% style="color:blue" %)**Temperature:** | ||
| 574 | |||
| 575 | If payload is: 00da(H) : (00da & 8000 == 0), temp = 00da(H) /10 = 21.8 degree | ||
| 576 | |||
| 577 | If payload is: FF3F(H) : (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. | ||
| 578 | |||
| 579 | (FF3F & 8000: Judge whether the highest bit is 1, when the highest bit is 1, it is negative) | ||
| 580 | |||
| 581 | |||
| 582 | (% style="color:blue" %)**Voise:** | ||
| 583 | |||
| 584 | Ex1:0x01eb(H) = 491(D) Value: 491/10=49.1, So 49.1dB/y | ||
| 585 | |||
| 586 | |||
| 587 | (% style="color:blue" %)**CO2:** | ||
| 588 | |||
| 589 | Ex1: 0x002f(H) = 47(D) | ||
| 590 | |||
| 591 | |||
| 592 | (% style="color:blue" %)**Pressure:** | ||
| 593 | |||
| 594 | Ex1: 0x03f6(H) = 1014(D) Value: 1014/10= 101.4, So 101.4kPa | ||
| 595 | |||
| 596 | |||
| 597 | (% style="color:blue" %)**illumination:** | ||
| 598 | |||
| 599 | Ex1: 0x00000286(H) = 390(D) Lux | ||
| 600 | |||
| 601 | |||
| 602 | (% style="color:blue" %)**Flag:** | ||
| 603 | |||
| 604 | (% style="color:#037691" %)**Higher byte:** | ||
| 605 | |||
| 606 | s_flag: (0x01>>6)&0x01= 000**1 **, A value of 1 for the last value means that the sensor has been recognized, and 0 means that, the sensor has not been recognized. | ||
| 607 | |||
| 608 | i_flag: (0x01>>5)&0x01 = 000**1 **, A last value of 1 means that the interrupt has been triggered, and 0 means that the interrupt has not been triggered. | ||
| 609 | |||
| 610 | (% style="color:#037691" %)**Low byte:** | ||
| 611 | |||
| 612 | Ext:0x0a = 10/100=0.1, This represents 0.1mm of rainfall per trigger conversion. | ||
| 613 | |||
| 614 | |||
| 615 | (% style="color:blue" %)**DIY Sensors(A1~~A4)** | ||
| 616 | |||
| 617 | Ex1: 0xa203fafc1e | ||
| 618 | |||
| 619 | a2 : 485 Sensor Address | ||
| 620 | |||
| 621 | 03: The sensor returns a total of 3 bytes | ||
| 622 | |||
| 623 | fafc1e: Hexadecimal data returned from sensor acquisition | ||
| 624 | |||
| 625 | (% style="color:red" %)**Note: **(%%)DIY sensor data needs to be set up before it has to go up with the device. (Setup reference link: [[Reference Links>>https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/WSC2-C--Weather_Station_Kit_User_Manual/#H3.3.3AddorDeleteRS485Sensor]]) | ||
| 626 | |||
| 627 | |||
| 628 | (% style="color:blue" %)**TimeStamp: ** | ||
| 629 | |||
| 630 | Unit TimeStamp Example: 678dae10(H) = 1737338384(D) | ||
| 631 | |||
| 632 | Put the decimal value into this link(https:~/~/www.epochconverter.com/) to get the time. | ||
| 633 | |||
| 634 | |||
| 635 | (% style="color:blue" %)**Latitude:** | ||
| 636 | |||
| 637 | **Example: **0x015A7A7A(H)=22706810(D)=22.706810 | ||
| 638 | |||
| 639 | |||
| 640 | (% style="color:blue" %)**Longitude:** | ||
| 641 | |||
| 642 | **Example: **0x06CF33CE(H)=114242510(D)=114.242510 | ||
| 643 | |||
| 644 | |||
| 645 | (% style="color:blue" %)**GPS Timestamp:** | ||
| 646 | |||
| 647 | Unit TimeStamp Example: 678dad17(H) = 1737338135(D) | ||
| 648 | |||
| 649 | Put the decimal value into this link(https:~/~/www.epochconverter.com/) to get the time. | ||
| 650 | |||
| 651 | |||
| 652 | |||
| 653 | === 2.3.3 ThingsBoard Payload(Type~=3) === | ||
| 654 | |||
| 655 | |||
| 656 | Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard. | ||
| 657 | |||
| 658 | (% style="color:#4472c4" %)**{ | ||
| 659 | "IMEI": "868508065628110", | ||
| 660 | "IMSI": "460240210507481", | ||
| 661 | "Model": "WSC2-C", | ||
| 662 | "payload_ver": 1, | ||
| 663 | "rain_count": 120.00, | ||
| 664 | "wind_speed": 0.00, | ||
| 665 | "wind_level": 0, | ||
| 666 | "wind_direction": 0, | ||
| 667 | "wind_angel": 0, | ||
| 668 | "humidity": 38.4, | ||
| 669 | "temperature": 24.5, | ||
| 670 | "voise": 50.1, | ||
| 671 | "CO2": 38, | ||
| 672 | "pressure": 101.1, | ||
| 673 | "illumination": 632, | ||
| 674 | "interrupt": 0, | ||
| 675 | "interrupt_level": 0, | ||
| 676 | "battery": 3.34, | ||
| 677 | "signal": 26, | ||
| 678 | "time": "2025-01-20T06:12:29Z", | ||
| 679 | "latitude": 0.000000, | ||
| 680 | "longitude": 0.000000, | ||
| 681 | "gps_time": "2025-01-20T06:00:19Z" | ||
| 682 | }** | ||
| 683 | |||
| 684 | [[image:image-20250120141719-6.png||height="632" width="1332"]] | ||
| 685 | |||
| 686 | |||
| 687 | === 2.3.4 ThingSpeak Payload(Type~=1) === | ||
| 688 | |||
| 689 | |||
| 690 | This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~~8 are: | ||
| 691 | |||
| 692 | (% style="color:#4472c4" %)**payload_ver**(%%), (% style="color:#4472c4" %)**exit_count(rain)**(%%), (% style="color:#4472c4" %)**WIND_SPEED**(%%) & (% style="color:#4472c4" %)**WIND_LEVEL **(%%)& (% style="color:#4472c4" %)**WIND_DIRECTION **(%%)& (% style="color:#4472c4" %)**WIND_ANGLE **(%%)& (% style="color:#4472c4" %)**Humidity **(%%)& (% style="color:#4472c4" %)**Temperature**(%%). This payload type only valid for ThingsSpeak Platform | ||
| 693 | |||
| 694 | As below: | ||
| 695 | |||
| 696 | (% style="color:#4472c4" %)**field1=payload_ver & field2=exit_count(rain) & field3=WIND_SPEED & field4=WIND_LEVEL & field5=WIND_DIRECTION & field6=WIND_ANGLE & field7=Humidity & field8=Temperature** | ||
| 697 | |||
| 698 | [[image:image-20250120135427-4.png]] | ||
| 699 | |||
| 700 | [[image:image-20250120135438-5.png]] | ||
| 701 | |||
| 702 | |||
| 703 | == 2.4 Test Uplink and Change Update Interval == | ||
| 704 | |||
| 705 | |||
| 706 | By default, Sensor will send uplinks (% style="color:blue" %)**every 2 hours**(%%) | ||
| 707 | |||
| 708 | User can use below commands to change the (% style="color:blue" %)**uplink interval**. | ||
| 709 | |||
| 710 | (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s | ||
| 711 | |||
| 712 | User can also push the button for more than 1 seconds to activate an uplink. | ||
| 713 | |||
| 714 | |||
| 715 | = 3. Configure WSC2-C = | ||
| 716 | |||
| 717 | == 3.1 Configure Methods == | ||
| 718 | |||
| 719 | |||
| 720 | WSC2-C supports below configure method: | ||
| 721 | |||
| 722 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
| 723 | |||
| 724 | * AT Command via UART Connection : See [[UART Connection>>https://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.4UARTConnectionforRS485-BLbasemotherboard]]. | ||
| 725 | |||
| 726 | * NB-Iot Downlink. Instruction for different platforms: See [[NB-Iot downlink>>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/#H4.A0MQTT2FUDP2FTCPdownlink]] section. | ||
| 727 | |||
| 728 | == 3.2 Serial Access Password == | ||
| 729 | |||
| 730 | After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window. | ||
| 731 | |||
| 732 | 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. | ||
| 733 | |||
| 734 | [[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"]] | ||
| 735 | |||
| 736 | If you need to change the password, use **AT+PWORD=**xxxxxx (6 characters), CB nodes only support lowercase letters. | ||
| 737 | |||
| 738 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TS01-CB--NB-IoTLTE-M_Tilting_Sensor_User_Manual/WebHome/image-20240826181440-2.png?rev=1.1||alt="image-20240826181440-2.png"]] | ||
| 739 | |||
| 740 | **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.** | ||
| 741 | |||
| 742 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TS01-CB--NB-IoTLTE-M_Tilting_Sensor_User_Manual/WebHome/image-20240826181446-3.png?rev=1.1||alt="image-20240826181446-3.png"]] | ||
| 743 | |||
| 744 | |||
| 745 | == 3.3 Commands special design for WSC2-C == | ||
| 746 | |||
| 747 | |||
| 748 | These commands only valid for WSC2-C, as below: | ||
| 749 | |||
| 750 | |||
| 751 | === 3.3.1 Set Transmit Interval Time === | ||
| 752 | |||
| 753 | |||
| 754 | Feature: Change NB-Iot End Node Transmit Interval. | ||
| 755 | |||
| 756 | (% style="color:#037691" %)**AT Command: AT+TDC** | ||
| 757 | |||
| 758 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:501px" %) | ||
| 759 | |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:166px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:180px" %)**Response** | ||
| 760 | |(% style="width:155px" %)AT+TDC=?|(% style="width:162px" %)Show current transmit Interval|(% style="width:177px" %)((( | ||
| 761 | 30000 | ||
| 762 | OK | ||
| 763 | the interval is 30000ms = 30s | ||
| 764 | ))) | ||
| 765 | |(% style="width:155px" %)AT+TDC=60000|(% style="width:162px" %)Set Transmit Interval|(% style="width:177px" %)((( | ||
| 766 | OK | ||
| 767 | Set transmit interval to 60000ms = 60 seconds | ||
| 768 | ))) | ||
| 769 | |||
| 770 | (% style="color:#037691" %)**Downlink Command: 0x01** | ||
| 771 | |||
| 772 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
| 773 | |||
| 774 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
| 775 | |||
| 776 | * Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
| 777 | * Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
| 778 | |||
| 779 | === 3.3.2 Set the CO2 or PM mode === | ||
| 780 | |||
| 781 | |||
| 782 | (% style="color:red" %)**Note: Default shipment is CO2 sensor, optional CO2 or PM sensor is available at the time of purchase, which needs to be modified according to the sensor selected at the time of purchase.** | ||
| 783 | |||
| 784 | Feature: Set the CO2/PM mode, and the user can set the corresponding mode according to the purchased sensor. | ||
| 785 | |||
| 786 | (% style="color:#037691" %)**AT Command:** | ||
| 787 | |||
| 788 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:466px" %) | ||
| 789 | |(% style="background-color:#4f81bd; color:white; width:156px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:225px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:85px" %)**Response** | ||
| 790 | |(% style="width:155px" %)AT+PMMOD=1|(% style="width:224px" %)The working sensors are PM2.5 and PM10|(% style="width:84px" %)((( | ||
| 791 | OK | ||
| 792 | |||
| 793 | ))) | ||
| 794 | |(% style="width:155px" %)AT+PMMOD=0|(% style="width:224px" %)The working sensors are CO2|(% style="width:84px" %)((( | ||
| 795 | OK | ||
| 796 | ))) | ||
| 797 | |||
| 798 | (% style="color:#037691" %)**Downlink Command:** | ||
| 799 | |||
| 800 | * 0xE101 Same as: AT+PMMOD=1 | ||
| 801 | * 0xE100 Same as: AT+PMMOD=0 | ||
| 802 | |||
| 803 | === 3.3.3 Add or Delete RS485 Sensor === | ||
| 804 | |||
| 805 | |||
| 806 | ((( | ||
| 807 | Feature: User can add or delete 3^^rd^^ party sensor as long they are RS485/Modbus interface,baud rate support 4800.Maximum can add 4 sensors. | ||
| 808 | ))) | ||
| 809 | |||
| 810 | ((( | ||
| 811 | (% style="color:#037691" %)**AT Command: ** | ||
| 812 | ))) | ||
| 813 | |||
| 814 | ((( | ||
| 815 | (% style="color:blue" %)**AT+DYSENSOR=Type_Code, Query_Length, Query_Command , Read_Length , Valid_Data ,has_CRC,timeout** | ||
| 816 | ))) | ||
| 817 | |||
| 818 | * ((( | ||
| 819 | Type_Code range: A1 ~~ A4 | ||
| 820 | ))) | ||
| 821 | * ((( | ||
| 822 | Query_Length: RS485 Query frame length, Value cannot be greater than 10 | ||
| 823 | ))) | ||
| 824 | * ((( | ||
| 825 | Query_Command: RS485 Query frame data to be sent to sensor, cannot be larger than 10 bytes | ||
| 826 | ))) | ||
| 827 | * ((( | ||
| 828 | Read_Length: RS485 response frame length supposed to receive. Max can receive | ||
| 829 | ))) | ||
| 830 | * ((( | ||
| 831 | Valid_Data: valid data from RS485 Response, Valid Data will be added to Payload and upload via LoRaWAN. | ||
| 832 | ))) | ||
| 833 | * ((( | ||
| 834 | has_CRC: RS485 Response crc check (0: no verification required 1: verification required). If CRC=1 and CRC error, valid data will be set to 0. | ||
| 835 | ))) | ||
| 836 | * ((( | ||
| 837 | timeout: RS485 receive timeout (uint:ms). Device will close receive window after timeout | ||
| 838 | ))) | ||
| 839 | |||
| 840 | ((( | ||
| 841 | **Example:** | ||
| 842 | ))) | ||
| 843 | |||
| 844 | ((( | ||
| 845 | User need to change external sensor use the type code as address code. | ||
| 846 | ))) | ||
| 847 | |||
| 848 | ((( | ||
| 849 | With a 485 sensor, after correctly changing the address code to A1, the RS485 query frame is shown in the following table: | ||
| 850 | ))) | ||
| 851 | |||
| 852 | [[image:image-20220624143553-10.png]] | ||
| 853 | |||
| 854 | |||
| 855 | The response frame of the sensor is as follows: | ||
| 856 | |||
| 857 | [[image:image-20220624143618-11.png]] | ||
| 858 | |||
| 859 | |||
| 860 | **Then the following parameters should be:** | ||
| 861 | |||
| 862 | * Address_Code range: A1 | ||
| 863 | * Query_Length: 8 | ||
| 864 | * Query_Command: A103000000019CAA | ||
| 865 | * Read_Length: 8 | ||
| 866 | * Valid_Data: 23 (Indicates that the data length is 2 bytes, starting from the 3th byte) | ||
| 867 | * has_CRC: 1 | ||
| 868 | * timeout: 1500 (Fill in the test according to the actual situation) | ||
| 869 | |||
| 870 | **So the input command is:** | ||
| 871 | |||
| 872 | AT+DYSENSOR=A1,8,A103000000019CAA,8,24,1,1500 | ||
| 873 | |||
| 874 | |||
| 875 | In every sampling. WSC2-C will auto append the sensor segment as per this structure and uplink. | ||
| 876 | |||
| 877 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:351px" %) | ||
| 878 | |=(% style="width: 95px;background-color:#4F81BD;color:white" %)Type Code|=(% style="width: 122px;background-color:#4F81BD;color:white" %)Length (Bytes)|=(% style="width: 134px;background-color:#4F81BD;color:white" %)Measured Value | ||
| 879 | |(% style="width:94px" %)A1|(% style="width:121px" %)2|(% style="width:132px" %)0x000A | ||
| 880 | |||
| 881 | **Related commands:** | ||
| 882 | |||
| 883 | AT+DYSENSOR=A1,0 ~-~-> Delete 3^^rd^^ party sensor A1. | ||
| 884 | |||
| 885 | AT+DYSENSOR ~-~-> List All 3^^rd^^ Party Sensor. Like below: | ||
| 886 | |||
| 887 | |||
| 888 | (% style="color:#037691" %)**Downlink Command: ** | ||
| 889 | |||
| 890 | **delete custom sensor A1:** | ||
| 891 | |||
| 892 | * 0xE5A1 Same as: AT+DYSENSOR=A1,0 | ||
| 893 | |||
| 894 | **Remove all custom sensors** | ||
| 895 | |||
| 896 | * 0xE5FF | ||
| 897 | |||
| 898 | === 3.3.4 RS485 Test Command === | ||
| 899 | |||
| 900 | |||
| 901 | (% style="color:#037691" %)**AT Command:** | ||
| 902 | |||
| 903 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:494px" %) | ||
| 904 | |=(% style="width: 160px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 248px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 86px;background-color:#4F81BD;color:white" %)**Response** | ||
| 905 | |(% style="width:159px" %)AT+RSWRITE=xxxxxx|(% style="width:227px" %)((( | ||
| 906 | Send command to 485 sensor. Range : no more than 10 bytes | ||
| 907 | )))|(% style="width:85px" %)OK | ||
| 908 | |||
| 909 | Eg: Send command **01 03 00 00 00 01 84 0A** to 485 sensor | ||
| 910 | |||
| 911 | AT+RSWRITE=0103000001840A | ||
| 912 | |||
| 913 | |||
| 914 | (% style="color:#037691" %)**Downlink Command:** | ||
| 915 | |||
| 916 | * 0xE20103000001840A Same as: AT+RSWRITE=0103000001840A | ||
| 917 | |||
| 918 | === 3.3.5 RS485 response timeout === | ||
| 919 | |||
| 920 | |||
| 921 | Feature: Set or get extended time to receive 485 sensor data. | ||
| 922 | |||
| 923 | (% style="color:#037691" %)**AT Command:** | ||
| 924 | |||
| 925 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:433px" %) | ||
| 926 | |=(% style="width: 157px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 190px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 86px;background-color:#4F81BD;color:white" %)**Response** | ||
| 927 | |(% style="width:157px" %)AT+DTR=1000|(% style="width:188px" %)((( | ||
| 928 | Set response timeout to: Range : 0~~10000 | ||
| 929 | )))|(% style="width:85px" %)OK | ||
| 930 | |||
| 931 | (% style="color:#037691" %)**Downlink Command:** | ||
| 932 | |||
| 933 | Format: Command Code (0xE0) followed by 3 bytes time value. | ||
| 934 | |||
| 935 | If the downlink payload=E0000005, it means set the END Node's Transmit Interval to 0x000005=5(S), while type code is E0. | ||
| 936 | |||
| 937 | * Example 1: Downlink Payload: E0000005 ~/~/ Set Transmit Interval (DTR) = 5 seconds | ||
| 938 | * Example 2: Downlink Payload: E000000A ~/~/ Set Transmit Interval (DTR) = 10 seconds | ||
| 939 | |||
| 940 | === 3.3.6 Set or get the total count value === | ||
| 941 | |||
| 942 | |||
| 943 | Feature: The user can set the counting to start from the set value according to the requirements. (only available in counting mode). | ||
| 944 | |||
| 945 | (% style="color:#037691" %)**AT Command:** | ||
| 946 | |||
| 947 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:433px" %) | ||
| 948 | |=(% style="width: 157px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 190px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 86px;background-color:#4F81BD;color:white" %)**Response** | ||
| 949 | |(% style="width:157px" %)AT+SETCNT=1000|(% style="width:188px" %)Set the total count to start from 1000|(% style="width:85px" %)OK | ||
| 950 | |||
| 951 | (% style="color:#037691" %)**Downlink Command:** | ||
| 952 | |||
| 953 | Format: Command Code (0x09) followed by 5 bytes time value. | ||
| 954 | |||
| 955 | If the downlink payload=09000003E8, This means that the count of the END node will start counting from setting 0x000003E8=1000 (times). while type code is 09. | ||
| 956 | |||
| 957 | * Example 1: Downlink Payload: 09000003E8 ~/~/ Set the value to start counting from 1000 = 1000 (times) | ||
| 958 | |||
| 959 | === 3.3.7 Set interrupt or counting mode === | ||
| 960 | |||
| 961 | |||
| 962 | Feature: Users can set the trigger mode to counting mode or interrupt mode as needed. | ||
| 963 | |||
| 964 | (% style="color:#037691" %)**AT Command:** | ||
| 965 | |||
| 966 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:433px" %) | ||
| 967 | |=(% style="width: 157px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 190px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 86px;background-color:#4F81BD;color:white" %)**Response** | ||
| 968 | |(% style="width:157px" %)AT+COUNTMOD=0|(% style="width:188px" %)set to interrupt mode|(% style="width:85px" %)OK | ||
| 969 | |(% style="width:157px" %)AT+COUNTMOD=1|(% style="width:188px" %)((( | ||
| 970 | set to counting mode | ||
| 971 | )))|(% style="width:85px" %)OK | ||
| 972 | |||
| 973 | (% style="color:#037691" %)**Downlink Command:** | ||
| 974 | |||
| 975 | Format: Command Code (0x10) followed by 1 bytes time value. | ||
| 976 | |||
| 977 | If the downlink payload=10 00, Set the trigger mode to interrupt mode, while type code is 10. | ||
| 978 | |||
| 979 | * Example 1: Downlink Payload: 10 00 ~/~/ Same as: AT+COUNTMOD=0 set to interrupt mode | ||
| 980 | |||
| 981 | === 3.3.8 Domain name resolution settings === | ||
| 982 | |||
| 983 | |||
| 984 | Feature: Set dynamic domain name resolution IP. | ||
| 985 | |||
| 986 | (% style="color:blue" %)**AT command: AT+BKDNS** | ||
| 987 | |||
| 988 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
| 989 | |=(% 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** | ||
| 990 | |(% style="width:134px" %)((( | ||
| 991 | AT+BKDNS=? | ||
| 992 | )))|(% style="width:143px" %)Get current Settings|(% style="width:606px" %)((( | ||
| 993 | 0,0,NULL (default) | ||
| 994 | OK | ||
| 995 | ))) | ||
| 996 | |(% colspan="1" rowspan="3" style="width:134px" %)((( | ||
| 997 | |||
| 998 | |||
| 999 | |||
| 1000 | |||
| 1001 | |||
| 1002 | |||
| 1003 | |||
| 1004 | |||
| 1005 | |||
| 1006 | |||
| 1007 | |||
| 1008 | AT+BKDNS=a,b,c | ||
| 1009 | )))|(% style="width:143px" %)((( | ||
| 1010 | **a**: Enable/Disable dynamic domain name resolution. | ||
| 1011 | )))|(% 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. | ||
| 1012 | **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. | ||
| 1013 | |(% style="width:143px" %)**b**: Set the time to update the domain name resolution at regular intervals.|(% style="width:606px" %)((( | ||
| 1014 | Unit: hour | ||
| 1015 | ))) | ||
| 1016 | |(% style="width:143px" %)((( | ||
| 1017 | **c**: Set the IP address manually. | ||
| 1018 | )))|(% style="width:606px" %)((( | ||
| 1019 | The format is the same as AT+SERVADDR. | ||
| 1020 | 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. | ||
| 1021 | ))) | ||
| 1022 | |||
| 1023 | **Example:** | ||
| 1024 | |||
| 1025 | * AT+BKDNS=1,0 ~/~/ Dynamic domain name resolution is disabled. | ||
| 1026 | * AT+BKDNS=2,1 ~/~/ The dynamic domain name resolution function is enabled and the automatic update time is set to 1 hour. | ||
| 1027 | * 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. | ||
| 1028 | |||
| 1029 | (% style="color:blue" %)**Downlink Command: ** | ||
| 1030 | |||
| 1031 | No downlink commands for feature | ||
| 1032 | |||
| 1033 | |||
| 1034 | === 3.3.9 Set the downlink debugging mode === | ||
| 1035 | |||
| 1036 | Feature: Set the conversion between the standard version and 1T version downlinks. | ||
| 1037 | |||
| 1038 | (% style="color:blue" %)**AT command: AT+DOWNTE** | ||
| 1039 | |||
| 1040 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
| 1041 | |=(% 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** | ||
| 1042 | |(% style="width:134px" %)AT+DOWNTE=?|(% style="width:143px" %)Get current Settings|(% style="width:229px" %)((( | ||
| 1043 | 0,0 (default) | ||
| 1044 | OK | ||
| 1045 | ))) | ||
| 1046 | |(% colspan="1" rowspan="2" style="width:134px" %)((( | ||
| 1047 | |||
| 1048 | |||
| 1049 | |||
| 1050 | |||
| 1051 | AT+DOWNTE=a,b | ||
| 1052 | )))|(% style="width:143px" %)**a**: Set the conversion between the downlink of the standard version and 1T version|(% style="width:229px" %)((( | ||
| 1053 | **0**: Set the downlink of the standard version. | ||
| 1054 | **1**: Set the downlink of the 1T version(ThingsEye platform) | ||
| 1055 | ))) | ||
| 1056 | |(% style="width:143px" %)**b**: Enable/Disable downlink debugging|(% style="width:229px" %)((( | ||
| 1057 | **0**: Disable downlink debugging mode. | ||
| 1058 | **1**: Enable downlink debugging mode, users can see the original downlink reception. | ||
| 1059 | ))) | ||
| 1060 | |||
| 1061 | **Example:** | ||
| 1062 | |||
| 1063 | * AT+DOWNTE=0,1 ~/~/ Set to standard version downlink, and enable downlink debugging. | ||
| 1064 | * AT+DOWNTE=1,1 ~/~/ Set to 1T version downlink, and enable downlink debugging. | ||
| 1065 | |||
| 1066 | (% style="color:blue" %)**Downlink Command: ** | ||
| 1067 | |||
| 1068 | No downlink commands for feature | ||
| 1069 | |||
| 1070 | |||
| 1071 | === 3.3.10 Set the TLS mode === | ||
| 1072 | |||
| 1073 | |||
| 1074 | Refer to this link ([[MQTT Connection to send data to Tago.io>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H3.7Tago.io28viaMQTT29]])to use the TLS mode. | ||
| 1075 | |||
| 1076 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TLSMOD** | ||
| 1077 | |||
| 1078 | **Example 1: ** AT+TLSMOD=0,0 ~/~/ Disable TLS Mode. | ||
| 1079 | |||
| 1080 | **Example 2:** AT+TLSMOD=1,0 ~/~/ No authentication | ||
| 1081 | |||
| 1082 | AT+TLSMOD=1,1 ~/~/ Perform server authentication | ||
| 1083 | |||
| 1084 | AT+TLSMOD=1,2 ~/~/ Perform server and client authentication if requested by the remote server | ||
| 1085 | |||
| 1086 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x09(%%)** | ||
| 1087 | |||
| 1088 | Format: Command Code (0x09) followed by 2 bytes. | ||
| 1089 | |||
| 1090 | Example1: Downlink Payload: **09 00 00 **~/~/ AT+TLSMOD=0,0 | ||
| 1091 | |||
| 1092 | Example2: Downlink Payload: **09 01 02 **~/~/ AT+TLSMOD=1,2 | ||
| 1093 | |||
| 1094 | |||
| 1095 | === 3.3.11 Set GNSS open time === | ||
| 1096 | |||
| 1097 | |||
| 1098 | Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated. | ||
| 1099 | |||
| 1100 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST** | ||
| 1101 | |||
| 1102 | Example: AT+GNSST=30 ~/~/ Set the GPS positioning time to 30 seconds | ||
| 1103 | |||
| 1104 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)** | ||
| 1105 | |||
| 1106 | Format: Command Code (0x10) followed by 2 bytes. | ||
| 1107 | |||
| 1108 | Example: Downlink Payload: **10 00 1E **~/~/ AT+GNSST=30 | ||
| 1109 | |||
| 1110 | |||
| 1111 | === 3.3.12 Turn on/off GPS === | ||
| 1112 | |||
| 1113 | |||
| 1114 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS ** | ||
| 1115 | |||
| 1116 | **Ex1: **AT+GPS=0 ~/~/ Turn off GPS | ||
| 1117 | |||
| 1118 | **Ex2: **AT+GPS=1 ~/~/ Turn on GPS | ||
| 1119 | |||
| 1120 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)** | ||
| 1121 | |||
| 1122 | Format: Command Code (0x11) followed by 1 byte. | ||
| 1123 | |||
| 1124 | Example: Downlink Payload: **11 01 **~/~/ AT+GPS=1 | ||
| 1125 | |||
| 1126 | |||
| 1127 | === 3.3.13 Set GPS positioning interval === | ||
| 1128 | |||
| 1129 | |||
| 1130 | Feature: Set GPS positioning interval (unit: hour). | ||
| 1131 | |||
| 1132 | When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation. | ||
| 1133 | |||
| 1134 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC** | ||
| 1135 | |||
| 1136 | Example: AT+GTDC=24 ~/~/ Set the GPS positioning interval to 24h. | ||
| 1137 | |||
| 1138 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)** | ||
| 1139 | |||
| 1140 | Format: Command Code (0x12) followed by 3 bytes. | ||
| 1141 | |||
| 1142 | Example: 24 hours: 24(D)=0x18(H) | ||
| 1143 | |||
| 1144 | Downlink Payload: **12 00 00 18 **~/~/ AT+GTDC=24 | ||
| 1145 | |||
| 1146 | |||
| 1147 | === 3.3.14 Set the search network time === | ||
| 1148 | |||
| 1149 | |||
| 1150 | Feature: Get or Set the time to join the network(unit: minutes). | ||
| 1151 | |||
| 1152 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+CSQTIME** | ||
| 1153 | |||
| 1154 | Example: AT+CSQTIME=10 ~/~/ Set the search time to 10 minutes. | ||
| 1155 | |||
| 1156 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x13(%%)** | ||
| 1157 | |||
| 1158 | Format: Command Code (0x13) followed by 1 byte. | ||
| 1159 | |||
| 1160 | Example: Downlink Payload: **13 0A **~/~/ AT+CSQTIME=10 | ||
| 1161 | |||
| 1162 | |||
| 1163 | === 3.3.15 Set the IPv4 or IPv6 === | ||
| 1164 | |||
| 1165 | |||
| 1166 | This command is used to set IP version. | ||
| 1167 | |||
| 1168 | (% style="color:blue" %)**AT command:** | ||
| 1169 | |||
| 1170 | * (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=1**(%%)** **~/~/ IPv4 | ||
| 1171 | * (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=2**(%%)** **~/~/ IPv6 | ||
| 1172 | |||
| 1173 | === 3.3.16 Configure Network Category to be Searched for under LTE RAT. === | ||
| 1174 | |||
| 1175 | |||
| 1176 | (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+IOTMOD=xx(%%)** | ||
| 1177 | |||
| 1178 | (% style="color:#037691" %)**xx:**(%%) **0:** eMTC | ||
| 1179 | |||
| 1180 | **1:** NB-IoT | ||
| 1181 | |||
| 1182 | **2:** eMTC and NB-IoT | ||
| 1183 | |||
| 1184 | |||
| 1185 | === 3.3.17 Factory data reset === | ||
| 1186 | |||
| 1187 | |||
| 1188 | Two different restore factory Settings configurations. | ||
| 1189 | |||
| 1190 | (% style="color:blue" %)**AT command:** | ||
| 1191 | |||
| 1192 | * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default. | ||
| 1193 | * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values **except for passwords**. | ||
| 1194 | |||
| 1195 | === 3.3.19 Set CoAP option === | ||
| 1196 | |||
| 1197 | |||
| 1198 | Feature: Set CoAP option, follow this link to set up the CoaP protocol. | ||
| 1199 | |||
| 1200 | (% style="color:blue" %)**AT command: **(% style="color:#037691; font-weight:bold" %)**AT+URI1~~AT+URI8** | ||
| 1201 | |||
| 1202 | (% 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" | ||
| 1203 | |||
| 1204 | (% style="color:#037691; font-weight:bold" %)**AT+URI2=11,"CoAP endpoint URl" **(%%)~/~/ 11 is a fixed parameter. | ||
| 1205 | |||
| 1206 | **Example: ** i/13a35fbe-9515-6e55-36e8-081fb6aacf86 | ||
| 1207 | |||
| 1208 | AT+URI1=11,"i" | ||
| 1209 | |||
| 1210 | AT+URI2=11,"13a35fbe-9515-6e55-36e8-081fb6aacf86" | ||
| 1211 | |||
| 1212 | ~-~-> If multiple groups of CoAP endpoint urls: | ||
| 1213 | |||
| 1214 | AT+URI3=11,"i" | ||
| 1215 | |||
| 1216 | AT+URI4=11,"CoAP endpoint URl" | ||
| 1217 | |||
| 1218 | |||
| 1219 | === 3.3.20 Power on / power off BG95 module === | ||
| 1220 | |||
| 1221 | |||
| 1222 | This command is used to power on and power off BG95 module. | ||
| 1223 | |||
| 1224 | * (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+QSW** | ||
| 1225 | |||
| 1226 | The module is powered on after the command is sent for the first time, and powered off after the command is sent again. | ||
| 1227 | |||
| 1228 | [[image:image-20250120110640-4.png]] | ||
| 1229 | |||
| 1230 | |||
| 1231 | === 3.3.21 Set the receiving time === | ||
| 1232 | |||
| 1233 | |||
| 1234 | Feature: Extend the receiving time | ||
| 1235 | |||
| 1236 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+RXDL** | ||
| 1237 | |||
| 1238 | Example: AT+RXDL=1000 ~/~/ Set the receiving time delay to 1000ms | ||
| 1239 | |||
| 1240 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x03** | ||
| 1241 | |||
| 1242 | Format: Command Code (0x03) followed by 3 bytes. | ||
| 1243 | |||
| 1244 | Example: Downlink Payload: **03 00 03 E8 **~/~/ AT+RXDL=1000 | ||
| 1245 | |||
| 1246 | |||
| 1247 | === 3.3.22 Reset === | ||
| 1248 | |||
| 1249 | |||
| 1250 | Feature: Trig a reset of the MCU. | ||
| 1251 | |||
| 1252 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**ATZ** | ||
| 1253 | |||
| 1254 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x04FF** | ||
| 1255 | |||
| 1256 | |||
| 1257 | === 3.3.23 Set the QoS level === | ||
| 1258 | |||
| 1259 | |||
| 1260 | This command is used to set the QoS level of **MQTT**. | ||
| 1261 | |||
| 1262 | (% style="color:blue" %)**AT command:** | ||
| 1263 | |||
| 1264 | * (% style="color:#037691" %)**AT+MQOS=xx**(%%)** **~/~/ 0~~2 | ||
| 1265 | |||
| 1266 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x07(%%)** | ||
| 1267 | |||
| 1268 | Format: Command Code (0x07) followed by 1 byte. | ||
| 1269 | |||
| 1270 | **Ex1:** Downlink payload: **0x0700** ~/~/ AT+MQOS=0 | ||
| 1271 | |||
| 1272 | **Ex2:** Downlink payload: **0x0701** ~/~/ AT+MQOS=1 | ||
| 1273 | |||
| 1274 | |||
| 1275 | == 3.4 Add 3rd RS485 / Modbus Sensor == | ||
| 1276 | |||
| 1277 | === 3.4.1 Hardware Connection === | ||
| 1278 | |||
| 1279 | |||
| 1280 | WSC2-C has a 1 to 3 cables. All the three connectors has same defination as below. It include Five Pins: VCC, GND, RS485-A, RS485-B, Count. | ||
| 1281 | |||
| 1282 | (% style="color:red" %)**Notice: RS485-A,RS485-B can be used to connect multiply sensors. but the COUNT can be only use for one sensor. Which means if you already add a Pulse output Rain Guage in the system, you are not able to add another Pulse Output device.** | ||
| 1283 | |||
| 1284 | [[image:image-20240707220859-4.png||height="313" width="366"]] | ||
| 1285 | |||
| 1286 | |||
| 1287 | === 3.4.2 Software Setup === | ||
| 1288 | |||
| 1289 | |||
| 1290 | Send AT+DYSENSOR to activate the RS485 sensor for collecting 3rd RS485 sensor. You can refer to the instructions in section 3.3.3 of the manual. | ||
| 1291 | |||
| 1292 | For example: AT+DYSENSOR=A1,8,A103000000019CAA,8,24,1,1500 | ||
| 1293 | |||
| 1294 | |||
| 1295 | === 3.4.3 Payload === | ||
| 1296 | |||
| 1297 | [[image:image-20240416163658-1.png]] | ||
| 1298 | |||
| 1299 | For example: A1 02 00 00 | ||
| 1300 | |||
| 1301 | A1 : A1 register data acquisition instruction | ||
| 1302 | |||
| 1303 | 02 : The valid data returned is 2 bytes in total. | ||
| 1304 | |||
| 1305 | 00 00 : Return valid data | ||
| 1306 | |||
| 1307 | |||
| 1308 | = 3.5 Add tipping bucket total solar radiation sensor = | ||
| 1309 | |||
| 1310 | === 3.5.1 Hardware Connection === | ||
| 1311 | |||
| 1312 | |||
| 1313 | The following is an example of connecting a total solar radiation sensor to a matching interface cable, and then using the interface to connect the WSC2-C. | ||
| 1314 | |||
| 1315 | Users can also choose to connect the sensor directly to the WSC2-C via the cable and pin instructions below. | ||
| 1316 | |||
| 1317 | The following is an explanation of the [[pins>>||anchor="H5.7PinMapping"]] required for WSC2-C： | ||
| 1318 | |||
| 1319 | **A:** RS485-A (Connect the RS485 sensor) | ||
| 1320 | |||
| 1321 | **B:** RS485-B (Connect the RS485 sensor) | ||
| 1322 | |||
| 1323 | **GPIO_EXTI:** Interrupt pin (Can be used to connect an additionally added pulsed rain gauge) | ||
| 1324 | |||
| 1325 | |||
| 1326 | * Total Solar Radiation Sensor Cable Descripti | ||
| 1327 | |||
| 1328 | [[image:image-20240906174635-2.jpeg||height="430" width="813"]] | ||
| 1329 | |||
| 1330 | |||
| 1331 | |||
| 1332 | * Mating Interface Cable Description | ||
| 1333 | |||
| 1334 | [[image:image-20240906173843-1.jpeg||height="404" width="815"]] | ||
| 1335 | |||
| 1336 | * Connect to WSC2-C | ||
| 1337 | |||
| 1338 | The Total solar radiation sensor does not need to connect the interrupt pin, so the white cable is not wired. | ||
| 1339 | |||
| 1340 | [[image:image-20240906182250-3.jpeg||height="442" width="820"]] | ||
| 1341 | |||
| 1342 | |||
| 1343 | === 3.5.2 Calculating & Decode === | ||
| 1344 | |||
| 1345 | |||
| 1346 | 0FC6 01 00000000 00EB 000F 0000 0003 008E 0251 00CE 0213 0017 001B 03EC 000000DE 90 A1020000 A2020032 | ||
| 1347 | |||
| 1348 | For example: A2 02 00 32 | ||
| 1349 | |||
| 1350 | A2 : A2 register data acquisition instruction | ||
| 1351 | |||
| 1352 | 02 : The valid data returned is 2 bytes in total. | ||
| 1353 | |||
| 1354 | 00 32(HEX) : Return valid data = 50(DEC)W/m2 | ||
| 1355 | |||
| 1356 | |||
| 1357 | == 3.6 AT Commands Set == | ||
| 1358 | |||
| 1359 | AT+<CMD>? : Help on <CMD> | ||
| 1360 | |||
| 1361 | AT+<CMD> : Run <CMD> | ||
| 1362 | |||
| 1363 | AT+<CMD>=<value> : Set the value | ||
| 1364 | |||
| 1365 | AT+<CMD>=? : Get the value | ||
| 1366 | |||
| 1367 | |||
| 1368 | (% style="color:blue" %)**General Commands ** | ||
| 1369 | |||
| 1370 | AT+MODEL : Get module information | ||
| 1371 | |||
| 1372 | ATZ : Trig a reset of the MCU | ||
| 1373 | |||
| 1374 | AT+CFGMOD : Working mode selection | ||
| 1375 | |||
| 1376 | AT+DEUI : Get or set the Device ID | ||
| 1377 | |||
| 1378 | AT+CFG : Print all settings | ||
| 1379 | |||
| 1380 | AT+SERVADDR: Get or Set the Server address | ||
| 1381 | |||
| 1382 | AT+TDC : Get or set the application data transmission interval in s | ||
| 1383 | |||
| 1384 | AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising) | ||
| 1385 | |||
| 1386 | AT+APN : Get or set the APN | ||
| 1387 | |||
| 1388 | AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP) | ||
| 1389 | |||
| 1390 | AT+RXDL : Get or Set the receiving time | ||
| 1391 | |||
| 1392 | AT+LDATA : Get the last upload data | ||
| 1393 | |||
| 1394 | AT+COUNTMOD : Get or Set the count mode | ||
| 1395 | |||
| 1396 | AT+RSWRITE : Write command to 485 sensor | ||
| 1397 | |||
| 1398 | AT+DTR : Set or get the delay time for receiving 485 sensor data | ||
| 1399 | |||
| 1400 | AT+DYSENSOR : Set or get 485 sensor | ||
| 1401 | |||
| 1402 | AT+PMMOD : CO2 to PM2.5/10 | ||
| 1403 | |||
| 1404 | AT+SETCNT : Get or set the count at present | ||
| 1405 | |||
| 1406 | AT+FACTOR : Get or Set factor | ||
| 1407 | |||
| 1408 | AT+GETSENSORVALUE : Returns the current sensor measurement | ||
| 1409 | |||
| 1410 | AT+DNSCFG : Get or Set DNS Server | ||
| 1411 | |||
| 1412 | AT+CSQTIME : Get or Set the time to join the network | ||
| 1413 | |||
| 1414 | AT+BKDNS : Get or Set dynamic domain name resolution IP | ||
| 1415 | |||
| 1416 | AT+SLEEP : Get or Set the sleep mode | ||
| 1417 | |||
| 1418 | AT+GETLOG : Print serial port logs | ||
| 1419 | |||
| 1420 | AT+DOWNTE: Get or set the conversion between the standard version and 1T version downlinks | ||
| 1421 | |||
| 1422 | AT+GDNS : Get or Set the DNS | ||
| 1423 | |||
| 1424 | AT+MQOS : Set the QoS level of MQTT | ||
| 1425 | |||
| 1426 | AT+IPTYPE : Set the IPv4 or IPv6 | ||
| 1427 | |||
| 1428 | AT+QSW : Power on and power off BG95 module | ||
| 1429 | |||
| 1430 | AT+QBAND: Get or set Frequency Band | ||
| 1431 | |||
| 1432 | AT+IOTMOD: Configure Network Category to be Searched for under LTE RAT | ||
| 1433 | |||
| 1434 | |||
| 1435 | (% style="color:blue" %)**MQTT Management** | ||
| 1436 | |||
| 1437 | |||
| 1438 | AT+CLIENT : Get or Set the MQTT clientID | ||
| 1439 | |||
| 1440 | AT+UNAME : Get or Set the MQTT Username | ||
| 1441 | |||
| 1442 | AT+PWD : Get or Set the MQTT password | ||
| 1443 | |||
| 1444 | AT+PUBTOPIC: Get or set MQTT publishing topic | ||
| 1445 | |||
| 1446 | AT+SUBTOPIC: Get or set MQTT subscription topic | ||
| 1447 | |||
| 1448 | AT+TLSMOD : Get or Set the TLS mode | ||
| 1449 | |||
| 1450 | |||
| 1451 | (% style="color:blue" %)**information** | ||
| 1452 | |||
| 1453 | AT+FDR1 : Reset parameters to factory default values except for passwords | ||
| 1454 | |||
| 1455 | AT+FDR : Reset Parameters to Factory Default | ||
| 1456 | |||
| 1457 | AT+PWORD : Get or set the System password | ||
| 1458 | |||
| 1459 | |||
| 1460 | (% style="color:blue" %)**Management** | ||
| 1461 | |||
| 1462 | AT+URI1: Get or set CoAP option 1 | ||
| 1463 | |||
| 1464 | AT+URI2: Get or set CoAP option 2 | ||
| 1465 | |||
| 1466 | AT+URI3: Get or set CoAP option 3 | ||
| 1467 | |||
| 1468 | AT+URI4: Get or set CoAP option 4 | ||
| 1469 | |||
| 1470 | AT+URI5: Get or set CoAP option 5 | ||
| 1471 | |||
| 1472 | AT+URI6: Get or set CoAP option 6 | ||
| 1473 | |||
| 1474 | AT+URI7: Get or set CoAP option 7 | ||
| 1475 | |||
| 1476 | AT+URI8: Get or set CoAP option 8 | ||
| 1477 | |||
| 1478 | |||
| 1479 | (% style="color:blue" %)**GPS** | ||
| 1480 | |||
| 1481 | AT+GNSST : Extend the time to turn on GNSS | ||
| 1482 | |||
| 1483 | AT+GPS : Turn off and on GPS | ||
| 1484 | |||
| 1485 | AT+GTDC : Get or set GPS positioning interval in units of h | ||
| 1486 | |||
| 1487 | |||
| 1488 | = 4. Power consumption and battery = | ||
| 1489 | |||
| 1490 | == 4.1 Total Power Consumption == | ||
| 1491 | |||
| 1492 | |||
| 1493 | Dragino Weather Station serial products include the main process unit (WSC2-C) and various sensors. The total power consumption equal total power of all above units. The power consumption for main process unit WSC2-C is 18ma @ 12v. and the power consumption of each sensor can be found on the Sensors chapter. | ||
| 1494 | |||
| 1495 | |||
| 1496 | == 4.2 Battery == | ||
| 1497 | |||
| 1498 | |||
| 1499 | ((( | ||
| 1500 | All sensors are only power by external power source. If external power source is off. All sensor won't work. | ||
| 1501 | ))) | ||
| 1502 | |||
| 1503 | ((( | ||
| 1504 | Main Process Unit WSC2-C is powered by both external power source and internal 1000mAh rechargeable battery. If external power source is off, WSC2-C still runs and can send periodically uplinks, but the sensors value will become invalid. External power source can recharge the 1000mAh rechargeable battery. | ||
| 1505 | ))) | ||
| 1506 | |||
| 1507 | |||
| 1508 | = 5. Main Process Unit WSC2-C = | ||
| 1509 | |||
| 1510 | |||
| 1511 | WSC2-C is the main process unit in Dragino Weather Station solution. WSC2-C is an an outdoor NB-IOT RS485 end node. It is powered by external 12v solar power and have a built-in Li-ion backup battery. | ||
| 1512 | |||
| 1513 | WSC2-C reads value from various sensors and upload these sensor data to IoT server via NB-Iot wireless protocol. | ||
| 1514 | |||
| 1515 | WSC2-C Supports BLE configure and wireless OTA update which make user easy to use. | ||
| 1516 | |||
| 1517 | |||
| 1518 | == 5.1 Features == | ||
| 1519 | |||
| 1520 | |||
| 1521 | * NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD | ||
| 1522 | * Ultra-low power consumption | ||
| 1523 | * RS485 / Modbus protocol | ||
| 1524 | * AT Commands to change parameters | ||
| 1525 | * Downlink to change configure | ||
| 1526 | * Powered by external 12v battery | ||
| 1527 | * Back up rechargeable 1000mAh battery | ||
| 1528 | * IP Rating: IP65 | ||
| 1529 | * Support default sensors or 3rd party RS485 sensors | ||
| 1530 | * Support wireless OTA update firmware | ||
| 1531 | * Wall Attachable. | ||
| 1532 | |||
| 1533 | == 5.2 Power Consumption == | ||
| 1534 | |||
| 1535 | |||
| 1536 | WSC2-C (without external sensor): Idle: 4mA, Transmit: max 40mA | ||
| 1537 | |||
| 1538 | |||
| 1539 | == 5.3 Storage & Operation Temperature == | ||
| 1540 | |||
| 1541 | |||
| 1542 | -20°C to +60°C | ||
| 1543 | |||
| 1544 | |||
| 1545 | == 5.4 Sleep mode and working mode == | ||
| 1546 | |||
| 1547 | |||
| 1548 | (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any NB-IoT activate. This mode is used for storage and shipping to save battery life. | ||
| 1549 | |||
| 1550 | (% 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. | ||
| 1551 | |||
| 1552 | |||
| 1553 | == 5.5 Button & LEDs == | ||
| 1554 | |||
| 1555 | |||
| 1556 | [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]] | ||
| 1557 | |||
| 1558 | |||
| 1559 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
| 1560 | |=(% 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** | ||
| 1561 | |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
| 1562 | If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
| 1563 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
| 1564 | ))) | ||
| 1565 | |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
| 1566 | (% 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 network. | ||
| 1567 | (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
| 1568 | 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 network or not. | ||
| 1569 | ))) | ||
| 1570 | |(% 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. | ||
| 1571 | |||
| 1572 | (% 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.** | ||
| 1573 | |||
| 1574 | |||
| 1575 | == 5.6 BLE connection == | ||
| 1576 | |||
| 1577 | |||
| 1578 | WSC2-C supports BLE remote configure. | ||
| 1579 | |||
| 1580 | 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: | ||
| 1581 | |||
| 1582 | * Press button to send an uplink | ||
| 1583 | * Press button to active device. | ||
| 1584 | * Device Power on or reset. | ||
| 1585 | |||
| 1586 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
| 1587 | |||
| 1588 | |||
| 1589 | == 5.7 Pin Mapping == | ||
| 1590 | |||
| 1591 | |||
| 1592 | [[image:image-20240412165523-2.png]] | ||
| 1593 | |||
| 1594 | |||
| 1595 | == 5.8 Mechanical == | ||
| 1596 | |||
| 1597 | |||
| 1598 | Refer LSn50v2 enclosure drawing in: [[https:~~/~~/www.dropbox.com/sh/0ir0l9jjmk6p95e/AADwWXorcKuNpPR5em7VgrEja?dl=0>>https://www.dropbox.com/sh/0ir0l9jjmk6p95e/AADwWXorcKuNpPR5em7VgrEja?dl=0]] | ||
| 1599 | |||
| 1600 | |||
| 1601 | = 6. OTA Firmware update = | ||
| 1602 | |||
| 1603 | |||
| 1604 | (% class="wikigeneratedid" %) | ||
| 1605 | **User can change firmware WSC2-C to:** | ||
| 1606 | |||
| 1607 | * Change Frequency band/ region. | ||
| 1608 | * Update with new features. | ||
| 1609 | * Fix bugs. | ||
| 1610 | |||
| 1611 | **Firmware and changelog can be downloaded from :** **[[Firmware download link>>https://www.dropbox.com/sh/8j3ioji411ni9gu/AADnOw3ErB1REsthKilfaq_Pa?dl=0]]** | ||
| 1612 | |||
| 1613 | **Methods to Update Firmware:** | ||
| 1614 | |||
| 1615 | * (Recommanded way) OTA firmware update via wireless: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]** | ||
| 1616 | |||
| 1617 | * Update through UART TTL interface: **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**. | ||
| 1618 | |||
| 1619 | = 7. FAQ = | ||
| 1620 | |||
| 1621 | == 7.1 What else do I need to purchase to build Weather Station? == | ||
| 1622 | |||
| 1623 | |||
| 1624 | Below is the installation photo and structure: | ||
| 1625 | |||
| 1626 | [[image:image-20250120111258-5.jpeg]] | ||
| 1627 | |||
| 1628 | == 7.2 Where can i find the modbus command for the WSS-09 sensor? == | ||
| 1629 | |||
| 1630 | See this link for the [[modbus command set>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/AJ0vtpF_CRE7KYMQMJNa9tw/LTE-M/WSC2-C?dl=0&e=1&preview=Weather_Sensors_Modbus_Command_List.xlsx&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]]. | ||
| 1631 | |||
| 1632 | |||
| 1633 | = 8. Trouble Shooting = | ||
| 1634 | |||
| 1635 | == 8.1 What should I do when the RS485 sensor cannot collect data? == | ||
| 1636 | |||
| 1637 | |||
| 1638 | ~1. Recheck whether the sensor's power supply voltage is 12V at maximum. | ||
| 1639 | |||
| 1640 | 2. Recheck whether the A and B signal lines of the sensor are connected reversely. | ||
| 1641 | |||
| 1642 | 3. Check whether the sensor's transmission baud rate is 4800. If not, please change it to 4800 and try reading again. | ||
| 1643 | |||
| 1644 | |||
| 1645 | == 8.2 Why does the weather station make electric current sounds during operation? == | ||
| 1646 | |||
| 1647 | |||
| 1648 | ~1. Because a certain amount of sound will be produced during long-term power supply operation. This is a normal phenomenon and does not affect use. | ||
| 1649 | |||
| 1650 | |||
| 1651 | == 8.3 How to solve the problem of temperature difference in weather stations? == | ||
| 1652 | |||
| 1653 | |||
| 1654 | You can use AT+RSWRITE (downlink: E2 xx xx xx xx xx xx xx ) to modify the temperature compensation function in the weather station. | ||
| 1655 | |||
| 1656 | **For example：** | ||
| 1657 | |||
| 1658 | When the temperature of the weather station is 3°C different from the right value, you can use AT+RSWRITE=01 06 00 50 00 1E 09 D3 (downlink: E2 01 06 00 50 00 1E 09 D3) to modify the temperature compensation value of the weather station to +3°C . | ||
| 1659 | |||
| 1660 | |||
| 1661 | == 8.4 Why does the rain gauge have no data? == | ||
| 1662 | |||
| 1663 | The default mode of the rain gauge is trigger mode. | ||
| 1664 | When it rains, it will trigger an uplink, and the data does not include rainfall data. | ||
| 1665 | If you want to query rainfall data, please change to counting mode | ||
| 1666 | |||
| 1667 | Feature: Users can set the trigger mode to counting mode or interrupt mode as needed. | ||
| 1668 | |||
| 1669 | (% style="color:#037691" %)**AT Command:** | ||
| 1670 | |||
| 1671 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:433px" %) | ||
| 1672 | |=(% style="width: 157px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 190px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 86px;background-color:#4F81BD;color:white" %)**Response** | ||
| 1673 | |(% style="width:157px" %)AT+COUNTMOD=0|(% style="width:188px" %)set to interrupt mode|(% style="width:85px" %)OK | ||
| 1674 | |(% style="width:157px" %)AT+COUNTMOD=1|(% style="width:188px" %)((( | ||
| 1675 | set to counting mode | ||
| 1676 | )))|(% style="width:85px" %)OK | ||
| 1677 | |||
| 1678 | (% style="color:#037691" %)**Downlink Command:** | ||
| 1679 | |||
| 1680 | Format: Command Code (0x10) followed by 1 bytes time value. | ||
| 1681 | |||
| 1682 | If the downlink payload=10 00, Set the trigger mode to interrupt mode, while type code is 10. | ||
| 1683 | |||
| 1684 | * Example 1: Downlink Payload: 10 00 ~/~/ Same as: AT+COUNTMOD=0 set to interrupt mode | ||
| 1685 | |||
| 1686 | = 9. Order Info = | ||
| 1687 | |||
| 1688 | Part Number: (% style="color:blue" %)**WSC2-C-XX / WSC2-CS-XX** | ||
| 1689 | |||
| 1690 | (% style="color:red" %)**XX**(%%): | ||
| 1691 | |||
| 1692 | * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card) | ||
| 1693 | |||
| 1694 | * (% style="color:#037691" %)**1T**(%%): with 1NCE * 10 years 500MB SIM card and Pre-configure to ThingsEye server | ||
| 1695 | |||
| 1696 | = 10. Support = | ||
| 1697 | |||
| 1698 | * 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. | ||
| 1699 | |||
| 1700 | * 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.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]. |