serversdown

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-25 11:34:17 -04:00

d522d31d63 docs(series4): what THOR's "status check" actually is -- 11 commands, 563 MB/month

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-25 11:30:09 -04:00

45f2997a5b feat(bridges): mm_link -- a bench "modem" with a readable log and fault injection

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-25 01:56:48 -04:00

96a8831472 docs(series4): pin down what the ACH config's volatile field is NOT

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-25 01:27:26 -04:00

8e37803d40 docs(series4): event download, PER-EVENT delete, and the ACH config write

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-25 00:56:26 -04:00

f839541d08 docs(series4): CORRECT the schedule record -- [6] is the Action bitmask, not [0]

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-25 00:37:40 -04:00

cc1388df65 feat(scratch): recover captures from the socat relay log -- validated byte-exact

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-25 00:35:40 -04:00

98cbdad489 docs(series4): Repeat is folded into Action -- and [6] is not the repeat flag

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 21:40:08 -04:00

4a1cccf3f5 docs(series4): the schedule file is DECODED -- two records, five confirmations

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 20:29:56 -04:00

508448e2dd docs(series4): the schedule record format, named by the firmware itself

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 20:02:33 -04:00

3f58402085 docs(series4): the ACH session, from the THOR manual -- and I was asking the wrong question

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 19:50:06 -04:00

8c2dacf035 docs(series4): the schedule has a setup-less start action -- Thor never uses it

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 19:46:16 -04:00

ebcc55e2ec docs(series4): the schedule<->config coupling is Thor's, not the protocol's

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 19:44:08 -04:00

bd876b6752 docs(series4): separate Thor's conventions from the protocol's requirements

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 19:26:41 -04:00

c5eed6fa46 docs(series4): RETRACT "no file transfer" -- 0x94/0x48/0x8D/0x8E read and write by path

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 19:19:02 -04:00

5400f1bef7 docs(series4): monitoring control, the setup-list walk, and the device clock

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 18:56:23 -04:00

b5e34ce8ae docs(series4): overwrite is protocol-identical to create -- no handshake

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 18:48:23 -04:00

d33e2d85be docs(series4): 0xDA creates setup files -- confirmed on the device

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 18:36:04 -04:00

c8d972f685 docs(series4): the setup-write path, observed end to end

serversdown opened issue serversdown/seismo-relay#41

2026-09-24 15:10:01 -04:00

Derive series-3 record_type from the binary, not the filename extension

serversdown pushed to feat/series4-protocol at serversdown/seismo-relay

2026-09-24 00:32:01 -04:00

701af47170 docs(series4): generate IDF filenames rather than detecting record type

02ed22f561 docs(series4): firmware static analysis, and all five bench events decoded

23cdbef737 docs(series4): setups are files; and the length field is a uint16

71f19c90d1 docs(series4): SUB 5A streams the .IDFW file verbatim -- read path complete

Compare 4 commits »