Hi Franco,
Two news, one good one not so good:
1. The mode change seems to be happening as it should, since I can see
in the log below that some requests were made in PSK250R and others in
PSK500R.
When you change the mode in pskmail, it does not change the mode in
Fldigi immediately. The mode change in Fldigi happens just before the
connect request (in fact just before any transmission).
2. The not so good news is that although IS0GRB-3 is receiving your
connect requests properly it is not responding for some strange
reason.
I have copied Roberto in this email to see if can find out why.
For connections to SM0RWO you may start with a more robust mode and
let the server adjust it upwards automatically. Here is the list of
modes, sorted from most robust to the fastest that trigger the
automatic speed adjustment by the server:
THOR8 MFSK16 THOR22 MFSK32 PSK250R PSK500R PSK500
I would start with MFSK32 or even THOR22 for connections at longer
distances (SM0RWO for example) in these conditions (time and
propagation). But for IS0GRB-3 I think PSK250R is robust enough.
So you are almost there. Let's see what Roberto can find out about the
server not responding.
Good luck,
73, John
----- Extract of log from IS0GRB-3 -----------------------
#Your beacon with it's reply as received by IS0GRB-3 (see SM0RWP log below
too)
<SOH>00uIW2DHW:26 !4539.44N/00910.28Eyjpskmail 0.5.2 9CFA<EOT>
<SOH>QSL IW2DHW de SM0RWO E7EE<EOT>
#Your connect request to IS0GRB-3 using PSK500R - should have resulted
in a connect reply from the server
<SOH>00cIW2DHW:1024 IS0GRB-3:24 6FD56<EOT>
#Damaged frame
<SOH>00cIWW:102[t R tq; ptecCTaTaTilt
#Your connect request to SM0RWO using PSK500R as received by IS0GRB-3
<SOH>00cIW2DHW:1024 SM0RW0:24 6A106<EOT>
#Your connect request to SM0RWO using PSK250R as received by IS0GRB-3
<SOH>00cIW2DHW:1024 SM0RW0:24 5A046<EOT>
#Your connect request to SM0RWO using PSK250R as received by IS0GRB-3
<SOH>00cIW2DHW:1024 SM0RWO:24 56F4D<EOT>
#Your connect request to IS0GRB-3 using PSK250R - should have resulted
in a connect reply from the server
<SOH>00cIW2DHW:1024 IS0GRB-3:24 5FC16<EOT>
#Rein's new beacon and it's reply as received by IS0GRB-3
<SOH>00uPA0R:6 -S6J%45O y!2732<EOT>
<SOH>QSL PA0R de PI4TUE 555F<EOT>
--------- extract of log from SM0RWO ------------------
#Your beacon and it's reply from SM0RWO
RX (2010-08-19 19:32Z): <SOH>00uIW2DHW:26 !4539.44N/00910.28Eyjpskmail
0.5.2 9CFA<EOT>
TX (2010-08-19 19:32Z): <US><SOH>QSL IW2DHW de SM0RWO E7EE<EOT><EOT>-
#One of your connect requests to SM0RWO but got damaged, the others
didn't make it at all (pleaase adjust the mode down)
RX (2010-08-19 19:35Z): <SOH>00cIW2DHW:1024 SM0RW4 heaeD<ESC>]keX
co<FS>iaIfLde Zi<DC2>
#Your connect request to IS0GRB-3 using PSK250R as received by SM0RWO
<SOH>00cIW2DHW:1024 IS0GRB-3:24 5FC16<EOT>
#Rein's new beacon and it's reply as received by SM0RWO
RX (2010-08-19 19:40Z): <SOH>00uPA0R:6 -S6J%45O y!2732<EOT>
RX (2010-08-19 19:47Z): <SOH>QSL PA0R de PI4TUE 555F<EOT>
__________ Informazioni da ESET NOD32 Antivirus, versione del database
delle firme digitali 5380 (20100819) __________
Il messaggio è stato controllato da ESET NOD32 Antivirus.
www.nod32.it
