Instance 1 is the Email handler. If someone connects to it and sends an email through it, Instance 1 sends the <ER>. If someone connects to Instance 2 and sends email, Instance 2 doesn't send the <ER> at the end of the process.
I have PTT Lock in the Cluster settings tab checked to solve a temporary problem. It works fine if one instance is connected and the other isn't doing anything. PTT is disabled as long as the other instance is connected/transmitting and is enabled when both are free.
If instance 2 is handling a contact, instance 1 is locked. But if you change bands in instance 1 during the contact on 2, it counts down the beacon, then pauses it as I would expect. But when 2 is clear it does not release the PTT disabled though the warning text above it does clear. I have to uncheck the PTT disabled manually.
The reason that I am using the PTT Lock is because I need to move one of my HF antennas, until I can make that happen, there is minor interference between the two antennas and radios. I have been trying to eliminate possible causes for the PTT Disabled lockup. When I originally reported this problem, this was the configuration:
Instance 2 – HF – Launched 1st – email handler – PTT Lock enabled
Instance 1 – HF – Launced 2nd – PTT Lock enabled
Instance 3 – 2m FM – Launched 3rd – PTT Lock NOT enabled
Thinking that maybe it was the instance numbering and the launch sequence, I brought each up individually and renumbered them.
Instance 1 – HF – Launched 1st - email handler
Instance 2 – HF – Launced 2nd
Instance 3 – 2m FM – Launched 3rd
I bring them up one at a time with a minute or two between launches. As I have them start beaconing at launch, I let each complete a beacon cycle before launching the next one.
It is always the same instance that has the problem, the 2nd launched instance, no matter what the instance number is.
I have run in debug mode for hours, and it doesn’t happen. Turn debug off (because it really crowds the data stream) it will happen randomly. There is never a common factor in the operating tempo.
If I’m in a QSO on #1, PTT Locks on #2 as it should. Most of the time it releases. Sometimes if I’m in a QSO on #1 and someone attempts to connect to #2 PTT doesn’t unlock after the QSO, sometimes it does release the lock.
Sometimes I will be away and I come back and #2 is locked with no one connected to the station.
I have turned debug back on for both #1 and #2 and will leave it on till something happens and upload the entire log.
Hello, I'm downloading from official site.
MS defender blocks before download completes. The detection is Trojan:win32/wacatac.B!ml. Is this a known false positive? If yes, is there a checksum or updated installer? Thank you! 73/Steve
VarAC is thoroughly scanned with professional-grade antivirus and security tools before every release, following industry-standard practices used across the high-tech industry.
If you encounter an antivirus alert, it is a false positive. You can safely proceed with the installation.
73s!