search

ac2cz / FoxTelem

AMSAT Fox-1 Telemetry Decoder
GNU General Public License v3.0
52 stars 17 forks source link

Another failure to open SDR #750

Closed burnsfisher closed 2 years ago

burnsfisher commented 2 years ago

I can't find this, although I'm pretty sure there is another issue like it. FoxTelem stopped because it said the soundcard was not available. It appears not to have tried 5 times (only 1 according to the data line at the bottom).

Screen Shot 2022-09-05 at 2 46 56 PM
ac2cz commented 2 years ago

Actually I think it did retry 5 times. The counter at the bottom is confusingly split into two. The first number is the fatal issues that result in this error. The second number is the number of retries. The first number may not be needed I suppose.

So this is expected behavior. There was an error on the USB bus that caused this to be unavailable. I could consider increasing the delay between retries. What do you think? Right now it waits 200ms between retries. That seems to work for the normal situation where a bit of noise on the bus caused the first try to fail. But should it wait longer and longer on each try?

burnsfisher commented 2 years ago

Oh, so the '1' means that all 5 problems were the same thing. It's possible this is "real". I'm trying to get it back online remotely and even a reboot does not seem to help. Maybe it needs a full power cycle. I'll let you know.

On Mon, Sep 5, 2022 at 5:34 PM Chris Thompson @.***> wrote:

Actually I think it did retry 5 times. The counter at the bottom is confusingly split into two. The first number is the fatal issues that result in this error. The second number is the number of retries. The first number may not be needed I suppose.

So this is expected behavior. There was an error on the USB bus that caused this to be unavailable. I could consider increasing the delay between retries. What do you think? Right now it waits 200ms between retries. That seems to work for the normal situation where a bit of noise on the bus caused the first try to fail. But should it wait longer and longer on each try?

— Reply to this email directly, view it on GitHub https://github.com/ac2cz/FoxTelem/issues/750#issuecomment-1237471557, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASNGPGJUKQTSHX2P44HTDLV4ZRPLANCNFSM6AAAAAAQFG3CI4 . You are receiving this because you authored the thread.Message ID: @.***>

burnsfisher commented 2 years ago

Very odd. I just unplugged the FCDPP and replugged it in another USB socket and then rebooted the Pi. Same behavior. I have it set so it does not autostart now. I push the start button and everything looks ok EXCEPT there is nothing in the RF or the AF windows. I stop and start again, and I get the message above and again a 1/5. I wonder if my FCDPP is dead? Maybe tomorrow I'll try a different one and/or an RTLSDR.

ac2cz commented 2 years ago

I doubt the FCD is dead. This behavior sounds familiar. I think I saw that in development. Try changing to a different mode, say DUV and start again. I think the decoder crashed because the mode was wrong. It then looks like the USB errors because it retries. The mode is wrong because I changed the way that it is stored in the MASTER files. Say the issue may reoccur again with auto start when it changes modes.

You could also move to 1.12y which I just released because it addressed that issue and might fix the problem.

burnsfisher commented 2 years ago

YES! Switching to DUV, stopping and restarting FoxTelem solved it. (Just switching did not solve the problem until I restarted it). Odd that it failed after running for several weeks. Anyway, I'll pull 1.12y.

On Tue, Sep 6, 2022 at 8:48 AM Chris Thompson @.***> wrote:

I doubt the FCD is dead. This behavior sounds familiar. I think I saw that in development. Try changing to a different mode, say DUV and start again. I think the decoder crashed because the mode was wrong. It then looks like the USB errors because it retries. The mode is wrong because I changed the way that it is stored in the MASTER files. Say the issue may reoccur again with auto start when it changes modes.

You could also move to 1.12y which I just released because it addressed that issue and might fix the problem.

— Reply to this email directly, view it on GitHub https://github.com/ac2cz/FoxTelem/issues/750#issuecomment-1238105259, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASNGPHBN6T3LKRFHNIZ463V444TFANCNFSM6AAAAAAQFG3CI4 . You are receiving this because you authored the thread.Message ID: @.***>

ac2cz commented 2 years ago

Ok, thanks good. Then I am going to mark this as fixed in 1.12y and you can confirm that.

burnsfisher commented 2 years ago

I have not seen this problem on 1.12z.