… that’s decoded w/ one of those embedded python blocks when there is not a native block to accomplish a particular task. I’ll get the .GRC file and the strongest packet sample I/Q posted asap.
Did a bit more digging (with Claude). Based on Scott K4KDR’s ChatGPT assisted grc, added some refinements. Just remove zip suffix.
Added carrier estimation and de-rotation, all codeblock counts instead of just 17 and 19, and brute-force 2-bit repair of up to two bad codeblocks, with the CRC and the 0x55 fill check deciding. The sample rate is a variable (tested at 93750, 57600 and 50000), and it writes UTC timestamps, KISS and CSV output. Hard decisions only, so bursts with more than about 3–4% bit errors are lost.
I couldn’t help myself, I had to drop the HEX image in Claude.
This satellite would be running on 3 cells in series, monitored on each cell.
Yes, I can read it from the image. I transcribed the first frame and decoded it. Short answer: nothing in common with GRITSS, but it decodes nicely in its own right.
Why it isn’t GRITSS-like:
No AX.25 header. There are no shifted call signs like GRITSS’s GRTSFM.
None of GRITSS’s frame types (8C, 8D, 8F, A0, A2 …).
No Unix timestamp. I searched every 4-byte position, little- and big-endian, and found nothing within a year of the reception time.
A different battery. GRITSS has a 4-cell pack at 14.5–16.1 V. This one has 3 cells (see below).
What it does show:
Frame start c0 01 3f a0 00 72 82. It’s the same in every frame, then comes a big-endian frame counter at bytes 7–8: 01 99 → 01 9a → 01 9b → 01 9c.
Two alternating frame types. You can tell them apart by bytes 9–15 (e0 08 09 c4 6x and e0 08 0a c6 ax).
From byte 27, uint16 little-endian values, mostly in pairs:
about 3444–3601 (14 values in pairs, perhaps min/max or A/B)
2496/2500
4149, 4092, 4215 and then 12456, the exact sum of those three: 4149 + 4092 + 4215 = 12456. That’s a 3S Li-ion battery with cells at 4.09–4.27 V and the pack at about 12.5–12.8 V. The next groups do the same: 4193/4121/4267 with 12566, and 4210/4222/4224 with about 12.7 V.
979/983, perhaps a current or another voltage
The last bytes are probably a checksum or CRC.
Because 4149 + 4092 + 4215 adds up exactly, my reading of those bytes from the screenshot is confirmed. A misread elsewhere is possible, but small. Which satellite is it? With the name I can look for a frame description.