v0.12.6 #10

2026-05-04T13:19:14-04:00

serversdown commented

2026-05-04 13:19:14 -04:00

v0.12.6 — 2026-05-01

Fixed

blastware_file.py — waveform frame classification — A5 frame classification for
waveform-only vs header-only frames now uses frame.record_type instead of frame index.
Only waveform frames (0x46) are written to the file body; metadata frames are skipped.
Fixes spurious data corruption from incorrectly classified frames.
s3_analyzer.py — A5/5A frame naming — Bulk waveform stream frames (SUB 5A response)
are now correctly labeled "A5" in analyzer output instead of being conflated with other
multi-frame responses (SUB A4, E5, etc.).
S3FrameParser — frame terminator detection — Corrected the bare ETX terminator
detection. Frame termination is now correctly identified by a standalone ETX=0x03 byte,
not by the DLE+ETX sequence (which is part of the payload when it appears within a frame).

v0.12.5 — 2026-04-21

Added

seismo_lab.py — Download tab — New fourth tab for live wire-byte capture during event
downloads. Captures both BW→device and device→S3 frames in real time, allowing inspection
of the 5A bulk stream chunk sequence and frame-by-frame analysis without needing a bridge
or MITM proxy. Files are saved with user-specified labels for easy tracking.

Changed

s3_bridge.py — raw captures always-on by default — --raw-bw and --raw-s3 now
default to "auto" instead of None. Every bridge session automatically generates
timestamped raw_bw_<ts>.bin and raw_s3_<ts>.bin files alongside the .bin/.log
session files. Pass --raw-bw "" (explicit empty string) to disable if needed.
gui_bridge.py — raw capture checkboxes pre-checked — Both "BW→S3 raw" and
"S3→BW raw" checkboxes start checked. Path fields are empty by default (bridge auto-names
the files). Unchecking a box passes --raw-bw "" to explicitly disable capture.
Bridge tab — TCP mode added — Serial/TCP radio toggle allows connection via cellular
modem (RV50/RV55) instead of direct RS-232. Supports multi-capture design (simultaneous
Bridge + Analyzer + Download sessions).
ach_server.py — TX capture added (raw_tx_<ts>.bin) — Every ACH inbound session
now saves both directions: raw_rx_<ts>.bin (device → us, S3 side, as before) and
raw_tx_<ts>.bin (us → device, BW side). Both files are usable in the Analyzer.
TX bytes are buffered in memory until startup handshake succeeds (same as RX), preventing
scanner probes from creating empty files.

## v0.12.6 — 2026-05-01 ### Fixed - **`blastware_file.py` — waveform frame classification** — A5 frame classification for waveform-only vs header-only frames now uses `frame.record_type` instead of frame index. Only waveform frames (0x46) are written to the file body; metadata frames are skipped. Fixes spurious data corruption from incorrectly classified frames. - **`s3_analyzer.py` — A5/5A frame naming** — Bulk waveform stream frames (SUB 5A response) are now correctly labeled "A5" in analyzer output instead of being conflated with other multi-frame responses (SUB A4, E5, etc.). - **`S3FrameParser` — frame terminator detection** — Corrected the bare ETX terminator detection. Frame termination is now correctly identified by a standalone `ETX=0x03` byte, not by the `DLE+ETX` sequence (which is part of the payload when it appears within a frame). --- ## v0.12.5 — 2026-04-21 ### Added - **`seismo_lab.py` — Download tab** — New fourth tab for live wire-byte capture during event downloads. Captures both BW→device and device→S3 frames in real time, allowing inspection of the 5A bulk stream chunk sequence and frame-by-frame analysis without needing a bridge or MITM proxy. Files are saved with user-specified labels for easy tracking. ### Changed - **`s3_bridge.py` — raw captures always-on by default** — `--raw-bw` and `--raw-s3` now default to `"auto"` instead of `None`. Every bridge session automatically generates timestamped `raw_bw_<ts>.bin` and `raw_s3_<ts>.bin` files alongside the `.bin`/`.log` session files. Pass `--raw-bw ""` (explicit empty string) to disable if needed. - **`gui_bridge.py` — raw capture checkboxes pre-checked** — Both "BW→S3 raw" and "S3→BW raw" checkboxes start checked. Path fields are empty by default (bridge auto-names the files). Unchecking a box passes `--raw-bw ""` to explicitly disable capture. - **`Bridge tab` — TCP mode added** — Serial/TCP radio toggle allows connection via cellular modem (RV50/RV55) instead of direct RS-232. Supports multi-capture design (simultaneous Bridge + Analyzer + Download sessions). - **`ach_server.py` — TX capture added (`raw_tx_<ts>.bin`)** — Every ACH inbound session now saves both directions: `raw_rx_<ts>.bin` (device → us, S3 side, as before) and `raw_tx_<ts>.bin` (us → device, BW side). Both files are usable in the Analyzer. TX bytes are buffered in memory until startup handshake succeeds (same as RX), preventing scanner probes from creating empty files.

serversdown added 43 commits 2026-05-04 13:19:14 -04:00

