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

GitBook: [master] 12 pages modified

Browse Source
This commit is contained in:
Daniel Spindelbauer
2018-08-03 10:19:08 +00:00
committed by gitbook-bot
parent 75a0404579
commit a9a3261384
11 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
1.-getting-started/programming/safeboot.md
View File

@@ -19,7 +19,7 @@ In order to fix this you can safe boot your module. This will prevent `boot.py`
Pin `P12` released during:
| 1st 3 secs window | 2nd 3 secs window |
| :---: | :---: |
| :--- | :--- |
| Disable `boot.py` and `main.py` | same as previous but using previous OTA firmware |
The selection made during safe boot is not persistent, therefore after the next normal reset, the latest firmware will proceed to run again.

2
1.-getting-started/registration/lora/ttn.md
View File

@@ -53,7 +53,7 @@ These are unique to each gateway, location and country specific frequency. Pleas
**You need to tick the "I'm using the legacy packet forwarder" to enable the right settings.** This is because the Nano-Gateway uses the 'de facto' standard Semtech UDP protocol.
| Option | Value |
| --- | --- |
| :--- | :--- |
| Protocol | Packet Forwarder |
| Gateway EUI | User Defined \(must match `config.py`\) |
| Description | User Defined |

2
3.-pytrack-pysense-pyscan/installation/firmware.md
View File

@@ -11,7 +11,7 @@ The latest firmware DFU file can be downloaded from the links below:
While in the normal, application mode, the Pysense/Pytrack/Pyscan/Expansion Board v3 require a Serial USB CDC driver, in DFU, bootloader mode, the DFU driver is required. Below, the USB Product ID is depicted for each case.
| Board | DFU bootloader \(update mode\) | Application firmware \(normal mode\) |
| --- | :---: | :---: |
| :--- | :--- | :--- |
| Pytrack | `0xF014` | `0xF013` |
| Pysense | `0xF011` | `0xF012` |
| Pyscan | `0xEF37` | `0xEF38` |

2
4.-tutorials-and-examples/all/modbus.md
View File

@@ -3,7 +3,7 @@
Modbus is a messaging protocol that defines the packet structure for transferring data between devices in a master/slave architecture. The protocol is independent of the transmission medium and is usually transmitted over TCP \(MODBUS TCP\) or serial communication \(MODBUS RTU\). Modbus is intended as a request/reply protocol and delivers services specified by function codes. The function code in the request tells the addressed slave what kind of action to perform. The function codes most commonly supported by devices are listed below.
| Function Name | Function Code |
| :--- | :---: |
| :--- | :--- |
| Read Coils | 0x01 |
| Read Discrete Inputs | 0x02 |
| Read Holding Registers | 0x03 |

2
4.-tutorials-and-examples/all/mqtt.md
View File

