[Moon] Moon Digest, Vol 15, Issue 17

[Rainer]

Hi,

I don't understand all this guessing and debating !

F6DRO clearly stated it was EME !!!

Antenna AZ from DL0SHF was 255deg and EL 13deg !  direct AZ=211deg
There were no tropo conditions at all.

The only problemis that BEACONSPOT displays falsly TR for Tropo:
2015-10-10 	14:09 	DL0SHF 	10368.0250 	519 	TR 	jn03<cw_eme>jo54 519 on 
120cm 	1401 	DXC 	F6DRO 	JN03TJ

!!!          ???????

and that's beacause there does not exist any  "CW_EME"-mode. If you 
enter "EME" instead of CW_EME all would
be ok. The report also is clear with "519" so it's not necessary to 
state "CW" !!!!

No mystery to be solved.


73, Rainer


Am 29.10.2015 um 12:44 schrieb Hans van Alphen:
> Hi All,
>
> In my opinion the best proof if it was EME or tropo comes from the 
> aiming off the dish. If it is aimed at the moon I cannot think it 
> would be tropo. If it was aiming horizontal and to the direction of 
> DL0SHF then it could be tropo but I am convinced this was EME.
>
> Dom, your spot was very clear and without a doubt a spot for EME.
> I cannot see anyone think it is a tropo spot. Furthermore I doubt if 
> tropo would be possible from DL0SHF to F6DRO. Looking at the direction 
> from DL0SHF to F6DRO the azimuth is somewere at 210 degrees. Its 
> doubtfull that with this azimuth the elevation at DL0SHF would ever be 
> as low that tropo can be possible at all.
>
> Best 73's  Hans PA0EHG
>
>> Hi Dom
>>
>> The proof of whether the signal was EME or tropo can come from both the
>> observed Doppler shift and from the DT of the decode.  EME decode 
>> will be
>> around 3.3s for DL0SHF (a bit more than moon delay because of the 
>> software
>> implementation of the JT coding).
>>
>> 73
>>
>> Charlie
>
> _______________________________________________
> Moon mailing list
> Moon at moonbounce.info
> http://lists.moonbounce.info/listinfo/moon

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.moonbounce.info/pipermail/moon/attachments/20151029/c3be7f8e/attachment.html>