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,203 +167,237 @@ 167 167 168 168 [[image:1652953414711-647.png||height="337" width="723"]] 169 169 170 - 170 +((( 171 171 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 +))) 172 172 173 - 174 +((( 174 174 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 +))) 175 175 178 +((( 176 176 **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL. 180 +))) 177 177 182 +((( 178 178 Each RS485-BL is shipped with a sticker with unique device EUI: 184 +))) 179 179 180 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]186 +[[image:1652953462722-299.png]] 181 181 182 - 183 - 184 - 188 +((( 185 185 User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot: 190 +))) 186 186 192 +((( 187 187 Add APP EUI in the application. 194 +))) 188 188 189 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]] 190 190 191 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]] 192 192 193 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]] 194 194 195 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]199 +[[image:image-20220519174512-1.png]] 196 196 201 +[[image:image-20220519174512-2.png||height="328" width="731"]] 197 197 203 +[[image:image-20220519174512-3.png||height="556" width="724"]] 198 198 205 +[[image:image-20220519174512-4.png]] 199 199 200 - 201 - 202 - 203 - 204 - 205 - 206 - 207 - 208 - 209 - 210 - 211 - 212 - 213 213 You can also choose to create the device manually. 214 214 215 -|((( 216 - 217 -))) 209 +[[image:1652953542269-423.png||height="710" width="723"]] 218 218 219 - 220 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]] 221 - 222 222 Add APP KEY and DEV EUI 223 223 224 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]213 +[[image:1652953553383-907.png||height="514" width="724"]] 225 225 226 226 216 +((( 227 227 **Step 2**: Power on RS485-BL and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel. 218 +))) 228 228 229 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]220 +[[image:1652953568895-172.png||height="232" width="724"]] 230 230 222 +== 3.3 Configure Commands to read data == 231 231 232 - 233 - 234 -1. 235 -11. Configure Commands to read data 236 - 224 +((( 237 237 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 +))) 238 238 228 +=== 3.3.1 onfigure UART settings for RS485 or TTL communication === 239 239 240 -1. 241 -11. 242 -111. Configure UART settings for RS485 or TTL communication 243 - 244 244 RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect. 245 245 246 -1. RS485-MODBUS mode: 232 +**~1. RS485-MODBUS mode:** 247 247 248 248 AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins. 249 249 236 +**2. TTL mode:** 250 250 251 -1. TTL mode: 252 - 253 253 AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins. 254 254 255 - 256 256 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. 257 257 258 - 259 -|**AT Commands**|**Description**|**Example** 260 -|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 +((( 261 261 AT+BAUDR=9600 257 +))) 262 262 259 +((( 263 263 Options: (1200,2400,4800,14400,19200,115200) 264 264 ))) 265 -|AT+PARITY|((( 262 +))) 263 +|((( 264 +AT+PARITY 265 +)))|(% style="width:285px" %)((( 266 +((( 266 266 Set UART parity (for RS485 connection) 268 +))) 267 267 270 +((( 268 268 Default Value is: no parity. 269 -)))|((( 272 +))) 273 +)))|(% style="width:347px" %)((( 274 +((( 270 270 AT+PARITY=0 276 +))) 271 271 278 +((( 272 272 Option: 0: no parity, 1: odd parity, 2: even parity 273 273 ))) 274 -|AT+STOPBIT|((( 281 +))) 282 +|((( 283 +AT+STOPBIT 284 +)))|(% style="width:285px" %)((( 285 +((( 275 275 Set serial stopbit (for RS485 connection) 287 +))) 276 276 289 +((( 277 277 Default Value is: 1bit. 278 -)))|((( 291 +))) 292 +)))|(% style="width:347px" %)((( 293 +((( 279 279 AT+STOPBIT=0 for 1bit 295 +))) 280 280 297 +((( 281 281 AT+STOPBIT=1 for 1.5 bit 299 +))) 282 282 301 +((( 283 283 AT+STOPBIT=2 for 2 bits 284 284 ))) 304 +))) 285 285 306 +=== 3.3.2 Configure sensors === 286 286 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 +))) 287 287 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 +))) 288 288 289 -1. 290 -11. 291 -111. Configure sensors 292 - 293 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV. 294 - 295 - 296 -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. 297 - 298 -|**AT Commands**|**Description**|**Example** 299 -|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" %)((( 300 300 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. 301 301 302 -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, 303 303 304 -m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 305 -)))|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 306 306 307 307 Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]]. 308 308 328 +=== 3.3.3 Configure read commands for each sampling === 309 309 310 - 311 - 312 - 313 -1. 314 -11. 315 -111. Configure read commands for each sampling 316 - 330 +((( 317 317 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 +))) 318 318 319 - 334 +((( 320 320 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 +))) 321 321 322 - 338 +((( 323 323 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 +))) 324 324 325 - 342 +((( 326 326 This section describes how to achieve above goals. 344 +))) 327 327 328 - 346 +((( 329 329 During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 348 +))) 330 330 331 - 350 +((( 332 332 **Command from RS485-BL to Sensor:** 352 +))) 333 333 354 +((( 334 334 RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar. 356 +))) 335 335 336 - 358 +((( 337 337 **Handle return from sensors to RS485-BL**: 360 +))) 338 338 362 +((( 339 339 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 +))) 340 340 366 +* ((( 367 +**AT+DATACUT** 368 +))) 341 341 342 -* **AT+DATACUT** 343 - 370 +((( 344 344 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 +))) 345 345 374 +* ((( 375 +**AT+SEARCH** 376 +))) 346 346 347 -* **AT+SEARCH** 348 - 378 +((( 349 349 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 +))) 350 350 351 - 382 +((( 352 352 **Define wait timeout:** 384 +))) 353 353 386 +((( 354 354 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 +))) 355 355 356 - 390 +((( 357 357 After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**. 392 +))) 358 358 359 - 360 360 **Examples:** 361 361 362 362 Below are examples for the how above AT Commands works. 363 363 364 - 365 365 **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is: 366 366 400 +(% border="1" class="table-bordered" %) 367 367 |((( 368 368 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 369 369 ... ... @@ -376,9 +376,9 @@ 376 376 377 377 In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 378 378 379 - 380 380 **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 381 381 415 +(% border="1" class="table-bordered" %) 382 382 |((( 383 383 **AT+SEARCHx=aa,xx xx xx xx xx** 384 384 ... ... @@ -396,7 +396,7 @@ 396 396 397 397 The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49 398 398 399 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]433 +[[image:1652954654347-831.png]] 400 400 401 401 402 402 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