@@ -2,7 +2,7 @@
MQTT is a lightweight messaging protocol that is ideal for sending small packets of data to and from IoT devices via WiFi.
The broker used in this example is the \[IO Adafruit\]\([https://io.adafruit.com](https://io.adafruit.com)\) platform, which is free and allows for tinkering with MQTT.
The broker used in this example is the [IO Adafruit](https://io.adafruit.com) platform, which is free and allows for tinkering with MQTT.
Visit [IO Adafruit](https://io.adafruit.com) and create an account. You'll need to get hold of an API Key as well as your credentials. Visit this [guide](https://learn.adafruit.com/adafruit-io/mqtt-api) for more information about MQTT and how to use it with Adafruit's Broker.

2
4.-tutorials-and-examples/all/rmt.md
View File

@@ -7,7 +7,7 @@ The RMT \(Remote Control\) peripheral of the ESP32 is primarily designed to send
The RMT has 7 channels, of which 5 are available and can be mapped to any GPIO pin \(_Note:_ Pins `P13` -`P18` can only be used as inputs\).
| Channel | Resolution | Maximum Pulse Width |
| --- | --- | --- |
| :--- | :--- | :--- |
| 0 Used by on-board LED | | |
| 1 Used by `pycom.pulses_get()` | | |
| 2 | 100nS | 3.2768 ms |

2
4.-tutorials-and-examples/lora/lorawan-nano-gateway.md
View File

@@ -358,7 +358,7 @@ On the Register Gateway page, you will need to set the following settings:
**You need to tick the "I'm using the legacy packet forwarder" to enable the right settings.** This is because the Nano-Gateway uses the 'de facto' standard Semtech UDP protocol.
| Option | Value |
| --- | --- |
| :--- | :--- |
| Protocol | Packet Forwarder |
| Gateway EUI | User Defined \(must match `config.py`\) |
| Description | User Defined |

2
5.-firmware-and-api-reference/pycom/machine/rmt.md
View File

@@ -45,7 +45,7 @@ data = rmt.recv_pulses()
Construct an RMT object on the given channel. `channel` can be 2-7. With no additional parameters, the RMT object is created but not initialised. If extra arguments are given, the RMT is initialised for transmission or reception. See `init` for parameters of initialisation. The resolution which a pulse can be sent/received depends on the selected channel:
| Channel | Resolution | Maximum Pulse Width |
| --- | --- | --- |
| :--- | :--- | :--- |
| 0 Used by on-board LED | | |
| 1 Used by `pycom.pulses_get()` | | |
| 2 | 100nS | 3.2768 ms |

2
SUMMARY.md
View File

@@ -4,7 +4,7 @@
## About
* [Preface](about/readme.md)
* [Preface](about/about.md)
* [Pycom Products](about/products.md)
## 1. Getting Started

0
about/readme.md → about/about.md
View File

6
about/products.md
View File

@@ -7,7 +7,7 @@ Below you will find tables of all Pycom products. These tables illustrate the fu
## Development Boards
| Module | WiFi | Bluetooth | LoRa | Sigfox | LTE CAT-M1 NB-IoT |
| :---: | :---: | :---: | :---: | :---: | :---: |
| :--- | :--- | :--- | :--- | :--- | :--- |
| [![](../.gitbook/assets/wipy2.png) WiPy 3.0](../6.-product-info/development/wipy3.md) | ✔ | ✔ | | | |
| [![](../.gitbook/assets/sipy%20%281%29.png) SiPy](../6.-product-info/development/sipy.md) | ✔ | ✔ | | ✔ | |
| [![](../.gitbook/assets/gpy.png) GPy](../6.-product-info/development/gpy.md) | ✔ | ✔ | | | ✔ |
@@ -19,7 +19,7 @@ Below you will find tables of all Pycom products. These tables illustrate the fu
## Accessories
| Accessory | [![](../.gitbook/assets/expansion3.png) Expansion Board](../6.-product-info/boards/expansion3.md) | [![](../.gitbook/assets/pysense_new.png) Pysense](../6.-product-info/boards/pysense.md) | [![](../.gitbook/assets/pytrack_new.png) Pytrack](../6.-product-info/boards/pytrack.md) | [![](../.gitbook/assets/pyscan.png) Pyscan](../6.-product-info/boards/pyscan.md) |
| :---: | :---: | :---: | :---: | :---: |
| :--- | :--- | :--- | :--- | :--- |
| [![](../.gitbook/assets/pycase.png) PyCase](https://pycom.io/product/pycase/) | ✔ | | | |
| [![](../.gitbook/assets/ip67_case_exp.png) IP67 Case for Expansion Board](https://pycom.io/product/ip67-expansion-board-case/) | ✔ | | | |
| [![](../.gitbook/assets/ip67_case_py.png) IP67 Case for Pysense/Pytrack/Pyscan](https://pycom.io/product/ip67-case/) | | ✔ | ✔ | ✔ |
@@ -31,7 +31,7 @@ Below you will find tables of all Pycom products. These tables illustrate the fu
## OEM Modules
| OEM Module | [![](../.gitbook/assets/oem_l01_ref.png) L01/W01 Reference Board](../6.-product-info/oem/l01_reference.md) | [![](../.gitbook/assets/oem_universal_ref.png) Universal Reference Board](../6.-product-info/oem/universal_reference.md) |
| :---: | :---: | :---: |
| :--- | :--- | :--- |
| [![](../.gitbook/assets/w01.png) W01](../6.-product-info/oem/w01.md) | ✔ | ✔ |
| [![](../.gitbook/assets/l01.png) L01](../6.-product-info/oem/l01.md) | ✔ | ✔ |
| [![](../.gitbook/assets/l04.png) L04](../6.-product-info/oem/l04.md) | | ✔ |