fix on alert info

This commit is contained in:
Emmanuel Florent
2019-07-09 14:48:53 +02:00
parent 4f7157cdd5
commit 05cbedee36
99 changed files with 154 additions and 156 deletions

View File

@@ -131,7 +131,7 @@ This library is split into two layers. The top level `OTA` class implements all
{{% hint style="danger" %}}
Although the above code is functional, it is provided only as an example of how an end user might implement a OTA update mechanism. It is not 100% feature complete e.g. even though it does backup previous versions of files, the roll back procedure is not implemented. This is left of the end user to do.
{{< /hint >}}
{{% /hint %}}
## Example
@@ -139,7 +139,7 @@ Below is am example implementing the methodology previously explained in this tu
{{% hint style="info" %}}
The example below will only work on a Pycom device with LoRa capabilities. If want to test it out on a device without LoRa functionality then simply comment out any code relating to LoRa. Leaving just the `WiFiOTA` initialisation and they `ota.connect()` and `ota.update()`
{{< /hint >}}
{{% /hint %}}
```python

View File

@@ -113,7 +113,7 @@ data = rmt.pulses_get()
{{% hint style="danger" %}}
If tx_idle_level is not set to the opposite of the third value in the tx_carrier tuple, the carrier wave will continue to be generated when the RMT channel is idle.
{{< /hint >}}
{{% /hint %}}
## Receiving

View File

@@ -57,4 +57,4 @@ clock = Clock()
{{% hint style="info" %}}
There are no restrictions to what can be done in an interrupt. For example, it is possible to even do network requests with an interrupt. However, it is important to keep in mind that interrupts are handled sequentially, so it's good practice to keep them short. More information can be found in [`Interrupt Handling`](/firmwareapi/notes#interrupt-handling).
{{< /hint >}}
{{% /hint %}}

View File

@@ -33,7 +33,7 @@ When changing the WLAN mode, if following the instructions below, the WLAN conne
2. Duplicate the REPL on UART. This way commands can be run via Serial USB.
{{< /hint >}}
{{% /hint %}}
## Connecting to a Router
@@ -84,7 +84,7 @@ if not wlan.isconnected():
{{% hint style="info" %}}
Notice how we check for the reset cause and the connection status, this is crucial in order to be able to soft reset the LoPy during a telnet session without breaking the connection.
{{< /hint >}}
{{% /hint %}}
## Multiple Networks using a Static IP Address

View File

@@ -110,5 +110,5 @@ To adapt this code to user specific needs:
* Increase the package size changing the `_LORA_PKG_FORMAT` to `BH%ds`. The `H` will allow the keeping of 2 bytes for size (for more information about [struct format](https://docs.python.org/2/library/struct.html#format-characters))
* Reduce the package size with bitwise manipulation
* Reduce the message size (for this demo, a string) to something more useful for specific development
{{< /hint >}}
{{% /hint %}}

View File

@@ -32,7 +32,7 @@ This example shows how to:
{{% hint style="info" %}}
The LoRa-Mesh socket supports only the following socket methods: `close()`, `bind()`, `sendto()`, and `recvfrom()`.
{{< /hint >}}
{{% /hint %}}
**Lora Mesh example**

View File

@@ -392,7 +392,7 @@ There are two methods of connecting LoPy devices to the nano-gateway, Over the A
{{% hint style="info" %}}
It's important that the following code examples (also on GitHub) are used to connect to the nano-gateway as it only supports single channel connections.
{{< /hint >}}
{{% /hint %}}
### OTAA (Over The Air Activation)

View File

@@ -8,7 +8,7 @@ aliases:
{{% hint style="info" %}}
Please ensure you have the latest Sequans modem firmware for the best network compatibility. Instructions for this can be found [here](../firmware).
{{< /hint >}}
{{% /hint %}}
The LTE Cat M1 service gives full IP access through the cellular modem.

View File

@@ -12,7 +12,7 @@ search: false
{{% hint style="info" %}}
This article is only related to GPy, FiPy, and G01 boards
{{< /hint >}}
{{% /hint %}}
{{% hint style="danger" %}}
**Important**: When upgrading your modem for the first time, even if you have updated it in the past with the old firmware update method, you **MUST** use the "recovery" upgrade method described below. Otherwise you will risk breaking your module.
@@ -24,7 +24,7 @@ Please also use the file upgdiff_33080-to-39529.dup (1.2M) from the archive.
import sqnsupgrade
sqnsupgrade.run('upgdiff_33080-to-39529.dup', 'updater.elf')
```
{{< /hint >}}
{{% /hint %}}
Please read the following instructions carefully as there are some significant changes compared to the previous updater version.
@@ -58,7 +58,7 @@ sqnsupgrade.run('upgdiff_38638-to-39529.dup')
```
If you are updating the Sequans firmware on your module for the first time, please use instead the file upgdiff_33080-to-39529.dup (1.2M) from the same archive.
Similar upgrade packages are available for the NB-IoT firmwares.
{{< /hint >}}
{{% /hint %}}
## Via SD card
@@ -138,7 +138,7 @@ SYSTEM VERSION
{{% hint style="info" %}}
Please note that the firmware update may seem to "stall" around 7-10% and again at 99%. This is not an indication of a failure but the fact that the modem has to do some tasks during and the updater will wait for these tasks to be completed. Unless the upgrade process is hanging for more than 5 minutes, **do not interrupt the process** as you will have to start again if you don't finish it. It may also take several minutes for the updater to load before responding to the AT wakeup command.
{{< /hint >}}
{{% /hint %}}
After you have updated your modem once using the recovery method, you can now flash your modem again using just the `CATM1-38638.dup` or `NB1-37781.dup` file without specifying the `updater.elf` file. However, should the upgrade fail, your modem may end up in recovery mode and you will need the `updater.elf` file again. The updater will check for this and prompt you if using the `updater.elf` file is necessary.

View File

@@ -10,7 +10,7 @@ aliases:
{{% hint style="info" %}}
As shipped, Pycom modules only support CAT-M1, in order to use NB-IoT you need to flash a different firmware to the Sequans modem. Instructions for this can be found [here](../firmware).
{{< /hint >}}
{{% /hint %}}
## NB-IoT usage

View File

@@ -33,7 +33,7 @@ s.send(bytes([1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12]))
{{% hint style="danger" %}}
Please ensure that there is an antenna connected to your device before sending/receiving Sigfox messages as in proper use (e.g. without an antenna), may damage the device.
{{< /hint >}}
{{% /hint %}}
## Disengage Sequence Number