Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 3 added, 0 removed)
  • image-20220602153621-1.png
  • image-20220602153621-2.png
  • image-20220602153621-3.png

Details

Page properties

Content

...	...	@@ -212,6 +212,7 @@
212	212
213	213	[[image:1652953568895-172.png||height="232" width="724"]]
214	214
	215	+
215	215	== 3.3 Configure Commands to read data ==
216	216
217	217	(((
...	...	@@ -221,6 +221,8 @@
221	221
222	222	(((
223	223	(% 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	+
224	224	)))
225	225	)))
226	226
...	...	@@ -228,19 +228,19 @@
228	228
229	229	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:
230	230
231		-(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
232		-|(((
	234	+(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
	235	+|(% style="width:128px" %)(((
233	233	**AT Commands**
234		-)))|(% style="width:285px" %)(((
	237	+)))|(% style="width:305px" %)(((
235	235	**Description**
236		-)))|(% style="width:347px" %)(((
	239	+)))|(% style="width:346px" %)(((
237	237	**Example**
238	238	)))
239		-|(((
	242	+|(% style="width:128px" %)(((
240	240	AT+BAUDR
241		-)))|(% style="width:285px" %)(((
	244	+)))|(% style="width:305px" %)(((
242	242	Set the baud rate (for RS485 connection). Default Value is: 9600.
243		-)))|(% style="width:347px" %)(((
	246	+)))|(% style="width:346px" %)(((
244	244	(((
245	245	AT+BAUDR=9600
246	246	)))
...	...	@@ -249,11 +249,11 @@
249	249	Options: (1200,2400,4800,14400,19200,115200)
250	250	)))
251	251	)))
252		-|(((
	255	+|(% style="width:128px" %)(((
253	253	AT+PARITY
254		-)))|(% style="width:285px" %)(((
	257	+)))|(% style="width:305px" %)(((
255	255	Set UART parity (for RS485 connection)
256		-)))|(% style="width:347px" %)(((
	259	+)))|(% style="width:346px" %)(((
257	257	(((
258	258	AT+PARITY=0
259	259	)))
...	...	@@ -262,9 +262,9 @@
262	262	Option: 0: no parity, 1: odd parity, 2: even parity
263	263	)))
264	264	)))
265		-|(((
	268	+|(% style="width:128px" %)(((
266	266	AT+STOPBIT
267		-)))|(% style="width:285px" %)(((
	270	+)))|(% style="width:305px" %)(((
268	268	(((
269	269	Set serial stopbit (for RS485 connection)
270	270	)))
...	...	@@ -272,7 +272,7 @@
272	272	(((
273	273
274	274	)))
275		-)))|(% style="width:347px" %)(((
	278	+)))|(% style="width:346px" %)(((
276	276	(((
277	277	AT+STOPBIT=0 for 1bit
278	278	)))
...	...	@@ -286,6 +286,8 @@
286	286	)))
287	287	)))
288	288
	292	+
	293	+
289	289	=== 3.3.2 Configure sensors ===
290	290
291	291	(((
...	...	@@ -304,80 +304,41 @@
304	304	mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
305	305	)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
306	306
307		-=== 3.3.3 Configure read commands for each sampling ===
308	308
309		-(((
310		-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.
311		-)))
312	312
313		-(((
314		-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.
315		-)))
	314	+=== 3.3.3 Configure read commands for each sampling ===
316	316
317	317	(((
	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.
	318	+
318	318	To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
319		-)))
320	320
321		-(((
322	322	This section describes how to achieve above goals.
323		-)))
324	324
325		-(((
326		-During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
327		-)))
	323	+During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
328	328
329		-(((
330		-**Command from RS485-BL to Sensor:**
331		-)))
332	332
333		-(((
334		-RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
335		-)))
	326	+**Each RS485 commands include two parts:**
336	336
337		-(((
338		-**Handle return from sensors to RS485-BL**:
339		-)))
	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.
340	340
341		-(((
342		-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**
343		-)))
	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.
344	344
345		-* (((
346		-**AT+DATACUT**
347		-)))
	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
348	348
349		-(((
350		-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.
351		-)))
	334	+**AT+CMDDL1=1000** to send the open time to 1000ms
352	352
353		-* (((
354		-**AT+SEARCH**
355		-)))
356	356
357		-(((
358		-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.
359		-)))
360		-
361		-(((
362		-**Define wait timeout:**
363		-)))
364		-
365		-(((
366		-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
367		-)))
368		-
369		-(((
370	370	After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
371		-)))
372	372
373		-**Examples:**
374	374
375	375	Below are examples for the how above AT Commands works.
376	376
377		-**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
378	378
379		-(% border="1" class="table-bordered" %)
380		-|(((
	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" %)(((
381	381	**AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
382	382
383	383	**xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
...	...	@@ -385,90 +385,42 @@
385	385	**m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
386	386	)))
387	387
388		-(((
389	389	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.
390		-)))
391	391
392		-(((
393		-In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
394		-)))
	356	+In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
395	395
396		-(((
397		-**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
398		-)))
399	399
400		-(% border="1" class="table-bordered" %)
401		-|(((
402		-**AT+SEARCHx=aa,xx xx xx xx xx**
403		-
404		-* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
405		-* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
406		-
407		-
408		-)))
409		-
410		-**Examples:**
411		-
412		-~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
413		-
414		-If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
415		-
416		-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**
417		-
418		-[[image:1653269403619-508.png]]
419		-
420		-2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
421		-
422		-If we set AT+SEARCH1=2, 1E 56 34+31 00 49
423		-
424		-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**
425		-
426		-[[image:1653269438444-278.png]]
427		-
428	428	**AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
429	429
430		-|(((
	361	+(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
	362	+|(% style="width:722px" %)(((
431	431	**AT+DATACUTx=a,b,c**
432	432
433	433	* **a: length for the return of AT+COMMAND**
434	434	* **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
435		-* **c: define the position for valid value.  **
	367	+* **c: define the position for valid value. **
436	436	)))
437	437
438		-Examples:
439	439
	371	+**Examples:**
	372	+
440	440	* Grab bytes:
441	441
442		-[[image:1653269551753-223.png||height="311" width="717"]]
	375	+[[image:image-20220602153621-1.png]]
443	443
	377	+
444	444	* Grab a section.
445	445
446		-[[image:1653269568276-930.png||height="325" width="718"]]
	380	+[[image:image-20220602153621-2.png]]
447	447
	382	+
448	448	* Grab different sections.
449	449
450		-[[image:1653269593172-426.png||height="303" width="725"]]
	385	+[[image:image-20220602153621-3.png]]
451	451
452		-(% style="color:red" %)**Note:**
	387	+
	388	+)))
453	453
454		-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.
455		-
456		-Example:
457		-
458		-(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
459		-
460		-(% style="color:red" %)AT+SEARCH1=1,1E 56 34
461		-
462		-(% style="color:red" %)AT+DATACUT1=0,2,1~~5
463		-
464		-(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
465		-
466		-(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
467		-
468		-(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
469		-
470		-[[image:1653269618463-608.png]]
471		-
472	472	=== 3.3.4 Compose the uplink payload ===
473	473
474	474	(((

image-20220602153621-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+23.4 KB

Content

image-20220602153621-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+22.2 KB

Content

image-20220602153621-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+22.3 KB

Content