SignalSlinger v2.0.6

SignalSlinger 2.0.6

SignalSlinger 2.0.6 improves manual-event continuity, button behavior and serial reliability. Packages are available for HW 3.4 and HW 3.5. Use SerialSlinger 2.0.21 for the accompanying clone-template, running-event read and log-viewer fixes.

User-visible changes

• Manually started events retain their running state and transmission timing across sleep and authorized button wake. Waking the unit no longer replaces a manual run with an expired saved schedule.
• An expired, invalid or unset schedule no longer limits a newly started manual run to an old event duration. The run continues until canceled, aligned to the clock when valid and to the manual start when the clock is unset.
• A long hold while asleep wakes the unit. Once awake with LEDs active, a long hold during an ordinary active timed event cancels the current day, advances to the next scheduled day if present, and sleeps. A hold before a future event sleeps with the schedule armed.
• Long holds during temporary carrier or Morse demonstrations cancel the temporary activity and return to the schedule without canceling the current day. A temporary test expiring, or an event starting while the button remains held, cannot change that hold into an unintended day cancellation.
• Three presses clear temporary activity before a future event, cancel the current day during an active timed event, and stop an indefinite manual run.
• Normally completed manual events report Event completed instead of misleading configuration/interruption errors. Genuine interruptions remain distinguishable.
• The fast green low-battery indication now requires a low internal battery and external voltage below 6.0 V, independently of charging state.

Stability and reliability

• Starting an indefinite manual run without a valid clock now marks its immediate transmit phase started before enabling timer processing, preventing an interrupt from replacing that phase with the fox's scheduled offset.

• EEPROM readiness checks before reads and between multi-byte writes let serial reception and timer interrupts continue during persistence operations. Reproductions that previously caused serial overruns and roughly 11 ms timer-service gaps passed with no errors and approximately 2 ms service intervals after the fix.

• Corrupted serial commands are discarded through their line terminator rather than executing a truncated setting; bounded receive-error counters aid diagnosis.

• Automated hardware support exercises the ordinary button detector and scheduler, captures bounded timer/state traces, and reports authorized button-wake snapshots. Optional latency instrumentation is excluded from normal release builds.

• Host checks cover EEPROM representations, interrupt-state preservation, simulated power-cut recovery, damaged serial input, button timing boundaries, manual/scheduled behavior, thermal protection and ADC/battery behavior. EEPROM layout, checksums and journal commit ordering remain compatible.

Hardware validation scope

The preceding development build passed all 24 automated HW 3.5 behavior cases and 21 continuous-traffic captures, including actual timed sleep/wake cycles, with zero receive errors in the final verification runs. The initial test-runner startup/wake synchronization error was corrected and the complete suite rerun. Both board revisions build without warnings. Release-image programming and readback evidence is recorded separately in the release checklist.

Physical button wake/contact bounce, external RF/optical/current measurements, actual supply-interruption recovery, physical HW 3.4 programming and full hardware rollback have not been established by those automated checks. These coverage limits are retained explicitly.

Release files

• SignalSlinger-Update-v2.0.6-HW-3.4.hex
• SignalSlinger-v2.0.6-HW-3.4-Release-Files.zip
• SignalSlinger-Update-v2.0.6-HW-3.5.hex
• SignalSlinger-v2.0.6-HW-3.5-Release-Files.zip

Full changelog

Compare v2.0.5...v2.0.6