Summary

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

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

image-20220607145603-4.png

Author

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

Size

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

Content