search

km4ack / pi-build

https://youtube.com/km4ack
338 stars 71 forks source link

Bullseye - Pi4 - FlRig issues #398

Closed thufer2002 closed 2 years ago

thufer2002 commented 2 years ago

Flrig works for about 2 contacts then locks up in transmit but with no signal driving the xmtr. Can't reboot PI4 must power off/on to reset. Flrig will take a long time to close if "X'ing out of app. As noted by another user Flrig open with 20M selected, also the apps location on the desktop is not remembered and always starts at the same position no mater what I do.

My setup: Pi4 with Flirc case, UBlock GPS, IC-705 Rig

km4ack commented 2 years ago

I could be wrong but this sounds more like an RFI issue than an FLRIG issue. I have the latest version of FLRIG running with my 705 without any issues. Try shortening the USB cable between the Pi and the 705 and adding a ferrite bead or two.

Another test is to reduce to power of the 705 to 1/2 watt and see if the same issue occurs. If not, it is almost certainly RFI getting into the Pi.

thufer2002 commented 2 years ago

Some suggestions for ferrite beads? Amazon link? I’ll try it.

Though the same length of cable and a PI Zero w2 (Non Bullseye) works just fine. Both pi’s built within last 3 days

From: KM4ACK @.> Reply-To: km4ack/pi-build @.> Date: Sunday, April 10, 2022 at 5:02 PM To: km4ack/pi-build @.> Cc: @." @.>, Author @.> Subject: Re: [km4ack/pi-build] Bullseye - Pi4 - FlRig issues (Issue #398)

I could be wrong but this sounds more like an RFI issue than an FLRIG issue. I have the latest version of FLRIG running with my 705 without any issues. Try shortening the USB cable between the Pi and the 705 and adding a ferrite bead or two.

Another test is to reduce to power of the 705 to 1/2 watt and see if the same issue occurs. If not, it is almost certainly RFI getting into the Pi.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

km4ack commented 2 years ago

I don't like recommending something that I haven't personally used. I picked up these https://amzn.to/379kvHd several years ago but they are no longer available.

That is odd that it is only happening on one pi. I am assuming that you are using the same cables for both?

You might also try posting in the FLDIGI forum and see if others might have suggestions. https://groups.io/g/linuxham/topics You are also welcome to post in the Build a Pi forum as well https://groups.io/g/KM4ACK-Pi/topics

By chance is this happening when you are only using ARDOP? If so, see this post. If this is the case, I apologize for not mentioning it in the first respone.