From 0a5edc7fce0bd920d529dfb6a595267e62d9a0b4 Mon Sep 17 00:00:00 2001 From: charlesmarseille <36216289+charlesmarseille@users.noreply.github.com> Date: Wed, 26 Oct 2022 10:32:28 -0400 Subject: [PATCH 1/7] Update remote-admin.mdx specify ID format for windows CLI --- docs/software/device/remote-admin.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/software/device/remote-admin.mdx b/docs/software/device/remote-admin.mdx index 0866537b..ff883bb1 100644 --- a/docs/software/device/remote-admin.mdx +++ b/docs/software/device/remote-admin.mdx @@ -87,6 +87,7 @@ Connected to radio ``` Using the node ID from that list, send a message through the mesh telling that node to change its owner name. +The --dest argument value must be in single quotes for linux/mac ('!28979058'), no quotes for Windows (!28979058). ```shell title="Expected output" $ meshtastic --dest '!28979058' --set-owner "Im Remote" From b4668786b649134ece031d8087b5bc674c5ba271 Mon Sep 17 00:00:00 2001 From: charlesmarseille Date: Wed, 26 Oct 2022 11:39:51 -0400 Subject: [PATCH 2/7] specify ID format for windows CLI --- docs/software/device/remote-admin.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/software/device/remote-admin.mdx b/docs/software/device/remote-admin.mdx index ff883bb1..896fc999 100644 --- a/docs/software/device/remote-admin.mdx +++ b/docs/software/device/remote-admin.mdx @@ -87,7 +87,7 @@ Connected to radio ``` Using the node ID from that list, send a message through the mesh telling that node to change its owner name. -The --dest argument value must be in single quotes for linux/mac ('!28979058'), no quotes for Windows (!28979058). +The --dest argument value must be in single quotes for linux/mac '!28979058', no quotes for Windows !28979058. ```shell title="Expected output" $ meshtastic --dest '!28979058' --set-owner "Im Remote" From 04a9ec342a871435086c0a9372513fa676d4f452 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20G=C3=B6ttgens?= Date: Thu, 27 Oct 2022 15:56:37 +0200 Subject: [PATCH 3/7] Update critical-faults.mdx --- docs/software/device/critical-faults.mdx | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/docs/software/device/critical-faults.mdx b/docs/software/device/critical-faults.mdx index ef3806aa..2bc2e524 100644 --- a/docs/software/device/critical-faults.mdx +++ b/docs/software/device/critical-faults.mdx @@ -12,12 +12,14 @@ This table is derived from the [protobufs](/docs/developers/protobufs/api#critic | Name | Number | Description | | ------------------- | ------ | ----------------------------------------------------------------------------------------------------------------------- | -| TxWatchdog | 1 | A software bug was detected while trying to send LoRa | -| SleepEnterWait | 2 | A software bug was detected on entry to sleep | -| NoRadio | 3 | No LoRa radio hardware could be found | -| Unspecified | 4 | Not normally used | -| UBloxInitFailed | 5 | We failed while configuring a UBlox GPS | -| NoAXP192 | 6 | This board was expected to have a power management chip and it is missing or broken | -| InvalidRadioSetting | 7 | The channel tried to set a radio setting which is not supported by this chipset, radio comms settings are now undefined | -| TransmitFailed | 8 | Radio transmit hardware failure. We sent data to the radio chip, but it did not reply with an interrupt | -| Brownout | 9 | We detected that the main CPU voltage dropped below the minimum acceptable value | +| TxWatchdog | 1 | A software bug was detected while trying to send LoRa | +| SleepEnterWait | 2 | A software bug was detected on entry to sleep | +| NoRadio | 3 | No LoRa radio hardware could be found | +| Unspecified | 4 | Not normally used | +| UBloxInitFailed | 5 | We failed while configuring a UBlox GPS | +| NoAXP192 | 6 | This board was expected to have a power management chip and it is missing or broken | +| InvalidRadioSetting | 7 | The channel tried to set a radio setting which is not supported by this chipset, radio comms settings are now undefined | +| TransmitFailed | 8 | Radio transmit hardware failure. We sent data to the radio chip, but it did not reply with an interrupt | +| Brownout | 9 | We detected that the main CPU voltage dropped below the minimum acceptable value | +| SX1262Failure | 10 | Selftest of SX1262 radio chip failed | +| RadioSpiBug | 11 | A (likely software but possibly hardware) failure was detected while trying to send packets. If this occurs on your board, please post in the forum so that we can ask you to collect some information to allow fixing this bug | From 2b8860591ca165ebfbeba59d08e28e9cb683b833 Mon Sep 17 00:00:00 2001 From: IZ1IVA <75425638+IZ1IVA@users.noreply.github.com> Date: Thu, 27 Oct 2022 19:55:43 +0200 Subject: [PATCH 4/7] Fixed discrepancy --- docs/settings/config/position.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/settings/config/position.mdx b/docs/settings/config/position.mdx index f060714e..a6e6864f 100644 --- a/docs/settings/config/position.mdx +++ b/docs/settings/config/position.mdx @@ -109,7 +109,7 @@ All Position config commands are available in the python CLI. Example commands a | position.gps_update_interval | `integer` (seconds) | Default `0` is 30 Seconds | | position.gps_attempt_time | `integer` (seconds) | Default of `0` is 30 Seconds | | position.fixed_position | `true`, `false` | `false` | -| position.broadcast_smart_enabled | `true`, `false` | `true` | +| position.position_broadcast_smart_enabled | `true`, `false` | `true` | | position.broadcast_secs | `integer` (seconds) | Default of `0` is 15 Minutes | | position.flags | `UNSET`, `ALTITUDE`, `ALTITUDE_MSL`, `GEOIDAL_SEPARATION`, `DOP`, `HVDOP`, `PDOP`, `SATINVIEW`, `SEQ_NO`, `TIMESTAMP`, `HEADING`, `SPEED` | `UNSET` | @@ -182,4 +182,4 @@ All position config options are available in the Web UI. :::caution Altering/disabling the GPS functionality does not mean that you will be unable to be found. Via triangulation of your radio, location may be given up to someone if they are determined enough. -::: \ No newline at end of file +::: From c152030ec07953703745a3a005fdf6d54c8432db Mon Sep 17 00:00:00 2001 From: IZ1IVA <75425638+IZ1IVA@users.noreply.github.com> Date: Thu, 27 Oct 2022 19:58:14 +0200 Subject: [PATCH 5/7] Fixed discrepancy --- docs/settings/config/position.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/settings/config/position.mdx b/docs/settings/config/position.mdx index f060714e..1ff09368 100644 --- a/docs/settings/config/position.mdx +++ b/docs/settings/config/position.mdx @@ -110,7 +110,7 @@ All Position config commands are available in the python CLI. Example commands a | position.gps_attempt_time | `integer` (seconds) | Default of `0` is 30 Seconds | | position.fixed_position | `true`, `false` | `false` | | position.broadcast_smart_enabled | `true`, `false` | `true` | -| position.broadcast_secs | `integer` (seconds) | Default of `0` is 15 Minutes | +| position.position_broadcast_secs | `integer` (seconds) | Default of `0` is 15 Minutes | | position.flags | `UNSET`, `ALTITUDE`, `ALTITUDE_MSL`, `GEOIDAL_SEPARATION`, `DOP`, `HVDOP`, `PDOP`, `SATINVIEW`, `SEQ_NO`, `TIMESTAMP`, `HEADING`, `SPEED` | `UNSET` | @@ -182,4 +182,4 @@ All position config options are available in the Web UI. :::caution Altering/disabling the GPS functionality does not mean that you will be unable to be found. Via triangulation of your radio, location may be given up to someone if they are determined enough. -::: \ No newline at end of file +::: From 0a1919687de109c26dcffa46b81d296582ced1c5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20G=C3=B6ttgens?= Date: Thu, 27 Oct 2022 21:48:18 +0200 Subject: [PATCH 6/7] Update position.mdx --- docs/settings/config/position.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/settings/config/position.mdx b/docs/settings/config/position.mdx index d9a9f1db..0161be7e 100644 --- a/docs/settings/config/position.mdx +++ b/docs/settings/config/position.mdx @@ -109,7 +109,7 @@ All Position config commands are available in the python CLI. Example commands a | position.gps_update_interval | `integer` (seconds) | Default `0` is 30 Seconds | | position.gps_attempt_time | `integer` (seconds) | Default of `0` is 30 Seconds | | position.fixed_position | `true`, `false` | `false` | -| position.position_broadcast_smart_enabled | `true`, `false` | `true` | `true`, `false` | `true` | +| position.position_broadcast_smart_enabled | `true`, `false` | `true` | | position.position_broadcast_secs | `integer` (seconds) | Default of `0` is 15 Minutes | | position.flags | `UNSET`, `ALTITUDE`, `ALTITUDE_MSL`, `GEOIDAL_SEPARATION`, `DOP`, `HVDOP`, `PDOP`, `SATINVIEW`, `SEQ_NO`, `TIMESTAMP`, `HEADING`, `SPEED` | `UNSET` | From 6e9c6a47379793e57be4ffb53b711bf51d634b5e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20G=C3=B6ttgens?= Date: Thu, 27 Oct 2022 21:59:35 +0200 Subject: [PATCH 7/7] Update build.mdx --- docs/developers/Firmware/build.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/developers/Firmware/build.mdx b/docs/developers/Firmware/build.mdx index 677e3f41..d0cd9088 100644 --- a/docs/developers/Firmware/build.mdx +++ b/docs/developers/Firmware/build.mdx @@ -33,23 +33,23 @@ The build system is modular. Adding a new board variant for an already supported ### Building for your own DIY hardware or mod that you don't want to distribute -1. go to the `variants` folder in the Meshtastic-device sourcecode and make a new directory for your hardware, let's call it `m5stack_core` and copy an existing configuration you wanna modify +1. go to the `variants` folder in the Meshtastic-device sourcecode and make a new directory for your hardware, let's call it `m5stack_atom` and copy an existing configuration you wanna modify ```shell - cd variants; mkdir m5stack_core - cp heltec_v1/* m5stack_core - cd m5stack_core + cd variants; mkdir m5stack_atom + cp heltec_v1/* m5stack_atom + cd m5stack_atom ``` 2. modify the `platformio.ini` _in this subdirectory_ from the canonical define of the hardware variant (`HELTEC_V1` in this case) to `PRIVATE_HW` and make the `-I` on the `build_flags` point to the newly created dir. ```shell - [env:m5stack-core] + [env:m5stack-atom] extends = esp32_base - board = m5stack-core-esp32 + board = m5stack-atom monitor_filters = esp32_exception_decoder build_flags = - ${esp32_base.build_flags} -D PRIVATE_HW -I variants/m5stack_core + ${esp32_base.build_flags} -D PRIVATE_HW -I variants/m5stack_atom lib_deps = ${esp32_base.lib_deps} ```