Il 21/05/2011 09:07, Rein Couperus ha scritto:
Yes, jPSKmail is controlling the RxID. At the moment the policy is that pings and beacons are sent in the default mode, which is PSK500R. All servers listen in PSK500R, so RSID is not necessary.
So this transmission don't need TXID ON in Fldigi.
Also, when a session is in progress and somebody sends a beacon with RSID on, and the client is in e.g. THOR22, it will switch back to PSK500R, and a resync is forced. This lengthens the connected session unncessarily.
This is a major problem. A client beacon switch another client mode. If this overlapp a server TX in connect mode, another server TX with TXID ON is needed. We perhaps need to force TXID off in Ping and Beacon?
Regards Franco Spinelli IW2DHW