Summary

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

Details

Page properties

Content

...	...	@@ -265,7 +265,6 @@
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		-
269	269	=== 2.3.7 Decode payload in The Things Network ===
270	270
271	271	While using TTN network, you can add the payload format to decode the payload.
...	...	@@ -401,11 +401,13 @@
401	401
402	402	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).
403	403
404		-After stable, user can use below command to calibrate.
405	405
	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	+
409	409	(% style="color:#037691" %)**Calibration Payload**
410	410
411	411	(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
...	...	@@ -430,23 +430,24 @@
430	430
431	431	User can also send 0x14 downlink command to poll the current calibration payload.
432	432
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	+
435	435	* Reply to the confirmation package: 14 01
436	436	* Reply to non-confirmed packet: 14 00
437	437
	441	+1.
	442	+11. Frequency Plans
438	438
439		-== 2.8 Frequency Plans ==
440		-
441		-(((
442	442	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		-)))
444	444
	446	+1.
	447	+11.
	448	+111. EU863-870 (EU868)
445	445
446		-=== 2.8.1 EU863-870 (EU868) ===
	450	+Uplink:
447	447
448		-(% style="color:blue" %)**Uplink:**
449		-
450	450	868.1 - SF7BW125 to SF12BW125
451	451
452	452	868.3 - SF7BW125 to SF12BW125 and SF7BW250
...	...	@@ -466,7 +466,7 @@
466	466	868.8 - FSK
467	467
468	468
469		-(% style="color:blue" %)**Downlink:**
	471	+Downlink:
470	470
471	471	Uplink channels 1-9 (RX1)
472	472
...	...	@@ -473,31 +473,28 @@
473	473	869.525 - SF9BW125 (RX2 downlink only)
474	474
475	475
	478	+1.
	479	+11.
	480	+111. US902-928(US915)
476	476
477		-=== 2.8.2 US902-928(US915) ===
478		-
479		-(((
480	480	Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
481		-)))
482	482
483		-(((
	484	+
484	484	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		-)))
490	490
491	491	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
492	492	* 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)
493	493
	493	+1.
	494	+11.
	495	+111. CN470-510 (CN470)
494	494
495		-
496		-=== 2.8.3 CN470-510 (CN470) ===
497		-
498	498	Used in China, Default use CHE=1
499	499
500		-(% style="color:blue" %)**Uplink:**
	499	+Uplink:
501	501
502	502	486.3 - SF7BW125 to SF12BW125
503	503
...	...	@@ -516,7 +516,7 @@
516	516	487.7 - SF7BW125 to SF12BW125
517	517
518	518
519		-(% style="color:blue" %)**Downlink:**
	518	+Downlink:
520	520
521	521	506.7 - SF7BW125 to SF12BW125
522	522
...	...	@@ -537,32 +537,25 @@
537	537	505.3 - SF12BW125 (RX2 downlink only)
538	538
539	539
	539	+1.
	540	+11.
	541	+111. AU915-928(AU915)
540	540
541		-=== 2.8.4 AU915-928(AU915) ===
542		-
543		-(((
544	544	Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
545		-)))
546	546
547		-(((
	545	+
548	548	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		-)))
550	550
551		-(((
552		-
553		-)))
554	554
555		-(((
556	556	After Join success, the end node will switch to the correct sub band by:
557		-)))
558	558
559	559	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
560	560	* 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)
561	561
	554	+1.
	555	+11.
	556	+111. AS920-923 & AS923-925 (AS923)
562	562
563		-
564		-=== 2.8.5 AS920-923 & AS923-925 (AS923) ===
565		-
566	566	**Default Uplink channel:**
567	567
568	568	923.2 - SF7BW125 to SF10BW125