ew8bakandClaude Sonnet 4.6 055873a43a Fix IQ data flow: send HP Run=1 before DDC/DUC Specific packets
The emulator (and real hardware) creates ddc_specific_thread (port 1025),
duc_specific_thread (port 1026), and rx_thread[0..3] (ports 1035+) only
after receiving HP Run=1. Previously ConfigureDDCs and SendDUCSpecific
were sent before SetRunAndFreq(True), so both packets arrived at closed
ports and were silently dropped — ddcenable remained -1, rx_thread slept
forever, no IQ data ever arrived, and the 5-second timeout fired Run=0.

Fix: reorder DoConnectDevice to send Run=1 first, then DDC/DUC Specific.
Also add keepalive resend of the cached DDC Specific packet every 500 ms
for the first 5 seconds after start, to handle thread-startup races on
real hardware over the network.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-28 13:31:39 +03:00
2026-03-26 22:50:55 +03:00
2026-03-09 18:48:24 +03:00
2026-04-22 22:09:42 +03:00
2026-03-09 18:48:24 +03:00
2026-04-25 14:50:52 +03:00
2026-04-25 14:50:52 +03:00
2026-03-05 16:19:26 +03:00
2026-03-09 18:48:24 +03:00
2026-03-09 18:48:24 +03:00
2026-03-05 16:19:26 +03:00
2026-03-05 16:19:26 +03:00
2026-03-05 16:19:26 +03:00
2026-03-05 16:19:26 +03:00
2026-03-05 16:19:26 +03:00
2026-03-05 16:19:26 +03:00
2026-04-25 14:50:52 +03:00
2026-04-22 22:09:42 +03:00
2026-04-22 22:09:42 +03:00
2026-03-08 22:34:18 +03:00
2026-03-05 16:19:26 +03:00
2026-03-05 16:19:26 +03:00
S
Description
No description provided
Readme GPL-2.0
12 MiB
Languages
Pascal 96.4%
Python 2.9%
Shell 0.6%