Could there be a delay in sending the I'm Away message, such as 10 seconds (just an example).
My reasoning behind this is in my case my radio and PC are set up behind me, I sometimes hear the connection being made to me, but the I'm away message is sent before I am able to turn around, cancel it, and respond accordingly, as I'm sometimes available for a QSO.
Regards
DAVE
I know what you mean and I have experienced it quite often.
Yet we want also to provide the other side a feedback about you being or not being there and a delay will mislead the other side.
To balance both needs, I believe its best to be left as is....
73s
Here's a further thought on this, immediately after sending the I'm away message the S/N is sent, could these not be reversed, as it may give enough time to cancel the I'm away as a queued message and begin a QSO.
This can't be done. I'll explain why.
A report can be sent once you receive something from the other side.
So your partner can't send you a report if you don't send them something first.
On the other end, you can't send them a report until they send you something first.
So this is why it is built this way:
Step 1: Side A: Sending an away message.
Step 2: Side B: Able now to send a report based on the away message
Step 3: Side A: Able now to send a report back based on the packet received on step 2.
I hope it helps
Irad
Would it not be beneficial then to send an automatic "Connected to <Callsign>" and then a signal report, this would allow time to cancel default away message and also help with pinging stations to get confirmation of "Connected to" instead of an away message. Only a thought Irad, you are the master at this, I wish I could code then I would understand more.
This will only extend the cycle with additional one more message (the "conneced to")... As for PINGS - next version will deal with in elegantly. the pinged party know it is being pinged and it will not send any away/welcome message.
great.
DAVE