Moon-net October 2014

moon-net@mailman.pe1itr.com

137 participants
197 discussions

by Pete M

I have been playing with a new Triquint ULNA device (TQP3M9036). It Shows a lot of promise. It is like a MAR or MSA device in that it is 50ohm in and out. and has a claimed NF about .4db nf ( their numbers). I have built several pramps to test them and have gotten even better than they claim and they cover 50-1296 with ease and NF is .4ish or below. The S11 and S22 are both great and the OIP3 is +35db also ...very nice device. It has great promise as a good terrestrial LNA. Preamps are foolproof to build and would cost under $50 if all the best quality parts are used. Just for information only ... Pete WA2ODO -- ++++++CONFIDENTIALITY NOTICE++++++ The information in this email may be confidential and/or privileged. This email is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system.

6 months

Beko HLV-1200 SOLD.

by pa3fpq

Gents, The amplifier is sold. Johan PA3FPQ

3 years, 5 months

Doppler question

by Juan Antonio Fernandez

Sri I made, at least a mistake, I send it again. Hi all, Very interesting answers. I come from Sats world, where the Doppler is a serious issue and it is so quick that it is impossible to work JT65. I will speak thinking in one carrier. Sats need to receive in only one fix frequency (it is an active RX with a wideband), if the Sat receives a carrier in this frequency then it will be repeated. The signal TX from the Sat will be in one fix frequency. So people who work Sats must correct its TX frequency (according with actual Doppler) to reach the sat in its fix frequency, in the same way because of the Sats will repeat this signal in a fix frequency, people must correct its RX frequency (according with actual Doppler). This way of dealing with Doppler is very interesting because NOBODY KNOWS the Doppler of the other stations and nobody needs to know it, we only need to know our own Doppler. If we would use this agreement to EME communications we will always speak about the frequency we hit the Moon, in other words the frequency which the Moon hear us and repeat our signal. The actual EME software shows us the Doppler as the sum of the Doppler effects to reach the Moon and to receive the bounce signal, so Moon will receive us at ½ Doppler announced, the other ½ effect will appear after de bounce. I will try to set a couple of examples. 1.- We will agree to hit the Moon in 1296.070. This is the frequency I will announce in the log. In our software the dates will be: *Self Doppler +3KHz *DX Doppler -2KHz The sign that the software shows will aplly to RX frequency and the opposite to the TX frequency, and always ½ magnitude on each one. Both of us must deal with Doppler, each one must do their task to hit the moon in the agreed frequency and to receive the bounce according our Doppler. Then we must set on our transceivers: *Me TX: 1296.070 -1.5KHz = 1296.0685MHz RX: 1296.070 +1.5KHz= 1296.0715MHz *DX TX: 1296.070 +1.0KHz = 1299.071MHz RX: 1296.070 -1.0KHz= 1296.069MHz Each station who sees the post will act only according its own Doppler. Don´t mind where is the DX station. 2.- In this case I see a signal in my receiver in 1296.070. What kind of pair of frequencies I must set (I know nothing about the DX station I have still decode nothing), I only know me own Doppler, and it is +2KHz. I must hit the moon in the same frequency that my partner: TX: 1296.070 -1.0KHz = 1296.069MHz RX: 1296.070 = 1296.070MHz WE WILL NOT NEED TO KNOW NO MORE THAN OUR DATES. I haven´t spoken about what frequencies will be the echoes (both echoes), to make the understanding easy. As a drawback we should change our habits, we should always use the RIT as follow: TX: The frequency we choose plus the opposite sign of Doppler and ½ Doppler magnitude. RIT: the sign of our Doppler and ½ Doppler magnitude. Although at first glance it seems not to be interesting in 144MHz but we will always hit the target in whatever band, even in 144MHz. Somebody can tell that they need a computer, to do JT65 of course, if you do CW surely have a smart phone with the proper software to know your own Doppler or you can print it before. If I made some mistakes let me know. It is my 2 cents. Juan Antonio EA4CYQ

6 years, 9 months

Preamplifier and Bandpass filter for 144 MHz

by Dual

7 years, 2 months

QRV on 2m

by Edward R Cole

Its been awhile since I have been QRV with my 2m-eme station. Four independent problems in my transmission line during the winter kept me off the Moon and then my HVPS acted up. Well it turned out to be a simple problem but it didn't appear that way. My 4kV dropped to 2.8kV without a load. I envisioned all kinds of problems but in the end it was simply a blown HV fuse. It did not blow open but instead went to 16meg-ohm which was enough to drop the HV with very low current being drawn by the HV panel meter. Having no replacement fuse, I decided to remove the HB fuse holder from the HVPS since changing the fuse required removing the 8877 deck from the rack to gain access thru the HVPS top plate which is directly under the amplifier. I will order some more HV fuses from Nebraska sales ($25/ea.) and make an inline HV fuse box which will be much quicker access to replace a fuse. Actually, I have only blown two of these fuses in 8-years of running. How I blew this one is that the 6-dB attenuator that I was using to lower drive to my transverter to keep drive below 50w to the 8877 failed in short resulting in over 100w drive to the 8877. Anode current spiked taking out the HV fuse as it is designed to do. Probably hit over 2kW output! A couple other improvements will make recovery from HV events quicker: I brought the 240vac mains fuses to the front panel of the HVPS and increased them to 20A. And I added a vernier to the 8877 drive input cap. Looks like I got a finer tune on the input as it is taking less drive to reach 1200w. I will be QRV Sunday from about 1400utc to 1700utc (Moonset): 144.116, 1st for CQ and on N0UK logger. Mon> I will be trying to work 6W/PE1L in Senegal very early in my morning. We only have about 30-min common Moon on Monday but this increases on subsequent days. 73, Ed - KL7UW http://www.kl7uw.com "Kits made by KL7UW" Dubus Mag business: dubususa(a)gmail.com

7 years, 9 months

Double Ridge waveguide, WRD-750 to WR90 or WR75 transition needed.

by Greg Bailey

My Teledyne (MTI5015D) TWT has a Double Ridged WRD-750 output flange. I would like to transition this to a WR90 or WR75 guide if possible. If you have such a transition, know of a surplus emporium, or have suggestions as to fabricating such a device I would appreciate a reply. 73, K6QPV GBailey(a)Mail.SDSU.Edu

8 years, 6 months

EME antenna 77 GHz

by Sergei RW3BP

Оne more thanks to organizers of excellent EME2014 conference. May be my conference paper and presentation will be interesting for 10 GHz and up EMErs. http://www.vhfdx.ru/rw3bp/RW3BP.pdf (0.82 MB) Conference paper http://www.vhfdx.ru/rw3bp/EME%20antenna%20and%20Jupiter%20noise%20on%2077%2… (2.6 MB) Presentation 73, Sergei RW3BP

8 years, 7 months

Correction: 10/31 --- 4M2098 7 syncs and - 23 dB

by rein0zn＠ix.netcom.com

