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, 24 removed)
- 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-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,288 +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="190" style="background-color:#ffffcc; color:green; width:510px" %) 286 -|=(% style="width: 125px;" %)((( 287 -((( 288 -**AT Commands** 289 -))) 290 -)))|=(% style="width: 110px;" %)((( 291 -((( 292 -**Description** 293 -))) 294 -)))|=(% style="width: 255px;" %)((( 295 -((( 296 -**Example** 297 -))) 298 -))) 299 -|(% style="width:125px" %)((( 300 -((( 301 -AT+BAUDR 302 -))) 303 -)))|(% style="width:110px" %)((( 304 -((( 305 -Set the baud rate (for RS485 connection). Default Value is: 9600. 306 -))) 307 -)))|(% style="width:255px" %)((( 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:125px" %)((( 321 -((( 322 -AT+PARITY 323 -))) 324 -)))|(% style="width:110px" %)((( 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:255px" %)((( 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:125px" %)((( 350 -((( 351 -AT+STOPBIT 352 -))) 353 -)))|(% style="width:110px" %)((( 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:255px" %)((( 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" style="background-color:#ffffcc; color:green; width:806px" %) 396 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example** 397 -|AT+CFGDEV|(% style="width:418px" %)((( 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:256px" %)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 -=== 3.3.3 Configure read commands for each sampling === 409 409 410 -((( 311 + 312 + 313 +1. 314 +11. 315 +111. Configure read commands for each sampling 316 + 411 411 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. 412 -))) 413 413 414 - (((319 + 415 415 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. 416 -))) 417 417 418 - (((322 + 419 419 To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload. 420 -))) 421 421 422 - (((325 + 423 423 This section describes how to achieve above goals. 424 -))) 425 425 426 - (((328 + 427 427 During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 428 -))) 429 429 430 - (((331 + 431 431 **Command from RS485-BL to Sensor:** 432 -))) 433 433 434 -((( 435 435 RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar. 436 -))) 437 437 438 - (((336 + 439 439 **Handle return from sensors to RS485-BL**: 440 -))) 441 441 442 -((( 443 443 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** 444 -))) 445 445 446 -* ((( 447 -**AT+DATACUT** 448 -))) 449 449 450 -((( 342 +* **AT+DATACUT** 343 + 451 451 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. 452 -))) 453 453 454 -* ((( 455 -**AT+SEARCH** 456 -))) 457 457 458 -((( 347 +* **AT+SEARCH** 348 + 459 459 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. 460 -))) 461 461 462 - (((351 + 463 463 **Define wait timeout:** 464 -))) 465 465 466 -((( 467 467 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 468 -))) 469 469 470 - (((356 + 471 471 After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**. 472 -))) 473 473 359 + 474 474 **Examples:** 475 475 476 476 Below are examples for the how above AT Commands works. 477 477 364 + 478 478 **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is: 479 479 480 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %) 481 -|(% style="width:498px" %)((( 367 +|((( 482 482 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 483 483 484 484 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent** ... ... @@ -490,38 +490,41 @@ 490 490 491 491 In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 492 492 379 + 493 493 **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 494 494 495 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %) 496 -|(% style="width:577px" %)((( 382 +|((( 497 497 **AT+SEARCHx=aa,xx xx xx xx xx** 498 498 499 499 * **aa: 1: prefix match mode; 2: prefix and suffix match mode** 500 500 * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix** 387 + 388 + 501 501 ))) 502 502 503 - **Examples:**391 +Examples: 504 504 505 -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 506 506 507 507 If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 508 508 509 -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 510 510 511 -[[image: 1653271044481-711.png]]399 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]] 512 512 513 -2)For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 514 514 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 + 515 515 If we set AT+SEARCH1=2, 1E 56 34+31 00 49 516 516 517 -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 518 518 519 -[[image: 1653271276735-972.png]]408 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]] 520 520 410 + 521 521 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 522 522 523 -(% style="background-color:#4f81bd; color:white; width:729px" %) 524 -|(% style="width:726px" %)((( 413 +|((( 525 525 **AT+DATACUTx=a,b,c** 526 526 527 527 * **a: length for the return of AT+COMMAND** ... ... @@ -529,143 +529,98 @@ 529 529 * **c: define the position for valid value. ** 530 530 ))) 531 531 532 - **Examples:**421 +Examples: 533 533 534 534 * Grab bytes: 535 535 536 -[[image: 1653271581490-837.png||height="313" width="722"]]425 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]] 537 537 538 - 539 539 * Grab a section. 540 540 541 -[[image: 1653271648378-342.png||height="326" width="720"]]429 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]] 542 542 543 - 544 544 * Grab different sections. 545 545 546 -[[image: 1653271657255-576.png||height="305" width="730"]]433 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]] 547 547 548 -((( 549 -(% style="color:red" %)**Note:** 550 -))) 551 551 552 -((( 436 +Note: 437 + 553 553 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. 554 -))) 555 555 556 -((( 557 -**Example:** 558 -))) 440 +Example: 559 559 560 -((( 561 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 562 -))) 442 +AT+COMMAND1=11 01 1E D0,0 563 563 564 -((( 565 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34 566 -))) 444 +AT+SEARCH1=1,1E 56 34 567 567 568 -((( 569 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5 570 -))) 446 +AT+DATACUT1=0,2,1~~5 571 571 572 -((( 573 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 574 -))) 448 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 575 575 576 -((( 577 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 578 -))) 450 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 579 579 580 -((( 581 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 582 -))) 452 +Valid payload after DataCUT command: 2e 30 58 5f 36 583 583 584 -[[image: 1653271763403-806.png]]454 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 585 585 586 586 587 -=== 3.3.4 Compose the uplink payload === 588 588 589 -((( 458 + 459 +1. 460 +11. 461 +111. Compose the uplink payload 462 + 590 590 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.** 591 -))) 592 592 593 -((( 594 -(% style="color:#037691" %)**Examples: AT+DATAUP=0** 595 -))) 596 596 597 -((( 598 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**. 599 -))) 466 +**Examples: AT+DATAUP=0** 600 600 601 -((( 468 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**. 469 + 602 602 Final Payload is 603 -))) 604 604 605 -((( 606 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx** 607 -))) 472 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 608 608 609 -((( 610 610 Where PAYVER is defined by AT+PAYVER, below is an example screen shot. 611 -))) 612 612 613 -[[image: 1653272787040-634.png||height="515" width="719"]]476 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 614 614 615 615 616 616 617 -((( 618 -(% style="color:#037691" %)**Examples: AT+DATAUP=1** 480 +**Examples: AT+DATAUP=1** 619 619 620 - 621 -))) 482 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 622 622 623 -((( 624 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 625 -))) 626 - 627 -((( 628 628 Final Payload is 629 -))) 630 630 631 -((( 632 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 633 -))) 486 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 634 634 635 -1. ((( 636 -Battery Info (2 bytes): Battery voltage 637 -))) 638 -1. ((( 639 -PAYVER (1 byte): Defined by AT+PAYVER 640 -))) 641 -1. ((( 642 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 643 -))) 644 -1. ((( 645 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 646 -))) 647 -1. ((( 648 -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 649 -))) 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 650 650 651 -[[image: 1653272817147-600.png||height="437" width="717"]]494 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 652 652 496 + 653 653 So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 654 654 499 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41 655 655 656 -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 657 657 658 -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 659 659 660 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30 661 661 662 662 663 663 Below are the uplink payloads: 664 664 665 -[[image: 1653272901032-107.png]]509 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]] 666 666 667 667 668 - (% 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: 669 669 670 670 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date) 671 671 ... ... @@ -677,185 +677,139 @@ 677 677 678 678 679 679 680 -=== 3.3.5 Uplink on demand === 524 +1. 525 +11. 526 +111. Uplink on demand 681 681 682 -((( 683 683 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. 684 -))) 685 685 686 -((( 687 687 Downlink control command: 688 -))) 689 689 690 -((( 691 -**0x08 command**: Poll an uplink with current command set in RS485-BL. 692 -))) 532 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL. 693 693 694 -((( 695 -**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. 696 696 697 - 698 -))) 699 699 700 -=== 3.3.6 Uplink on Interrupt === 701 701 702 -Put the interrupt sensor between 3.3v_out and GPIO ext. 538 +1. 539 +11. 540 +111. Uplink on Interrupt 703 703 704 -[[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]] 705 705 706 - 707 -((( 708 708 AT+INTMOD=0 Disable Interrupt 709 -))) 710 710 711 -((( 712 712 AT+INTMOD=1 Interrupt trigger by rising or falling edge. 713 -))) 714 714 715 -((( 716 716 AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 717 -))) 718 718 719 -((( 720 720 AT+INTMOD=3 Interrupt trigger by rising edge. 721 721 722 - 723 -))) 724 724 725 -== 3.4 Uplink Payload == 553 +1. 554 +11. Uplink Payload 726 726 727 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %) 728 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands** 729 -|Value|(% style="width:130px" %)((( 730 -((( 556 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 557 +|Value|((( 731 731 Battery(mV) 732 -))) 733 733 734 -((( 735 735 & 736 -))) 737 737 738 -((( 739 739 Interrupt _Flag 740 -))) 741 -)))|(% style="width:93px" %)((( 563 +)))|((( 742 742 PAYLOAD_VER 743 743 744 744 745 -)))| (% 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. 746 746 747 747 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 748 748 749 -((( 750 -{{{function Decoder(bytes, port) {}}} 751 -))) 752 752 753 -((( 754 -{{{//Payload Formats of RS485-BL Deceive}}} 755 -))) 572 +function Decoder(bytes, port) { 756 756 757 -((( 758 -{{{return {}}} 759 -))) 574 +~/~/Payload Formats of RS485-BL Deceive 760 760 761 -((( 762 -{{{ //Battery,units:V}}} 763 -))) 576 +return { 764 764 765 -((( 766 -{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}} 767 -))) 578 + ~/~/Battery,units:V 768 768 769 -((( 770 -{{{ //GPIO_EXTI }}} 771 -))) 580 + BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 772 772 773 -((( 774 -{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}} 775 -))) 582 + ~/~/GPIO_EXTI 776 776 777 -((( 778 -{{{ //payload of version}}} 779 -))) 584 + EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 780 780 781 -((( 782 -{{{ Pay_ver:bytes[2],}}} 783 -))) 586 + ~/~/payload of version 784 784 785 -((( 786 -{{{ }; }}} 787 -))) 588 + Pay_ver:bytes[2], 788 788 789 -((( 790 -**}** 590 + }; 791 791 792 - 793 -))) 592 + } 794 794 795 -((( 796 -TTN V3 uplink screen shot. 797 -))) 798 798 799 -[[image:1653274001211-372.png||height="192" width="732"]] 800 800 801 801 802 -== 3.5 Configure RS485-BL via AT or Downlink == 803 803 804 -User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands 805 805 806 -There are two kinds of Commands: 807 807 808 - * (% 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. 809 809 810 - * (% 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]] 811 811 812 -=== 3.5.1 Common Commands: === 604 +1. 605 +11. Configure RS485-BL via AT or Downlink 813 813 814 - 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 815 815 609 +There are two kinds of Commands: 816 816 817 - ===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 818 818 613 +* **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 819 819 820 -==== **Choose Device Type (RS485 or TTL)** ==== 615 +1. 616 +11. 617 +111. Common Commands: 821 821 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 + 822 822 RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect. 823 823 824 -* **AT Command**630 +* AT Command 825 825 826 -(% class="box infomessage" %) 827 -((( 828 828 **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins. 829 -))) 830 830 831 -(% class="box infomessage" %) 832 -((( 833 833 **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins. 834 -))) 835 835 836 836 837 -* **Downlink Payload**637 +* Downlink Payload 838 838 839 -**0A aa** ~-~->same as AT+MOD=aa639 +**0A aa** à same as AT+MOD=aa 840 840 841 841 842 842 843 -==== **RS485 Debug Command (AT+CFGDEV)**====643 +==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ==== 844 844 845 845 This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling. 846 846 847 -* **AT Command**647 +* AT Command 848 848 849 -(% class="box infomessage" %) 850 -((( 851 -**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m** 852 -))) 649 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 853 853 854 854 m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command. 855 855 856 856 857 -* **Downlink Payload** 858 858 655 +* Downlink Payload 656 + 859 859 Format: A8 MM NN XX XX XX XX YY 860 860 861 861 Where: ... ... @@ -869,15 +869,15 @@ 869 869 870 870 To connect a Modbus Alarm with below commands. 871 871 872 -* 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. 873 873 874 -* 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. 875 875 876 876 So if user want to use downlink command to control to RS485 Alarm, he can use: 877 877 878 - (% 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 879 879 880 - (% 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 881 881 882 882 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. 883 883 ... ... @@ -886,61 +886,48 @@ 886 886 887 887 Check TTL Sensor return: 888 888 889 -[[image: 1654132684752-193.png]]687 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]] 890 890 891 891 892 892 893 893 894 -==== **Set Payload version**====692 +==== Set Payload version ==== 895 895 896 896 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. 897 897 898 -* **AT Command:**696 +* AT Command: 899 899 900 -(% class="box infomessage" %) 901 -((( 902 -**AT+PAYVER: Set PAYVER field = 1** 903 -))) 698 +AT+PAYVER: Set PAYVER field = 1 904 904 905 905 906 -* **Downlink Payload:**701 +* Downlink Payload: 907 907 908 - **0xAE 01**~-~->Set PAYVER field = 0x01703 +0xAE 01 à Set PAYVER field = 0x01 909 909 910 - **0xAE 0F**~-~->Set PAYVER field = 0x0F705 +0xAE 0F à Set PAYVER field = 0x0F 911 911 912 912 708 +==== Set RS485 Sampling Commands ==== 913 913 914 -==== **Set RS485 Sampling Commands** ==== 915 - 916 916 AT+COMMANDx, AT+DATACUTx and AT+SEARCHx 917 917 918 -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]]. 919 919 920 920 921 -* **AT Command:**715 +* AT Command: 922 922 923 -(% class="box infomessage" %) 924 -((( 925 -**AT+COMMANDx: Configure RS485 read command to sensor.** 926 -))) 717 +AT+COMMANDx: Configure RS485 read command to sensor. 927 927 928 -(% class="box infomessage" %) 929 -((( 930 -**AT+DATACUTx: Configure how to handle return from RS485 devices.** 931 -))) 719 +AT+DATACUTx: Configure how to handle return from RS485 devices. 932 932 933 -(% class="box infomessage" %) 934 -((( 935 -**AT+SEARCHx: Configure search command** 936 -))) 721 +AT+SEARCHx: Configure search command 937 937 938 938 939 -* **Downlink Payload:**724 +* Downlink Payload: 940 940 941 - **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. 942 942 943 - (% 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. 944 944 945 945 Format: AF MM NN LL XX XX XX XX YY 946 946 ... ... @@ -947,23 +947,23 @@ 947 947 Where: 948 948 949 949 * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F, 950 -* NN: 951 -* 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 952 952 * XX XX XX XX: AT+COMMAND or AT+DATACUT command 953 -* 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. 954 954 955 - **Example:**740 +Example: 956 956 957 - (% 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 958 958 959 - (% 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** 960 960 961 - (% 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** 962 962 963 963 964 - **0xAB**downlink command can be used for set AT+SEARCHx749 +0xAB downlink command can be used for set AT+SEARCHx 965 965 966 - **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 967 967 968 968 * AB aa 01 03 xx xx xx same as AT+SEARCHaa=1,xx xx xx 969 969 * 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 ... ... @@ -971,166 +971,145 @@ 971 971 **AB aa 02 03 xx xx xx 02 yy yy** same as **AT+SEARCHaa=2,xx xx xx+yy yy** 972 972 973 973 759 +==== Fast command to handle MODBUS device ==== 974 974 975 -==== **Fast command to handle MODBUS device** ==== 976 - 977 977 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]]. 978 978 979 979 This command is valid since v1.3 firmware version 980 980 981 981 982 - **AT+MBFUN has only two value:**766 +AT+MBFUN has only two value: 983 983 984 -* **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 985 985 986 986 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. 987 987 988 -* **AT+MBFUN=0**: Disable Modbus fast reading.772 +* AT+MBFUN=0: Disable Modbus fast reading. 989 989 990 - **Example:**774 +Example: 991 991 992 992 * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). 993 993 * 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. 994 994 * 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. 995 995 996 -[[image: 1654133913295-597.png]]780 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]] 997 997 998 998 999 -[[image: 1654133954153-643.png]]783 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]] 1000 1000 1001 1001 1002 -* **Downlink Commands:**786 +* Downlink Commands: 1003 1003 1004 - **A9 aa**~-~->Same as AT+MBFUN=aa788 +A9 aa -à Same as AT+MBFUN=aa 1005 1005 1006 1006 791 +==== RS485 command timeout ==== 1007 1007 1008 -==== **RS485 command timeout** ==== 1009 - 1010 1010 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. 1011 1011 1012 1012 Default value: 0, range: 0 ~~ 5 seconds 1013 1013 1014 1014 1015 -* **AT Command:**798 +* AT Command: 1016 1016 1017 -(% class="box infomessage" %) 1018 -((( 1019 -**AT+CMDDLaa=hex(bb cc)** 1020 -))) 800 +AT+CMDDLaa=hex(bb cc) 1021 1021 1022 - **Example:**802 +Example: 1023 1023 1024 1024 **AT+CMDDL1=1000** to send the open time to 1000ms 1025 1025 1026 1026 1027 -* **Downlink Payload:**807 +* Downlink Payload: 1028 1028 1029 1029 0x AA aa bb cc 1030 1030 1031 1031 Same as: AT+CMDDLaa=hex(bb cc) 1032 1032 1033 - **Example:**813 + Example: 1034 1034 1035 - **0xAA 01 03 E8**~-~->Same as **AT+CMDDL1=1000 ms**815 + 0xAA 01 03 E8 à Same as **AT+CMDDL1=1000 ms** 1036 1036 1037 1037 818 +==== [[Uplink>>path:#downlink_A8]] payload mode ==== 1038 1038 1039 -==== **Uplink payload mode** ==== 1040 - 1041 1041 Define to use one uplink or multiple uplinks for the sampling. 1042 1042 1043 -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]] 1044 1044 1045 -* **AT Command:**824 +* AT Command: 1046 1046 1047 -(% class="box infomessage" %) 1048 -((( 1049 -**AT+DATAUP=0** 1050 -))) 826 +AT+DATAUP=0 1051 1051 1052 -(% class="box infomessage" %) 1053 -((( 1054 -**AT+DATAUP=1** 1055 -))) 828 +AT+DATAUP=1 1056 1056 1057 1057 1058 -* **Downlink Payload:**831 +* Downlink Payload: 1059 1059 1060 - **0xAD 00****~-~->**Same as AT+DATAUP=0833 +0xAD 00 à Same as AT+DATAUP=0 1061 1061 1062 - **0xAD 01****~-~->**Same as AT+DATAUP=1835 +0xAD 01 à Same as AT+DATAUP=1 1063 1063 1064 1064 838 +==== Manually trigger an Uplink ==== 1065 1065 1066 - 1067 -==== **Manually trigger an Uplink** ==== 1068 - 1069 1069 Ask device to send an uplink immediately. 1070 1070 1071 -* **Downlink Payload:**842 +* Downlink Payload: 1072 1072 1073 - **0x08 FF**, RS485-BL will immediately send an uplink.844 +0x08 FF, RS485-BL will immediately send an uplink. 1074 1074 1075 1075 847 +==== Clear RS485 Command ==== 1076 1076 1077 - 1078 -==== **Clear RS485 Command** ==== 1079 - 1080 1080 The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them. 1081 1081 1082 1082 1083 -* **AT Command:**852 +* AT Command: 1084 1084 1085 - (% 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 1086 1086 856 +Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10 857 + 1087 1087 Example screen shot after clear all RS485 commands. 1088 1088 1089 1089 861 + 1090 1090 The uplink screen shot is: 1091 1091 1092 -[[image: 1654134704555-320.png]]864 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 1093 1093 1094 1094 1095 -* **Downlink Payload:**867 +* Downlink Payload: 1096 1096 1097 - **0x09 aa bb**same as AT+CMDEAR=aa,bb869 +0x09 aa bb same as AT+CMDEAR=aa,bb 1098 1098 1099 1099 872 +==== Set Serial Communication Parameters ==== 1100 1100 1101 -==== **Set Serial Communication Parameters** ==== 1102 - 1103 1103 Set the Rs485 serial communication parameters: 1104 1104 1105 -* **AT Command:**876 +* AT Command: 1106 1106 1107 1107 Set Baud Rate: 1108 1108 1109 -(% class="box infomessage" %) 1110 -((( 1111 -**AT+BAUDR=9600** ~/~/ Options: (1200,2400,4800,14400,19200,115200) 1112 -))) 880 +AT+BAUDR=9600 ~/~/ Options: (1200,2400,4800,14400,19200,115200) 1113 1113 1114 -Set UART Parity 1115 1115 1116 -(% class="box infomessage" %) 1117 -((( 1118 -**AT+PARITY=0** ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 1119 -))) 883 +Set UART parity 1120 1120 885 +AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 886 + 887 + 1121 1121 Set STOPBIT 1122 1122 1123 -(% class="box infomessage" %) 1124 -((( 1125 -**AT+STOPBIT=0** ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 1126 -))) 890 +AT+STOPBIT=0 ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 1127 1127 1128 1128 1129 -* **Downlink Payload:**893 +* Downlink Payload: 1130 1130 1131 - **A7 01 aa bb**: Same AT+BAUDR=hex(aa bb)*100895 +A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100 1132 1132 1133 - **Example:**897 +Example: 1134 1134 1135 1135 * A7 01 00 60 same as AT+BAUDR=9600 1136 1136 * A7 01 04 80 same as AT+BAUDR=115200 ... ... @@ -1140,189 +1140,180 @@ 1140 1140 A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02) 1141 1141 1142 1142 907 +==== Control output power duration ==== 1143 1143 1144 -==== **Control output power duration** ==== 1145 - 1146 1146 User can set the output power duration before each sampling. 1147 1147 1148 -* **AT Command:**911 +* AT Command: 1149 1149 1150 - **Example:**913 +Example: 1151 1151 1152 - **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. 1153 1153 1154 - **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. 1155 1155 1156 1156 1157 -* **LoRaWAN Downlink Command:**920 +* LoRaWAN Downlink Command: 1158 1158 1159 - **07 01 aa bb**Same as AT+5VT=(aa bb)922 +07 01 aa bb Same as AT+5VT=(aa bb) 1160 1160 1161 - **07 02 aa bb**Same as AT+3V3T=(aa bb)924 +07 02 aa bb Same as AT+3V3T=(aa bb) 1162 1162 1163 1163 1164 1164 1165 -== 3.6 Buttons == 1166 1166 1167 -(% border="1" style="background-color:#ffffcc; color:green; width:233px" %) 1168 -|=(% style="width: 89px;" %)**Button**|=(% style="width: 141px;" %)**Feature** 1169 -|(% style="width:89px" %)**RST**|(% style="width:141px" %)Reboot RS485-BL 929 +1. 930 +11. Buttons 1170 1170 1171 -== 3.7 +3V3 Output == 932 +|**Button**|**Feature** 933 +|**RST**|Reboot RS485-BL 1172 1172 935 +1. 936 +11. +3V3 Output 937 + 1173 1173 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. 1174 1174 1175 1175 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. 1176 1176 942 + 1177 1177 The +3V3 output time can be controlled by AT Command. 1178 1178 945 +**AT+3V3T=1000** 1179 1179 1180 -(% style="color:#037691" %)**AT+3V3T=1000** 1181 - 1182 - 1183 1183 Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors. 1184 1184 949 + 1185 1185 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 1186 1186 1187 1187 1188 -== 3.8 +5V Output == 953 +1. 954 +11. +5V Output 1189 1189 1190 1190 RS485-BL has a Controllable +5V output, user can use this output to power external sensor. 1191 1191 1192 1192 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. 1193 1193 960 + 1194 1194 The 5V output time can be controlled by AT Command. 1195 1195 963 +**AT+5VT=1000** 1196 1196 1197 -(% style="color:#037691" %)**AT+5VT=1000** 1198 - 1199 - 1200 1200 Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors. 1201 1201 967 + 1202 1202 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. 1203 1203 1204 1204 1205 -== 3.9 LEDs == 1206 1206 1207 -(% border="1" style="background-color:#ffffcc; color:green; width:332px" %) 1208 -|=**LEDs**|=(% style="width: 274px;" %)**Feature** 1209 -|**LED1**|(% style="width:274px" %)Blink when device transmit a packet. 1210 1210 1211 -== 3.10 Switch Jumper == 973 +1. 974 +11. LEDs 1212 1212 1213 -(% border="1" style="background-color:#ffffcc; color:green; width:515px" %) 1214 -|=(% style="width: 124px;" %)**Switch Jumper**|=(% style="width: 388px;" %)**Feature** 1215 -|(% 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**|((( 1216 1216 ISP position: Upgrade firmware via UART 1217 1217 1218 1218 Flash position: Configure device, check running status. 1219 1219 ))) 1220 -| (% style="width:124px" %)**SW2**|(% style="width:388px" %)(((988 +|**SW2**|((( 1221 1221 5V position: set to compatible with 5v I/O. 1222 1222 1223 1223 3.3v position: set to compatible with 3.3v I/O., 1224 1224 ))) 1225 1225 1226 - **+3.3V**: is always ON994 ++3.3V: is always ON 1227 1227 1228 - **+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. 1229 1229 998 +1. Case Study 1230 1230 1231 - =4.CaseStudy =1000 +User can check this URL for some case studies. 1232 1232 1233 - 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]] 1234 1234 1235 1235 1236 -= 5. Use AT Command = 1237 1237 1238 -== 5.1 Access AT Command == 1239 1239 1007 +1. Use AT Command 1008 +11. Access AT Command 1009 + 1240 1240 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. 1241 1241 1242 -[[image: 1654135840598-282.png]]1012 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]] 1243 1243 1244 1244 1245 -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: 1246 1246 1247 -[[image: 1654136105500-922.png]]1017 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]] 1248 1248 1249 1249 1250 -More detail AT Command manual can be found at [[AT Command Manual>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] 1251 1251 1021 +More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]] 1252 1252 1253 -== 5.2 Common AT Command Sequence == 1254 1254 1255 -=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) === 1256 1256 1025 +1. 1026 +11. Common AT Command Sequence 1027 +111. Multi-channel ABP mode (Use with SX1301/LG308) 1028 + 1257 1257 If device has not joined network yet: 1258 1258 1259 -(% class="box infomessage" %) 1260 -((( 1261 -**AT+FDR** 1262 -))) 1031 +AT+FDR 1263 1263 1264 -(% class="box infomessage" %) 1265 -((( 1266 -**AT+NJM=0** 1267 -))) 1033 +AT+NJM=0 1268 1268 1269 -(% class="box infomessage" %) 1270 -((( 1271 -**ATZ** 1272 -))) 1035 +ATZ 1273 1273 1274 1274 1275 1275 If device already joined network: 1276 1276 1277 -(% class="box infomessage" %) 1278 -((( 1279 -**AT+NJM=0** 1280 -))) 1040 +AT+NJM=0 1281 1281 1282 -(% class="box infomessage" %) 1283 -((( 1284 -**ATZ** 1285 -))) 1042 +ATZ 1286 1286 1044 +1. 1045 +11. 1046 +111. Single-channel ABP mode (Use with LG01/LG02) 1287 1287 1288 - ===5.5.2 Single-channelABPode(UsewithLG01/LG02)===1048 +AT+FDR Reset Parameters to Factory Default, Keys Reserve 1289 1289 1050 +AT+NJM=0 Set to ABP mode 1290 1290 1291 - (% style="background-color:#dcdcdc" %)**AT+FDR**(%%) ResetParametersto FactoryDefault,KeysReserve1052 +AT+ADR=0 Set the Adaptive Data Rate Off 1292 1292 1293 - (% style="background-color:#dcdcdc" %)**AT+NJM=0**(%%)Set toABP mode1054 +AT+DR=5 Set Data Rate 1294 1294 1295 - (% style="background-color:#dcdcdc" %)**AT+ADR=0**(%%)Set the AdaptiveDataRateOff1056 +AT+TDC=60000 Set transmit interval to 60 seconds 1296 1296 1297 - (% style="background-color:#dcdcdc" %)**AT+DR=5**(%%)SetDataRate1058 +AT+CHS=868400000 Set transmit frequency to 868.4Mhz 1298 1298 1299 - (% style="background-color:#dcdcdc" %)**AT+TDC=60000**(%%)Settransmit interval60seconds1060 +AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server) 1300 1300 1301 - (% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%)Set transmitfrequencyto868.4Mhz1062 +AT+RX2DR=5 Set RX2DR to match the downlink DR from server. see below 1302 1302 1303 - (% 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. 1304 1304 1305 - (% style="background-color:#dcdcdc" %)**AT+RX2DR=5**(%%) SetRX2DR to match thedownlink DR fromserver.see below1066 +ATZ Reset MCU 1306 1306 1307 - (% 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:** 1308 1308 1309 -(% 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 1310 1310 1075 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]] 1311 1311 1312 -(% style="color:red" %)**Note:** 1313 1313 1314 -(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server. 1315 -2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting. 1316 -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. 1317 -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? 1318 1318 1319 -[[image:1654136435598-589.png]] 1320 - 1321 - 1322 -= 6. FAQ = 1323 - 1324 -== 6.1 How to upgrade the image? == 1325 - 1326 1326 The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to: 1327 1327 1328 1328 * Support new features ... ... @@ -1331,7 +1331,7 @@ 1331 1331 1332 1332 Below shows the hardware connection for how to upload an image to RS485-BL: 1333 1333 1334 -[[image: 1654136646995-976.png]]1089 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]] 1335 1335 1336 1336 **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]]. 1337 1337 ... ... @@ -1339,102 +1339,97 @@ 1339 1339 1340 1340 **Step3: **Open flashloader; choose the correct COM port to update. 1341 1341 1342 -[[image:image-20220602102605-1.png]] 1343 1343 1098 +|((( 1099 +HOLD PRO then press the RST button, SYS will be ON, then click next 1100 +))) 1344 1344 1345 -[[image:image-20220602102637-2.png]] 1102 +|((( 1103 +Board detected 1104 +))) 1346 1346 1106 +|((( 1107 + 1108 +))) 1347 1347 1348 -[[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]] 1349 1349 1350 1350 1351 1351 1352 - ==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]] 1353 1353 1354 -((( 1355 -User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download. 1356 -))) 1357 1357 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]] 1358 1358 1359 1359 1360 -== 6.3 How many RS485-Slave can RS485-BL connects? == 1120 +1. 1121 +11. How to change the LoRa Frequency Bands/Region? 1361 1361 1362 -((( 1363 -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"]]. 1364 -))) 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. 1365 1365 1366 1366 1367 1367 1368 -= 7. Trouble Shooting = 1127 +1. 1128 +11. How many RS485-Slave can RS485-BL connects? 1369 1369 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]]. 1370 1370 1371 -== 7.1 Downlink doesn’t work, how to solve it? == 1372 1372 1373 -Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]] 1374 1374 1375 1375 1376 -== 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? 1377 1377 1378 - 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: 1379 1379 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]] 1380 1380 1381 -= 8. Order Info = 1382 1382 1383 -(% style="color:blue" %)**Part Number: RS485-BL-XXX** 1384 1384 1385 -(% style="color:blue" %)**XXX:** 1144 +1. 1145 +11. Why I can’t join TTN V3 in US915 /AU915 bands? 1386 1386 1387 -* (% style="color:blue" %)**EU433**(%%): frequency bands EU433 1388 -* (% style="color:blue" %)**EU868**(%%): frequency bands EU868 1389 -* (% style="color:blue" %)**KR920**(%%): frequency bands KR920 1390 -* (% style="color:blue" %)**CN470**(%%): frequency bands CN470 1391 -* (% style="color:blue" %)**AS923**(%%): frequency bands AS923 1392 -* (% style="color:blue" %)**AU915**(%%): frequency bands AU915 1393 -* (% style="color:blue" %)**US915**(%%): frequency bands US915 1394 -* (% style="color:blue" %)**IN865**(%%): frequency bands IN865 1395 -* (% style="color:blue" %)**RU864**(%%): frequency bands RU864 1396 -* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865 1147 +It might about the channels mapping. Please see for detail. 1397 1397 1398 -= 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]] 1399 1399 1400 -((( 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 + 1401 1401 **Package Includes**: 1402 -))) 1403 1403 1404 -* ((( 1405 -RS485-BL x 1 1406 -))) 1407 -* ((( 1408 -Stick Antenna for LoRa RF part x 1 1409 -))) 1410 -* ((( 1411 -Program cable x 1 1412 -))) 1174 +* RS485-BL x 1 1175 +* Stick Antenna for LoRa RF part x 1 1176 +* Program cable x 1 1413 1413 1414 -((( 1415 1415 **Dimension and weight**: 1416 -))) 1417 1417 1418 -* ((( 1419 -Device Size: 13.5 x 7 x 3 cm 1420 -))) 1421 -* ((( 1422 -Device Weight: 105g 1423 -))) 1424 -* ((( 1425 -Package Size / pcs : 14.5 x 8 x 5 cm 1426 -))) 1427 -* ((( 1428 -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 1429 1429 1430 - 1431 -))) 1185 +1. Support 1432 1432 1433 -= 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 1434 1434 1435 -* ((( 1436 -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. 1437 -))) 1438 -* ((( 1439 -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]] 1440 -))) 1190 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
- 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-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