<
From version < 17.2 >
edited by Xiaoling
on 2022/05/19 18:05
To version < 15.5 >
edited by Xiaoling
on 2022/05/19 17:52
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -303,101 +303,87 @@
303 303  )))
304 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" %)(((
309 +1.
310 +11.
311 +111. Configure sensors
312 +
313 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
314 +
315 +
316 +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.
317 +
318 +|**AT Commands**|**Description**|**Example**
319 +|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,
322 +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
324 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
325 +)))|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 -(((
330 +
331 +
332 +
333 +1.
334 +11.
335 +111. Configure read commands for each sampling
336 +
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 -(((
339 +
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 -(((
342 +
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 -(((
345 +
343 343  This section describes how to achieve above goals.
344 -)))
345 345  
346 -(((
348 +
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 -(((
351 +
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 -(((
356 +
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 -(((
362 +* **AT+DATACUT**
363 +
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 -(((
367 +* **AT+SEARCH**
368 +
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 -(((
371 +
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 -(((
376 +
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  
379 +
394 394  **Examples:**
395 395  
396 396  Below are examples for the how above AT Commands works.
397 397  
384 +
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" %)
401 401  |(((
402 402  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
403 403  
... ... @@ -410,9 +410,9 @@
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  
399 +
413 413  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
414 414  
415 -(% border="1" class="table-bordered" %)
416 416  |(((
417 417  **AT+SEARCHx=aa,xx xx xx xx xx**
418 418  
... ... @@ -430,7 +430,7 @@
430 430  
431 431  The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
432 432  
433 -[[image:1652954654347-831.png]]
419 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
434 434  
435 435  
436 436  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
1652954654347-831.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0