Skip to content

2026‐05

Jump to bottom
Vector edited this page May 29, 2026 · 8 revisions

May 1, 2026

Spearhead Call — Recording

Attendees: alperenag, errrks.eth, zeynepb5793, thomasg, kbmollysuh

  • STORK Build / Upcoming Ankara Test Campaign

    • Alperen had stock/order problems during the week, but replacement parts are now in shipping. Expected arrival: tomorrow or worst case Monday, due to a Turkish national holiday.
    • Thomas is coming to Ankara the following week. Goal is to finish as much of the STORK build as possible before he arrives so the visit can focus on test flights if weather allows.
    • Zeynep is planning to come to Ankara Thursday or Friday next week to help finish the build.
    • Alperen has started gluing the exterior skeleton/fuselage together and showed the 3D-printed hatch/locking mechanism. He may reuse some design ideas for Spearhead.
    • Battery and charger are ordered. Alperen also has a 750 W car-battery AC inverter; charger is ~700 W, so field charging may be possible in ~15 minutes for longer test campaigns.
    • The team found the exact SpeedyBee flight controller used by the original design in Turkey, which should reduce integration work by allowing use of the same wiring/connectors and ArduPilot configuration.

  • Software-in-the-Loop Simulation (Zeynep)

    • Zeynep is working on ArduPilot software-in-the-loop simulation for QuadPlane so the team can get experience with modes and transition behavior before flying real aircraft.
    • She has downloaded the required software and plans to get it working over the weekend, then share updates on the forum.
    • Initial simulation will use STORK dimensions/weight and estimated inertias/parameters. It will not be a perfect physical model, but should be good enough to learn flight modes and workflow.
    • Longer-term idea: document or automate the local setup process so other contributors can install the SITL environment more easily from instructions/scripts in GitHub.

  • Spearhead Wing Redesign / Manufacturing

    • Alperen had a wing design ready, but found a lighter/stronger approach for flight loads and discarded the prior design. He is now redesigning the wings and attachment mechanism.
    • No major design blocker remains; he expects to make more progress over the weekend.
    • Manufacturing blocker: local laser-cutting vendors are not reliably available. One shop near Alperen has not responded; another is busy with production work and asked him to call back in three days.
    • The required spar/rib-slot part is ~1.45 m long and ideally one piece, requiring a ~1.6 m cutting machine. This makes shipping/carrying parts difficult and rules out many vendors.
    • Thomas suggested SendCutSend if parts can fit in luggage, and also discussed Shaper Origin-style handheld CNC routing as a possible alternative to a large CNC/laser table.
    • Alperen is investigating buying an industrial laser cutter (~$3,000) capable of cutting 4 mm beech plywood and 5 mm balsa. If purchased, it would primarily support Spearhead/prototype wood cutting and would require space in his shed.

  • Engine Starter / Generator Possibility

    • Alperen found a Pilot RC auto-starter product in China for Stinger/DLE-style engines, but has not received a reply from the company.
    • KBM searched Chinese sites and believes the specific Pilot RC starter may no longer be offered; these products appear more like DIY/small-batch items than mass-produced parts. Searching for DLE engine starters may produce more options.
    • Alperen likes the starter concept because it is lightweight and straightforward, and could potentially be combined with a generator.
    • Concept discussed: replace/control the starter motor electronics with a VESC-like controller that can feed power back to the battery as a generator.
    • Reference engine found by Alperen: DLE 35 cc with starter-generator and water cooling, but total engine is ~5.5 kg; starter-generator system alone is ~2 kg and water cooling another ~2 kg. Target would be closer to ~1 kg for a usable Spearhead system.

  • Motor / Propeller / ESC Procurement

    • Alperen contacted Mad Motor in Poland for motor, propeller, and ESC components. They are out of stock now, with restock/delivery expected in either two weeks or one month depending on Chinese factory import cycle.
    • Alperen asked whether they can provide an ATR movement certificate for EU–Turkey customs. If they can, import tax should be zero. They will respond Monday.

  • Here 4 CAN-to-PWM Validation

    • Zeynep drafted/reviewed a grant idea to test a Here 4 connected to a flight controller over CAN, then outputting PWM to a servo through the breakout board.
    • Estimated effort discussed: ~5–6 hours; rough bounty amount joked/discussed around $300–350.
    • Thomas is interested in taking the bounty after his trip if still open, and can bring a Here 4 to Ankara.
    • Alperen proposed testing during Thomas's visit. If it works, the Ankara team can buy/keep the unit; if it does not, Thomas may be able to return it.
    • Decision: hold the grant for now and test with Thomas in Ankara instead.

  • Upcoming Coordination

    • Alperen wants individual calls with Erick and Zeynep about upcoming month streams and possible work packages. He will DM them.

  • Open Items

    • Alperen: track STORK part deliveries and identify any missing parts early enough to reorder.
    • Zeynep: come to Ankara Thursday/Friday next week if available to help finish STORK build.
    • Alperen/Zeynep/Thomas: prioritize STORK build completion before Thomas's arrival so Ankara time can focus on test flights.
    • Zeynep: get QuadPlane SITL running and post updates/instructions on the forum.
    • Alperen: continue Spearhead wing and attachment redesign.
    • Alperen: follow up with laser-cutting vendors and evaluate laser cutter purchase / handheld CNC alternatives.
    • KBM: continue checking Chinese sources for lightweight DLE/Stinger starter options.
    • Alperen: follow up with Mad Motor on ATR certificate and delivery timing.
    • Thomas: bring Here 4 to Ankara for CAN-to-PWM validation if practical.
    • Alperen: DM Erick and Zeynep to schedule individual stream/work-package calls.

