Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 35.2 >
edited by Xiaoling
on 2022/06/02 15:44
To version < 32.14 >
edited by Xiaoling
on 2022/06/02 15:26
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -222,8 +222,6 @@
222 222  
223 223  (((
224 224  (% style="color:red" %)Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1
225 -
226 -
227 227  )))
228 228  )))
229 229  
... ... @@ -231,19 +231,19 @@
231 231  
232 232  To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are:
233 233  
234 -(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
235 -|(% style="width:128px" %)(((
232 +(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
233 +|(((
236 236  **AT Commands**
237 -)))|(% style="width:305px" %)(((
235 +)))|(% style="width:285px" %)(((
238 238  **Description**
239 -)))|(% style="width:346px" %)(((
237 +)))|(% style="width:347px" %)(((
240 240  **Example**
241 241  )))
242 -|(% style="width:128px" %)(((
240 +|(((
243 243  AT+BAUDR
244 -)))|(% style="width:305px" %)(((
242 +)))|(% style="width:285px" %)(((
245 245  Set the baud rate (for RS485 connection). Default Value is: 9600.
246 -)))|(% style="width:346px" %)(((
244 +)))|(% style="width:347px" %)(((
247 247  (((
248 248  AT+BAUDR=9600
249 249  )))
... ... @@ -252,11 +252,11 @@
252 252  Options: (1200,2400,4800,14400,19200,115200)
253 253  )))
254 254  )))
255 -|(% style="width:128px" %)(((
253 +|(((
256 256  AT+PARITY
257 -)))|(% style="width:305px" %)(((
255 +)))|(% style="width:285px" %)(((
258 258  Set UART parity (for RS485 connection)
259 -)))|(% style="width:346px" %)(((
257 +)))|(% style="width:347px" %)(((
260 260  (((
261 261  AT+PARITY=0
262 262  )))
... ... @@ -265,9 +265,9 @@
265 265  Option: 0: no parity, 1: odd parity, 2: even parity
266 266  )))
267 267  )))
268 -|(% style="width:128px" %)(((
266 +|(((
269 269  AT+STOPBIT
270 -)))|(% style="width:305px" %)(((
268 +)))|(% style="width:285px" %)(((
271 271  (((
272 272  Set serial stopbit (for RS485 connection)
273 273  )))
... ... @@ -275,7 +275,7 @@
275 275  (((
276 276  
277 277  )))
278 -)))|(% style="width:346px" %)(((
276 +)))|(% style="width:347px" %)(((
279 279  (((
280 280  AT+STOPBIT=0 for 1bit
281 281  )))
... ... @@ -289,8 +289,6 @@
289 289  )))
290 290  )))
291 291  
292 -
293 -
294 294  === 3.3.2 Configure sensors ===
295 295  
296 296  (((
... ... @@ -309,41 +309,80 @@
309 309  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
310 310  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
311 311  
312 -
313 -
314 314  === 3.3.3 Configure read commands for each sampling ===
315 315  
316 316  (((
317 -During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload.
311 +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.
312 +)))
318 318  
314 +(((
315 +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.
316 +)))
317 +
318 +(((
319 319  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
320 +)))
320 320  
322 +(((
321 321  This section describes how to achieve above goals.
324 +)))
322 322  
323 -During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
326 +(((
327 +During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
328 +)))
324 324  
330 +(((
331 +**Command from RS485-BL to Sensor:**
332 +)))
325 325  
326 -**Each RS485 commands include two parts:**
334 +(((
335 +RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
336 +)))
327 327  
328 -~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar.
338 +(((
339 +**Handle return from sensors to RS485-BL**:
340 +)))
329 329  
330 -2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar.
342 +(((
343 +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**
344 +)))
331 331  
332 -3. 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
346 +* (((
347 +**AT+DATACUT**
348 +)))
333 333  
334 -**AT+CMDDL1=1000** to send the open time to 1000ms
350 +(((
351 +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.
352 +)))
335 335  
354 +* (((
355 +**AT+SEARCH**
356 +)))
336 336  
358 +(((
359 +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.
360 +)))
361 +
362 +(((
363 +**Define wait timeout:**
364 +)))
365 +
366 +(((
367 +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
368 +)))
369 +
370 +(((
337 337  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
372 +)))
338 338  
374 +**Examples:**
339 339  
340 340  Below are examples for the how above AT Commands works.
341 341  
378 +**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
342 342  
343 -**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
344 -
345 -(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
346 -|(% style="width:496px" %)(((
380 +(% border="1" class="table-bordered" %)
381 +|(((
347 347  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
348 348  
349 349  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -351,40 +351,90 @@
351 351  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
352 352  )))
353 353  
389 +(((
354 354  For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.
391 +)))
355 355  
356 -In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
393 +(((
394 +In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
395 +)))
357 357  
397 +(((
398 +**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
399 +)))
358 358  
401 +(% border="1" class="table-bordered" %)
402 +|(((
403 +**AT+SEARCHx=aa,xx xx xx xx xx**
404 +
405 +* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
406 +* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
407 +
408 +
409 +)))
410 +
411 +**Examples:**
412 +
413 +~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
414 +
415 +If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
416 +
417 +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**
418 +
419 +[[image:1653269403619-508.png]]
420 +
421 +2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
422 +
423 +If we set AT+SEARCH1=2, 1E 56 34+31 00 49
424 +
425 +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**
426 +
427 +[[image:1653269438444-278.png]]
428 +
359 359  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
360 360  
361 -(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
362 -|(% style="width:722px" %)(((
431 +|(((
363 363  **AT+DATACUTx=a,b,c**
364 364  
365 365  * **a: length for the return of AT+COMMAND**
366 366  * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
367 -* **c: define the position for valid value. **
436 +* **c: define the position for valid value.  **
368 368  )))
369 369  
439 +Examples:
370 370  
371 -**Examples:**
372 -
373 373  * Grab bytes:
374 374  
375 -[[image:image-20220602153621-1.png]]
443 +[[image:1653269551753-223.png||height="311" width="717"]]
376 376  
377 -
378 378  * Grab a section.
379 379  
380 -[[image:image-20220602153621-2.png]]
447 +[[image:1653269568276-930.png||height="325" width="718"]]
381 381  
382 -
383 383  * Grab different sections.
384 384  
385 -[[image:image-20220602153621-3.png]]
386 -)))
451 +[[image:1653269593172-426.png||height="303" width="725"]]
387 387  
453 +(% style="color:red" %)**Note:**
454 +
455 +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.
456 +
457 +Example:
458 +
459 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
460 +
461 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
462 +
463 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
464 +
465 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
466 +
467 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
468 +
469 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
470 +
471 +[[image:1653269618463-608.png]]
472 +
388 388  === 3.3.4 Compose the uplink payload ===
389 389  
390 390  (((
image-20220602153621-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.4 KB
Content
image-20220602153621-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.2 KB
Content
image-20220602153621-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0