SRI 73 Rein W6SZ -----Original Message----- >From: rein0zn(a)ix.netcom.com >Sent: Oct 31, 2014 5:52 PM >To: Ray Rector <wa4njp(a)bellsouth.net> >Cc: moon-net(a)nlsa.com, 'Moon' <Moon(a)luxspace.lu>, moon-net-bounces(a)mailman.pe1itr.com, 'nick priborsky' <nick.priborsky(a)lsespace.com>, k1jt(a)arrl.net, 'Ghislain Ruy-Longépé' <ruygh(a)yahoo.fr> >Subject: Re: [Moon-Net] 4M: update of trajectory - thanks > >Hi Ray, > >Thanks for the info. Vy interesting. > >In spite of the almost 2 MHz difference in frequency, your antenna is working just fine compared what I get here. >WE might have all the same problems with higher gain antenna's > > >Did a quick Google on you call and found some info on the SETI League's picture page. I did not look at the date's >but from those pictures it looks like you are using more than one yagi! >Multi-band BIG EME station. Very impressive! > >I found out about the project 4 hours, I think, before the launch. At that point I thought lets see whether >I can hear it. My HB antenna had been parked ( laying on the ground in the yard for quite some time ) together with >a shorter yagi 8 ft or so made many years ago unknown manufacturer. Anyway put the antenna on a stepladder and >did full decodes I guess # 4M0076 or so. > >The next day I had the bigger Yagi with manual pointing again and have been tracking on and off during the period since that >first day. > >Unfortunately I was totally unprepared about the data warehouse project, so did not pay attention to proper data collection. >Was totally unaware of the All.txt concept ( after many years of having used WSJT and WSPR on many bands ) >so will try to back analyze what I collected. > >Yesterday was a day of lower attention due to activities with xyl away from house. > > >The last decodes from 10/30 02:00 UTC or there about were: > >Looking to results from yesterday I had for # 4M2098 7 syncs and - 23 dB > # 4M2099 4 syncs and - 24 dB > >Anyway your results were also dB's better than mine without a doubt. > >In the end, I am and have been enjoying this very much and seriously hope it will be repeated with perhaps a little more >advanced notice. May be I have to blame myself about the noticing, though > >73 Rein W6SZ > > > > > > >-----Original Message----- >>From: Ray Rector <wa4njp(a)bellsouth.net> >>Sent: Oct 31, 2014 4:43 PM >>To: "rein0zn(a)ix.netcom.com" <rein0zn(a)ix.netcom.com> >>Subject: Re: [Moon-Net] 4M: update of trajectory - thanks >> >>Hello Rein >> I have had some time to observe the 4m and I let you look at my all.... my antenna does not work well at 145.9 but it did get a lot of copy.. >> Have a nice day, >>Ray WA4NJP EM84dg >> >> >>My RX was always on 145.980.000 and the time offset can be seen as last digit in the file ID, most time -6, -7 or -8 >> >> >>On Friday, October 31, 2014 12:03 PM, "rein0zn(a)ix.netcom.com" <rein0zn(a)ix.netcom.com> wrote: >> >> >> >>Hi George, >> >>If I may ask you, what are you using now as an antenna? >> >>$ * 3 WL ? >> >> >>Looking to your RX results it appears you doing 2-3 dB better than I seem to be doing with my HB 3 wl LFA. >> >>That extra gain makes quite a bit of difference on the bottom line of course! >> >>73 Rein W6SZ >> >> >> >>-----Original Message----- >>>From: George VK4AMG <vk4amg(a)gmail.com> >>>Sent: Oct 31, 2014 10:43 AM >>>To: 'Attilio Pier Paolo Pannella' <attilio.pannella(a)lsespace.com> >>>Cc: moon-net(a)nlsa.com, 'Moon' <Moon(a)luxspace.lu>, moon-net-bounces(a)mailman.pe1itr.com, 'nick priborsky' <nick.priborsky(a)lsespace.com>, k1jt(a)arrl.net, 'Ghislain Ruy-Longépé' <ruygh(a)yahoo.fr> >>>Subject: Re: [Moon-Net] 4M: update of trajectory - thanks >>> >>> >>> >>>UTC Date: 2014 Oct 30 >>> >>> >>> >>> >>> >>> >>> >>>................................................ >>> >>> >>> >>> >>> >>> >>> >>>101300 6 -22 1.805 -3 3* 139V244A -7C 1 0 0.0 >>> >>>101400 6 -18 1.813 -3 3* 73 DE N0BML 1 0 0.0 >>> >>>101500 11 -17 1.822 -3 3* RAOBY3UIG5 1 0 0.0 >>> >>>101600 12 -19 1.825 -3 3* 73 DE K4CNM 1 0 0.0 >>> >>>101700 6 -18 1.835 -3 3* LX0OHB-4M2195 1 0 0.0 >>> >>>101800 9 -17 1.848 -3 3* 139V244A -7C 1 0 0.0 >>> >>>101900 9 -19 1.857 -3 3* HOLA DE NX6ED 1 0 0.0 >>> >>>102000 7 -19 1.875 -3 3* R4EJB3OR4J 1 0 0.0 >>> >>>102100 14 -16 1.883 -3 3* AQUI LU4FRH 1 0 0.0 >>> >>>011000 2 40/48 >>> >>>102200 3 -22 1.870 -3 3* LX0OHB-4M2196 1 0 0.0 >>> >>>102300 9 -20 1.911 -3 3* 139V244A -7C 1 0 0.0 >>> >>>102400 10 -15 1.914 -3 3* 73 DE KR0SIV 1 0 0.0 >>> >>>102500 7 -21 1.941 -3 3* RAN?A3UIEW 1 0 0.0 >>> >>>102600 11 -17 1.940 -3 3* N4PDY PEACE 1 0 0.0 >>> >>>102700 6 -23 1.761 -5 4* LX0OHB-4M2197 1 0 0.0 >>> >>>102800 10 -17 1.769 -5 0* 142V241A -7C 1 0 0.0 >>> >>>102900 5 -21 1.768 -5 4* 73 DE K4RTS 1 0 0.0 >>> >>>103000 4 -24 1.773 -3 4* R4EPF3M Y5 1 0 0.0 >>> >>>103100 13 -19 1.780 -3 3* QRV DE WA8MCD 1 0 0.0 >>> >>>103200 3 -21 1.756 -5 4* LX0OHB-4M2198 1 0 0.0 >>> >>>103300 11 -18 1.794 -5 1* 139V244A -7C 1 0 0.0 >>> >>>103400 9 -16 1.798 -5 3* 73 DE AA7EE 1 0 0.0 >>> >>>103500 6 -21 1.791 -5 3* RAOFA3UIGI 1 0 0.0 >>> >>>103600 7 -19 1.807 -5 3* 73 DE N8ABW 1 0 0.0 >>> >>>103700 10 -17 1.803 -5 3* LX0OHB-4M2199 1 0 0.0 >>> >>>103800 8 -20 1.842 -5 3* 139V244A -6C 1 0 0.0 >>> >>> >>> >>>Attilio, >>> >>> >>> >>>Last 25minute decodes: >>> >>> >>> >>>101300 6 -22 1.805 -3 3* 139V244A -7C 1 0 0.0 >>> >>>101400 6 -18 1.813 -3 3* 73 DE N0BML 1 0 0.0 >>> >>>101500 11 -17 1.822 -3 3* RAOBY3UIG5 1 0 0.0 >>> >>>101600 12 -19 1.825 -3 3* 73 DE K4CNM 1 0 0.0 >>> >>>101700 6 -18 1.835 -3 3* LX0OHB-4M2195 1 0 0.0 >>> >>>101800 9 -17 1.848 -3 3* 139V244A -7C 1 0 0.0 >>> >>>101900 9 -19 1.857 -3 3* HOLA DE NX6ED 1 0 0.0 >>> >>>102000 7 -19 1.875 -3 3* R4EJB3OR4J 1 0 0.0 >>> >>>102100 14 -16 1.883 -3 3* AQUI LU4FRH 1 0 0.0 >>> >>>102200 3 -22 1.870 -3 3* LX0OHB-4M2196 1 0 0.0 >>> >>>102300 9 -20 1.911 -3 3* 139V244A -7C 1 0 0.0 >>> >>>102400 10 -15 1.914 -3 3* 73 DE KR0SIV 1 0 0.0 >>> >>>102500 7 -21 1.941 -3 3* RAN?A3UIEW 1 0 0.0 >>> >>>102600 11 -17 1.940 -3 3* N4PDY PEACE 1 0 0.0 >>> >>>102700 6 -23 1.761 -5 4* LX0OHB-4M2197 1 0 0.0 >>> >>>102800 10 -17 1.769 -5 0* 142V241A -7C 1 0 0.0 >>> >>>102900 5 -21 1.768 -5 4* 73 DE K4RTS 1 0 0.0 >>> >>>103000 4 -24 1.773 -3 4* R4EPF3M Y5 1 0 0.0 >>> >>>103100 13 -19 1.780 -3 3* QRV DE WA8MCD 1 0 0.0 >>> >>>103200 3 -21 1.756 -5 4* LX0OHB-4M2198 1 0 0.0 >>> >>>103300 11 -18 1.794 -5 1* 139V244A -7C 1 0 0.0 >>> >>>103400 9 -16 1.798 -5 3* 73 DE AA7EE 1 0 0.0 >>> >>>103500 6 -21 1.791 -5 3* RAOFA3UIGI 1 0 0.0 >>> >>>103600 7 -19 1.807 -5 3* 73 DE N8ABW 1 0 0.0 >>> >>>103700 10 -17 1.803 -5 3* LX0OHB-4M2199 1 0 0.0 >>> >>> >>> >>>Client restarted. >>> >>> >>> >>> >>> >>>cid:image001.png@01CFF54B.0BA579A0 >>> >>> >>> >>> >>> >>>Still no go! >>> >>> >>> >>>Hope this helps. >>> >>> >>> >>>George >>> >>> VK4AMG >>> >>> >>> >>>Note because of DT and want to use MAP65, PC is GPS timesync’d to -10 sec >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>>Attilio, >>> >>> >>> >>>I understand the requirement of the client. >>> >>> >>> >>>I was keen to provide access to the All.txt to allow realtime upload to the warehouse. >>> >>> >>> >>>However the client never proceeds past “Waiting for new packet”. >>> >>> >>> >>>I see there has been some comment on “blogs” that the client needs to determine the sequence and find the start of sequence before uploading packets. >>> >>> >>> >>>Under the QSB environment that most have experienced this means the client never starts to transfer. >>> >>> >>> >>>Tonight is the first time I have seen 100% decode in any 5 or more sequences. >>> >>> >>> >>>I regret that this seems to have been an unexpected limitation by the developers of the Client. >>> >>> >>> >>>Problems also arose due to the received frequency (Doppler and frequency stability issues) and the timing issues, up to 12 seconds DT. Neither WSJT or MAP65 were intended to operate in this envelope. >>> >>> >>> >>>I have alternatively uploaded audio files as soon as possible. I however have no idea whether you decode near realtime of whether these contribute to the data warehouse. >>> >>> >>> >>>Regardless of this and my late introduction to the project, I have, like many others, enjoyed using my EME station outside its specification to track and decode the 4M project “satellite”. >>> >>> >>> >>>Thanks for your comments. Thanks for the opportunity to participate. >>> >>> >>> >>>Best 73 >>> >>> >>> >>>George >>> >>> VK4AMG >>> >>> >>> >>>PS: my background outlined on my QRZ.com page. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>>From: Attilio Pier Paolo Pannella [mailto:attilio.pannella@lsespace.com] >>>Sent: Friday, 31 October 2014 5:56 PM >>>To: 'George VK4AMG' >>>Cc: Ghislain Ruy-Longépé; moon-net-bounces(a)mailman.pe1itr.com; 'Moon'; moon-net(a)nlsa.com; k1jt(a)arrl.net; nick priborsky >>>Subject: Re: [Moon-Net] 4M: update of trajectory >>> >>> >>> >>>Dear George >>>I am sorry to hear about the frustration you've been facing lately. >>>I am here to provide you with some explanation about the 4M client as unfortunately I think there has been some confusion about it. >>>The main purpose of this client is to get JT65B messages as they are received from WSJT and provide them to the data warehouse. >>>Once the client gets a message, it has to mark its sequence type/number and send this information along with other information and the message itself to the data warehouse. >>>This way users can check on their side the information they are submitting and we are getting information in near real time, to allow LuxSpace to process them as they are available. This way LuxSpace can check radiation experiment data or estimate the battery life and so on, without having to wait the availability of the ALL.TXT files from the OMs supporting the project at the end of the day. >>>Moreover the client allow users to easily upload audio files which are also very important for the project. >>>Unfortunately, though, I think there has been some confusion on the way the 4M client works, that is, the client relies on the decoded.txt file to retrieve messages from WSJT as they are decoded, but it neither gets JT65B messages from ALL.TXT nor sends this file to LuxSpace. >>>The ALL.TXT files have to be send to LuxSpace manually via email as it has been requested for the contest. >>>If you are referring about the fact that the client does keep messages to be delivered in Waiting... status, I posted an explanation of this on our blog as Ghislain pointed out. >>>I understand that some more functionalities from the 4M client would have been nice and appreciated (as the automatic deliver of ALL.TXT files) and others might have been differently implemented, but this client and the data warehouse have both been developed in short times keeping in mind near-realtime approaches, and we are very proud of what we achieved and delivered during this time. >>>I hope this clarifies some of the issues you have been facing. >>> >>>I take advantage of this email to thank you for your precious support and your reports. >>> >>>Vy 73 de Attilio - DL1UNX >>> >>> >>> >>>On 31/10/14 04:37, Ghislain Ruy-Longépé wrote: >>> >>>Dear George, >>> >>>Indeed, the clock drift is quite annoying, but so much ingenuity was put everywhere to solve the problem that it is amazing. >>> >>>We cannot solve the 4M client problem. The explanation has been published by LSE space on our blog. >>> >>>We all thank you and many others for all your efforts and endeavor. >>> >>>I try to reply to every single OM individually, quite an overwhelming task, we could not foresee such a success and interest. >>> >>>Thanks for AOS and LOS information, that allowed me to confirm the trajectory after the flyby. We are on the +1 sigma side of the dispersion, this also shows the performances of the LM3-C launcher. (the venting out of the tanks after the Chang'e 5T1 separation gave us an additional impulse, that was purposedly oriented in the right direction for 4M) >>> >>>Best 73 lx2rg >>> >>> >>> >>>-----Original Message----- >>>From: George VK4AMG [mailto:vk4amg@gmail.com] >>>Sent: vendredi 31 octobre 2014 00:54 >>>To: 'Ghislain Ruy-Longépé'; moon-net-bounces(a)mailman.pe1itr.com; 'Moon'; moon-net(a)nlsa.com >>>Cc: k1jt(a)arrl.net >>>Subject: RE: [Moon-Net] 4M: update of trajectory >>> >>>Ghislain, >>> >>>Yesterday was an interesting but initially frustrating day of receiving the 4M messages. >>> >>>In addition to using a FuncubePro to WSJT10, I have been receiving on MAP65 from an IQ+. Both receivers are fed from a splitter in the shack, MHLNA, and 4x 7el DK7ZB AZEL array. >>> >>>My computer is time locked with a Bluetooth GPS and a homebrew (VB6) application. MAP65 refused to decode once the DT went beyond 10secs. >>> >>>4M rose in QG62 around 0000Z. >>> >>>In order to maintain the dual receiving environment, I shifted the WSJT10 to a eeePC netbook (a snail in a black plastic case). The hope was to maintain time accuracy for audio file for upload while I sorted the MAP65 problem. >>> >>>Due to earth induced noise on the audio feed to the eeePC, I found it necessary to shift the Funcube freq by 500hz. >>> >>>After modifying my GPS time sync application to shift the PC time by 10 seconds, MAP65 didn't know the difference and happily resumed decoding. >>> >>>Sadly home pressures meant I was not able to upload as many audio files as I would have liked. The 4M client still refuses to parse and upload my ALL.txt file even on eeePC and a Win8 PC looking at the eeePC audio files as a network drive. >>> >>>After 4M set (1308Z), I merged the files from the 3 decode logs. This was a much bigger job than I expected due to the frequency offset and the differing file formats from MAP65 and the two WSJT instances running under different operating systems (W7 and W8). The latter was not anticipated. >>> >>>You will see, by the timestamp on my log submission email, it was very late (actually early) before the day's results (13 hours approx) were submitted. >>> >>>I found the tracking information to be accurate. As I do not have automated tracking (yet) and due to the uncertainty of the trajectory, I continued to search when I could. >>> >>>The trajectory in the last 6 hours required little adjustment of the antenna position, and thus there was some relief for the domestic situation (grandkid school dropoff, pickup and minding day). >>> >>>Best 73 >>> >>>George >>> VK4aAMG >>> >>>-----Original Message----- >>>From: moon-net-bounces(a)mailman.pe1itr.com [mailto:moon-net-bounces@mailman.pe1itr.com] On Behalf Of Ghislain Ruy-Longépé >>>Sent: Friday, 31 October 2014 12:52 AM >>>To: moon-net-bounces(a)mailman.pe1itr.com; 'Moon'; moon-net(a)nlsa.com >>>Subject: [Moon-Net] 4M: update of trajectory >>> >>>Dear All, >>> >>>Please use the AFTER_HIGH.txt TLE. You can find it here: >>>https://cloud.luxspace.lu/public.php?service=files<https://cloud.luxspace.lu/public.php?service=files&t=d620fe27918fe6aa728658…> &t=d620fe27918fe6aa72865817d8f1b8de >>> >>>Alternatively, our tracking webpage will be updated in a few minutes. >>> >>>73 >>>Lx2rg >>> >>>-----Original Message----- >>>From: Jean-Baptiste Frappé [mailto:frappe@luxspace.lu] >>>Sent: jeudi 30 octobre 2014 09:39 >>>To: Ghislain Ruy-Longépé; 'Allan Saul'; moon-net-bounces(a)mailman.pe1itr.com; Moon; wbauer(a)pt.lu; lx1db(a)rlx.lu; Bart Van Schie >>>Subject: RE: AOS in JF96fd >>> >>>OK, will try these tracking orientations during the pass of today. >>>Regards, >>> >>>Jean-Baptiste >>> >>> >>> >>>Jean-Baptiste FRAPPE >>>LuxSpace Sàrl – Space Systems Engineer >>>SES Business Center, >>>9, rue Pierre Werner, L-6832 Betzdorf, Luxembourg >>>Phone: +352 267890 8048 >>>Fax: +352 267890 4049 >>> >>>-----Original Message----- >>>From: Ghislain Ruy-Longépé [mailto:ruygh@yahoo.fr] >>>Sent: 30 October 2014 8:45 AM >>>To: 'Allan Saul'; moon-net-bounces(a)mailman.pe1itr.com; Moon; wbauer(a)pt.lu; lx1db(a)rlx.lu; Jean-Baptiste Frappé; Bart Van Schie >>>Subject: RE: AOS in JF96fd >>> >>>Dear Allan, >>> >>>I made simulation and it seems that AFTERHIGH.txt tle is the best match to your observation. >>> >>>Can you tell me what is the altitude of your QTH and the height of the antenna AG ? >>> >>>The TLE set can be found in : >>>https://cloud.luxspace.lu/public.php?service=files<https://cloud.luxspace.lu/public.php?service=files&t=33c4a21c09ba3736a55fc0…> &t=33c4a21c09ba3736a55fc09896e463f6 >>> >>> >>>73 LX2RG >>> >>>-----Original Message----- >>>From: Allan Saul [mailto:allan@rfdesign.co.za] >>>Sent: jeudi 30 octobre 2014 07:54 >>>To: Ghislain Ruy-Longépé >>>Subject: AOS in JF96fd >>> >>>Hi Ghislain, >>> >>>AOS early in JF96fd. >>>Your TLE set predicted AOS at 0704z but I see a decode now at 0648.z Doppler is at 530Hz and that’s with the IC-910 set to 145.980 USB. >>> >>>73 Allan ZS1LS >>> >>>------------------------------- >>>LuxSpace Sàrl >>>Registered Office: SES Business Center; 9, rue Pierre Werner; 6832 Betzdorf; LUXEMBOURG Board of Directors: Jochen Harms (Managing Director), Marco R. Fuchs, Oliver Salisch Registry Court Luxembourg: B104935 >>>NAT-ID: 2004 2427 218 >>>VAT-ID: LU20546250 >>>IBLC: 20546250 >>>This message and any attachments is intended solely for the addressee and is confidential. If you receive this message in error, please delete it and immediately notify the sender. >>>Any use not in accordance with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except LuxSpace formal approval. >>>The internet cannot guarantee the integrity of this message. LuxSpace and its sister companies will not be liable for the message if modified. >>> >>>_______________________________________________ >>>Moon-Net posting and subscription instructions are at http://www.nlsa.com/nets/moon-net-help.html >>> >>> >>> >>> >>> >>>-- >>>Attilio Pannella >>>System Engineer >>> >>>LSE Space GmbH >>>Argelsrieder Feld 22 >>>82234 - Wessling - Germany >>>Tel: +49 (0) 8153.881.099.21 >>>Fax: +49 (0) 8153.881.099.15 >>> >>>LSE Space GmbH >>>Argelsrieder Feld 22, D-82234 Wessling, Germany >>>Geschäftsführer: Daniel Gestal, Nicholas Priborsky >>>Registergericht: Amtsgericht München >>>Register-Nr.: HRB 195494 >>> >> >>_______________________________________________ >>Moon-Net posting and subscription instructions are at http://www.nlsa.com/nets/moon-net-help.html