May 4, 2026

Spearhead Call — Recording

Attendees: alperenag, errrks.eth, zeynepb5793, thomasg, kbmollysuh, far1no

  • STORC / Ankara Build Preparation

    • Alperen reported that build parts are effectively gathered, with final RC hobby shop items purchased.
    • He visited a laser cutter vendor and found a machine model that can be customized to a 1.5 m × 60 cm bed, large enough to cut wing spars/ribs in-house.
    • Alperen still had limited weekend design progress, but the material/tooling situation improved.

  • SITL / FlightGear Simulation

    • Zeynep worked on ArduPilot software-in-the-loop simulation for STORC and Spearhead.
    • She got SITL working on Mac after macOS/Tahoe 26-related issues.
    • She is working on FlightGear integration so pilots can visualize the aircraft instead of relying only on terminal/QGroundControl views.
    • Windows and Linux laptop environments remain fallback options. Goal is to have the simulation ready before the Ankara work session next week.

  • Spearhead Electrical Layout

    • Alperen and Erick discussed the electrical layout on the prior Friday.
    • Erick is collecting power, wiring, equipment, location, MTOW, cruise speed, mission time, and performance requirements.
    • Prototype 1 direction is to use off-the-shelf components and avoid custom PCBs where possible.
    • Likely architecture includes Pixhawk 6C, breakout board(s), direct wiring to ESCs/flight controller, and minimal PCB use.
    • Battery breakout remains the main area where a PCB may be needed.

  • IC Engine Starter / Generator Concept

    • Alperen contacted the electric starter vendor. The unit is not in stock, but can be prepared in roughly 30 days after order.
    • The vendor said the starter system cannot be used as a generator, but did not explain whether the limitation is mechanical, electrical, ESC-related, or due to disengagement after starting.
    • Engine target remains 35–55 cc.
    • Team may still order one after engine selection and examine whether it can be strengthened or modified.

  • Ankara Test Sites

    • Alperen discussed test sites around Ankara for STORC and Spearhead.
    • A small RC airfield is under construction and should be available later.
    • In the meantime, an informal open field near a village outside Ankara is used for RC testing. It is not fully clear/legal without permission, but in practice appears tolerated. Alperen received the location.

  • Open Items

    • Zeynep: finish FlightGear/SITL environment before Ankara, or fall back to Windows/Linux.
    • Erick: produce first-pass Spearhead electrical requirements/layout package.
    • Alperen/team: decide whether to order starter after engine selection.
    • Alperen: ask vendor for the specific reason the starter cannot be used as a generator.
    • Team: confirm permission/risk posture for the Ankara test site before flight testing.

May 11, 2026

Spearhead Call — Recording

Attendees: alperenag, errrks.eth, zeynepb5793

