Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -548,23 +548,23 @@
548	548
549	549	If user don't want to use DATACUT for some command, he simply want to uplink all returns. AT+ALLDATAMOD can be set to 1.
550	550
551		-**AT+ALLDATAMOD** will simply get all return and don't do CRC check as result for SDI-12 command. AT+DATACUTx command has higher priority, if AT+DATACUTx has been set, AT+ALLDATAMOD will be ignore for this SDI-12 command.
	551	+**(% style="color:blue" %)AT+ALLDATAMOD**(%%) will simply get all return and don't do CRC check as result for SDI-12 command. AT+DATACUTx command has higher priority, if AT+DATACUTx has been set, AT+ALLDATAMOD will be ignore for this SDI-12 command.
552	552
553	553
554		-**For example: ** as below photo, AT+ALLDATAMOD=1, but AT+DATACUT1 has been set, AT+DATACUT1 will be still effect the result.
	554	+**(% style="color:#4F81BD" %)For example: ** as below photo, AT+ALLDATAMOD=1, but AT+DATACUT1 has been set, AT+DATACUT1 will be still effect the result.
555	555
556	556
557	557	[[image:1675215782925-448.png]]
558	558
559	559
560		-If AT+ALLDATAMOD=1, **FX,X** will be added in the payload, FX specify which command is used and X specify the length of return. for example in above screen, F1 05 means the return is from AT+COMMAND1 and the return is 5 bytes.
	560	+If AT+ALLDATAMOD=1, **(% style="color:#4F81BD" %)FX,X**(%%) will be added in the payload, FX specify which command is used and X specify the length of return. for example in above screen, F1 05 means the return is from AT+COMMAND1 and the return is 5 bytes.
561	561
562	562
563	563
564		-**Compose Uplink**
	564	+**(% style="color:blue" %)Compose Uplink**
565	565
566	566
567		-**AT+DATAUP=0**
	567	+**(% style="color:#4F81BD" %)AT+DATAUP=0**
568	568
569	569	Compose the uplink payload with value returns in sequence and send with A SIGNLE UPLINK.
570	570
...	...	@@ -576,7 +576,7 @@
576	576	[[image:1675215828102-844.png]]
577	577
578	578
579		-**AT+DATAUP=1**
	579	+**(% style="color:#4F81BD" %)AT+DATAUP=1**
580	580
581	581	Compose the uplink payload with value returns in sequence and send with Multiply UPLINKs.
582	582
...	...	@@ -593,7 +593,7 @@
593	593	[[image:1675215848113-696.png]]
594	594
595	595
596		-**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
	596	+**(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
597	597
598	598	* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
599	599	* For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
...	...	@@ -600,9 +600,9 @@
600	600	* For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
601	601	* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
602	602
603		-**~ When AT+DATAUP=1, the maximum number of segments is 15, and the maximum total number of bytes is 1500;**
	603	+**(% style="color:red" %)When AT+DATAUP=1, the maximum number of segments is 15, and the maximum total number of bytes is 1500;**
604	604
605		-**~ When AT+DATAUP=1 and AT+ADR=0, the maximum number of bytes of each payload is determined by the DR value.**
	605	+**(% style="color:red" %)When AT+DATAUP=1 and AT+ADR=0, the maximum number of bytes of each payload is determined by the DR value.**
606	606
607	607
608	608	== ​​​​​​​2.4 Uplink Payload ==
...	...	@@ -633,11 +633,11 @@
633	633	[[image:1675215946738-635.png]]
634	634
635	635
636		-**Sensor Model**: For SDI-12-LB, this value is 0x17
	636	+**(% style="color:#037691" %)Sensor Model**(%%): For SDI-12-LB, this value is 0x17
637	637
638		-**Firmware Version**: 0x0100, Means: v1.0.0 version
	638	+**(% style="color:#037691" %)Firmware Version**(%%): 0x0100, Means: v1.0.0 version
639	639
640		-**Frequency Band**:
	640	+**(% style="color:#037691" %)Frequency Band**:
641	641
642	642	*0x01: EU868
643	643
...	...	@@ -668,7 +668,7 @@
668	668	*0x0e: MA869
669	669
670	670
671		-**Sub-Band**:
	671	+**(% style="color:#037691" %)Sub-Band**:
672	672
673	673	AU915 and US915:value 0x00 ~~ 0x08
674	674
...	...	@@ -677,7 +677,7 @@
677	677	Other Bands: Always 0x00
678	678
679	679
680		-**Battery Info**:
	680	+**(% style="color:#037691" %)Battery Info**:
681	681
682	682	Check the battery voltage.
683	683
...	...	@@ -703,7 +703,7 @@
703	703	Battery(mV)
704	704	&
705	705	Interrupt_Flag
706		-)))|(% style="width:70px" %)[[PAYLOAD_VER>>path:#Probe_Model]]|(% style="width:234px" %)(((
	706	+)))|(% style="width:70px" %)[[PAYLOAD_VER>>||anchor="H3.6Setthepayloadversion"]]|(% style="width:234px" %)(((
707	707	If the valid payload is too long and exceed the maximum support.
708	708	Payload length in server,server will show payload not provided in the LoRaWAN server.
709	709	)))
...	...	@@ -724,7 +724,7 @@
724	724	=== 2.4.4 Interrupt Pin ===
725	725
726	726
727		-This data field shows if this packet is generated by **Interrupt Pin** or not. [[Click here>>path:#Int_mod]] for the hardware and software set up. Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>path:#pins]].
	727	+This data field shows if this packet is generated by **Interrupt Pin** or not. [[Click here>>||anchor="H3.2SetInterruptMode"]] for the hardware and software set up. Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.7PinMapping"]].
728	728
729	729	**Example:**
730	730