Install VARA on a Raspberry Pi 4

[@kwinzman]

A friend just asked me how to install VARA on ARM today. Your video was perfect! Thank you!

[@kurtzFPV]

This is great Jason! Really appreciate the walk thru. I'll probably purchase a license after I get everything up and running.

[@KM4ACK]

Thanks Bryan. I supported the developer and purchased a key after I got it up and running myself. Another tool for the Pi is always worth the investment :-)

[@KB5WCK_Radio]

Great Video Jason!!!! Got it configured and made my first ever VARA connection of any type. Checked into the WinLink Net 9a day late) !!! Works like a champ!

[@georgedandrade-hp1gds296]

Extraordinary news. Congratulations for the advances. Thanks a lot.

[@wolfgangbachschwelloe1wbs905]

Hi Jason, great work. Just connected on VARA FM and VARA HF for the first time following your instructions. 73 de Wolfgang OE1WBS Austria.

[@nomore1007]

Thanks for the video, I was able to modify this info for install on linux x64

[@briandale9274]

Just an FYI. PAT isn't commanding VARA to switch to 500hz bandwidth for 500 hz HF connections (it just stays at 2300 hz). The PAT team has been made aware and are working on it. 500 hz connections are what I use at QRP almost exclusively. I also let them know about the unexpected command messages. 73 de AD4XJ

[@KM4ACK]

Thanks for the report. I have just began working with VARA now that it is available on the Pi. Can the bandwidth be set manually in VARA?

[@srector3773]

@@KM4ACK I'm having that issue too. Connects fine to VARA but not to VARA-500 stns. There doesn't seem to be a place in the VARA GUI or in the PAT web interface to choose VARA 500.

[@KM4ACK]

@@srector3773 correct. Brian has reported to the dev team to address

[@briandale9274]

The correct beta update deb files were uploaded last night. Current version corrected the bandwidth switching and the unexpected command message.

[@thuff3207]

Thank you for showing how this works with Vara. Now can you easily run direwolf for FM Packet if needed and switch to Vara if needed. This might mean different ports to allow this to work for each program.

[@joshuacarroll7310]

Jason, it has been a year later. Is the beta version still required?

[@thomascorcoran9544]

Hello Jason, You specified the set of apps you used for this project. Do I create an issue if I add more applications to this image? Project works great incidentally with DigiRig/G90. RPi does run hot (65C). tnx Tom VE3NY

[@KM4ACK]

It would depend on what additional apps you intended to add. Most should have no negative impact. Since you have it working, just do a backup before adding additional software. Then you have a place to fall back to if things go wrong. kzbin.info/www/bejne/hZSvaIiiYsadsJI

[@EricMackie-v3f]

Hello Jason. I am trying to install Vara on my RPi 4B And looked at your very informative video above. I am running OS version 11 Bullseye but 64 bit so I went to the downloads section to get the 32 bit version. I then noticed that version 11 has been relegated to legacy status and there is a version 12 bookworm. Given that this video is now a bit dated, should I still download and install version 11 bullseye or should I use version 12 and 32 or 64 bit?

[@johngaynor3246]

Great video Jason. I have a question about VarAC, the new chat function that works with VARA HF or VARA FM. I would be interested to know if you have used it and whether or not you think it's of any value? Maybe a suggestion for a future video?

[@KM4ACK]

I haven't used it yet. Right now it isn't available on the Pi and I don't own a Windows device. GARIM is available on the Pi and has a similar feature set. The bigger question with these apps is always how widely adopted they will become.

[@Sebastian-nd1jh]

@@KM4ACK IIRC the pendant to gARIM (for ARDOP) is vARIM

[@angelscomputers]

This video is a year old, is this still experimental? it still need the 32bit version? I am just trying to install VARA on a Pi 4 to somehow get Varanny working and be able to use the Radiomail app from my iPhone and send emails from my truck. Thanks in advance Jason

Is there a later version of this video illustrating a more mature setup?

[@KM4ACK]

Not yet. This is still a good guide. The only difference is that you don't have to install the dev version of Pat. The latest Pat (0.13.0) supports VARA out of the box. The next version of Build a Pi will include an option to install VARA.

[@joelblack6174]

