Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 15.1
edited by Xiaoling
on 2022/05/19 17:46
Change comment: Uploaded new attachment "1652953568895-172.png", version {1}
To version 29.4
edited by Xiaoling
on 2022/06/01 17:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,6 +7,7 @@
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 +
10 10  **Table of Contents:**
11 11  
12 12  
... ... @@ -13,6 +13,7 @@
13 13  
14 14  
15 15  
17 +
16 16  = 1.Introduction =
17 17  
18 18  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
... ... @@ -167,204 +167,238 @@
167 167  
168 168  [[image:1652953414711-647.png||height="337" width="723"]]
169 169  
170 -
172 +(((
171 171  The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
174 +)))
172 172  
173 -
176 +(((
174 174  The LG308 is already set to connect to [[TTN V3 network >>url:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
178 +)))
175 175  
180 +(((
176 176  **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
182 +)))
177 177  
184 +(((
178 178  Each RS485-BL is shipped with a sticker with unique device EUI:
186 +)))
179 179  
180 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
188 +[[image:1652953462722-299.png]]
181 181  
182 -
183 -
184 -
190 +(((
185 185  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
192 +)))
186 186  
194 +(((
187 187  Add APP EUI in the application.
196 +)))
188 188  
189 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
190 190  
191 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
192 192  
193 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
194 194  
195 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
201 +[[image:image-20220519174512-1.png]]
196 196  
203 +[[image:image-20220519174512-2.png||height="328" width="731"]]
197 197  
205 +[[image:image-20220519174512-3.png||height="556" width="724"]]
198 198  
207 +[[image:image-20220519174512-4.png]]
199 199  
200 -
201 -
202 -
203 -
204 -
205 -
206 -
207 -
208 -
209 -
210 -
211 -
212 -
213 213  You can also choose to create the device manually.
214 214  
215 -|(((
216 -
217 -)))
211 +[[image:1652953542269-423.png||height="710" width="723"]]
218 218  
219 -
220 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
221 -
222 222  Add APP KEY and DEV EUI
223 223  
224 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
215 +[[image:1652953553383-907.png||height="514" width="724"]]
225 225  
226 226  
218 +(((
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.
220 +)))
228 228  
229 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
222 +[[image:1652953568895-172.png||height="232" width="724"]]
230 230  
224 +== 3.3 Configure Commands to read data ==
231 231  
232 -
233 -
234 -1.
235 -11. Configure Commands to read data
236 -
226 +(((
237 237  There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
228 +)))
238 238  
230 +=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
239 239  
240 -1.
241 -11.
242 -111. Configure UART settings for RS485 or TTL communication
243 -
244 244  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
245 245  
246 -1. RS485-MODBUS mode:
234 +**~1. RS485-MODBUS mode:**
247 247  
248 248  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
249 249  
238 +**2. TTL mode:**
250 250  
251 -1. TTL mode:
252 -
253 253  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
254 254  
255 -
256 256  RS485-BL default UART settings is **9600, no parity, stop bit 1**. If the sensor has a different settings, user can change the RS485-BL setting to match.
257 257  
258 -
259 -|**AT Commands**|**Description**|**Example**
260 -|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
244 +(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
245 +|(((
246 +**AT Commands**
247 +)))|(% style="width:285px" %)(((
248 +**Description**
249 +)))|(% style="width:347px" %)(((
250 +**Example**
251 +)))
252 +|(((
253 +AT+BAUDR
254 +)))|(% style="width:285px" %)(((
255 +Set the baud rate (for RS485 connection). Default Value is: 9600.
256 +)))|(% style="width:347px" %)(((
257 +(((
261 261  AT+BAUDR=9600
259 +)))
262 262  
261 +(((
263 263  Options: (1200,2400,4800,14400,19200,115200)
264 264  )))
265 -|AT+PARITY|(((
264 +)))
265 +|(((
266 +AT+PARITY
267 +)))|(% style="width:285px" %)(((
268 +(((
266 266  Set UART parity (for RS485 connection)
270 +)))
267 267  
272 +(((
268 268  Default Value is: no parity.
269 -)))|(((
274 +)))
275 +)))|(% style="width:347px" %)(((
276 +(((
270 270  AT+PARITY=0
278 +)))
271 271  
280 +(((
272 272  Option: 0: no parity, 1: odd parity, 2: even parity
273 273  )))
274 -|AT+STOPBIT|(((
283 +)))
284 +|(((
285 +AT+STOPBIT
286 +)))|(% style="width:285px" %)(((
287 +(((
275 275  Set serial stopbit (for RS485 connection)
289 +)))
276 276  
291 +(((
277 277  Default Value is: 1bit.
278 -)))|(((
293 +)))
294 +)))|(% style="width:347px" %)(((
295 +(((
279 279  AT+STOPBIT=0 for 1bit
297 +)))
280 280  
299 +(((
281 281  AT+STOPBIT=1 for 1.5 bit
301 +)))
282 282  
303 +(((
283 283  AT+STOPBIT=2 for 2 bits
284 284  )))
306 +)))
285 285  
308 +=== 3.3.2 Configure sensors ===
286 286  
310 +(((
311 +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**.
312 +)))
287 287  
314 +(((
315 +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.
316 +)))
288 288  
289 -1.
290 -11.
291 -111. Configure sensors
292 -
293 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
294 -
295 -
296 -When user issue an AT+CFGDEV command, Each AT+CFGDEV equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
297 -
298 -|**AT Commands**|**Description**|**Example**
299 -|AT+CFGDEV|(((
318 +(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
319 +|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
320 +|AT+CFGDEV|(% style="width:418px" %)(((
300 300  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
301 301  
302 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
323 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
303 303  
304 -m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
305 -)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
325 +mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
326 +)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
306 306  
307 307  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
308 308  
330 +=== 3.3.3 Configure read commands for each sampling ===
309 309  
310 -
311 -
312 -
313 -1.
314 -11.
315 -111. Configure read commands for each sampling
316 -
332 +(((
317 317  RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink.
334 +)))
318 318  
319 -
336 +(((
320 320  During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload.
338 +)))
321 321  
322 -
340 +(((
323 323  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
342 +)))
324 324  
325 -
344 +(((
326 326  This section describes how to achieve above goals.
346 +)))
327 327  
328 -
348 +(((
329 329  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
350 +)))
330 330  
331 -
352 +(((
332 332  **Command from RS485-BL to Sensor:**
354 +)))
333 333  
356 +(((
334 334  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
358 +)))
335 335  
336 -
360 +(((
337 337  **Handle return from sensors to RS485-BL**:
362 +)))
338 338  
364 +(((
339 339  After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands**
366 +)))
340 340  
368 +* (((
369 +**AT+DATACUT**
370 +)))
341 341  
342 -* **AT+DATACUT**
343 -
372 +(((
344 344  When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.
374 +)))
345 345  
376 +* (((
377 +**AT+SEARCH**
378 +)))
346 346  
347 -* **AT+SEARCH**
348 -
380 +(((
349 349  When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string.
382 +)))
350 350  
351 -
384 +(((
352 352  **Define wait timeout:**
386 +)))
353 353  
388 +(((
354 354  Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example, AT+CMDDL1=1000 to send the open time to 1000ms
390 +)))
355 355  
356 -
392 +(((
357 357  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
394 +)))
358 358  
359 -
360 360  **Examples:**
361 361  
362 362  Below are examples for the how above AT Commands works.
363 363  
364 -
365 365  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
366 366  
367 -|(((
402 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
403 +|(% style="width:498px" %)(((
368 368  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
369 369  
370 370  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -376,41 +376,38 @@
376 376  
377 377  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
378 378  
379 -
380 380  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
381 381  
382 -|(((
417 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
418 +|(% style="width:577px" %)(((
383 383  **AT+SEARCHx=aa,xx xx xx xx xx**
384 384  
385 385  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
386 386  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
387 -
388 -
389 389  )))
390 390  
391 -Examples:
425 +**Examples:**
392 392  
393 393  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
394 394  
395 395  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
396 396  
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
431 +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**
398 398  
399 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
433 +[[image:1653271044481-711.png]]
400 400  
401 -
402 402  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
403 403  
404 404  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
405 405  
406 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
439 +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**
407 407  
408 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
441 +[[image:1653271276735-972.png]]
409 409  
410 -
411 411  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
412 412  
413 -|(((
445 +(% style="background-color:#4f81bd; color:white; width:729px" %)
446 +|(% style="width:726px" %)(((
414 414  **AT+DATACUTx=a,b,c**
415 415  
416 416  * **a: length for the return of AT+COMMAND**
... ... @@ -422,95 +422,130 @@
422 422  
423 423  * Grab bytes:
424 424  
425 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
458 +[[image:1653271581490-837.png||height="313" width="722"]]
426 426  
427 427  * Grab a section.
428 428  
429 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
462 +[[image:1653271648378-342.png||height="326" width="720"]]
430 430  
431 431  * Grab different sections.
432 432  
433 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
466 +[[image:1653271657255-576.png||height="305" width="730"]]
434 434  
468 +(((
469 +(% style="color:red" %)**Note:**
470 +)))
435 435  
436 -Note:
437 -
472 +(((
438 438  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.
474 +)))
439 439  
440 -Example:
476 +(((
477 +**Example:**
478 +)))
441 441  
442 -AT+COMMAND1=11 01 1E D0,0
480 +(((
481 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
482 +)))
443 443  
444 -AT+SEARCH1=1,1E 56 34
484 +(((
485 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
486 +)))
445 445  
446 -AT+DATACUT1=0,2,1~~5
488 +(((
489 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
490 +)))
447 447  
448 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
492 +(((
493 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
494 +)))
449 449  
450 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
496 +(((
497 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
498 +)))
451 451  
452 -Valid payload after DataCUT command: 2e 30 58 5f 36
500 +(((
501 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
502 +)))
453 453  
454 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
504 +[[image:1653271763403-806.png]]
455 455  
506 +=== 3.3.4 Compose the uplink payload ===
456 456  
457 -
458 -
459 -1.
460 -11.
461 -111. Compose the uplink payload
462 -
508 +(((
463 463  Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.**
510 +)))
464 464  
512 +(((
513 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
514 +)))
465 465  
466 -**Examples: AT+DATAUP=0**
516 +(((
517 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
518 +)))
467 467  
468 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
469 -
520 +(((
470 470  Final Payload is
522 +)))
471 471  
472 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
524 +(((
525 +(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
526 +)))
473 473  
528 +(((
474 474  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
530 +)))
475 475  
476 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
532 +[[image:1653272787040-634.png||height="515" width="719"]]
477 477  
534 +(((
535 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
536 +)))
478 478  
538 +(((
539 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
540 +)))
479 479  
480 -**Examples: AT+DATAUP=1**
481 -
482 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
483 -
542 +(((
484 484  Final Payload is
544 +)))
485 485  
486 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
546 +(((
547 +(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
548 +)))
487 487  
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
550 +1. (((
551 +Battery Info (2 bytes): Battery voltage
552 +)))
553 +1. (((
554 +PAYVER (1 byte): Defined by AT+PAYVER
555 +)))
556 +1. (((
557 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
558 +)))
559 +1. (((
560 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
561 +)))
562 +1. (((
563 +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
564 +)))
493 493  
494 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
566 +[[image:1653272817147-600.png||height="437" width="717"]]
495 495  
496 -
497 497  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
498 498  
499 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
570 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
500 500  
501 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
572 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
502 502  
503 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
574 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
504 504  
505 -
506 -
507 507  Below are the uplink payloads:
508 508  
509 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
578 +[[image:1653272901032-107.png]]
510 510  
580 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
511 511  
512 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
513 -
514 514   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
515 515  
516 516   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -519,90 +519,121 @@
519 519  
520 520   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
521 521  
590 +=== 3.3.5 Uplink on demand ===
522 522  
523 -
524 -1.
525 -11.
526 -111. Uplink on demand
527 -
592 +(((
528 528  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.
594 +)))
529 529  
596 +(((
530 530  Downlink control command:
598 +)))
531 531  
532 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
600 +(((
601 +**0x08 command**: Poll an uplink with current command set in RS485-BL.
602 +)))
533 533  
534 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
604 +(((
605 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
606 +)))
535 535  
608 +=== 3.3.6 Uplink on Interrupt ===
536 536  
610 +Put the interrupt sensor between 3.3v_out and GPIO ext.
537 537  
538 -1.
539 -11.
540 -111. Uplink on Interrupt
612 +[[image:1653273818896-432.png]]
541 541  
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]]
543 -
614 +(((
544 544  AT+INTMOD=0  Disable Interrupt
616 +)))
545 545  
618 +(((
546 546  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
620 +)))
547 547  
622 +(((
548 548  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
624 +)))
549 549  
626 +(((
550 550  AT+INTMOD=3  Interrupt trigger by rising edge.
628 +)))
551 551  
630 +== 3.4 Uplink Payload ==
552 552  
553 -1.
554 -11. Uplink Payload
555 -
556 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
557 -|Value|(((
632 +(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
633 +|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
634 +|Value|(% style="width:130px" %)(((
635 +(((
558 558  Battery(mV)
637 +)))
559 559  
639 +(((
560 560  &
641 +)))
561 561  
643 +(((
562 562  Interrupt _Flag
563 -)))|(((
645 +)))
646 +)))|(% style="width:93px" %)(((
564 564  PAYLOAD_VER
565 565  
566 566  
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.
650 +)))|(% 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.
568 568  
569 569  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
570 570  
571 -
654 +(((
572 572  function Decoder(bytes, port) {
656 +)))
573 573  
658 +(((
574 574  ~/~/Payload Formats of RS485-BL Deceive
660 +)))
575 575  
662 +(((
576 576  return {
664 +)))
577 577  
666 +(((
578 578   ~/~/Battery,units:V
668 +)))
579 579  
670 +(((
580 580   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
672 +)))
581 581  
674 +(((
582 582   ~/~/GPIO_EXTI 
676 +)))
583 583  
678 +(((
584 584   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
680 +)))
585 585  
682 +(((
586 586   ~/~/payload of version
684 +)))
587 587  
686 +(((
588 588   Pay_ver:bytes[2],
688 +)))
589 589  
690 +(((
590 590   };
692 +)))
591 591  
694 +(((
592 592   }
696 +)))
593 593  
594 -
595 -
596 -
597 -
598 -
599 -
698 +(((
600 600  TTN V3 uplink screen shot.
700 +)))
601 601  
602 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
702 +[[image:1653274001211-372.png||height="192" width="732"]]
603 603  
604 -1.
605 -11. Configure RS485-BL via AT or Downlink
704 +== 3.5 Configure RS485-BL via AT or Downlink ==
606 606  
607 607  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
608 608  
1652954654347-831.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653271044481-711.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.8 KB
Content
1653271276735-972.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.6 KB
Content
1653271581490-837.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653271648378-342.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653271657255-576.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653271763403-806.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653272787040-634.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content
1653272817147-600.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
1653272901032-107.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content
1653273818896-432.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.6 KB
Content
1653274001211-372.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.4 KB
Content