Changes for page RS485-BL – Waterproof RS485 to LoRaWAN Converter
Last modified by Xiaoling on 2025/04/23 15:57
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 30 removed)
- 1652953542269-423.png
- 1652953553383-907.png
- 1652953568895-172.png
- 1652954654347-831.png
- 1653271044481-711.png
- 1653271276735-972.png
- 1653271581490-837.png
- 1653271648378-342.png
- 1653271657255-576.png
- 1653271763403-806.png
- 1653272787040-634.png
- 1653272817147-600.png
- 1653272901032-107.png
- 1653273818896-432.png
- 1653274001211-372.png
- 1654132684752-193.png
- 1654133913295-597.png
- 1654133954153-643.png
- 1654134704555-320.png
- 1654135840598-282.png
- 1654136105500-922.png
- 1654136435598-589.png
- 1654136646995-976.png
- image-20220519174512-1.png
- image-20220519174512-2.png
- image-20220519174512-3.png
- image-20220519174512-4.png
- image-20220602102605-1.png
- image-20220602102637-2.png
- image-20220602102715-3.png
Details
- Page properties
-
- Content
-
... ... @@ -7,15 +7,12 @@ 7 7 **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual** 8 8 9 9 10 - 11 11 **Table of Contents:** 12 12 13 -{{toc/}} 14 14 15 15 16 16 17 17 18 - 19 19 = 1.Introduction = 20 20 21 21 == 1.1 What is RS485-BL RS485 to LoRaWAN Converter == ... ... @@ -25,19 +25,19 @@ 25 25 ))) 26 26 27 27 ((( 28 -The Dragino RS485-BL is a (% style="color:blue" %)**RS485 / UART to LoRaWAN Converter**(%%)for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.25 +The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server. 29 29 ))) 30 30 31 31 ((( 32 -RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides (% style="color:blue" %)**a 3.3v output**(%%)and**(% style="color:blue" %)a 5v output(%%)** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.29 +RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption. 33 33 ))) 34 34 35 35 ((( 36 -RS485-BL is IP67 (% style="color:blue" %)**waterproof**(%%)and powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use for several years.33 +RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years. 37 37 ))) 38 38 39 39 ((( 40 -RS485-BL runs standard (% style="color:blue" %)**LoRaWAN 1.0.3 in Class A**(%%). It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.37 +RS485-BL runs standard **LoRaWAN 1.0.3 in Class A**. It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server. 41 41 ))) 42 42 43 43 ((( ... ... @@ -54,11 +54,8 @@ 54 54 55 55 [[image:1652953304999-717.png||height="424" width="733"]] 56 56 57 - 58 - 59 59 == 1.2 Specifications == 60 60 61 - 62 62 **Hardware System:** 63 63 64 64 * STM32L072CZT6 MCU ... ... @@ -65,6 +65,8 @@ 65 65 * SX1276/78 Wireless Chip 66 66 * Power Consumption (exclude RS485 device): 67 67 ** Idle: 6uA@3.3v 62 + 63 +* 68 68 ** 20dB Transmit: 130mA@3.3v 69 69 70 70 **Interface for Model:** ... ... @@ -118,57 +118,34 @@ 118 118 119 119 [[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]] 120 120 121 - 122 122 == 1.6 Hardware Change log == 123 123 124 124 ((( 125 - 126 - 127 -((( 128 128 v1.4 129 129 ))) 130 -))) 131 131 132 132 ((( 133 -((( 134 134 ~1. Change Power IC to TPS22916 135 135 ))) 136 -))) 137 137 138 -((( 139 - 140 -))) 141 141 142 142 ((( 143 -((( 144 144 v1.3 145 145 ))) 146 -))) 147 147 148 148 ((( 149 -((( 150 150 ~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire 151 151 ))) 152 -))) 153 153 154 -((( 155 - 156 -))) 157 157 158 158 ((( 159 -((( 160 160 v1.2 161 161 ))) 162 -))) 163 163 164 164 ((( 165 -((( 166 166 Release version 167 167 ))) 168 168 169 - 170 -))) 171 - 172 172 = 2. Pin mapping and Power ON Device = 173 173 174 174 ((( ... ... @@ -180,7 +180,6 @@ 180 180 181 181 The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper. 182 182 183 - 184 184 = 3. Operation Mode = 185 185 186 186 == 3.1 How it works? == ... ... @@ -187,8 +187,6 @@ 187 187 188 188 ((( 189 189 The RS485-BL is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-BL. It will auto join the network via OTAA. 190 - 191 - 192 192 ))) 193 193 194 194 == 3.2 Example to join LoRaWAN network == ... ... @@ -197,289 +197,204 @@ 197 197 198 198 [[image:1652953414711-647.png||height="337" width="723"]] 199 199 200 - (((170 + 201 201 The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. 202 -))) 203 203 204 - (((173 + 205 205 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: 206 -))) 207 207 208 -((( 209 209 **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL. 210 -))) 211 211 212 -((( 213 213 Each RS485-BL is shipped with a sticker with unique device EUI: 214 -))) 215 215 216 -[[image: 1652953462722-299.png]]180 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]] 217 217 218 -((( 182 + 183 + 184 + 219 219 User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot: 220 -))) 221 221 222 -((( 223 223 Add APP EUI in the application. 224 -))) 225 225 189 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]] 226 226 227 -[[image:image -20220519174512-1.png]]191 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]] 228 228 229 -[[image:i mage-20220519174512-2.png||height="328" width="731"]]193 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]] 230 230 231 -[[image:image -20220519174512-3.png||height="556" width="724"]]195 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]] 232 232 233 -[[image:image-20220519174512-4.png]] 234 234 198 + 199 + 200 + 201 + 202 + 203 + 204 + 205 + 206 + 207 + 208 + 209 + 210 + 211 + 212 + 235 235 You can also choose to create the device manually. 236 236 237 -[[image:1652953542269-423.png||height="710" width="723"]] 215 +|((( 216 + 217 +))) 238 238 219 + 220 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]] 221 + 239 239 Add APP KEY and DEV EUI 240 240 241 -[[image: 1652953553383-907.png||height="514" width="724"]]224 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]] 242 242 243 243 244 -((( 245 245 **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. 246 -))) 247 247 248 -[[image: 1652953568895-172.png||height="232" width="724"]]229 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]] 249 249 250 250 251 -== 3.3 Configure Commands to read data == 252 252 253 -((( 254 -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>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors. 255 255 256 - 257 - )))234 +1. 235 +11. Configure Commands to read data 258 258 259 - ===3.3.1onfigureUART settings for RS485 orTTLcommunication===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. 260 260 261 -((( 239 + 240 +1. 241 +11. 242 +111. Configure UART settings for RS485 or TTL communication 243 + 262 262 RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect. 263 -))) 264 264 265 -((( 266 -**~1. RS485-MODBUS mode:** 267 -))) 246 +1. RS485-MODBUS mode: 268 268 269 -((( 270 270 AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins. 271 -))) 272 272 273 -((( 274 -**2. TTL mode:** 275 -))) 276 276 277 -((( 251 +1. TTL mode: 252 + 278 278 AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins. 279 -))) 280 280 281 - (((255 + 282 282 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. 283 -))) 284 284 285 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 286 -|=(% style="width: 120px;" %)((( 287 -((( 288 -**AT Commands** 289 -))) 290 -)))|=(% style="width: 190px;" %)((( 291 -((( 292 -**Description** 293 -))) 294 -)))|=(% style="width: 190px;" %)((( 295 -((( 296 -**Example** 297 -))) 298 -))) 299 -|(% style="width:120px" %)((( 300 -((( 301 -AT+BAUDR 302 -))) 303 -)))|(% style="width:190px" %)((( 304 -((( 305 -Set the baud rate (for RS485 connection). Default Value is: 9600. 306 -))) 307 -)))|(% style="width:190px" %)((( 308 -((( 309 -((( 258 + 259 +|**AT Commands**|**Description**|**Example** 260 +|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|((( 310 310 AT+BAUDR=9600 311 -))) 312 -))) 313 313 314 -((( 315 -((( 316 316 Options: (1200,2400,4800,14400,19200,115200) 317 317 ))) 318 -))) 319 -))) 320 -|(% style="width:120px" %)((( 321 -((( 322 -AT+PARITY 323 -))) 324 -)))|(% style="width:190px" %)((( 325 -((( 326 -((( 265 +|AT+PARITY|((( 327 327 Set UART parity (for RS485 connection) 328 -))) 329 -))) 330 330 331 -((( 332 -((( 333 333 Default Value is: no parity. 334 -))) 335 -))) 336 -)))|(% style="width:190px" %)((( 337 -((( 338 -((( 269 +)))|((( 339 339 AT+PARITY=0 340 -))) 341 -))) 342 342 343 -((( 344 -((( 345 345 Option: 0: no parity, 1: odd parity, 2: even parity 346 346 ))) 347 -))) 348 -))) 349 -|(% style="width:120px" %)((( 350 -((( 351 -AT+STOPBIT 352 -))) 353 -)))|(% style="width:190px" %)((( 354 -((( 355 -((( 274 +|AT+STOPBIT|((( 356 356 Set serial stopbit (for RS485 connection) 357 -))) 358 -))) 359 359 360 -((( 361 -((( 362 362 Default Value is: 1bit. 363 -))) 364 -))) 365 -)))|(% style="width:190px" %)((( 366 -((( 367 -((( 278 +)))|((( 368 368 AT+STOPBIT=0 for 1bit 369 -))) 370 -))) 371 371 372 -((( 373 -((( 374 374 AT+STOPBIT=1 for 1.5 bit 375 -))) 376 -))) 377 377 378 -((( 379 -((( 380 380 AT+STOPBIT=2 for 2 bits 381 381 ))) 382 -))) 383 -))) 384 384 385 -=== 3.3.2 Configure sensors === 386 386 387 -((( 388 -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**. 389 -))) 390 390 391 -((( 392 -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. 393 -))) 394 394 395 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 396 -|=(% style="width: 120px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example** 397 -|AT+CFGDEV|(% style="width:120px" %)((( 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|((( 398 398 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. 399 399 400 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx, 302 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 401 401 402 -m m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command403 -)))| (% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m304 +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 404 404 405 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>> ||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].307 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]]. 406 406 407 407 408 408 409 -=== 3.3.3 Configure read commands for each sampling === 410 410 411 -((( 312 + 313 +1. 314 +11. 315 +111. Configure read commands for each sampling 316 + 412 412 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. 413 -))) 414 414 415 - (((319 + 416 416 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. 417 -))) 418 418 419 - (((322 + 420 420 To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload. 421 -))) 422 422 423 - (((325 + 424 424 This section describes how to achieve above goals. 425 -))) 426 426 427 - (((328 + 428 428 During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 429 -))) 430 430 431 - (((331 + 432 432 **Command from RS485-BL to Sensor:** 433 -))) 434 434 435 -((( 436 436 RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar. 437 -))) 438 438 439 - (((336 + 440 440 **Handle return from sensors to RS485-BL**: 441 -))) 442 442 443 -((( 444 444 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** 445 -))) 446 446 447 -* ((( 448 -**AT+DATACUT** 449 -))) 450 450 451 -((( 342 +* **AT+DATACUT** 343 + 452 452 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. 453 -))) 454 454 455 -* ((( 456 -**AT+SEARCH** 457 -))) 458 458 459 -((( 347 +* **AT+SEARCH** 348 + 460 460 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. 461 -))) 462 462 463 - (((351 + 464 464 **Define wait timeout:** 465 -))) 466 466 467 -((( 468 468 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 469 -))) 470 470 471 - (((356 + 472 472 After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**. 473 -))) 474 474 359 + 475 475 **Examples:** 476 476 477 477 Below are examples for the how above AT Commands works. 478 478 364 + 479 479 **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is: 480 480 481 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:500px" %) 482 -|(% style="width:498px" %)((( 367 +|((( 483 483 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 484 484 485 485 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent** ... ... @@ -491,38 +491,41 @@ 491 491 492 492 In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 493 493 379 + 494 494 **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 495 495 496 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:500px" %) 497 -|(% style="width:577px" %)((( 382 +|((( 498 498 **AT+SEARCHx=aa,xx xx xx xx xx** 499 499 500 500 * **aa: 1: prefix match mode; 2: prefix and suffix match mode** 501 501 * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix** 387 + 388 + 502 502 ))) 503 503 504 - **Examples:**391 +Examples: 505 505 506 -1 )For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49393 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 507 507 508 508 If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 509 509 510 -The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)**2e 30 58 5f 36 41 30 31 00 49**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 511 511 512 -[[image: 1653271044481-711.png]]399 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]] 513 513 514 -2)For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 515 515 402 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 403 + 516 516 If we set AT+SEARCH1=2, 1E 56 34+31 00 49 517 517 518 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is (%style="background-color:yellow" %) **2e 30 58 5f 36 41 30**406 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30 519 519 520 -[[image: 1653271276735-972.png]]408 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]] 521 521 410 + 522 522 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 523 523 524 -(% style="background-color:#4f81bd; color:white; width:510px" %) 525 -|(% style="width:726px" %)((( 413 +|((( 526 526 **AT+DATACUTx=a,b,c** 527 527 528 528 * **a: length for the return of AT+COMMAND** ... ... @@ -530,147 +530,98 @@ 530 530 * **c: define the position for valid value. ** 531 531 ))) 532 532 533 - **Examples:**421 +Examples: 534 534 535 535 * Grab bytes: 536 536 537 -[[image: 1653271581490-837.png||height="313" width="722"]]425 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]] 538 538 539 - 540 540 * Grab a section. 541 541 542 -[[image: 1653271648378-342.png||height="326" width="720"]]429 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]] 543 543 544 - 545 545 * Grab different sections. 546 546 547 -[[image: 1653271657255-576.png||height="305" width="730"]]433 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]] 548 548 549 -((( 550 -(% style="color:red" %)**Note:** 551 -))) 552 552 553 -((( 436 +Note: 437 + 554 554 AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0. 555 -))) 556 556 557 -((( 558 -**Example:** 559 -))) 440 +Example: 560 560 561 -((( 562 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 563 -))) 442 +AT+COMMAND1=11 01 1E D0,0 564 564 565 -((( 566 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34 567 -))) 444 +AT+SEARCH1=1,1E 56 34 568 568 569 -((( 570 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5 571 -))) 446 +AT+DATACUT1=0,2,1~~5 572 572 573 -((( 574 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 575 -))) 448 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 576 576 577 -((( 578 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 579 -))) 450 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 580 580 581 -((( 582 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 583 -))) 452 +Valid payload after DataCUT command: 2e 30 58 5f 36 584 584 585 -[[image: 1653271763403-806.png]]454 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 586 586 587 587 588 -=== 3.3.4 Compose the uplink payload === 589 589 590 -((( 591 -Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.** 592 592 593 - 594 -))) 459 +1. 460 +11. 461 +111. Compose the uplink payload 595 595 596 -((( 597 -(% style="color:#037691" %)**Examples: AT+DATAUP=0** 463 +Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.** 598 598 599 - 600 -))) 601 601 602 -((( 603 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**. 604 -))) 466 +**Examples: AT+DATAUP=0** 605 605 606 -((( 468 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**. 469 + 607 607 Final Payload is 608 -))) 609 609 610 -((( 611 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx** 612 -))) 472 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 613 613 614 -((( 615 615 Where PAYVER is defined by AT+PAYVER, below is an example screen shot. 616 -))) 617 617 618 -[[image: 1653272787040-634.png||height="515" width="719"]]476 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 619 619 620 620 621 621 622 -((( 623 -(% style="color:#037691" %)**Examples: AT+DATAUP=1** 480 +**Examples: AT+DATAUP=1** 624 624 625 - 626 -))) 482 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 627 627 628 -((( 629 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 630 -))) 631 - 632 -((( 633 633 Final Payload is 634 -))) 635 635 636 -((( 637 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 638 -))) 486 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 639 639 640 -1. ((( 641 -Battery Info (2 bytes): Battery voltage 642 -))) 643 -1. ((( 644 -PAYVER (1 byte): Defined by AT+PAYVER 645 -))) 646 -1. ((( 647 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 648 -))) 649 -1. ((( 650 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 651 -))) 652 -1. ((( 653 -DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes 654 -))) 488 +1. Battery Info (2 bytes): Battery voltage 489 +1. PAYVER (1 byte): Defined by AT+PAYVER 490 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 491 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 492 +1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes 655 655 656 -[[image: 1653272817147-600.png||height="437" width="717"]]494 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 657 657 496 + 658 658 So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 659 659 499 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41 660 660 661 -DATA 1=RETURN1 ValidValue= (% style="background-color:#4f81bd;color:white"%)20200a33 9041501 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20 662 662 663 -DATA 2=1^^st^^ ~~6^^th^^ byte of Valid value of RETURN10=(% style="background-color:#4f81bd;color:white" %)02aa05810a20503 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30 664 664 665 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30 666 666 667 667 668 668 Below are the uplink payloads: 669 669 670 -[[image: 1653272901032-107.png]]509 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]] 671 671 672 672 673 - (% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:512 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 674 674 675 675 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date) 676 676 ... ... @@ -682,185 +682,139 @@ 682 682 683 683 684 684 685 -=== 3.3.5 Uplink on demand === 524 +1. 525 +11. 526 +111. Uplink on demand 686 686 687 -((( 688 688 Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command. 689 -))) 690 690 691 -((( 692 692 Downlink control command: 693 -))) 694 694 695 -((( 696 -**0x08 command**: Poll an uplink with current command set in RS485-BL. 697 -))) 532 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL. 698 698 699 -((( 700 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors. 534 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors. 701 701 702 - 703 -))) 704 704 705 -=== 3.3.6 Uplink on Interrupt === 706 706 707 -Put the interrupt sensor between 3.3v_out and GPIO ext. 538 +1. 539 +11. 540 +111. Uplink on Interrupt 708 708 709 -[[image: 1653273818896-432.png]]542 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]] 710 710 711 - 712 -((( 713 713 AT+INTMOD=0 Disable Interrupt 714 -))) 715 715 716 -((( 717 717 AT+INTMOD=1 Interrupt trigger by rising or falling edge. 718 -))) 719 719 720 -((( 721 721 AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 722 -))) 723 723 724 -((( 725 725 AT+INTMOD=3 Interrupt trigger by rising edge. 726 726 727 - 728 -))) 729 729 730 -== 3.4 Uplink Payload == 553 +1. 554 +11. Uplink Payload 731 731 732 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %) 733 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands** 734 -|Value|(% style="width:130px" %)((( 735 -((( 556 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 557 +|Value|((( 736 736 Battery(mV) 737 -))) 738 738 739 -((( 740 740 & 741 -))) 742 742 743 -((( 744 744 Interrupt _Flag 745 -))) 746 -)))|(% style="width:93px" %)((( 563 +)))|((( 747 747 PAYLOAD_VER 748 748 749 749 750 -)))| (% style="width:509px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.567 +)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server. 751 751 752 752 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 753 753 754 -((( 755 -{{{function Decoder(bytes, port) {}}} 756 -))) 757 757 758 -((( 759 -{{{//Payload Formats of RS485-BL Deceive}}} 760 -))) 572 +function Decoder(bytes, port) { 761 761 762 -((( 763 -{{{return {}}} 764 -))) 574 +~/~/Payload Formats of RS485-BL Deceive 765 765 766 -((( 767 -{{{ //Battery,units:V}}} 768 -))) 576 +return { 769 769 770 -((( 771 -{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}} 772 -))) 578 + ~/~/Battery,units:V 773 773 774 -((( 775 -{{{ //GPIO_EXTI }}} 776 -))) 580 + BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 777 777 778 -((( 779 -{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}} 780 -))) 582 + ~/~/GPIO_EXTI 781 781 782 -((( 783 -{{{ //payload of version}}} 784 -))) 584 + EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 785 785 786 -((( 787 -{{{ Pay_ver:bytes[2],}}} 788 -))) 586 + ~/~/payload of version 789 789 790 -((( 791 -{{{ }; }}} 792 -))) 588 + Pay_ver:bytes[2], 793 793 794 -((( 795 -**}** 590 + }; 796 796 797 - 798 -))) 592 + } 799 799 800 -((( 801 -TTN V3 uplink screen shot. 802 -))) 803 803 804 -[[image:1653274001211-372.png||height="192" width="732"]] 805 805 806 806 807 -== 3.5 Configure RS485-BL via AT or Downlink == 808 808 809 -User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands 810 810 811 -There are two kinds of Commands: 812 812 813 - * (% style="color:#4f81bd" %)**Common Commands**(%%):Theyshouldbe available for each sensor, such as: change uplinkinterval, reset device. Forfirmwarev1.3, user canfind what common commands itsupports: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]600 +TTN V3 uplink screen shot. 814 814 815 - * (% style="color:#4f81bd" %)**Sensor RelatedCommands**(%%):Thesecommands arespecialdesigned for RS485-BL. User can see thesecommands below:602 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 816 816 817 -=== 3.5.1 Common Commands: === 604 +1. 605 +11. Configure RS485-BL via AT or Downlink 818 818 819 - Theyshould beavailable foreach of DraginoSensors, such as: changeuplink interval, resetdevice.For firmwarev1.3, user can find whatcommon commands it supports:[[End DeviceAT Commandsand Downlink Command>>doc:Main.End DeviceATCommandsandDownlink Command.WebHome]]607 +User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands 820 820 609 +There are two kinds of Commands: 821 821 822 - ===3.5.2Sensor related commands: ===611 +* **Common Commands**: They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: http:~/~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands 823 823 613 +* **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 824 824 825 -==== **Choose Device Type (RS485 or TTL)** ==== 615 +1. 616 +11. 617 +111. Common Commands: 826 826 619 +They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]] 620 + 621 + 622 +1. 623 +11. 624 +111. Sensor related commands: 625 + 626 +==== Choose Device Type (RS485 or TTL) ==== 627 + 827 827 RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect. 828 828 829 -* **AT Command**630 +* AT Command 830 830 831 -(% class="box infomessage" %) 832 -((( 833 833 **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins. 834 -))) 835 835 836 -(% class="box infomessage" %) 837 -((( 838 838 **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins. 839 -))) 840 840 841 841 842 -* **Downlink Payload**637 +* Downlink Payload 843 843 844 -**0A aa** ~-~->same as AT+MOD=aa639 +**0A aa** à same as AT+MOD=aa 845 845 846 846 847 847 848 -==== **RS485 Debug Command (AT+CFGDEV)**====643 +==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ==== 849 849 850 850 This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling. 851 851 852 -* **AT Command**647 +* AT Command 853 853 854 -(% class="box infomessage" %) 855 -((( 856 -**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m** 857 -))) 649 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 858 858 859 859 m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command. 860 860 861 861 862 -* **Downlink Payload** 863 863 655 +* Downlink Payload 656 + 864 864 Format: A8 MM NN XX XX XX XX YY 865 865 866 866 Where: ... ... @@ -874,15 +874,15 @@ 874 874 875 875 To connect a Modbus Alarm with below commands. 876 876 877 -* The command to active alarm is: 0A 05 00 04 00 01 **4C B0**. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.670 +* The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually. 878 878 879 -* The command to deactivate alarm is: 0A 05 00 04 00 00 **8D 70**. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.672 +* The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually. 880 880 881 881 So if user want to use downlink command to control to RS485 Alarm, he can use: 882 882 883 - (% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm676 +**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm 884 884 885 - (% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm678 +**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm 886 886 887 887 A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output. 888 888 ... ... @@ -891,61 +891,48 @@ 891 891 892 892 Check TTL Sensor return: 893 893 894 -[[image: 1654132684752-193.png]]687 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]] 895 895 896 896 897 897 898 898 899 -==== **Set Payload version**====692 +==== Set Payload version ==== 900 900 901 901 This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload. 902 902 903 -* **AT Command:**696 +* AT Command: 904 904 905 -(% class="box infomessage" %) 906 -((( 907 -**AT+PAYVER: Set PAYVER field = 1** 908 -))) 698 +AT+PAYVER: Set PAYVER field = 1 909 909 910 910 911 -* **Downlink Payload:**701 +* Downlink Payload: 912 912 913 - **0xAE 01**~-~->Set PAYVER field = 0x01703 +0xAE 01 à Set PAYVER field = 0x01 914 914 915 - **0xAE 0F**~-~->Set PAYVER field = 0x0F705 +0xAE 0F à Set PAYVER field = 0x0F 916 916 917 917 708 +==== Set RS485 Sampling Commands ==== 918 918 919 -==== **Set RS485 Sampling Commands** ==== 920 - 921 921 AT+COMMANDx, AT+DATACUTx and AT+SEARCHx 922 922 923 -These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>> ||anchor="H3.3.3Configurereadcommandsforeachsampling"]].712 +These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]]. 924 924 925 925 926 -* **AT Command:**715 +* AT Command: 927 927 928 -(% class="box infomessage" %) 929 -((( 930 -**AT+COMMANDx: Configure RS485 read command to sensor.** 931 -))) 717 +AT+COMMANDx: Configure RS485 read command to sensor. 932 932 933 -(% class="box infomessage" %) 934 -((( 935 -**AT+DATACUTx: Configure how to handle return from RS485 devices.** 936 -))) 719 +AT+DATACUTx: Configure how to handle return from RS485 devices. 937 937 938 -(% class="box infomessage" %) 939 -((( 940 -**AT+SEARCHx: Configure search command** 941 -))) 721 +AT+SEARCHx: Configure search command 942 942 943 943 944 -* **Downlink Payload:**724 +* Downlink Payload: 945 945 946 - **0xAF**downlink command can be used to set AT+COMMANDx or AT+DATACUTx.726 +0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx. 947 947 948 - (% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.728 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink. 949 949 950 950 Format: AF MM NN LL XX XX XX XX YY 951 951 ... ... @@ -952,23 +952,23 @@ 952 952 Where: 953 953 954 954 * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F, 955 -* NN: 956 -* LL: 735 +* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value. 736 +* LL: The length of AT+COMMAND or AT+DATACUT command 957 957 * XX XX XX XX: AT+COMMAND or AT+DATACUT command 958 -* YY: 738 +* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command. 959 959 960 - **Example:**740 +Example: 961 961 962 - (% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1742 +**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1 963 963 964 - (% style="color:#037691" %)**AF 03 02 06**(%style="color:orange" %)**10**(% style="color:red" %)**01**(% style="color:green" %)**05 06 09 0A**(%style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**744 +**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10** 965 965 966 - (% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)**0B**(%style="color:red" %)**02**(% style="color:green" %)**05 07 08 0A**(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**746 +**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10** 967 967 968 968 969 - **0xAB**downlink command can be used for set AT+SEARCHx749 +0xAB downlink command can be used for set AT+SEARCHx 970 970 971 - **Example:****AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So751 +Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So 972 972 973 973 * AB aa 01 03 xx xx xx same as AT+SEARCHaa=1,xx xx xx 974 974 * AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands ... ... @@ -976,166 +976,145 @@ 976 976 **AB aa 02 03 xx xx xx 02 yy yy** same as **AT+SEARCHaa=2,xx xx xx+yy yy** 977 977 978 978 759 +==== Fast command to handle MODBUS device ==== 979 979 980 -==== **Fast command to handle MODBUS device** ==== 981 - 982 982 AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]]. 983 983 984 984 This command is valid since v1.3 firmware version 985 985 986 986 987 - **AT+MBFUN has only two value:**766 +AT+MBFUN has only two value: 988 988 989 -* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return768 +* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return 990 990 991 991 AT+MBFUN=1, device can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore. 992 992 993 -* **AT+MBFUN=0**: Disable Modbus fast reading.772 +* AT+MBFUN=0: Disable Modbus fast reading. 994 994 995 - **Example:**774 +Example: 996 996 997 997 * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). 998 998 * AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08. 999 999 * AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10. 1000 1000 1001 -[[image: 1654133913295-597.png]]780 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]] 1002 1002 1003 1003 1004 -[[image: 1654133954153-643.png]]783 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]] 1005 1005 1006 1006 1007 -* **Downlink Commands:**786 +* Downlink Commands: 1008 1008 1009 - **A9 aa**~-~->Same as AT+MBFUN=aa788 +A9 aa -à Same as AT+MBFUN=aa 1010 1010 1011 1011 791 +==== RS485 command timeout ==== 1012 1012 1013 -==== **RS485 command timeout** ==== 1014 - 1015 1015 Some Modbus device has slow action to send replies. This command is used to configure the RS485-BL to use longer time to wait for their action. 1016 1016 1017 1017 Default value: 0, range: 0 ~~ 5 seconds 1018 1018 1019 1019 1020 -* **AT Command:**798 +* AT Command: 1021 1021 1022 -(% class="box infomessage" %) 1023 -((( 1024 -**AT+CMDDLaa=hex(bb cc)** 1025 -))) 800 +AT+CMDDLaa=hex(bb cc) 1026 1026 1027 - **Example:**802 +Example: 1028 1028 1029 1029 **AT+CMDDL1=1000** to send the open time to 1000ms 1030 1030 1031 1031 1032 -* **Downlink Payload:**807 +* Downlink Payload: 1033 1033 1034 1034 0x AA aa bb cc 1035 1035 1036 1036 Same as: AT+CMDDLaa=hex(bb cc) 1037 1037 1038 - **Example:**813 + Example: 1039 1039 1040 - **0xAA 01 03 E8**~-~->Same as **AT+CMDDL1=1000 ms**815 + 0xAA 01 03 E8 à Same as **AT+CMDDL1=1000 ms** 1041 1041 1042 1042 818 +==== [[Uplink>>path:#downlink_A8]] payload mode ==== 1043 1043 1044 -==== **Uplink payload mode** ==== 1045 - 1046 1046 Define to use one uplink or multiple uplinks for the sampling. 1047 1047 1048 -The use of this command please see: [[Compose Uplink payload>> ||anchor="H3.3.4Composetheuplinkpayload"]]822 +The use of this command please see: [[Compose Uplink payload>>path:#DataUP]] 1049 1049 1050 -* **AT Command:**824 +* AT Command: 1051 1051 1052 -(% class="box infomessage" %) 1053 -((( 1054 -**AT+DATAUP=0** 1055 -))) 826 +AT+DATAUP=0 1056 1056 1057 -(% class="box infomessage" %) 1058 -((( 1059 -**AT+DATAUP=1** 1060 -))) 828 +AT+DATAUP=1 1061 1061 1062 1062 1063 -* **Downlink Payload:**831 +* Downlink Payload: 1064 1064 1065 - **0xAD 00****~-~->**Same as AT+DATAUP=0833 +0xAD 00 à Same as AT+DATAUP=0 1066 1066 1067 - **0xAD 01****~-~->**Same as AT+DATAUP=1835 +0xAD 01 à Same as AT+DATAUP=1 1068 1068 1069 1069 838 +==== Manually trigger an Uplink ==== 1070 1070 1071 - 1072 -==== **Manually trigger an Uplink** ==== 1073 - 1074 1074 Ask device to send an uplink immediately. 1075 1075 1076 -* **Downlink Payload:**842 +* Downlink Payload: 1077 1077 1078 - **0x08 FF**, RS485-BL will immediately send an uplink.844 +0x08 FF, RS485-BL will immediately send an uplink. 1079 1079 1080 1080 847 +==== Clear RS485 Command ==== 1081 1081 1082 - 1083 -==== **Clear RS485 Command** ==== 1084 - 1085 1085 The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them. 1086 1086 1087 1087 1088 -* **AT Command:**852 +* AT Command: 1089 1089 1090 - (% style="color:#037691" %)**AT+CMDEAR=mm,nn**(%%)mm: start position of erase ,nn: stop position of eraseEtc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10854 +**AT+CMDEAR=mm,nn** mm: start position of erase ,nn: stop position of erase 1091 1091 856 +Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10 857 + 1092 1092 Example screen shot after clear all RS485 commands. 1093 1093 1094 1094 861 + 1095 1095 The uplink screen shot is: 1096 1096 1097 -[[image: 1654134704555-320.png]]864 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 1098 1098 1099 1099 1100 -* **Downlink Payload:**867 +* Downlink Payload: 1101 1101 1102 - **0x09 aa bb**same as AT+CMDEAR=aa,bb869 +0x09 aa bb same as AT+CMDEAR=aa,bb 1103 1103 1104 1104 872 +==== Set Serial Communication Parameters ==== 1105 1105 1106 -==== **Set Serial Communication Parameters** ==== 1107 - 1108 1108 Set the Rs485 serial communication parameters: 1109 1109 1110 -* **AT Command:**876 +* AT Command: 1111 1111 1112 1112 Set Baud Rate: 1113 1113 1114 -(% class="box infomessage" %) 1115 -((( 1116 -**AT+BAUDR=9600** ~/~/ Options: (1200,2400,4800,14400,19200,115200) 1117 -))) 880 +AT+BAUDR=9600 ~/~/ Options: (1200,2400,4800,14400,19200,115200) 1118 1118 1119 -Set UART Parity 1120 1120 1121 -(% class="box infomessage" %) 1122 -((( 1123 -**AT+PARITY=0** ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 1124 -))) 883 +Set UART parity 1125 1125 885 +AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 886 + 887 + 1126 1126 Set STOPBIT 1127 1127 1128 -(% class="box infomessage" %) 1129 -((( 1130 -**AT+STOPBIT=0** ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 1131 -))) 890 +AT+STOPBIT=0 ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 1132 1132 1133 1133 1134 -* **Downlink Payload:**893 +* Downlink Payload: 1135 1135 1136 - **A7 01 aa bb**: Same AT+BAUDR=hex(aa bb)*100895 +A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100 1137 1137 1138 - **Example:**897 +Example: 1139 1139 1140 1140 * A7 01 00 60 same as AT+BAUDR=9600 1141 1141 * A7 01 04 80 same as AT+BAUDR=115200 ... ... @@ -1145,189 +1145,180 @@ 1145 1145 A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02) 1146 1146 1147 1147 907 +==== Control output power duration ==== 1148 1148 1149 -==== **Control output power duration** ==== 1150 - 1151 1151 User can set the output power duration before each sampling. 1152 1152 1153 -* **AT Command:**911 +* AT Command: 1154 1154 1155 - **Example:**913 +Example: 1156 1156 1157 - **AT+3V3T=1000**~/~/ 3V3 output power will open 1s before each sampling.915 +AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling. 1158 1158 1159 - **AT+5VT=1000**~/~/ +5V output power will open 1s before each sampling.917 +AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling. 1160 1160 1161 1161 1162 -* **LoRaWAN Downlink Command:**920 +* LoRaWAN Downlink Command: 1163 1163 1164 - **07 01 aa bb**Same as AT+5VT=(aa bb)922 +07 01 aa bb Same as AT+5VT=(aa bb) 1165 1165 1166 - **07 02 aa bb**Same as AT+3V3T=(aa bb)924 +07 02 aa bb Same as AT+3V3T=(aa bb) 1167 1167 1168 1168 1169 1169 1170 -== 3.6 Buttons == 1171 1171 1172 -(% border="1" style="background-color:#ffffcc; color:green; width:233px" %) 1173 -|=(% style="width: 89px;" %)**Button**|=(% style="width: 141px;" %)**Feature** 1174 -|(% style="width:89px" %)**RST**|(% style="width:141px" %)Reboot RS485-BL 929 +1. 930 +11. Buttons 1175 1175 1176 -== 3.7 +3V3 Output == 932 +|**Button**|**Feature** 933 +|**RST**|Reboot RS485-BL 1177 1177 935 +1. 936 +11. +3V3 Output 937 + 1178 1178 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. 1179 1179 1180 1180 The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling. 1181 1181 942 + 1182 1182 The +3V3 output time can be controlled by AT Command. 1183 1183 945 +**AT+3V3T=1000** 1184 1184 1185 -(% style="color:#037691" %)**AT+3V3T=1000** 1186 - 1187 - 1188 1188 Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors. 1189 1189 949 + 1190 1190 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 1191 1191 1192 1192 1193 -== 3.8 +5V Output == 953 +1. 954 +11. +5V Output 1194 1194 1195 1195 RS485-BL has a Controllable +5V output, user can use this output to power external sensor. 1196 1196 1197 1197 The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling. 1198 1198 960 + 1199 1199 The 5V output time can be controlled by AT Command. 1200 1200 963 +**AT+5VT=1000** 1201 1201 1202 -(% style="color:#037691" %)**AT+5VT=1000** 1203 - 1204 - 1205 1205 Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors. 1206 1206 967 + 1207 1207 By default, the AT+5VT=0. If the external sensor which require 5v and require more time to get stable state, user can use this command to increase the power ON duration for this sensor. 1208 1208 1209 1209 1210 -== 3.9 LEDs == 1211 1211 1212 -(% border="1" style="background-color:#ffffcc; color:green; width:332px" %) 1213 -|=**LEDs**|=(% style="width: 274px;" %)**Feature** 1214 -|**LED1**|(% style="width:274px" %)Blink when device transmit a packet. 1215 1215 1216 -== 3.10 Switch Jumper == 973 +1. 974 +11. LEDs 1217 1217 1218 -(% border="1" style="background-color:#ffffcc; color:green; width:515px" %) 1219 -|=(% style="width: 124px;" %)**Switch Jumper**|=(% style="width: 388px;" %)**Feature** 1220 -|(% style="width:124px" %)**SW1**|(% style="width:388px" %)((( 976 +|**LEDs**|**Feature** 977 +|**LED1**|Blink when device transmit a packet. 978 + 979 +1. 980 +11. Switch Jumper 981 + 982 +|**Switch Jumper**|**Feature** 983 +|**SW1**|((( 1221 1221 ISP position: Upgrade firmware via UART 1222 1222 1223 1223 Flash position: Configure device, check running status. 1224 1224 ))) 1225 -| (% style="width:124px" %)**SW2**|(% style="width:388px" %)(((988 +|**SW2**|((( 1226 1226 5V position: set to compatible with 5v I/O. 1227 1227 1228 1228 3.3v position: set to compatible with 3.3v I/O., 1229 1229 ))) 1230 1230 1231 - **+3.3V**: is always ON994 ++3.3V: is always ON 1232 1232 1233 - **+5V**: Only open before every sampling. The time is by default, it is AT+5VT=0. Max open time. 5000 ms.996 ++5V: Only open before every sampling. The time is by default, it is AT+5VT=0. Max open time. 5000 ms. 1234 1234 998 +1. Case Study 1235 1235 1236 - =4.CaseStudy =1000 +User can check this URL for some case studies. 1237 1237 1238 - User can checkthis URL forsomecase studies: [[APPdoc:Main.ApplicationNote \: CommunicatewithDifferentSensors -----RS485-LNRS485-BL.WebHome]]1002 +[[http:~~/~~/wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS>>url:http://wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS]] 1239 1239 1240 1240 1241 -= 5. Use AT Command = 1242 1242 1243 -== 5.1 Access AT Command == 1244 1244 1007 +1. Use AT Command 1008 +11. Access AT Command 1009 + 1245 1245 RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below. 1246 1246 1247 -[[image: 1654135840598-282.png]]1012 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]] 1248 1248 1249 1249 1250 -In PC, User needs to set (% style="color:blue" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to(% style="color:green" %)**9600**(%%)to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:1015 +In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to **9600** to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference: 1251 1251 1252 -[[image: 1654136105500-922.png]]1017 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]] 1253 1253 1254 1254 1255 -More detail AT Command manual can be found at [[AT Command Manual>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] 1256 1256 1021 +More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]] 1257 1257 1258 -== 5.2 Common AT Command Sequence == 1259 1259 1260 -=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) === 1261 1261 1025 +1. 1026 +11. Common AT Command Sequence 1027 +111. Multi-channel ABP mode (Use with SX1301/LG308) 1028 + 1262 1262 If device has not joined network yet: 1263 1263 1264 -(% class="box infomessage" %) 1265 -((( 1266 -**AT+FDR** 1267 -))) 1031 +AT+FDR 1268 1268 1269 -(% class="box infomessage" %) 1270 -((( 1271 -**AT+NJM=0** 1272 -))) 1033 +AT+NJM=0 1273 1273 1274 -(% class="box infomessage" %) 1275 -((( 1276 -**ATZ** 1277 -))) 1035 +ATZ 1278 1278 1279 1279 1280 1280 If device already joined network: 1281 1281 1282 -(% class="box infomessage" %) 1283 -((( 1284 -**AT+NJM=0** 1285 -))) 1040 +AT+NJM=0 1286 1286 1287 -(% class="box infomessage" %) 1288 -((( 1289 -**ATZ** 1290 -))) 1042 +ATZ 1291 1291 1044 +1. 1045 +11. 1046 +111. Single-channel ABP mode (Use with LG01/LG02) 1292 1292 1293 - ===5.5.2 Single-channelABPode(UsewithLG01/LG02)===1048 +AT+FDR Reset Parameters to Factory Default, Keys Reserve 1294 1294 1050 +AT+NJM=0 Set to ABP mode 1295 1295 1296 - (% style="background-color:#dcdcdc" %)**AT+FDR**(%%) ResetParametersto FactoryDefault,KeysReserve1052 +AT+ADR=0 Set the Adaptive Data Rate Off 1297 1297 1298 - (% style="background-color:#dcdcdc" %)**AT+NJM=0**(%%)Set toABP mode1054 +AT+DR=5 Set Data Rate 1299 1299 1300 - (% style="background-color:#dcdcdc" %)**AT+ADR=0**(%%)Set the AdaptiveDataRateOff1056 +AT+TDC=60000 Set transmit interval to 60 seconds 1301 1301 1302 - (% style="background-color:#dcdcdc" %)**AT+DR=5**(%%)SetDataRate1058 +AT+CHS=868400000 Set transmit frequency to 868.4Mhz 1303 1303 1304 - (% style="background-color:#dcdcdc" %)**AT+TDC=60000**(%%)Settransmit interval60seconds1060 +AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server) 1305 1305 1306 - (% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%)Set transmitfrequencyto868.4Mhz1062 +AT+RX2DR=5 Set RX2DR to match the downlink DR from server. see below 1307 1307 1308 - (% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000**(%%)SetRX2Frequencyto868.4Mhz(accordingto theresult fromserver)1064 +AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal. 1309 1309 1310 - (% style="background-color:#dcdcdc" %)**AT+RX2DR=5**(%%) SetRX2DR to match thedownlink DR fromserver.see below1066 +ATZ Reset MCU 1311 1311 1312 - (% style="background-color:#dcdcdc" %)**AT+DADDR=26** (%%) 01 1A F1 Set Device Address to26 01 1A F1,this ID can befound in the LoRa Server portal.1068 +**Note:** 1313 1313 1314 -(% style="background-color:#dcdcdc" %)**ATZ** (%%) Reset MCU 1070 +1. Make sure the device is set to ABP mode in the IoT Server. 1071 +1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting. 1072 +1. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means. 1073 +1. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5 1315 1315 1075 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]] 1316 1316 1317 -(% style="color:red" %)**Note:** 1318 1318 1319 -(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server. 1320 -2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting. 1321 -3. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means. 1322 -4. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5 1078 +1. FAQ 1079 +11. How to upgrade the image? 1323 1323 1324 -[[image:1654136435598-589.png]] 1325 - 1326 - 1327 -= 6. FAQ = 1328 - 1329 -== 6.1 How to upgrade the image? == 1330 - 1331 1331 The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to: 1332 1332 1333 1333 * Support new features ... ... @@ -1336,7 +1336,7 @@ 1336 1336 1337 1337 Below shows the hardware connection for how to upload an image to RS485-BL: 1338 1338 1339 -[[image: 1654136646995-976.png]]1089 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]] 1340 1340 1341 1341 **Step1:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. 1342 1342 ... ... @@ -1344,102 +1344,97 @@ 1344 1344 1345 1345 **Step3: **Open flashloader; choose the correct COM port to update. 1346 1346 1347 -[[image:image-20220602102605-1.png]] 1348 1348 1098 +|((( 1099 +HOLD PRO then press the RST button, SYS will be ON, then click next 1100 +))) 1349 1349 1350 -[[image:image-20220602102637-2.png]] 1102 +|((( 1103 +Board detected 1104 +))) 1351 1351 1106 +|((( 1107 + 1108 +))) 1352 1352 1353 -[[image:image -20220602102715-3.png]]1110 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]] 1354 1354 1355 1355 1356 1356 1357 - ==6.2 HowtongetheLoRaFrequency Bands/Region? ==1114 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]] 1358 1358 1359 -((( 1360 -User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download. 1361 -))) 1362 1362 1117 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]] 1363 1363 1364 1364 1365 -== 6.3 How many RS485-Slave can RS485-BL connects? == 1120 +1. 1121 +11. How to change the LoRa Frequency Bands/Region? 1366 1366 1367 -((( 1368 -The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]]. 1369 -))) 1123 +User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. 1370 1370 1371 1371 1372 1372 1373 -= 7. Trouble Shooting = 1127 +1. 1128 +11. How many RS485-Slave can RS485-BL connects? 1374 1374 1130 +The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>path:#downlink_A8]]. 1375 1375 1376 -== 7.1 Downlink doesn’t work, how to solve it? == 1377 1377 1378 -Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]] 1379 1379 1380 1380 1381 -== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? == 1135 +1. Trouble Shooting 1136 +11. Downlink doesn’t work, how to solve it? 1382 1382 1383 - It might about the channels mapping.Please seefor detail:[[NoticeofFrequencyband>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]1138 +Please see this link for debug: 1384 1384 1140 +[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]] 1385 1385 1386 -= 8. Order Info = 1387 1387 1388 -(% style="color:blue" %)**Part Number: RS485-BL-XXX** 1389 1389 1390 -(% style="color:blue" %)**XXX:** 1144 +1. 1145 +11. Why I can’t join TTN V3 in US915 /AU915 bands? 1391 1391 1392 -* (% style="color:blue" %)**EU433**(%%): frequency bands EU433 1393 -* (% style="color:blue" %)**EU868**(%%): frequency bands EU868 1394 -* (% style="color:blue" %)**KR920**(%%): frequency bands KR920 1395 -* (% style="color:blue" %)**CN470**(%%): frequency bands CN470 1396 -* (% style="color:blue" %)**AS923**(%%): frequency bands AS923 1397 -* (% style="color:blue" %)**AU915**(%%): frequency bands AU915 1398 -* (% style="color:blue" %)**US915**(%%): frequency bands US915 1399 -* (% style="color:blue" %)**IN865**(%%): frequency bands IN865 1400 -* (% style="color:blue" %)**RU864**(%%): frequency bands RU864 1401 -* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865 1147 +It might about the channels mapping. Please see for detail. 1402 1402 1403 -= PackingInfo1149 +[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]] 1404 1404 1405 -((( 1151 + 1152 + 1153 +1. Order Info 1154 + 1155 +**Part Number: RS485-BL-XXX** 1156 + 1157 +**XXX:** 1158 + 1159 +* **EU433**: frequency bands EU433 1160 +* **EU868**: frequency bands EU868 1161 +* **KR920**: frequency bands KR920 1162 +* **CN470**: frequency bands CN470 1163 +* **AS923**: frequency bands AS923 1164 +* **AU915**: frequency bands AU915 1165 +* **US915**: frequency bands US915 1166 +* **IN865**: frequency bands IN865 1167 +* **RU864**: frequency bands RU864 1168 +* **KZ865: **frequency bands KZ865 1169 + 1170 +1. Packing Info 1171 + 1406 1406 **Package Includes**: 1407 -))) 1408 1408 1409 -* ((( 1410 -RS485-BL x 1 1411 -))) 1412 -* ((( 1413 -Stick Antenna for LoRa RF part x 1 1414 -))) 1415 -* ((( 1416 -Program cable x 1 1417 -))) 1174 +* RS485-BL x 1 1175 +* Stick Antenna for LoRa RF part x 1 1176 +* Program cable x 1 1418 1418 1419 -((( 1420 1420 **Dimension and weight**: 1421 -))) 1422 1422 1423 -* ((( 1424 -Device Size: 13.5 x 7 x 3 cm 1425 -))) 1426 -* ((( 1427 -Device Weight: 105g 1428 -))) 1429 -* ((( 1430 -Package Size / pcs : 14.5 x 8 x 5 cm 1431 -))) 1432 -* ((( 1433 -Weight / pcs : 170g 1180 +* Device Size: 13.5 x 7 x 3 cm 1181 +* Device Weight: 105g 1182 +* Package Size / pcs : 14.5 x 8 x 5 cm 1183 +* Weight / pcs : 170g 1434 1434 1435 - 1436 -))) 1185 +1. Support 1437 1437 1438 -= 10. Support = 1187 +* 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. 1188 +* 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 1439 1439 1440 -* ((( 1441 -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. 1442 -))) 1443 -* ((( 1444 -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]] 1445 -))) 1190 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
- 1652953542269-423.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -118.5 KB - Content
- 1652953553383-907.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -94.0 KB - Content
- 1652953568895-172.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -109.3 KB - Content
- 1652954654347-831.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.7 KB - Content
- 1653271044481-711.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.8 KB - Content
- 1653271276735-972.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -26.6 KB - Content
- 1653271581490-837.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.7 KB - Content
- 1653271648378-342.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -131.4 KB - Content
- 1653271657255-576.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -142.6 KB - Content
- 1653271763403-806.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.7 KB - Content
- 1653272787040-634.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -294.0 KB - Content
- 1653272817147-600.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.3 KB - Content
- 1653272901032-107.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -197.8 KB - Content
- 1653273818896-432.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.6 KB - Content
- 1653274001211-372.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.4 KB - Content
- 1654132684752-193.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.8 KB - Content
- 1654133913295-597.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -116.2 KB - Content
- 1654133954153-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.2 KB - Content
- 1654134704555-320.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.4 KB - Content
- 1654135840598-282.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -1.3 MB - Content
- 1654136105500-922.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -203.7 KB - Content
- 1654136435598-589.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -158.9 KB - Content
- 1654136646995-976.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -1.3 MB - Content
- image-20220519174512-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -32.2 KB - Content
- image-20220519174512-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -42.7 KB - Content
- image-20220519174512-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.3 KB - Content
- image-20220519174512-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -19.1 KB - Content
- image-20220602102605-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -102.6 KB - Content
- image-20220602102637-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -250.8 KB - Content
- image-20220602102715-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -176.2 KB - Content