开云体育

Equipment: G90, digirig mobile, raspberry pi 4 with 8g. ?Ferrite toroid is used to block any RFI coming from the usb c cable to the Pi4. ?I’m using the uBlox GPS dongle. ?The GPS connects within a few minutes. ?

the problem: ?Flrig connects to The G90. ?WSJT-x decodes fine, but the decodes are at best .5 off. ? I still get lots of qso’s, but I’d like it better. ?

what I’ve done: ?I’ve made certain the GPS works. ?The time in Conkey looks correct. ?I’ve used time.is as a guide to sync the Pi4 with the terminal command to set the date and time. ? But, I’m still .5 off. ?Any ideas? ?

FYI, while testing for another project, installed clean RPiOS-64, updated, and then attempted to run the Build-A-Pi set of instructions, and got a failure:
pi@raspi4:~ $ cd ~
git clone https://github.com/km4ack/pi-build.git
bash: git: command not found
Installed git manually.
Afterwards, process proceeded normally. Might want to check for 'git' availability, or include it in your setup instructions....

Jason - That fixed the ARDOP modem not starting. ?Tested and made connection on 40 meters.
VNC Viewer is also working.
tested HAMRS this morning and it runs fine.

For me, it's whether the applications that I need have a 64-bit build and, if so, whether there's a performance difference worth the effort.? Having recently backed out of Bullseye 64-bit with BaP to 32-bit, I presently see little upside in the former for my uses and greater value in the "least common denominator" of 32-bit.?

The RPi 4 w/8GB here is just loafing around even then most of the time with the BaP applications that I use.? CubicSDR puts a higher load on the processor, but isn't critical in my intended uses so I'm not interested in comparing its 64- v. 32-bit performance differences or whether CubicSDR's application development trajectory would push me toward 64-bit at some foreseeable point down the road.

? Dan
? N7SHM

2. The TQSL application said there was a newer version available, even though BAP Update said latest version installed.

Jeff,

For TQSL, the latest version (2.5.9) installed during testing this morning. I did get the following dialog:


Were you possibly confusing this for a new version of TQSL?

--

I use any of a number of USB dongles for my Rpi4-8GB and Argone One V2 case. Most are EDIMax, or RaLink ET series, and work well at the 802.11a,b,g & n levels. I've only found one that runs well at 802.11ac with built in kernel driver, an ASUSTeK USB-AC55 Dual Band AC1300. When in AP mode, everything I have that can connect in AC mode (5GHz) does (laptops, tablets, other Pi4s, etc), and I don't have to worry about adding or modifying drivers to use it.

Be sure you are running the test on a clean build. If the build is a couple of week's old, it could introduce issues. I just built FLDIGI & FLRIG this morning on a Pi 4 without issue.

ARDOP - there was an issue with the modem installing but has been resolved (I think). To update your system, run:
cd ~/pi-build
git pull
Now reinstall ARDOP using the BAP update tool.

VNC Viewer - This issue has been resolved. I thought it was a curl issue but it was a broken link. Follow the same directions as stated for ARDOP above.

I'll look into TQSL to see if I can figure out the version issue.


--

There are mods out there to add an external antenna on the Pi to be utilized instead of the internal one.? It involves some pretty careful soldering and SMD work.? I've done the install on one of my spares but haven't get tested it thoroughly.? Try


mike
KO4BCN

Hi David,

Since you just started and haven't loaded anything yet, it might be easier to reflash the SD card. This will assure that the Pi user is in the correct groups and reduce the possibility of issues later down the line. You can set the hostname to anything you want but leave the user as Pi. I have a video coming Friday that will walk you through step by step getting Build a Pi running on your setup.

The only VNC viewer I have experience with is RealVNC
--

I ran Update again, this time with all the flsuite. Same result.? I ran it again, just with flrig and fldigi selected.? THe file flsuite.txt was created, containing FLRIG and FLDIGI.
It was compiled from source, flrig1-4.4. When it finished, the output showed this:

