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