QSY Glitch
I connected with a station on the calling slot. I picked the QSY slot. The communications started for me to send the QSY, but I suspect the recipient either lost contact or just went off the air. After a few times of trying to get the QSY through, once my station didn't get any response, things just stopped. No more attempts to send the QSY. Nothing, it just sat waiting for something that was obviously not happening. I had to use the Abort button to terminate the link.
Shouldn't the QSY be more aggressive? If responses don't arrive within a reasonable amount of time I would expect the app to either retry or decide the partner had dropped for some reason and terminate the link. It shouldn't just sit and require operator intervention to terminate the link.
There could be some idle limiter that would ultimately have triggered and terminated the link. But the QSY clearly needs to have a tighter timing, and not just drop off. Fortunately, this doesn't happen often. But I have seen it more than once.
Doug / N3JXB
I would need to see a datastream traffic of this QSO to determin what went wrong. Usually the VARA modem waits and doing nothing if the other side is trying to send data. In nothing is heard for 60 seconds the link is terminated, I cant tell by your description if the QSY command did went through or not and where exactly things went wrong. To analyze this please :
Send me the section of the datastream. you can use the datastream log file or the CALLSIGN HISTORY module and get the QSO data.
Send the VarAC.log entries from that timefreame.
Just in general - there are no "retries of QSY". the VARA modem is an ARQ based - meaning delivery is gurenteed. If the QSY command did not went through - the VARA modem continue and try to deliver the message. if it was delivered and the other side did not respond - there is no need to resend the QSY invitation - it is 100% there. now it might be that propogation went bad and you didnt hear anythingf from the other side and VARA gave up after 60 seconds.
We will know more after we see the log.
73s
73s
Irad