From d47458d25f0c79314db89ba01ea3a46759ec6a0c Mon Sep 17 00:00:00 2001 From: gijsio <67470426+gijsio@users.noreply.github.com> Date: Tue, 28 Jul 2020 10:25:18 +0200 Subject: [PATCH] updated datasheet format --- content/datasheets/development/fipy.md | 41 ++++++------------------- content/datasheets/development/gpy.md | 31 +++---------------- content/datasheets/development/lopy.md | 31 +++++-------------- content/datasheets/development/lopy4.md | 32 ++++++------------- content/datasheets/development/sipy.md | 25 +++------------ content/datasheets/development/wipy2.md | 17 +++------- content/datasheets/development/wipy3.md | 16 ++++++---- content/datasheets/oem/g01.md | 15 +++------ content/datasheets/oem/l01.md | 11 ++----- content/datasheets/oem/l04.md | 12 ++------ 10 files changed, 60 insertions(+), 171 deletions(-) diff --git a/content/datasheets/development/fipy.md b/content/datasheets/development/fipy.md index e7877ad..c0063a2 100644 --- a/content/datasheets/development/fipy.md +++ b/content/datasheets/development/fipy.md @@ -9,15 +9,13 @@ aliases: ![](/gitbook/assets/fipy-1.png) +> Note: Orient the RGB LED / reset button over the USB connector on any expansion board -{{% hint style="info" %}} - Please Note: We have removed the labels from the pictures in the documentation due to inconsistencies with label orientation. *The LED must be aligned above the USB socket* when inserting or removing a development board from an expansion board/Pytrack/Pysense/Pyscan. -{{% /hint %}} **Store**: [Buy Here](https://pycom.io/product/fipy/) -**Getting Started:** [Click Here](/gettingstarted/connection/fipy) +**Getting Started:** [Click Here](/gettingstarted/) ## Datasheet @@ -31,42 +29,21 @@ The Fipy is certified for [CE RED](/gitbook/assets/fipy_c03-b0-red-final.pdf) an [ROHS certification](gitbook/assets/RoHs_declarations/RoHS-for-FiPy(8217-00091P)-20190523.pdf) ## Pinout -The pinout of the FiPy is available as a PDF File - - FiPy Pinout +The pinout of the FiPy is available as a [PDF File](/gitbook/assents/fipy-pinout.pdf) ![](/gitbook/assets/fipy-pinout.png) -{{% hint style="info" %}} -Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. -{{% /hint %}} +> Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. ## Notes -### WiFi - -By default, upon booting up the FiPy will create a WiFi access point with the SSID `fipy-wlan-XXXX`, where `XXXX` is a random 4-digit number, and the password `www.pycom.io`. - -The RF switch that chooses between the on-board and external antenna is connected to `P12`, so for this reason using `P12` should be avoided unless WiFi is disabled on your application. - ### Power +Do not use the 3.3V pin **in combination with** the Vin pin to supply the device as this will damage the voltage regulator on the board. + +### Antenna placement +Always attach the appropriate antenna when using a wireless connection (LoRa / LTE / SigFox). For WiFi / BLE, it is not mandatory to use an external antenna when you did not explicitly specify this in your code. -The `Vin` pin on the FiPy can be supplied with a voltage ranging from `3.5v` to `5.5v`. The `3.3v` pin, on the other hand, is output **only** and must not be used to feed power into the FiPy otherwise the on-board regulator will be damaged. ### AT Commands -The AT commands for the Sequans Monarch modem on the FiPy are available in a PDF file. - - AT Commands for Sequans - -## Tutorials - -Tutorials on how to the FiPy module can be found in the [examples](/tutorials/introduction) section of this documentation. The following tutorials might be of interest for those using the FiPy: - -* [WiFi connection](/tutorials/all/wlan) -* [LoRaWAN node](/tutorials/lora/lorawan-abp) -* [LoRaWAN nano gateway](/tutorials/lora/lorawan-nano-gateway) -* [Sigfox](/tutorials/sigfox) -* [LTE CAT-M1](/tutorials/lte/cat-m1) -* [NB-IoT](/tutorials/lte/nb-iot) -* [BLE](/tutorials/all/ble) +The AT commands for the Sequans Monarch modem on the FiPy are available in a [PDF file](gitbook/assets/Monarch-LR5110-ATCmdRefMan-rev6_noConfidential.pdf). diff --git a/content/datasheets/development/gpy.md b/content/datasheets/development/gpy.md index bd03583..47501af 100644 --- a/content/datasheets/development/gpy.md +++ b/content/datasheets/development/gpy.md @@ -9,9 +9,7 @@ aliases: ![](/gitbook/assets/gpy-1.png) -{{% hint style="info" %}} - Please Note: We have removed the labels from the pictures in the documentation due to inconsistencies with label orientation. *The LED must be aligned above the USB socket* when inserting or removing a development board from an expansion board/Pytrack/Pysense/Pyscan. -{{% /hint %}} +> Note: Orient the RGB LED / reset button over the USB connector on any expansion board **Store**: [Buy Here](https://pycom.io/product/gpy) @@ -19,10 +17,6 @@ aliases: ## Datasheet -{{% hint style="info" %}} -Please Note: We have removed the labels from the pictures in the documentation due to inconsistencies with label orientation. *The LED must be aligned above the USB socket* when inserting or removing a development board from an expansion board/Pytrack/Pysense/Pyscan. -{{% /hint %}} - The datasheet of the GPy is available as a [PDF File](/gitbook/assets/specsheets/Pycom_002_Specsheets_GPy_v2.pdf") @@ -46,27 +40,12 @@ Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MIS ## Notes -### WiFi - -By default, upon booting up the GPy will create a WiFi access point with the SSID `gpy-wlan-XXXX`, where `XXXX` is a random 4-digit number, and the password `www.pycom.io`. - -The RF switch that selects between the on-board and external antenna is connected to `P12`, so for this reason using `P12` should be avoided unless WiFi is disabled in your application. - ### Power +Do not use the 3.3V pin **in combination with** the Vin pin to supply the device as this will damage the voltage regulator on the board. -The `Vin` pin on the GPy can be supplied with a voltage ranging from `3.5v` to `5.5v`. The `3.3v` pin on the other hand is output **only**, and must not be used to feed power into the GPy, otherwise the on-board regulator will be damaged. +### Antenna placement +Always attach the appropriate antenna when using a wireless connection (LTE). For WiFi / BLE, it is not mandatory to use an external antenna when you did not explicitly specify this in your code. ### AT Commands -The AT commands for the Sequans Monarch modem on the GPy are available in a PDF file. - - AT Commands for Sequans - -## Tutorials - -Tutorials on how to the GPy module can be found in the [examples](/tutorials/introduction) section of this documentation. The following tutorials might be of interest for those using the GPy: - -* [WiFi connection](/tutorials/all/wlan) -* [LTE CAT-M1](/tutorials/lte/cat-m1) -* [NB-IoT](/tutorials/lte/nb-iot) -* [BLE](/tutorials/all/ble) +The AT commands for the Sequans Monarch modem on the GPy are available in a [PDF file](/gitbook/assets/Monarch-LR5110-ATCmdRefMan-rev6_noConfidential.pdf) diff --git a/content/datasheets/development/lopy.md b/content/datasheets/development/lopy.md index 6847d8c..a9b234d 100644 --- a/content/datasheets/development/lopy.md +++ b/content/datasheets/development/lopy.md @@ -10,14 +10,11 @@ aliases: ![](/gitbook/assets/lopy-1.png) -{{% hint style="info" %}} -Please Note: We have removed the labels from the pictures in the documentation due to inconsistencies with label orientation. *The LED must be aligned above the USB socket* when inserting or removing a development board from an expansion board/Pytrack/Pysense/Pyscan. -{{% /hint %}} - +> Note: Orient the RGB LED / reset button over the USB connector on any expansion board **Store**: [Buy Here](https://pycom.io/product/lopy) -**Getting Started:** [Click Here](/gettingstarted/connection/lopy) +**Getting Started:** [Click Here](/gettingstarted/) ## Datasheet @@ -33,29 +30,17 @@ The pinout of the LoPy is available as a [PDF File](/gitbook/assets/lopy-pinout. ![](/gitbook/assets/lopy-pinout.png) -{{% hint style="info" %}} -Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. -{{% /hint %}} +> Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. + ## Notes -### WiFi - -By default, upon booting up the LoPy will create a WiFi access point with the SSID `lopy-wlan-XXXX`, where `XXXX` is a random 4-digit number and the password `www.pycom.io`. - ### Power +Do not use the 3.3V pin **in combination with** the Vin pin to supply the device as this will damage the voltage regulator on the board. -The `Vin` pin on the LoPy can be supplied with a voltage ranging from `3.5v` to `5.5v`. The `3.3v` pin on the other hand is output **only**, and must not be used to feed power into the LoPy, otherwise the on-board regulator will be damaged. +### Antenna placement +Always attach the appropriate antenna when using a wireless connection (LoRa). For WiFi / BLE, it is not mandatory to use an external antenna when you did not explicitly specify this in your code. ### Deep Sleep -Due to a couple of issues with the LoPy design, the module draws more current than it should while in Deep Sleep. The DC-DC switching regulator always stays in high performance mode, which is used to provide the lowest possible output ripple when the module is in use. In this mode, it draws a quiescent current of 10mA. When the regulator is put into ECO mode the quiescent current drops to 10uA. Unfortunately, the pin used to control this mode is out of the RTC domain. This means that it is not usable during Deep Sleep. This results in the regulator remaining in PWM mode, keeping its quiescent current at 10mA. The flash chip also doesn't enter into power down mode as the CS pin floats during Deep Sleep. This causes the flash chip to consume around 2mA of current. To work around this issue a ["deep sleep shield"](../../boards/deepsleep/) is available that attaches to the module and allows power to be cut off from the device. The device can then be re-enabled either through a timer or via a pin interrupt. With the Deep Sleep Shield, the current consumption during deep sleep is between 7uA and 10uA depending on the wake sources configured. - -## Tutorials - -Tutorials on the LoPy module can be found in the [examples](/tutorials/introduction) section of this documentation. The following tutorials might be of interest for those using the LoPy: - -* [WiFi connection](/tutorials/all/wlan) -* [LoRaWAN node](/tutorials/lora/lorawan-abp) -* [LoRaWAN nano gateway](/tutorials/lora/lorawan-nano-gateway) -* [BLE](/tutorials/all/ble) +Due to a couple of issues with the LoPy design, the module draws more current than it should while in Deep Sleep. The DC-DC switching regulator always stays in high performance mode, which is used to provide the lowest possible output ripple when the module is in use. In this mode, it draws a quiescent current of 10mA. When the regulator is put into ECO mode the quiescent current drops to 10uA. Unfortunately, the pin used to control this mode is out of the RTC domain. This means that it is not usable during Deep Sleep. This results in the regulator remaining in PWM mode, keeping its quiescent current at 10mA. The flash chip also doesn't enter into power down mode as the CS pin floats during Deep Sleep. This causes the flash chip to consume around 2mA of current. To work around this issue a ["deep sleep shield"](../../boards/deepsleep/) is available that attaches to the module and allows power to be cut off from the device. The device can then be re-enabled either through a timer or via a pin interrupt. With the Deep Sleep Shield, the current consumption during deep sleep is between 7uA and 10uA depending on the wake sources configured. \ No newline at end of file diff --git a/content/datasheets/development/lopy4.md b/content/datasheets/development/lopy4.md index 0152911..8b118bd 100644 --- a/content/datasheets/development/lopy4.md +++ b/content/datasheets/development/lopy4.md @@ -10,10 +10,7 @@ aliases: ![](/gitbook/assets/lopy4-1.png) -{{% hint style="info" %}} - Please Note: We have removed the labels from the pictures in the documentation due to inconsistencies with label orientation. *The LED must be aligned above the USB socket* when inserting or removing a development board from an expansion board/Pytrack/Pysense/Pyscan. -{{% /hint %}} - +> Note: Orient the RGB LED / reset button over the USB connector on any expansion board **Store**: [Buy Here](https://pycom.io/product/lopy4/) @@ -35,28 +32,19 @@ The pinout of the LoPy4 is available as a [PDF File](/gitbook/assets/lopy4-pinou ![](/gitbook/assets/lopy4-pinout.png) -{{% hint style="info" %}} -Please note that the PIN assignments for UART1 (TX1/RX1), SPI (CLK, MOSI, MISO) and I2C (SDA, SCL) are defaults and can be changed in Software. -{{% /hint %}} + +> Please note that the PIN assignments for UART1 (TX1/RX1), SPI (CLK, MOSI, MISO) and I2C (SDA, SCL) are defaults and can be changed in Software. ## Notes +### Power +Do not use the 3.3V pin **in combination with** the Vin pin to supply the device as this will damage the voltage regulator on the board. -### WiFi +### Antenna placement +Always attach the appropriate antenna when using a wireless connection (LoRa / SigFox). For WiFi / BLE, it is not mandatory to use an external antenna when you did not explicitly specify this in your code. -By default, upon booting up the LoPy4 will create a WiFi access point with the SSID `lopy4-wlan-XXXX`, where `XXXX` is a random 4-digit number and the password `www.pycom.io`. - -The RF switch that chooses between the on-board and external antenna is connected to `P12`, so for this reason using `P12` should be avoided unless WiFi is disabled in your application. ### Power +Do not use the 3.3V pin **in combination with** the Vin pin to supply the device as this will damage the voltage regulator on the board. -The `Vin` pin on the LoPy4 can be supplied with a voltage ranging from `3.5v` to `5.5v`. The `3.3v` pin on the other hand is output **only**, and must not be used to feed power into the LoPy4, otherwise the on-board regulator will be damaged. - -## Tutorials - -Tutorials on the LoPy4 module can be found in the [examples](/tutorials/introduction) section of this documentation. The following tutorials might be of interest for those using the LoPy4: - -* [WiFi connection](/tutorials/all/wlan) -* [LoRaWAN node](/tutorials/lora/lorawan-abp) -* [LoRaWAN nano gateway](/tutorials/lora/lorawan-nano-gateway) -* [Sigfox](/tutorials/sigfox) -* [BLE](/tutorials/all/ble) +### Antennas +Always attach the appropriate antenna when using a wireless connection (LoRa / LTE). For WiFi / BLE, it is not mandatory to use an external antenna when you did not explicitly specify this in your code. diff --git a/content/datasheets/development/sipy.md b/content/datasheets/development/sipy.md index ae465d1..49bb2e3 100644 --- a/content/datasheets/development/sipy.md +++ b/content/datasheets/development/sipy.md @@ -9,11 +9,7 @@ aliases: ![](/gitbook/assets/sipy-2.png) -{{% hint style="info" %}} - Please Note: We have removed the labels from the pictures in the documentation due to inconsistencies with label orientation. *The LED must be aligned above the USB socket* when inserting or removing a development board from an expansion board/Pytrack/Pysense/Pyscan. -{{% /hint %}} - - +> Note: Orient the RGB LED / reset button over the USB connector on any expansion board **Store**: [Buy Here](https://pycom.io/product/sipy) @@ -32,28 +28,17 @@ The pinout of the SiPy is available as a [PDF File](/gitbook/assets/sipy-pinout. ![](/gitbook/assets/sipy-pinout.png) -{{% hint style="info" %}} -Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. -{{% /hint %}} +> Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. ## Notes -### WiFi - -By default, upon booting up the SiPy will create a WiFi access point with the SSID `sipy-wlan-XXXX`, where `XXXX` is a random 4-digit number, and the password `www.pycom.io`. - ### Power +Do not use the 3.3V pin **in combination with** the Vin pin to supply the device as this will damage the voltage regulator on the board. -The `Vin` pin on the SiPy can be supplied with a voltage ranging from `3.5v` to `5.5v`. The `3.3v` pin on the other hand is output **only**, and must not be used to feed power into the SiPy, otherwise the on-board regulator will be damaged. +### Antenna placement +Always attach the appropriate antenna when using a wireless connection (SigFox). For WiFi / BLE, it is not mandatory to use an external antenna when you did not explicitly specify this in your code. ### Deep Sleep Due to a couple of issues with the SiPy design, the module draws more current than it should while in Deep Sleep. The DC-DC switching regulator always stays in high performance mode, which is used to provide the lowest possible output ripple when the module is in use. In this mode, it draws a quiescent current of 10mA. When the regulator is put into ECO mode the quiescent current drops to 10uA. Unfortunately, the pin used to control this mode is out of the RTC domain. This means that it is not usable during Deep Sleep. This results in the regulator remaining in PWM mode, keeping its quiescent current at 10mA. The flash chip also doesn't enter into power down mode as the CS pin floats during Deep Sleep. This causes the flash chip to consume around 2mA of current. To work around this issue a ["deep sleep shield"](../../boards/deepsleep/) is available that attaches to the module and allows power to be cut off from the device. The device can then be re-enabled either through a timer or via a pin interrupt. With the Deep Sleep Shield, the current consumption during deep sleep is between 7uA and 10uA depending on the wake sources configured. -## Tutorials - -Tutorials on the SiPy module can be found in the [examples](/tutorials/introduction) section of this documentation. The following tutorials might be of interest for those using the SiPy: - -* [WiFi connection](/tutorials/all/wlan) -* [Sigfox](/tutorials/sigfox) -* [BLE](/tutorials/all/ble) diff --git a/content/datasheets/development/wipy2.md b/content/datasheets/development/wipy2.md index 6907ac7..c406c33 100644 --- a/content/datasheets/development/wipy2.md +++ b/content/datasheets/development/wipy2.md @@ -9,10 +9,7 @@ aliases: ![](/gitbook/assets/wipy2-1.png) -{{% hint style="info" %}} - Please Note: We have removed the labels from the pictures in the documentation due to inconsistencies with label orientation. *The LED must be aligned above the USB socket* when inserting or removing a development board from an expansion board/Pytrack/Pysense/Pyscan. -{{% /hint %}} - +> Note: Orient the RGB LED / reset button over the USB connector on any expansion board **Store**: Discontinued, See [WiPy3](../wipy3) @@ -31,19 +28,15 @@ The pinout of the WiPy2 is available as a [PDF File](/gitbook/assets/wipy2-pinou ![](/gitbook/assets/wipy2-pinout.png) -{{% hint style="info" %}} -Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. -{{% /hint %}} +> Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. ## Notes -### WiFi - -By default, upon booting up the WiPy2 will create a WiFi access point with the SSID `wipy-wlan-XXXX`, where `XXXX` is a random 4-digit number, and the password `www.pycom.io`. - ### Power +Do not use the 3.3V pin **in combination with** the Vin pin to supply the device as this will damage the voltage regulator on the board. -The `Vin` pin on the WiPy2 can be supplied with a voltage ranging from `3.5v` to `5.5v`. The `3.3v` pin on the other hand is output **only**, and must not be used to feed power into the WiPy2, otherwise the on-board regulator will be damaged. +### Antenna placement +Always attach the appropriate antenna when using a wireless connection. For WiFi / BLE, it is not mandatory to use an external antenna when you did not explicitly specify this in your code. ### Deep Sleep diff --git a/content/datasheets/development/wipy3.md b/content/datasheets/development/wipy3.md index b324163..5d99ef4 100644 --- a/content/datasheets/development/wipy3.md +++ b/content/datasheets/development/wipy3.md @@ -9,9 +9,7 @@ aliases: ![](/gitbook/assets/wipy3.png) -{{% hint style="info" %}} - Please Note: We have removed the labels from the pictures in the documentation due to inconsistencies with label orientation. *The LED must be aligned above the USB socket* when inserting or removing a development board from an expansion board/Pytrack/Pysense/Pyscan. -{{% /hint %}} +> Note: Orient the RGB LED / reset button over the USB connector on any expansion board **Store**: [Buy Here](https://pycom.io/product/wipy-3-0/) @@ -35,9 +33,8 @@ The pinout of the WiPy3 is available as a [PDF File](/gitbook/assets/wipy3-pinou ![](/gitbook/assets/wipy3-pinout.png) -{{% hint style="info" %}} -Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. -{{% /hint %}} +> Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. + ## Differences from WiPy 2.0 @@ -48,6 +45,13 @@ Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MIS ## Notes +### Power +Do not use the 3.3V pin **in combination with** the Vin pin to supply the device as this will damage the voltage regulator on the board. + +### Antenna placement +Always attach the appropriate antenna when using a wireless connection. For WiFi / BLE, it is not mandatory to use an external antenna when you did not explicitly specify this in your code. + + ### WiFi By default, upon booting up the WiPy3 will create a WiFi access point with the SSID `wipy-wlan-XXXX`, where `XXXX` is a random 4-digit number, and the password `www.pycom.io`. diff --git a/content/datasheets/oem/g01.md b/content/datasheets/oem/g01.md index ea009c2..ac848ab 100644 --- a/content/datasheets/oem/g01.md +++ b/content/datasheets/oem/g01.md @@ -32,21 +32,14 @@ The G01 is certified for [CE RED](/gitbook/assets/17-213357_red-certificate_pyco The drawings for the G01 is available as a [PDF File](/gitbook/assets/g01-drawing.pdf) -{{% hint style="info" %}} -Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. -{{% /hint %}} +> Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. + ## AT Commands -The AT commands for the Sequans Monarch modem on the G01 are available in a PDF file. +The AT commands for the Sequans Monarch modem on the G01 are available in a [PDF file](/gitbook/assets/Monarch-LR5110-ATCmdRefMan-rev6_noConfidential.pdf). - - AT Commands for Sequans ## Tutorials -Tutorials on the G01 module can be found in the [examples](/tutorials/introduction) section of this documentation. The following tutorials might be of interest for those using the G01: +Tutorials on the G01 module can be found in the [examples](/tutorials/) section of this documentation. -* [WiFi connection](/tutorials/all/wlan) -* [LTE CAT-M1](/tutorials/lte/cat-m1) -* [NB-IoT](/tutorials/lte/nb-iot) -* [BLE](/tutorials/all/ble) diff --git a/content/datasheets/oem/l01.md b/content/datasheets/oem/l01.md index 6cb8f8e..2ea349a 100644 --- a/content/datasheets/oem/l01.md +++ b/content/datasheets/oem/l01.md @@ -29,16 +29,9 @@ The pinout of the L01 is available as a [PDF File](/gitbook/assets/l01-pinout.pd The drawings for the L01 is available as a [PDF File](/gitbook/assets/l01-drawing.pdf) +> Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. -{{% hint style="info" %}} -Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. -{{% /hint %}} ## Tutorials -Tutorials on the L01 module can be found in the [examples](/tutorials/introduction) section of this documentation. The following tutorials might be of interest for those using the L01: - -* [WiFi connection](/tutorials/all/wlan) -* [LoRaWAN node](/tutorials/lora/lorawan-abp) -* [LoRaWAN nano gateway](/tutorials/lora/lorawan-nano-gateway) -* [BLE](/tutorials/all/ble) +Tutorials on the L01 module can be found in the [examples](/tutorials/) section of this documentation. \ No newline at end of file diff --git a/content/datasheets/oem/l04.md b/content/datasheets/oem/l04.md index 84dfcd1..9910333 100644 --- a/content/datasheets/oem/l04.md +++ b/content/datasheets/oem/l04.md @@ -28,10 +28,8 @@ The pinout of the L04 is available as a [PDF File](/gitbook/assets/l04-pinout.pd The drawings for the L04 are available as a [PDF File](/gitbook/assets/l04-drawing.pdf) -{{% hint style="info" %}} -Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. -{{% /hint %}} +> Please note that the PIN assignments for UART1 \(TX1/RX1\), SPI \(CLK, MOSI, MISO\) and I2C \(SDA, SCL\) are defaults and can be changed via software. ## Power Consumption @@ -46,10 +44,4 @@ Here are some basic power usage measurements for various scenarios. ## Tutorials -Tutorials on the L04 module can be found in the [examples](/tutorials/introduction) section of this documentation. The following tutorials might be of interest for those using the L04: - -* [WiFi connection](/tutorials/all/wlan) -* [LoRaWAN node](/tutorials/lora/lorawan-abp) -* [LoRaWAN nano gateway](/tutorials/lora/lorawan-nano-gateway) -* [Sigfox](/tutorials/sigfox) -* [BLE](/tutorials/all/ble) +Tutorials on the L04 module can be found in the [examples](/tutorials/ section of this documentation.