Summary

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

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" %)
...	...	@@ -424,29 +424,30 @@
424	424
425	425	Calibrate value
426	426	)))|Reserve|(((
427		-[[Message Type Always 0x03>>||anchor="H2.3.6MessageType"]]
	426	+[[Message Type>>||anchor="H2.3.6MessageType"]]
	427	+
	428	+Always 0x03
428	428	)))
429	429
430	430	User can also send 0x14 downlink command to poll the current calibration payload.
431	431
	433	+[[image:image-20220607145603-4.png]]
432	432
433		-|**Downlink Control Type**|**FPort**|**Type Code**|**Downlink payload size(bytes)**
434		-|Get Calibration Version Info|Any|14|2
435		-
436	436	* Reply to the confirmation package: 14 01
437	437	* Reply to non-confirmed packet: 14 00
438	438
439		-1.
440		-11. Frequency Plans
441	441
	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	+)))
443	443
444		-1.
445		-11.
446		-111. EU863-870 (EU868)
447	447
448		-Uplink:
	446	+=== 2.8.1 EU863-870 (EU868) ===
449	449
	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		-Downlink:
	469	+(% style="color:blue" %)**Downlink:**
470	470
471	471	Uplink channels 1-9 (RX1)
472	472
...	...	@@ -473,28 +473,31 @@
473	473	869.525 - SF9BW125 (RX2 downlink only)
474	474
475	475
476		-1.
477		-11.
478		-111. US902-928(US915)
479	479
	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	+)))
481	481
482		-
	483	+(((
483	483	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	+)))
484	484
485		-
	487	+(((
486	486	After Join success, the end node will switch to the correct sub band by:
	489	+)))
487	487
488	488	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
489	489	* 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)
490	490
491		-1.
492		-11.
493		-111. CN470-510 (CN470)
494	494
	495	+
	496	+=== 2.8.3 CN470-510 (CN470) ===
	497	+
495	495	Used in China, Default use CHE=1
496	496
497		-Uplink:
	500	+(% style="color:blue" %)**Uplink:**
498	498
499	499	486.3 - SF7BW125 to SF12BW125
500	500
...	...	@@ -513,7 +513,7 @@
513	513	487.7 - SF7BW125 to SF12BW125
514	514
515	515
516		-Downlink:
	519	+(% style="color:blue" %)**Downlink:**
517	517
518	518	506.7 - SF7BW125 to SF12BW125
519	519
...	...	@@ -534,25 +534,32 @@
534	534	505.3 - SF12BW125 (RX2 downlink only)
535	535
536	536
537		-1.
538		-11.
539		-111. AU915-928(AU915)
540	540
	541	+=== 2.8.4 AU915-928(AU915) ===
	542	+
	543	+(((
541	541	Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
	545	+)))
542	542
543		-
	547	+(((
544	544	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	+)))
545	545
	551	+(((
	552	+
	553	+)))
546	546
	555	+(((
547	547	After Join success, the end node will switch to the correct sub band by:
	557	+)))
548	548
549	549	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
550	550	* 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)
551	551
552		-1.
553		-11.
554		-111. AS920-923 & AS923-925 (AS923)
555	555
	563	+
	564	+=== 2.8.5 AS920-923 & AS923-925 (AS923) ===
	565	+
556	556	**Default Uplink channel:**
557	557
558	558	923.2 - SF7BW125 to SF10BW125

image-20220607145603-4.png

Author

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

Size

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

Content