开云体育

Actually, I may have mis-spoke. It seems that if the monitor is disconnected ardop locks up the pi, but if the monitor is connected it works... There is a chromium window that pops up on the monitor

Hi Jason, thanks for your response! I just got time to do a little more testing and I'm not sure that it's RFI. When starting the ardop modem there shouldn't be any trigger to TX at that point? Also I

I agree with Mark Johnson. When it comes to RFI issues with USB devices, I have had very good results using a type 31 mix ferrite and placing as many turns of the USB cable as possible through the

With the Raspberry Pi 4B? I have always used the official Pi wall wart PS.? It is recommended that 5.1 at 3A be supplied to the Pi4's USB-C port, that supply meets that criteria.? In the past they

I think you are onto something as with the RPi off but powered through the GPIO, I get noise with the SDR dongle connected but not with the WIFI dongle connected. So obviously it might well be the

Thank you Jasn for the hard work put into the BAP and getting it to work =) A lot of your time has been put into this project and you have done well =) My hat is off to you for the great job and

With the power supply attached to the GPIO pins, your RTL SDR dongle is probably always powered on, as confirmed by the RFI being generated if the RPi itself is on or off. can you borrow a different

Pi OS 64bit running on a Pi 4 4GB A bit more experimenting this morning. My suspicion about VNC was incorrect. I made these changes to the /boot/config.txt file. Uncomment the following lines:

I tried using firefox-esr over chromium because I don't like anything google and had far more problems.? 30 minutes later I bit my pride, locked down chromiun and put it back into service. On Fri,

Hi Kevin, Thanks a lot, I will try out this weekend and come back with a feedback Klaus, DC2JR Von meinem iPhone gesendet

Ptt is set to true with ?no luck

Guys I have no intention of tackling x86 machines right now. Between my day job, the channel and Build a Pi, I just don't have the time to support yet another version. With that said, my code is

I don't own that radio but I am guessing that it is RFI getting into the Pi or radio that is causing it to lock up on transmit. Shorten every cable as much as possible and add ferrite beads to all of

In Pat Menu, click on Manage Pat Winlink->Set ARDOP PTT. Set this to true and test your PTT again. -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar ( https://www.paypal.me/km4ack )

I would flash a new card and start over. Your old system is probably running Buster and Bullseye is the latest available. The Pi foundation does not recommend upgrading from Buster to Bullseye as many

got this figured out... found a substream on here where, when using the update tool just enter "*" in the ip address... i was entering the ip address for the raspberry pi... but when using the

This is possible but an advanced setup. Try pointing one of the applications to the actual sound card and the other to "pulse". Then open pulse controls from the Pi menu and link the second (pulse)

Hi Jason: Yes, possible & probable! I should have looked closer. Thanks, -- Jeff Marden N1JCM

Dan, Thanks for the testing and the detailed explanation. I have been extremely frustrated with Chromium since Bullseye came out. I never had this issue in Buster. I suspect it is something in VNC

IIRC, BAP is on github; it might well be as simple as forking it, and doing a search/replace to change the architecture specified in the scripts. I might have a look myself when i have a moment.