Blue_on_Transparent.png

  • Home

  • Release updates

  • Download VarAC

  • Resources

    • Manuals (EN)
    • Manuals (NL/DL/SP)
    • RIG control file
    • FAQ

  • Forum

  • Contact

  • Members

  • Hall of fame

  • More

    Use tab to navigate through the menu items.
    • Facebook
    To see this working, head to your live site.
    • Categories
    • All Posts
    • My Posts
    Erik Finskas OH2LAK TF3EY
    Apr 09
      ·  Edited: Apr 09

    Transmit buffer remaining after QSO

    in Bugs - Fixed

    I have noticed in few QSO's with low signal levels or other issues with a lot of retries that the transmit buffer (Messages currently being sent) is not flushed after the other party has sent <DISC> successfully and the QSO has been finished.

    In these cases my transmit buffer had included my '73s' canned message including the <DISC> command. With the next QSO, being either the calling or called party. this remaining buffer has then been the first thing to be sent in the new QSO, eventually disconnecting it immediately.

    The only way to get around this now is to close VarAC and restart.

    I recall seeing a feature request of possibility of clearing the transmit buffer but could not find it now so I don't know the status of that or is it related to this finding.


    73,

    Erik OH2LAK TF3EY


    3 comments
    irad d
    Apr 09

    This is how it works :

    1. If you have a message in the Queue and/or a message currently being sent, and you are disconnected, then whats in the queue will remain there and the "currently being sent" message will move back to the queue also.

    2. If you reconnect to the same station, it will be sent again. This is for cases when you get disconnected before time, accidently or just because the link went down and you don't want to loose everything you typed.

    3. If you connect to a new station, the QUEUE is cleared.


    in all cases, you can of course manually clear the queue.

    If this is not how it is behaving then please LMK and I will try to dig in and see if there is a problem. I am not aware of such.


    Irad

    0
    Erik Finskas OH2LAK TF3EY
    Apr 14

    I was able to 'reproduce' the issue today with fading conditions QSO with NC3Z. Our QSO got eventually disconnected due to a timeout and a I had a message in the 'Currently being sent' -window, where it remained even I tried to clear the queue with the button.


    Next, whenwhen G3SJX called me and the connection was established, he got this message from NC3Z QSO first out. I was not able to clear it from the window with clear queue -button (VarAC restart of course would have cleared it)



    73, Erik OH2LAK TF3EY

    0
    irad d
    Apr 25

    Finally nailed it. (I hope HIHI)

    Will be fixed on V3.6.6.

    3 comments
     

    ©2022 by 4Z1AC, Irad Deutsch