diff --git a/docs/about/contributing.mdx b/docs/about/contributing.mdx index cd4cd29d..fa23d48d 100644 --- a/docs/about/contributing.mdx +++ b/docs/about/contributing.mdx @@ -29,7 +29,7 @@ Most communication and interactions happen with protocol buffers. The [Meshtasti ### Device Firmware -The [firmware repo](https://github.com/meshtastic/firmware) is where all of the device firmware development happens. This is where the code for the ESP32 and nRF52 based devices is developed. It is mainly C and C++ code. Think Arduino. It is where the first level of hardware interaction begins and ends. +The [firmware repo](https://github.com/meshtastic/firmware) is where all of the device firmware development happens. This is where the code for the ESP32, nRF52 and RP2040 based devices is developed. It is mainly C and C++ code. Think Arduino. It is where the first level of hardware interaction begins and ends. ### Firmware Modules diff --git a/docs/configuration/module/mqtt.mdx b/docs/configuration/module/mqtt.mdx index a7699448..675713e6 100644 --- a/docs/configuration/module/mqtt.mdx +++ b/docs/configuration/module/mqtt.mdx @@ -131,6 +131,10 @@ All MQTT module config options are available for the Web UI. ## Connect to the Default Public Server +:::important +The default channel (LongFast) on the public server usually has a lot of traffic. Your device may get overloaded and may no longer function properly anymore. It is recommended to use a different channel or to use your own MQTT server if you experience issues. +::: + - Install NRF52 Drivers + Install nRF52/RP2040 Drivers @@ -115,7 +115,7 @@ After completing the previous steps, you can now flash the Meshtastic firmware o className={"button button--outline button--lg cta--button"} to={"/docs/getting-started/flashing-firmware/nrf52/"} > - Flash nRF52 Firmware + Flash nRF52/RP2040 Firmware diff --git a/docs/getting-started/serial-drivers/serial-drivers-nrf52.mdx b/docs/getting-started/serial-drivers/serial-drivers-nrf52.mdx index fd85b48a..5d2dc7e1 100644 --- a/docs/getting-started/serial-drivers/serial-drivers-nrf52.mdx +++ b/docs/getting-started/serial-drivers/serial-drivers-nrf52.mdx @@ -1,7 +1,7 @@ --- id: nrf52 -title: nRF52 Serial Drivers -sidebar_label: nRF52 Drivers +title: nRF52/RP2040 Serial Drivers +sidebar_label: nRF52/RP2040 Drivers sidebar_position: 2 --- @@ -9,11 +9,11 @@ import Tabs from "@theme/Tabs"; import TabItem from "@theme/TabItem"; import Link from "@docusaurus/Link"; -## Install nRF52 USB to Serial Drivers +## Install nRF52/RP2040 USB to Serial Drivers :::caution -nRF52 devices typically do not require serial drivers. They use the UF2 bootloader which makes the devices appear as flash drives. Do _NOT_ download the USB device drivers unless required to install UF2 support. +nRF52/RP2040 devices typically do not require serial drivers. They use the UF2 bootloader which makes the devices appear as flash drives. Do _NOT_ download the USB device drivers unless required to install UF2 support. ::: @@ -86,6 +86,6 @@ After installing the serial drivers, you can now flash the Meshtastic firmware o className={"button button--outline button--lg cta--button"} to={"/docs/getting-started/flashing-firmware/nrf52/"} > - Flash nRF52 Firmware + Flash nRF52/RP2040 Firmware diff --git a/docs/getting-started/serial-drivers/test-serial-driver-installation.mdx b/docs/getting-started/serial-drivers/test-serial-driver-installation.mdx index 6fa58938..7e5ebb4d 100644 --- a/docs/getting-started/serial-drivers/test-serial-driver-installation.mdx +++ b/docs/getting-started/serial-drivers/test-serial-driver-installation.mdx @@ -94,7 +94,7 @@ After completing the previous steps, you can now flash the Meshtastic firmware o className={"button button--outline button--lg cta--button"} to={"/docs/getting-started/flashing-firmware/nrf52/"} > - Flash nRF52 Firmware + Flash nRF52/RP2040 Firmware diff --git a/docs/hardware/devices/heltec/index.mdx b/docs/hardware/devices/heltec/index.mdx index 10d9429d..a9167196 100644 --- a/docs/hardware/devices/heltec/index.mdx +++ b/docs/hardware/devices/heltec/index.mdx @@ -194,10 +194,15 @@ Image Source: [Heltec](https://heltec.org/project/wireless-tracker/) -:::info -This device may have issues charging a connected battery if utilizing a USB-C to USB-C cable. It's recommended to use a USB-A to USB-C cable. +:::caution + +Please note, this device is only partially supported. The display is not currently implemented in the firmware. + +Additionally, this device may have issues charging a connected battery if utilizing a USB-C to USB-C cable. It's recommended to use a USB-A to USB-C cable. + ::: + - **MCU:** - ESP32-S3FN8 (WiFi & Bluetooth) - **LoRa Transceiver:** diff --git a/docs/software/mqtt/index.mdx b/docs/software/mqtt/index.mdx index a1ef38e4..83a5f3c0 100644 --- a/docs/software/mqtt/index.mdx +++ b/docs/software/mqtt/index.mdx @@ -17,6 +17,8 @@ You can find the settings available for MQTT [here](/docs/configuration/module/m :::important When MQTT is turned on, you are potentially broadcasting your entire mesh's traffic onto the public internet. This includes messages and position information. + +The default channel (LongFast) on the public MQTT server usually has a lot of traffic. Your device may get overloaded and may no longer function properly anymore. It is recommended to use a different channel or to use your own MQTT server if you experience issues. ::: ## Software Integrations