From 056ee0bdad247316219dd2420567faac8a737f29 Mon Sep 17 00:00:00 2001 From: Cyd Date: Tue, 11 Aug 2026 15:23:42 -0500 Subject: [PATCH] The per-packet trace goes behind RP412CAMLOG Playback is confirmed good - Cyd on the replay: "it looks as good as the Live cam view" - so the scaffolding that got it there can come down. DispatchPacket's line per packet earned its keep: one of them identified the spool's own header being parsed as packet one, which was the whole crash. But a station in a pod bay has no business writing two dozen log lines at the start of every replay, and the pods are where this is headed. Gated on RP412CAMLOG, kept rather than deleted, because the next thing to go wrong in this path will want it back. Co-Authored-By: Claude Opus 5 (1M context) --- RP_L4/RPL4PB.cpp | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/RP_L4/RPL4PB.cpp b/RP_L4/RPL4PB.cpp index f275dc1..3684038 100644 --- a/RP_L4/RPL4PB.cpp +++ b/RP_L4/RPL4PB.cpp @@ -437,6 +437,13 @@ void // release build, so a missing interest manager would be a call through // nothing rather than a complaint. // + // + // Behind RP412CAMLOG now that playback works. It earned its place - + // one line of it identified the header being parsed as packet one - but + // a station in a pod bay should not be writing a log line per packet + // for the first two dozen packets of every replay. + // + if (RPCameraLog()) { static int said = 0;