diff --git a/docfx/Common_Assets/Meadow_F7_Micro_Pinout.svg b/docfx/Common_Assets/Meadow_F7_Micro_Pinout.svg
index 676af9592..f785cdf4a 100644
--- a/docfx/Common_Assets/Meadow_F7_Micro_Pinout.svg
+++ b/docfx/Common_Assets/Meadow_F7_Micro_Pinout.svg
@@ -8,7 +8,7 @@
- Meadow F7 Micro IO
+ Meadow F7 Micro v1 IO
diff --git a/docs/Hardware/Reference/Meadow_Hardware/Meadow_F7/F7v1/index.md b/docs/Hardware/Reference/Meadow_Hardware/Meadow_F7/F7v1/index.md
index f49d54f3c..354df69fe 100644
--- a/docs/Hardware/Reference/Meadow_Hardware/Meadow_F7/F7v1/index.md
+++ b/docs/Hardware/Reference/Meadow_Hardware/Meadow_F7/F7v1/index.md
@@ -10,25 +10,25 @@ The Meadow F7v1 was the inaugural Meadow F7 board that shipped as part of our Ki
The Meadow F7v1 board is feature packed:
- * STMicroelectronics STM32F7 32-bit ARM Cortex-M7 based core MCU at up to 216MHz
- * 2MB internal Flash memory
- * 412Kb internal RAM
- * 2D Graphics Acceleration (DMA2D) via ST Chrom-ART Accelerator
- * Internal, low-power realtime clock (RTC)
- * Cryptographic Hardware Acceleration for AES 128, 192, 256, triple DES, HASH (MD5, SHA-1, SHA-2), and HMAC
- True random number generator
- Floating point unit (FPU)
- Secure Boot secure, encrypted firmware loader
- * Espressif ESP32 (ESP-Pico-D4) Xtensa 32-bit dual-core LX6 up to 240MHz coprocessor.
- * 2.4GHz WiFi 802.11 b/g/n with WFA, WPA/WPA2 and WAPI
- * Bluetooth 4.2, 5.1
- * 32MB external, onboard QSPI RAM
- * 32MB external, onboard non-volatile Flash memory (~28MB available for user code)
- * 25 Mixed Signal IO ports (6/8x Analog, 12x PWM, 3x UART, I2C, SPI, CAN, 2x DAC)
- * On-board 2.4GHz ceramic chip antenna
- * U.FL external antenna connector
- * RoHS compliant (lead and hazardous materials-free)
+* STMicroelectronics STM32F7 32-bit ARM Cortex-M7 based core MCU at up to 216MHz
+ * 2MB internal Flash memory
+ * 412Kb internal RAM
+ * 2D Graphics Acceleration (DMA2D) via ST Chrom-ART Accelerator
+ * Internal, low-power realtime clock (RTC)
+ * Cryptographic Hardware Acceleration for AES 128, 192, 256, triple DES, HASH (MD5, SHA-1, SHA-2), and HMAC
+ True random number generator
+ Floating point unit (FPU)
+ Secure Boot secure, encrypted firmware loader
+* Espressif ESP32 (ESP-Pico-D4) Xtensa 32-bit dual-core LX6 up to 240MHz coprocessor.
+ * 2.4GHz WiFi 802.11 b/g/n with WFA, WPA/WPA2 and WAPI
+ * Bluetooth 4.2, 5.1
+* 32MB external, onboard QSPI RAM
+* 32MB external, onboard non-volatile Flash memory (~28MB available for user code)
+* 25 Mixed Signal IO ports (6/8x Analog, 12x PWM, 3x UART, I2C, SPI, CAN, 2x DAC)
+* On-board 2.4GHz ceramic chip antenna
+* U.FL external antenna connector
+* RoHS compliant (lead and hazardous materials-free)
## Pinout
-
+
diff --git a/docs/Hardware/Tutorials/Electronics/Part3/Direct_Current/index.md b/docs/Hardware/Tutorials/Electronics/Part3/Direct_Current/index.md
index 98b8b8a88..fbfe0a6e1 100644
--- a/docs/Hardware/Tutorials/Electronics/Part3/Direct_Current/index.md
+++ b/docs/Hardware/Tutorials/Electronics/Part3/Direct_Current/index.md
@@ -9,14 +9,14 @@ subtitle: Constant polarity current.
[Direct current (DC)](https://en.wikipedia.org/wiki/Direct_current) specifies a unidirectional flow of electrons; that is they flow in one direction only.
The simple nature of direct current lends itself well to creating digital logic circuits, because it can represent binary `1` when `ON` (within a given voltage range), and binary `0` when `OFF` (at ground, or `0V`). It's also the type of current that batteries generate.
-
+
Because DC is used as the primary type of current in digital logic circuits, most of this tutorial will focus on DC circuits.
Direct curent is also used in [long distance, high power, electrical transmission lines](https://en.wikipedia.org/wiki/High-voltage_direct_current) (usually `>250kV`) because of lower electrical losses.
Meadow provides two _power rails_ that supply `5V` and `3.3V` direct current. The `3.3V` rail can be found on the left header, and the `5V` rail can be found on the right header:
-
+
### DC Power Symbols
@@ -36,13 +36,13 @@ The logic level is based on what `HIGH` means in a circuit, and falls into two c
#### Complementary Metal-Oxide-Semiconductor (CMOS)
-CMOS is the technology that nearly all modern integrated circuits use. CMOS `HIGH` signals can vary but they're defined as the `V``DD` level, which is usually `3.3V` in most common circuits. In fact, for nearly all circuits we'll create, we'll use the CMOS standard with `V``DD` = `3.3V` as the upper end of the voltage supply source.
+CMOS is the technology that nearly all modern integrated circuits use. CMOS `HIGH` signals can vary but they're defined as the `V``DD` level, which is usually `3.3V` in most common circuits. In fact, for nearly all circuits we'll create, we'll use the CMOS standard with `V``DD` = `3.3V` as the upper end of the voltage supply source.
Internally, most microcontrollers, CPUs, and other complex chips use a lower `V``DD`, often `1.8V` or less, which allows them to operate at faster speeds. However, most microcontrollers use `3.3V` on their IO pins.
#### Transistor-Transistor-Logic (TTL)
-TTL is based on older transistor technologies in which the `HIGH` signal is defined as `V``CC`, which is usually `5V`.
+TTL is based on older transistor technologies in which the `HIGH` signal is defined as `V``CC`, which is usually `5V`.
#### VCC/VDD
diff --git a/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/index.md b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/index.md
new file mode 100644
index 000000000..a3dab1249
--- /dev/null
+++ b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/index.md
@@ -0,0 +1,281 @@
+---
+layout: Meadow
+sidebar_label: Hello, Project Lab + Cellular
+title: Hello, Meadow Project Lab + Cellular
+subtitle: Create, deploy, and understand your first Meadow application.
+---
+
+
+
+This guide shows you how to set up your [Meadow Project Lab + Cellular bundle](https://store.wildernesslabs.co/collections/frontpage/products/project-lab-board) board from unboxing all the way to deploying your first Meadow app from either Visual Studio 2022 or Visual Studio Code.
+
+:::info important
+Meadow has multiple ways to provide connectivity capabilities to your IoT applications: **WiFi**, **Ethernet** & **Cellular**. Switching between network interfaces is a straightforward process, and we offer working samples for each use case:
+* WiFi Sample ([Code](https://github.com/WildernessLabs/Meadow.Samples/tree/main/Source/Meadow%20F7/Network/WiFi_Basics) | [Config](https://github.com/WildernessLabs/Meadow.Samples/tree/main/Source/Meadow%20F7/Network/WiFiConfig))
+* [Ethernet Sample](https://github.com/WildernessLabs/Meadow.Samples/tree/main/Source/Meadow%20F7/Network/Ethernet_Basics)
+* [Cellular Sample](https://github.com/WildernessLabs/Meadow.Samples/tree/main/Source/Meadow%20F7/Network/Cell_Basics)
+:::
+
+## Adding the cellular module on a Project Lab
+
+Your cellular bundle comes with these parts:
+
+
+
+- Connect the [Skywire click](https://www.mikroe.com/skywire-click) adapter on the MicroBus 1 connector on the project lab.
+- Insert the [Teal SIM](https://tealcom.io/) card in the SIM Card slot under the [BG95-M3 cellular module](https://www.digikey.ca/en/products/detail/nimbelink,-llc/NL-SW-LTE-QBG95-D/21363405).
+- Place the cellular module on the Skywire click adapter.
+- Finally, connect the Mini GSM Antenna on the Antenna connector marked with X1.
+
+Once everything connected, it should look like this:
+
+
+
+## Activating your Teal SIM Card
+
+First, you'll need to fill out their [Account Creation Form](https://forms.monday.com/forms/5610d871c689ea18cde677ca13f1922f?r=use1), which would submit a request to Teal to create an account for you. As soon the account is created, they will send you and email with a link to the Teal Portal along with the login credentials.
+
+Once you have the credentials, login to your account and you will land on the **Dashboard** tab, showing basic metrics such as _Data Consumption_, _Device Network Status_, _eSIM Operation Status_, etc.
+
+Click on the **OneChip eUICC** tab where you will see your SIM Card(s). Select your card(s) on the far left end of the row and click the **Actions** drop down menu, and click **Activate**.
+
+
+
+After a few seconds or a minute, refresh the site and you should see the card(s) **Network Status** changed to **Activated**.
+
+## Setting up Project Lab + Cellular
+
+
+
+
+### Step 1 - Install .NET Runtime
+
+Download and install the latest version of the [.NET runtime](https://dotnet.microsoft.com/en-us/download).
+
+### Step 2 - Deploy latest version of Meadow.OS
+
+Follow this quick guide to Deploy Meadow.OS to your board to ensure it’s running with the latest version available.
+
+### Step 3 - Install Visual Studio
+
+Download and Install [Visual Studio 2022](https://visualstudio.microsoft.com/) for either Windows or macOS to prepare your development machine. Community edition will work fine.
+
+### Step 4 - Add Meadow Visual Studio Extension
+
+Follow this guide to install the VS Tools for Meadow Extension for Visual Studio 2022, to deploy applications to your Meadow devices.
+
+### Step 5 - Install Meadow Project Templates
+
+Open a console window and enter the following command to install a list of Meadow project templates:
+
+```console
+dotnet new install WildernessLabs.Meadow.Template
+```
+
+When installed, you’ll see a list of templates available:
+
+```console
+The following template packages will be installed:
+ WildernessLabs.Meadow.Template
+
+Success: WildernessLabs.Meadow.Template installed the following templates:
+Template Name Short Name Language Tags
+----------------------- ------------------ -------------- -------------------
+Meadow Core-Compute App meadow-ccm [C#],F#,VB.NET Meadow/Console
+Meadow Desktop App meadow-desktop [C#] Meadow/Console
+Meadow F7 Feather App meadow-feather [C#],F#,VB.NET Meadow/Console
+Meadow Jetson Nano App meadow-jetson-nano [C#] Meadow/Console
+Meadow Library meadow-library [C#],F#,VB.NET Meadow/Library
+Meadow Project Lab App meadow-project-lab [C#] Meadow/Console
+Meadow Raspberry Pi App meadow-rpi [C#] Meadow/Console
+Meadow reTerminal App meadow-reterminal [C#] Meadow/Console
+Meadow StartKit App meadow-startkit [C#] Meadow/App/StartKit
+```
+
+### Step 6 - Validate hardware
+
+To make sure you have your Project Lab up-to-date and the Cellular module is properly configured, try out our [CellularSample](https://github.com/WildernessLabs/Meadow.Samples/tree/main/Source/ProjectLab/CellularSample) project from our [Meadow.Samples](https://github.com/WildernessLabs/Meadow.Samples/) repo:
+
+
+
+Things to consider:
+
+* This sample doesnt need any modifications, just build and deploy it and you should see the Project Lab picking up a cellular signal, showing you the IP Address, conexion status and a signal strength indicator.
+* Its recommended to be close to a window to improve signal detection.
+* If signal is still not great, you might want to try switching Networks for your SIM card on the Teal Portal.
+
+### Step 7 - Deploy your application
+
+When your application is ready and builds, connect your board if disconnected, and in the **Meadow devices** drop down it should list its corresponding COM port. Once selected, click on the play **Debug button** to start transferring the application to your board.
+
+
+
+:::caution
+When deploying a project for the first time, the transfer will take several minutes, since it's transferring all the necessary libraries to run the application. Once the app is running for the first time, deployment will be faster as it will transfer only the files that have been changed.
+:::
+
+Once all the files are transferred to your device, the app will start in debug mode and you should see Project Lab's screen turn on and it will indicate your Cellular connectivity status.
+
+### Step 8 - Check out additional samples
+
+You can check more samples in our [Meadow.Samples](https://github.com/WildernessLabs/Meadow.Samples/tree/main) GitHub repo.
+
+
+
+
+
+
+### Step 1 - Install .NET Runtime
+
+Download and install the latest version of the [.NET runtime](https://dotnet.microsoft.com/en-us/download).
+
+### Step 2 - Deploy latest version of Meadow.OS
+
+Follow this quick guide to Deploy Meadow.OS to your board to ensure it’s running with the latest version available.
+
+### Step 3 - Install Visual Studio Code
+
+Download and Install [Visual Studio Code](https://visualstudio.microsoft.com/) to prepare your development machine.
+
+### Step 4 - Add Meadow VSCode Extension
+
+Follow this guide to install the VSCode Tools for Meadow Extension for Visual Studio Code, to deploy applications to your Meadow devices.
+
+### Step 5 - Install Meadow Project Templates
+
+Open a console window and enter the following command to install a list of Meadow project templates:
+
+```console
+dotnet new install WildernessLabs.Meadow.Template
+```
+
+When installed, you’ll see a list of templates available:
+
+```console
+The following template packages will be installed:
+ WildernessLabs.Meadow.Template
+
+Success: WildernessLabs.Meadow.Template installed the following templates:
+Template Name Short Name Language Tags
+----------------------- ------------------ -------------- -------------------
+Meadow Core-Compute App meadow-ccm [C#],F#,VB.NET Meadow/Console
+Meadow Desktop App meadow-desktop [C#] Meadow/Console
+Meadow F7 Feather App meadow-feather [C#],F#,VB.NET Meadow/Console
+Meadow Jetson Nano App meadow-jetson-nano [C#] Meadow/Console
+Meadow Library meadow-library [C#],F#,VB.NET Meadow/Library
+Meadow Project Lab App meadow-project-lab [C#] Meadow/Console
+Meadow Raspberry Pi App meadow-rpi [C#] Meadow/Console
+Meadow reTerminal App meadow-reterminal [C#] Meadow/Console
+Meadow StartKit App meadow-startkit [C#] Meadow/App/StartKit
+```
+
+### Step 6 - Validate Hardware
+
+To make sure you have your Project Lab up-to-date and the Cellular module is properly configured, try out our [CellularSample](https://github.com/WildernessLabs/Meadow.Samples/tree/main/Source/ProjectLab/CellularSample) project from our [Meadow.Samples](https://github.com/WildernessLabs/Meadow.Samples/) repo:
+
+
+
+Things to consider:
+
+* This sample doesnt need any modifications, just build and deploy it and you should see the Project Lab picking up a cellular signal, showing you the IP Address, conexion status and a signal strength indicator.
+* Its recommended to be close to a window to improve signal detection.
+* If signal is still not great, you might want to try switching Networks for your SIM card on the Teal Portal.
+
+### Step 7 - Deploy your application
+
+With no code changes, let's deploy this app to your new Project Lab.
+
+In the Activity Bar on the side of the window, select the **Run and Debug** icon.
+
+Within the **Run and Debug** side bar, select the configuration drop-down and select the port corresponding to your connected Meadow device.
+
+
+
+:::caution
+When deploying a project for the first time, the transfer will take several minutes, since it's transferring all the necessary libraries to run the application. Once the app is running for the first time, deployment will be faster as it will transfer only the files that have been changed.
+:::
+
+Once all the files are transferred to your device, the app will start in debug mode and you should see Project Lab's screen turn on and it will indicate your Cellular connectivity status.
+
+### Step 8 - Check out additional samples
+
+You can check more samples in our [Meadow.Samples](https://github.com/WildernessLabs/Meadow.Samples/tree/main) GitHub repo.
+
+
+
+
+
+
+### Step 1 - Install .NET Runtime
+
+Download and install the latest version of the [.NET runtime](https://dotnet.microsoft.com/en-us/download).
+
+### Step 2 - Install Meadow CLI
+
+Download and Install [Meadow CLI](https://www.nuget.org/packages/WildernessLabs.Meadow.CLI//) if it's not installed already.
+
+### Step 3 - Deploy latest version of Meadow.OS
+
+Follow this quick guide to Deploy Meadow.OS to your board to ensure it’s running with the latest version available.
+
+### Step 4 - Install Meadow Project Templates
+
+Open a console window and enter the following command to install a list of Meadow project templates:
+
+```console
+dotnet new install WildernessLabs.Meadow.Template
+```
+
+When installed, you’ll see a list of templates available:
+
+```console
+The following template packages will be installed:
+ WildernessLabs.Meadow.Template
+
+Success: WildernessLabs.Meadow.Template installed the following templates:
+Template Name Short Name Language Tags
+----------------------- ------------------ -------------- -------------------
+Meadow Core-Compute App meadow-ccm [C#],F#,VB.NET Meadow/Console
+Meadow Desktop App meadow-desktop [C#] Meadow/Console
+Meadow F7 Feather App meadow-feather [C#],F#,VB.NET Meadow/Console
+Meadow Jetson Nano App meadow-jetson-nano [C#] Meadow/Console
+Meadow Library meadow-library [C#],F#,VB.NET Meadow/Library
+Meadow Project Lab App meadow-project-lab [C#] Meadow/Console
+Meadow Raspberry Pi App meadow-rpi [C#] Meadow/Console
+Meadow reTerminal App meadow-reterminal [C#] Meadow/Console
+Meadow StartKit App meadow-startkit [C#] Meadow/App/StartKit
+```
+
+### Step 5 - Validate Hardware
+
+To make sure you have your Project Lab up-to-date and the Cellular module is properly configured, try out our [CellularSample](https://github.com/WildernessLabs/Meadow.Samples/tree/main/Source/ProjectLab/CellularSample) project from our [Meadow.Samples](https://github.com/WildernessLabs/Meadow.Samples/) repo:
+
+
+
+Things to consider:
+
+* This sample doesnt need any modifications, just build and deploy it and you should see the Project Lab picking up a cellular signal, showing you the IP Address, conexion status and a signal strength indicator.
+* Its recommended to be close to a window to improve signal detection.
+* If signal is still not great, you might want to try switching Networks for your SIM card on the Teal Portal.
+
+### Step 6 - Deploy your application
+
+With no code changes, let's deploy this app to your new board.
+
+Again in your console window, use the `meadow app run` command to build, trim, deploy and start your Meadow application.
+
+:::caution
+When deploying a project for the first time, the transfer will take several minutes, since it's transferring all the necessary libraries to run the application. Once the app is running for the first time, deployment will be faster as it will transfer only the files that have been changed.
+:::
+
+Once all the files are transferred to your device, the app will start in debug mode and you should see Project Lab's screen turn on and it will indicate your Cellular connectivity status.
+
+### Step 7 - Check out additional samples
+
+You can check more samples in our [Meadow.Samples](https://github.com/WildernessLabs/Meadow.Samples/tree/main) GitHub repo.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wilderness-labs-meadow-projectlab-samples.jpg b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wilderness-labs-meadow-projectlab-samples.jpg
new file mode 100644
index 000000000..b6505f1b4
Binary files /dev/null and b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wilderness-labs-meadow-projectlab-samples.jpg differ
diff --git a/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-meadow-project-lab-cellular-specs.jpg b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-meadow-project-lab-cellular-specs.jpg
new file mode 100644
index 000000000..abbd78885
Binary files /dev/null and b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-meadow-project-lab-cellular-specs.jpg differ
diff --git a/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-meadow-project-lab-cellular-top-board.jpg b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-meadow-project-lab-cellular-top-board.jpg
new file mode 100644
index 000000000..7427f14b5
Binary files /dev/null and b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-meadow-project-lab-cellular-top-board.jpg differ
diff --git a/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-projectlab-cellular-assembled.jpg b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-projectlab-cellular-assembled.jpg
new file mode 100644
index 000000000..02c07347c
Binary files /dev/null and b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-projectlab-cellular-assembled.jpg differ
diff --git a/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-teal-sim-activate.jpg b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-teal-sim-activate.jpg
new file mode 100644
index 000000000..b8f067802
Binary files /dev/null and b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs-teal-sim-activate.jpg differ
diff --git a/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs_projectlab_getting_started.jpg b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs_projectlab_getting_started.jpg
new file mode 100644
index 000000000..dbf09c84d
Binary files /dev/null and b/docs/Meadow/Getting_Started/MCUs/Project_Lab_Cellular/wildernesslabs_projectlab_getting_started.jpg differ
diff --git a/docs/Meadow/Meadow_Basics/IO/Digital/Protocols/SPI/index.md b/docs/Meadow/Meadow_Basics/IO/Digital/Protocols/SPI/index.md
index 0ae7370d4..6471c7b5b 100644
--- a/docs/Meadow/Meadow_Basics/IO/Digital/Protocols/SPI/index.md
+++ b/docs/Meadow/Meadow_Basics/IO/Digital/Protocols/SPI/index.md
@@ -40,7 +40,7 @@ Note: SPI supports shared `CS` lines in a _daisy-chain_ configuration, but it's
The SPI pins on the F7 Feather are labeled `SCK`, `MOSI` (`COPI`), and `MISO` (`CIPO`) and can be found between `A05` and `D00`:
-
+
Any pin that supports digital output can be used as a chip select line.
diff --git a/docs/Meadow/Meadow_Basics/IO/Digital/Protocols/UART/index.md b/docs/Meadow/Meadow_Basics/IO/Digital/Protocols/UART/index.md
index aa1ffae82..0a66a7bcb 100644
--- a/docs/Meadow/Meadow_Basics/IO/Digital/Protocols/UART/index.md
+++ b/docs/Meadow/Meadow_Basics/IO/Digital/Protocols/UART/index.md
@@ -61,7 +61,7 @@ The Meadow F7 Feather has two exposed serial ports, named `COM4` and `COM1` with
* **COM4** - `D00` = `RX`, `D01` = `TX`
* **COM1** - `D13` = `RX`, `D12` = `TX`
-
+
## Using the Meadow Serial API
diff --git a/docs/Meadow/Meadow_Basics/IO/Power/index.md b/docs/Meadow/Meadow_Basics/IO/Power/index.md
index e77b73469..e26902719 100644
--- a/docs/Meadow/Meadow_Basics/IO/Power/index.md
+++ b/docs/Meadow/Meadow_Basics/IO/Power/index.md
@@ -59,7 +59,7 @@ The STM32F7 is equipped with a real-time clock (RTC), which, when set, will reta
## Hardware Pins
-
+
### Reset (`RST`)
diff --git a/docs/Meadow/Meadow_Basics/IO/index.md b/docs/Meadow/Meadow_Basics/IO/index.md
index 349dd1a7e..f3785c136 100644
--- a/docs/Meadow/Meadow_Basics/IO/index.md
+++ b/docs/Meadow/Meadow_Basics/IO/index.md
@@ -77,7 +77,7 @@ GPIO ports are available via pins (as well as the onboard LED) on the Meadow F7
#### Meadow F7v1 Feather Pinout
-
+
The function that they serve depends on how they are configured when a _port_ is instantiated on one of the pins. For instance, pin `D00` can be configured to be used a digital input or output, or as the `RX` (receive) half of a Serial UART port available as "COM4".
@@ -185,8 +185,8 @@ The following table lists all the accessible pins on the Meadow F7 Feather dev b
| D02 | PH10 | PH10 | | 1 | |
| D03 | PB8 | PB8 | | 3 | 8 |
| D04 | PB9 | PB9 | | 4 | 9 |
-| D05 | PB4 | PB4 | | 1 | 4 |
-| D06 | PB13 | PB13 | | 1 | 13 |
+| D05 | PB4 | PB4 | | | 4 |
+| D06 | PB13 | PB13 | | | 13 |
| D07 | PB7 | PB7 | | 2 | 7 |
| D08 | PB6 | PB6 | | 1 | 6 |
| D09 | PC6 | PC6 | | 1 | 6 |
diff --git a/docs/Meadow/Release_Notes/Beta3/index.md b/docs/Meadow/Release_Notes/Beta3/index.md
index e23d02e8d..dc3236d24 100644
--- a/docs/Meadow/Release_Notes/Beta3/index.md
+++ b/docs/Meadow/Release_Notes/Beta3/index.md
@@ -654,7 +654,7 @@ In order to be compatible with the file system changes, the `Meadow.CLI` has als
### SPI
-We got [SPI](/Meadow/Meadow_Basics/IO/Digital/Protocols/SPI/) validated and merged. We’re excited to get this out, as we know that several of you are working on integrations that require SPI. To use it, you’ll need to flash your Meadow board with the [latest OS firmware binaries](http://wldrn.es/latestmeadowos).
+We got [SPI](/Meadow/Meadow_Basics/IO/Digital/Protocols/SPI/) validated and merged. We're excited to get this out, as we know that several of you are working on integrations that require SPI. To use it, you'll need to flash your Meadow board with the [latest OS firmware binaries](http://wldrn.es/latestmeadowos).
### Visual Studio Extension
@@ -692,9 +692,9 @@ Say hello to productivity! That's right, we now have extensions for [Visual Stud
PWM is now live! Along with it, PwmLed, RgbPwmLed, Servo Core, etc.
-```
+```csharp
IPwmPort pwm = Device.CreatePwmPort(
- pin: Device.Pins.D05,
+ pin: Device.Pins.D04,
frequency: 100,
dutyCycle: 0.5f);
pwm.Start();
@@ -704,7 +704,7 @@ pwm.Start();
The I2C protocol is also available in our latest Meadow OS.
-```
+```csharp
II2cBus i2c = Device.CreateI2cBus();
GY521Test(i2c); // Pass i2c to an I2C capable device
```
diff --git a/docs/api/Meadow.Foundation/Meadow.Foundation.Leds.PwmLed.md b/docs/api/Meadow.Foundation/Meadow.Foundation.Leds.PwmLed.md
index 01863a91d..e6ffcdfa0 100644
--- a/docs/api/Meadow.Foundation/Meadow.Foundation.Leds.PwmLed.md
+++ b/docs/api/Meadow.Foundation/Meadow.Foundation.Leds.PwmLed.md
@@ -26,19 +26,19 @@ public override Task Initialize()
{
Resolver.Log.Info("Initializing...");
- // Using an array of Pins that support PWM (D02 - D13)
+ // Using an array of Pins that support PWM (F7v2: D02-D04, D07-D13)
IPin[] pins =
{
- Device.Pins.D11,
- Device.Pins.D10,
- Device.Pins.D09,
- Device.Pins.D08,
- Device.Pins.D07,
- Device.Pins.D06,
- Device.Pins.D05,
- Device.Pins.D04,
- Device.Pins.D03,
- Device.Pins.D02
+ Device.Pins.D11,
+ Device.Pins.D10,
+ Device.Pins.D09,
+ Device.Pins.D08,
+ Device.Pins.D07,
+ // Device.Pins.D06, // Only available for PWM on F7v1
+ // Device.Pins.D05, // Only available for PWM on F7v1
+ Device.Pins.D04,
+ Device.Pins.D03,
+ Device.Pins.D02
};
pwmLedBarGraph = new PwmLedBarGraph(pins, new Voltage(2.2));
diff --git a/docs/api/Meadow.Foundation/Meadow.Foundation.Leds.PwmLedBarGraph.md b/docs/api/Meadow.Foundation/Meadow.Foundation.Leds.PwmLedBarGraph.md
index 1863358c8..53e0b3383 100644
--- a/docs/api/Meadow.Foundation/Meadow.Foundation.Leds.PwmLedBarGraph.md
+++ b/docs/api/Meadow.Foundation/Meadow.Foundation.Leds.PwmLedBarGraph.md
@@ -26,19 +26,19 @@ public override Task Initialize()
{
Resolver.Log.Info("Initializing...");
- // Using an array of Pins that support PWM (D02 - D13)
+ // Using an array of Pins that support PWM (F7v2: D02-D04, D07-D13)
IPin[] pins =
{
- Device.Pins.D11,
- Device.Pins.D10,
- Device.Pins.D09,
- Device.Pins.D08,
- Device.Pins.D07,
- Device.Pins.D06,
- Device.Pins.D05,
- Device.Pins.D04,
- Device.Pins.D03,
- Device.Pins.D02
+ Device.Pins.D11,
+ Device.Pins.D10,
+ Device.Pins.D09,
+ Device.Pins.D08,
+ Device.Pins.D07,
+ // Device.Pins.D06, // Only available for PWM on F7v1
+ // Device.Pins.D05, // Only available for PWM on F7v1
+ Device.Pins.D04,
+ Device.Pins.D03,
+ Device.Pins.D02
};
pwmLedBarGraph = new PwmLedBarGraph(pins, new Voltage(2.2));
diff --git a/src/sidebars/meadowOsSidebar.js b/src/sidebars/meadowOsSidebar.js
index 92042acbe..200921732 100644
--- a/src/sidebars/meadowOsSidebar.js
+++ b/src/sidebars/meadowOsSidebar.js
@@ -22,6 +22,7 @@ const meadowOsSidebar = [
"Meadow/Getting_Started/MCUs/F7_Feather/index",
"Meadow/Getting_Started/MCUs/Core_Compute_Module_DevKit/index",
"Meadow/Getting_Started/MCUs/Project_Lab/index",
+ "Meadow/Getting_Started/MCUs/Project_Lab_Cellular/index",
],
},
diff --git a/static/Common_Files/Meadow_F7v2_Micro_Pinout.svg b/static/Common_Files/Meadow_F7v2_Micro_Pinout.svg
index 53e11b6fd..ff60eed54 100644
--- a/static/Common_Files/Meadow_F7v2_Micro_Pinout.svg
+++ b/static/Common_Files/Meadow_F7v2_Micro_Pinout.svg
@@ -1,5 +1,5 @@