wsjt-devel

[wsjt-devel] Q65 Pileup Feature Request

[Lance C. W. <w7...@bi...>]

This request is for a feature that would (I think) be primarily of use 
during pileup situations during DXpeditions. So Q65 PILEUP makes it the 
logical place for it. As I have been suggesting for years, it would be 
EXTREMELY HELPFUL and make DXpedition operations so much more 
productive, if there could be an indicator when a station is receiving 
during the last receive sequence. When multiple stations are calling at 
the same time (especially during common moonset windows), a lot of time 
can be wasted by cycling through the list of all the callers and trying 
to reply to each one to see if there happens to be any reciprocal 
propagation with any of them. By the time one tries responding to 10 or 
12 callers, plus delays in running out to aim the antenna, considerable 
valuable common moon time has been used up :-(  I don't profess to have 
any idea how the system works, but here are my suggestions from a 
DXpeditioner's point of view:

1. In Q65 PILEUP, apparently there is some way to transmit "R" with the 
callsigns and grid TX3) and for that information to be received by the 
other station.

2. If a station could optionally turn on the feature, perhaps they could 
send an * (or some other symbol or letter or number) when they receive a 
yellow spike (perhaps with some adjustable threshold above the 
background noise) during their previous reception period.

3. The DXpedition station could receive the new TX3 message with the * 
(or whatever instead of the R), and know that he could reply with a 
standard TX3 message and have it received by that caller. Of course, 
reception of that * message should not engage the AUTO SEQUENCE.  If the 
caller stops receiving a yellow spike, the program would go back to 
automatically sending TX2.

