You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a heads-up to others... My Linux boxes work just fine with the Firehose, but both my M1 and M2 macs drop ethernet packets randomly (shows up as IQ values of 0). Appears that the M1 and M2 macs have something wrong in their ethernet firmware or hardware.
The text was updated successfully, but these errors were encountered:
Might there be options in the macOS networking stack or device drivers to help with this? Back in the day I remember playing with things like the Linux driver's RX buffer size or interrupt threshold to decrease drops. Everything has been reliable at default settings of late, though.
By the way, if the dropped packets are single packets only, then the dropout is likely too short in duration to affect the GNSS signal processing. Large contiguous drops, though, of say more than 100 packets in a row, can start to be a problem. Each packet's payload has a timestamp inserted by the FPGA, so the packet2wav tool knows when to fill in with zeros; this means the timing of the sample stream emitted by packet2wav is undisturbed by dropped packets, but of course the SNR decreases because of the lost signal.
I researched online and found others having the same issue. I tried several different OS setting changes, but none worked for me. So i gave up trying to use the M2 Mac for recording. The dropped packets were pretty large blocks, and the dropouts occur regularly.
Just a heads-up to others... My Linux boxes work just fine with the Firehose, but both my M1 and M2 macs drop ethernet packets randomly (shows up as IQ values of 0). Appears that the M1 and M2 macs have something wrong in their ethernet firmware or hardware.
The text was updated successfully, but these errors were encountered: