Skip to content

Byte Blaster v1.1.25

Pre-release
Pre-release

Choose a tag to compare

View all tags
@parkerg16 parkerg16 released this 01 Oct 17:14
· 11 commits to main since this release
v1.1.25
8ce96fe

Byte Blaster v1.1.25 — Prerelease

This release brings the optimizer reference, measured wheel speeds and motor commands into one launch comparison so a missed spin-up deadline can be investigated. It does not add a startup boost or claim to fix the observed 2,000 RPM overshoot.

Launch comparison and recording

  • Simulation & Graphs now overlays optimizer RPM, the actual firmware reference and both measured wheel speeds. New calculator exports retain the dense simulation waveform and model inputs; older JSONs use their 16 knots.
  • The board records the latest 320 ms launch at 2 ms intervals in the production motor service. Recording includes requested and applied commands, controller ceilings, feedforward, acceleration compensation, voltage, telemetry age, limiter flags and solenoid state.
  • A capture includes an immutable snapshot of its duration, knots, target, gains and calibrated feedforward. Read and download it while idle before the next launch overwrites it.
  • Findings distinguish configuration mismatch, firmware command limiting and lag after the requested command reaches the applied output. They do not claim to measure phase voltage/current or uniquely distinguish ESC limiting from motor/model error.
  • Rise/peak analysis excludes stale RPM measurements and samples at/after the first recorded solenoid pulse. Separate 90% and 95% timing avoids confusing measured rise with firing-ready time.

Startup and defaults workflow

  • Diagnostic target selection now includes 2,000 and 5,000 RPM with cold and already-spinning baselines. Use these to investigate startup overshoot; measurement does not automatically apply its proposed gains.
  • Board tuning can be exported as a defaults candidate with actual readback, gain/curve/feedforward values and provenance. No factory defaults were replaced.
  • Calculator cold-start exports now begin at zero RPM; the previous approximately 6 RPM origin was borrowed from the first integration timestep. Startup assumptions are included explicitly: ideal torque per amp, assumed handoff time, and no AM32 startup or winding-inductance simulation.
  • The calculator is deployed alongside the configurator at https://parkerg16.github.io/Byte-Blaster/brushless_motor_thermal_calculator.html.

Hardware checks

  1. Back up your profile, flash only the RP2040 UF2, refresh the website and confirm both show 1.1.25. Keep the current ESC firmware and tuning for comparison.
  2. With no darts, confirm normal startup, rev and release. Upload the 125 ms curve through the existing burn control and load the same JSON into Launch comparison separately.
  3. Save five cold no-shot launches at the usual preset. Read and download each last-launch capture while idle, before the next run. Confirm recorded duration/knots match the uploaded curve; record displayed timing separately from 90%/95% RPM rise.
  4. Compare a 150 ms reference with the same normalized knots, preset, gains and similar battery voltage. Inspect requested/applied command and limiting flags where RPM falls behind.
  5. Save three 2,000 RPM cold measurements and three already-spinning measurements. Compare motor peaks and command 48 during overspeed; do not apply diagnostic gains during this comparison.
  6. Restore the desired curve and check single shots in HVZ, other presets/modes and a short burst. Verify firing gates, dart counting and rev release. Check USB reconnect and an intentional comparison-duration mismatch.
  7. Export board tuning for defaults and retain the original curve JSON, comparison downloads and tuning report for review.

Detailed expectations and evidence to return: hardware checklist.

Validation and assets

  • All 46 strict test suites pass, including native capture/serialization and actual configurator parsing/rendering/connection tests.
  • RP2040 compilation passes for rp2040:rp2040:waveshare_rp2040_zero. Physical timing and UI operation still require the hardware checks above.
  • Byte_Blaster_RP2040_v1.1.25.uf2 / .bin: new RP2040 firmware.
  • Bundled AM32 2.21 .hex / .bin: unchanged ESC firmware.
  • manifest.json: asset hashes, sizes, source commit and prerelease channel.
Assets 7
Loading