Hello Rein,
I have the following setup:
Server:
Ubuntu 9.10
pskmail server 0.9.29
fldigi 3.13BH compiled from source - only source mod is to eliminate
date coding on log file (I'll work on PSK500 after everything else is solid)
Client:
Ubuntu 9.10
jpskmail 0.4.0
fldigi 3.13BH compiled from source - no source code mods
When I start pskmail_server, server says "MYMODEnow: PSK500" but fldigi
switches to BPSK250. Anyway, I have the block length in the client set
to 0 for "server default". I set the client to BPSK250 and connect.
Everything works fine. The link is solid so the server shows "PSK250 T=0
LQ=-2 BL=6" for the whole session. To impair the path I just pull the
receive audio jack out of the client for one poll of the server. The
client doesn't respond and the server sets the retry mode to PSK250R. I
plug the jack back in. At this point the server is in PSK250R mode and
the client is in PSK250. The server sends an RSID and a poll. The client
does not change to PSK250R upon RSID reception. The server then
downshifts to PSK125R mode, sends another poll. The client still does
not change modes. Eventually the server disconnects. After
disconnection, the server stays in the PSK125R mode.
The two main problems I am experiencing are: 1) fldigi in the client is
not changing modes to match the server, and 2) the server stays in the
downshifted retry mode and does not default back up to be ready for the
next connection.
I hope I am understanding how the RSID works. I have tried a couple of
block lengths in jpskmail to try different mode profiles but saw no
change from the above description. I have looked around in the client
fldigi configuration to see if RSID is disabled, but have found nothing.
I would appreciate any feedback on my feedback :>)
73,
Fred - WB5CON
Rein Couperus wrote:
The new robust pskmail server (0.9.29) is now ready for alpha testing. Together
with the jpskmail-0.4 client and fldigi-3.13BG it builds a system which is
extremely robust, and can be used under a broad range of band conditions.
What is new?
The server uses RSID technology to change modes. The client and server have
been changed to handle RSID in such a way that they work together efficiently.
Transmission modes are changed automatically depending on channel quality in
such a way that maximum speed is combined with optimum robustness. This is
achieved by a mode switcher which constantly monitors the link, and changes to
a more robust mode when the channel stalls, either because of qrm,qrn or qsb.
The server offers various mode profiles which can be set from the client. Each
profile has 3 modes, and the server will automatically switch between them, and
also adjust the block length by looking at the number of errors on the link.
The following 9 profiles are available:
9: PSK500 PSK500R PSKR125
8: PSK500 PSK250R PSKR125
7: PSK500 MFSK32 PSKR125
6: PSK500 THOR22 PSKR125
5: PSK250 PSK250R PSKR125
4: PSK500R MFSK32 PSKR125
3: PSK500R THOR22 PSKR125
2: PSK250R PSK125R PSKR125
1: MFSK32 MFSK16 PSKR125
0: Use server default
The client can choose the profile by setting the Blocklength variable through
the preferences dialog.
This mode table is preliminary, lot of testing will be needed to fix the most
effective combinations. The ones we use now are the ones I prefer :)
The server can be connected in any mode (PSKR125, THOR22, PSK500... etc.)
The new test software is available at
http://hermes.esrac.ele.tue.nl/pskmail/alpha
Fldigi and client packages are available for windows and linux.
At this moment only PI4TUE is running the new test server, but i hope there
will be more soon. Using the new server I can now work PI4TUE with 1 Watts (20
km, 18105 kHz), on 30 meters I need 10 Watts.
I hope some of you can do some tersting, and let me know of any quirks....
73,
Rein PA0R
