Replies: 6 comments 8 replies
-
|
F4GMU: |
Beta Was this translation helpful? Give feedback.
-
|
Hi F4GMU |
Beta Was this translation helpful? Give feedback.
-
|
KD2ROS: |
Beta Was this translation helpful? Give feedback.
-
|
IC-7100, Vara FM/HF, packet with direwolf (build-a-pi) |
Beta Was this translation helpful? Give feedback.
-
|
9V1MH/VK2AMH/YF2AAH Trying a few things - IC-7610, X-6100, IC-705, TX-500, KX-2, KX-3 - with Mobilink, Signalink (USB), DigiRig and of course the inbuilt interfaces in the 705, 7610 and x6100 - will let you know how it goes Be patient but this is a great project and if we can get all the other software to run as well (FLDigii, WSJT-X, JS8Call etc) then it does exactly what a lot of us want - not having a *nix Vara option means we have all gone to a tablet/miniPC and abandoned the RPi. Would also like to know if you are looking at the Pi 64bit OS for use on a Pi4/Zero2W? |
Beta Was this translation helpful? Give feedback.
-
|
Hey Matt, sorry I didn’t see the question at the end of your post. I’m interested in how this might run on a Pi0 2W, but I’m not confident that it will run well enough to be usable. I’ll let you know if I get a Pi0 2W to play with. Best of luck with your setup too |
Beta Was this translation helpful? Give feedback.
-
|
I am using Raspberry PI 4 8 gig 128 gig Micro SD, 64 bit buster, over clocked to 1500, TIMEWAVE Navigator attached to a USB 3 hub connected to the Pi in the USB 3 slot. The Navigator is connected to an Elecraft K3. Under Buster all native Linux software works very good. been using WSJT-X for a couple of weeks no problems. Installed Winlink Express and VARA HF, FM, Sat. software runs OK. CAN NOT GET THE COM PORTS IN VARA HF WINLINK SESSION TO MAP TO THE TTYUSBX PORTS. I have made links using ln, edited the .reg file edited the registry regedit. nothing works. IF i don't have RIG control and no audio out, so what if the software runs. |
Beta Was this translation helpful? Give feedback.
-
|
same issue IC705 rpi4 and everything else works but winlink-VARA-HF same as this past comment (CAN NOT GET THE COM PORTS IN VARA HF WINLINK SESSION TO MAP TO THE TTYUSBX PORTS. I have made links using ln, edited the .reg file edited the registry regedit. nothing works.) I want to be clear this very specific to -winlink and Vara-HF-PTT - it is the only non working (I assume a winlink issue with wine) FM and VarAC and VARChat HF all work fine. (similar but I dont think the same .. could be a ocx issue #17) |
Beta Was this translation helpful? Give feedback.
-
|
I have the very same issue. My set up is an Elecraft K3 a Timewave Navigator and a Raspberry Pi 4 8 gig with dual touch screens. Everything that is native Linux which I have set up works fine. I have been using WSJT-X for several weeks with very little too no trouble. Everything that runs through wine does not work. I can not get a link from the windows com or USB ports to the actual device in Linux. I have tried the same things you have, regedit, ln links, patching the reg file etc. For me the Winlink and VARA apps are the most important. This issue however will effect any windows based com application. WSJT-X was written so that it could be compiled for both Windows and Linux, the same needs to be done for Winlink and VARA. Nothing beats running native. II have the same problems with my logging software from N3FJP. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, my email alert hasn't been updating me on the discussions page, just the issues trackers - sorry for the delay.
I'm also sorry for your disappointment with the script. This gihub page is made for free/opensource collaboration though, so if you find a solution before I do, let me know. Best of luck |
Beta Was this translation helpful? Give feedback.
-
Good thinking, but that bug was fixed by wine-mono's author and all mono's going forward have that function implemented. |
Beta Was this translation helpful? Give feedback.
-
|
I may not have made my self clear. I DO get all audio out of the PI to the modem a TIMEWAVE Navigator ergo audio to the RIG. I DO NOT however get Rig control through to the Navigator. from the PI. My Pi has since died and I have gone back to my windows machine. Same problem. Before implementing the Pi my windows machine worked flawlessly. I need to find out why my Pi died. |
Beta Was this translation helpful? Give feedback.
-
|
Hello All
Earlier I have posted that on my ic7100 all the modes were working with
patmenu and rms-express.
That was with the version where the icons were on the desktop.
The version with the icons in the menu is not working so well for me.
For the vara-hf it works for me with patmenu. But when I try to work
vara-fm with patmenu it is starting and connecting but not always there is
an audio signal. And because of that, I can`t make a properly connection.
Listening to another radio, I am getting a carrier, but there is no audio.
The option to work with vara fm is to use rms-express that works well for
me. But the vara HF can't find the com port under rms-express and so I get
an error with no connection to the ic 7100.
Conclusion: vara hf works for me with patmenu and vara-fm works for me with
the use of rms-express.
That is not handy, and I hope that someone knows a solution that it will
work again with both or with patmenu or rms-express so changing isn't
necessary anymore.
I am using debian bullseye 32bit and have also tried 64 bit on a raspberry
pi 4. Both debian`s gave the same problems.
73 Ron
PD7RON
Op do 18 aug. 2022 om 20:49 schreef Wes-KF7BWS ***@***.***>:
… I have the very same issue.
My set up is an Elecraft K3 a Timewave Navigator and a Raspberry Pi 4 8
gig with dual touch screens. Everything that is native Linux which I have
set up works fine. I have been using WSJT-X for several weeks with very
little too no trouble.
Everything that runs through wine does not work. I can not get a link from
the windows com or USB ports to the actual device in Linux. I have tried
the same things you have, regedit, ln links, patching the reg file etc.
For me the Winlink and VARA apps are the most important. This issue
however will effect any windows based com application.
WSJT-X was written so that it could be compiled for both Windows and
Linux, the same needs to be done for Winlink and VARA. Nothing beats
running native. II have the same problems with my logging software from
N3FJP.
—
Reply to this email directly, view it on GitHub
<#25 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALDYUH3QORT7EJKKVK6NHELVZ2AS3ANCNFSM5NNWWBQQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
This might be from changing to a different version of box86 in the newer version of the script. It is always possible to go to an older version of the script using the Clock icon on the main page, then going to the script, then going to 'file', then going to 'RAW', and getting a link to download (here's a link to a "raw" version of I think the script that put the icons on the desktop: https://raw.githubusercontent.com/WheezyE/Winelink/5d4d6f83023eb9e7b02ec783a9b3643c3cff8523/install_winelink.sh ) There's a bug in versions of box86 after Dec 2021 related to VARA not using TCP/IP correctly that is preventing me from updating it in future iterations of the script. I have to find that bug and see if Seb can fix it before I can try to squash other bugs. |
Beta Was this translation helpful? Give feedback.
-
I just wanted to catalog which hardware setups we all have working with RMS Express + wine + wine-mono + box86.
I'll go first. KI7POL:
FT-891+dummyload, RPi4(4GB): VARA HF, VARA FM, VARA Chat, and ARDOP with PTT & Channel Selection CAT control.
Beta Was this translation helpful? Give feedback.
All reactions