Follow up after successfully getting BAP completely installed on the RasPi 64-bit OS:

I was able to set up Flrig and Fldigi, then operate WSJT-X, but no joy with Pat. Today I plan to put the 32-bit card back in and confirm all the settings then swap out to the 64-bit card in the event I’ve overlooked something. ?Thought I went through all the steps, but when clicking Start ARDOP Modem, received the “ARDOP failed to start” error message multiple times. ?After clicking O.K., then the browser opens showing “This site Can’t be reached” - 127.0.0.1 refused to connect and the URL line shows 127.0.0.1:5000. ? Settings process: ? Went into Pat Menu Settings and Rig Control is set to “yes” and Pat Port shows 5000. ?The ARDOP Command line shows “… plughw:3,0 plughw: 3,0” which are the same shown when running the command “arecord -l” (card 3: CODEC [USB Audio CODEC], device 0: Audio [USB Audio]”. ?I updated had updated the Sound Card Set ARDOP PTT = true

Not sure what’s driving the non-start, but will add more details later.

73, Ken NB6S

Kevin,

Thanks for the detailed log. I'll take a look at VNC viewer this afternoon and double check the link that BAP is using to download.

--

Crontab is your issue. Run this command:
crontab -e
Pick nano if you have never used the crontab editor before. Now delete all but these two lines

#Winlink Gateway Auto Start at Boot
@reboot sleep 20 && /usr/local/bin/gateway-start

Press ctrl+s to save then ctrl+x to exit. Reboot and you should be in business.

--

What might we expect the pros and cons of a working 64 bit build to be?

Faster? Smaller?

Faster, bigger?

More efficient memory use?

Would appreciate comments of those that might know!

TY

Thanks for the response, Bryan.

? Dan

32-bit.? I tried 64-bit before BaP v3 came out and really had a mess.? Things may have settled with Bullseye 64-bit by now.

Dan
N7SHM

Hi Doug,
I have a G90 that works well with WSJTX. Unfortunately, my connection does not include a digirig or the Xiegu C19, so these settings may not work for you. I run a line from the ACC jack that splits in two and goes directly into an inexpensive usb sound card connected to the PI. I primarily use Pat winlink, JS8call and WSJT-X and don't make any changes in between.? My settings on the G90 are:

I was having trouble with not being able to access VNC and the system seemed to have frozen several times over the first week or so of install. A restart would fix it. But I came here to let you know that I have applied all available updates and have not had any problems with the system or any applications that I use for at least the past 5 days now. That said, I only use Conky, JS8Call, WSJTx Flrig and Patwinlink. Most of my SDR stuff is on my Windows machine with a different radio. I am on 32bit Bullseye.

开云体育

Hi Dan

I don't think I can help, but a question, is this on a 32bit or 64bit system?

Marty kd8bj

I'll just toss my "Installed everything with no problem" in there as well.

I don't have a radio currently to hook up to, but will be trying them with wfview on a remote station as I was using the previous 32 bit build that way. No hiccups during install at all.

I was able to install the entire BAP package. Now to start actually trying out some of the programs...

Nice job...

73, Ken NB6S

Am I the only one struggling with Bullseye?? Setup: RPi 4, 8GB. Eviciv 7" touchscreen/case + VNC.

It seems like every time I turn around, something stops working.? Right now, it's screen blanking on the physical device.? For the time being, at least, while configuring and testing, I turn off screen blanking while I do most work via VNC.? The screen was staying on until, after a couple reboots, it started blanking after awhile.? Sure enough, the switch in RPi Configuration (GUI) was turned back 'on'. Turned it back off and went back to work.? Online research shows Bullseye has been plagued with related trouble for months.

Today, the "switch" is still off, but the screen is still blanking and the touchscreen is unresponsive.? Reboot and the physical device (display, touch UI, and BT keyboard) works fine until the screen blanks.? VNC continues working, regardless.? I'm confident that the physical device is stable because it's completely stable upon a new OS flash.? Yesterday, CubicSDR with an RSP2Pro suddenly (and again) broke while I was working on something completely unrelated and seemingly innocuous.?

I'm becoming convinced that Bullseye, components, and applications are not sufficiently stable for the appliance-like functionality that I'm seeking.? Not being new to Linux (25 years) or RPi "appliances", I'm really getting frustrated trying to get a basic set of BaP functions all configured and running stable.? Past experience suggests this isn't a hardware issue.? Even doing (semi-) regular SD card copies for system snapshots, I've had to start from scratch a couple times.? The SDR setup went kaput yesterday right after I started seeing "updates available" although I didn't install anything.? At this point, I'm going to have to turn off all updates and maybe even disconnect the network altogether.

Anyone else seeing similar?

?? Dan
?? N7SHM

开云体育

I hope "large" does not mean full screen.? I want it just big enough to read the text but not full screen.? Thanks for the information!

David

Clean install of RPiOS-64
sudo apt update && sudo apt upgrade -y
cd ~
git clone https://github.com/km4ack/pi-build.git
cd ~/pi-build
git checkout dev
bash build-a-pi
Select Conky & VNC Viewer for install
runs through the process
reboot
Wall paper changed
Conky runs,
VNC Viewer not found
re-run Hamradio, Build-a-Pi, Update tool
VNC Viewer: not installed.
Check it for installation
Click Install/Update Selected
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Reading package lists... Done???????????????????????????? ?
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
--2022-03-01 09:27:29--? https://realvnc.com/download/file/viewer.files/id=download-link-path%22
Resolving realvnc.com (realvnc.com)... 54.187.227.204
Connecting to realvnc.com (realvnc.com)|54.187.227.204|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://downloads.realvnc.com/download/file/viewer.files/id=download-link-path" [following]
--2022-03-01 09:27:29--? https://downloads.realvnc.com/download/file/viewer.files/id=download-link-path%22
Resolving downloads.realvnc.com (downloads.realvnc.com)... 18.67.76.6, 18.67.76.117, 18.67.76.82, ...
Connecting to downloads.realvnc.com (downloads.realvnc.com)|18.67.76.6|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2022-03-01 09:27:30 ERROR 403: Forbidden.

--2022-03-01 09:27:30--? http://value=/
Resolving value= (value=)... failed: Name or service not known.
wget: unable to resolve host address ‘value=’
dpkg: error: cannot access archive 'id=download-link-path"': No such file or directory
rm: cannot remove 'id=download-link-path"': No such file or directory
rm: cannot remove 'value=': No such file or directory
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'libhamlib4' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Installed everything last night and the install went smoothy.

WSJTX installed and works. No problems


Ryan NC4RA

--

Interesting. Something has to be starting multiples at boot. Run this command and post the results please:
crontab -l
--

Mike is correct. Each kit ships with ~68 feet of wire allowing the operator to tune it for their favorite portion of the band.
--

The executable file is in /usr/local/bin/ You can also use the BAP update tool to change the size (large/small) by reinstalling.
--