Hi Robert, No problems. Please let us know how you go. 73, John On Mon, Jan 16, 2012 at 2:25 PM, Robert J. Krasowski <rkrasowski@xxxxxxxxx>wrote: > Thanks John for eplanaition. I do not knoe why I was thinking that TXdelay > is the one responsible for the problem. Will ask my friend on the boat to > make changes. We are talking daily on SSB. > > Thanks like always > Robert > KB2PNM > > Sent from my iPad > > On Jan 15, 2012, at 9:51 PM, John Douyere <vk2eta@xxxxxxxxx> wrote: > > Hi Robert, > > I am not sure I understood you properly but let me make sure there is no > confusion. > > The rxdelay parameter in the server is a delay added between the end of > receiving and interpreting the received data from the client and its > transition to TX. > > So it does not have any effect on the fact that the server is missing the > beggining of the client's data. > > What I think you describe is a too small value of the txdelay of the > client. > > I definitely recommend at least 1 or even 2 seconds to start with on the > client. Especially if the client runs on a fast machine or Android device. > > Please leave the TX delay at 1 on the server, and get the client to > increase its delay to 2 to start with. > > I am sure the exchange will be smoother. Timeouts on missed exchanges are > much more costly in terms of lost time than a slightly too long TX delay. > > Hope this helps, > > 73, John > > Robert Krasowski <rkrasowski@xxxxxxxxx> wrote: > > Hi all, > we have been successfully exchanging email with my friend on sailing boat. > One thing is problematic. With the setting of TXdelay=1, and modes > TX=PSK250R and RX=PSK250, server switch to receive too late and is catching > only the end of Client response. Not a killing problem but a problem that > cause delays. > Best Regards > Robert > KB2PNM > >