Pluto inconsistently sees no signal #1

Closed
opened 2025-01-06 16:22:43 -07:00 by brendanhaines · 1 comment

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)

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)
Author
Owner

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🤞.

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🤞.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: brendanhaines/charon_vna#1
No description provided.