Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 28.3
edited by Xiaoling
on 2022/05/23 10:46
Change comment: There is no comment for this version
To version 15.4
edited by Xiaoling
on 2022/05/19 17:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -60,7 +60,7 @@
60 60  * Power Consumption (exclude RS485 device):
61 61  ** Idle: 6uA@3.3v
62 62  
63 -*
63 +*
64 64  ** 20dB Transmit: 130mA@3.3v
65 65  
66 66  **Interface for Model:**
... ... @@ -219,186 +219,143 @@
219 219  
220 220  [[image:1652953568895-172.png||height="232" width="724"]]
221 221  
222 -== 3.3 Configure Commands to read data ==
223 223  
224 -(((
223 +
224 +
225 +1.
226 +11. Configure Commands to read data
227 +
225 225  There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
226 -)))
227 227  
228 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
229 229  
231 +1.
232 +11.
233 +111. Configure UART settings for RS485 or TTL communication
234 +
230 230  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
231 231  
232 -**~1. RS485-MODBUS mode:**
237 +1. RS485-MODBUS mode:
233 233  
234 234  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
235 235  
236 -**2. TTL mode:**
237 237  
242 +1. TTL mode:
243 +
238 238  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
239 239  
246 +
240 240  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.
241 241  
242 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
243 -|(((
244 -**AT Commands**
245 -)))|(% style="width:285px" %)(((
246 -**Description**
247 -)))|(% style="width:347px" %)(((
248 -**Example**
249 -)))
250 -|(((
251 -AT+BAUDR
252 -)))|(% style="width:285px" %)(((
253 -Set the baud rate (for RS485 connection). Default Value is: 9600.
254 -)))|(% style="width:347px" %)(((
255 -(((
249 +
250 +|**AT Commands**|**Description**|**Example**
251 +|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
256 256  AT+BAUDR=9600
257 -)))
258 258  
259 -(((
260 260  Options: (1200,2400,4800,14400,19200,115200)
261 261  )))
262 -)))
263 -|(((
264 -AT+PARITY
265 -)))|(% style="width:285px" %)(((
266 -(((
256 +|AT+PARITY|(((
267 267  Set UART parity (for RS485 connection)
268 -)))
269 269  
270 -(((
271 271  Default Value is: no parity.
272 -)))
273 -)))|(% style="width:347px" %)(((
274 -(((
260 +)))|(((
275 275  AT+PARITY=0
276 -)))
277 277  
278 -(((
279 279  Option: 0: no parity, 1: odd parity, 2: even parity
280 280  )))
281 -)))
282 -|(((
283 -AT+STOPBIT
284 -)))|(% style="width:285px" %)(((
285 -(((
265 +|AT+STOPBIT|(((
286 286  Set serial stopbit (for RS485 connection)
287 -)))
288 288  
289 -(((
290 290  Default Value is: 1bit.
291 -)))
292 -)))|(% style="width:347px" %)(((
293 -(((
269 +)))|(((
294 294  AT+STOPBIT=0 for 1bit
295 -)))
296 296  
297 -(((
298 298  AT+STOPBIT=1 for 1.5 bit
299 -)))
300 300  
301 -(((
302 302  AT+STOPBIT=2 for 2 bits
303 303  )))
304 -)))
305 305  
306 -=== 3.3.2 Configure sensors ===
307 307  
308 -(((
309 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**.
310 -)))
311 311  
312 -(((
313 -When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
314 -)))
315 315  
316 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
317 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
318 -|AT+CFGDEV|(% style="width:418px" %)(((
280 +1.
281 +11.
282 +111. Configure sensors
283 +
284 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
285 +
286 +
287 +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.
288 +
289 +|**AT Commands**|**Description**|**Example**
290 +|AT+CFGDEV|(((
319 319  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
320 320  
321 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
293 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
322 322  
323 -mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
324 -)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
295 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
296 +)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
325 325  
326 326  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
327 327  
328 -=== 3.3.3 Configure read commands for each sampling ===
329 329  
330 -(((
301 +
302 +
303 +
304 +1.
305 +11.
306 +111. Configure read commands for each sampling
307 +
331 331  RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink.
332 -)))
333 333  
334 -(((
310 +
335 335  During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload.
336 -)))
337 337  
338 -(((
313 +
339 339  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
340 -)))
341 341  
342 -(((
316 +
343 343  This section describes how to achieve above goals.
344 -)))
345 345  
346 -(((
319 +
347 347  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
348 -)))
349 349  
350 -(((
322 +
351 351  **Command from RS485-BL to Sensor:**
352 -)))
353 353  
354 -(((
355 355  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
356 -)))
357 357  
358 -(((
327 +
359 359  **Handle return from sensors to RS485-BL**:
360 -)))
361 361  
362 -(((
363 363  After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands**
364 -)))
365 365  
366 -* (((
367 -**AT+DATACUT**
368 -)))
369 369  
370 -(((
333 +* **AT+DATACUT**
334 +
371 371  When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.
372 -)))
373 373  
374 -* (((
375 -**AT+SEARCH**
376 -)))
377 377  
378 -(((
338 +* **AT+SEARCH**
339 +
379 379  When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string.
380 -)))
381 381  
382 -(((
342 +
383 383  **Define wait timeout:**
384 -)))
385 385  
386 -(((
387 387  Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example, AT+CMDDL1=1000 to send the open time to 1000ms
388 -)))
389 389  
390 -(((
347 +
391 391  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
392 -)))
393 393  
350 +
394 394  **Examples:**
395 395  
396 396  Below are examples for the how above AT Commands works.
397 397  
355 +
398 398  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
399 399  
400 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
401 -|(% style="width:498px" %)(((
358 +|(((
402 402  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
403 403  
404 404  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -410,38 +410,41 @@
410 410  
411 411  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
412 412  
370 +
413 413  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
414 414  
415 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
416 -|(% style="width:577px" %)(((
373 +|(((
417 417  **AT+SEARCHx=aa,xx xx xx xx xx**
418 418  
419 419  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
420 420  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
378 +
379 +
421 421  )))
422 422  
423 -**Examples:**
382 +Examples:
424 424  
425 425  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
426 426  
427 427  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
428 428  
429 -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**
388 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
430 430  
431 -[[image:1653271044481-711.png]]
390 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
432 432  
392 +
433 433  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
434 434  
435 435  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
436 436  
437 -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**
397 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
438 438  
439 -[[image:1653271276735-972.png]]
399 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
440 440  
401 +
441 441  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
442 442  
443 -(% style="background-color:#4f81bd; color:white; width:729px" %)
444 -|(% style="width:726px" %)(((
404 +|(((
445 445  **AT+DATACUTx=a,b,c**
446 446  
447 447  * **a: length for the return of AT+COMMAND**
... ... @@ -453,130 +453,95 @@
453 453  
454 454  * Grab bytes:
455 455  
456 -[[image:1653271581490-837.png||height="313" width="722"]]
416 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
457 457  
458 458  * Grab a section.
459 459  
460 -[[image:1653271648378-342.png||height="326" width="720"]]
420 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
461 461  
462 462  * Grab different sections.
463 463  
464 -[[image:1653271657255-576.png||height="305" width="730"]]
424 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
465 465  
466 -(((
467 -(% style="color:red" %)**Note:**
468 -)))
469 469  
470 -(((
427 +Note:
428 +
471 471  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.
472 -)))
473 473  
474 -(((
475 -**Example:**
476 -)))
431 +Example:
477 477  
478 -(((
479 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
480 -)))
433 +AT+COMMAND1=11 01 1E D0,0
481 481  
482 -(((
483 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
484 -)))
435 +AT+SEARCH1=1,1E 56 34
485 485  
486 -(((
487 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
488 -)))
437 +AT+DATACUT1=0,2,1~~5
489 489  
490 -(((
491 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
492 -)))
439 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
493 493  
494 -(((
495 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
496 -)))
441 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
497 497  
498 -(((
499 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
500 -)))
443 +Valid payload after DataCUT command: 2e 30 58 5f 36
501 501  
502 -[[image:1653271763403-806.png]]
445 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
503 503  
504 -=== 3.3.4 Compose the uplink payload ===
505 505  
506 -(((
448 +
449 +
450 +1.
451 +11.
452 +111. Compose the uplink payload
453 +
507 507  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.**
508 -)))
509 509  
510 -(((
511 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
512 -)))
513 513  
514 -(((
515 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
516 -)))
457 +**Examples: AT+DATAUP=0**
517 517  
518 -(((
459 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
460 +
519 519  Final Payload is
520 -)))
521 521  
522 -(((
523 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
524 -)))
463 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
525 525  
526 -(((
527 527  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
528 -)))
529 529  
530 -[[image:1653272787040-634.png||height="515" width="719"]]
467 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
531 531  
532 -(((
533 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
534 -)))
535 535  
536 -(((
537 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
538 -)))
539 539  
540 -(((
471 +**Examples: AT+DATAUP=1**
472 +
473 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
474 +
541 541  Final Payload is
542 -)))
543 543  
544 -(((
545 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
546 -)))
477 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
547 547  
548 -1. (((
549 -Battery Info (2 bytes): Battery voltage
550 -)))
551 -1. (((
552 -PAYVER (1 byte): Defined by AT+PAYVER
553 -)))
554 -1. (((
555 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
556 -)))
557 -1. (((
558 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
559 -)))
560 -1. (((
561 -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
562 -)))
479 +1. Battery Info (2 bytes): Battery voltage
480 +1. PAYVER (1 byte): Defined by AT+PAYVER
481 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
482 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
483 +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
563 563  
564 -[[image:1653272817147-600.png||height="437" width="717"]]
485 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
565 565  
487 +
566 566  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
567 567  
568 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
490 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
569 569  
570 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
492 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
571 571  
572 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
494 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
573 573  
496 +
497 +
574 574  Below are the uplink payloads:
575 575  
576 -[[image:1653272901032-107.png]]
500 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
577 577  
578 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
579 579  
503 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
504 +
580 580   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
581 581  
582 582   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -585,30 +585,28 @@
585 585  
586 586   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
587 587  
588 -=== 3.3.5 Uplink on demand ===
589 589  
590 -(((
514 +
515 +1.
516 +11.
517 +111. Uplink on demand
518 +
591 591  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.
592 -)))
593 593  
594 -(((
595 595  Downlink control command:
596 -)))
597 597  
598 -(((
599 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
600 -)))
523 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
601 601  
602 -(((
603 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
604 -)))
525 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
605 605  
606 -=== 3.3.6 Uplink on Interrupt ===
607 607  
608 -Put the interrupt sensor between 3.3v_out and GPIO ext.
609 609  
610 -[[image:1653273818896-432.png]]
529 +1.
530 +11.
531 +111. Uplink on Interrupt
611 611  
533 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
534 +
612 612  AT+INTMOD=0  Disable Interrupt
613 613  
614 614  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
... ... @@ -617,27 +617,22 @@
617 617  
618 618  AT+INTMOD=3  Interrupt trigger by rising edge.
619 619  
620 -== 3.4 Uplink Payload ==
621 621  
622 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
623 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
624 -|Value|(% style="width:130px" %)(((
625 -(((
544 +1.
545 +11. Uplink Payload
546 +
547 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
548 +|Value|(((
626 626  Battery(mV)
627 -)))
628 628  
629 -(((
630 630  &
631 -)))
632 632  
633 -(((
634 634  Interrupt _Flag
635 -)))
636 -)))|(% style="width:93px" %)(((
554 +)))|(((
637 637  PAYLOAD_VER
638 638  
639 639  
640 -)))|(% 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.
558 +)))|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.
641 641  
642 642  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
643 643  
... ... @@ -685,15 +685,15 @@
685 685  
686 686  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
687 687  
688 -1.
689 -11.
606 +1.
607 +11.
690 690  111. Common Commands:
691 691  
692 692  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]]
693 693  
694 694  
695 -1.
696 -11.
613 +1.
614 +11.
697 697  111. Sensor related commands:
698 698  
699 699  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -999,13 +999,13 @@
999 999  
1000 1000  
1001 1001  
1002 -1.
920 +1.
1003 1003  11. Buttons
1004 1004  
1005 1005  |**Button**|**Feature**
1006 1006  |**RST**|Reboot RS485-BL
1007 1007  
1008 -1.
926 +1.
1009 1009  11. +3V3 Output
1010 1010  
1011 1011  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -1023,7 +1023,7 @@
1023 1023  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1024 1024  
1025 1025  
1026 -1.
944 +1.
1027 1027  11. +5V Output
1028 1028  
1029 1029  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -1043,13 +1043,13 @@
1043 1043  
1044 1044  
1045 1045  
1046 -1.
964 +1.
1047 1047  11. LEDs
1048 1048  
1049 1049  |**LEDs**|**Feature**
1050 1050  |**LED1**|Blink when device transmit a packet.
1051 1051  
1052 -1.
970 +1.
1053 1053  11. Switch Jumper
1054 1054  
1055 1055  |**Switch Jumper**|**Feature**
... ... @@ -1095,7 +1095,7 @@
1095 1095  
1096 1096  
1097 1097  
1098 -1.
1016 +1.
1099 1099  11. Common AT Command Sequence
1100 1100  111. Multi-channel ABP mode (Use with SX1301/LG308)
1101 1101  
... ... @@ -1114,8 +1114,8 @@
1114 1114  
1115 1115  ATZ
1116 1116  
1117 -1.
1118 -11.
1035 +1.
1036 +11.
1119 1119  111. Single-channel ABP mode (Use with LG01/LG02)
1120 1120  
1121 1121  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1190,7 +1190,7 @@
1190 1190  [[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]]
1191 1191  
1192 1192  
1193 -1.
1111 +1.
1194 1194  11. How to change the LoRa Frequency Bands/Region?
1195 1195  
1196 1196  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1197,7 +1197,7 @@
1197 1197  
1198 1198  
1199 1199  
1200 -1.
1118 +1.
1201 1201  11. How many RS485-Slave can RS485-BL connects?
1202 1202  
1203 1203  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]].
... ... @@ -1214,7 +1214,7 @@
1214 1214  
1215 1215  
1216 1216  
1217 -1.
1135 +1.
1218 1218  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1219 1219  
1220 1220  It might about the channels mapping. Please see for detail.
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