[Moon-net] PJ4EME CW activity 17 june

[DF2ZC]

Jimmy,

Congratulations on your speed. As ususal you are once again shooting from
the hip. I said nothing about last weekend, I'm talking of a communicated
callsign list of possible stations BEFORE the time slot for CW. 

Here you have a string of 15 stations and now please don't tell me of
information transferred, something that you and others obviously are not
willing to understand - the difference between data bits and information
bits. With 15 callsigns there are is only less than 4 bit of information
transferred with one of those callsigns. Since PJ4EME is klnown already
there is a 5th bit of information transferred with this callsign. You are
always publicly complaining and lamenting about callsign lists but now this
here is very much similar. And of course, no doubt all DATA bits are copied
on air, be it CW or JT65. But now the information transferred is less. I
hope this clarifies it now.

And the PJ4EME team does know I very much give them credit for their
excellent achievement and their very professional dxpedition.

Peter CEW I know you are grateful to me now for giving you another input for
your blog ;-)

Vy 73 Bernd DF2ZC
-----Original Message-----
From: jimmyv at hol.gr [mailto:jimmyv at hol.gr] 
Sent: Freitag, 15. Juni 2007 16:51
To: DF2ZC
Cc: Moon-Net; moon at moonbounce.info
Subject: RE: PJ4EME CW activity 17 june

Bernd

so how last Sunday they did not know who was calling and they made 10 cw
QSOs on random, without preamp, filter and headphones? Same was true for
those that worked them.
You know why? Because they COPIED the signals. Not identified with some
certainty 1/7 of the information to match it to a database list, as Deep
Search (DS) decoder does in jt65. And as DJ5HG articles well have pointed
out.
Pls do not create false impressions and do unfortunate mode comparisons,
when current digital status is at least -25db (300 times) and beyond, easier
than cw. Plus the fact that in DS there is NO COPY of full information as
required by EME operating procedures that apply for years.

So give PJ4EME some credit for their cw FB work and being the only 2m
expedition that at least keeps its promise and works both modes by honoring
the time slots they had announced per mode.

By the way, why didn't u try to work them too last Sunday or coming one,
copy them yourself, and tx anywhere near their transmitting frequency; this
is what happened when for example I had the QSO with
them:-)
So as to compare apples with apples and see for yourself the difficulty each
mode entails.

73,
Jimmy SV1BTR

> hmmm...so the PJ4 teams knows in advance who will be calling, i.e. 
> which callsigns might be in the pileup. Isn't that exactly what is 
> always complained about the JT65 DS mode?
>
> ;-)
>
> vy 73 Bernd DF2ZC (JO30RN)
> __________________________
> Website: www.df2zc.de
> ICQ    : 273214349
> 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
>
>
>   _____
>
> From: moon-bounces at moonbounce.info 
> [mailto:moon-bounces at moonbounce.info] On Behalf Of Paul Chominski
> Sent: Freitag, 15. Juni 2007 05:09
> To: Marko Tsekov; PE1L Ren?
> Cc: moon at moonbounce.info
> Subject: Re: [Moon] ] PJ4EME CW activity 17 june
>
>
> WA6PY is also interested
>
> ----- Original Message -----
> From: Marko Tsekov <mailto:lz2us at orbinet.bg>
> To: PE1L Ren? <mailto:moonnet at cqdx.nl>
> Cc: moon at moonbounce.info
> Sent: Thursday, June 14, 2007 1:13 AM
> Subject: [Moon] ] PJ4EME CW activity 17 june
>
>
>
> Latest info about stations wanted to work PJ4EME on CW:
>
> CT1HZE
> G4DHF
> G3ZIG
> DF6NA
> IK2DDR
> IV3GBO
> I5WBE
> K9DX
> LZ1DP
> LZ2US
> YO2AMU
> RA6DA
> RN6MT
> SV3AAF
> EI4DQ
>
> 15 stations  for now................
>
> 73 de  LZ2US
>
>
>
>   _____
>
>
>
>
> _______________________________________________
> 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
>
>