Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Karry Zhuang on 2025/03/06 16:34
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -RS485- BL –WaterproofRS485 to LoRaWAN Converter1 +RS485-LN – RS485 to LoRaWAN Converter - Content
-
... ... @@ -167,19 +167,31 @@ 167 167 168 168 [[image:1652953414711-647.png||height="337" width="723"]] 169 169 170 +((( 170 170 The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. 172 +))) 171 171 174 +((( 172 172 The LG308 is already set to connect to [[TTN V3 network >>url:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3: 176 +))) 173 173 178 +((( 174 174 **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL. 180 +))) 175 175 182 +((( 176 176 Each RS485-BL is shipped with a sticker with unique device EUI: 184 +))) 177 177 178 178 [[image:1652953462722-299.png]] 179 179 188 +((( 180 180 User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot: 190 +))) 181 181 192 +((( 182 182 Add APP EUI in the application. 194 +))) 183 183 184 184 185 185 ... ... @@ -207,142 +207,185 @@ 207 207 208 208 [[image:1652953568895-172.png||height="232" width="724"]] 209 209 222 +== 3.3 Configure Commands to read data == 210 210 211 - 212 - 213 -1. 214 -11. Configure Commands to read data 215 - 224 +((( 216 216 There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors. 226 +))) 217 217 228 +=== 3.3.1 onfigure UART settings for RS485 or TTL communication === 218 218 219 -1. 220 -11. 221 -111. Configure UART settings for RS485 or TTL communication 222 - 223 223 RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect. 224 224 225 -1. RS485-MODBUS mode: 232 +**~1. RS485-MODBUS mode:** 226 226 227 227 AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins. 228 228 236 +**2. TTL mode:** 229 229 230 -1. TTL mode: 231 - 232 232 AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins. 233 233 234 - 235 235 RS485-BL default UART settings is **9600, no parity, stop bit 1**. If the sensor has a different settings, user can change the RS485-BL setting to match. 236 236 237 - 238 -|**AT Commands**|**Description**|**Example** 239 -|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|((( 242 +(% border="1" style="background-color:#ffffcc; color:green; width:795px" %) 243 +|((( 244 +**AT Commands** 245 +)))|(% style="width:285px" %)((( 246 +**Description** 247 +)))|(% style="width:347px" %)((( 248 +**Example** 249 +))) 250 +|((( 251 +AT+BAUDR 252 +)))|(% style="width:285px" %)((( 253 +Set the baud rate (for RS485 connection). Default Value is: 9600. 254 +)))|(% style="width:347px" %)((( 255 +((( 240 240 AT+BAUDR=9600 257 +))) 241 241 259 +((( 242 242 Options: (1200,2400,4800,14400,19200,115200) 243 243 ))) 244 -|AT+PARITY|((( 262 +))) 263 +|((( 264 +AT+PARITY 265 +)))|(% style="width:285px" %)((( 266 +((( 245 245 Set UART parity (for RS485 connection) 268 +))) 246 246 270 +((( 247 247 Default Value is: no parity. 248 -)))|((( 272 +))) 273 +)))|(% style="width:347px" %)((( 274 +((( 249 249 AT+PARITY=0 276 +))) 250 250 278 +((( 251 251 Option: 0: no parity, 1: odd parity, 2: even parity 252 252 ))) 253 -|AT+STOPBIT|((( 281 +))) 282 +|((( 283 +AT+STOPBIT 284 +)))|(% style="width:285px" %)((( 285 +((( 254 254 Set serial stopbit (for RS485 connection) 287 +))) 255 255 289 +((( 256 256 Default Value is: 1bit. 257 -)))|((( 291 +))) 292 +)))|(% style="width:347px" %)((( 293 +((( 258 258 AT+STOPBIT=0 for 1bit 295 +))) 259 259 297 +((( 260 260 AT+STOPBIT=1 for 1.5 bit 299 +))) 261 261 301 +((( 262 262 AT+STOPBIT=2 for 2 bits 263 263 ))) 304 +))) 264 264 306 +=== 3.3.2 Configure sensors === 265 265 308 +((( 309 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**. 310 +))) 266 266 312 +((( 313 +When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling. 314 +))) 267 267 268 -1. 269 -11. 270 -111. Configure sensors 271 - 272 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV. 273 - 274 - 275 -When user issue an AT+CFGDEV command, Each AT+CFGDEV equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling. 276 - 277 -|**AT Commands**|**Description**|**Example** 278 -|AT+CFGDEV|((( 316 +(% border="1" style="background-color:#ffffcc; color:green; width:806px" %) 317 +|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example** 318 +|AT+CFGDEV|(% style="width:418px" %)((( 279 279 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. 280 280 281 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx, m321 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx, 282 282 283 -m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 284 -)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 323 +mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 324 +)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 285 285 286 286 Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]]. 287 287 328 +=== 3.3.3 Configure read commands for each sampling === 288 288 289 - 290 - 291 - 292 -1. 293 -11. 294 -111. Configure read commands for each sampling 295 - 330 +((( 296 296 RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink. 332 +))) 297 297 298 - 334 +((( 299 299 During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload. 336 +))) 300 300 301 - 338 +((( 302 302 To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload. 340 +))) 303 303 304 - 342 +((( 305 305 This section describes how to achieve above goals. 344 +))) 306 306 307 - 346 +((( 308 308 During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 348 +))) 309 309 310 - 350 +((( 311 311 **Command from RS485-BL to Sensor:** 352 +))) 312 312 354 +((( 313 313 RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar. 356 +))) 314 314 315 - 358 +((( 316 316 **Handle return from sensors to RS485-BL**: 360 +))) 317 317 362 +((( 318 318 After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands** 364 +))) 319 319 366 +* ((( 367 +**AT+DATACUT** 368 +))) 320 320 321 -* **AT+DATACUT** 322 - 370 +((( 323 323 When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command. 372 +))) 324 324 374 +* ((( 375 +**AT+SEARCH** 376 +))) 325 325 326 -* **AT+SEARCH** 327 - 378 +((( 328 328 When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string. 380 +))) 329 329 330 - 382 +((( 331 331 **Define wait timeout:** 384 +))) 332 332 386 +((( 333 333 Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example, AT+CMDDL1=1000 to send the open time to 1000ms 388 +))) 334 334 335 - 390 +((( 336 336 After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**. 392 +))) 337 337 338 - 339 339 **Examples:** 340 340 341 341 Below are examples for the how above AT Commands works. 342 342 343 - 344 344 **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is: 345 345 400 +(% border="1" class="table-bordered" %) 346 346 |((( 347 347 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 348 348 ... ... @@ -355,9 +355,9 @@ 355 355 356 356 In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 357 357 358 - 359 359 **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 360 360 415 +(% border="1" class="table-bordered" %) 361 361 |((( 362 362 **AT+SEARCHx=aa,xx xx xx xx xx** 363 363 ... ... @@ -375,7 +375,7 @@ 375 375 376 376 The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49 377 377 378 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]433 +[[image:1652954654347-831.png]] 379 379 380 380 381 381 1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
- 1652954654347-831.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +138.7 KB - Content
- 1653266934636-343.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +176.5 KB - Content