docs(parts): v3 case cables, power input, and working Mouser links - #273
Merged
Merged
Conversation
Add the 200 mm Raspberry Pi display cable (SC1131) the Touch Display 2 needs in the openflight-enclosure v3 case, where the Pi and UPS mount to the shell rather than the screen and the ~100 mm ribbon in the box does not reach (openflight-enclosure#11). Document power input on the v3 case: the shell has no USB-C opening, so a USB-C supply is captive and a detachable supply is the DC route. Add the no-solder parts for it (a pre-wired 5.5 x 2.1 mm panel jack, Tensility 10-03609 on Mouser or Amazon DC-099 kits; two Wago 221-412 for the XH header option; the Adafruit 369 screw-terminal plug for the barrel option into the X1202's own jack, with the plug dimensions), fed at 12 V because the XH input is rated for about 3 A. Note that 5 A USB-C pass-throughs are hard to find. Give every Mouser ProductDetail link the ?qs= token from the shared Mouser project, which is the form Mouser still resolves, add Amazon options beside them, and move the Qwiic-to-Dupont row to the SparkFun CAB-17261 the project carries. Move every measured distance out of the product rows into the collapsible cable-lengths section and replace the v2 table with runs measured on the v3 STEP, including the display and camera ribbons, Ethernet, both DC jack options and both button-hole options. Record that both rear holes in the v3 shell are 12.5 mm, so the 16 mm Adafruit 1445 needs the CAD hole opened or a 12 mm button. Replace the v2 insert and screw table with a link to the enclosure repository's Required hardware page, re-base the filament estimate on the v3 print set from the STL mesh volumes (~750 g PETG, ~$17) inside a collapsible block, and fold the deprecated K-LD7 section into one too. Drop the DS3502 potentiometer and its cable, since the internal trigger in PR open-flight#221 makes a software gain trim moot; drop the IARC case and the X1206 input-range comparison; correct the internal-trigger firmware to OPS243-A 1.3.2. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com>
HuggeK
force-pushed
the
docs/v3-parts-cables
branch
from
September 21, 2026 15:38
9660a70 to
24117c7
Compare
HuggeK
marked this pull request as ready for review
September 21, 2026 15:41
jewbetcha
approved these changes
Sep 21, 2026
10 tasks
Contributor
|
@HuggeK To avoid risking burning OF boards, could you please add information about polarity of the DC 5521 power jack on the X1202/X1206 (Geekworm wiki give the center pin of the DC 5521 jack is positive (+) for X1202, I post a question on Geekworm wiki for the X1206 ) |
Contributor
Author
Absolutely, will add that tomorrow - linking in the appropriate sections to the Geekworm wiki. |
Contributor
|
I got a response from Geekworm. The center pin of the DC 5521 jack is positive (+) also for X1206 |
This was referenced Sep 22, 2026
Contributor
Author
|
Ok, I put up PR # mentioning this and moving the powering part as discussed in the #enclosure channel to its on .md file becuase the parts.md got kinda clustered with it now that there is two ways to power it for the pi only design, the proposed pi + powerboard to get DC jack input or the UPS route in: #275 |
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is fixed to the brick and the v3 shell has no USB-C opening, so it stays captive to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes 5 V USB-C only and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. The cost summary is rebuilt as four staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Boards and power 482 + angle radar 632 + case, a usable unit 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The subtotals now say what they are rather than implying a finished unit: $482 buys boards on a bench, and ~$684 in a case is the realistic entry price, with the caveat that $52 assumes you print it yourself. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure and a ready-to-use subtotal, so its headline is a unit you can pick up rather than a pile of boards. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is fixed to the brick and the v3 shell has no USB-C opening, so it stays captive to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes 5 V USB-C only and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is fixed to the brick and the v3 shell has no USB-C opening, so it stays captive to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes 5 V USB-C only and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is fixed to the brick and the v3 shell has no USB-C opening, so it stays captive to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes 5 V USB-C only and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is fixed to the brick and the v3 shell has no USB-C opening, so it stays captive to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes 5 V USB-C only and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is fixed to the brick and the v3 shell has no USB-C opening, so it stays captive to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes 5 V USB-C only and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is fixed to the brick and the v3 shell has no USB-C opening, so it stays captive to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes 5 V USB-C only and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is fixed to the brick and the v3 shell has no USB-C opening, so it stays captive to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes 5 V USB-C only and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. The documentation list links the new page, and it is in the site nav and the Get Started index. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is captive to the brick and the shell has no USB-C socket to unplug at, so it stays tethered to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. There is also a 2b, which is the only way to have batteries without a barrel plug anywhere in the build: both UPS boards take 5 V 5 A on their own USB-C socket, and 5 V 5 A is exactly what the route 1 supply exists to make, so the official brick can feed the UPS directly. Geekworm list the X1202's USB-C input as "Compatible with Raspberry Pi USB-C Power Supply", and on the X1206 V1.1 they "strongly recommend" it over the DC jack, so on that revision it is the recommended input rather than a workaround. It drops the adapter, the panel jack, the Wagos and the XH lead, which is $26 of parts and every step where a polarity can be got wrong, at the price of keeping the tether and charging more slowly: 25 W in barely covers a Pi that can pull 25.5 W at peak, so the pack tops up when the rig is idle rather than under load. The shell does not stand in the way of that. It has no USB-C socket, but the plug passes through a rear opening, and the USB-C specification caps a plug's overmould at 12.35 x 6.5 mm: the 16.0 x 14.0 mm Ethernet cut-out takes any legal plug, and the 12.5 mm DC hole takes most of them. The page says to measure first, because a plug that is square in section is limited by its corner-to-corner diagonal rather than its width. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. That rule is also what lets the barrel option into the UPS be either kind of plug. A screw-terminal plug takes the panel jack's leads directly, but a plug already on a flying lead does the same job, joined with the same two Wagos as the header option, so long as that lead carries the 3 A. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes USB-C 5 V, or 5-6 V on its DC input, and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. The documentation list links the new page, and it is in the site nav and the Get Started index. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is captive to the brick and the shell has no USB-C socket to unplug at, so it stays tethered to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. There is also a 2b, for anyone who can live with a supply that does not detach. The barrel jack stays the default for a UPS build, since being able to unplug at the case is most of the reason to fit a panel jack, and none of that route is removed. But both UPS boards take 5 V 5 A on their own USB-C socket, and 5 V 5 A is exactly what the route 1 supply exists to make, so the official captive brick can feed the UPS directly, and that is the only way to have batteries with no barrel plug anywhere in the build. Geekworm list the X1202's USB-C input as "Compatible with Raspberry Pi USB-C Power Supply", and on the X1206 V1.1 they "strongly recommend" it over the DC jack, so on that revision it is the recommended input rather than a workaround. It drops the adapter, the panel jack, the Wagos and the XH lead, which is $26 of parts and every step where a polarity can be got wrong. The price is that nothing detaches at the case and charging is slower: 25 W in barely covers a Pi that can pull 25.5 W at peak, so the pack tops up when the rig is idle rather than under load. The page says which of the two to build rather than leaving it as a preference. The shell does not stand in the way of that. It has no USB-C socket, but the plug passes through a rear opening, and the USB-C specification caps a plug's overmould at 12.35 x 6.5 mm: the 16.0 x 14.0 mm Ethernet cut-out takes any legal plug, and the 12.5 mm DC hole takes most of them. The page says to measure first, because a plug that is square in section is limited by its corner-to-corner diagonal rather than its width. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. That rule is also what lets the barrel option into the UPS be either kind of plug. A screw-terminal plug takes the panel jack's leads directly, but a plug already on a flying lead does the same job, joined with the same two Wagos as the header option, so long as that lead carries the 3 A. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes USB-C 5 V, or 5-6 V on its DC input, and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. The documentation list links the new page, and it is in the site nav and the Get Started index. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is captive to the brick and the shell has no USB-C socket to unplug at, so it stays tethered to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. There is also a 2b, for anyone who can live with a supply that does not detach. The barrel jack stays the default for a UPS build, since being able to unplug at the case is most of the reason to fit a panel jack, and none of that route is removed. But both UPS boards take 5 V 5 A on their own USB-C socket, and 5 V 5 A is exactly what the route 1 supply exists to make, so the official captive brick can feed the UPS directly, and that is the only way to have batteries with no barrel plug anywhere in the build. Geekworm list the X1202's USB-C input as "Compatible with Raspberry Pi USB-C Power Supply", and on the X1206 V1.1 they "strongly recommend" it over the DC jack, so on that revision it is the recommended input rather than a workaround. It drops the adapter, the panel jack and the lead into the board, which is about $25 of parts and every step where a polarity can be got wrong. The price is that nothing detaches at the case and charging is slower: 25 W in barely covers a Pi that can pull 25.5 W at peak, so the pack tops up when the rig is idle rather than under load. The page says which of the two to build rather than leaving it as a preference. The shell does not stand in the way of that. It has no USB-C socket, but the plug passes through a rear opening: the official supply's plug measures 12.0 mm across at its widest, which clears the 12.5 mm DC hole, and the 16.0 x 14.0 mm Ethernet cut-out has room to spare. Measured on the supply itself rather than derived from the USB-C envelope, so the page states it rather than working through it. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. The two ways into the UPS are reordered so the shorter one leads. A screw-terminal barrel plug takes the panel jack's stripped leads directly and goes into the board's own jack, and that is the whole run: no Wago splices, no XH lead, nothing crimped or soldered. Wagos only ever existed to join two leads, so they are needed for the XH header option, or for a barrel plug that arrived pre-wired, and the parts table says that rather than listing them as unconditional. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes USB-C 5 V, or 5-6 V on its DC input, and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. The documentation list links the new page, and it is in the site nav and the Get Started index. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is captive to the brick and the shell has no USB-C socket to unplug at, so it stays tethered to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. There is also a 2b, for anyone who can live with a supply that does not detach. The barrel jack stays the default for a UPS build, since being able to unplug at the case is most of the reason to fit a panel jack, and none of that route is removed. But both UPS boards take 5 V 5 A on their own USB-C socket, and 5 V 5 A is exactly what the route 1 supply exists to make, so the official captive brick can feed the UPS directly, and that is the only way to have batteries with no barrel plug anywhere in the build. Geekworm list the X1202's USB-C input as "Compatible with Raspberry Pi USB-C Power Supply", and on the X1206 V1.1 they "strongly recommend" it over the DC jack, so on that revision it is the recommended input rather than a workaround. It drops the adapter, the panel jack and the lead into the board, which is about $25 of parts and every step where a polarity can be got wrong. The price is that nothing detaches at the case and charging is slower: 25 W in barely covers a Pi that can pull 25.5 W at peak, so the pack tops up when the rig is idle rather than under load. The page says which of the two to build rather than leaving it as a preference. The shell does not stand in the way of that. It has no USB-C socket, but the plug passes through a rear opening: the official supply's plug measures 12.0 mm across at its widest, which clears the 12.5 mm DC hole, and the 16.0 x 14.0 mm Ethernet cut-out has room to spare. Measured on the supply itself rather than derived from the USB-C envelope, so the page states it rather than working through it. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. The two ways into the UPS are reordered so the shorter one leads. A screw-terminal barrel plug takes the panel jack's stripped leads directly and goes into the board's own jack, and that is the whole run: no Wago splices, no XH lead, nothing crimped or soldered. Wagos only ever existed to join two leads, so they are needed for the XH header option, or for a barrel plug that arrived pre-wired, and the parts table says that rather than listing them as unconditional. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes USB-C 5 V, or 5-6 V on its DC input, and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. The documentation list links the new page, and it is in the site nav and the Get Started index. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around five routes, and parts.md keeps the accessories every build needs whichever route you pick. The five routes: 1. The official 27 W supply. Its cable is captive to the brick and the shell has no USB-C socket to unplug at, so it stays tethered to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. 4. A USB-C PD charger or power bank through a VFLEX or a PD trigger board. 5. Power over Ethernet through an 802.3bt splitter, which suits this case because the shell already has an Ethernet opening beside the DC hole. Routes 4 and 5 feed routes 2 or 3 rather than replacing them. There is also a 2b, for anyone who can live with a supply that does not detach. The barrel jack stays the default for a UPS build, since being able to unplug at the case is most of the reason to fit a panel jack, and none of that route is removed. But both UPS boards take 5 V 5 A on their own USB-C socket, and 5 V 5 A is exactly what the route 1 supply exists to make, so the official captive brick can feed the UPS directly, and that is the only way to have batteries with no barrel plug anywhere in the build. Geekworm list the X1202's USB-C input as "Compatible with Raspberry Pi USB-C Power Supply", and on the X1206 V1.1 they "strongly recommend" it over the DC jack, so on that revision it is the recommended input rather than a workaround. It drops the adapter, the panel jack and the lead into the board, which is about $25 of parts and every step where a polarity can be got wrong. The price is that nothing detaches at the case and charging is slower: 25 W in barely covers a Pi that can pull 25.5 W at peak, so the pack tops up when the rig is idle rather than under load. The page says which of the two to build rather than leaving it as a preference. The shell does not stand in the way of that. It has no USB-C socket, but the plug passes through a rear opening: the official supply's plug measures 12.0 mm across at its widest, which clears the 12.5 mm DC hole, and the 16.0 x 14.0 mm Ethernet cut-out has room to spare. Measured on the supply itself rather than derived from the USB-C envelope, so the page states it rather than working through it. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. The two ways into the UPS are reordered so the shorter one leads. A screw-terminal barrel plug takes the panel jack's stripped leads directly and goes into the board's own jack, and that is the whole run: no Wago splices, no XH lead, nothing crimped or soldered. Wagos only ever existed to join two leads, so they are needed for the XH header option, or for a barrel plug that arrived pre-wired, and the parts table says that rather than listing them as unconditional. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes USB-C 5 V, or 5-6 V on its DC input, and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. The documentation list links the new page, and it is in the site nav and the Get Started index. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around three routes, a battery variant of one of them, and two add-ons, and parts.md keeps the accessories every build needs whichever route you pick. The routes: 1. The official 27 W supply. Its cable is captive to the brick and the shell has no USB-C socket to unplug at, so it stays tethered to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. A USB-C PD charger or power bank through a VFLEX or a PD trigger board, and Power over Ethernet through an 802.3bt splitter, are not routes and are no longer numbered as though they were. Each only changes what plugs into the barrel jack in the back of the case, with the UPS or the converter behind that jack unchanged, so both now sit under a "what plugs into the barrel jack" table next to the wall adapter they stand in for. PoE suits this case in particular, because the shell already has an Ethernet opening beside the DC hole. There is also a 2b, for anyone who can live with a supply that does not detach. The barrel jack stays the default for a UPS build, since being able to unplug at the case is most of the reason to fit a panel jack, and none of that route is removed. But both UPS boards take 5 V 5 A on their own USB-C socket, and 5 V 5 A is exactly what the route 1 supply exists to make, so the official captive brick can feed the UPS directly, and that is the only way to have batteries with no barrel plug anywhere in the build. Geekworm list the X1202's USB-C input as "Compatible with Raspberry Pi USB-C Power Supply", and on the X1206 V1.1 they "strongly recommend" it over the DC jack, so on that revision it is the recommended input rather than a workaround. It drops the adapter, the panel jack and the lead into the board, which is about $25 of parts and every step where a polarity can be got wrong. The price is that nothing detaches at the case and charging is slower: 25 W in barely covers a Pi that can pull 25.5 W at peak, so the pack tops up when the rig is idle rather than under load. The page says which of the two to build rather than leaving it as a preference. The shell does not stand in the way of that. It has no USB-C socket, but the plug passes through a rear opening: the official supply's plug measures 12.0 mm across at its widest, which clears the 12.5 mm DC hole, and the 16.0 x 14.0 mm Ethernet cut-out has room to spare. Measured on the supply itself rather than derived from the USB-C envelope, so the page states it rather than working through it. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. The two ways into the UPS are reordered so the shorter one leads. A screw-terminal barrel plug takes the panel jack's stripped leads directly and goes into the board's own jack, and that is the whole run: no Wago splices, no XH lead, nothing crimped or soldered. Wagos only ever existed to join two leads, so they are needed for the XH header option, or for a barrel plug that arrived pre-wired, and the parts table says that rather than listing them as unconditional. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes USB-C 5 V, or 5-6 V on its DC input, and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. The documentation list links the new page, and it is in the site nav and the Get Started index. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around three routes, a battery variant of one of them, and two add-ons, and parts.md keeps the accessories every build needs whichever route you pick. The routes: 1. The official 27 W supply. Its cable is captive to the brick, and there is no panel connector to unplug at either, because a USB-C pass-through carrying a genuine 5 A is not a practical part to buy. So it stays tethered to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. A USB-C PD charger or power bank through a VFLEX or a PD trigger board, and Power over Ethernet through an 802.3bt splitter, are not routes and are no longer numbered as though they were. Each only changes what plugs into the barrel jack in the back of the case, with the UPS or the converter behind that jack unchanged, so both now sit under a "what plugs into the barrel jack" table next to the wall adapter they stand in for. PoE suits this case in particular, because the shell already has an Ethernet opening beside the DC hole. There is also a 2b, for anyone who can live with a supply that does not detach. The barrel jack stays the default for a UPS build, since being able to unplug at the case is most of the reason to fit a panel jack, and none of that route is removed. But both UPS boards take 5 V 5 A on their own USB-C socket, and 5 V 5 A is exactly what the route 1 supply exists to make, so the official captive brick can feed the UPS directly, and that is the only way to have batteries with no barrel plug anywhere in the build. Geekworm list the X1202's USB-C input as "Compatible with Raspberry Pi USB-C Power Supply", and on the X1206 V1.1 they "strongly recommend" it over the DC jack, so on that revision it is the recommended input rather than a workaround. It drops the adapter, the panel jack and the lead into the board, which is about $25 of parts and every step where a polarity can be got wrong. The price is that nothing detaches at the case and charging is slower: 25 W in barely covers a Pi that can pull 25.5 W at peak, so the pack tops up when the rig is idle rather than under load. The page says which of the two to build rather than leaving it as a preference. The shell does not stand in the way of that. There is no USB-C panel connector in it, which is not an oversight — a pass-through rated for a genuine 5 A is not a practical part, and the repo's own USB-C rear shells are EOL for "USB-C spec compatibility" — but the plug passes through a rear opening: the official supply's plug measures 12.0 mm across at its widest, which clears the 12.5 mm DC hole, and the 16.0 x 14.0 mm Ethernet cut-out has room to spare. Measured on the supply itself rather than derived from the USB-C envelope, so the page states it rather than working through it. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. The two ways into the UPS are reordered so the shorter one leads. A screw-terminal barrel plug takes the panel jack's stripped leads directly and goes into the board's own jack, and that is the whole run: no Wago splices, no XH lead, nothing crimped or soldered. Wagos only ever existed to join two leads, so they are needed for the XH header option, or for a barrel plug that arrived pre-wired, and the parts table says that rather than listing them as unconditional. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes USB-C 5 V, or 5-6 V on its DC input, and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. The documentation list links the new page, and it is in the site nav and the Get Started index. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around three routes, a battery variant of one of them, and two add-ons, and parts.md keeps the accessories every build needs whichever route you pick. The routes: 1. The official 27 W supply. Its cable is captive to the brick, and there is no panel connector to unplug at either, because a USB-C pass-through carrying a genuine 5 A is not a practical part to buy. So it stays tethered to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. A USB-C PD charger or power bank through a VFLEX or a PD trigger board, and Power over Ethernet through an 802.3bt splitter, are not routes and are no longer numbered as though they were. Each only changes what plugs into the barrel jack in the back of the case, with the UPS or the converter behind that jack unchanged, so both now sit under a "what plugs into the barrel jack" table next to the wall adapter they stand in for. PoE suits this case in particular, because the shell already has an Ethernet opening beside the DC hole. There is also a 2b, for anyone who can live with a supply that does not detach. The barrel jack stays the default for a UPS build, since being able to unplug at the case is most of the reason to fit a panel jack, and none of that route is removed. But both UPS boards take 5 V 5 A on their own USB-C socket, and 5 V 5 A is exactly what the route 1 supply exists to make, so the official captive brick can feed the UPS directly, and that is the only way to have batteries with no barrel plug anywhere in the build. Geekworm list the X1202's USB-C input as "Compatible with Raspberry Pi USB-C Power Supply", and on the X1206 V1.1 they "strongly recommend" it over the DC jack, so on that revision it is the recommended input rather than a workaround. It drops the adapter, the panel jack and the lead into the board, which is about $25 of parts and every step where a polarity can be got wrong. The price is that nothing detaches at the case and charging is slower: 25 W in barely covers a Pi that can pull 25.5 W at peak, so the pack tops up when the rig is idle rather than under load. The page says which of the two to build rather than leaving it as a preference. The shell does not stand in the way of that. There is no USB-C panel connector in it, which is not an oversight — a pass-through rated for a genuine 5 A is not a practical part, and the repo's own USB-C rear shells are EOL for "USB-C spec compatibility" — but the plug passes through a rear opening: the official supply's plug measures 12.0 mm across at its widest, which clears the 12.5 mm DC hole, and the 16.0 x 14.0 mm Ethernet cut-out has room to spare. Measured on the supply itself rather than derived from the USB-C envelope, so the page states it rather than working through it. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. The two ways into the UPS are reordered so the shorter one leads. A screw-terminal barrel plug takes the panel jack's stripped leads directly and goes into the board's own jack, and that is the whole run: no Wago splices, no XH lead, nothing crimped or soldered. Wagos only ever existed to join two leads, so they are needed for the XH header option, or for a barrel plug that arrived pre-wired, and the parts table says that rather than listing them as unconditional. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes USB-C 5 V, or 5-6 V on its DC input, and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. The documentation list links the new page, and it is in the site nav and the Get Started index. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 22, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around three routes, a battery variant of one of them, and two add-ons, and parts.md keeps the accessories every build needs whichever route you pick. The routes: 1. The official 27 W supply. Its cable is captive to the brick, and there is no panel connector to unplug at either, because a USB-C pass-through carrying a genuine 5 A is not a practical part to buy. So it stays tethered to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. A USB-C PD charger or power bank through a VFLEX or a PD trigger board, and Power over Ethernet through an 802.3bt splitter, are not routes and are no longer numbered as though they were. Each only changes what plugs into the barrel jack in the back of the case, with the UPS or the converter behind that jack unchanged, so both now sit under a "what plugs into the barrel jack" table next to the wall adapter they stand in for. PoE suits this case in particular, because the shell already has an Ethernet opening beside the DC hole. There is also a 2b, for anyone who can live with a supply that does not detach. The barrel jack stays the default for a UPS build, since being able to unplug at the case is most of the reason to fit a panel jack, and none of that route is removed. But both UPS boards take 5 V 5 A on their own USB-C socket, and 5 V 5 A is exactly what the route 1 supply exists to make, so the official captive brick can feed the UPS directly, and that is the only way to have batteries with no barrel plug anywhere in the build. Geekworm list the X1202's USB-C input as "Compatible with Raspberry Pi USB-C Power Supply", and on the X1206 V1.1 they "strongly recommend" it over the DC jack, so on that revision it is the recommended input rather than a workaround. It drops the adapter, the panel jack and the lead into the board, which is about $25 of parts and every step where a polarity can be got wrong. The price is that nothing detaches at the case and charging is slower: 25 W in barely covers a Pi that can pull 25.5 W at peak, so the pack tops up when the rig is idle rather than under load. The page says which of the two to build rather than leaving it as a preference. The shell does not stand in the way of that. There is no USB-C panel connector in it, which is not an oversight — a pass-through rated for a genuine 5 A is not a practical part, and the repo's own USB-C rear shells are EOL for "USB-C spec compatibility" — but the plug passes through a rear opening: the official supply's plug measures 12.0 mm across at its widest, which clears the 12.5 mm DC hole, and the 16.0 x 14.0 mm Ethernet cut-out has room to spare. Measured on the supply itself rather than derived from the USB-C envelope, so the page states it rather than working through it. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. The two ways into the UPS are reordered so the shorter one leads. A screw-terminal barrel plug takes the panel jack's stripped leads directly and goes into the board's own jack, and that is the whole run: no Wago splices, no XH lead, nothing crimped or soldered. Wagos only ever existed to join two leads, so they are needed for the XH header option, or for a barrel plug that arrived pre-wired, and the parts table says that rather than listing them as unconditional. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes USB-C 5 V, or 5-6 V on its DC input, and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. The documentation list links the new page, and it is in the site nav and the Get Started index. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HuggeK
added a commit
to HuggeK/openflight
that referenced
this pull request
Sep 23, 2026
Power decisions were scattered across two tables and three blockquotes in the parts list. That hid the thing that matters most: picking a power route decides about six purchases at once, and one of those routes can destroy the build if it is wired backwards. All of it moves to a new docs/get-started/power.md built around three routes, a battery variant of one of them, and two add-ons, and parts.md keeps the accessories every build needs whichever route you pick. The routes: 1. The official 27 W supply. Its cable is captive to the brick, and there is no panel connector to unplug at either, because a USB-C pass-through carrying a genuine 5 A is not a practical part to buy. So it stays tethered to the case. The page says plainly why it is still the right default: nothing to wire, nothing extra to buy, and no unkeyed barrel plug near the boards. 2. A Geekworm X1202/X1206 UPS HAT. Leads with the trap, which is that a UPS HAT is not one purchase: it arrives with neither cells nor any way to get power into it, so the DC adapter, the panel jack and the leads that join them have to be bought at the same time. 3. A Geekworm Pi5-5V5APD, for a detachable lead without batteries. Flags that it needs more than 30 W in, so the official 27 W brick will not drive it, and that the case has no mount for it. A USB-C PD charger or power bank through a VFLEX or a PD trigger board, and Power over Ethernet through an 802.3bt splitter, are not routes and are no longer numbered as though they were. Each only changes what plugs into the barrel jack in the back of the case, with the UPS or the converter behind that jack unchanged, so both now sit under a "what plugs into the barrel jack" table next to the wall adapter they stand in for. PoE suits this case in particular, because the shell already has an Ethernet opening beside the DC hole. There is also a 2b, for anyone who can live with a supply that does not detach. The barrel jack stays the default for a UPS build, since being able to unplug at the case is most of the reason to fit a panel jack, and none of that route is removed. But both UPS boards take 5 V 5 A on their own USB-C socket, and 5 V 5 A is exactly what the route 1 supply exists to make, so the official captive brick can feed the UPS directly, and that is the only way to have batteries with no barrel plug anywhere in the build. Geekworm list the X1202's USB-C input as "Compatible with Raspberry Pi USB-C Power Supply", and on the X1206 V1.1 they "strongly recommend" it over the DC jack, so on that revision it is the recommended input rather than a workaround. It drops the adapter, the panel jack and the lead into the board, which is about $25 of parts and every step where a polarity can be got wrong. The price is that nothing detaches at the case and charging is slower: 25 W in barely covers a Pi that can pull 25.5 W at peak, so the pack tops up when the rig is idle rather than under load. The page says which of the two to build rather than leaving it as a preference. The shell does not stand in the way of that. There is no USB-C panel connector in it, which is not an oversight — a pass-through rated for a genuine 5 A is not a practical part, and the repo's own USB-C rear shells are EOL for "USB-C spec compatibility" — but the plug passes through a rear opening: the official supply's plug measures 12.0 mm across at its widest, which clears the 12.5 mm DC hole, and the 16.0 x 14.0 mm Ethernet cut-out has room to spare. Measured on the supply itself rather than derived from the USB-C envelope, so the page states it rather than working through it. Adds the barrel-jack polarity section JedS asked for on open-flight#273. A 5.5 x 2.1 mm plug has no keying, so a centre-negative supply mates perfectly with a centre-positive jack and reverses the rail into the Pi, the UPS and both radars at once. The X1202 and X1206 are both centre pin positive; since Geekworm's wiki does not state it either way, the page cites the exchange where Geekworm confirmed it rather than sending readers to a page that will not answer them. Adds wire sizing for the DC run, the only part of this build carrying real current: 20 AWG or heavier, 22 AWG as the floor on a sub-100 mm run, and not the 26 AWG lead whose connector would otherwise fit. The two ways into the UPS are reordered so the shorter one leads. A screw-terminal barrel plug takes the panel jack's stripped leads directly and goes into the board's own jack, and that is the whole run: no Wago splices, no XH lead, nothing crimped or soldered. Wagos only ever existed to join two leads, so they are needed for the XH header option, or for a barrel plug that arrived pre-wired, and the parts table says that rather than listing them as unconditional. On lithium safety, Geekworm's guidance is about charging rather than storage: "When charging the Battery Pack, please place the battery in a fireproof container." There is no Geekworm guidance about storing cells and no mention of a metal or airtight container, so the page says what they actually say, and notes that the battery-handling site their template links to no longer resolves. Corrections found while moving things: - X1206 V1.1 takes USB-C 5 V, or 5-6 V on its DC input, and wide voltage will burn it out. The old text implied the 12 V route applied to every X1206. - The v3 case wants a 12 mm power button, not the 16 mm one the cost lines named. - Geekworm states flat-top for the X1202's 18650s but only "unprotected" for the X1206's 21700s. - A long-reach hex key is no longer called required. The case screws sit deep in the shell, so a driver needs about 90 mm of reach, but the head type follows whichever screws you buy. The cost summary is rebuilt as three staged tables with running totals, so you can see what it costs to stop at each point instead of reading one number off a flat list that mixed required parts, optional extras and mutually exclusive alternatives in a single column. Doing the arithmetic turned up three errors: - The Core line read $355 while its own rows sum to $425. Checked rather than assumed: Adafruit 5812 is a Pi 5 4 GB at $130, so the rows were right and the summary understated every build by $70. The README carried the same gap. - The micro-USB cable was counted twice. There is one cable and the layout decides which board it plugs into: the OPS243 when it is the only radar, the IWR6843LEVM once Layout A moves the OPS243 to the GPIO UART. - The angle radar's GATE-to-BCM17 jumper was counted twice, being one wire from the pack the Sound Trigger line already buys. The battery line also costed only the HAT, the cells and the button, when a UPS cannot be powered in a closed case without a DC adapter, a panel jack and the leads between them. Those are now in it, itemised, and expressed as a net add because a UPS replaces the 27 W supply rather than adding to it. Base build, OPS243 in its case 534 + angle radar 684 + inclinometer and camera 729 Everything, X1202 battery power 819 Everything, X1206 instead 831 The enclosure sits in the base rather than under optional, because you need one whichever radars you fit and the same printed set covers both builds: the radar front carries mounts for the OPS243 and the IWR6843, so an OPS-only build prints the same parts and leaves the IWR mounts empty. Nothing measures repeatably until the boards are held in a fixed arrangement. The $52 assumes you print it yourself. build-order.md follows, moving the enclosure out of Optional extras into a step of its own, and pointing that step at the openflight-enclosure repository rather than the IARC case: choose a variant, required hardware, print, assemble. The IARC page is kept as a note for existing builds only. Also in the same files: - The firmware hex for the internal-trigger route can be requested on OmniPreSense's Discord or through the contact page on their site, not only by email. Sandy at OmniPreSense offered both. - Explains why the internal trigger is worth wanting beyond the parts it saves: a microphone cannot distinguish your strike from the rest of the room, so a noisy range is what the sound trigger handles worst. Marked as the expectation rather than a measured result. - Drops the claim that this build needs no soldering, which contradicted the R17 resistor and the heat-set inserts. - Trims the J-Link EDU Mini row to what is in the box. - Shortens five cable rows that re-derived their lengths in the row text when the Cable Lengths section already covers it. - Names the rear DC jack and power button in Enclosure Hardware, since they fall between that list and the enclosure repository's. README's hardware table gains the enclosure, so its headline figure is a unit you can pick up rather than a pile of boards, and both glance tables say the 27 W supply's cable is captive, since that is the tradeoff the route page spends a section on. The documentation list links the new page, and it is in the site nav and the Get Started index. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Brings
docs/get-started/parts.mdin line with the openflight-enclosure v3 case and with Mouser's changed product URLs. One file, docs only.XH2.54-2PDC input (panel DC jack with leads, one JST XH lead, two Wago 221 lever connectors) and the barrel-plug alternative into the X1202's own jack with the plug dimensions, using Adafruit 369 (a 5.5 × 2.1 mm plug on a screw-terminal block, listed by Mouser) so that option needs no Wagos. Both are fed at 12 V because the XH connector is rated for about 3 A.ProductDetaillink now carries the?qs=token from the shared Mouser project, which is the form Mouser still resolves; parts the project does not carry keep a Mouser search link. The Qwiic-to-Dupont row moves from Adafruit 4397 (Mouser page broken) to the SparkFun CAB-17261 that is in the project, with the Adafruit part kept as the direct-order alternative.PSWheader from the middle hole with slack but from the right-hand hole only pulled straight.?V), and the two cases: units shipping since OmniPreSense's 2026-09-10 note arrive with 1.3.2, older ones are flashed over theJ2JTAG header with a SEGGER J-Link and Infineon's XMCFlasher per AN-013 (SWD mode, XMC4500-1024 or XMC4700 per?P, hex from OmniPreSense support, never Erase, the Windows driver caveat from the upgrade done on a project unit). A one-row table for the SEGGER J-Link EDU Mini (Adafruit 3571, ~$76, in the Mouser project, with Amazon and Adafruit links) puts the cost of that route next to the $18 detector, and the Cost Summary paragraph says the same.Why was this required?
The parts page was written against the v2 Onshape housing, which the project no longer designs against; the openflight-enclosure v3 case (released 2026-09-15, re-laid out in openflight-enclosure#10 on 2026-09-21) is what builders print now. Following the page as it stood, a builder would buy a Touch Display 2 without the display cable that the v3 layout needs (a tester hit exactly this, openflight-enclosure#11), would have no documented way to get power into the case, would order a 16 mm power button for a case whose hole is 12.5 mm, and would read the wrong firmware version for the internal trigger. On top of that, Mouser changed its URL handling in September 2026 and every product link on the page stopped resolving, so the ordering shortcut the page is built around was broken. Not doing this means wrong orders and a second shopping round for anyone building the v3 case.
Automated tests
None added: this PR changes one Markdown file and no code. The automated coverage that applies is the existing CI on the PR (docs site build, lint, format, Python tests, UI build and e2e), which passes with the change. There is nothing in the change a unit test could assert.
Manual (human) testing
Open-Flight-Monitor-3.stepfrom the enclosure repo (both the 2026-09-15 release and the PR Dev analysis tools #10 revision), resolved the assembly transforms, and took every hole and body extent in one frame. Placed the parts the CAD does not contain (Pi 5, X1202, SEN-14262, Display 2) from their own drawings and Geekworm's X1202 interface photo. Computed straight-line and right-angle routed lengths for each run in the new table; the ones that matter reproduce the field report (display ribbon ~140 mm routed, so 200 mm is right and the ~100 mm box cable is not).Shell-x1202.stlfiles (DC-jack, USB-C and the PR Dev analysis tools #10 v1 shell) with a binary-STL ring probe and rasterised the rear recess wall to PNG to see the cutout shapes: two Ø12.5 mm round holes and a ~16 × 13 mm keystone opening with Ø4 screw holes 27 mm apart. This is what the button-row statement and the DC-jack rows rest on./en/ProductDetaillinks and the old firmware string with grep; read the rendered sections back.Not in this PR
Pricing the v3 insert and screw set (short 4 mm inserts, M3 × 10 case screws, a 90 mm-reach ball-end hex key) is a separate pass once openflight-enclosure#4 settles the insert family; the Cost Summary carries the v2 $35 allowance until then. The Ethernet opening in the v3 shell is a ~16 × 13 mm flanged keystone cutout, so the round Adafruit 4130 coupler in the Mouser project does not fit it as drawn; that is raised in openflight-enclosure#4, and Adafruit 909 looks like the matching part.
Checklist
uv run pytest tests/ -v) — in CI on this PRuv run pylint src/openflight/ --fail-under=9) — in CI on this PRuv run ruff check src/openflight/) — in CI on this PRcd ui && npm run build) — in CI on this PRcd ui && npm run lint) — in CI on this PR🤖 Generated with Claude Code