From 24ab1accfcf1cc44ffef5578f45df24ce15c4f69 Mon Sep 17 00:00:00 2001 From: gijsio <67470426+gijsio@users.noreply.github.com> Date: Fri, 11 Sep 2020 10:15:18 +0200 Subject: [PATCH] fixed more broken links using spider --- config.toml | 2 +- content/advance/cli.md | 2 +- content/datasheets/_index.md | 1 + content/datasheets/development/fipy.md | 2 +- content/datasheets/development/gpy.md | 4 ++-- content/datasheets/development/lopy.md | 2 +- content/datasheets/development/sipy.md | 2 +- content/datasheets/development/wipy2.md | 6 +++--- content/datasheets/expansionboards/pyscan.md | 2 +- content/datasheets/expansionboards/pysense2.md | 2 +- content/datasheets/expansionboards/pytrack.md | 2 +- content/datasheets/oem/l01.md | 2 +- content/firmwareapi/micropython/usocket.md | 2 +- content/firmwareapi/notes.md | 2 +- content/firmwareapi/pycom/machine/adc.md | 6 +++--- content/firmwareapi/pycom/machine/pygate.md | 2 +- content/firmwareapi/pycom/pycom.md | 2 +- content/gettingstarted/_index.md | 2 +- content/gettingstarted/registration/_index.md | 2 +- content/gettingstarted/registration/lora/_index.md | 4 ++-- content/gettingstarted/registration/lora/ttn.md | 2 +- content/pybytes/_index.md | 8 ++++---- content/pybytes/api/_index.md | 2 +- content/pybytes/dashboard.md | 2 +- content/pybytes/networks/sigfox/devkit.md | 2 +- content/pymesh/pymesh-br.md | 2 +- content/pymesh/security.md | 4 ++-- content/tutorials/basic/sleep.md | 2 +- content/tutorials/expansionboards/pygate.md | 2 +- content/tutorials/introduction.md | 2 +- 30 files changed, 40 insertions(+), 39 deletions(-) diff --git a/config.toml b/config.toml index 02350f9..f814b3e 100644 --- a/config.toml +++ b/config.toml @@ -1357,7 +1357,7 @@ theme = "doc-theme" [[menu.main]] name = "Write configuration" - url = "/pybytes/api/write_config/" + url = "/pybytes/api/update_config/" identifier = "pybytes@api@write_config" parent = "pybytes@api" weight = 38 diff --git a/content/advance/cli.md b/content/advance/cli.md index e804f0b..753fcea 100644 --- a/content/advance/cli.md +++ b/content/advance/cli.md @@ -2,7 +2,7 @@ title: "CLI Updater" aliases: - advance/cli.html - - advance/cli.md + - advance/cli - chapter/advance/cli --- diff --git a/content/datasheets/_index.md b/content/datasheets/_index.md index e0447bb..9e08fb7 100644 --- a/content/datasheets/_index.md +++ b/content/datasheets/_index.md @@ -23,6 +23,7 @@ The follow pages contain all information relating to each product, for example: ## OEM modules - [W01](/datasheets/oem/w01/) +- [G01](/datasheets/oem/g01/) - [L01](/datasheets/oem/l01/) - [L01 OEM Baseboard](/datasheets/oem/l01_reference/) - [L04](/datasheets/oem/l04/) diff --git a/content/datasheets/development/fipy.md b/content/datasheets/development/fipy.md index d7cbf83..f6973f8 100644 --- a/content/datasheets/development/fipy.md +++ b/content/datasheets/development/fipy.md @@ -46,4 +46,4 @@ Always attach the appropriate antenna when using a wireless connection (LoRa / L ### AT Commands -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). +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 3eb900a..b0b9f08 100644 --- a/content/datasheets/development/gpy.md +++ b/content/datasheets/development/gpy.md @@ -20,9 +20,9 @@ aliases: The datasheet of the GPy is available as a [PDF File](/gitbook/assets/specsheets/Pycom_002_Specsheets_GPy_v2.pdf) -The drawing of the LTE-M antenna is available as a [PDF File](/gitbook/assets/lte-m-antenna-drawing.pdf") +The drawing of the LTE-M antenna is available as a [PDF File](/gitbook/assets/lte-m-antenna-drawing.pdf) -The Gpy is certified for [CE RED](/gitbook/assets/gpy_c03-b0-red-final.pdf) and [FCC DSS](/gitbook/assets/pycom-2ajmtgpy01r-fcc-grant-dss.pdf) [FCC DTS](/gitbook/assets/pycom-2ajmtgpy01r-fcc-grant-dts.pdf) [FCC TNB](//gitbook/assets/pycom-2ajmtgpy01r-fcc-grant-tnb.pdf) +The Gpy is certified for [CE RED](/gitbook/assets/c03-b0-red-gpy.pdf) and [FCC DSS](/gitbook/assets/pycom-2ajmtgpy01r-fcc-grant-dss.pdf) [FCC DTS](/gitbook/assets/pycom-2ajmtgpy01r-fcc-grant-dts.pdf) [FCC TNB](//gitbook/assets/pycom-2ajmtgpy01r-fcc-grant-tnb.pdf) [RCM](/gitbook/assets/RCM-Gpy.pdf) [ROHS certification](/gitbook/assets/RoHs_declarations/RoHS-for-GPy(8217-00090P)-20190523.pdf) diff --git a/content/datasheets/development/lopy.md b/content/datasheets/development/lopy.md index 7010cb8..f6816fc 100644 --- a/content/datasheets/development/lopy.md +++ b/content/datasheets/development/lopy.md @@ -21,7 +21,7 @@ aliases: The datasheet of the LoPy is available as a [PDF File](/gitbook/assets/specsheets/Pycom_002_Specsheets_LoPy_v2.pdf) -The Lopy is certified for [CE RED](/gitbook/assets/16-213298_expertise_pycom_lopy-1.0r.pdf) and [FCC ACC](/gitbook/assets/2090acc16_grant.pdf") [FCC BCC](/gitbook/assets/2090bcc16_grant.pdf) [FCC CCC](/gitbook/assets/2090ccc16_grant.pdf) +The Lopy is certified for [CE RED](/gitbook/assets/16-213298_expertise_pycom_lopy-1.0r.pdf) and [FCC ACC](/gitbook/assets/2090acc16_grant.pdf) [FCC BCC](/gitbook/assets/2090bcc16_grant.pdf) [FCC CCC](/gitbook/assets/2090ccc16_grant.pdf) ## Pinout diff --git a/content/datasheets/development/sipy.md b/content/datasheets/development/sipy.md index 49bb2e3..ce4a8df 100644 --- a/content/datasheets/development/sipy.md +++ b/content/datasheets/development/sipy.md @@ -19,7 +19,7 @@ aliases: The datasheet of the SiPy is available as a [PDF File](/gitbook/assets/specsheets/Pycom_002_Specsheets_SiPy_v2.pdf) -The Sipy is certified for [CE RED](gitbook/assets/17-210585_expertise_sipy_sipy-1.0.pdf) +The Sipy is certified for [CE RED](/gitbook/assets/17-210585_expertise_sipy_sipy-1.0.pdf) ## Pinout diff --git a/content/datasheets/development/wipy2.md b/content/datasheets/development/wipy2.md index f188380..80d0994 100644 --- a/content/datasheets/development/wipy2.md +++ b/content/datasheets/development/wipy2.md @@ -40,11 +40,11 @@ Always attach the appropriate antenna when using a wireless connection. For WiFi ### Deep Sleep -Due to a couple of issues with the WiPy2 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. +Due to a couple of issues with the WiPy2 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"]../expansionboards/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 WiPy2 module can be found in the [examples](/tutorials/introduction) section of this documentation. The following tutorials might be of interest for those using the WiPy2: -* [WiFi connection](/tutorials/all/wlan) -* [BLE](/tutorials/all/ble) +* [WiFi connection](/tutorials/networks/wlan) +* [BLE](/tutorials/networks/ble) diff --git a/content/datasheets/expansionboards/pyscan.md b/content/datasheets/expansionboards/pyscan.md index bfc4b97..3a41140 100644 --- a/content/datasheets/expansionboards/pyscan.md +++ b/content/datasheets/expansionboards/pyscan.md @@ -29,7 +29,7 @@ The datasheet of the Pyscan is available as a [PDF File](/gitbook/assets/pyscan- ## Driver -The Windows 7 driver for Pyscan is located [here](/pytrackpysense/installation/firmware). +The Windows 7 driver for Pyscan is located [here](/gettingstarted/software/drivers/). For other Operating Systems, no driver is required. diff --git a/content/datasheets/expansionboards/pysense2.md b/content/datasheets/expansionboards/pysense2.md index a10e8d4..98f84f1 100644 --- a/content/datasheets/expansionboards/pysense2.md +++ b/content/datasheets/expansionboards/pysense2.md @@ -11,7 +11,7 @@ aliases: ## Datasheet -The datasheet of the Pysense 2.0X is available as a [PDF File](gitbook/assets/PySense2X_specsheet.pdf) +The datasheet of the Pysense 2.0X is available as a [PDF File](/gitbook/assets/PySense2X_specsheet.pdf) ## Pinout diff --git a/content/datasheets/expansionboards/pytrack.md b/content/datasheets/expansionboards/pytrack.md index 3abe232..ba90570 100644 --- a/content/datasheets/expansionboards/pytrack.md +++ b/content/datasheets/expansionboards/pytrack.md @@ -36,4 +36,4 @@ The board features a single cell Li-Ion/Li-Po charger with a JST PHR‑2 connect ### 3D model for case design -* Please see the [3D model](/gitbook/assets/PyTrack_v1.1.step") (step format) +* Please see the [3D model](/gitbook/assets/PyTrack_v1.1.step) (step format) diff --git a/content/datasheets/oem/l01.md b/content/datasheets/oem/l01.md index 2ea349a..0f32590 100644 --- a/content/datasheets/oem/l01.md +++ b/content/datasheets/oem/l01.md @@ -13,7 +13,7 @@ aliases: The drawings for the L01 are available as a [PDF File](/gitbook/assets/specsheets/Pycom_002_Specsheets_L01_v2.pdf) -The L01 is certified for [CE RED](gitbook/assets/17-213356_red-certificate_pycom_l01-1.0.pdf) and [FCC DSS](/gitbook/assets/172181413_aa_00_final.pdf) +The L01 is certified for [CE RED](/gitbook/assets/17-213356_red-certificate_pycom_l01-1.0.pdf) and [FCC DSS](/gitbook/assets/172181413_aa_00_final.pdf) [FCC DTS](/gitbook/assets/172181414_aa_00_final.pdf) [FCC DAA](/gitbook/assets/172181411_aa_00_final.pdf) [RCM](/gitbook/assets/RCM-L01.pdf) [ROHS certification](/gitbook/assets/RoHs_declarations/RoHS-for-L01(f8217-00088P)-20190523.pdf) diff --git a/content/firmwareapi/micropython/usocket.md b/content/firmwareapi/micropython/usocket.md index a0224fe..7811d49 100644 --- a/content/firmwareapi/micropython/usocket.md +++ b/content/firmwareapi/micropython/usocket.md @@ -129,7 +129,7 @@ The socket must be in blocking mode; it can have a timeout, but the file object' #### socket.read(size) -Read up to size bytes from the socket. Return a bytes object. If `size` is not given, it behaves just like [`socket.readall()`](../usocket.md#socket-readall), see below. +Read up to size bytes from the socket. Return a bytes object. If `size` is not given, it behaves just like [`socket.readall()`](../usocket#socket-readall), see below. #### socket.readall() diff --git a/content/firmwareapi/notes.md b/content/firmwareapi/notes.md index c108d15..00a756d 100644 --- a/content/firmwareapi/notes.md +++ b/content/firmwareapi/notes.md @@ -14,7 +14,7 @@ These limitations were raised by handling the interrupt events differently. When 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) 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. +Currently, there are 2 classes that support interrupts; the [`Alarm`](../pycom/machine/timer#class-timer-alarm-handler-none-s-ms-us-arg-none-periodic-false) and [`Pin`](../pycom/machine/pin) 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**. diff --git a/content/firmwareapi/pycom/machine/adc.md b/content/firmwareapi/pycom/machine/adc.md index c980e71..fa9c5ce 100644 --- a/content/firmwareapi/pycom/machine/adc.md +++ b/content/firmwareapi/pycom/machine/adc.md @@ -9,13 +9,13 @@ aliases: ## class ADC – Analog to Digital Conversion -{{% development version="" style="dev" %}} +{{% development version="" style="block" %}} {{% /development %}} ### Quick Usage Example -{{% development version="" style="dev" %}} +{{% development version="" style="block" %}} {{% /development %}} @@ -30,7 +30,7 @@ val = apin() # read an analog value ## Constructors -### class machine.ADC([id=0]) +### class machine.ADC([id=0] {{% development version="" style="inline" %}}hello {{% /development %}}) Create an ADC object; associate a channel with a pin. For more info check the hardware section. diff --git a/content/firmwareapi/pycom/machine/pygate.md b/content/firmwareapi/pycom/machine/pygate.md index e9d3d8b..7d0c8e1 100644 --- a/content/firmwareapi/pycom/machine/pygate.md +++ b/content/firmwareapi/pycom/machine/pygate.md @@ -6,7 +6,7 @@ aliases: - chapter/firmwareapi/pycom/machine/pygate --- -The Pygate is an 8-channel LoRaWAN gateway. Connect a WiPy, Gpy or LoPy4 board to the Pygate and flash the Pygate firmware. See the [Pygate tutorial](/tutorials/all/pygate) to get started. +The Pygate is an 8-channel LoRaWAN gateway. Connect a WiPy, Gpy or LoPy4 board to the Pygate and flash the Pygate firmware. See the [Pygate tutorial](/tutorials/expansionboards/pygate) to get started. ## Methods diff --git a/content/firmwareapi/pycom/pycom.md b/content/firmwareapi/pycom/pycom.md index f93edc4..ba929cd 100644 --- a/content/firmwareapi/pycom/pycom.md +++ b/content/firmwareapi/pycom/pycom.md @@ -193,7 +193,7 @@ with open(APPIMG, "rb") as f: Instead of reading the data to be written from a file, it can obviously also be received from a server using any suitable protocol, without the need to store it in the devices file system. -> For more information about the OTA process, go [here](/updatefirmware/OTA/) +> For more information about the OTA process, go [here](/updatefirmware/ota/) ### pycom.diff_update_enabled() Provides the status of the differential update feature. Returns `True` if differential update is enabled and `False` otherwise. `DIFF_UPDATE_ENABLED` build flag can be used to enable the differential update feature. diff --git a/content/gettingstarted/_index.md b/content/gettingstarted/_index.md index 8c0603f..1953569 100644 --- a/content/gettingstarted/_index.md +++ b/content/gettingstarted/_index.md @@ -30,7 +30,7 @@ This step works the same for all our development boards and expansion boards. In ![](/gitbook/assets/expansion_board_3_lopy4.png) ->Note: If you do not have an expansion board, you are able to use a [USB-Serial converter](/gettinstarted/programming/usbserial/) or [WiFi](/gettingstarted/programming/ftp/) to connect. +>Note: If you do not have an expansion board, you are able to use a [USB-Serial converter](/gettingstarted/programming/usbserial/) or [WiFi](/gettingstarted/programming/ftp/) to connect. ## Step 2: Setting up your computer diff --git a/content/gettingstarted/registration/_index.md b/content/gettingstarted/registration/_index.md index bcc3e06..7348163 100644 --- a/content/gettingstarted/registration/_index.md +++ b/content/gettingstarted/registration/_index.md @@ -10,7 +10,7 @@ Some of our devices require registration before you can utilise specific feature * [Objenious](/gettingstarted/registration/lora/objenious/) ## Other * [SigFox](/gettingstarted/registration/sigfox/) -* [Cellular](/gettinsgtarted/registration/cellular/) +* [Cellular](/gettingstarted/registration/cellular/) >**Not all Pycom devices require activation**; most features work immediately out of the box! diff --git a/content/gettingstarted/registration/lora/_index.md b/content/gettingstarted/registration/lora/_index.md index a8138a0..cec77eb 100644 --- a/content/gettingstarted/registration/lora/_index.md +++ b/content/gettingstarted/registration/lora/_index.md @@ -27,11 +27,11 @@ The output will be a hex string like: `70B3D5499585FCA1`. Once you have this you #### OTAA -If you wish to connect via OTAA (which is the recommended method) the network will provide you with an `Application EUI` and `Application Key`. The former identifies what application your device is connecting to, the latter is a shared secret key unique to your device to generate the session keys that prove its identity to the network. Once you have these you can use the [LoRaWAN OTAA example](/tutorials/lora/lorawan-otaa) code to connect to the network. +If you wish to connect via OTAA (which is the recommended method) the network will provide you with an `Application EUI` and `Application Key`. The former identifies what application your device is connecting to, the latter is a shared secret key unique to your device to generate the session keys that prove its identity to the network. Once you have these you can use the [LoRaWAN OTAA example](/tutorials/networks/lora/lorawan-otaa) code to connect to the network. #### ABP -With ABP the encryption keys enabling communication with the network are preconfigured in the device. The network will need to provide you with a `Device Address`, `Network Session Key` and `Application Session Key`. Once you have these you can use the [LoRaWAN ABP example](/tutorials/lora/lorawan-abp) code to connect to the network. +With ABP the encryption keys enabling communication with the network are preconfigured in the device. The network will need to provide you with a `Device Address`, `Network Session Key` and `Application Session Key`. Once you have these you can use the [LoRaWAN ABP example](/tutorials/networks/lora/lorawan-abp) code to connect to the network. ### Networks diff --git a/content/gettingstarted/registration/lora/ttn.md b/content/gettingstarted/registration/lora/ttn.md index ab6f8d9..de169d4 100644 --- a/content/gettingstarted/registration/lora/ttn.md +++ b/content/gettingstarted/registration/lora/ttn.md @@ -45,7 +45,7 @@ Once the device has been added, change the `Activation Method` between `OTAA` an ## Register a Nano-Gateway -You can also setup your Pycom module to act as a gateway with The Things Network. The code required to do this can be found [here](/tutorials/lora/lorawan-nano-gateway). +You can also setup your Pycom module to act as a gateway with The Things Network. The code required to do this can be found [here](/tutorials/networks/lora/lorawan-nano-gateway). Inside the TTN Console, there are two options, `Applications` and `Gateways`. Select `Gateways` and then click on `register Gateway`. This will allow for the set up and registration of a new nano-gateway. diff --git a/content/pybytes/_index.md b/content/pybytes/_index.md index 5f3f407..75d15be 100644 --- a/content/pybytes/_index.md +++ b/content/pybytes/_index.md @@ -31,8 +31,8 @@ In a nutshell, Pybytes is an environment designed to optimise your IoT applicati ## Let's get started! -* [Getting started with Pybytes](/pybytes/getstarted) -* [Connect your Pycom module to Pybytes](/pybytes/connect) -* [Visualise data from your device](/pybytes/dashboard) -* [LoRa Servers](/pybytes/lora) +* [Getting started with Pybytes](/pybytes/getstarted/) +* [Connect your Pycom module to Pybytes](/pybytes/connect/) +* [Visualise data from your device](/pybytes/dashboard/) +* [LoRa Servers](/pybytes/networks/lora/) * ​[Integrations with external services](/pybytes/integrations/index.html)​ diff --git a/content/pybytes/api/_index.md b/content/pybytes/api/_index.md index 55d2510..d373e84 100644 --- a/content/pybytes/api/_index.md +++ b/content/pybytes/api/_index.md @@ -30,7 +30,7 @@ There are multiple debug levels, the lowest is 0 which is for warnings only and * [Activate](activate) -* [Connect](connect) +* [Connect](connect_device) * [Connect LTE](connect_lte) diff --git a/content/pybytes/dashboard.md b/content/pybytes/dashboard.md index dc80039..86a39c8 100644 --- a/content/pybytes/dashboard.md +++ b/content/pybytes/dashboard.md @@ -18,7 +18,7 @@ The first step is to have your python application uploaded and running on your P 1. Install the [Pymakr](https://atom.io/packages/pymakr) plugin. - (We highly recommend using Pymakr with Atom, but you can also use Pymakr with [VS Code](https://marketplace.visualstudio.com/items?itemName=pycom.Pymakr)). Learn more about Pymakr [here](/pymakr). + (We highly recommend using Pymakr with Atom, but you can also use Pymakr with [VS Code](https://marketplace.visualstudio.com/items?itemName=pycom.Pymakr)). 2. In Atom create a project folder `my-first-wipy` (any other name will work as well). 4. In your project folder create the `main.py` file 3. Copy and paste the following code into your `main.py` diff --git a/content/pybytes/networks/sigfox/devkit.md b/content/pybytes/networks/sigfox/devkit.md index eb8d356..e48c957 100644 --- a/content/pybytes/networks/sigfox/devkit.md +++ b/content/pybytes/networks/sigfox/devkit.md @@ -47,4 +47,4 @@ This is not an issue with Custom contract, where _device type_ on Sigfox backend ## Troubleshooting -[Disengage Sigfox sequence number](/tutorials/sigfox#disengage-sequence-number) +[Disengage Sigfox sequence number](/tutorials/networks/sigfox#disengage-sequence-number) diff --git a/content/pymesh/pymesh-br.md b/content/pymesh/pymesh-br.md index 202153f..ed9f9b8 100644 --- a/content/pymesh/pymesh-br.md +++ b/content/pymesh/pymesh-br.md @@ -21,7 +21,7 @@ Several things must be accomplished: ## Border Router using CLI -As explained in [Pymesh CLI - Border Router section](pymesh/lib-cli/#border-router-specific), using commands `br` and `brs`, a simple test scenario can be easily implemented. +As explained in [Pymesh CLI - Border Router section](/pymesh/lib-cli/#border-router-specific), using commands `br` and `brs`, a simple test scenario can be easily implemented. ## Border Router using Pymesh API diff --git a/content/pymesh/security.md b/content/pymesh/security.md index 1e4113a..532ebb4 100644 --- a/content/pymesh/security.md +++ b/content/pymesh/security.md @@ -30,10 +30,10 @@ The challenge is in distributing the keys used for encryption(decryption), this Symmetric-key algorithms are algorithms for cryptography that use the same cryptographic keys for both encryption of plaintext and decryption of ciphertext. More info could be checked on [Symmetric-key algorithm](https://en.wikipedia.org/wiki/Symmetric-key_algorithm). -A micropython example script can be seen [here](../../firmwareapi/pycom/aes.md) using AES 128, 192 or 256 bits keys (`crypto.AES` class). +A micropython example script can be seen [here](../../firmwareapi/pycom/aes/) using AES 128, 192 or 256 bits keys (`crypto.AES` class). ### Asymmetric encryption Public-key cryptography, or asymmetric cryptography, is a cryptographic system that uses pairs of keys: public keys which may be disseminated widely, and private keys which are known only to the owner. More info could be checked on [Public-key cryptography](https://en.wikipedia.org/wiki/Public-key_cryptography). -A micropython example script can be seen [here](../../firmwareapi/micropython/ucrypto.md) using RSA 2048 bits keys (`crypto.rsa_encrypt()` method). +A micropython example script can be seen [here](../../firmwareapi/micropython/ucrypto/) using RSA 2048 bits keys (`crypto.rsa_encrypt()` method). diff --git a/content/tutorials/basic/sleep.md b/content/tutorials/basic/sleep.md index 2277af8..5c541b2 100644 --- a/content/tutorials/basic/sleep.md +++ b/content/tutorials/basic/sleep.md @@ -82,4 +82,4 @@ print("This will never be printed") >Note: Using `deepsleep()` will also stop the USB connection. Be wary of that when trying to upload new code to the device! -For the Pysense, Pytrack and Pyscan expansionboards, an additional sleep function is available. You can find out more about that [here](../expansionboards/sleep/) \ No newline at end of file +For the Pysense, Pytrack and Pyscan expansionboards, an additional sleep function is available. You can find out more about that [here](/tutorials/expansionboards/sleep/) \ No newline at end of file diff --git a/content/tutorials/expansionboards/pygate.md b/content/tutorials/expansionboards/pygate.md index ec9e5b2..bb58a26 100644 --- a/content/tutorials/expansionboards/pygate.md +++ b/content/tutorials/expansionboards/pygate.md @@ -8,7 +8,7 @@ While the Pygate shield has the radio chips required to act as a LoRaWAN gateway A USB connection is recommended for the initial firmware update of the Pycom development module (WiPy 3, GPy, LoPy4) and to upload the configuration & start-up script. The module can be updated over the air via WiFi / LTE-M (depending on network capabilities) or via Ethernet connection which allows installation of the gateway in remote locations. -The Pygate board can have the PyEthernet adapter connected which allows an Ethernet connection. The PyEthernet also supports PoE. Please check the separate [page and warning for PoE-NI!](/tutorials/all/poe) +The Pygate board can have the PyEthernet adapter connected which allows an Ethernet connection. The PyEthernet also supports PoE. Please check the separate [page and warning for PoE-NI!](/tutorials/networkprotocols/poe/) ### Quickstart diff --git a/content/tutorials/introduction.md b/content/tutorials/introduction.md index aaaaacc..9586af0 100644 --- a/content/tutorials/introduction.md +++ b/content/tutorials/introduction.md @@ -14,7 +14,7 @@ This section contains tutorials and examples for use with Pycom modules and Expa General Pycom tutorials contains tutorials that may be run on any Pycom device, such as connecting to a WiFi network, Bluetooth, controlling I/O pins etc. Later sections are specific to the LoPy and SiPy devices such as setting up a LoRa node or connecting to the Sigfox network. The final sections are related to examples using the Pytrack and Pysense. -Before starting, ensure that any Pycom devices are running the latest firmware; for instructions see [Firmware Updates](/gettingstarted/installation/firmwaretool). +Before starting, ensure that any Pycom devices are running the latest firmware; for instructions see [Firmware Updates](/updatefirmware/device/). The source code for these tutorials, along with the required libraries can be found in in the [pycom-libraries](https://github.com/pycom/pycom-libraries) repository.