Update: additional VTT context from the same call was added after the initial notes.

  • STORK Build / Electronics Integration

    • STORK structure was mostly complete. Remaining assembly items were wing attachment after motor-cable bullet connectors, ESC soldering, flight-controller wiring, and related electronics work.
    • The call focused on getting the electronics safe enough to finish: solder paste versus flux, large battery wires to pads, through-hole PWM pins, ESC signal/BEC wiring, capacitors, and field charging.
    • Erick explained solder paste is actual solder, while flux helps solder wet/flow. Extra flux can still help, especially on large pads. Flux is not conductive in normal use, but excess should be cleaned and it also burns off during heating.
    • For high-current wiring, Erick recommended staying close to battery cable gauge. Dropping from 10 AWG to 12 AWG could cause heat; using 8 AWG and carefully shaping/reducing strands at the pad may be acceptable but is not ideal.
    • Large pads/heavy wires likely need more heat transfer than a fine soldering tip can provide; a chisel tip and practice/tutorial review were recommended.
    • Alperen and Zeynep planned to add pin headers for PWM connections. Erick recommended normal through-hole technique: insert pin, heat pad and pin together, then feed solder so it wicks into the joint.
    • Loose headers give builders the option to solder wires directly or from underneath in tight spaces; for STORK, they planned to solder the supplied headers and use connectors.

  • ESC / Flight Controller Questions

    • The Velox V50 ESC / SpeedyBee flight-controller wiring remained partially uncertain. The specific uncertainty was whether the ESC red/BEC/VX wiring should be connected.
    • Zeynep flagged SpeedyBee guidance saying not to connect ESC BEC output to the VX pad / middle red wire; Erick planned to compare the STORK docs, ESC docs, and flight-controller docs before answering.
    • ESC rating is 50 A continuous / 55 A peak. Hover estimates suggest limited margin for hover-heavy early testing; main concern is heat rather than immediate failure.
    • The ESC package included a capacitor. Erick advised that it likely belongs across ESC power input with correct polarity and should help voltage stability, especially with longer power leads.

  • Field Charging

    • Alperen evaluated charging STORK batteries from a car.
    • The charger supports AC, DC, and USB-C input. USB-C is limited to ~65 W; AC charging through Alperen's clamp-style inverter is ~200 W; DC input can be higher, but at 12 V practical input power is closer to ~360 W than the advertised 700 W.
    • Direct DC input from a running car battery could work electrically, but the battery's 1C charge limit means very fast charging is unsafe.
    • Using the existing inverter/AC charger path may be good enough. Buying another battery may be cleaner than trying to push field charge rate.

  • Documentation Process Note

    • The team discussed Quiver documentation process. Manufacturing guide should be treated as the more important live assembly reference, with the structural guide synced from it periodically.

  • Open Items

    • Erick: send drone soldering tutorial to Alperen/Zeynep.
    • Erick: review Velox V50 ESC and flight-controller docs to confirm PWM/BEC/VX/red-wire wiring, then give Alperen/Zeynep a clear answer.
    • Alperen/Zeynep: acquire/check solder flux, suitable soldering tips, and 10 AWG wire if possible.
    • Alperen: continue manufacturing-guide PR and fix both bolt issues Thomas flagged.
    • Team: when changing parts/designs, update the manufacturing guide via PR or notify Alperen.
    • Erick: inspect busbar fit/manufacturing issue after the call.
    • Zeynep: prepare simulator practice documentation for Erick once time allows.

May 18, 2026

Spearhead Call — Recording