Jason, I just ran this script this morning and ran into an issue with VARA HF where I had to restart my RPi. When configuring VARA HF, it appears that the script auto-completes all the needed config in VARA HF. When I first ran the script, I tried to configure it myself. I may have mis-understood your instructions... I'm not sure. Regardless, if you just hit "OK" when the script tells you it is going to configure the sound card, do nothing. The script will configure VARA HF (and VARA FM and VARA SAT) sound card configs. You just have to sit back and let it complete. You just keep hitting "OK" when it pops up to configure the next application.

[@thomascorcoran9544]

Is it possible to add VarAC to this RPi 4 platform? This would be a great facility for field ops. FWIW, I did install WSJT and FLdigi and all seems to work ok. Tom VE3NY

[@KM4ACK]

According to this it is possible - www.varac-hamradio.com/forum/varac-discussion-forum/running-on-wine-raspberry64

[@dreupen]

This is great. When will there be an auto-vara-connect?

[@KM4ACK]

Eventually I hope to add this but a few key pieces are missing right now.

[@Alex_556]

First let me thank you for the script. You did an amazing work Jason! But... Running Windows applications under Windows emulator under x86 cpu emulator on ARM platform - this double emulation won't end up with acceptable results, that's no surprise. Apps are starting somehow but overall performance, stability, and usability are awful. So this way is good for a demonstration purposes but not a solution for a workhorse. RPI4 would be acceptable platform for ft8/ft4 clients (jtdx and mshv), fldigi, but not for fully functional Winlink or VarAC, unfortunately. I recommend to get a micro-PC instead. Just a tad bigger than RPi it has Intel cpu (N100 with 12Gb RAM in mine), runs Windows and all Windows apps as a breeze, feed from USB-C, can be controlled over VNC as well. A good solid working solution. 73!

[@KM4ACK]

For the last year or so I have been running the Evolve (x86) laptop. I have had no issues running VARA HF or VARA FM on it. It has been super reliable. As a personal choice, I stay as far away from Windows as I possibly can.

[@Alex_556]

@@KM4ACK x86 is a different beast. VARA works in wine on x86 just fine, but consumes more CPU cycles, comparing to Windows on the same hardware, because of wine emulation. Can't say the same about ARM platforms.

[@ericg1391]

So I am installing this on your build a pi build. How do I find the correct ip address? the 127.0.0.1:8080 is not working for me. Thank you for all of this. I am building a go box and hope to run it exclusively from the build a pi.

[@stuartcumming836]

Hi Jason . Thanks for the videos and walkthrough. I'm keen to get this working but having a few issues. Not sure how to upgrade to to V2.70 I'm using V2.11. I've gong to the git page and loaded v0.14.1 which looks like its the latest. The only one with a 2 is V0.2.4 I've loaded tried them both but it isn't changing the version on Pat Menu in my Pi. Do I need to uninstall earlier versions? Any help apprieciated. 72 Stuart VK6MK

[@KM4ACK]

Pat Menu is a separate app from Pat Winlink. Pat Menu can be downloaded from github.com/km4ack/patmenu2 Pat Winlink can be downloaded from github.com/la5nta/pat/releases

[@mikeclark4847]

On pi 4 64bit bullseye. Modem installs, but browser no longer accesses GUI PAT email. Connection refused. Any ideas?

[@KM4ACK]

Please post this question on the forum groups.io/g/KM4ACK-Pi/topics as it is easier to provide tech support there. Thanks.

[@OleSaastad]

I wish we could have a RPi native build of VARA-HF, how hard can it be to just recompile it ? Being forced to run en x86 emulator just to get around the none ARM build is a waste.

[@Sebastian-nd1jh]

You would need to decompile the .exe. VARA itself is written in Visual BASIC, using no multimedia extension for x86 at all, because of that it's using so much CPU, and Visual BASIC is only supported on Windows. I mean, it's a language from Microsoft itself... The author refused multiple times to port it to anything else than x86 Windows.

[@briandale9274]

Is there a way to disable PTT in the terminal window when you use rigctld -m 4? My g90 doesn't play well with CAT PTT and Signalink triggering PTT? I guess I could temporarily turn it off in FLrig but a command line switch would be awesome. How is it done with ARDOP?

[@KM4ACK]

