I am trying to get the new Broadcast mode to work. I have upgraded to VARA v4.6.5. I can make normal connections and pings with stations. When I try and do a Broadcast to a station I have a good SNR to nothing happens.
I would like to thank Irad & everyone else for the excellent support! I can confirm that my issue with Broadcast mode not working was infact a Windows Defender Firewall issue. See the screen shot below. That said I am wondering if it would be possible to resolve the misleading error message that VARA HF posts? That would be KISS Interface Disabled (Winlink Priority). See the attached screenshot below.
According to the VARA HF KISS documentation KISS is automatically disabled when using a Winlink App. That is exactly what I see happening on my installation. I do have Winlink installed on my Windows 10 computer but of course I am not trying to run Winlink. That said I am running the new version of VARA HF.
It looks like I had installed Winlink but never used it. I have removed it and along with any of the folders/data. I am still getting the same error etc. Seems to me we should be able to find out what the process it that is running the the background and kill it /remove it. I have poked around with the task manager and don't see anything. I spend 2 hrs on this yesterday and did the suggestion of adding send/receive ports, I see there are some rules that allow TCP to use any/all with VarAC/Vara... I also have tried some of the other suggestions but has not worked. We need to find out what is causing this =Winlink Priority= to lock up the interface.
@AD0KI ... Yes, Tnx! That does indeed seem to work. I still have yet to see a broadcast message from anyone yet, and I have not been able to confirm that mine are being received by anyone as well. I am sitting on 40m and not seeing any beacons or CQ calls. I do see mine on PSKReporter however. I takes forever for the broadcast to finally get sent. A task for another day I am afraid.
FWIW I'm having similar problems as everyone else. I tried the few different fixes suggested here, but I'm not a power user so a lot of the TCP Port, Port 8100 Firewall stuff is totally over my head and I'm probably doing something wrong.
I made other test inverted port numbers for main port and kiss, so i put 8100 port for normal varac mode, and 8300 for kiss mode, now 8100 works in normal and 8300 not for kiss mode
Donno your architecture. Log says VarAC is trying to connect the VARA modem on the KISS port (default is 8100) and it fails to do so. Take it from there.
If you cant telnet the modem - its a network issue on your end. 4.6.5 is the same version we all work. some that faced an issue already sorted it out by allowing KISS port in their firewall - like the link I shared with you.
Windows install with rig control. VARA (4.6.5) and VarAC (6.2.4). frq: 14,105.00
"Broadcast send" does not activate TX, just says "Preparing to broadcast to G4..." in the log, after filling in the broadcast message window, Not working to specific call nor all.
Not sure if you say you did not decode a broadcast yet or you are unable to get one out. we will need some logs / screenshots and a better decsripiton.
I see the same behavior when I telnet to port 8100 and VARAHF. It shows connected. When I open VarAC, when VARAHF comes up, I get the same KISS Interface Disabled (Winlink Priority) message as well. I am running both programs as administrator and firewall has been disabled (no network issue at this point) and still see the same behavior. Is there a switch that could keep KISS active in VaraHF?
Mike,
my broadcast seems to work...have received and sent.....no acknowledgements returned to me, for the sent ones, though I have asked....kindly....
My two modems, monitor left and "main modem" right looks like this:
It says disconnected, no mention of interface disabled.
(I do not have winlink installed)
For what it is worth....
73, Henrik
I would like to thank Irad & everyone else for the excellent support! I can confirm that my issue with Broadcast mode not working was infact a Windows Defender Firewall issue. See the screen shot below. That said I am wondering if it would be possible to resolve the misleading error message that VARA HF posts? That would be KISS Interface Disabled (Winlink Priority). See the attached screenshot below.
73 - Mike - KB0FX
According to the VARA HF KISS documentation KISS is automatically disabled when using a Winlink App. That is exactly what I see happening on my installation. I do have Winlink installed on my Windows 10 computer but of course I am not trying to run Winlink. That said I am running the new version of VARA HF.
FWIW I'm having similar problems as everyone else. I tried the few different fixes suggested here, but I'm not a power user so a lot of the TCP Port, Port 8100 Firewall stuff is totally over my head and I'm probably doing something wrong.
I made other test inverted port numbers for main port and kiss, so i put 8100 port for normal varac mode, and 8300 for kiss mode, now 8100 works in normal and 8300 not for kiss mode
Here is how Henrik Bo Carisen sorted it out:
https://www.varac-hamradio.com/forum/main/comment/e4270dcb-3ae2-44ba-ba83-c521e562a725?postId=637ba963b360320012188da6
Please send a broadcast, wait for 1 minutes and attach here the VArAC.log output
Also me trying to make a all stns message in broadcast mode but not works and also to a desired station not working
Windows install with rig control. VARA (4.6.5) and VarAC (6.2.4). frq: 14,105.00
"Broadcast send" does not activate TX, just says "Preparing to broadcast to G4..." in the log, after filling in the broadcast message window, Not working to specific call nor all.
Have not received any broadcasts either.
73
OZ6F, Henrik
Not sure if you say you did not decode a broadcast yet or you are unable to get one out. we will need some logs / screenshots and a better decsripiton.