Attendees: alperenag, zeynepb5793, errrks.eth, thomasg, kbmollysuh

  • STORK Build / Flight Recap

    • Alperen recapped an intense STORK build/test week in Ankara. The team completed the aircraft, worked through a major electrical failure, and achieved hover, transition, RTL-assisted recovery, and a successful ~4.5 minute flight.
    • The first hover looked good overall. Thomas saw some yaw oscillation. Landing was hard because motors stopped around 30–40 cm above ground. Cause is unclear: possible RC disarm command versus overheated ESC. Zeynep wants logs.
    • A second flight included transition attempt and back-transition near the end of the road/runway. It ended in another hard landing, possibly due to low battery or ESC overheating.
    • The left wing appeared pulled but spar engagement likely stayed intact. The nose cracked because the battery pushed into the nose wall; CA glue field repair worked.
    • The third flight was successful. Thomas transitioned quickly, used RTL when visually uncertain, and reported that ArduPilot RTL was excellent. Flight controls felt somewhat conservative/muted, likely helpful for first flights but worth tuning later.

  • Electrical Failure / Recovery Architecture

    • During battery cable extension, Alperen soldered an XT90 connector with reversed polarity, shorting the system and frying the SpeedyBee flight-controller/PDB stack.
    • The team recovered using a Pixhawk 6C from the testbed, Pixhawk power module, UBEC for servo power, MatX hex PDB, salvaged XT60 cables, and a large amount of extra wiring.
    • The result was messy, heavy, and EMI-unfriendly, but it flew and helped bring CG forward.
    • The team used a better F9P GPS/antenna after the original GPS setup stopped working. Zeynep noted the original GPS may have been damaged by the electrical event or static/electrical abnormality.

  • Flight-Test Lessons

    • Telemetry radio dropped out frequently, so Thomas flew almost entirely visually.
    • Zeynep strongly recommended FPV or at least an onboard video feed to make future flights safer/easier.
    • Post-flight, the PETG-CF pusher motor adapter heat-deformed, tilting the pusher motor downward roughly 5–8 degrees.
    • The pusher motor had made scratching noises before flight. Alperen plans to reprint the adapter in PA6-CF and replace/check the motor.
    • STORK is now seen as an important Spearhead learning platform. Alperen wants to fly it often, possibly weekly or twice a week, with Zeynep reviewing logs.

  • Zeynep Fabrication Update

    • Zeynep ordered a Bambu Lab X2D printer and a soldering station after the Ankara build week.
    • She wants to learn more hands-on fabrication and use the equipment for Arrow work.

  • Spearhead Aero Database

    • Alperen used Codex to make a custom adaptive-sampling-style aerodynamic database tool.
    • StarCCM+ GPU solving reduced analysis time from ~30 minutes to ~3 minutes each.
    • He had already produced ~350 analyses and expects to hand Zeynep improved data by the end of the week after comparing against VDM cases and deriving a prop correction factor.

  • Spearhead Electrical Layout / Here 4

    • Erick's Spearhead electrical-layout/work-package material is mostly ready but blocked on component choices: servo types/torques, telemetry unit, RC/control scheme, and similar details.
    • A short working session was scheduled for the next day, one hour before the Caribou meeting / around 5 PM for Zeynep.
    • The Here 4 external cable set apparently does not expose all PWM outputs, so using it may require opening the housing and connecting to internal JST/breakout connectors.
    • Erick planned to review docs/disassembly video; Alperen may carefully open it with plastic pry tools/guitar pick if needed.
    • Thomas is interested in building a STORK using Here 4 as both GPS and flight controller depending on these experiments.
    • KBM offered that if Spearhead needs a special/custom PDB, the team can make one.

  • Open Items

    • Alperen: send latest STORK flight log to Zeynep.
    • Zeynep: analyze uploaded STORK logs, especially possible ESC overheating, low-voltage events, and hard-landing causes.
    • Alperen: reprint pusher motor adapter in PA6-CF.
    • Alperen: replace or inspect pusher motor due scratching noise and post-flight heat/mount issue.
    • Team: add FPV/onboard video and improve telemetry reliability for future STORK flights.
    • Alperen: finish GPU-based aero database runs.
    • Alperen: compare GPU results against VDM cases and derive propeller correction factor.
    • Zeynep: prepare/update simulation model to consume new aero database.
    • Erick/team: answer Spearhead electrical-layout blockers: servo type/torque, telemetry unit, and RC/control scheme.
    • Erick: inspect Here 4 documentation/disassembly video for internal PWM/JST connector access.
    • Alperen: carefully open Here 4 housing only if needed and preferably with non-marring tools.

May 20, 2026

Spearhead Call — Recording

Attendees: alperenag, 21stCenturyAlex, errrks.eth, zeynepb5793

  • STORK / Proto-Spearhead Lessons

    • STORK was a purchased Flytoury-style design, but Arrow made substantial electrical-layout customizations before flying it.
    • The aircraft flew successfully and survived, so the team can keep using it for ArduPlane configuration experiments and Spearhead transition learning.
    • The vendor supplied an ArduPlane configuration file. The team flashed it rather than building the autopilot setup from scratch, but Alperen noted the experience still helped Zeynep understand ArduPlane settings/parameters that can inform Spearhead.
    • Test site is near Ankara, about 45 minutes from Alperen, and is commonly used by RC/model-plane pilots.

  • Quiver Hub / Telemetry Timing

    • Alex raised Quiver Hub-style telemetry for Spearhead.
    • Alperen agreed Spearhead will likely need something like it eventually, but not yet: gasoline engine choice and telemetry architecture are still undecided, and the platform needs to mature first.

  • Pusher Propulsion Path — Electric First vs Gasoline First

    • After STORK, Thomas and Alperen discussed using an electric pusher motor before the gasoline engine.
    • Rationale: transition behavior is still not well understood, and adding a gasoline engine immediately may combine two hard problems — VTOL transition and IC-engine integration.
    • Direction is not locked, but electric-first is a serious risk-reduction option: learn VTOL/transition first, then add gasoline complexity.

  • Gasoline Engine / Prop Data Problem

    • Manufacturer thrust/performance data for the target gasoline engine/prop class is weak.
    • Static test-bench data would not capture dynamic in-flight behavior well enough.
    • Zeynep suggested checking whether Ankara RC-plane contacts have flown the same engine and can share data.
    • Alperen already asked Selçuk from THK; Selçuk has not used the exact ~35 cc class engine but can ask around once Arrow selects the engine model.
    • Alternate path: buy a standard compatible ~20×10 propeller, 3D scan it, and run CFD. Alperen believes the current GPU workflow can make this accurate enough for design decisions.
    • Alperen floated a trailer/highway dynamic prop test as a cheap wind-tunnel substitute; Zeynep pushed back. Treat this as unsafe / not an action item.

  • Electrical Architecture Overview

    • Erick walked through a Spearhead electrical decision document. It is partly AI-assisted and should be treated as a working decision record until reviewed.
    • Current/general assumptions: smart battery with high-voltage kill switch; high-voltage power bus feeding ESCs; separate avionics low-voltage kill path; separate regulators for main-wing servos, tail servos, and later payloads.
    • High-voltage kill likely uses a contactor; low-voltage kill could use a relay or similar.
    • CAN is expected for ESCs and Here 4 / CAN-to-PWM conversion; additional telemetry likely UART; RC receiver likely SBUS.
    • No additional standalone external magnetometer appears necessary beyond flight controller/GPS/Here 4 sources.
    • Pusher-engine control remains undecided; gasoline throttle/choke servos may be needed later.

  • GPS / Here 4 / CAN-to-PWM

    • Spearhead likely needs at least one Here 4 in the tail for CAN-to-PWM conversion and possibly GPS.
    • Likely architecture: primary RTK GPS in the cockpit/nose, secondary Here 4 in the tail for GPS + CAN-to-PWM.
    • GPS-for-yaw would require two separated RTK-capable GPS antennas.
    • Nose GPS option remains open: Here 4, F9P, F9P Neo, or available/salvaged F9P hardware.

  • PCB vs Wiring / Busbar Layout

    • Alperen prefers avoiding custom PCBs for PT1 if design/order/manufacturing would cost too much time.
    • Erick is increasingly concerned that copying Feather/PT-style wiring into Spearhead will be cramped, heavy, and messy, with many cables crossing busbars.
    • A simple PCB may be cleaner for distributing ESC power/signals, pusher control signals, and flight-controller power while keeping FC ports available.
    • Alperen found a Turkish PCB manufacturer that may be faster than ordering from China and will send Erick the link.
    • Decision is not final: a simple PT1 PCB is acceptable if Erick concludes it improves harnessing/weight/timeline versus discrete wiring/busbars.

  • Battery Sizing / Smart Battery Tradeoff

    • Erick initially leaned toward a smart battery similar to Quiver/Caribou assumptions.
    • Alperen found a large weight penalty: a 12S 16Ah dumb pack around 3.8 kg versus smart equivalent around 4.8 kg, roughly +1 kg.
    • Alperen is not eager to take the smart-battery penalty for the end product. Feather BMS hardware is a possible temporary option but known-problematic.
    • Battery bay is currently sized around 12S 16Ah. Alperen will rerun mission energy numbers and publish a short note.
    • For PT1, weight is less strict; extra battery can go in the empty fuel-tank area if needed.

  • ESC / Wiring / Motor Mounts

    • Erick needs cable-routing lengths and ESC placement to calculate voltage drop and decide whether additional capacitors are needed.
    • Alperen estimated cable run length around 1.4 m, with rear runs possibly 20–30 cm longer.
    • ESC power cables will need extension. Phase wires can likely remain existing short ESC/motor leads if ESCs are mounted near motors.
    • Cable weight may exceed the previous 1 kg budget, strengthening the case for simpler distribution hardware/PCB.
    • Alperen’s current motor/ESC mount idea: PA6-CF 3D-printed mounts on square tubes with integrated ESC slots, similar in concept to Quiver/T-Motor mounts.
    • 3D printing is preferred initially because tilt angle may need adjustment; switch to aluminum if weight/heat/structure demand it.
    • Motor shaft / prop compatibility should still be verified even though the props were manufacturer-recommended.

  • Servo Torque / Regulators

    • Erick needs main-wing and tail servo torque/spec requirements because those drive voltage-regulator selection.
    • Alperen asked for about one day before answering confidently.

  • Here 4 Breakout-Board Test Plan

    • Alperen opened the Here 4 case, installed the external breakout-board cable/cap, and now has Here 4 + breakout board, servo, Pixhawk, voltage regulator, and multimeter ready.
    • Erick wants Alperen to first check continuity across the breakout-board positive rail and negative rail for the servo power pins.
    • Initial wiring: connect Here 4 to Pixhawk via CAN; use CAN 5 V to power Here 4 if reliable; connect one servo signal to the breakout board; power servo positive/negative rails from a regulator/UBEC.
    • If CAN-supplied 5 V is unreliable over the full tail distance, Spearhead may need a separate 5 V supply for the tail Here 4 and possibly shielded CAN cable.
    • Tail servos likely need a separate ~7.4–7.8 V regulator/UBEC from the Here 4’s 5 V supply.
    • Zeynep noted the current STORK/Pixhawk config will not send the needed output without parameter/config help; no firmware flashing should be needed if only enabling CAN output.
    • Zeynep will rewatch the Here 4 setup/programming video and help Alperen configure Pixhawk/CAN output.
    • The available Here 4 has blue tape / troubleshooting history. If the test fails, firmware/hardware state should be considered before rejecting the architecture.

  • Open Items

    • Alperen/Zeynep: keep using STORK for ArduPlane configuration experiments and Spearhead transition learning.
    • Alperen/Thomas/team: decide whether the next pusher integration should be electric-first or gasoline-first.
    • Alperen/team: choose target gasoline engine size/model before deeper telemetry/hub integration.
    • Alperen: ask Selçuk/THK and Ankara RC-plane contacts for real flight data once the candidate engine is selected.
    • Alperen: consider buying/scanning a compatible ~20×10 propeller and running CFD if manufacturer/community data is insufficient.
    • Alex/team: revisit Quiver Hub-style telemetry integration after engine/telemetry architecture matures.
    • Erick: share/review the Spearhead electrical decision document and separate AI-populated assumptions from confirmed choices.
    • Alperen: send Erick the Turkish PCB manufacturer link.
    • Erick: decide whether a simple PT1 PCB is worth it versus busbars/discrete wiring.
    • Alperen: rerun 12S 16Ah mission-energy/battery sizing numbers and publish a short note.
    • Erick: measure ESC/motor cable runs in Fusion, estimate voltage drop, and check ESC docs for capacitor requirements.
    • Alperen: provide confident main-wing and tail servo torque/spec requirements.
    • Alperen/Erick: verify motor shaft / recommended prop compatibility.
    • Alperen: test Here 4 breakout-board positive/negative rail continuity with a multimeter.
    • Alperen/Zeynep: connect Here 4 to Pixhawk over CAN and test CAN-to-PWM output with one servo.
    • Zeynep: rewatch Here 4 setup/programming video and help configure Pixhawk/CAN output.
    • Erick/Alperen: determine whether CAN-supplied 5 V is sufficient over actual tail cable length or whether separate 5 V tail supply/shielded cable is needed.
    • Team: treat the blue-taped Here 4’s unknown firmware/history as possible test-failure cause before rejecting the architecture.

