Improvement suggestion rejected.

Not a bug but a requested improvement. Moved it to the right place.

It is being rejected as you posted the same big twice. This is your initial report - this post which I replied that the bug will be fixed in the next version. 73s

I have a fix for you to test. please send me an email to iradirad@gmail.com and I'll send you a link to download. 73s Irad

Ok. I get it now. Thank you for reporting and providing this data. Indeed broadcasts are blocked in when unattended links is behavior. As Advanced beacons are based on broadcasts it is affected. I will fix that.

I look on your screenshot and see at the top (VarAC log) a small hint about "ignoring PTT..." but I Cant see the rest. Please pull this from the log file to find out why.

I am happy you are happy :) And yes - I'll be at Ham-Radio - I'll have a lecture there at Saturday morning 10:00AM at Hall A2. But I will be there for the whole week and you can find me easily as I will probably wear a T-Shirt Saying "VarAC" :) Feel free to reach out and say Hello. 73s! Irad

I can not confirm this bug. When showing parked - it shows the time for which the VMails entered the Vmail box at the parking stations When showing relayed - it shows the time for which the VMail was sent from the station where it was parked. Can you show me a smoking gun somehow ? I was not able to duplicate and the code looks fine. Irad

Standard beacons works fine. The text you attached is for standard beacons showing the use of digipeaters and they work fine. Andy referred to advanced beacons.

Truth. I will make sure it is clear when setting this when using VARA FM. Advanced beacon does not work with AX25 protocol so the VARA modem cant handle it as such (AS25 packets has dedicated placed for digipeaters data). Advanced Beacons are a VarAC proprietary protocol over VARA. Sorry for the inconvenience.

* No issue detected regrading the one-time beacon. PTT Lock is respected also for one time beacons. * As to the other thing you mentioned - not Beaconing while in AWAY - no such thing. 95% precents of beacons on the air are when people are in "I'm away" state. as the one thing in common both your issues have is not Keying a PTT - I would suggest you check whats wrong in general with your PTT. Make sure you work with VARA 4.8.9 as the Advanced beacon had a bein in 4.8.8.

C# console applications (no Graphical UI) can be compiled to run on Linux natively. It is not the same for Win-Forms applications. they can't. WINE is your only option. VARA is the first obstacle to overcome. There are no plans to port VARA to Linux based on my knowledge. 73s.

Its not V11.2. its your windows screen SCALE. reduce the SCALE to bit all elements into screen.

Fixed. next version will includ that fix. on both ends 1, Better verification on the sending side that the Email address well structured.. 1. On the gateway side It will alert you on the log until you resolve it but it will continue to deliver other Email and will stay green.

For the sake of consistency - Some sort of message should appear to allow the user to know there was an attempt to look for old chats and that it is not an error. So have decided to present a "------ NO PREVIOUS CHATS WITH {{connected_to_callsign}} ------" in that case. 73s

Thank you for reporting. problem simulated. I will fix that.

99% of beacons are away beacons. no real need to have a specific flag. most users let VarAC handle the away automatically. meaning that if you do not touch VarAC automatically set the away status. There is no many reasons for people to play with VarAC unless they are engaging in QSO or calling CQ. all other tasks are short term and sporadic. Do in the end - most beacons you try to connect you will find they are AWAY. I guess you noticed it yourself so it would be a waste of emission to tell everyone the obvious. I do use Beacons to connect friends and leave them VMails. 73s Irad

Thank you Ivan!

Meir you keep preaching over and over for a feature we have for 2 years. please read Gary's comment to you providing you with the screenshot from the VarAC cluster manual. Locking between VarAC instances is what we provide and it is a great solution. When one VarAC instance is busy, all other instances wait. No need to get down to what instances uses what screw in the rig. its a niche usecase with no real values. Closing thread.

Thank you for reporting. I was able to simulate. I will contact the VARA author to see what would be a best fix. and I will keep you updated. Irad