Summary

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

Details

Page properties

Content

...	...	@@ -501,33 +501,35 @@
501	501
502	502	== 3.4 Uplink Payload ==
503	503
504		-(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
505		-|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
506		-|Value|(% style="width:120px" %)(((
507		-Battery(mV)
508	508
509		-&
	505	+[[image:image-20220606110929-1.png]]
510	510
511		-Interrupt _Flag
512		-)))|(% style="width:116px" %)(((
513		-PAYLOAD_VER
514		-
515		-
516		-)))|(% style="width:386px" %)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.
517		-
518	518	Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
519	519
520	520
521	521	== 3.5 Configure RS485-BL via AT or Downlink ==
522	522
	512	+(((
523	523	User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
	514	+)))
524	524
	516	+(((
525	525	There are two kinds of Commands:
	518	+)))
526	526
527		-* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
	520	+* (((
	521	+(% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
	522	+)))
528	528
529		-* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
	524	+* (((
	525	+(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
	526	+)))
530	530
	528	+(((
	529	+
	530	+)))
	531	+
	532	+
531	531	=== 3.5.1 Common Commands ===
532	532
533	533	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: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
...	...	@@ -548,58 +548,121 @@
548	548
549	549	==== **RS485 Debug Command** ====
550	550
	553	+(((
551	551	This command is used to configure the RS485 devices; they won’t be used during sampling.
	555	+)))
552	552
553		-* **AT Command**
	557	+* (((
	558	+**AT Command**
	559	+)))
554	554
555	555	(% class="box infomessage" %)
556	556	(((
	563	+(((
557	557	**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
558	558	)))
	566	+)))
559	559
	568	+(((
560	560	m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
	570	+)))
561	561
562		-* **Downlink Payload**
	572	+* (((
	573	+**Downlink Payload**
	574	+)))
563	563
	576	+(((
564	564	Format: A8 MM NN XX XX XX XX YY
	578	+)))
565	565
	580	+(((
566	566	Where:
	582	+)))
567	567
568		-* MM: 1: add CRC-16/MODBUS ; 0: no CRC
569		-* NN: The length of RS485 command
570		-* XX XX XX XX: RS485 command total NN bytes
571		-* YY: How many bytes will be uplink from the return of this RS485 command,
572		-** if YY=0, RS485-LN will execute the downlink command without uplink;
573		-** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
574		-** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
	584	+* (((
	585	+MM: 1: add CRC-16/MODBUS ; 0: no CRC
	586	+)))
	587	+* (((
	588	+NN: The length of RS485 command
	589	+)))
	590	+* (((
	591	+XX XX XX XX: RS485 command total NN bytes
	592	+)))
	593	+* (((
	594	+(((
	595	+YY: How many bytes will be uplink from the return of this RS485 command,
	596	+)))
575	575
	598	+* (((
	599	+if YY=0, RS485-LN will execute the downlink command without uplink;
	600	+)))
	601	+* (((
	602	+if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
	603	+)))
	604	+* (((
	605	+if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
	606	+)))
	607	+)))
	608	+
	609	+(((
576	576	**Example 1** ~-~-> Configure without ask for uplink (YY=0)
	611	+)))
577	577
	613	+(((
578	578	To connect a Modbus Alarm with below commands.
	615	+)))
579	579
580		-* The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
	617	+* (((
	618	+The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
	619	+)))
581	581
582		-* The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
	621	+* (((
	622	+The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
	623	+)))
583	583
	625	+(((
584	584	So if user want to use downlink command to control to RS485 Alarm, he can use:
	627	+)))
585	585
	629	+(((
586	586	(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
	631	+)))
587	587
	633	+(((
588	588	(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
	635	+)))
589	589
	637	+(((
590	590	A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.
	639	+)))
591	591
	641	+(((
	642	+
	643	+)))
592	592
	645	+(((
593	593	**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
	647	+)))
594	594
	649	+(((
595	595	User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
	651	+)))
596	596
	653	+(((
	654	+
	655	+)))
597	597
	657	+(((
598	598	RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is:
	659	+)))
599	599
	661	+(((
600	600	**A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
	663	+)))
601	601
	665	+(((
602	602	[[image:1654159460680-153.png]]
	667	+)))
603	603
604	604
605	605

image-20220606110929-1.png

Author

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

Size

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

Content