Pluto inconsistently sees no signal #1
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sometimes both the forward and backward RX channels show no signal. This is either a failure to TX or mis-mapping of RX channels. I don't remember exactly what I saw when I encountered this issue a couple weeks ago but I remember questioning if the input MUX inside the Pluto was selecting the wrong ports resulting in no (or extremely low) signal.
This seems related to an issue John Kraft had a couple years ago:
https://ez.analog.com/adieducation/university-program/f/q-a/555400/pluto-rev-c-2nd-tx-channel-is-not-consistently-sending-data
It is possible this was resolved in a firmware update since 2022 (I haven't updated firmware in ages)
This may be related to #2 which also has to do with bad data from the Pluto after re-initialization but I don't think its the same.
"no signal" in this issue was very low levels but not truly zeros if I recall correctly so would not result in divide by zero warnings as in #2 (unless there are just a few zero points.
I haven't seen this particular issue for a while so I'm gonna say I fixed it while thrashing all of the code🤞.