Yes, THOR4 takes more than a minute to get a connect request through to
There are 2 solutions I have tried:
* Connect in THOR22 or THOR8, and use THOR4 as a last resort mode when you
don't want connections to break whatever happens....
* Give the server a 2-minute chance to get the THOR4 request. This function
was broken in 1.5.0, and I repaired it in 1.5.1. tried it on PI4TUE...
What I did was set the modes in freq.txt to PSK500R,PSK500R,PSK500R,THOR4,THOR4.
The server will scan these modes, and you can still connect in other modes using TXID....
So the second method lets you connect in THOR4 even if the server does not
receive the RXID correctly....
You still have to start the THOR4 request early in the 3rd minute though, it won't work
Anyway, my tests have shown this lets you dig even deeper into the QRM.....
The ~RESETRECORD command must be written into the normal text input field..
I also forgot to mention the new CONNECT screen, which lets you set both TX and RX
modes for the session....
YOU CAN NOT USE MORE THAN 7 MODES IN THE MODE TABLE !!
But that would not make sense anyway, I normally use max. 5 modes.
I AM USING THE NEW SERVER AND CLIENT 1.5.6 AND 1.5.1
I CANNOT START A CONNECTION THE SERVER IN THOR 4
BEFORE IT HAS A CHANCE TO GET STARTED TE SERVER SWITCHES
BACK TO THE DEFAULT SPEED OF THOR 22
HE WE HAVE TWO CHOICES ONE ALLOW THE SERVER TO DEFAULT TO THOR 4 SO IT IS "READY"
FOR THE WORST OF CONDITIONS ALLOWING THE CLIENT TO JUDGE WHAT THE DEFAULT SPEED SHOULD BE
OR CHANGE THE RETURN TO DEFAULT MODE IN THE SERVER TO ALLOW TIME FOR A CONNECTION IN THOR 4
OTHERWISE THE ONLY FUNCTION FOR THOR 4 IS A LAST RESORT AN USUALLY WHEN THOR 8 WAS THE
SLOWEST MODE DID NOT WORK WELL AS WHEN CONDITIONS USUALLY FAIL THAT BAD IT WOULDN’T MAKE A LOT OF DIFFERENCE
LASTLY WHERE IS THE RESET RECORD COMMAND ?
DAVID KF4WBS / KF4WBS