feat(logging): add detailed logging for anchor position in compliance config encoding/decoding 9b5cdfd857

fix(client): correct recording_mode anchor position in compliance config encoding b3dcfe7239

feat(protocol): enhance raw capture functionality and documentation updates 4331215e23

- Update `s3_bridge.py` to default raw capture file paths to "auto" for timestamped naming.
- Modify `gui_bridge.py` to pre-check raw capture options and streamline path handling.
- Extend `ach_server.py` to save both incoming and outgoing raw bytes for analysis.
- Revise `CHANGELOG.md` and `instantel_protocol_reference.md` to reflect changes in recording mode handling and compliance data encoding.

feat: first try at building waveform binary files. dfbc9f29c5

feat(protocol): update Blastware file format documentation and encoding details c47e3a3af0

feat(protocol): fully decode Blastware filename encoding and update related documentation 6dcca4da79

fix(server): add error logging for device event handling 8cb8b86192

fix(protocol): improve terminator frame detection in write_blastware_file. 3eeafd24aa

fix: rename .n00 to just blastware file (.n00 was false positive)

fix(protocol): include terminator in waveform stream downloads ec6362cb8e

fix(protocol): adjust waveform download to use full_waveform for accurate event streaming 84c87d0b57

fix(protocol): revert endpoint back to stop_after_metadata=True 39ebd4bdaa

fix(protocol): enable full_waveform for continuous mode. 5e2f3bf2a1

fix(protocol): adjust full_waveform setting for event downloads to end when it should. 9e7e0bce2a

fix(protocol): fetch additional chunk after metadata to ensure valid termination response 2a2031c3a9

fix(protocol): add record_time based chunk scaling for longer event record times aa2b02535b

fix(protocol): adjust extra_chunks calculation to use integer conversion of record_time bc9f16e503

fix(protocol): enhance extra chunk fetching logic to ensure footer detection ecd980d345

fix(protocol): update extra chunk fetching logic to stop at silence detection fa887b85d9

fix(protocol): refine extra chunk fetching logic for accurate termination response ab2c11e9a9

fix(protocol): update device_event_blastware_file to include extra chunk for accurate data retrieval f83fd880c0

fix: raise max_chunks to 128 for metadata-only 5A download 03540fdc00

For 2-second events at 1024 sps the "Project:" metadata frame appears
beyond chunk 32 (the old default cap), causing the safety limit to be
hit and ~34 KB of waveform data to be downloaded instead of stopping
at the metadata frame.  Raising max_chunks to 128 ensures
stop_after_metadata=True can locate the metadata frame for record
times up to ~4 seconds.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

fix(protocol): correct chunk counter formula for accurate data streaming 242666f358

feat(blastware_file): classify A5 frames, only write waveform frames to body 43c8158493

Add classify_frame() which categorises each A5 frame by content:
  terminator    — page_key == 0x0000
  probe_or_strt — contains b"STRT"
  metadata      — contains compliance-config ASCII markers
                  (Project:, Client:, Standard Recording Setup, …)
  waveform      — binary-heavy (< 20% printable ASCII), i.e. raw ADC data
  unknown       — fallback

Update write_blastware_file() body loop: frame 0 (probe) is still
always processed; frames 1+ are only included when classify_frame
returns "waveform".  Metadata frames (compliance config block with
Project:/Client:/etc.) and any stray STRT-bearing frames are skipped
with a warning/debug log.  Terminator frame handling is unchanged.

Adds temporary print() diagnostics so each frame's classification is
visible in the server log to aid debugging.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

fix(protocol): correct A5 frame classification and chunk counter formula 35c3f4f945

fix(blastware_file): remove seen_metadata flag and adjust frame processing logic 0415af19b4

fix(blastware_file): never skip A5 frames based on classification at fi>0 7976b544ed

Frame 0 is always the probe; frames 1+ are always data (waveform ADC
chunks, compliance config, compliance continuation).  Gating on
classify_frame() at fi>0 produces false positives: ADC binary data
can coincidentally contain b"STRT\xff\xfe", causing frames 1 and 5
to be silently dropped from the body (confirmed from live capture on
event key=01110000).  Remove all type-based filtering; include every
frame unconditionally with the standard index-based skip amounts.

fix(protocol): update chunk counter formula to use max(key4[2:4], 0x0400) for accurate data streaming 2f084ed105

fix(blastware_file, server): enhance logging and correct chunk handling for accurate data processing ae30a02898

fix(parser): correct S3 frame terminator — bare ETX, not DLE+ETX 9bbecea70f

parse_s3 had the S3 terminator logic inverted vs the real S3FrameParser
in framing.py. It was terminating on DLE+ETX and treating bare ETX as
payload, which caused every bare 0x03 to be swallowed — bundling multiple
real S3 frames into one giant body until a DLE+ETX sequence happened to
appear. Result: 583-byte POLL_RESPONSE 'frames' containing many real
frames concatenated, all showing BAD CHK.

Fix: mirror S3FrameParser exactly —
  - Bare ETX (0x03) = real frame terminator
  - DLE+ETX (0x10 0x03) = inner-frame literal data (A4/E5 sub-frames),
    appended to body and parsing continues

