开云体育

I think the consensus is to start a "clean" build ie: new SD card flashed with Bullseye and then recompile apps using BAP. I think Jason redid BAP to be compatible with Bullseye.? Other option would

I am going to upgrade my Ultimate Pi and upgrade to Bullseye and the latest set of BAP apps.? I am not exactly sure how to do this.? If it were like a Windows box I would create a new MicroSD with

Excellent, will try tonight. As an aside, would installing a real time clock module, a 3231 I think, affect connectivity? Rich ___________________________ Think different, Macintosh. ? This e-mail,

Not always but typically this is a symptom of Radio Frequency Interference. Try ferrite beads on all of the cables connected to the Pi and use as short of cables as possible. RFI drove me nuts a

FLRIG will lose the config in my experience unless you shut it down correctly after configuring your radio. Try configuring the radio and doing a graceful exit for FLRIG. Now restart and the rig

Hello there, Regards from Costa Rica, this is TI2GBB. I have? Pi 4 B and I just installed the KM4ACK build pi. I configured all following the next video

Jason,?So I ran two commands, no errors, Hamlib 4.3 version. So what is very interesting is that I could not get FLrig to connect to the radio until I close down, restarted and then was able to

OK, thanks. -- 73 de N5RKE

Yes I run an update as a Sudo apt update-full (forgive syntax I'm at work if this is wrong). I also did run BAP update on all with exception for FLDIGI which I updated manually. I will try the code

Another up-vote for rpi-clone.? Worked a treat for duplicating my working setup into a second microSD (smaller) for some hardware experimenting. 73 WX4P

It isn't recommended to update a Buster system to Bullseye. There are a lot of changes under the hood in Bullseye and the probability of something going wrong is increased. It is best to start with a

Did you run any update since it worked last? Either manually or using the BAP update tool? Run this command and see if it throws any errors: *rigctl -m 1 f * also run this command to see which version

Hi folks, I was wondering if you could give me some help on where I need to look to get the error pictured below corrected. I have several Pi running BAP and up until last week I was able to connect

I'm confused (nothing new). Can we update Buster to Bullseye, and then run this new BAP, or will this only work on a clean (never had Buster) Bullseye build? -- 73 de N5RKE

Are you running BAP Beta for Bullseye? The Build a Pi version number of the beta is 3.2.0. -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar ( https://www.paypal.me/km4ack ) Twitter (

It would be possible to script it and then auto start either using a cron job or systemd but you would need to verify that the mobilinkd is turned on before booting the Pi. Feel free to use my script

Hi I have found a solution for having 2 monitors plus USB audio codec (from Signaling). Further looking on Web for just sound card issues, got directed to Web site: instructibles.com

Also, for the GPS 'hat',your /etc/default/gpsd file should contain these lines: *START_DAEMON="true"* *USBAUTO="false"* *DEVICES="/dev/ttyS0"* (your device may be different) *GPSD_OPTIONS="-n -b"*

Have you enabled the uart in /boot/config.txt? *enable_uart=1* *init_uart_baud=9600* if you'll use the pps function of the hat: *dtoverlay=pps-gpio,gpiopin=18* (your pin may be different) also, in

Are the folks getting a good build of Bulleye BAP using a GPS module?? Are gpsd and related GPS functions working OK? I have a Bullseye/BAP build but I use a GPS "hat" plugged into the GPIO pins (not