8 years, 7 months

Re: [Moon-Net] 4M: update of trajectory - thanks

by rein0zn＠ix.netcom.com

Hi Ray, Thanks for the info. Vy interesting. In spite of the almost 2 MHz difference in frequency, your antenna is working just fine compared what I get here. WE might have all the same problems with higher gain antenna's Did a quick Google on you call and found some info on the SETI League's picture page. I did not look at the date's but from those pictures it looks like you are using more than one yagi! Multi-band BIG EME station. Very impressive! I found out about the project 4 hours, I think, before the launch. At that point I thought lets see whether I can hear it. My HB antenna had been parked ( laying on the ground in the yard for quite some time ) together with a shorter yagi 8 ft or so made many years ago unknown manufacturer. Anyway put the antenna on a stepladder and did full decodes I guess # 4M0076 or so. The next day I had the bigger Yagi with manual pointing again and have been tracking on and off during the period since that first day. Unfortunately I was totally unprepared about the data warehouse project, so did not pay attention to proper data collection. Was totally unaware of the All.txt concept ( after many years of having used WSJT and WSPR on many bands ) so will try to back analyze what I collected. Yesterday was a day of lower attention due to activities with xyl away from house. The last decodes from 10/30 02:00 UTC or there about were: Looking to results from yesterday I had for # 4M2098 7 syncs and - 23 dB # 4M2099 4 syncs and - 24 dB Anyway your results were also dB's better than mine without a doubt. In the end, I am and have been enjoying this very much and seriously hope it will be repeated with perhaps a little more advanced notice. May be I have to blame myself about the noticing, though 73 Rein W6SZ -----Original Message----- >From: Ray Rector <wa4njp(a)bellsouth.net> >Sent: Oct 31, 2014 4:43 PM >To: "rein0zn(a)ix.netcom.com" <rein0zn(a)ix.netcom.com> >Subject: Re: [Moon-Net] 4M: update of trajectory - thanks > >Hello Rein > I have had some time to observe the 4m and I let you look at my all.... my antenna does not work well at 145.9 but it did get a lot of copy.. > Have a nice day, >Ray WA4NJP EM84dg > > >My RX was always on 145.980.000 and the time offset can be seen as last digit in the file ID, most time -6, -7 or -8 > > >On Friday, October 31, 2014 12:03 PM, "rein0zn(a)ix.netcom.com" <rein0zn(a)ix.netcom.com> wrote: > > > >Hi George, > >If I may ask you, what are you using now as an antenna? > >$ * 3 WL ? > > >Looking to your RX results it appears you doing 2-3 dB better than I seem to be doing with my HB 3 wl LFA. > >That extra gain makes quite a bit of difference on the bottom line of course! > >73 Rein W6SZ > > > >-----Original Message----- >>From: George VK4AMG <vk4amg(a)gmail.com> >>Sent: Oct 31, 2014 10:43 AM >>To: 'Attilio Pier Paolo Pannella' <attilio.pannella(a)lsespace.com> >>Cc: moon-net(a)nlsa.com, 'Moon' <Moon(a)luxspace.lu>, moon-net-bounces(a)mailman.pe1itr.com, 'nick priborsky' <nick.priborsky(a)lsespace.com>, k1jt(a)arrl.net, 'Ghislain Ruy-Longépé' <ruygh(a)yahoo.fr> >>Subject: Re: [Moon-Net] 4M: update of trajectory - thanks >> >> >> >>UTC Date: 2014 Oct 30 >> >> >> >> >> >> >> >>................................................ >> >> >> >> >> >> >> >>101300 6 -22 1.805 -3 3* 139V244A -7C 1 0 0.0 >> >>101400 6 -18 1.813 -3 3* 73 DE N0BML 1 0 0.0 >> >>101500 11 -17 1.822 -3 3* RAOBY3UIG5 1 0 0.0 >> >>101600 12 -19 1.825 -3 3* 73 DE K4CNM 1 0 0.0 >> >>101700 6 -18 1.835 -3 3* LX0OHB-4M2195 1 0 0.0 >> >>101800 9 -17 1.848 -3 3* 139V244A -7C 1 0 0.0 >> >>101900 9 -19 1.857 -3 3* HOLA DE NX6ED 1 0 0.0 >> >>102000 7 -19 1.875 -3 3* R4EJB3OR4J 1 0 0.0 >> >>102100 14 -16 1.883 -3 3* AQUI LU4FRH 1 0 0.0 >> >>011000 2 40/48 >> >>102200 3 -22 1.870 -3 3* LX0OHB-4M2196 1 0 0.0 >> >>102300 9 -20 1.911 -3 3* 139V244A -7C 1 0 0.0 >> >>102400 10 -15 1.914 -3 3* 73 DE KR0SIV 1 0 0.0 >> >>102500 7 -21 1.941 -3 3* RAN?A3UIEW 1 0 0.0 >> >>102600 11 -17 1.940 -3 3* N4PDY PEACE 1 0 0.0 >> >>102700 6 -23 1.761 -5 4* LX0OHB-4M2197 1 0 0.0 >> >>102800 10 -17 1.769 -5 0* 142V241A -7C 1 0 0.0 >> >>102900 5 -21 1.768 -5 4* 73 DE K4RTS 1 0 0.0 >> >>103000 4 -24 1.773 -3 4* R4EPF3M Y5 1 0 0.0 >> >>103100 13 -19 1.780 -3 3* QRV DE WA8MCD 1 0 0.0 >> >>103200 3 -21 1.756 -5 4* LX0OHB-4M2198 1 0 0.0 >> >>103300 11 -18 1.794 -5 1* 139V244A -7C 1 0 0.0 >> >>103400 9 -16 1.798 -5 3* 73 DE AA7EE 1 0 0.0 >> >>103500 6 -21 1.791 -5 3* RAOFA3UIGI 1 0 0.0 >> >>103600 7 -19 1.807 -5 3* 73 DE N8ABW 1 0 0.0 >> >>103700 10 -17 1.803 -5 3* LX0OHB-4M2199 1 0 0.0 >> >>103800 8 -20 1.842 -5 3* 139V244A -6C 1 0 0.0 >> >> >> >>Attilio, >> >> >> >>Last 25minute decodes: >> >> >> >>101300 6 -22 1.805 -3 3* 139V244A -7C 1 0 0.0 >> >>101400 6 -18 1.813 -3 3* 73 DE N0BML 1 0 0.0 >> >>101500 11 -17 1.822 -3 3* RAOBY3UIG5 1 0 0.0 >> >>101600 12 -19 1.825 -3 3* 73 DE K4CNM 1 0 0.0 >> >>101700 6 -18 1.835 -3 3* LX0OHB-4M2195 1 0 0.0 >> >>101800 9 -17 1.848 -3 3* 139V244A -7C 1 0 0.0 >> >>101900 9 -19 1.857 -3 3* HOLA DE NX6ED 1 0 0.0 >> >>102000 7 -19 1.875 -3 3* R4EJB3OR4J 1 0 0.0 >> >>102100 14 -16 1.883 -3 3* AQUI LU4FRH 1 0 0.0 >> >>102200 3 -22 1.870 -3 3* LX0OHB-4M2196 1 0 0.0 >> >>102300 9 -20 1.911 -3 3* 139V244A -7C 1 0 0.0 >> >>102400 10 -15 1.914 -3 3* 73 DE KR0SIV 1 0 0.0 >> >>102500 7 -21 1.941 -3 3* RAN?A3UIEW 1 0 0.0 >> >>102600 11 -17 1.940 -3 3* N4PDY PEACE 1 0 0.0 >> >>102700 6 -23 1.761 -5 4* LX0OHB-4M2197 1 0 0.0 >> >>102800 10 -17 1.769 -5 0* 142V241A -7C 1 0 0.0 >> >>102900 5 -21 1.768 -5 4* 73 DE K4RTS 1 0 0.0 >> >>103000 4 -24 1.773 -3 4* R4EPF3M Y5 1 0 0.0 >> >>103100 13 -19 1.780 -3 3* QRV DE WA8MCD 1 0 0.0 >> >>103200 3 -21 1.756 -5 4* LX0OHB-4M2198 1 0 0.0 >> >>103300 11 -18 1.794 -5 1* 139V244A -7C 1 0 0.0 >> >>103400 9 -16 1.798 -5 3* 73 DE AA7EE 1 0 0.0 >> >>103500 6 -21 1.791 -5 3* RAOFA3UIGI 1 0 0.0 >> >>103600 7 -19 1.807 -5 3* 73 DE N8ABW 1 0 0.0 >> >>103700 10 -17 1.803 -5 3* LX0OHB-4M2199 1 0 0.0 >> >> >> >>Client restarted. >> >> >> >> >> >>cid:image001.png@01CFF54B.0BA579A0 >> >> >> >> >> >>Still no go! >> >> >> >>Hope this helps. >> >> >> >>George >> >> VK4AMG >> >> >> >>Note because of DT and want to use MAP65, PC is GPS timesync’d to -10 sec >> >> >> >> >> >> >> >> >> >> >> >> >> >>Attilio, >> >> >> >>I understand the requirement of the client. >> >> >> >>I was keen to provide access to the All.txt to allow realtime upload to the warehouse. >> >> >> >>However the client never proceeds past “Waiting for new packet”. >> >> >> >>I see there has been some comment on “blogs” that the client needs to determine the sequence and find the start of sequence before uploading packets. >> >> >> >>Under the QSB environment that most have experienced this means the client never starts to transfer. >> >> >> >>Tonight is the first time I have seen 100% decode in any 5 or more sequences. >> >> >> >>I regret that this seems to have been an unexpected limitation by the developers of the Client. >> >> >> >>Problems also arose due to the received frequency (Doppler and frequency stability issues) and the timing issues, up to 12 seconds DT. Neither WSJT or MAP65 were intended to operate in this envelope. >> >> >> >>I have alternatively uploaded audio files as soon as possible. I however have no idea whether you decode near realtime of whether these contribute to the data warehouse. >> >> >> >>Regardless of this and my late introduction to the project, I have, like many others, enjoyed using my EME station outside its specification to track and decode the 4M project “satellite”. >> >> >> >>Thanks for your comments. Thanks for the opportunity to participate. >> >> >> >>Best 73 >> >> >> >>George >> >> VK4AMG >> >> >> >>PS: my background outlined on my QRZ.com page. >> >> >> >> >> >> >> >> >> >>From: Attilio Pier Paolo Pannella [mailto:attilio.pannella@lsespace.com] >>Sent: Friday, 31 October 2014 5:56 PM >>To: 'George VK4AMG' >>Cc: Ghislain Ruy-Longépé; moon-net-bounces(a)mailman.pe1itr.com; 'Moon'; moon-net(a)nlsa.com; k1jt(a)arrl.net; nick priborsky >>Subject: Re: [Moon-Net] 4M: update of trajectory >> >> >> >>Dear George >>I am sorry to hear about the frustration you've been facing lately. >>I am here to provide you with some explanation about the 4M client as unfortunately I think there has been some confusion about it. >>The main purpose of this client is to get JT65B messages as they are received from WSJT and provide them to the data warehouse. >>Once the client gets a message, it has to mark its sequence type/number and send this information along with other information and the message itself to the data warehouse. >>This way users can check on their side the information they are submitting and we are getting information in near real time, to allow LuxSpace to process them as they are available. This way LuxSpace can check radiation experiment data or estimate the battery life and so on, without having to wait the availability of the ALL.TXT files from the OMs supporting the project at the end of the day. >>Moreover the client allow users to easily upload audio files which are also very important for the project. >>Unfortunately, though, I think there has been some confusion on the way the 4M client works, that is, the client relies on the decoded.txt file to retrieve messages from WSJT as they are decoded, but it neither gets JT65B messages from ALL.TXT nor sends this file to LuxSpace. >>The ALL.TXT files have to be send to LuxSpace manually via email as it has been requested for the contest. >>If you are referring about the fact that the client does keep messages to be delivered in Waiting... status, I posted an explanation of this on our blog as Ghislain pointed out. >>I understand that some more functionalities from the 4M client would have been nice and appreciated (as the automatic deliver of ALL.TXT files) and others might have been differently implemented, but this client and the data warehouse have both been developed in short times keeping in mind near-realtime approaches, and we are very proud of what we achieved and delivered during this time. >>I hope this clarifies some of the issues you have been facing. >> >>I take advantage of this email to thank you for your precious support and your reports. >> >>Vy 73 de Attilio - DL1UNX >> >> >> >>On 31/10/14 04:37, Ghislain Ruy-Longépé wrote: >> >>Dear George, >> >>Indeed, the clock drift is quite annoying, but so much ingenuity was put everywhere to solve the problem that it is amazing. >> >>We cannot solve the 4M client problem. The explanation has been published by LSE space on our blog. >> >>We all thank you and many others for all your efforts and endeavor. >> >>I try to reply to every single OM individually, quite an overwhelming task, we could not foresee such a success and interest. >> >>Thanks for AOS and LOS information, that allowed me to confirm the trajectory after the flyby. We are on the +1 sigma side of the dispersion, this also shows the performances of the LM3-C launcher. (the venting out of the tanks after the Chang'e 5T1 separation gave us an additional impulse, that was purposedly oriented in the right direction for 4M) >> >>Best 73 lx2rg >> >> >> >>-----Original Message----- >>From: George VK4AMG [mailto:vk4amg@gmail.com] >>Sent: vendredi 31 octobre 2014 00:54 >>To: 'Ghislain Ruy-Longépé'; moon-net-bounces(a)mailman.pe1itr.com; 'Moon'; moon-net(a)nlsa.com >>Cc: k1jt(a)arrl.net >>Subject: RE: [Moon-Net] 4M: update of trajectory >> >>Ghislain, >> >>Yesterday was an interesting but initially frustrating day of receiving the 4M messages. >> >>In addition to using a FuncubePro to WSJT10, I have been receiving on MAP65 from an IQ+. Both receivers are fed from a splitter in the shack, MHLNA, and 4x 7el DK7ZB AZEL array. >> >>My computer is time locked with a Bluetooth GPS and a homebrew (VB6) application. MAP65 refused to decode once the DT went beyond 10secs. >> >>4M rose in QG62 around 0000Z. >> >>In order to maintain the dual receiving environment, I shifted the WSJT10 to a eeePC netbook (a snail in a black plastic case). The hope was to maintain time accuracy for audio file for upload while I sorted the MAP65 problem. >> >>Due to earth induced noise on the audio feed to the eeePC, I found it necessary to shift the Funcube freq by 500hz. >> >>After modifying my GPS time sync application to shift the PC time by 10 seconds, MAP65 didn't know the difference and happily resumed decoding. >> >>Sadly home pressures meant I was not able to upload as many audio files as I would have liked. The 4M client still refuses to parse and upload my ALL.txt file even on eeePC and a Win8 PC looking at the eeePC audio files as a network drive. >> >>After 4M set (1308Z), I merged the files from the 3 decode logs. This was a much bigger job than I expected due to the frequency offset and the differing file formats from MAP65 and the two WSJT instances running under different operating systems (W7 and W8). The latter was not anticipated. >> >>You will see, by the timestamp on my log submission email, it was very late (actually early) before the day's results (13 hours approx) were submitted. >> >>I found the tracking information to be accurate. As I do not have automated tracking (yet) and due to the uncertainty of the trajectory, I continued to search when I could. >> >>The trajectory in the last 6 hours required little adjustment of the antenna position, and thus there was some relief for the domestic situation (grandkid school dropoff, pickup and minding day). >> >>Best 73 >> >>George >> VK4aAMG >> >>-----Original Message----- >>From: moon-net-bounces(a)mailman.pe1itr.com [mailto:moon-net-bounces@mailman.pe1itr.com] On Behalf Of Ghislain Ruy-Longépé >>Sent: Friday, 31 October 2014 12:52 AM >>To: moon-net-bounces(a)mailman.pe1itr.com; 'Moon'; moon-net(a)nlsa.com >>Subject: [Moon-Net] 4M: update of trajectory >> >>Dear All, >> >>Please use the AFTER_HIGH.txt TLE. You can find it here: >>https://cloud.luxspace.lu/public.php?service=files<https://cloud.luxspace.lu/public.php?service=files&t=d620fe27918fe6aa728658…> &t=d620fe27918fe6aa72865817d8f1b8de >> >>Alternatively, our tracking webpage will be updated in a few minutes. >> >>73 >>Lx2rg >> >>-----Original Message----- >>From: Jean-Baptiste Frappé [mailto:frappe@luxspace.lu] >>Sent: jeudi 30 octobre 2014 09:39 >>To: Ghislain Ruy-Longépé; 'Allan Saul'; moon-net-bounces(a)mailman.pe1itr.com; Moon; wbauer(a)pt.lu; lx1db(a)rlx.lu; Bart Van Schie >>Subject: RE: AOS in JF96fd >> >>OK, will try these tracking orientations during the pass of today. >>Regards, >> >>Jean-Baptiste >> >> >> >>Jean-Baptiste FRAPPE >>LuxSpace Sàrl – Space Systems Engineer >>SES Business Center, >>9, rue Pierre Werner, L-6832 Betzdorf, Luxembourg >>Phone: +352 267890 8048 >>Fax: +352 267890 4049 >> >>-----Original Message----- >>From: Ghislain Ruy-Longépé [mailto:ruygh@yahoo.fr] >>Sent: 30 October 2014 8:45 AM >>To: 'Allan Saul'; moon-net-bounces(a)mailman.pe1itr.com; Moon; wbauer(a)pt.lu; lx1db(a)rlx.lu; Jean-Baptiste Frappé; Bart Van Schie >>Subject: RE: AOS in JF96fd >> >>Dear Allan, >> >>I made simulation and it seems that AFTERHIGH.txt tle is the best match to your observation. >> >>Can you tell me what is the altitude of your QTH and the height of the antenna AG ? >> >>The TLE set can be found in : >>https://cloud.luxspace.lu/public.php?service=files<https://cloud.luxspace.lu/public.php?service=files&t=33c4a21c09ba3736a55fc0…> &t=33c4a21c09ba3736a55fc09896e463f6 >> >> >>73 LX2RG >> >>-----Original Message----- >>From: Allan Saul [mailto:allan@rfdesign.co.za] >>Sent: jeudi 30 octobre 2014 07:54 >>To: Ghislain Ruy-Longépé >>Subject: AOS in JF96fd >> >>Hi Ghislain, >> >>AOS early in JF96fd. >>Your TLE set predicted AOS at 0704z but I see a decode now at 0648.z Doppler is at 530Hz and that’s with the IC-910 set to 145.980 USB. >> >>73 Allan ZS1LS >> >>------------------------------- >>LuxSpace Sàrl >>Registered Office: SES Business Center; 9, rue Pierre Werner; 6832 Betzdorf; LUXEMBOURG Board of Directors: Jochen Harms (Managing Director), Marco R. Fuchs, Oliver Salisch Registry Court Luxembourg: B104935 >>NAT-ID: 2004 2427 218 >>VAT-ID: LU20546250 >>IBLC: 20546250 >>This message and any attachments is intended solely for the addressee and is confidential. If you receive this message in error, please delete it and immediately notify the sender. >>Any use not in accordance with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except LuxSpace formal approval. >>The internet cannot guarantee the integrity of this message. LuxSpace and its sister companies will not be liable for the message if modified. >> >>_______________________________________________ >>Moon-Net posting and subscription instructions are at http://www.nlsa.com/nets/moon-net-help.html >> >> >> >> >> >>-- >>Attilio Pannella >>System Engineer >> >>LSE Space GmbH >>Argelsrieder Feld 22 >>82234 - Wessling - Germany >>Tel: +49 (0) 8153.881.099.21 >>Fax: +49 (0) 8153.881.099.15 >> >>LSE Space GmbH >>Argelsrieder Feld 22, D-82234 Wessling, Germany >>Geschäftsführer: Daniel Gestal, Nicholas Priborsky >>Registergericht: Amtsgericht München >>Register-Nr.: HRB 195494 >> > >_______________________________________________ >Moon-Net posting and subscription instructions are at http://www.nlsa.com/nets/moon-net-help.html