https://claude.ai/code/session_014NczSHUz9uTzCAf4cVASTJ

fix(blastware_file, server): implement logic to skip extra chunks after metadata for accurate file writing a7585cb5e0

fix(analyzer): name A5/5A frames; revert S3 checksum validation e1150b30aa

Add 0x5A (BULK_WAVEFORM_STREAM) and 0xA5 (BULK_WAVEFORM_RESPONSE) to
SUB_TABLE so they display with real names instead of UNKNOWN_5A/A5.

Revert S3 checksum validation to checksum_valid=None (the original
intentional behavior). Large S3 frames (A5 bulk waveform, E5 compliance
config) embed inner DLE+ETX sub-frame delimiters; the trailing 0x03 of
the last inner delimiter can land where the parser expects the SUM8
checksum byte, causing false BAD CHK on every valid A5 frame.
protocol.py _validate_frame documents and ignores exactly this issue.

https://claude.ai/code/session_014NczSHUz9uTzCAf4cVASTJ

Merge pull request 'seismo-lab2' (#7 ) from seismo-lab2 into seismo-lab 310fc5986c

Reviewed-on: #7

Add TCP MITM capture tab (TcpBridgePanel) 897ac8a3f3

New 'TCP Capture' tab in seismo_lab.py: listens on a configurable local
port for an incoming Blastware connection, transparently forwards all
traffic to the real seismograph device, and saves both directions to
raw_bw_<ts>.bin / raw_s3_<ts>.bin in the same format the Analyzer already
understands.  Session start wires up Analyzer live mode automatically via
the same on_bridge_started callback as the COM-port bridge.

https://claude.ai/code/session_014NczSHUz9uTzCAf4cVASTJ

Merge branch 'seismo-lab' of https://github.com/serversdwn/seismo-relay into seismo-lab 5cd5652560

Merge TCP mode into Bridge tab (Serial/TCP radio toggle) 6861d9ed97

Removes the separate 'TCP Capture' tab and folds TCP MITM capture directly
into the existing Bridge tab.  A Serial/TCP radio selector at the top swaps
the connection fields (COM ports vs. listen port + device host:port) while
keeping the same Start Bridge / Stop Bridge / Add Mark buttons, capture
checkboxes, log dir, and live log — identical UX for both modes.

https://claude.ai/code/session_014NczSHUz9uTzCAf4cVASTJ

Restore multi-capture Bridge design + TCP mode 9004241846

Brings back the protocol-exp BridgePanel design:
- Single bridge session stays up; New Capture / Stop Capture create
  labelled raw-file segments on demand (no files created at bridge start)
- Capture history listbox shows all segments; double-click reloads in Analyzer
- On capture complete: Analyzer auto-populates and runs analysis

TCP mode integrated into same tab (Serial/TCP radio toggle):
- Each incoming Blastware connection is automatically a capture segment
- Session appears in history list; Analyzer wires up live on connect
- Stop Capture disconnects current TCP session

https://claude.ai/code/session_014NczSHUz9uTzCAf4cVASTJ

Fix TCP capture: write files only when capture is active b9ab368934

Previously every Blastware connection auto-created files.
Now TCP mode works the same as serial mode:
- Start Bridge: proxy listens and forwards silently, no files written
- New Capture: opens raw_bw/raw_s3 files; pipe threads write to them
- Stop Capture: flushes and closes files, fires Analyzer callback
- No connection = no file; multiple captures per bridge session work correctly

https://claude.ai/code/session_014NczSHUz9uTzCAf4cVASTJ

Include capture label in TCP raw filename b14f31f3b0

Matches serial bridge naming: raw_bw_{ts}_{label}.bin / raw_s3_{ts}_{label}.bin

https://claude.ai/code/session_014NczSHUz9uTzCAf4cVASTJ

feat(seismo_lab): add Download tab that captures wire bytes during event download 625b0a4dfc

Adds a new CapturingTransport wrapper in minimateplus.transport that mirrors
every TX/RX byte to two raw .bin files using the same on-wire format as
bridges/ach_mitm.py, so the resulting captures are byte-for-byte compatible
with the existing Blastware MITM captures and load directly in the Analyzer.

A new "Download" tab in seismo_lab.py lets the user connect to a device over
TCP or serial and run connect / list-keys / download-events while the wrapper
saves raw_bw_<ts>.bin (our TX) and raw_s3_<ts>.bin (device TX) into a
seismo_dl_<ts>[_<label>]/ session directory. On completion, the panel hands
both files to the Analyzer and switches tabs, mirroring the UX of the
existing Bridge capture flow.

Manually Merged seismo lab persistent connection branch into the new direct download branch, creating a new branch called seismo-lab-new 738b39f3cb

Fix: Removed duplicates from merge botch. Stable version of seismo_lab.py 1ef55521b1

doc: update to v0.12.5 bb33ad3837

Doc: Update docs for 0.12.6 e15f1567ef

serversdown merged commit 4ab604eff1 into main

2026-05-04 13:22:56 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: serversdown/seismo-relay#10