stardance has been extended another month! the new deadline is october 31 :)

You are browsing as a guest. Sign up (or log in) to start making projects!

9h 56m 46s logged

DEVLOG #45

The setup recorded 5,165 raw frames in a short test, but the run still failed because its rejection log overflowed. I expanded that bounded log and moved slow startup hashing out of the packet-processing locks.

I also installed RX1’s new memory-diagnostic firmware and checked it for about 15 minutes. The old heap dip didn’t reappear, although that doesn’t prove its cause is fixed.

Wi-Fi is now the main headache. TX1’s access point restarted internally, and the receivers didn’t reliably reconnect. Restarting them helped temporarily, but the problem returned. I found a firmware path where an immediately failed reconnect schedules no further attempt. The corrected candidate is built and tested offline, with extra UART diagnostics to capture what happens during a real failure. The actual outage cause is still unproven.

Next: check the reconnect candidate on hardware, capture the failure, then retry the short recording and full baseline/peer comparison.

0
74

Comments 1

@Gerafftes

By the way, I work according to a schedule. The issues I’m currently dealing with were originally scheduled for the 14th. It’s now the 23rd, and I’ve already spent over 80 hours trying to complete the work that was supposed to be finished on the 14th.