8 years, 7 months

Re: [Moon-Net] 4M: update of trajectory - thanks

by rein0zn＠ix.netcom.com

Hi George, If I may ask you, what are you using now as an antenna? $ * 3 WL ? Looking to your RX results it appears you doing 2-3 dB better than I seem to be doing with my HB 3 wl LFA. That extra gain makes quite a bit of difference on the bottom line of course! 73 Rein W6SZ -----Original Message----- >From: George VK4AMG <vk4amg(a)gmail.com> >Sent: Oct 31, 2014 10:43 AM >To: 'Attilio Pier Paolo Pannella' <attilio.pannella(a)lsespace.com> >Cc: moon-net(a)nlsa.com, 'Moon' <Moon(a)luxspace.lu>, moon-net-bounces(a)mailman.pe1itr.com, 'nick priborsky' <nick.priborsky(a)lsespace.com>, k1jt(a)arrl.net, 'Ghislain Ruy-Longépé' <ruygh(a)yahoo.fr> >Subject: Re: [Moon-Net] 4M: update of trajectory - thanks > > > >UTC Date: 2014 Oct 30 > > > > > > > >................................................ > > > > > > > >101300 6 -22 1.805 -3 3* 139V244A -7C 1 0 0.0 > >101400 6 -18 1.813 -3 3* 73 DE N0BML 1 0 0.0 > >101500 11 -17 1.822 -3 3* RAOBY3UIG5 1 0 0.0 > >101600 12 -19 1.825 -3 3* 73 DE K4CNM 1 0 0.0 > >101700 6 -18 1.835 -3 3* LX0OHB-4M2195 1 0 0.0 > >101800 9 -17 1.848 -3 3* 139V244A -7C 1 0 0.0 > >101900 9 -19 1.857 -3 3* HOLA DE NX6ED 1 0 0.0 > >102000 7 -19 1.875 -3 3* R4EJB3OR4J 1 0 0.0 > >102100 14 -16 1.883 -3 3* AQUI LU4FRH 1 0 0.0 > >011000 2 40/48 > >102200 3 -22 1.870 -3 3* LX0OHB-4M2196 1 0 0.0 > >102300 9 -20 1.911 -3 3* 139V244A -7C 1 0 0.0 > >102400 10 -15 1.914 -3 3* 73 DE KR0SIV 1 0 0.0 > >102500 7 -21 1.941 -3 3* RAN?A3UIEW 1 0 0.0 > >102600 11 -17 1.940 -3 3* N4PDY PEACE 1 0 0.0 > >102700 6 -23 1.761 -5 4* LX0OHB-4M2197 1 0 0.0 > >102800 10 -17 1.769 -5 0* 142V241A -7C 1 0 0.0 > >102900 5 -21 1.768 -5 4* 73 DE K4RTS 1 0 0.0 > >103000 4 -24 1.773 -3 4* R4EPF3M Y5 1 0 0.0 > >103100 13 -19 1.780 -3 3* QRV DE WA8MCD 1 0 0.0 > >103200 3 -21 1.756 -5 4* LX0OHB-4M2198 1 0 0.0 > >103300 11 -18 1.794 -5 1* 139V244A -7C 1 0 0.0 > >103400 9 -16 1.798 -5 3* 73 DE AA7EE 1 0 0.0 > >103500 6 -21 1.791 -5 3* RAOFA3UIGI 1 0 0.0 > >103600 7 -19 1.807 -5 3* 73 DE N8ABW 1 0 0.0 > >103700 10 -17 1.803 -5 3* LX0OHB-4M2199 1 0 0.0 > >103800 8 -20 1.842 -5 3* 139V244A -6C 1 0 0.0 > > > >Attilio, > > > >Last 25minute decodes: > > > >101300 6 -22 1.805 -3 3* 139V244A -7C 1 0 0.0 > >101400 6 -18 1.813 -3 3* 73 DE N0BML 1 0 0.0 > >101500 11 -17 1.822 -3 3* RAOBY3UIG5 1 0 0.0 > >101600 12 -19 1.825 -3 3* 73 DE K4CNM 1 0 0.0 > >101700 6 -18 1.835 -3 3* LX0OHB-4M2195 1 0 0.0 > >101800 9 -17 1.848 -3 3* 139V244A -7C 1 0 0.0 > >101900 9 -19 1.857 -3 3* HOLA DE NX6ED 1 0 0.0 > >102000 7 -19 1.875 -3 3* R4EJB3OR4J 1 0 0.0 > >102100 14 -16 1.883 -3 3* AQUI LU4FRH 1 0 0.0 > >102200 3 -22 1.870 -3 3* LX0OHB-4M2196 1 0 0.0 > >102300 9 -20 1.911 -3 3* 139V244A -7C 1 0 0.0 > >102400 10 -15 1.914 -3 3* 73 DE KR0SIV 1 0 0.0 > >102500 7 -21 1.941 -3 3* RAN?A3UIEW 1 0 0.0 > >102600 11 -17 1.940 -3 3* N4PDY PEACE 1 0 0.0 > >102700 6 -23 1.761 -5 4* LX0OHB-4M2197 1 0 0.0 > >102800 10 -17 1.769 -5 0* 142V241A -7C 1 0 0.0 > >102900 5 -21 1.768 -5 4* 73 DE K4RTS 1 0 0.0 > >103000 4 -24 1.773 -3 4* R4EPF3M Y5 1 0 0.0 > >103100 13 -19 1.780 -3 3* QRV DE WA8MCD 1 0 0.0 > >103200 3 -21 1.756 -5 4* LX0OHB-4M2198 1 0 0.0 > >103300 11 -18 1.794 -5 1* 139V244A -7C 1 0 0.0 > >103400 9 -16 1.798 -5 3* 73 DE AA7EE 1 0 0.0 > >103500 6 -21 1.791 -5 3* RAOFA3UIGI 1 0 0.0 > >103600 7 -19 1.807 -5 3* 73 DE N8ABW 1 0 0.0 > >103700 10 -17 1.803 -5 3* LX0OHB-4M2199 1 0 0.0 > > > >Client restarted. > > > > > >cid:image001.png@01CFF54B.0BA579A0 > > > > > >Still no go! > > > >Hope this helps. > > > >George > > VK4AMG > > > >Note because of DT and want to use MAP65, PC is GPS timesync’d to -10 sec > > > > > > > > > > > > > >Attilio, > > > >I understand the requirement of the client. > > > >I was keen to provide access to the All.txt to allow realtime upload to the warehouse. > > > >However the client never proceeds past “Waiting for new packet”. > > > >I see there has been some comment on “blogs” that the client needs to determine the sequence and find the start of sequence before uploading packets. > > > >Under the QSB environment that most have experienced this means the client never starts to transfer. > > > >Tonight is the first time I have seen 100% decode in any 5 or more sequences. > > > >I regret that this seems to have been an unexpected limitation by the developers of the Client. > > > >Problems also arose due to the received frequency (Doppler and frequency stability issues) and the timing issues, up to 12 seconds DT. Neither WSJT or MAP65 were intended to operate in this envelope. > > > >I have alternatively uploaded audio files as soon as possible. I however have no idea whether you decode near realtime of whether these contribute to the data warehouse. > > > >Regardless of this and my late introduction to the project, I have, like many others, enjoyed using my EME station outside its specification to track and decode the 4M project “satellite”. > > > >Thanks for your comments. Thanks for the opportunity to participate. > > > >Best 73 > > > >George > > VK4AMG > > > >PS: my background outlined on my QRZ.com page. > > > > > > > > > >From: Attilio Pier Paolo Pannella [mailto:attilio.pannella@lsespace.com] >Sent: Friday, 31 October 2014 5:56 PM >To: 'George VK4AMG' >Cc: Ghislain Ruy-Longépé; moon-net-bounces(a)mailman.pe1itr.com; 'Moon'; moon-net(a)nlsa.com; k1jt(a)arrl.net; nick priborsky >Subject: Re: [Moon-Net] 4M: update of trajectory > > > >Dear George >I am sorry to hear about the frustration you've been facing lately. >I am here to provide you with some explanation about the 4M client as unfortunately I think there has been some confusion about it. >The main purpose of this client is to get JT65B messages as they are received from WSJT and provide them to the data warehouse. >Once the client gets a message, it has to mark its sequence type/number and send this information along with other information and the message itself to the data warehouse. >This way users can check on their side the information they are submitting and we are getting information in near real time, to allow LuxSpace to process them as they are available. This way LuxSpace can check radiation experiment data or estimate the battery life and so on, without having to wait the availability of the ALL.TXT files from the OMs supporting the project at the end of the day. >Moreover the client allow users to easily upload audio files which are also very important for the project. >Unfortunately, though, I think there has been some confusion on the way the 4M client works, that is, the client relies on the decoded.txt file to retrieve messages from WSJT as they are decoded, but it neither gets JT65B messages from ALL.TXT nor sends this file to LuxSpace. >The ALL.TXT files have to be send to LuxSpace manually via email as it has been requested for the contest. >If you are referring about the fact that the client does keep messages to be delivered in Waiting... status, I posted an explanation of this on our blog as Ghislain pointed out. >I understand that some more functionalities from the 4M client would have been nice and appreciated (as the automatic deliver of ALL.TXT files) and others might have been differently implemented, but this client and the data warehouse have both been developed in short times keeping in mind near-realtime approaches, and we are very proud of what we achieved and delivered during this time. >I hope this clarifies some of the issues you have been facing. > >I take advantage of this email to thank you for your precious support and your reports. > >Vy 73 de Attilio - DL1UNX > > > >On 31/10/14 04:37, Ghislain Ruy-Longépé wrote: > >Dear George, > >Indeed, the clock drift is quite annoying, but so much ingenuity was put everywhere to solve the problem that it is amazing. > >We cannot solve the 4M client problem. The explanation has been published by LSE space on our blog. > >We all thank you and many others for all your efforts and endeavor. > >I try to reply to every single OM individually, quite an overwhelming task, we could not foresee such a success and interest. > >Thanks for AOS and LOS information, that allowed me to confirm the trajectory after the flyby. We are on the +1 sigma side of the dispersion, this also shows the performances of the LM3-C launcher. (the venting out of the tanks after the Chang'e 5T1 separation gave us an additional impulse, that was purposedly oriented in the right direction for 4M) > >Best 73 lx2rg > > > >-----Original Message----- >From: George VK4AMG [mailto:vk4amg@gmail.com] >Sent: vendredi 31 octobre 2014 00:54 >To: 'Ghislain Ruy-Longépé'; moon-net-bounces(a)mailman.pe1itr.com; 'Moon'; moon-net(a)nlsa.com >Cc: k1jt(a)arrl.net >Subject: RE: [Moon-Net] 4M: update of trajectory > >Ghislain, > >Yesterday was an interesting but initially frustrating day of receiving the 4M messages. > >In addition to using a FuncubePro to WSJT10, I have been receiving on MAP65 from an IQ+. Both receivers are fed from a splitter in the shack, MHLNA, and 4x 7el DK7ZB AZEL array. > >My computer is time locked with a Bluetooth GPS and a homebrew (VB6) application. MAP65 refused to decode once the DT went beyond 10secs. > >4M rose in QG62 around 0000Z. > >In order to maintain the dual receiving environment, I shifted the WSJT10 to a eeePC netbook (a snail in a black plastic case). The hope was to maintain time accuracy for audio file for upload while I sorted the MAP65 problem. > >Due to earth induced noise on the audio feed to the eeePC, I found it necessary to shift the Funcube freq by 500hz. > >After modifying my GPS time sync application to shift the PC time by 10 seconds, MAP65 didn't know the difference and happily resumed decoding. > >Sadly home pressures meant I was not able to upload as many audio files as I would have liked. The 4M client still refuses to parse and upload my ALL.txt file even on eeePC and a Win8 PC looking at the eeePC audio files as a network drive. > >After 4M set (1308Z), I merged the files from the 3 decode logs. This was a much bigger job than I expected due to the frequency offset and the differing file formats from MAP65 and the two WSJT instances running under different operating systems (W7 and W8). The latter was not anticipated. > >You will see, by the timestamp on my log submission email, it was very late (actually early) before the day's results (13 hours approx) were submitted. > >I found the tracking information to be accurate. As I do not have automated tracking (yet) and due to the uncertainty of the trajectory, I continued to search when I could. > >The trajectory in the last 6 hours required little adjustment of the antenna position, and thus there was some relief for the domestic situation (grandkid school dropoff, pickup and minding day). > >Best 73 > >George > VK4aAMG > >-----Original Message----- >From: moon-net-bounces(a)mailman.pe1itr.com [mailto:moon-net-bounces@mailman.pe1itr.com] On Behalf Of Ghislain Ruy-Longépé >Sent: Friday, 31 October 2014 12:52 AM >To: moon-net-bounces(a)mailman.pe1itr.com; 'Moon'; moon-net(a)nlsa.com >Subject: [Moon-Net] 4M: update of trajectory > >Dear All, > >Please use the AFTER_HIGH.txt TLE. You can find it here: >https://cloud.luxspace.lu/public.php?service=files <https://cloud.luxspace.lu/public.php?service=files&t=d620fe27918fe6aa728658…> &t=d620fe27918fe6aa72865817d8f1b8de > >Alternatively, our tracking webpage will be updated in a few minutes. > >73 >Lx2rg > >-----Original Message----- >From: Jean-Baptiste Frappé [mailto:frappe@luxspace.lu] >Sent: jeudi 30 octobre 2014 09:39 >To: Ghislain Ruy-Longépé; 'Allan Saul'; moon-net-bounces(a)mailman.pe1itr.com; Moon; wbauer(a)pt.lu; lx1db(a)rlx.lu; Bart Van Schie >Subject: RE: AOS in JF96fd > >OK, will try these tracking orientations during the pass of today. >Regards, > >Jean-Baptiste > > > >Jean-Baptiste FRAPPE >LuxSpace Sàrl – Space Systems Engineer >SES Business Center, >9, rue Pierre Werner, L-6832 Betzdorf, Luxembourg >Phone: +352 267890 8048 >Fax: +352 267890 4049 > >-----Original Message----- >From: Ghislain Ruy-Longépé [mailto:ruygh@yahoo.fr] >Sent: 30 October 2014 8:45 AM >To: 'Allan Saul'; moon-net-bounces(a)mailman.pe1itr.com; Moon; wbauer(a)pt.lu; lx1db(a)rlx.lu; Jean-Baptiste Frappé; Bart Van Schie >Subject: RE: AOS in JF96fd > >Dear Allan, > >I made simulation and it seems that AFTERHIGH.txt tle is the best match to your observation. > >Can you tell me what is the altitude of your QTH and the height of the antenna AG ? > >The TLE set can be found in : >https://cloud.luxspace.lu/public.php?service=files <https://cloud.luxspace.lu/public.php?service=files&t=33c4a21c09ba3736a55fc0…> &t=33c4a21c09ba3736a55fc09896e463f6 > > >73 LX2RG > >-----Original Message----- >From: Allan Saul [mailto:allan@rfdesign.co.za] >Sent: jeudi 30 octobre 2014 07:54 >To: Ghislain Ruy-Longépé >Subject: AOS in JF96fd > >Hi Ghislain, > >AOS early in JF96fd. >Your TLE set predicted AOS at 0704z but I see a decode now at 0648.z Doppler is at 530Hz and that’s with the IC-910 set to 145.980 USB. > >73 Allan ZS1LS > >------------------------------- >LuxSpace Sàrl >Registered Office: SES Business Center; 9, rue Pierre Werner; 6832 Betzdorf; LUXEMBOURG Board of Directors: Jochen Harms (Managing Director), Marco R. Fuchs, Oliver Salisch Registry Court Luxembourg: B104935 >NAT-ID: 2004 2427 218 >VAT-ID: LU20546250 >IBLC: 20546250 >This message and any attachments is intended solely for the addressee and is confidential. If you receive this message in error, please delete it and immediately notify the sender. >Any use not in accordance with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except LuxSpace formal approval. >The internet cannot guarantee the integrity of this message. LuxSpace and its sister companies will not be liable for the message if modified. > >_______________________________________________ >Moon-Net posting and subscription instructions are at http://www.nlsa.com/nets/moon-net-help.html > > > > > >-- >Attilio Pannella >System Engineer > >LSE Space GmbH >Argelsrieder Feld 22 >82234 - Wessling - Germany >Tel: +49 (0) 8153.881.099.21 >Fax: +49 (0) 8153.881.099.15 > >LSE Space GmbH >Argelsrieder Feld 22, D-82234 Wessling, Germany >Geschäftsführer: Daniel Gestal, Nicholas Priborsky >Registergericht: Amtsgericht München >Register-Nr.: HRB 195494 >

8 years, 7 months

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Moon-net October 2014