as the WLAN using the Argon One case is very poor, I want to use a USB WLAN dongle. What do I have to do, that I can use the WLAN dongle for connecting to local wlan and also running as accesspoint instead of the build in wlan of the raspi 4

vy 73 de Klaus, DC2JR

Hello Jason:

I loaded the 64-bit OS and then ran the BAP beta installation as per your directions. Pi4 2GB and a 32GB SD Card.

I installed all of the apps on you test list and ran them after install; all seemed to install and run correctly.

Two notes:
1. During the installs the Update box had many "Warning" entries in purple. I assume you know about these.
2. The TQSL application said there was a newer version available, even though BAP Update said latest version installed.

I hope this helps.

Thanks for all your work.

--
Jeff Marden
N1JCM

? Hello all, Well I am a newbie to PI..? ?First Off I want to thank everyone who has contributed to this huge project!!! Especially Jason for for taking so much time and effort to make all of the videos and scripts need to make this all happen!!? I am running the ultimate pi for hardware, as suggested in the video. I have debian bullseye loaded and running.
I get to the build a pi script and I get a flag saying my user name should be pi.? Somewhere I filled in the blanks and put in a username.? ? How do I fix this?? ? ??
? I do plan to run this machine headless and may run into problems.... The tablet I plan to use is pretty old but still works, with this said my tablet is to old to run the VNC viewer recommended here I have installed OMX Remote.? ? If there is a better one to use I would appreciate any advice.
?At this time I will let this soak until tmo.
Thank you in advance for the help.? KF0EXO? 73

Build-a-pi install ran smooth on a new 64bit OS installed on a 64Gb SD card.? The Raspberry pi 4 w/ 8Gb on board memory.

I have tested the following:
FLrig - set up and worked
Fldigi - set up and worked (using Flrig for rig control)
JS8Call - set up and sent out Heartbeat (using Flrig for rig control)
WSJT - set up and made several FT8 contacts (using Flrig for rig control)
GPS - worked using USB connected GPS and posted to Conky with correct Grid.
GPS - worked using iphone with GPS2IP app and posted to Conky with correct Grid.
Conky OK
Tested PAT Menu with the following results:
?- ARDOP modem - got "Modem Failed" message.? But it did start Pat Winlink.
?- Packet modem - modem started ok.? it started Pat Winlink and was able to make connection.
?- Mobilinkd (Beta) - Using a Mobilinkd TNC3 started the modem OK but did not start Pat Winlink.? ?I stopped?
? ?all modems and then selected Packet modem so it started Pat Winlink.? Then went back and stopped all
? ?in the Pat menu.? Then selected the Mobilinkd (Beta) and it started the TNC3 modem.? Then went to Pat?
? ?Winlink and selected X.25 and connect.? Worked fine and pulled down received message (the one I sent out?
? ?when using the packet modem.

Jason - Pat Menu Mobilinkd (Beta).? I went back to my old build-a-pi on 32 bit OS and found the same thing.? That it did not start Pat Winlink.? So it is not in the 64 bit build-a-pi build.

I had installed the 64-bit OS a couple of weeks ago and ran BAP.? Flrig aand fldigi did not install. I hd to indtall js8call twice to get it to work properly.? Several attempts at BSP update failed to get flrig installed.
WIth the new BAP, I moved the old directory aside and ran BAP again.? It detected the programs that I had already installed. I tried flrig and fldigi again, with the same result - not there.
Is there somewhere in the log that I can look to see what the problem is?

Paul VK2AHB

I'm not beta testing but running bullseye 64bit on rpi4 and rpi3 running fldigi and pat winlink. I haven't tried packet yet or any other modes. My gps isn't working on it yet.

I currently have a 64bit build of raspberry pi os on my 8gb pi 4. I believe it is a bit quicker than the 32bit version was. Install size of base system isn't much bigger if any.
I I haven't done any benchmarking tests but it feels faster to me.

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.

--