Skip to Content
Last modified by Kilight Cao on 2025/08/14 09:54
From version 349.1
edited by Kilight Cao
on 2025/02/08 14:05
Change comment: There is no comment for this version
To version 355.2
edited by Kilight Cao
on 2025/08/14 09:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,4 @@
1 -(% style="text-align:center" %)
2 -[[image:image-20220620202334-2.png||height="467" width="809"]]
1 +[[image:image-20220620202334-2.png||data-xwiki-image-style-alignment="center" height="467" width="809"]]
3 3  
4 4  
5 5  (((
... ... @@ -31,7 +31,7 @@
31 31  )))
32 32  
33 33  (((
34 -LPS8v2 also includes a (% style="color:blue" %)**built-in LoRaWAN Server and IoT server**(%%), which provide the possibility for the system integrator to deploy the IoT service without cloud service or 3rd servers.
33 +LPS8v2 also includes a (% style="color:blue" %)**built-in LoRaWAN Server ChirpStack-V4 and IoT server Node-red**(%%), which provide the possibility for the system integrator to deploy the IoT service without cloud service or 3rd servers.
35 35  )))
36 36  
37 37  (((
... ... @@ -43,6 +43,10 @@
43 43  )))
44 44  
45 45  
45 +
46 +
47 +
48 +
46 46  == 1.2 Specifications ==
47 47  
48 48  
... ... @@ -596,7 +596,9 @@
596 596  
597 597  After the v1.7-230606 version, the LPS8-V2 default factory pre-installed the LoRaWAN Server: (% style="color:blue" %)**ChirpStack-V4**(%%), Application Server: (% style="color:blue" %)**Node-Red**(%%).
598 598  
602 +(% style="color:red" %)**Note: LPS8V2 has built-in chirpstack based on Docker, so customers do not need to install it manually again**
599 599  
604 +
600 600  == 1). LoRaWAN Network Server: (% style="color:blue" %)**ChirpStack-V4**(%%) ==
601 601  
602 602  [[image:image-20231106180816-4.png||height="416" width="896"]]
... ... @@ -906,7 +906,15 @@
906 906  [[image:image-20231207145210-3.png||height="310" width="1021"]]
907 907  
908 908  
914 +**SysLog :**
909 909  
916 +(% class="box infomessage" %)
917 +(((
918 +**tail -f /var/log/syslog **
919 +)))
920 +
921 +[[image:1754364208742-890.png||height="295" width="1023"]]
922 +
910 910  (% data-sider-select-id="65e92cfb-62df-4513-8469-b74edd72dea5" %)
911 911  = (% data-sider-select-id="ce97a758-4348-4c0c-86eb-412b6b8d3996" %)9. More Services(%%) =
912 912  
... ... @@ -1247,7 +1247,12 @@
1247 1247  
1248 1248  == (% data-sider-select-id="9b024263-b754-45b6-ac15-22f86a4e1436" %)12(% data-sider-select-id="ac1f33b3-1f28-477d-880c-534ac36adcbe" %).5  Why the LPS8V2's Access Point does not do not appear & Fallback IP unable to access(%%) ==
1249 1249  
1263 +(% style="color:red" %)**Note: The following steps are only applicable to Wi-Fi module MT7601**
1250 1250  
1265 +
1266 +Users can find the model of the wifi module on the AWS page
1267 +
1268 +
1251 1251  Earlier versions of the LPS8V2 which missing the AP driver and not installed the fallback package, so the users have to do an extra update.
1252 1252  
1253 1253  (% class="box infomessage" %)
... ... @@ -1282,7 +1282,7 @@
1282 1282  
1283 1283  (% class="box infomessage" %)
1284 1284  (((
1285 -df -sh
1303 +df -h
1286 1286  )))
1287 1287  
1288 1288  [[image:image-20250207145702-2.png]]
1754364208742-890.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +158.1 KB
Content
1755136434780-847.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +41.4 KB
Content