Open jaycedowell opened 8 months ago
The error message comes from:
based on info from:
That function looks at all the usual suspects: time, frequency, and bandwidth. It's not clear from the logs what doesn't match.
This might be more of a buffer size issue when dealing with a big skew between the two polarizations. Maybe https://github.com/lwa-project/ng_digital_processor/tree/new_drx_packetizer would help?
It's still happening. Maybe we really do need to go to new_drx_packetizer.
Ah, I can trigger this if I send two DRX commands in rapid succession.
Using a much larger buffer size (minimum of 64 blocks vs. the original value of 8) seems to help but that isn't a very satisfying solution. Maybe it's the ordering of the packets coming out of the T-engine. I should do a raw recording (and one at Sevilleta) to see what that is like.
When I look at the DRX flow at North Arm vs. Sevilleta I think the North Arm flow is much more consistent with nice, uniform blocks of eight packets. Sevilleta, on the other hand, seems to have a lot more variation in the packet ordering. Based on that I would expect Sevilleta to be the problem station unless this issue is related to some kind of rare condition at North Arm.
Since STP seems to work I've dropped back to the default block count limits to see if this is a viable solution.
Nope, this is still happening. The stress test failed this morning as well as another test I ran this afternoon.
Update: Going back to larger buffers for testing (64 <= buffer count <= 256).
"INCOMPATIBLE" might be a clue...