sascha_hemi/pycom-documentation
1
0
Fork 0
mirror of https://github.com/sascha-hemi/pycom-documentation.git synced 2026-03-21 06:06:03 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #307 from pycom/peter-pycom-patch-1

Browse Source 
lte tutorial tweaks
This commit is contained in:
gijsio
2020-08-05 11:24:26 +02:00
committed by GitHub
parent 47121c30d4 a8c3b4cc32
commit dcc60c7742
1 changed files with 20 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
content/tutorials/networks/lte/_index.md
View File

@@ -4,23 +4,20 @@ aliases:
- chapter/tutorials/lte
---
The following tutorials demonstrate the use of the LTE CAT-M1 and NB-IoT functionality on cellular enabled Pycom modules.
The following tutorial demonstrates the use of the LTE CAT-M1 and NB-IoT functionality on cellular enabled Pycom modules.
Our cellular modules support both LTE CAT-M1 and NB-IoT, these are new lower power, long range, cellular protocols. These are not the same as the full version of 2G/3G/LTE supported by cell phones, and require your local carriers to support them. At the time of writing, CAT-M1 and NB-IoT connectivity is not widely available so be sure to check with local carriers if support is available where you are.
GPy and FiPy support both LTE CAT-M1 and NB-IoT. These are newer, low power, long range, cellular protocols. They are not the same as the full version of 2G/3G/LTE supported by cell phones, and require your local carriers to support them. At the time of writing, CAT-M1 and NB-IoT connectivity is not widely available so be sure to check with local carriers if support is available where you are. Together with the SIM card, the provider will supply you with configuration details: Usually band and APN. Use these in the example code below.
Both networks make can make use of the same example:
(Make sure you check the coverage map of your provider to confirm coverage in your area)
```python
from network import LTE
import time
import socket
lte = LTE()
lte.init()
#when using verizon, use
#lte.init(carrier=verizon)
#when usint AT&T use,
#use lte.init(carrier = at&t)
#lte.init(carrier=at&t)
#some carriers do not require an APN
#also, check the band settings, for some carriers they auto-configure.
@@ -28,7 +25,7 @@ lte.attach(band=20, apn="your apn")
while not lte.isattached()
time.delay(0.25)
print('.')
print(lte.send_at_cmd('AT!="fsm"') # get the System FSM
print(lte.send_at_cmd('AT!="fsm"')) # get the System FSM
print("LTE modem attached!")
lte.connect()
while not lte.isconnected():
@@ -40,19 +37,17 @@ print("LTE modem connected!")
print(socket.getaddrinfo('pycom.io', 80))
lte.disconnect()
lte.detach()
lte.deinit()
#now we can safely machine.deepsleep()
```
The last line of the script should return a tuple containing the IP address of the Pycom server.
The last line of the script should return a tuple containing the IP address of the Pycom webserver.
>Note: the first time, it can take a long while to attach to the network.
# LTE Troubleshooting guide
Below, we review the responses from `print(lte.send_at_cmd('AT!="fsm"'))`. If you are having trouble attaching to the network, or getting a connection up and running, this might give some direction into what you are looking for. We are mainly looking at the status of the top two indicators for now.
* Before calling `lte.attach()`, the status will be `STOPPED`.
1. Before calling `lte.attach()`, the status will be `STOPPED`.
```
SYSTEM FSM
==========
@@ -78,7 +73,7 @@ Below, we review the responses from `print(lte.send_at_cmd('AT!="fsm"'))`. If yo
| HP CAT FSM |IDLE |
+--------------------------+--------------------+
```
* With no SIM card detected, the `RRC TOP FSM` will keep status `CAMPED`. You will see `HP USIM FSM` marked `ABSENT`.
1. With no SIM card detected, the `RRC TOP FSM` will keep status `CAMPED`. You will see `HP USIM FSM` marked `ABSENT`.
```
SYSTEM FSM
==========
@@ -104,19 +99,13 @@ Below, we review the responses from `print(lte.send_at_cmd('AT!="fsm"'))`. If yo
| HP CAT FSM |NULL |
+--------------------------+--------------------+
```
* SIM card inserted and attaching:
1. SIM card inserted and attaching:
* While `SCANNING`, the `RRC SEARCH FSM` goes from `WAIT_RSSI` to `WAIT_CELL_ID`
* Later, the `RRC TOP FSM` goes from `SCANNING` to `SYNCING`
* There are some states in between not discussed here.
* If it is stuck at `WAIT_RSSI`, check the antenna connection
* If the system returns multiple times from `SYNCING` to `CAMPED`, check the network availability, simcard placement and / or the firmware version.
>Note: Use the following to check the version number:
>```python
>import sqnsupgrade
>print(sqnsupgrade.info()
>```
>* Versions LR5.xx are for CAT-M1
>* Versions LR6.xx are for NB-IoT
```
SYSTEM FSM
@@ -143,7 +132,7 @@ Below, we review the responses from `print(lte.send_at_cmd('AT!="fsm"'))`. If yo
| HP CAT FSM |IDLE |
+--------------------------+--------------------+
```
* Connecting
1. Connecting
```
SYSTEM FSM
==========
@@ -169,7 +158,7 @@ Below, we review the responses from `print(lte.send_at_cmd('AT!="fsm"'))`. If yo
| HP CAT FSM |IDLE |
+--------------------------+--------------------+
```
* Connected
1. Connected
```
SYSTEM FSM
==========
@@ -195,5 +184,13 @@ Below, we review the responses from `print(lte.send_at_cmd('AT!="fsm"'))`. If yo
| HP CAT FSM |IDLE |
+--------------------------+--------------------+
```
* Firmware version:
Use the following to check the version number:
```python
import sqnsupgrade
sqnsupgrade.info()
```
* Versions LR5.xx are for CAT-M1
* Versions LR6.xx are for NB-IoT
* Potential other errors:
* `OSError: [Errno 202] EAI_FAIL`: Check the data plan / SIM activation status on network
* `OSError: [Errno 202] EAI_FAIL`: Check the data plan / SIM activation status on network