The HUGE advantage would be that the DXpedition station would be able to 
identify stations that have the capability for a reciprocal contact! 
Today, for example, I spent a lot time replying to a number of different 
stations who never received any decodes from me at all when I tried to 
reply to them :-(

MNI TNX for your kind consideration!  VY 73, Lance  at H40GJ

-- 
Lance Collister, W7GJ (ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ, H40GJ)
P.O. Box 73
Frenchtown, MT   59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL: http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11 - 6m DXCC #815 - FFMA #7

Interested in 6m EME?  Ask me about subscribing to the Magic Band EME
email group, or just fill in the request box at the bottom of my web
page (above)!

Re: [wsjt-devel] Q65 Pileup Feature Request

[Charles S. <g3...@gm...>]

Hi Lance

I'll leave it others to comment on the first part of your request

It seems from your last point that you suffer a lot from 'blind calling'.
This was a real problem during the early days of Superfox mode, and was
overcome by code that prevents a 'hound' from transmitting at all until
they have managed to decode the signal from the fox.

The code for this exists already, and could perhaps be applied to Q65
pileup at some point if you felt this would at least partially alleviate
your problem.

In the meantime, perhaps you could ask your followers to just adopt the
discipline of not calling you unless they have decoded you first, in
everybody's interest.

73

Charlie DL3WDG

On Tue, 19 Aug 2025 at 00:08, Lance Collister, W7GJ via wsjt-devel <
wsj...@li...> wrote:

> This request is for a feature that would (I think) be primarily of use
> during pileup situations during DXpeditions. So Q65 PILEUP makes it the
> logical place for it. As I have been suggesting for years, it would be
> EXTREMELY HELPFUL and make DXpedition operations so much more
> productive, if there could be an indicator when a station is receiving
> during the last receive sequence. When multiple stations are calling at
> the same time (especially during common moonset windows), a lot of time
> can be wasted by cycling through the list of all the callers and trying
> to reply to each one to see if there happens to be any reciprocal
> propagation with any of them. By the time one tries responding to 10 or
> 12 callers, plus delays in running out to aim the antenna, considerable
> valuable common moon time has been used up :-(  I don't profess to have
> any idea how the system works, but here are my suggestions from a
> DXpeditioner's point of view:
>
> 1. In Q65 PILEUP, apparently there is some way to transmit "R" with the
> callsigns and grid TX3) and for that information to be received by the
> other station.
>
> 2. If a station could optionally turn on the feature, perhaps they could
> send an * (or some other symbol or letter or number) when they receive a
> yellow spike (perhaps with some adjustable threshold above the
> background noise) during their previous reception period.
>
> 3. The DXpedition station could receive the new TX3 message with the *
> (or whatever instead of the R), and know that he could reply with a
> standard TX3 message and have it received by that caller. Of course,
> reception of that * message should not engage the AUTO SEQUENCE.  If the
> caller stops receiving a yellow spike, the program would go back to
> automatically sending TX2.
>
> The HUGE advantage would be that the DXpedition station would be able to
> identify stations that have the capability for a reciprocal contact!
> Today, for example, I spent a lot time replying to a number of different
> stations who never received any decodes from me at all when I tried to
> reply to them :-(
>
> MNI TNX for your kind consideration!  VY 73, Lance  at H40GJ
>
> --
> Lance Collister, W7GJ (ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX,
> 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ,
> S79GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ, H40GJ)
> P.O. Box 73
> Frenchtown, MT   59834-0073
> USA
> TEL: (406) 626-5728
> QTH: DN27ub
> URL: http://www.bigskyspaces.com/w7gj
> Skype: lanceW7GJ
> 2m DXCC #11 - 6m DXCC #815 - FFMA #7
>
> Interested in 6m EME?  Ask me about subscribing to the Magic Band EME
> email group, or just fill in the request box at the bottom of my web
> page (above)!
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Q65 Pileup Feature Request

[Jim B. <k9...@au...>]

On 8/18/2025 8:32 PM, Charles Suckling via wsjt-devel wrote:
> It seems from your last point that you suffer a lot from 'blind 
> calling'.  This was a real problem during the early days of Superfox 
> mode, and was overcome by code that prevents a 'hound' from transmitting 
> at all until they have managed to decode the signal from the fox.

Hi Charles,

To understand Lance's request, you must understand his operating 
conditions. He does 6M moon-bounce Dxpeditions to remote places, which 
requires very low noise, high power, and big antennas. To minimize his 
need for power, which translates to minimizing the cost of buying and 
transporting fuel over oceans, and then to remote locations where 
there's no noise, he INVITES blind callers. This is a method of 
operation he devised years ago. He's currently somewhere in the South 
Pacific, don't remember where.

This is his website.  https://www.bigskyspaces.com/  Scroll down to see 
his instructions to callers.

I would encourage the development team to take his request seriously and 
do your best to accommodate it.

73, Jim K9YC

Re: [wsjt-devel] Q65 Pileup Feature Request

[Lance C. W. <w7...@bi...>]

Hello Charlie et al,

Yes, I invite "blind callers" for the following two reasons:

1. I need their calls to be decoded to populate the Q65 PILEUP ACTIVE 
STATIONS LIST ("ASL") and provide the added sensitivity when it comes 
time to participate in a contact exchange with them.

2. Due to the nature of Faraday Rotation on VHF EME, there may appear to 
be "one way propagation" for extended periods of time. If people waited 
until they copied me before calling, I may have lost the opportunity for 
a complete Faraday Rotation cycle to receive them and add them to the 
ASL. Since many of the callers are horizon-only stations utilizing 
narrow ground gain antenna lobes, there are by nature very limited 
windows during which to complete with them; having them delay the start 
of the contact until they decode me further reduces the available time 
for a contact exchange to take place.

I am sure you can appreciate the huge difference between this type of 
weak signal contact and the essentially instantaneous strong signal 
reciprocal contacts on HF using Fox/Hound or Superfox.  On VHF EME, it 
is quite an advantage to be able to determine which station(s) to engage 
in a QSO that might be able to provide a quick reciprocal type of 
contact. Currently, the only way to do this (without resorting to the 
internet to have people report "I am decoding you now", which 
essentially makes the contact invalid) is to try to work through the 
pile of callers, replying to each in turn to see which ones may be 
capable of completing a quick "reciprocal" type of contact with you.  
Thanks to the ASL, it may be that some of the callers to whom you reply 
may actually receive your message, although you won't know it until you 
receive "RRR" from them at some later time.  However, the best success 
rates involve choosing the proper QSO partners with which you have the 
highest probability of making a quick reciprocal contact thinning out 
the number of callers.

It struck me that the Q65 PILEUP mode may finally actually provide the 
means to transmit this information! I thought that there might be room 
for this information the way the R report is inserted in TX3. I wonder 
if the program could automatically send a message in place of TX2, but 
similar to TX2 except with some other character (perhaps just a dash 
instead of a space) to indicate that the station copied a yellow spike 
during the receive cycle immediately preceding their transmit cycle. 
This would be in place of TX2, and would revert to the standard TX2 if 
no such yellow spike were received. It would not affect the AUTO 
SEQUENCE of either station (other than the current action upon receipt 
of a TX2 message) but would simply be displayed as a received message. 
But it would be a sign to the DXpedition (or other) station to "please 
select me next because I am copying your trace".  I suspect that the 
activation of this feature should be manually turned on by the callers, 
although I guess it wouldn't hurt to have it running all the time 
(unless it would add significant processing to the computers on one or 
both ends).

Perhaps there are significant impediments that would make something like 
this impractical. However, after hours of trying to answer callers one 
at a time who don't copy at the time you tried them, I think it would be 
a tremendous improvement if it were in any way possible!

Thank you for your kind consideration, and for the HUGE advance that Q65 
PILEUP provides. It is already the standard on 6m EME! VY 73, Lance

On 19 Aug 2025 03:58, Jim Brown via wsjt-devel wrote:
> On 8/18/2025 8:32 PM, Charles Suckling via wsjt-devel wrote:
>> It seems from your last point that you suffer a lot from 'blind 
>> calling'.  This was a real problem during the early days of Superfox 
>> mode, and was overcome by code that prevents a 'hound' from 
>> transmitting at all until they have managed to decode the signal from 
>> the fox.
>
> Hi Charles,
>
> To understand Lance's request, you must understand his operating 
> conditions. He does 6M moon-bounce Dxpeditions to remote places, which 
> requires very low noise, high power, and big antennas. To minimize his 
> need for power, which translates to minimizing the cost of buying and 
> transporting fuel over oceans, and then to remote locations where 
> there's no noise, he INVITES blind callers. This is a method of 
> operation he devised years ago. He's currently somewhere in the South 
> Pacific, don't remember where.
>
> This is his website.  https://www.bigskyspaces.com/  Scroll down to 
> see his instructions to callers.
>
> I would encourage the development team to take his request seriously 
> and do your best to accommodate it.
>
> 73, Jim K9YC
>
>
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

-- 
Lance Collister, W7GJ (ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ, H40GJ)
P.O. Box 73
Frenchtown, MT   59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL: http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11 - 6m DXCC #815 - FFMA #7

Interested in 6m EME?  Ask me about subscribing to the Magic Band EME
email group, or just fill in the request box at the bottom of my web
page (above)!

Re: [wsjt-devel] Q65 Pileup Feature Request

[Charles S. <g3...@gm...>]

Hi Lance

I understand your reason for wanting blind callers.  I had not quite
understood your comment at the end of your first email, but all is now
clear thanks.

We  used to use a somewhat similar scheme when Rex VK7MO was touring
Australia with a small dish on 10GHz,  The interested stations were
allocated a single tone frequency beforehand, As soon as someone had
decoded Rex, they would transmit a single tone and that would tell Rex who
was copying him, and he would then call them, or call them next.  I think
we got up to about 6 stations in the end with this scheme. With GPS locked
systems and CFOM  Doppler control it worked well.

73

Charlie DL3WDG






On Tue, 19 Aug 2025 at 07:31, Lance Collister, W7GJ via wsjt-devel <
wsj...@li...> wrote:

> Hello Charlie et al,
>
> Yes, I invite "blind callers" for the following two reasons:
>
> 1. I need their calls to be decoded to populate the Q65 PILEUP ACTIVE
> STATIONS LIST ("ASL") and provide the added sensitivity when it comes
> time to participate in a contact exchange with them.
>
> 2. Due to the nature of Faraday Rotation on VHF EME, there may appear to
> be "one way propagation" for extended periods of time. If people waited
> until they copied me before calling, I may have lost the opportunity for
> a complete Faraday Rotation cycle to receive them and add them to the
> ASL. Since many of the callers are horizon-only stations utilizing
> narrow ground gain antenna lobes, there are by nature very limited
> windows during which to complete with them; having them delay the start
> of the contact until they decode me further reduces the available time
> for a contact exchange to take place.
>
> I am sure you can appreciate the huge difference between this type of
> weak signal contact and the essentially instantaneous strong signal
> reciprocal contacts on HF using Fox/Hound or Superfox.  On VHF EME, it
> is quite an advantage to be able to determine which station(s) to engage
> in a QSO that might be able to provide a quick reciprocal type of
> contact. Currently, the only way to do this (without resorting to the
> internet to have people report "I am decoding you now", which
> essentially makes the contact invalid) is to try to work through the
> pile of callers, replying to each in turn to see which ones may be
> capable of completing a quick "reciprocal" type of contact with you.
> Thanks to the ASL, it may be that some of the callers to whom you reply
> may actually receive your message, although you won't know it until you
> receive "RRR" from them at some later time.  However, the best success
> rates involve choosing the proper QSO partners with which you have the
> highest probability of making a quick reciprocal contact thinning out
> the number of callers.
>
> It struck me that the Q65 PILEUP mode may finally actually provide the
> means to transmit this information! I thought that there might be room
> for this information the way the R report is inserted in TX3. I wonder
> if the program could automatically send a message in place of TX2, but
> similar to TX2 except with some other character (perhaps just a dash
> instead of a space) to indicate that the station copied a yellow spike
> during the receive cycle immediately preceding their transmit cycle.
> This would be in place of TX2, and would revert to the standard TX2 if
> no such yellow spike were received. It would not affect the AUTO
> SEQUENCE of either station (other than the current action upon receipt
> of a TX2 message) but would simply be displayed as a received message.
> But it would be a sign to the DXpedition (or other) station to "please
> select me next because I am copying your trace".  I suspect that the
> activation of this feature should be manually turned on by the callers,
> although I guess it wouldn't hurt to have it running all the time
> (unless it would add significant processing to the computers on one or
> both ends).
>
> Perhaps there are significant impediments that would make something like
> this impractical. However, after hours of trying to answer callers one
> at a time who don't copy at the time you tried them, I think it would be
> a tremendous improvement if it were in any way possible!
>
> Thank you for your kind consideration, and for the HUGE advance that Q65
> PILEUP provides. It is already the standard on 6m EME! VY 73, Lance
>
> On 19 Aug 2025 03:58, Jim Brown via wsjt-devel wrote:
> > On 8/18/2025 8:32 PM, Charles Suckling via wsjt-devel wrote:
> >> It seems from your last point that you suffer a lot from 'blind
> >> calling'.  This was a real problem during the early days of Superfox
> >> mode, and was overcome by code that prevents a 'hound' from
> >> transmitting at all until they have managed to decode the signal from
> >> the fox.
> >
> > Hi Charles,
> >
> > To understand Lance's request, you must understand his operating
> > conditions. He does 6M moon-bounce Dxpeditions to remote places, which
> > requires very low noise, high power, and big antennas. To minimize his
> > need for power, which translates to minimizing the cost of buying and
> > transporting fuel over oceans, and then to remote locations where
> > there's no noise, he INVITES blind callers. This is a method of
> > operation he devised years ago. He's currently somewhere in the South
> > Pacific, don't remember where.
> >
> > This is his website.  https://www.bigskyspaces.com/  Scroll down to
> > see his instructions to callers.
> >
> > I would encourage the development team to take his request seriously
> > and do your best to accommodate it.
> >
> > 73, Jim K9YC
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > wsjt-devel mailing list
> > wsj...@li...
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> --
> Lance Collister, W7GJ (ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX,
> 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ,
> S79GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ, H40GJ)
> P.O. Box 73
> Frenchtown, MT   59834-0073
> USA
> TEL: (406) 626-5728
> QTH: DN27ub
> URL: http://www.bigskyspaces.com/w7gj
> Skype: lanceW7GJ
> 2m DXCC #11 - 6m DXCC #815 - FFMA #7
>
> Interested in 6m EME?  Ask me about subscribing to the Magic Band EME
> email group, or just fill in the request box at the bottom of my web
> page (above)!
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Q65 Pileup Feature Request

[Reino T. <rei...@ko...>]

Lance Collister, W7GJ, Tuesday, August 19, 2025 8:25 AM wrote
> I thought
> that there might be room for this information the way the R
> report is inserted in TX3. I wonder if the program could
> automatically send a message in place of TX2, but similar to
> TX2 except with some other character (perhaps just a dash
> instead of a space) to indicate that the station copied a
> yellow spike during the receive cycle immediately
> preceding their transmit cycle.

Hello Lance and Charlie,

Unfortunately, that message or all standard messages support the 'R' using a single bit and there is no easy way to add another bit for that message. On the other hand, the field that conveys the report, grid or any of 'RRR', 'RR73', '73' and 'space' have available some unused bit combinations. 
If the grid is important for the QSO one possibility is to allocate a value that is presented to the user as '*' or any text. That new message could indicate that the station has *not* received the yellow spike in the immediately preceding slot. Or we could have even more values:
'BLIND ONLY', 'THREE OR MORE CYCLES AGO', TWO CYCLES AGO' and 'ONE CYCLE AGO' or something similar. The previous cycle would be indicated by the use of the grid i.e. normal Tx2. 

That method may not be best. if you need the grid value in the list for any transmission or reception purposes. In the case EME it may not be so important as it will be there once you want to contact that station.

Whatever it is a program update, I leave it to the designers.

73, Reino OH3mA

Re: [wsjt-devel] Q65 Pileup Feature Request

[Lance C. W. <w7...@bi...>]

Hi Reino,

MNI TNX for the background. No, we need the grid for the contact 
exchange. So the message would have to be TX2 PLUS some other indicator 
such as a hyphen (-) between the calls and the grid. I was hoping this 
could be done instead of the R, but I understand that apparently there 
is not enough available bits to send - instead of R 🙁  It is only 
valuable to know if a trace was copied (yellow spike received) during 
the immediately preceding sequence...

VY 73, Lance

On 19 Aug 2025 21:07, Reino Talarmo wrote:
> Lance Collister, W7GJ, Tuesday, August 19, 2025 8:25 AM wrote
>> I thought
>> that there might be room for this information the way the R
>> report is inserted in TX3. I wonder if the program could
>> automatically send a message in place of TX2, but similar to
>> TX2 except with some other character (perhaps just a dash
>> instead of a space) to indicate that the station copied a
>> yellow spike during the receive cycle immediately
>> preceding their transmit cycle.
> Hello Lance and Charlie,
>
> Unfortunately, that message or all standard messages support the 'R' using a single bit and there is no easy way to add another bit for that message. On the other hand, the field that conveys the report, grid or any of 'RRR', 'RR73', '73' and 'space' have available some unused bit combinations.
> If the grid is important for the QSO one possibility is to allocate a value that is presented to the user as '*' or any text. That new message could indicate that the station has *not* received the yellow spike in the immediately preceding slot. Or we could have even more values:
> 'BLIND ONLY', 'THREE OR MORE CYCLES AGO', TWO CYCLES AGO' and 'ONE CYCLE AGO' or something similar. The previous cycle would be indicated by the use of the grid i.e. normal Tx2.
>
> That method may not be best. if you need the grid value in the list for any transmission or reception purposes. In the case EME it may not be so important as it will be there once you want to contact that station.
>
> Whatever it is a program update, I leave it to the designers.
>
> 73, Reino OH3mA
>
>
-- 
Lance Collister, W7GJ (ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ, H40GJ)
P.O. Box 73
Frenchtown, MT   59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL: http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11 - 6m DXCC #815 - FFMA #7

Interested in 6m EME?  Ask me about subscribing to the Magic Band EME
email group, or just fill in the request box at the bottom of my web
page (above)!

Re: [wsjt-devel] Q65 Pileup Feature Request

[Lance C. W. <w7...@bi...>]

Thanks everyone for all the information. It appears that the only way to 
implement this feature would be to do a second decode with the inverse 
of the timing sequence, the way Joe did with JT65. That sure would be a 
great feature for Q65 Pileup!!!  TNX and VY 73, Lance

On 19 Aug 2025 22:11, Lance Collister, W7GJ wrote:
> Hi Reino,
>
> MNI TNX for the background. No, we need the grid for the contact 
> exchange. So the message would have to be TX2 PLUS some other 
> indicator such as a hyphen (-) between the calls and the grid. I was 
> hoping this could be done instead of the R, but I understand that 
> apparently there is not enough available bits to send - instead of R 
> 🙁  It is only valuable to know if a trace was copied (yellow spike 
> received) during the immediately preceding sequence...
>
> VY 73, Lance
>
> On 19 Aug 2025 21:07, Reino Talarmo wrote:
>> Lance Collister, W7GJ, Tuesday, August 19, 2025 8:25 AM wrote
>>> I thought
>>> that there might be room for this information the way the R
>>> report is inserted in TX3. I wonder if the program could
>>> automatically send a message in place of TX2, but similar to
>>> TX2 except with some other character (perhaps just a dash
>>> instead of a space) to indicate that the station copied a
>>> yellow spike during the receive cycle immediately
>>> preceding their transmit cycle.
>> Hello Lance and Charlie,
>>
>> Unfortunately, that message or all standard messages support the 'R' 
>> using a single bit and there is no easy way to add another bit for 
>> that message. On the other hand, the field that conveys the report, 
>> grid or any of 'RRR', 'RR73', '73' and 'space' have available some 
>> unused bit combinations.
>> If the grid is important for the QSO one possibility is to allocate a 
>> value that is presented to the user as '*' or any text. That new 
>> message could indicate that the station has *not* received the yellow 
>> spike in the immediately preceding slot. Or we could have even more 
>> values:
>> 'BLIND ONLY', 'THREE OR MORE CYCLES AGO', TWO CYCLES AGO' and 'ONE 
>> CYCLE AGO' or something similar. The previous cycle would be 
>> indicated by the use of the grid i.e. normal Tx2.
>>
>> That method may not be best. if you need the grid value in the list 
>> for any transmission or reception purposes. In the case EME it may 
>> not be so important as it will be there once you want to contact that 
>> station.
>>
>> Whatever it is a program update, I leave it to the designers.
>>
>> 73, Reino OH3mA
>>
>>
-- 
Lance Collister, W7GJ (ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ, H40GJ)
P.O. Box 73
Frenchtown, MT   59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL: http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11 - 6m DXCC #815 - FFMA #7

Interested in 6m EME?  Ask me about subscribing to the Magic Band EME
email group, or just fill in the request box at the bottom of my web
page (above)!