Since you are using the signalink, you can skip the "rigctld -m 4". That is for CAT PTT and the signalink handles PTT via VOX. Also, you may need to manually edit the config.json file and change PTT from true to false in the VARA section. I don't know this for certain as I haven't tested with the signalink. I would only edit the config file as a last resort. If you do, be VERY careful in that file. One comma out of place in that file and Pat will no longer start. If that happens, use the "Restore config" feature of Pat Menu to get you back on track.

[@briandale9274]

@@KM4ACK editing the config file and changing PTT to false worked great. Thanks!

[@TheRanger53]

Hi Jason, I am trying to install Vara onto a RPI 4b. I have followed the video and have Pat winlink and Pat menu installed. When I get to the Wheezy/Winelink installs I keep getting the error that Autohotkey download failed! Winelink installation Failed. Internet connection is good.

[@KM4ACK]

File a bug report - github.com/WheezyE/Winelink/issues and see if Eric has a solution.

[@TheRanger53]

@@KM4ACK It seems that there is a problem with the script on Github. Another ham posted a issue and got the answer that the version was purged from GitHub 2.0. The script is currently critical stop. I guess I am out of luck.

[@andrewhamop6665]

Same error here, did you ever find a fix?

[@TheRanger53]

@@andrewhamop6665 there is a fix by Kelly posted as a fork

[@patrickhall5739]

@@TheRanger53 Hi Mike, I am having the same issue. I searched for the the link above but didn't see the fix? you wouldn't happen to have the link?

[@carltonsiple1876]

👍😎

[@timbookedtwo2375]

This is a breakthrough. It looks some kind of "WINE" is used to get VARA installed and running. Is that correct? If enough people start using VARA on Linux systems, maybe the author will do a clean port to Linux based systems, improving stability, performance and reducing overhead. I wanted to try out VARA, but I have no stand-alone Windoz system. I do run Oracle VM on all my computers, (not 0n a RBPi) and installed a test version of Windows 10 on a Linux laptop. I also installed Winlink Express, FLRIG,FLDIGI JS8CALL, PAT and AROP seperately. FLRIG, FLDIGI, JS8Call function as they should under my Windows installation, so I Iknow I have all the drivers set correctly. Even PAT and ARDOP are functional, meaning the TRX keyed up. After ending and closing these apps I started Winlink Express and tried both an ARDOP and VARA connection. I noticed I kept getting the message (in red no less) that the selected channel was busy. The channels are always busy und RMS Express. Under Linux PAT worked as it should. Under Linux/OracleVM/Windows 10 I was unable to connect, although the rig keyed up, in an almost A/B test. To make a long story short, I would be happy to see VARA or something else llike it run in a 100% Linux environment and would be happy to pay a reasonable license fee for something that is stable, fast and works. I am looking forward to trying out this BETA version of VARA asap. I just have to go down to the sacred store where I bought my cards before, and buy an SD card to back up my Pi4. As always, Jason, great work! 73! SV0SGS

[@FunInSC]

It's not just wine, it's Box86 as well since VARA is for x86 processors, while the Pi uses an ARM processor.

[@Sebastian-nd1jh]

Will probably never happen as José refuses to port it to anything else than x86 Windows because he doesn't know anybody who uses anything else than Windows.

[@neubert500]

This is great, but I am saddened that my Pi-3B+ cannot run this, and prices on Pi4s are crazy right now.

[@KM4ACK]

There's hope for the 3B+ github.com/WheezyE/Winelink/issues/35

[@harryhino2267]

Nice video Jason. Well presented as always. I lost interest as soon as WINE was mentioned. Nothing personal, but I prefer (and support) applications that run natively on Linux.

[@KM4ACK]

I would prefer it to run native as well but for now, this is the best we have.

[@ks2743]

@@KM4ACK with more and more *stuff* running in virtual machines, or virtual environments, I don't mind WINE so much anymore, as long as the installs and configs and maintenance are made as clean as possible. Thank you for your efforts, Jason, to that end. Yes, I don't mind it, but I do hope for native versions to be planned, as less can go wrong, I think, when doing updates... less links in the chain. Until then, thank you again, for being the middle man for so many of us.

[@Sebastian-nd1jh]

Probably won't change anytime since the author repeatedly refused to port it to any other operating system. His words: "Just get an Intel NUC with Windows", "I know nobody who uses anything else than Windows". Wonderful, amateur radio operators flock to a proprietary closed-source mode whose specs are barely documented at all. "It works great!!!! Stop whining!!!!! I don't care how it works!!!!"

[@ovalshrimp]

What is Vara anyway? Thanks Jason.

[@KM4ACK]

A software modem. Typically used to pass Winlink messages. VARA is for HF and VARA FM for 2M packet connections over FM.

[@mikemcdonald5147]

and its much faster than winlink

[@dougbas3980]

and has way better sensitivity in noisy environments. At QRP or 10 watt levels you are way more likely to succeed. VARA is a very good mode for weak signals.

[@briandale9274]

@@mikemcdonald5147 I think you meant ARDOP. Both ARDOP and VARA are the current software modems used for HF work with Winlink. WINMOR is NOMORE and VARA is much more affordable than PACTOR with no dedicated hardware modem required.

[@mikemcdonald5147]

@@briandale9274 thanks for catching that LOL Yeah vara is still Winlink and ardop is too. Messed up my terminology but you knew what I meant LOL :) Thanks again

[@uns3cur3]

Is this still a beta ??

[@KM4ACK]

Not sure of the official designation now but many have been using it with very little issue over the last several months.

[@richardwhitcroftkc3rrw63]

alot to digest....

[@no5x937]

If my Signalink was not attached to my RPi4 during this install, how do I setup its soundcard settings for Wine, VARA HF, and VARA FM? Can I do that from the menus or from the command line? What are the commands? Thanks.

[@KM4ACK]

From the menu, open VARA and click settings->soundcard. Choose the USB option for both input and output device. Repeat the process for VARA FM. No need to configure PTT as the Signalink has built in VOX to handle the PTT.

[@ks2743]

The current pat (beta) installer pat_b12a797_linux_armhf.deb has of course changed (thank you to the busy developer team), no doubt improving and fixing things. With that version installed on a fresh BAP with a fresh pi os 32 bullseye, and running the install vara only script at wheezey, all done today, I am getting the 2022/03/21 20:52:57 QSY vara: 7100.0 2022/03/21 20:53:00 Connecting to NA1DX (vara)... 2022/03/21 20:53:06 got a vara command I wasn't expecting: REGISTERED 2022/03/21 20:53:13 Disconnecting vara... 2022/03/21 20:53:19 Unable to establish connection to remote: connection failed 2022/03/21 20:53:20 QSX vara: 7100.000 same at several other gateways. Since I am not sure what component might be causing this, I wasn't sure where to report it. Other software in the clean BAP is working, wsjt, etc, except for js8call which it can not find on a full BAP install. Many thanks for your continuing efforts as I am excited when VARA will work for me. I am glad things are crawling forward as this has worked for some folks. Looking fwd to the first vara connection! :-)

[@ks2743]

I wonder if those who have had success with vara on the pi, with this beta project, in general, are *registered*, and those who have had this error are attempting connections with an *unregistered* version, ie no registration key entered for the vara. Yes or no, I will be watching for pat developments and beta releases towards a stable version. :-) BTW, regarding that JS8CALL issue I experienced yesterday: Using the BAP updater, it indicated that JS8CALL was, in fact, not installed. Odd. I installed (re-installed?) it and it is now working fine. I don't know why that happened, but I don't think it is related to the pat and vara issue with the *got a command I wasn't expecting*. Since I had mentioned the js8 issue, a followup seemed appropriate. Although... why the tangent? The versions of all the libraries and dependencies that a js8call install require (yesterday) may not have been the versions on my pi when I did the pat beta install. It may have found a useable version and proceeded anyway. Not being an active developer on the pat project, I'm not going to try to unravel whether this may be an issue or not. Just thought I'd mention it. Versions of dependencies have been known to sneak up and bite.

[@briandale9274]

@@ks2743 No, it had nothing to do with that. It had to do with the VARA command list they (PAT team) were using. They were using an old one that didn't include all of the current VARA commands and messages--you got the message regardless of registration status. Anyway, it's fixed with the current beta along with the bandwidth switching issue as of yesterday.

[@KB5WCK_Radio]

I get this too: got a vara command I wasn't expecting: REGISTERED. Any ideas how to fix this?

[@FunInSC]

@@KB5WCK_Radio update to the current Pat beta

[@KB5WCK_Radio]

@@FunInSC I have it. Works great!