May 29, 2026

Spearhead Call — Recording · HearHear transcript

Attendees: alperenag, errrks.eth, zeynepb5793, sleety.eth, kbmollysuh

  • STORK Test-Flight Status

    • Alperen planned STORK flights this week, but weather was windy/rainy.
    • Good weekend weather was expected, but the rear-left control surface stopped responding after transport from the field.
    • Alperen swapped cables and reprogrammed another PWM pin with no improvement.
    • Zeynep checked logs and did not see evidence the failure happened in flight; likely hardware/servo damage during transportation.
    • Servo replacement is mechanically easy, but Turkish holiday shipping delays mean likely Tuesday/Wednesday arrival before flights can resume.

  • STORK / Spearhead Airspeed Sensor Path

    • Zeynep asked whether STORK should get an airspeed sensor because Spearhead will need one.
    • Alperen agreed it would be useful practice, but the existing no-name pitot/airspeed sensor is unidentified.
    • Alperen will try image/AI identification before digging through old reimbursement receipts.
    • Nose packaging idea: use the camera hole for pitot tube + camera, remove/replace the F9P antenna there, and use a smaller GPS antenna.
    • Sensor protocol remains uncertain, but Zeynep expects Pixhawk/ArduPilot integration to be manageable if a suitable I2C/UART-style port is available.

  • Mission Planner on Mac

    • Alperen got Mission Planner working on Mac via an emulator-style setup, similar to Thomas.
    • Zeynep suggested documenting/uploading the setup somewhere, though it is not a custom build.

  • Spearhead Structural Design / Aero Database

    • Alperen is back on structural design; aero database work, laser-cutter work, and STORK slowed finalization.
    • Structural design is now his top priority, with a goal to finalize next week and then begin manufacturing parts slowly.
    • Zeynep requested control-input delta coefficient lookup-table data for the flight model: alpha, beta, and control deflection sweeps that can be added on top of the baseline aero database.
    • Starting point discussed: alpha/beta around -30° to +30° and control deflections such as ±5/10/15° or comparable increments.
    • Alperen will prioritize those runs, likely through another Latin-hypercube/adaptive sampling setup weighted around small alpha/beta cases.

  • Flight Dynamics / Stability Model

    • Zeynep has nearly finalized the model and stability analysis, but is revising code against Alperen's latest large design commit.
    • Expected output this weekend / Monday: Python aircraft model with trim and linearization routines, plus a preliminary-design stability analysis document.
    • If analysis finds red flags, Zeynep will flag them immediately so Alperen can still adjust the preliminary/structural design before freezing.

  • Electrical Layout

    • Erick had less progress than desired because Quiver took more time this week.
    • He expects to wrap electrical work packages/layout material next week.
    • For Monday, he committed to a v1 electrical layout/planning diagram with currently discussed connections.

  • Here 4 No Longer Favored for CAN-to-PWM Conversion

    • The team revisited the Here 4 CAN-to-PWM idea.
    • Concern: if Here 4 handles both secondary GPS and tail servo conversion, a Here 4 failure could remove tail control-surface outputs, not just GPS.
    • Because Here 4 / RTK GPS failures have been seen on Quiver, using Here 4 as a control-surface conversion point is now considered a significant single-point failure risk.
    • New preferred direction: use a dedicated CAN-to-PWM adapter board for tail servo conversion, and keep Here 4 only as secondary GPS if useful.
    • Erick agreed the adapter path looks reasonable and easier than flashing/configuring Here 4 as a converter.
    • Zeynep noted this is a normal ArduPilot fixed-wing pattern: configure servo outputs over CAN, then convert to PWM at the adapter.

  • Tail Electronics / Future PCB Idea

    • Alperen thinks the tail/horizontal section can house both a dedicated CAN-to-PWM converter and a Here 4.
    • Future concept: small tail PCB with Here 4 connector, CAN-to-PWM converter, voltage regulation, and servo outputs. The aircraft would provide high voltage and CAN; the tail module would provide local servo outputs.
    • Erick said this is plausible, treating the converter like a daughterboard/hat if pin pitch and connector layout are handled.

  • Open Items

    • Alperen: identify the no-name pitot/airspeed sensor, preferably via image/AI search before old receipts.
    • Alperen: source/order replacement rear-left STORK servo after the holiday delay; replace it and resume flight testing.
    • Alperen/Zeynep: evaluate STORK airspeed sensor integration and possible nose packaging changes.
    • Alperen: provide control-input delta coefficient lookup-table data for Zeynep's model, including alpha/beta and control deflection sweeps.
    • Zeynep: publish/upload FlightDynamicModel / flight mechanics analyzer v1 with trim and linearization routines plus preliminary stability analysis — target Monday, June 1.
    • Zeynep: flag stability/control red flags quickly so Alperen can adjust structural/preliminary design before freezing.
    • Erick: produce electrical layout planning v1, including dedicated CAN-to-PWM adapter instead of Here 4-as-converter — target Monday, June 1.
    • Erick: compare candidate CAN-to-PWM converter boards and recommend which one best fits Spearhead.
    • Alperen: continue/finalize structural design enough for Monday review/checkpoint.
    • Alperen: make the Project Spearhead task board public after the meeting.

Clone this wiki locally