Closed hemna closed 4 years ago
This is what I'm seeing from goesproc
VC 1: Detected TP_PDU drop (skipped 9 packet(s) on APID 38; prev: 2544, packet: 2554)
VC 1: VCDU drop! (lost 3; prev: 6576364; packet: 6576368)
VC 1: Detected TP_PDU drop (skipped 9 packet(s) on APID 38; prev: 2554, packet: 2564)
VC 1: VCDU drop! (lost 3; prev: 6576369; packet: 6576373)
VC 1: Detected TP_PDU drop (skipped 9 packet(s) on APID 38; prev: 2567, packet: 2577)
VC 1: VCDU drop! (lost 3; prev: 6576373; packet: 6576377)
VC 1: Detected TP_PDU drop (skipped 9 packet(s) on APID 38; prev: 2577, packet: 2587)
VC 1: VCDU drop! (lost 3; prev: 6576377; packet: 6576381)
VC 1: Detected TP_PDU drop (skipped 9 packet(s) on APID 38; prev: 2587, packet: 2597)
VC 1: VCDU drop! (lost 3; prev: 6576382; packet: 6576386)
VC 1: Detected TP_PDU drop (skipped 8 packet(s) on APID 38; prev: 2600, packet: 2609)
VC 1: VCDU drop! (lost 3; prev: 6576386; packet: 6576390)
VC 1: Detected TP_PDU drop (skipped 8 packet(s) on APID 38; prev: 2610, packet: 2619)
VC 1: VCDU drop! (lost 2; prev: 6576391; packet: 6576394)
VC 1: Detected TP_PDU drop (skipped 5 packet(s) on APID 38; prev: 2622, packet: 2628)
VC 1: VCDU drop! (lost 3; prev: 6576394; packet: 6576398)
VC 1: Detected TP_PDU drop (skipped 9 packet(s) on APID 38; prev: 2629, packet: 2639)
VC 1: VCDU drop! (lost 3; prev: 6576399; packet: 6576403)
VC 1: Detected TP_PDU drop (skipped 9 packet(s) on APID 38; prev: 2642, packet: 2652)
VC 1: VCDU drop! (lost 3; prev: 6576403; packet: 6576407)
VC 1: Detected TP_PDU drop (skipped 9 packet(s) on APID 38; prev: 2653, packet: 2663)
VC 1: VCDU drop! (lost 3; prev: 6576408; packet: 6576412)
VC 1: Detected TP_PDU drop (skipped 10 packet(s) on APID 38; prev: 2666, packet: 2677)
VC 1: VCDU drop! (lost 3; prev: 6576412; packet: 6576416)
VC 1: Detected TP_PDU drop (skipped 9 packet(s) on APID 38; prev: 2678, packet: 2688)
VC 1: VCDU drop! (lost 3; prev: 6576417; packet: 6576421)
VC 1: Detected TP_PDU drop (skipped 9 packet(s) on APID 38; prev: 2691, packet: 2701)
VC 1: VCDU drop! (lost 3; prev: 6576421; packet: 6576425)
It's likely that your machine is dropping I/Q samples before they're reaching goesrecv. If you're using a Raspberry Pi, then it might have its CPU throttled. This can happen because of high temperature or high load and can be undone by rebooting it.
It was due to a bad power supply, causing low voltage
Hey guys, I've had goestools running for a long while on my rpi in a docker container. I've been noticing that I've not been able to decode any packets for a while due to drops. I'm seeing vit rates between 280 and 500, all with 13+ or so drops. I'm not sure what's up. Am I just not getting good enough signal to decode anything?