mirror of
https://github.com/sascha-hemi/pycom-documentation.git
synced 2026-03-21 05:06:35 +01:00
GitBook: [master] 30 pages modified
This commit is contained in:
Daniel Spindelbauer
committed by
gitbook-bot
gitbook-bot
parent
be2101c4c6
commit
f07b7256fd
@@ -4,7 +4,7 @@ Welcome to the Pycom documentation site. The documentation is split into 5 secti
|
|||||||
|
|
||||||
To get started, read through the Getting Started Guide then feel free to jump straight into the tutorials and examples in Tutorials & Examples to begin building your projects.
|
To get started, read through the Getting Started Guide then feel free to jump straight into the tutorials and examples in Tutorials & Examples to begin building your projects.
|
||||||
|
|
||||||
* [Products](about/products.md)
|
* [Products](products.md)
|
||||||
* [Getting Started](getting-started/introduction.md)
|
* [Getting Started](getting-started/introduction.md)
|
||||||
* [Tutorials](tutorials-and-examples/introduction.md)
|
* [Tutorials](tutorials-and-examples/introduction.md)
|
||||||
* [Product Info](product-info/introduction.md)
|
* [Product Info](product-info/introduction.md)
|
||||||
|
|||||||
55
SUMMARY.md
55
SUMMARY.md
@@ -2,10 +2,6 @@
|
|||||||
|
|
||||||
* [Introduction](README.md)
|
* [Introduction](README.md)
|
||||||
|
|
||||||
## About
|
|
||||||
|
|
||||||
* [Pycom Products](about/products.md)
|
|
||||||
|
|
||||||
## 1. Getting Started
|
## 1. Getting Started
|
||||||
|
|
||||||
* [1.0 Introduction](getting-started/introduction.md)
|
* [1.0 Introduction](getting-started/introduction.md)
|
||||||
@@ -35,6 +31,7 @@
|
|||||||
* [1.4.3 LoRaWAN](getting-started/registration/lora/README.md)
|
* [1.4.3 LoRaWAN](getting-started/registration/lora/README.md)
|
||||||
* [1.4.3.1 The Things Network](getting-started/registration/lora/ttn.md)
|
* [1.4.3.1 The Things Network](getting-started/registration/lora/ttn.md)
|
||||||
* [1.4.3.2 Objenious](getting-started/registration/lora/objenious.md)
|
* [1.4.3.2 Objenious](getting-started/registration/lora/objenious.md)
|
||||||
|
* [Pycom Products](products.md)
|
||||||
|
|
||||||
## 2. Pymakr Plugin
|
## 2. Pymakr Plugin
|
||||||
|
|
||||||
@@ -149,6 +146,7 @@
|
|||||||
* [5.3.18 ustruct](firmware-and-api-reference/micropython/ustruct.md)
|
* [5.3.18 ustruct](firmware-and-api-reference/micropython/ustruct.md)
|
||||||
* [5.3.19 \_thread](firmware-and-api-reference/micropython/_thread.md)
|
* [5.3.19 \_thread](firmware-and-api-reference/micropython/_thread.md)
|
||||||
* [5.3.20 Builtin](firmware-and-api-reference/micropython/builtin.md)
|
* [5.3.20 Builtin](firmware-and-api-reference/micropython/builtin.md)
|
||||||
|
* [5.4 Notes](firmware-and-api-reference/notes.md)
|
||||||
|
|
||||||
## 6. Product Info
|
## 6. Product Info
|
||||||
|
|
||||||
@@ -178,42 +176,33 @@
|
|||||||
* [6.3.6.1 Deep Sleep API](product-info/boards/deepsleep/api.md)
|
* [6.3.6.1 Deep Sleep API](product-info/boards/deepsleep/api.md)
|
||||||
* [6.4 Notes](product-info/notes.md)
|
* [6.4 Notes](product-info/notes.md)
|
||||||
|
|
||||||
## 7. Datasheets
|
## 7. Pybytes
|
||||||
|
|
||||||
* [7.1 Development Modules](datasheets/development.md)
|
* [7.1 Introduction](pybytes/introduction.md)
|
||||||
* [7.2 OEM Modules](datasheets/oem.md)
|
* [7.2 Getting Started with Pybytes](pybytes/getting-started.md)
|
||||||
* [7.3 Expansion Boards and Shields](datasheets/boards.md)
|
* [7.3 Add a device to Pybytes](pybytes/add-device/README.md)
|
||||||
|
* [7.3.1 Connect to Pybytes: Quick Add](pybytes/add-device/quick.md)
|
||||||
|
* [7.3.2 Connect to Pybytes: Flash Pybytes library manually](pybytes/add-device/flash.md)
|
||||||
|
* [7.3.3 Add Sigfox device](pybytes/add-device/sigfox/README.md)
|
||||||
|
* [7.3.3.1 DevKit contract](pybytes/add-device/sigfox/devkit.md)
|
||||||
|
* [7.3.3.2 Custom contract](pybytes/add-device/sigfox/custom.md)
|
||||||
|
* [7.4 Visualise data from your device](pybytes/visualise-data.md)
|
||||||
|
|
||||||
## 8. Pybytes
|
## 8. Documentation Notes
|
||||||
|
|
||||||
* [8.1 Introduction](pybytes/introduction.md)
|
* [8.1 Introduction](documentation-notes/introduction.md)
|
||||||
* [8.2 Getting Started with Pybytes](pybytes/getting-started.md)
|
* [8.2 Syntax](documentation-notes/syntax.md)
|
||||||
* [8.3 Add a device to Pybytes](pybytes/add-device/README.md)
|
* [8.3 REPL vs Scripts](documentation-notes/replscript.md)
|
||||||
* [8.3.1 Connect to Pybytes: Quick Add](pybytes/add-device/quick.md)
|
* [8.4 Mesh Networks](documentation-notes/mesh-networks.md)
|
||||||
* [8.3.2 Connect to Pybytes: Flash Pybytes library manually](pybytes/add-device/flash.md)
|
|
||||||
* [8.3.3 Add Sigfox device](pybytes/add-device/sigfox/README.md)
|
|
||||||
* [8.3.3.1 DevKit contract](pybytes/add-device/sigfox/devkit.md)
|
|
||||||
* [8.3.3.2 Custom contract](pybytes/add-device/sigfox/custom.md)
|
|
||||||
* [8.4 Visualise data from your device](pybytes/visualise-data.md)
|
|
||||||
|
|
||||||
## 9. Documentation Notes
|
## 9. Advanced Topics
|
||||||
|
|
||||||
* [9.1 Introduction](documentation-notes/introduction.md)
|
* [9.1 Firmware Downgrade](advanced-topics/downgrade.md)
|
||||||
* [9.2 Syntax](documentation-notes/syntax.md)
|
* [9.2 CLI Updater](advanced-topics/cli.md)
|
||||||
* [9.3 REPL vs Scripts](documentation-notes/replscript.md)
|
* [9.3 SecureBoot and Encryption](advanced-topics/encryption.md)
|
||||||
* [9.4 Mesh Networks](documentation-notes/mesh-networks.md)
|
|
||||||
|
|
||||||
## 10. Advanced Topics
|
|
||||||
|
|
||||||
* [10.1 Firmware Downgrade](advanced-topics/downgrade.md)
|
|
||||||
* [10.2 CLI Updater](advanced-topics/cli.md)
|
|
||||||
* [10.3 SecureBoot and Encryption](advanced-topics/encryption.md)
|
|
||||||
|
|
||||||
## 11. License
|
|
||||||
|
|
||||||
* [11.1 License](license/license.md)
|
|
||||||
|
|
||||||
## Have a question?
|
## Have a question?
|
||||||
|
|
||||||
* [Ask on the Forum](https://forum.pycom.io)
|
* [Ask on the Forum](https://forum.pycom.io)
|
||||||
|
* [License](license.md)
|
||||||
|
|
||||||
|
|||||||
@@ -1,39 +0,0 @@
|
|||||||
# Pycom Products
|
|
||||||
|
|
||||||
## Pycom Products
|
|
||||||
|
|
||||||
Below you will find tables of all Pycom products. These tables illustrate the functionality of our various products, their compatibility with each other, as well as what accessories are required to utilise certain functionality.
|
|
||||||
|
|
||||||
## Development Boards
|
|
||||||
|
|
||||||
| Module | WiFi | Bluetooth | LoRa | Sigfox | LTE CAT-M1 NB-IoT |
|
|
||||||
| :--- | :--- | :--- | :--- | :--- | :--- |
|
|
||||||
| [ WiPy 3.0](../product-info/development/wipy3.md) | ✔ | ✔ | | | |
|
|
||||||
| [ SiPy](../product-info/development/sipy.md) | ✔ | ✔ | | ✔ | |
|
|
||||||
| [ GPy](../product-info/development/gpy.md) | ✔ | ✔ | | | ✔ |
|
|
||||||
| [ LoPy](../product-info/development/lopy.md) | ✔ | ✔ | ✔ | | |
|
|
||||||
| [ LoPy4](../product-info/development/lopy4.md) | ✔ | ✔ | ✔ | ✔ | |
|
|
||||||
| [ FiPy](../product-info/development/fipy.md) | ✔ | ✔ | ✔ | ✔ | ✔ |
|
|
||||||
| Antennas [ External WiFi/BT Antenna Kit](https://pycom.io/product/external-wifi-antenna/)[ LoRa & Sigfox Antenna Kit](https://pycom.io/product/lora-antenna-kit/) | [ LTE-M Antenna Kit](https://pycom.io/product/lte-m-antenna-kit/) | | | | |
|
|
||||||
|
|
||||||
## Accessories
|
|
||||||
|
|
||||||
| Accessory | [ Expansion Board](../product-info/boards/expansion3.md) | [ Pysense](../product-info/boards/pysense.md) | [ Pytrack](../product-info/boards/pytrack.md) | [ Pyscan](../product-info/boards/pyscan.md) |
|
|
||||||
| :--- | :--- | :--- | :--- | :--- |
|
|
||||||
| [ PyCase](https://pycom.io/product/pycase/) | ✔ | | | |
|
|
||||||
| [ IP67 Case for Expansion Board](https://pycom.io/product/ip67-expansion-board-case/) | ✔ | | | |
|
|
||||||
| [ IP67 Case for Pysense/Pytrack/Pyscan](https://pycom.io/product/ip67-case/) | | ✔ | ✔ | ✔ |
|
|
||||||
| [ IP67 Case \(universal\)](https://pycom.io/product/universal-ip67-case/) | ✔ | ✔ | ✔ | ✔ |
|
|
||||||
|  LiPo Battery \(user-supplied\) | ✔ | ✔ | ✔ | ✔ |
|
|
||||||
|  Micro USB Cable Required \(user-supplied\) | ✔ | ✔ | ✔ | ✔ |
|
|
||||||
| Pyscan Modules [ OLED Module](https://pycom.io/product/oled-screen/)[ 2MP Camera](https://pycom.io/product/2mp-camera/)[ Barcode Reader](https://pycom.io/product/barcode-reader)[ Fingerprint Scanner](https://pycom.io/product/fingerprint-scanner/)[ IR Image Sensor](https://pycom.io/product/infared-image-sensor/) | ✔ | | | |
|
|
||||||
|
|
||||||
## OEM Modules
|
|
||||||
|
|
||||||
| OEM Module | [ L01/W01 Reference Board](../product-info/oem/l01_reference.md) | [ Universal Reference Board](../product-info/oem/universal_reference.md) |
|
|
||||||
| :--- | :--- | :--- |
|
|
||||||
| [ W01](../product-info/oem/w01.md) | ✔ | ✔ |
|
|
||||||
| [ L01](../product-info/oem/l01.md) | ✔ | ✔ |
|
|
||||||
| [ L04](../product-info/oem/l04.md) | | ✔ |
|
|
||||||
| [ G01](../product-info/oem/g01.md) | | ✔ |
|
|
||||||
|
|
||||||
@@ -1,4 +1,4 @@
|
|||||||
# 10.2 CLI Updater
|
# 9.2 CLI Updater
|
||||||
|
|
||||||
## Command Line Update Utility
|
## Command Line Update Utility
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 10.1 Firmware Downgrade
|
# 9.1 Firmware Downgrade
|
||||||
|
|
||||||
The firmware upgrade tool usually updates your device to the latest available firmware version. If you require to downgrade your device to a previous firmware there are two methods to achieve this.
|
The firmware upgrade tool usually updates your device to the latest available firmware version. If you require to downgrade your device to a previous firmware there are two methods to achieve this.
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 10.3 SecureBoot and Encryption
|
# 9.3 SecureBoot and Encryption
|
||||||
|
|
||||||
## Summary
|
## Summary
|
||||||
|
|
||||||
|
|||||||
@@ -1,12 +0,0 @@
|
|||||||
# 7.3 Expansion Boards and Shields
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/expansion3-specsheet.pdf" caption="Expansion Board 3.0" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/pytrack-specsheet.pdf" caption="Pytrack" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/pysense-specsheet \(1\).pdf" caption="Pysense" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/pyscan-specsheet \(1\).pdf" caption="Pyscan" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/expansion2-specsheet \(1\).pdf" caption="Expansion Board 2.0" %}
|
|
||||||
|
|
||||||
@@ -1,16 +0,0 @@
|
|||||||
# 7.1 Development Modules
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/wipy2-specsheet \(1\).pdf" caption="WiPy 2.0" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/wipy3-specsheet \(1\).pdf" caption="WiPy 3.0" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/lopy-specsheet \(1\).pdf" caption="LoPy" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/lopy4-specsheet.pdf" caption="LoPy 4" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/sipy-specsheet \(1\).pdf" caption="SiPy" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/gpy-specsheet \(1\).pdf" caption="GPy" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/fipy-specsheet.pdf" caption="FiPy" %}
|
|
||||||
|
|
||||||
@@ -1,10 +0,0 @@
|
|||||||
# 7.2 OEM Modules
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/w01-specsheet.pdf" caption="W01" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/l01-specsheet.pdf" caption="L01" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/l04-specsheet \(1\).pdf" caption="L04" %}
|
|
||||||
|
|
||||||
{% file src="../.gitbook/assets/g01-specsheet \(1\).pdf" caption="G01" %}
|
|
||||||
|
|
||||||
@@ -1,4 +1,4 @@
|
|||||||
# 9.1 Introduction
|
# 8.1 Introduction
|
||||||
|
|
||||||
The Pycom documentation aims to be straightforward and to adhere to typical Python documentation to allow for ease of understanding. However, there may be some unusual features for those not used to Python documentation or that are new to the MicroPython Language. This section of the documentation aims to provide clarity for any of the design specifics that might be confusing for those new to Python and this style of documentation.
|
The Pycom documentation aims to be straightforward and to adhere to typical Python documentation to allow for ease of understanding. However, there may be some unusual features for those not used to Python documentation or that are new to the MicroPython Language. This section of the documentation aims to provide clarity for any of the design specifics that might be confusing for those new to Python and this style of documentation.
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 9.4 Mesh Networks
|
# 8.4 Mesh Networks
|
||||||
|
|
||||||
Mesh Networking is currently under development. Please click [here](https://docs.pycom.io/v/development_release/chapter/tutorials/lora/lora-mesh.html) for the documentation. Please keep in mind that this document is still only informational.
|
Mesh Networking is currently under development. Please click [here](https://docs.pycom.io/v/development_release/chapter/tutorials/lora/lora-mesh.html) for the documentation. Please keep in mind that this document is still only informational.
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 9.3 REPL vs Scripts
|
# 8.3 REPL vs Scripts
|
||||||
|
|
||||||
Users of this documentation should be aware that examples given in the docs are under the expectation that they are being executed using the MicroPython REPL. This means that when certain functions are called, their output may not necessarily be printed to the console if they are run from a script. When using the REPL many classes/functions automatically produce a printed output displaying the return value of the function to the console. The code snippet below demonstrates some examples of classes/functions that might display this behaviour.
|
Users of this documentation should be aware that examples given in the docs are under the expectation that they are being executed using the MicroPython REPL. This means that when certain functions are called, their output may not necessarily be printed to the console if they are run from a script. When using the REPL many classes/functions automatically produce a printed output displaying the return value of the function to the console. The code snippet below demonstrates some examples of classes/functions that might display this behaviour.
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 9.2 Syntax
|
# 8.2 Syntax
|
||||||
|
|
||||||
The Pycom documentation follows standard Python Library format using the popular Sphinx Docs tool. There are some notable points regarding the syntax of classes, methods and constants. Please see the notes below and familiarise yourself with the specific details before reviewing the documentation.
|
The Pycom documentation follows standard Python Library format using the popular Sphinx Docs tool. There are some notable points regarding the syntax of classes, methods and constants. Please see the notes below and familiarise yourself with the specific details before reviewing the documentation.
|
||||||
|
|
||||||
|
|||||||
16
firmware-and-api-reference/notes.md
Normal file
16
firmware-and-api-reference/notes.md
Normal file
@@ -0,0 +1,16 @@
|
|||||||
|
# 5.4 Notes
|
||||||
|
|
||||||
|
## Interrupt Handling
|
||||||
|
|
||||||
|
In Pycom’s ESP32 MicroPython port there are no restrictions on what can be done within an interrupt handler. For example, other ports do not allow allocating memory inside the handler or the use of sockets.
|
||||||
|
|
||||||
|
These limitations were raised by handling the interrupt events differently. When an interrupt happens, a message is posted into a queue, notifying a separate thread that the appropriate callback handler should be called. Such handler would receive an argument. By default it is the object associated with the event.
|
||||||
|
|
||||||
|
The user can do whatever is required inside of the callback, such as creating new variables, or even sending network packets. Bear in mind that interrupts are processed sequentially and thus it is ideal to keep the handlers as short as possible in order to attend all of them in the minimum time.
|
||||||
|
|
||||||
|
Currently, there are 2 classes that support interrupts; the [`Alarm`](pycom/machine/timer.md#class-timer-alarm-handler-none-s-ms-us-arg-none-periodic-false) and [`Pin`](pycom/machine/pin.md) classes. Both classes provide the `.callback()` method that enables the interrupt and registers the given handler. For more details about interrupt usage along with examples, please visit their respective sections.
|
||||||
|
|
||||||
|
{% hint style="info" %}
|
||||||
|
Currently the interrupt system can queue up to **16 interrupts**.
|
||||||
|
{% endhint %}
|
||||||
|
|
||||||
@@ -119,7 +119,7 @@ p_in.callback(Pin.IRQ_FALLING | Pin.IRQ_RISING, pin_handler)
|
|||||||
```
|
```
|
||||||
|
|
||||||
{% hint style="info" %}
|
{% hint style="info" %}
|
||||||
For more information on how Pycom’s products handle interrupts, see [here](https://github.com/pycom/pycom-docs/tree/37661883902849b1a931ee273a23ae8e0f3d773e/chapter/toolsandfeatures/notes.md).
|
For more information on how Pycom’s products handle interrupts, see [here](../../notes.md#interrupt-handling).
|
||||||
{% endhint %}
|
{% endhint %}
|
||||||
|
|
||||||
## Attributes
|
## Attributes
|
||||||
|
|||||||
@@ -118,6 +118,6 @@ clock = Clock()
|
|||||||
```
|
```
|
||||||
|
|
||||||
{% hint style="info" %}
|
{% hint style="info" %}
|
||||||
For more information on how Pycom’s products handle interrupts, see [notes](https://github.com/pycom/pycom-docs/tree/37661883902849b1a931ee273a23ae8e0f3d773e/chapter/toolsandfeatures/notes.md).
|
For more information on how Pycom’s products handle interrupts, see [notes](../../notes.md#interrupt-handling).
|
||||||
{% endhint %}
|
{% endhint %}
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
# 1.0 Introduction
|
# 1.0 Introduction
|
||||||
|
|
||||||
So, you've decided to order a Pycom development module. Firstly we would like to congratulate you in making an excellent decision. If you haven't yet placed your order we highly recommend you check out the [products](../about/products.md) page before you place your order to ensure you know which accessories you might require.
|
So, you've decided to order a Pycom development module. Firstly we would like to congratulate you in making an excellent decision. If you haven't yet placed your order we highly recommend you check out the [products](../products.md) page before you place your order to ensure you know which accessories you might require.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 11.1 License
|
# License
|
||||||
|
|
||||||
The MIT License \(MIT\)
|
The MIT License \(MIT\)
|
||||||
|
|
||||||
39
products.md
Normal file
39
products.md
Normal file
@@ -0,0 +1,39 @@
|
|||||||
|
# Pycom Products
|
||||||
|
|
||||||
|
## Pycom Products
|
||||||
|
|
||||||
|
Below you will find tables of all Pycom products. These tables illustrate the functionality of our various products, their compatibility with each other, as well as what accessories are required to utilise certain functionality.
|
||||||
|
|
||||||
|
## Development Boards
|
||||||
|
|
||||||
|
| Module | WiFi | Bluetooth | LoRa | Sigfox | LTE CAT-M1 NB-IoT |
|
||||||
|
| :--- | :--- | :--- | :--- | :--- | :--- |
|
||||||
|
| [ WiPy 3.0](product-info/development/wipy3.md) | ✔ | ✔ | | | |
|
||||||
|
| [ SiPy](product-info/development/sipy.md) | ✔ | ✔ | | ✔ | |
|
||||||
|
| [ GPy](product-info/development/gpy.md) | ✔ | ✔ | | | ✔ |
|
||||||
|
| [ LoPy](product-info/development/lopy.md) | ✔ | ✔ | ✔ | | |
|
||||||
|
| [ LoPy4](product-info/development/lopy4.md) | ✔ | ✔ | ✔ | ✔ | |
|
||||||
|
| [ FiPy](product-info/development/fipy.md) | ✔ | ✔ | ✔ | ✔ | ✔ |
|
||||||
|
| Antennas [ External WiFi/BT Antenna Kit](https://pycom.io/product/external-wifi-antenna/)[ LoRa & Sigfox Antenna Kit](https://pycom.io/product/lora-antenna-kit/) | [ LTE-M Antenna Kit](https://pycom.io/product/lte-m-antenna-kit/) | | | | |
|
||||||
|
|
||||||
|
## Accessories
|
||||||
|
|
||||||
|
| Accessory | [ Expansion Board](product-info/boards/expansion3.md) | [ Pysense](product-info/boards/pysense.md) | [ Pytrack](product-info/boards/pytrack.md) | [ Pyscan](product-info/boards/pyscan.md) |
|
||||||
|
| :--- | :--- | :--- | :--- | :--- |
|
||||||
|
| [ PyCase](https://pycom.io/product/pycase/) | ✔ | | | |
|
||||||
|
| [ IP67 Case for Expansion Board](https://pycom.io/product/ip67-expansion-board-case/) | ✔ | | | |
|
||||||
|
| [ IP67 Case for Pysense/Pytrack/Pyscan](https://pycom.io/product/ip67-case/) | | ✔ | ✔ | ✔ |
|
||||||
|
| [ IP67 Case \(universal\)](https://pycom.io/product/universal-ip67-case/) | ✔ | ✔ | ✔ | ✔ |
|
||||||
|
|  LiPo Battery \(user-supplied\) | ✔ | ✔ | ✔ | ✔ |
|
||||||
|
|  Micro USB Cable Required \(user-supplied\) | ✔ | ✔ | ✔ | ✔ |
|
||||||
|
| Pyscan Modules [ OLED Module](https://pycom.io/product/oled-screen/)[ 2MP Camera](https://pycom.io/product/2mp-camera/)[ Barcode Reader](https://pycom.io/product/barcode-reader)[ Fingerprint Scanner](https://pycom.io/product/fingerprint-scanner/)[ IR Image Sensor](https://pycom.io/product/infared-image-sensor/) | ✔ | | | |
|
||||||
|
|
||||||
|
## OEM Modules
|
||||||
|
|
||||||
|
| OEM Module | [ L01/W01 Reference Board](product-info/oem/l01_reference.md) | [ Universal Reference Board](product-info/oem/universal_reference.md) |
|
||||||
|
| :--- | :--- | :--- |
|
||||||
|
| [ W01](product-info/oem/w01.md) | ✔ | ✔ |
|
||||||
|
| [ L01](product-info/oem/l01.md) | ✔ | ✔ |
|
||||||
|
| [ L04](product-info/oem/l04.md) | | ✔ |
|
||||||
|
| [ G01](product-info/oem/g01.md) | | ✔ |
|
||||||
|
|
||||||
@@ -1,4 +1,4 @@
|
|||||||
# 8.3 Add a device to Pybytes
|
# 7.3 Add a device to Pybytes
|
||||||
|
|
||||||
In this section, we will explain to you how to add a device to Pybytes
|
In this section, we will explain to you how to add a device to Pybytes
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 8.3.2 Connect to Pybytes: Flash Pybytes library manually
|
# 7.3.2 Connect to Pybytes: Flash Pybytes library manually
|
||||||
|
|
||||||
## Connecting a device to Pybytes by flashing Pybytes library manually
|
## Connecting a device to Pybytes by flashing Pybytes library manually
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 8.3.1 Connect to Pybytes: Quick Add
|
# 7.3.1 Connect to Pybytes: Quick Add
|
||||||
|
|
||||||
## Connecting a device to Pybytes quickly by using the Firmware Updater
|
## Connecting a device to Pybytes quickly by using the Firmware Updater
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 8.3.3 Add Sigfox device
|
# 7.3.3 Add Sigfox device
|
||||||
|
|
||||||
{% hint style="danger" %}
|
{% hint style="danger" %}
|
||||||
Before you start you need to create Sigfox account. You need Pycom device with Sigfox to get your Sigfox account. [**Follow these instructions**](../../../getting-started/registration/sigfox.md).
|
Before you start you need to create Sigfox account. You need Pycom device with Sigfox to get your Sigfox account. [**Follow these instructions**](../../../getting-started/registration/sigfox.md).
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 8.3.3.2 Custom contract
|
# 7.3.3.2 Custom contract
|
||||||
|
|
||||||
For building Sigfox application on Pybytes we recommend to [buy Sigfox contract](https://buy.sigfox.com/).
|
For building Sigfox application on Pybytes we recommend to [buy Sigfox contract](https://buy.sigfox.com/).
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 8.3.3.1 DevKit contract
|
# 7.3.3.1 DevKit contract
|
||||||
|
|
||||||
Every Sigfox Pycom device comes with free Sigfox connectivity - Sigfox DevKit contract. It provides one year of Sigfox connectivity. This is great for prototyping.
|
Every Sigfox Pycom device comes with free Sigfox connectivity - Sigfox DevKit contract. It provides one year of Sigfox connectivity. This is great for prototyping.
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 8.2 Getting Started with Pybytes
|
# 7.2 Getting Started with Pybytes
|
||||||
|
|
||||||
Follow these steps to create a Pybytes account:
|
Follow these steps to create a Pybytes account:
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 8.1 Introduction
|
# 7.1 Introduction
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# 8.4 Visualise data from your device
|
# 7.4 Visualise data from your device
|
||||||
|
|
||||||
In this section, we will explain to you how to create widgets for data visualisation and set up your device's dashboard on Pybytes.
|
In this section, we will explain to you how to create widgets for data visualisation and set up your device's dashboard on Pybytes.
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
# 4.2.12 Timers
|
# 4.2.12 Timers
|
||||||
|
|
||||||
Detailed information about this class can be found in [`Timer`](https://github.com/pycom/pycom-docs/tree/37661883902849b1a931ee273a23ae8e0f3d773e/chapter/firmwareapi/pycom/machine/Timer.html).
|
Detailed information about this class can be found in [`Timer`](../../firmware-and-api-reference/pycom/machine/timer.md).
|
||||||
|
|
||||||
## Chronometer
|
## Chronometer
|
||||||
|
|
||||||
@@ -48,6 +48,6 @@ clock = Clock()
|
|||||||
```
|
```
|
||||||
|
|
||||||
{% hint style="info" %}
|
{% 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`](timers.md).
|
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`](../../firmware-and-api-reference/notes.md#interrupt-handling).
|
||||||
{% endhint %}
|
{% endhint %}
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user