Summary

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

Details

Page properties

Content

...	...	@@ -265,6 +265,7 @@
265	265	|0x02|Reply configures info|[[Configure Info Payload>>||anchor="H3.4GetFirmwareVersionInfo"]]
266	266	|0x03|Reply Calibration Info|[[Calibration Payload>>||anchor="H2.7Calibration"]]
267	267
	268	+
268	268	=== 2.3.7 Decode payload in The Things Network ===
269	269
270	270	While using TTN network, you can add the payload format to decode the payload.
...	...	@@ -400,13 +400,11 @@
400	400
401	401	User can do calibration for the probe. It is limited to use below pH buffer solution to calibrate: 4.00, 6.86, 9.18. When calibration, user need to clean the electrode and put the probe in the pH buffer solution to wait the value stable ( a new clean electrode might need max 24 hours to be stable).
402	402
	404	+After stable, user can use below command to calibrate.
403	403
404		-(% style="color:#037691" %)**After stable, user can use below command to calibrate.**
405		-
406	406	[[image:image-20220607144936-3.png]]
407	407
408	408
409		-
410	410	(% style="color:#037691" %)**Calibration Payload**
411	411
412	412	(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
...	...	@@ -431,24 +431,23 @@
431	431
432	432	User can also send 0x14 downlink command to poll the current calibration payload.
433	433
	433	+[[image:image-20220607145603-4.png]]
434	434
435		-|**Downlink Control Type**|**FPort**|**Type Code**|**Downlink payload size(bytes)**
436		-|Get Calibration Version Info|Any|14|2
437		-
438	438	* Reply to the confirmation package: 14 01
439	439	* Reply to non-confirmed packet: 14 00
440	440
441		-1.
442		-11. Frequency Plans
443	443
	439	+== 2.8 Frequency Plans ==
	440	+
	441	+(((
444	444	The LSPH01 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
	443	+)))
445	445
446		-1.
447		-11.
448		-111. EU863-870 (EU868)
449	449
450		-Uplink:
	446	+=== 2.8.1 EU863-870 (EU868) ===
451	451
	448	+(% style="color:blue" %)**Uplink:**
	449	+
452	452	868.1 - SF7BW125 to SF12BW125
453	453
454	454	868.3 - SF7BW125 to SF12BW125 and SF7BW250
...	...	@@ -468,7 +468,7 @@
468	468	868.8 - FSK
469	469
470	470
471		-Downlink:
	469	+(% style="color:blue" %)**Downlink:**
472	472
473	473	Uplink channels 1-9 (RX1)
474	474
...	...	@@ -475,28 +475,31 @@
475	475	869.525 - SF9BW125 (RX2 downlink only)
476	476
477	477
478		-1.
479		-11.
480		-111. US902-928(US915)
481	481
	477	+=== 2.8.2 US902-928(US915) ===
	478	+
	479	+(((
482	482	Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
	481	+)))
483	483
484		-
	483	+(((
485	485	To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
	485	+)))
486	486
487		-
	487	+(((
488	488	After Join success, the end node will switch to the correct sub band by:
	489	+)))
489	489
490	490	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
491	491	* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
492	492
493		-1.
494		-11.
495		-111. CN470-510 (CN470)
496	496
	495	+
	496	+=== 2.8.3 CN470-510 (CN470) ===
	497	+
497	497	Used in China, Default use CHE=1
498	498
499		-Uplink:
	500	+(% style="color:blue" %)**Uplink:**
500	500
501	501	486.3 - SF7BW125 to SF12BW125
502	502
...	...	@@ -515,7 +515,7 @@
515	515	487.7 - SF7BW125 to SF12BW125
516	516
517	517
518		-Downlink:
	519	+(% style="color:blue" %)**Downlink:**
519	519
520	520	506.7 - SF7BW125 to SF12BW125
521	521
...	...	@@ -536,25 +536,32 @@
536	536	505.3 - SF12BW125 (RX2 downlink only)
537	537
538	538
539		-1.
540		-11.
541		-111. AU915-928(AU915)
542	542
	541	+=== 2.8.4 AU915-928(AU915) ===
	542	+
	543	+(((
543	543	Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
	545	+)))
544	544
545		-
	547	+(((
546	546	To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
	549	+)))
547	547
	551	+(((
	552	+
	553	+)))
548	548
	555	+(((
549	549	After Join success, the end node will switch to the correct sub band by:
	557	+)))
550	550
551	551	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
552	552	* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
553	553
554		-1.
555		-11.
556		-111. AS920-923 & AS923-925 (AS923)
557	557
	563	+
	564	+=== 2.8.5 AS920-923 & AS923-925 (AS923) ===
	565	+
558	558	**Default Uplink channel:**
559	559
560	560	923.2 - SF7BW125 to SF10BW125