[Moon] another question abt 3XT1

[DF2ZC]

They will be zero, Wolfgang, if exactly this construction is being used with
the the "/" and the space between the callsigns. However "3XT1PJ4PA3CNX"
would work since it is 13 characters only. It is almost like in the old days
when your keyer memory had a particular size only and you had to try what is
possible to make the callsigns fit in.

There are more possibilities for a valid callsign exchange to work which
extend the time of the QSO exchange and still comply with QSO rules. 

vy 73 Bernd DF2ZC (JO30RN)
www.df2zc.de

____________________________________________
144 MHz EME NewsLetter:
www.df2zc.de/newsletter

144 MHz DXCC #21
144 MHz WAC

Kenwood TS 2000
2 x GU74b by LZ2US
4 x 2M18XXX 21 dBd full elevation



-----Original Message-----
From: moon-bounces at moonbounce.info [mailto:moon-bounces at moonbounce.info] On
Behalf Of dl5mae at wa7v.ampr.org
Sent: Dienstag, 6. November 2007 16:03
To: moon at moonbounce.info
Subject: Re: [Moon] another question abt 3XT1


Hi,

K1JT wrote:
>A JT65 plain-text message is truncated for only one reason: if the 
>transmitting operator tries to send a message with more than 13 
>characters, only the first 13 will be sent.


I am not sure, but what are the chances for i.e. PJ4/PA3CNX to work 3XT1 ??

vy 73 de dl5mae Wolfgang

_______________________________________________
Moon mailing list
Moon at moonbounce.info
http://www.moonbounce.info/mailman/listinfo/moon

 Please enter/update your standings: 
 http://www.vhf-dx.net/top.html

 When you decide to remain anonymous I may consider this unpolite and remove
you from the list