Wiki source code of WSC2-L -- Weather Station Kit User Manual
Last modified by Xiaoling on 2025/05/06 10:05
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 LoRaWAN transmitter WSC2-L, a 9 in 1 Weather Station WSS-09 and a Rain Gauge WSS-08**. | ||
| 32 | |||
| 33 | (% style="color:blue" %)**Please note that the WSC2-L 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 LoRaWAN 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-L is full compatible with LoRaWAN Class A protocol, it can work with standard LoRaWAN gateway. | ||
| 40 | |||
| 41 | |||
| 42 | == 1.2 Features & Spec for WSC2-L Transmitter == | ||
| 43 | |||
| 44 | |||
| 45 | * LoRaWAN 1.0.3 Class A | ||
| 46 | * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865 | ||
| 47 | * Ultra-low power consumption | ||
| 48 | * Support WSS09 9 in 1 Sensors: Wind Speed, Wind Direction, Temperature, Humidity, Air Pressure, Illumination, PM2.5, PM10, Noise & Rain Gauge | ||
| 49 | * RS485 Interface for 3rd party Sensors | ||
| 50 | * Support WSS08 optical Rain Gauge or tipping bucket Rain Gauge | ||
| 51 | * Support Bluetooth v5.1 and LoRaWAN remote configure | ||
| 52 | * Support wireless OTA update firmware | ||
| 53 | * AT Commands to change parameters | ||
| 54 | * Downlink to change configure | ||
| 55 | * IP66 Waterproof Enclosure | ||
| 56 | * 1000mAh Rechargeable Li-ion Battery | ||
| 57 | * Input and Recharge power: 12v | ||
| 58 | |||
| 59 | == 1.3 Specification for WSS-09 9 in 1 weather sensors == | ||
| 60 | |||
| 61 | Older versions of interfaces New version of the interface | ||
| 62 | |||
| 63 | [[image:image-20240708092247-1.png]] [[image:image-20250505190455-1.png||height="283" width="226"]] | ||
| 64 | |||
| 65 | More Detail: [[WSS-09 Manual.>>doc:Main.Agriculture & Weather Stations.WebHome||anchor="H1.WSS099in1WeatherStationSensor"]] | ||
| 66 | |||
| 67 | |||
| 68 | (% style="color:blue" %)**Wind Speed:** | ||
| 69 | |||
| 70 | * Range: 0~~60m/s | ||
| 71 | * Accuracy: ±(0.2m/s±0.02*v)(v : the wind speed) | ||
| 72 | * Ultrasonic measurement,no start wind strength needed | ||
| 73 | |||
| 74 | (% style="color:blue" %)**Wind Direction:** | ||
| 75 | |||
| 76 | * Range: 0~~3599 | ||
| 77 | * Accuracy: ±3° | ||
| 78 | * Ultrasonic measurement,no start wind strength needed | ||
| 79 | * Built-in electronic compass. No need to consider installation direction | ||
| 80 | |||
| 81 | (% style="color:blue" %)**Temperature:** | ||
| 82 | |||
| 83 | * Range: -40°C ~~ +80°C | ||
| 84 | * Accuracy: ±0.5°C | ||
| 85 | |||
| 86 | (% style="color:blue" %)**Humidity:** | ||
| 87 | |||
| 88 | * Range: 0 ~~ 99% RH | ||
| 89 | * Accuracy Tolerance : Typ ±3% RH | ||
| 90 | |||
| 91 | (% style="color:blue" %)**Air Pressure:** | ||
| 92 | |||
| 93 | * Accuracy: ±0.15kPa@25°C 101kPa | ||
| 94 | * Range: 0~~120kPa | ||
| 95 | |||
| 96 | (% style="color:blue" %)**Noise:** | ||
| 97 | |||
| 98 | * Range: 30dB~~120dB | ||
| 99 | * Accuracy: ±0.5dB | ||
| 100 | |||
| 101 | (% style="color:blue" %)**PM2.5:** | ||
| 102 | |||
| 103 | * Range: 0~~1000ug/m3 | ||
| 104 | * Accuracy: ±3%FS | ||
| 105 | * Resolution: 1ug/m3 | ||
| 106 | |||
| 107 | (% style="color:blue" %)**PM10:** | ||
| 108 | |||
| 109 | * Range: 0~~1000ug/m3 | ||
| 110 | * Accuracy: ±3%FS | ||
| 111 | * Resolution: 1ug/m3 | ||
| 112 | |||
| 113 | (% style="color:blue" %)**llumination:** | ||
| 114 | |||
| 115 | * Range: 0~~200k Lux | ||
| 116 | * Accuracy: ±7%(25 °C) | ||
| 117 | |||
| 118 | == 1.4 Specification for WSS-08 Optical Rain Guage == | ||
| 119 | |||
| 120 | Older versions of interfaces New version of the interface | ||
| 121 | |||
| 122 | [[image:image-20240707215336-2.png||height="159" width="218"]] [[image:image-20250505190636-2.png||height="158" width="201"]] | ||
| 123 | |||
| 124 | * Input Power: 9~~30 VDC | ||
| 125 | * Sense diameter: 6cm | ||
| 126 | * Pulse Output | ||
| 127 | |||
| 128 | More Detail: [[WSS-08 Manual.>>doc:Main.Agriculture & Weather Stations.WebHome||anchor="H2.WSS08OpticalRangeGuage"]] | ||
| 129 | |||
| 130 | = 2. How to use = | ||
| 131 | |||
| 132 | == 2.1 Installation == | ||
| 133 | |||
| 134 | |||
| 135 | Below is an installation example for the weather station: | ||
| 136 | |||
| 137 | [[image:image-20240327231510-1.png||height="499" width="1156"]] | ||
| 138 | |||
| 139 | |||
| 140 | (% style="color:blue" %)** Wiring:** | ||
| 141 | |||
| 142 | 1. WSC2-L and sensors all powered by solar power via MPPT | ||
| 143 | 1. WSC2-L Weather Station Kit already include 9 sensors. | ||
| 144 | 1. Possible to add optional 3rd sensors to measure more parameter | ||
| 145 | |||
| 146 | (% style="color:red" %)**Notice 1:** | ||
| 147 | |||
| 148 | * All weather sensors and WSC2-L are powered by MPPT solar recharge controller. MPPT is connected to solar panel and storage battery. | ||
| 149 | * Weather sensors won't work if solar panel and storage battery fails. | ||
| 150 | |||
| 151 | (% style="color:red" %)**Notice 2:** | ||
| 152 | |||
| 153 | Due to shipment and importation limitation, user is better to purchase below parts locally: | ||
| 154 | |||
| 155 | * Solar Panel | ||
| 156 | * Storage Battery | ||
| 157 | * MPPT Solar Recharger | ||
| 158 | * Cabinet. | ||
| 159 | |||
| 160 | == 2.2 How it works? == | ||
| 161 | |||
| 162 | |||
| 163 | ((( | ||
| 164 | Each WSC2-L is shipped with a worldwide unique set of OTAA keys. To use WSC2-L in a LoRaWAN network, user needs to input the OTAA keys in LoRaWAN network server. After finish installation as above. Create WSC2-L in your LoRaWAN server and Power on WSC2-L , it can join the LoRaWAN network and start to transmit sensor data. The default period for each uplink is 20 minutes. | ||
| 165 | ))) | ||
| 166 | |||
| 167 | |||
| 168 | == 2.3 Example to use for LoRaWAN network == | ||
| 169 | |||
| 170 | |||
| 171 | This section shows an example for how to join the TTN V3 LoRaWAN IoT server. Usages with other LoRaWAN IoT servers are of similar procedure. | ||
| 172 | |||
| 173 | Assume the DLOS8 is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. We need to add the WSC2-L device in TTN V3: | ||
| 174 | |||
| 175 | |||
| 176 | (% style="color:blue" %)**Step 1**(%%): Create a device in TTN V3 with the OTAA keys from WSC2-L. | ||
| 177 | |||
| 178 | Each WSC2-L is shipped with a sticker with the default device EUI as below: | ||
| 179 | |||
| 180 | [[image:image-20230426084533-1.png||height="231" width="497"]] | ||
| 181 | |||
| 182 | |||
| 183 | User can enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot: | ||
| 184 | |||
| 185 | The user needs to press and hold the ACT button(Push button) for more than 3s to start the node. | ||
| 186 | |||
| 187 | [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png||height="386" width="262"]] | ||
| 188 | |||
| 189 | |||
| 190 | **Create the application.** | ||
| 191 | |||
| 192 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SAC01L_LoRaWAN_Temperature%26Humidity_Sensor_User_Manual/WebHome/image-20250423093843-1.png?width=756&height=264&rev=1.1||alt="image-20250423093843-1.png"]] | ||
| 193 | |||
| 194 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111305-2.png?width=1000&height=572&rev=1.1||alt="image-20240907111305-2.png"]] | ||
| 195 | |||
| 196 | |||
| 197 | **Add devices to the created Application.** | ||
| 198 | |||
| 199 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111659-3.png?width=977&height=185&rev=1.1||alt="image-20240907111659-3.png"]] | ||
| 200 | |||
| 201 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111820-5.png?width=975&height=377&rev=1.1||alt="image-20240907111820-5.png"]] | ||
| 202 | |||
| 203 | |||
| 204 | **Enter end device specifics manually.** | ||
| 205 | |||
| 206 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112136-6.png?width=697&height=687&rev=1.1||alt="image-20240907112136-6.png"]] | ||
| 207 | |||
| 208 | |||
| 209 | **Add DevEUI and AppKey.** | ||
| 210 | |||
| 211 | **Customize a platform ID for the device.** | ||
| 212 | |||
| 213 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112427-7.png?rev=1.1||alt="image-20240907112427-7.png"]] | ||
| 214 | |||
| 215 | |||
| 216 | (% style="color:blue" %)**Step 2**(%%): Add decoder. | ||
| 217 | |||
| 218 | In TTN, user can add a custom payload so it shows friendly reading. | ||
| 219 | |||
| 220 | Click this link to get the decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/WSC2-LB>>https://github.com/dragino/dragino-end-node-decoder/tree/main/WSC2-LB]] | ||
| 221 | |||
| 222 | Below is TTN screen shot: | ||
| 223 | |||
| 224 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140556-1.png?width=1184&height=488&rev=1.1||alt="image-20241009140556-1.png" height="488" width="1184"]] | ||
| 225 | |||
| 226 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140603-2.png?width=1168&height=562&rev=1.1||alt="image-20241009140603-2.png" height="562" width="1168"]] | ||
| 227 | |||
| 228 | |||
| 229 | ((( | ||
| 230 | (% style="color:blue" %)**Step 3**(%%): Power on WSC2-L, it will start to join TTN server. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel. | ||
| 231 | ))) | ||
| 232 | |||
| 233 | [[image:image-20240413134413-1.png||height="244" width="854"]] | ||
| 234 | |||
| 235 | |||
| 236 | == 2.4 Uplink Payload == | ||
| 237 | |||
| 238 | |||
| 239 | Uplink payloads include two types: Valid Sensor Value and other status / control command. | ||
| 240 | |||
| 241 | * Valid Sensor Value: Use FPORT=2 | ||
| 242 | * Other control command: Use FPORT other than 2. | ||
| 243 | |||
| 244 | === 2.4.1 Uplink FPORT~=5, Device Status === | ||
| 245 | |||
| 246 | Uplink the device configures with FPORT=5. Once WSC2-L Joined the network, it will uplink this message to the server. | ||
| 247 | |||
| 248 | ((( | ||
| 249 | User can also use downlink command**(0x2601)** to ask WSC2-L to resend this uplink | ||
| 250 | ))) | ||
| 251 | |||
| 252 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %) | ||
| 253 | |=(% style="width: 70px;background-color:#4F81BD;color:white" %)**Size(**bytes)|=(% style="width: 85px;background-color:#4F81BD;color:white" %)1|=(% style="width: 105px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 105px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 85px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**2** | ||
| 254 | |(% style="width:99px" %)Value|(% style="width:112px" %)[[Sensor Model>>||anchor="HSensorModel:"]]|(% style="width:135px" %)[[Firmware Version>>||anchor="HFirmwareVersion:"]]|(% style="width:126px" %)[[Frequency Band>>||anchor="HFrequencyBand:"]]|(% style="width:85px" %)[[Sub-band>>||anchor="HSub-Band:"]]|(% style="width:46px" %)[[BAT>>||anchor="HBAT:"]] | ||
| 255 | |||
| 256 | [[image:image-20240415092848-2.png||height="329" width="1045"]] | ||
| 257 | |||
| 258 | |||
| 259 | Example Payload (FPort=5): [[image:image-20240415091027-1.png||height="16" width="104"]] | ||
| 260 | |||
| 261 | |||
| 262 | ==== (% style="color:#037691" %)**Sensor Model:**(%%) ==== | ||
| 263 | |||
| 264 | For WSC2-L, this value is 0x2E. | ||
| 265 | |||
| 266 | |||
| 267 | ==== (% style="color:#037691" %)**Firmware Version:**(%%) ==== | ||
| 268 | |||
| 269 | 0x0100, Means: v1.0.0 version. | ||
| 270 | |||
| 271 | |||
| 272 | ==== (% style="color:#037691" %)**Frequency Band:**(%%) ==== | ||
| 273 | |||
| 274 | 0x01: EU868 | ||
| 275 | |||
| 276 | 0x02: US915 | ||
| 277 | |||
| 278 | 0x03: IN865 | ||
| 279 | |||
| 280 | 0x04: AU915 | ||
| 281 | |||
| 282 | 0x05: KZ865 | ||
| 283 | |||
| 284 | 0x06: RU864 | ||
| 285 | |||
| 286 | 0x07: AS923 | ||
| 287 | |||
| 288 | 0x08: AS923-1 | ||
| 289 | |||
| 290 | 0x09: AS923-2 | ||
| 291 | |||
| 292 | 0x0a: AS923-3 | ||
| 293 | |||
| 294 | |||
| 295 | ==== (% style="color:#037691" %)**Sub-Band:**(%%) ==== | ||
| 296 | |||
| 297 | value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00) | ||
| 298 | |||
| 299 | |||
| 300 | ==== (% style="color:#037691" %)**BAT:**(%%) ==== | ||
| 301 | |||
| 302 | ((( | ||
| 303 | shows the battery voltage for WSC2-L MCU. | ||
| 304 | ))) | ||
| 305 | |||
| 306 | ((( | ||
| 307 | Ex1: 0x0FE4/1000 = 4068/1000=4.068V | ||
| 308 | ))) | ||
| 309 | |||
| 310 | |||
| 311 | Users can also use the downlink command (0x2301) to change the uplink port of WSC2-L: | ||
| 312 | |||
| 313 | (% style="color:#037691" %)**Example**(%%) (% style="color:#037691" %)**Downlink:0x23 01(Change to port 1)** | ||
| 314 | |||
| 315 | [[image:image-20240413104831-3.png||height="364" width="934"]] | ||
| 316 | |||
| 317 | |||
| 318 | === 2.4.2 Uplink FPORT~=2, Real time sensor value === | ||
| 319 | |||
| 320 | |||
| 321 | ((( | ||
| 322 | WSC2-L will send this uplink after Device Config uplink once join LoRaWAN network successfully. And it will periodically send this uplink. Default interval is 20 minutes and [[can be changed>>||anchor="H3.1SetTransmitIntervalTime"]]. | ||
| 323 | ))) | ||
| 324 | |||
| 325 | ((( | ||
| 326 | Uplink uses FPORT=2 and every 20 minutes send one uplink by default. | ||
| 327 | ))) | ||
| 328 | |||
| 329 | |||
| 330 | ((( | ||
| 331 | The upload length is dynamic, depends on what type of weather sensors are connected. The uplink payload is combined with sensor segments. As below: | ||
| 332 | ))) | ||
| 333 | |||
| 334 | |||
| 335 | (% style="color:#4472c4" %)** Uplink Payload**: | ||
| 336 | |||
| 337 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:464px" %) | ||
| 338 | |(% style="width:140px" %)Sensor Segment 1|(% style="width:139px" %)Sensor Segment 2|(% style="width:42px" %)……|(% style="width:140px" %)Sensor Segment n | ||
| 339 | |||
| 340 | (% style="color:#4472c4" %)** Sensor Segment Define**: | ||
| 341 | |||
| 342 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:330px" %) | ||
| 343 | |(% style="width:89px" %)Type Code|(% style="width:114px" %)Length (Bytes)|(% style="width:124px" %)Measured Value | ||
| 344 | |||
| 345 | (% style="color:#4472c4" %)**Sensor Type Table:** | ||
| 346 | |||
| 347 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) | ||
| 348 | |(% style="background-color:#4f81bd; color:white; width:80px" %)**Sensor Type**|(% style="background-color:#4f81bd; color:white; width:65px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:116px" %)**Range**|(% style="background-color:#4f81bd; color:white; width:88px" %)**Length( Bytes)**|(% style="background-color:#4f81bd; color:white; width:166px" %)**Example** | ||
| 349 | |(% style="width:103px" %)Wind Speed|(% style="width:91px" %)0x01|(% style="width:116px" %)((( | ||
| 350 | Speed: 0 ~~ 60m/s | ||
| 351 | )))|(% style="width:88px" %)0x02 |(% style="width:181px" %)((( | ||
| 352 | 0x0028/100=0.40m/s | ||
| 353 | ))) | ||
| 354 | |(% style="width:103px" %)Wind Level|(% style="width:91px" %)0x02|(% style="width:116px" %)Wind Level: (0 ~~18)|(% style="width:88px" %)0x02|(% style="width:181px" %)0x0002=2(Current wind level) | ||
| 355 | |(% style="width:103px" %)((( | ||
| 356 | Wind Direction | ||
| 357 | )))|(% style="width:91px" %)0x03|(% style="width:116px" %)Direction: 0~~7|(% style="width:88px" %)0x02|(% style="width:181px" %)((( | ||
| 358 | 0X0004=3(Due north is 0, increasing clockwise, and due east is 2) | ||
| 359 | ))) | ||
| 360 | |(% style="width:103px" %)Wind Angle|(% style="width:91px" %)0x04|(% style="width:116px" %)((( | ||
| 361 | Angel: 0 ~~ 359° | ||
| 362 | )))|(% style="width:88px" %)0x02|(% style="width:181px" %)((( | ||
| 363 | 0x02C9/10=66.6°(Due north is 0°, increasing clockwise, due east is 90°) | ||
| 364 | ))) | ||
| 365 | |(% style="width:103px" %)Humidity|(% style="width:91px" %)0x05|(% style="width:116px" %)Hum: 099%RH|(% style="width:88px" %)0x02|(% style="width:181px" %)0x0164/10=35.6%RH | ||
| 366 | |(% style="width:103px" %)Temperature|(% style="width:91px" %)0x06|(% style="width:116px" %)Temp: -40 ~~ +80°C|(% style="width:88px" %)0x02|(% style="width:181px" %)((( | ||
| 367 | 0xFFDD/10=-3.5°C | ||
| 368 | ))) | ||
| 369 | |(% style="width:103px" %)Noise|(% style="width:91px" %)0x07|(% style="width:116px" %)Nosie: 30~~120dB|(% style="width:88px" %)0x02|(% style="width:181px" %)((( | ||
| 370 | 0x023e/10=57.4dB | ||
| 371 | ))) | ||
| 372 | |(% style="width:103px" %)((( | ||
| 373 | PM2.5 / CO2 | ||
| 374 | )))|(% style="width:91px" %)0x08|(% style="width:116px" %)((( | ||
| 375 | PM2.5: 01000μg/m^^3^^ | ||
| 376 | |||
| 377 | CO2: 0~~5000ppm | ||
| 378 | )))|(% style="width:88px" %)0x02|(% style="width:181px" %)((( | ||
| 379 | 0x0023=35μg/m^^3 ^^ | ||
| 380 | |||
| 381 | 0x04fb=1275ppm | ||
| 382 | ))) | ||
| 383 | |(% style="width:103px" %)PM10|(% style="width:91px" %)0x09|(% style="width:116px" %)((( | ||
| 384 | PM10: 01000μg/m^^3^^ | ||
| 385 | )))|(% style="width:88px" %)0x02|(% style="width:181px" %)((( | ||
| 386 | 0x002D=45μg/m^^3 ^^ | ||
| 387 | ))) | ||
| 388 | |(% style="width:103px" %)Pressure|(% style="width:91px" %)0x0A|(% style="width:116px" %)0~~120kPa/y|(% style="width:88px" %)0x02|(% style="width:181px" %)((( | ||
| 389 | 0x2748/10=1005.6kPa | ||
| 390 | ))) | ||
| 391 | |(% style="width:103px" %)illumination|(% style="width:91px" %)0x0B|(% style="width:116px" %)0200000kLux|(% style="width:88px" %)0x04|(% style="width:181px" %)0x04D2*10=12340kLux | ||
| 392 | |||
| 393 | ((( | ||
| 394 | Below is an example payload: 0FF60100000000012F00280001000400AD025E0117023E0023003203ED0001678390A102FFFF | ||
| 395 | ))) | ||
| 396 | |||
| 397 | |||
| 398 | ((( | ||
| 399 | When sending this payload to LoRaWAN server. WSC2-L will send this in one uplink or several uplinks according to LoRaWAN spec requirement. For example, total length of Payload is 54 bytes. | ||
| 400 | ))) | ||
| 401 | |||
| 402 | * ((( | ||
| 403 | When WSC2-L sending in US915 frequency DR0 data rate. Because this data rate has limitation of 11 bytes payload for each uplink. The payload will be split into below packets and uplink. | ||
| 404 | ))) | ||
| 405 | |||
| 406 | ((( | ||
| 407 | Uplink 1: [[image:image-20240418135453-1.png||height="26" width="202"]](% style="display:none" %) | ||
| 408 | ))) | ||
| 409 | |||
| 410 | ((( | ||
| 411 | Uplink 2: [[image:image-20240418141234-5.png||height="38" width="352"]](% style="display:none" %) | ||
| 412 | ))) | ||
| 413 | |||
| 414 | |||
| 415 | * ((( | ||
| 416 | When WSC2-L sending in EU868 frequency DR0 data rate. The payload will be split into below packets and uplink: | ||
| 417 | ))) | ||
| 418 | |||
| 419 | ((( | ||
| 420 | Uplink 1: [[image:image-20240418141304-6.png||height="39" width="408"]] | ||
| 421 | ))) | ||
| 422 | |||
| 423 | Uplink 2: [[image:image-20240418141312-7.png||height="24" width="74"]] | ||
| 424 | |||
| 425 | |||
| 426 | === 2.4.3 Decoder in TTN V3 === | ||
| 427 | |||
| 428 | |||
| 429 | ((( | ||
| 430 | In LoRaWAN platform, user only see HEX payload by default, user needs to use payload formatters to decode the payload to see human-readable value. | ||
| 431 | ))) | ||
| 432 | |||
| 433 | ((( | ||
| 434 | Download decoder for suitable platform from: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]] | ||
| 435 | ))) | ||
| 436 | |||
| 437 | ((( | ||
| 438 | and put as below: | ||
| 439 | ))) | ||
| 440 | |||
| 441 | [[image:image-20240413140757-2.png||height="423" width="892"]] | ||
| 442 | |||
| 443 | |||
| 444 | == 2.5 Show data on Application Server == | ||
| 445 | |||
| 446 | |||
| 447 | ((( | ||
| 448 | Application platform provides a human friendly interface to show the sensor data, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps: | ||
| 449 | ))) | ||
| 450 | |||
| 451 | ((( | ||
| 452 | (% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the LoRaWAN network. | ||
| 453 | ))) | ||
| 454 | |||
| 455 | ((( | ||
| 456 | (% style="color:blue" %)**Step 2**(%%): Configure your Application to forward data to Datacake you will need to add integration. Go to TTN V3 Console ~-~-> Applications ~-~-> Integrations ~-~-> Add Integrations. | ||
| 457 | ))) | ||
| 458 | |||
| 459 | [[image:1656051197172-131.png]] | ||
| 460 | |||
| 461 | |||
| 462 | |||
| 463 | **Add TagoIO:** | ||
| 464 | |||
| 465 | [[image:1656051223585-631.png]] | ||
| 466 | |||
| 467 | |||
| 468 | |||
| 469 | **Authorization:** | ||
| 470 | |||
| 471 | [[image:1656051248318-368.png]] | ||
| 472 | |||
| 473 | |||
| 474 | In TagoIO console ([[https:~~/~~/admin.tago.io~~/~~/>>url:https://datacake.co/]]) , add WSC2-L: | ||
| 475 | |||
| 476 | |||
| 477 | [[image:1656051277767-168.png]] | ||
| 478 | |||
| 479 | |||
| 480 | == 2.6 Frequency Plans == | ||
| 481 | |||
| 482 | |||
| 483 | The WSC2-L uses OTAA mode and below frequency plans by default. Each frequency band use different firmware, user update the firmware to the corresponding band for their country. | ||
| 484 | |||
| 485 | [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]] | ||
| 486 | |||
| 487 | |||
| 488 | = 3. Configure WSC2-L = | ||
| 489 | |||
| 490 | == 3.1 Configure Methods == | ||
| 491 | |||
| 492 | |||
| 493 | WSC2-L supports below configure method: | ||
| 494 | |||
| 495 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
| 496 | |||
| 497 | * 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]]. | ||
| 498 | |||
| 499 | * LoRaWAN Downlink. Instruction for different platforms: See [[IoT LoRaWAN Server>>http://wiki.dragino.com/xwiki/bin/view/Main/]] section. | ||
| 500 | |||
| 501 | == 3.2 General Commands == | ||
| 502 | |||
| 503 | |||
| 504 | These commands are to configure: | ||
| 505 | |||
| 506 | * General system settings like: uplink interval. | ||
| 507 | * LoRaWAN protocol & radio related command. | ||
| 508 | |||
| 509 | They are same for all Dragino Devices which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: | ||
| 510 | |||
| 511 | [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]] | ||
| 512 | |||
| 513 | |||
| 514 | == 3.3 Commands special design for WSC2-L == | ||
| 515 | |||
| 516 | |||
| 517 | These commands only valid for WSC2-L, as below: | ||
| 518 | |||
| 519 | |||
| 520 | === 3.3.1 Set Transmit Interval Time === | ||
| 521 | |||
| 522 | |||
| 523 | Feature: Change LoRaWAN End Node Transmit Interval. | ||
| 524 | |||
| 525 | (% style="color:#037691" %)**AT Command: AT+TDC** | ||
| 526 | |||
| 527 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:501px" %) | ||
| 528 | |(% 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** | ||
| 529 | |(% style="width:155px" %)AT+TDC=?|(% style="width:162px" %)Show current transmit Interval|(% style="width:177px" %)((( | ||
| 530 | 30000 | ||
| 531 | OK | ||
| 532 | the interval is 30000ms = 30s | ||
| 533 | ))) | ||
| 534 | |(% style="width:155px" %)AT+TDC=60000|(% style="width:162px" %)Set Transmit Interval|(% style="width:177px" %)((( | ||
| 535 | OK | ||
| 536 | Set transmit interval to 60000ms = 60 seconds | ||
| 537 | ))) | ||
| 538 | |||
| 539 | (% style="color:#037691" %)**Downlink Command: 0x01** | ||
| 540 | |||
| 541 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
| 542 | |||
| 543 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
| 544 | |||
| 545 | * Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
| 546 | * Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
| 547 | |||
| 548 | === 3.3.2 Set the CO2 or PM mode === | ||
| 549 | |||
| 550 | |||
| 551 | (% 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.** | ||
| 552 | |||
| 553 | Feature: Set the CO2/PM mode, and the user can set the corresponding mode according to the purchased sensor. | ||
| 554 | |||
| 555 | (% style="color:#037691" %)**AT Command:** | ||
| 556 | |||
| 557 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:466px" %) | ||
| 558 | |(% 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** | ||
| 559 | |(% style="width:155px" %)AT+PMMOD=1|(% style="width:224px" %)The working sensors are PM2.5 and PM10|(% style="width:84px" %)((( | ||
| 560 | OK | ||
| 561 | |||
| 562 | ))) | ||
| 563 | |(% style="width:155px" %)AT+PMMOD=0|(% style="width:224px" %)The working sensors are CO2|(% style="width:84px" %)((( | ||
| 564 | OK | ||
| 565 | ))) | ||
| 566 | |||
| 567 | (% style="color:#037691" %)**Downlink Command:** | ||
| 568 | |||
| 569 | * 0xE101 Same as: AT+PMMOD=1 | ||
| 570 | * 0xE100 Same as: AT+PMMOD=0 | ||
| 571 | |||
| 572 | === 3.3.3 Add or Delete RS485 Sensor === | ||
| 573 | |||
| 574 | |||
| 575 | ((( | ||
| 576 | 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. | ||
| 577 | ))) | ||
| 578 | |||
| 579 | ((( | ||
| 580 | (% style="color:#037691" %)**AT Command: ** | ||
| 581 | ))) | ||
| 582 | |||
| 583 | ((( | ||
| 584 | (% style="color:blue" %)**AT+DYSENSOR=Type_Code, Query_Length, Query_Command , Read_Length , Valid_Data ,has_CRC,timeout** | ||
| 585 | ))) | ||
| 586 | |||
| 587 | * ((( | ||
| 588 | Type_Code range: A1 ~~ A4 | ||
| 589 | ))) | ||
| 590 | * ((( | ||
| 591 | Query_Length: RS485 Query frame length, Value cannot be greater than 10 | ||
| 592 | ))) | ||
| 593 | * ((( | ||
| 594 | Query_Command: RS485 Query frame data to be sent to sensor, cannot be larger than 10 bytes | ||
| 595 | ))) | ||
| 596 | * ((( | ||
| 597 | Read_Length: RS485 response frame length supposed to receive. Max can receive | ||
| 598 | ))) | ||
| 599 | * ((( | ||
| 600 | Valid_Data: valid data from RS485 Response, Valid Data will be added to Payload and upload via LoRaWAN. | ||
| 601 | ))) | ||
| 602 | * ((( | ||
| 603 | 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. | ||
| 604 | ))) | ||
| 605 | * ((( | ||
| 606 | timeout: RS485 receive timeout (uint:ms). Device will close receive window after timeout | ||
| 607 | ))) | ||
| 608 | |||
| 609 | ((( | ||
| 610 | **Example:** | ||
| 611 | ))) | ||
| 612 | |||
| 613 | ((( | ||
| 614 | User need to change external sensor use the type code as address code. | ||
| 615 | ))) | ||
| 616 | |||
| 617 | ((( | ||
| 618 | With a 485 sensor, after correctly changing the address code to A1, the RS485 query frame is shown in the following table: | ||
| 619 | ))) | ||
| 620 | |||
| 621 | [[image:image-20220624143553-10.png]] | ||
| 622 | |||
| 623 | |||
| 624 | The response frame of the sensor is as follows: | ||
| 625 | |||
| 626 | [[image:image-20220624143618-11.png]] | ||
| 627 | |||
| 628 | |||
| 629 | **Then the following parameters should be:** | ||
| 630 | |||
| 631 | * Address_Code range: A1 | ||
| 632 | * Query_Length: 8 | ||
| 633 | * Query_Command: A103000000019CAA | ||
| 634 | * Read_Length: 8 | ||
| 635 | * Valid_Data: 23 (Indicates that the data length is 2 bytes, starting from the 3th byte) | ||
| 636 | * has_CRC: 1 | ||
| 637 | * timeout: 1500 (Fill in the test according to the actual situation) | ||
| 638 | |||
| 639 | **So the input command is:** | ||
| 640 | |||
| 641 | AT+DYSENSOR=A1,8,A103000000019CAA,8,24,1,1500 | ||
| 642 | |||
| 643 | |||
| 644 | In every sampling. WSC2-L will auto append the sensor segment as per this structure and uplink. | ||
| 645 | |||
| 646 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:351px" %) | ||
| 647 | |=(% 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 | ||
| 648 | |(% style="width:94px" %)A1|(% style="width:121px" %)2|(% style="width:132px" %)0x000A | ||
| 649 | |||
| 650 | **Related commands:** | ||
| 651 | |||
| 652 | AT+DYSENSOR=A1,0 ~-~-> Delete 3^^rd^^ party sensor A1. | ||
| 653 | |||
| 654 | AT+DYSENSOR ~-~-> List All 3^^rd^^ Party Sensor. Like below: | ||
| 655 | |||
| 656 | |||
| 657 | (% style="color:#037691" %)**Downlink Command: ** | ||
| 658 | |||
| 659 | **delete custom sensor A1:** | ||
| 660 | |||
| 661 | * 0xE5A1 Same as: AT+DYSENSOR=A1,0 | ||
| 662 | |||
| 663 | **Remove all custom sensors** | ||
| 664 | |||
| 665 | * 0xE5FF | ||
| 666 | |||
| 667 | === 3.3.4 RS485 Test Command === | ||
| 668 | |||
| 669 | |||
| 670 | (% style="color:#037691" %)**AT Command:** | ||
| 671 | |||
| 672 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:494px" %) | ||
| 673 | |=(% 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** | ||
| 674 | |(% style="width:159px" %)AT+RSWRITE=xxxxxx|(% style="width:227px" %)((( | ||
| 675 | Send command to 485 sensor. Range : no more than 10 bytes | ||
| 676 | )))|(% style="width:85px" %)OK | ||
| 677 | |||
| 678 | Eg: Send command **01 03 00 00 00 01 84 0A** to 485 sensor | ||
| 679 | |||
| 680 | AT+RSWRITE=0103000001840A | ||
| 681 | |||
| 682 | |||
| 683 | (% style="color:#037691" %)**Downlink Command:** | ||
| 684 | |||
| 685 | * 0xE20103000001840A Same as: AT+RSWRITE=0103000001840A | ||
| 686 | |||
| 687 | === 3.3.5 RS485 response timeout === | ||
| 688 | |||
| 689 | |||
| 690 | Feature: Set or get extended time to receive 485 sensor data. | ||
| 691 | |||
| 692 | (% style="color:#037691" %)**AT Command:** | ||
| 693 | |||
| 694 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:433px" %) | ||
| 695 | |=(% 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** | ||
| 696 | |(% style="width:157px" %)AT+DTR=1000|(% style="width:188px" %)((( | ||
| 697 | Set response timeout to: Range : 0~~10000 | ||
| 698 | )))|(% style="width:85px" %)OK | ||
| 699 | |||
| 700 | (% style="color:#037691" %)**Downlink Command:** | ||
| 701 | |||
| 702 | Format: Command Code (0xE0) followed by 3 bytes time value. | ||
| 703 | |||
| 704 | If the downlink payload=E0000005, it means set the END Node's Transmit Interval to 0x000005=5(S), while type code is E0. | ||
| 705 | |||
| 706 | * Example 1: Downlink Payload: E0000005 ~/~/ Set Transmit Interval (DTR) = 5 seconds | ||
| 707 | * Example 2: Downlink Payload: E000000A ~/~/ Set Transmit Interval (DTR) = 10 seconds | ||
| 708 | |||
| 709 | === 3.3.6 Set or get the total count value === | ||
| 710 | |||
| 711 | |||
| 712 | Feature: The user can set the counting to start from the set value according to the requirements. (only available in counting mode). | ||
| 713 | |||
| 714 | (% style="color:#037691" %)**AT Command:** | ||
| 715 | |||
| 716 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:433px" %) | ||
| 717 | |=(% 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** | ||
| 718 | |(% style="width:157px" %)AT+SETCNT=1000|(% style="width:188px" %)Set the total count to start from 1000|(% style="width:85px" %)OK | ||
| 719 | |||
| 720 | (% style="color:#037691" %)**Downlink Command:** | ||
| 721 | |||
| 722 | Format: Command Code (0x09) followed by 5 bytes time value. | ||
| 723 | |||
| 724 | 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. | ||
| 725 | |||
| 726 | * Example 1: Downlink Payload: 09000003E8 ~/~/ Set the value to start counting from 1000 = 1000 (times) | ||
| 727 | |||
| 728 | === 3.3.7 Set interrupt or counting mode === | ||
| 729 | |||
| 730 | |||
| 731 | Feature: Users can set the trigger mode to counting mode or interrupt mode as needed. | ||
| 732 | |||
| 733 | (% style="color:#037691" %)**AT Command:** | ||
| 734 | |||
| 735 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:433px" %) | ||
| 736 | |=(% 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** | ||
| 737 | |(% style="width:157px" %)AT+COUNTMOD=0|(% style="width:188px" %)set to interrupt mode|(% style="width:85px" %)OK | ||
| 738 | |(% style="width:157px" %)AT+COUNTMOD=1|(% style="width:188px" %)((( | ||
| 739 | set to counting mode | ||
| 740 | )))|(% style="width:85px" %)OK | ||
| 741 | |||
| 742 | (% style="color:#037691" %)**Downlink Command:** | ||
| 743 | |||
| 744 | Format: Command Code (0x10) followed by 1 bytes time value. | ||
| 745 | |||
| 746 | If the downlink payload=10 00, Set the trigger mode to interrupt mode, while type code is 10. | ||
| 747 | |||
| 748 | * Example 1: Downlink Payload: 10 00 ~/~/ Same as: AT+COUNTMOD=0 set to interrupt mode | ||
| 749 | |||
| 750 | == 3.4 Add 3rd RS485 / Modbus Sensor == | ||
| 751 | |||
| 752 | === 3.4.1 Hardware Connection === | ||
| 753 | |||
| 754 | |||
| 755 | WSC2-L 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. | ||
| 756 | |||
| 757 | (% 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.** | ||
| 758 | |||
| 759 | [[image:image-20240707220859-4.png||height="313" width="366"]] | ||
| 760 | |||
| 761 | |||
| 762 | === 3.4.2 Software Setup === | ||
| 763 | |||
| 764 | |||
| 765 | 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. | ||
| 766 | |||
| 767 | For example: AT+DYSENSOR=A1,8,A103000000019CAA,8,24,1,1500 | ||
| 768 | |||
| 769 | |||
| 770 | === 3.4.3 Payload === | ||
| 771 | |||
| 772 | [[image:image-20240416163658-1.png]] | ||
| 773 | |||
| 774 | For example: A1 02 00 00 | ||
| 775 | |||
| 776 | A1 : A1 register data acquisition instruction | ||
| 777 | |||
| 778 | 02 : The valid data returned is 2 bytes in total. | ||
| 779 | |||
| 780 | 00 00 : Return valid data | ||
| 781 | |||
| 782 | |||
| 783 | == 3.5 Add tipping bucket total solar radiation sensor == | ||
| 784 | |||
| 785 | === 3.5.1 Hardware Connection === | ||
| 786 | |||
| 787 | |||
| 788 | 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-L. | ||
| 789 | |||
| 790 | Users can also choose to connect the sensor directly to the WSC2-L via the cable and pin instructions below. | ||
| 791 | |||
| 792 | The following is an explanation of the [[pins>>||anchor="H5.7PinMapping"]] required for WSC2-L： | ||
| 793 | |||
| 794 | **A:** RS485-A (Connect the RS485 sensor) | ||
| 795 | |||
| 796 | **B:** RS485-B (Connect the RS485 sensor) | ||
| 797 | |||
| 798 | **GPIO_EXTI:** Interrupt pin (Can be used to connect an additionally added pulsed rain gauge) | ||
| 799 | |||
| 800 | |||
| 801 | * Total Solar Radiation Sensor Cable Descripti | ||
| 802 | |||
| 803 | [[image:image-20240906174635-2.jpeg||height="430" width="813"]] | ||
| 804 | |||
| 805 | |||
| 806 | |||
| 807 | * Mating Interface Cable Description | ||
| 808 | |||
| 809 | [[image:image-20240906173843-1.jpeg||height="404" width="815"]] | ||
| 810 | |||
| 811 | * Connect to WSC2-L | ||
| 812 | |||
| 813 | The Total solar radiation sensor does not need to connect the interrupt pin, so the white cable is not wired. | ||
| 814 | |||
| 815 | [[image:image-20240906182250-3.jpeg||height="442" width="820"]] | ||
| 816 | |||
| 817 | |||
| 818 | === 3.5.2 Calculating & Decode === | ||
| 819 | |||
| 820 | |||
| 821 | 0FC6 01 00000000 00EB 000F 0000 0003 008E 0251 00CE 0213 0017 001B 03EC 000000DE 90 A1020000 A2020032 | ||
| 822 | |||
| 823 | For example: A2 02 00 32 | ||
| 824 | |||
| 825 | A2 : A2 register data acquisition instruction | ||
| 826 | |||
| 827 | 02 : The valid data returned is 2 bytes in total. | ||
| 828 | |||
| 829 | 00 32(HEX) : Return valid data = 50(DEC)W/m2 | ||
| 830 | |||
| 831 | |||
| 832 | = 4. Power consumption and battery = | ||
| 833 | |||
| 834 | == 4.1 Total Power Consumption == | ||
| 835 | |||
| 836 | |||
| 837 | Dragino Weather Station serial products include the main process unit (WSC2-L) and various sensors. The total power consumption equal total power of all above units. The power consumption for main process unit WSC2-L is 18ma @ 12v. and the power consumption of each sensor can be found on the Sensors chapter. | ||
| 838 | |||
| 839 | |||
| 840 | == 4.2 Reduce power consumption == | ||
| 841 | |||
| 842 | |||
| 843 | The main process unit WSC2-L is set to LoRaWAN Class C by default. If user want to reduce the power consumption of this unit, user can set it to run in Class A. In Class A mode, WSC2-L will not be to get real-time downlink command from IoT Server. | ||
| 844 | |||
| 845 | |||
| 846 | == 4.3 Battery == | ||
| 847 | |||
| 848 | |||
| 849 | ((( | ||
| 850 | All sensors are only power by external power source. If external power source is off. All sensor won't work. | ||
| 851 | ))) | ||
| 852 | |||
| 853 | ((( | ||
| 854 | Main Process Unit WSC2-L is powered by both external power source and internal 1000mAh rechargeable battery. If external power source is off, WSC2-L still runs and can send periodically uplinks, but the sensors value will become invalid. External power source can recharge the 1000mAh rechargeable battery. | ||
| 855 | ))) | ||
| 856 | |||
| 857 | |||
| 858 | = 5. Main Process Unit WSC2-L = | ||
| 859 | |||
| 860 | |||
| 861 | WSC2-L is the main process unit in Dragino Weather Station solution. WSC2-L is an an outdoor LoRaWAN RS485 end node. It is powered by external 12v solar power and have a built-in Li-ion backup battery. | ||
| 862 | |||
| 863 | WSC2-L reads value from various sensors and upload these sensor data to IoT server via LoRaWAN wireless protocol. | ||
| 864 | |||
| 865 | WSC2-L is full compatible with LoRaWAN Class A protocol, it can work with standard LoRaWAN gateway. | ||
| 866 | |||
| 867 | WSC2-L Supports BLE configure and wireless OTA update which make user easy to use. | ||
| 868 | |||
| 869 | Each WSC2-L is pre-load with a set of unique keys for LoRaWAN registration, register these keys to local LoRaWAN server and it will auto connect after power on. | ||
| 870 | |||
| 871 | |||
| 872 | == 5.1 Features == | ||
| 873 | |||
| 874 | |||
| 875 | * LoRaWAN v1.0.3 Class A protocol. | ||
| 876 | * RS485 / Modbus protocol | ||
| 877 | * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915 | ||
| 878 | * AT Commands to change parameters | ||
| 879 | * Downlink to change configure | ||
| 880 | * Powered by external 12v battery | ||
| 881 | * Back up rechargeable 1000mAh battery | ||
| 882 | * IP Rating: IP65 | ||
| 883 | * Support default sensors or 3rd party RS485 sensors | ||
| 884 | * Support Bluetooth v5.1 and LoRaWAN remote configure | ||
| 885 | * Support wireless OTA update firmware | ||
| 886 | * Wall Attachable. | ||
| 887 | |||
| 888 | == 5.2 Power Consumption == | ||
| 889 | |||
| 890 | |||
| 891 | WSC2-L (without external sensor): Idle: 4mA, Transmit: max 40mA | ||
| 892 | |||
| 893 | |||
| 894 | == 5.3 Storage & Operation Temperature == | ||
| 895 | |||
| 896 | |||
| 897 | -20°C to +60°C | ||
| 898 | |||
| 899 | |||
| 900 | == 5.4 Sleep mode and working mode == | ||
| 901 | |||
| 902 | |||
| 903 | (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any LoRaWAN activate. This mode is used for storage and shipping to save battery life. | ||
| 904 | |||
| 905 | (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as LoRaWAN Sensor to Join LoRaWAN network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode. | ||
| 906 | |||
| 907 | |||
| 908 | == 5.5 Button & LEDs == | ||
| 909 | |||
| 910 | |||
| 911 | [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]] | ||
| 912 | |||
| 913 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
| 914 | |=(% 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** | ||
| 915 | |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
| 916 | If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
| 917 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
| 918 | ))) | ||
| 919 | |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
| 920 | (% 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 JOIN LoRaWAN network. | ||
| 921 | (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
| 922 | Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device join or not join LoRaWAN network. | ||
| 923 | ))) | ||
| 924 | |(% 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. | ||
| 925 | |||
| 926 | == 5.6 BLE connection == | ||
| 927 | |||
| 928 | |||
| 929 | WSC2-L supports BLE remote configure. | ||
| 930 | |||
| 931 | 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: | ||
| 932 | |||
| 933 | * Press button to send an uplink | ||
| 934 | * Press button to active device. | ||
| 935 | * Device Power on or reset. | ||
| 936 | |||
| 937 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
| 938 | |||
| 939 | |||
| 940 | == 5.7 Pin Mapping == | ||
| 941 | |||
| 942 | |||
| 943 | [[image:image-20240412165523-2.png]] | ||
| 944 | |||
| 945 | |||
| 946 | == 5.8 Mechanical == | ||
| 947 | |||
| 948 | |||
| 949 | Refer LSn50v2 enclosure drawing in: [[https:~~/~~/www.dropbox.com/sh/0ir0l9jjmk6p95e/AADwWXorcKuNpPR5em7VgrEja?dl=0>>https://www.dropbox.com/sh/0ir0l9jjmk6p95e/AADwWXorcKuNpPR5em7VgrEja?dl=0]] | ||
| 950 | |||
| 951 | |||
| 952 | = 6. OTA Firmware update = | ||
| 953 | |||
| 954 | |||
| 955 | (% class="wikigeneratedid" %) | ||
| 956 | **User can change firmware WSC2-L to:** | ||
| 957 | |||
| 958 | * Change Frequency band/ region. | ||
| 959 | * Update with new features. | ||
| 960 | * Fix bugs. | ||
| 961 | |||
| 962 | **Firmware and changelog can be downloaded from :** **[[Firmware download link>>https://www.dropbox.com/sh/8j3ioji411ni9gu/AADnOw3ErB1REsthKilfaq_Pa?dl=0]]** | ||
| 963 | |||
| 964 | **Methods to Update Firmware:** | ||
| 965 | |||
| 966 | * (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/]]** | ||
| 967 | |||
| 968 | * 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]]**. | ||
| 969 | |||
| 970 | = 7. FAQ = | ||
| 971 | |||
| 972 | == 7.1 What else do I need to purchase to build Weather Station? == | ||
| 973 | |||
| 974 | |||
| 975 | Below is the installation photo and structure: | ||
| 976 | |||
| 977 | [[image:image-20240413172530-3.png]] | ||
| 978 | |||
| 979 | == 7.2 Where can i find the modbus command for the WSS-09 sensor? == | ||
| 980 | |||
| 981 | See this link for the [[modbus command set>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/AK7twfUnkB4qKMvtU4XcEss/LoRaWAN%20End%20Node/WSC2-L%20Combine%20Weather%20Station%20Kit?dl=0&e=2&preview=Weather_Sensors_Modbus_Command_List.xlsx&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]]. | ||
| 982 | |||
| 983 | |||
| 984 | = 8. Trouble Shooting = | ||
| 985 | |||
| 986 | == 8.1 What should I do when the RS485 sensor cannot collect data? == | ||
| 987 | |||
| 988 | |||
| 989 | ~1. Recheck whether the sensor's power supply voltage is 12V at maximum. | ||
| 990 | |||
| 991 | 2. Recheck whether the A and B signal lines of the sensor are connected reversely. | ||
| 992 | |||
| 993 | 3. Check whether the sensor's transmission baud rate is 4800. If not, please change it to 4800 and try reading again. | ||
| 994 | |||
| 995 | |||
| 996 | == 8.2 Why does the weather station make electric current sounds during operation? == | ||
| 997 | |||
| 998 | |||
| 999 | ~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. | ||
| 1000 | |||
| 1001 | |||
| 1002 | == 8.3 How to solve the problem of temperature difference in weather stations? == | ||
| 1003 | |||
| 1004 | |||
| 1005 | You can use AT+RSWRITE (downlink: E2 xx xx xx xx xx xx xx ) to modify the temperature compensation function in the weather station. | ||
| 1006 | |||
| 1007 | **For example：** | ||
| 1008 | |||
| 1009 | 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 . | ||
| 1010 | |||
| 1011 | |||
| 1012 | == 8.4 Why does the rain gauge have no data? == | ||
| 1013 | |||
| 1014 | The default mode of the rain gauge is trigger mode. | ||
| 1015 | When it rains, it will trigger an uplink, and the data does not include rainfall data. | ||
| 1016 | If you want to query rainfall data, please change to counting mode | ||
| 1017 | |||
| 1018 | Feature: Users can set the trigger mode to counting mode or interrupt mode as needed. | ||
| 1019 | |||
| 1020 | (% style="color:#037691" %)**AT Command:** | ||
| 1021 | |||
| 1022 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:433px" %) | ||
| 1023 | |=(% 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** | ||
| 1024 | |(% style="width:157px" %)AT+COUNTMOD=0|(% style="width:188px" %)set to interrupt mode|(% style="width:85px" %)OK | ||
| 1025 | |(% style="width:157px" %)AT+COUNTMOD=1|(% style="width:188px" %)((( | ||
| 1026 | set to counting mode | ||
| 1027 | )))|(% style="width:85px" %)OK | ||
| 1028 | |||
| 1029 | (% style="color:#037691" %)**Downlink Command:** | ||
| 1030 | |||
| 1031 | Format: Command Code (0x10) followed by 1 bytes time value. | ||
| 1032 | |||
| 1033 | If the downlink payload=10 00, Set the trigger mode to interrupt mode, while type code is 10. | ||
| 1034 | |||
| 1035 | * Example 1: Downlink Payload: 10 00 ~/~/ Same as: AT+COUNTMOD=0 set to interrupt mode | ||
| 1036 | |||
| 1037 | = 9. Order Info = | ||
| 1038 | |||
| 1039 | |||
| 1040 | Part Number: (% style="color:blue" %)**WSC2-L-XX** | ||
| 1041 | |||
| 1042 | (% style="color:blue" %)**XX**(%%): The default frequency band | ||
| 1043 | |||
| 1044 | * (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band | ||
| 1045 | * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band | ||
| 1046 | * (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band | ||
| 1047 | * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band | ||
| 1048 | * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band | ||
| 1049 | * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band | ||
| 1050 | * (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band | ||
| 1051 | * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band | ||
| 1052 | |||
| 1053 | = 10. Support = | ||
| 1054 | |||
| 1055 | * 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. | ||
| 1056 | |||
| 1057 | * 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]]. |