10ghz – Page 2 – Daniel Estévez

Measuring the ED4YAE 10GHz beacon

Last week, the 10GHz beacon ED4YAE on Alto del León was installed again after having been off the air for quite some time (I think a couple of years). The beacon uses a 10MHz OCXO and a 500mW power amplifier, and transmits CW on 10368.862MHz. The message transmitted by the beacon is DE ED4YAE ED4YAE ED4YAE IN70WR30HX, followed by a 5.8 second long tone.

On 2019-08-31, I went to the countryside just outside my city, Tres Cantos, to receive the beacon and do some measurements. The measurements were done around 10:00 UTC from locator IN80DO68TW. The receiving equipment was a 60cm offset dish from diesl.es, an Avenger Ku band LNB, and a LimeSDR USB. Everything was locked to a 10MHz GPSDO. The dish was placed on a camera tripod at a height of approximately 1.5 metres above the ground.

In this post I show the results of my measurements.

Measuring the gain of a dish

Here I want to show a technique for measuring the gain of a dish that I first learned from an article by Christian Monstein about the Moon’s temperature at a wavelength of 2.77cm. The technique only uses power measurements from an observation of a radio source, at different angles from the boresight. Ideally, the radio source should be strong and point-like. It is also important that the angles at which the power measurements are made are known with good accuracy. This can be achieved either with a good rotator or by letting an astronomical object drift by on a dish that is left stationary.

Second Moon observation with my QO-100 station.

In May 25, the Moon passed through the beam of my QO-100 groundstation and I took the opportunity to measure the Moon noise and receive the Moonbounce 10GHz beacon DL0SHF. A few days ago, in July 22, the Moon passed again through the beam of the dish. This is interesting because, in contrast to the opportunity in May, where the Moon only got within 0.5º of the dish pointing, in July 22 the Moon passed almost through the nominal dish pointing. Also, incidentally this occasion has almost coincided with the 50th anniversary of the arrival to the Moon of Apollo 11, and all the activities organized worldwide to celebrate this event.

The figure below shows the noise measurement at 10366.5GHz with 1MHz and a 1.2m offset dish, compared with the angular separation between the Moon and the nominal pointing of the dish (defined as the direction from my station to Es’hail 2). The same recording settings as in the first observation were used here.

The first thing to note is that I made a mistake when programming the recording. I intended to make a 30 minute recording centred at the moment of closest approach, but instead I programmed the recording to start at the moment of closest approach. The LimeSDR used to make the recording was started to stream one hour before the recording, in order to achieve a stable temperature (this was one lesson I learned from my first observation).

The second comment is that the maximum noise doesn’t coincide with the moment when the Moon is closest to the nominal pointing. Luckily, this makes all the noise hump fit into the recording interval, but it means that my dish pointing is off. Indeed, the maximum happens when the Moon is 1.5º away from the nominal pointing, so my dish pointing error is at least 1.5º. I will try adjust the dish soon by peaking on the QO-100 beacon signal.

The noise hump is approximately 0.085dB, which is much better than the 0.05dB hump that I obtained in the first observation. It may not seem like much, but assuming the same noise in both observations, this is a difference of 2.32dB in the signal. This difference can be explained by the dish pointing error.

The recording I have made also covers the 10GHz Amateur EME band, but I have not been able to detect the signal of the DL0SHF beacon. Perhaps it was not transmitting when the recording was made. I have also arrived to the conclusion that the recording for my first observation had severe sample loss, as it was made on a mechanical hard drive. This explains the odd timing I detected in the DL0SHF signal.

The next observation is planned for October 11, but before this there is the Sun outage season between September 6 and 11, in which the Sun passes through the beam of the dish, so that Sun noise measurements can be performed.

First Moon observation with my QO-100 station

A month ago, I spoke about planning the passes of the Moon through the beam of my QO-100 station. These give an occasion to observe the Moon without moving a dish that is pointing to Es’hail 2. The next opportunity after writing that post was on May 16 at 20:16 UTC.

Since I wasn’t going to be at home at that time, I programmed my computer to make a recording for later analysis. I recorded 4MHz of spectrum centred at 10367.5MHz using a LimeSDR connected to the LNB that I use to receive QO-100. The recording was planned to be 30 minutes long starting at 20:01 UTC, but for some reason only approximately 27 minutes were recorded.

This kind of events can be used to measure Moon noise and receive 10GHz EME signals. This post is an analysis of my recording, looking at these two things.

Planning Moon observations with my QO-100 station

There is a saying that goes like “even a broken clock is right twice a day”. In the same spirit, even a QO-100 station, which is installed with a fixed dish aiming to Es’hail 2, can sometimes be used for observing the Moon, as it happens to pass in front of the beam.

My station has a 1.2m offset dish with a GPSDO disciplined LNB. There are a few things that can be done when the Moon passes in front of the beam of the dish, such as measuring moon noise (though the increase in noise is only of around 10K with such a small dish), or receiving the 10GHz EME beacon or other EME stations. Therefore, it is interesting to know when these events happen, in order to prepare the observations.

I have made a simple Jupyter notebook that uses Astropy to compute the moments when the moon will pass through the beam of the dish (say, closer than 1º to the position of Es’hail 2 in the sky). Of course, the results are highly dependent on the location of the groundstation, so these are only valid for my groundstation and perhaps other groundstations in Madrid. Other people can run this notebook again using their data.

It turns out that each year the Moon passes roughly a dozen times in front of the dish beam. The next observation for me is on May 16. The separation in degrees between the centre of the Moon and the centre of the dish beam can be seen in the figure below.

This notebook can be used to plan for transits of other astronomical objects, but besides the Moon and the Sun, there are no other objects that are visible at 10GHz with a small dish. It is well known when the Sun passes in front of the beam, since this disturbs communications with GEO satellites. This is called Sun outage and it happens during a few days around the equinoxes (a few weeks sooner or later, depending on the latitude of the station). On the other hand, the transits of the Moon happen throughout the whole year, at rather unpredictable moments, so I think this notebook is quite useful to plan observations.

Rain fade in the QO-100 downlink

The Amateur transponders of Es’hail 2 have their downlink in the 10GHz Amateur band. Even though the path to the satellite through the atmosphere is rather short, in extreme weather conditions it is possible to observe a small amount of fading in the signal. Two days ago there was intense rain over Madrid. As I’m often recording the power of the narrowband transponder beacons and the transponder noise floor, I have examined my data to see if the effect of the rain is visible.

The data is plotted in the figure below. See this post for an explanation of the measurements.

The power of the beacons is not very stable. It can vary up to 2 or 3dB along the course of the day. Therefore, it is not so easy to measure the drop in signal power caused by rain. However, it is noticeable that on April 24, between 05:00 and 17:00 UTC, the power of the beacons varies much more rapidly than usually. A small ripple of 0.5dB of amplitude is visible on the data. I think that this ripple is caused by varying rain intensity. Therefore, the data seems to suggest that the rains two days ago caused up to 0.5dB of fading in the signal.

As seen from my station, the satellite is at an elevation of \(\theta = 33.6^\circ\), so assuming a slant factor of \(1/\sin \theta = 1.8\), so taking a typical height of around 1km for the column of rain (see the corresponding METAR for Madrid airport), we get an attenuation on the order of 0.3dB/km. However, all the measurements used here are too imprecise to obtain any good conclusions. See this related post, in which I measured a 2.5dB increase in the noise floor at 12GHz during a hailstorm, but no change in signal power.

New dish for Es’hail 2 reception

I have replaced the dish I had for receiving Es’hail 2 by a new one. The former dish was a 95cm offset from diesl.es which was a few years old. I had previously used this dish for portable experiments, and it had been lying on an open balcony for many months until I finally installed it in my garden, so it wasn’t in very good shape.

Comparing with other stations in Spain, I received less transponder noise from the narrowband transponder of QO-100 than other stations. Doing some tests, I found out that the dish was off focus. I could get an improvement of 4dB or so by placing the LNB a bit farther from the dish. This was probably caused by a few hits that the dish got while using it portable. Rather than trying to fix this by modifying the arm (as the LNB couldn’t be held in this position), I decided to buy a new dish.

QO-100 beacons power

In the QO-100 (Es’hail 2) narrow band transponder, the recommendation for the adjustment of your downlink signal power is not to be stronger than the beacon. This was also the recommended usage of the old AO-40. Since the transponder has two beacons marking the transponder edges: a CW beacon marking the lower edge and a 400baud BPSK beacon marking the upper edge, there has been some debate on Twitter about which beacon does this recommendation refer to and what does “stronger” mean.

Of course, more formally, signal strength means power, which is a well defined physical concept, so there should be no argument about what does power mean. However, there are two different power measurements used for RF: average power and peak envelope power. I will assume that the recommendation refers to average power, not to peak envelope power. This makes more sense from the point of view of the power budget of the satellite amplifier (The total average power it needs to deliver is just the sum of the average powers of the signals of all the users, while the behaviour of the peak envelope power is much more complicated).

Also, I think that using peak envelope power for this restriction would be a very strict requirement on high PAPR signals. Note that the PAPR of CW is 0dB and the PAPR of BPSK is between 2 and 3dB, depending on the pulse shaping, so these are rather low PAPRs. For comparison, a moderately compressed SSB voice signal has a PAPR of 6dB.

In my opinion, the main problem with these discussions about “signal strength” is that many people are trying to judge power by looking at their waterfall or spectrum display and seeing what signal looks “higher”. This kind of measurement is not any good, because it doesn’t take signal bandwidth into account, depends on the FFT size, the window function, etc. It doesn’t help that many popular SDR software don’t have a good signal meter displaying the average power of the signal tuned in the passband.

In any case, I was curious about whether the power of the two beacons is the same and whether there is any interesting change over time. I have made a GNU Radio flowgraph that measures the power of each of the two beacons and of the transponder noise, and saves them to a file for later analysis.

In-orbit testing of Es’hail 2 Amateur transponders

Yesterday, December 23, MELCO carried out some in-orbit tests of the Es’hail 2 Amateur radio transponders. Since Es’hail 2 is currently under commissioning, it was expected that at some point the Amateur transponders would be activated for testing, but no announcement of the tests was done in advance. At around 11:00 UTC, Rob Janssen PE1CHL, noticed that the narrowband transponder was active and a carrier signal was being transmitted through it.

Since then, I monitored most of the tests and sent updates on Twitter, together with other people (see also the posts in the AMSAT-DL forum). Without knowing the details of the test plans, we limited ourselves to watching and following the tests that were being made. If some schedule of the tests had been published in advanced, we could have thought, prepared and performed some interesting measurements on the downlink signals.

I understand that since these tests are carried out by MELCO, AMSAT-DL might not have the specific details, but still I think that AMSAT-DL is publishing very little information about Es’hail 2 events. It was only at 22:35 UTC that AMSAT-DL published a small note on Twitter about the tests. I think the greatest concern is that people start transmitting through the transponder, interfering with the tests. However, since news spread very fast these days through social media, I think that publishing more information rather than keeping things discreetly serves better to prevent people from using the transponder during the commissioning. In any case, I’ll repeat it here:

Es’hail 2 is currently under commissioning. The 2.4GHz uplink of the Amateur transponders should never be used until authorized by AMSAT-DL. The Amateur transponders will sometimes be enabled for in-orbit testing by the MELCO/Es’hailSat/AMSAT-DL engineers. Relax, sit back, and watch the tests on the 10GHz downlink.

I also think that publishing more information would be beneficial to educate the community of radio Amateurs. Some people have asked me about the concept of in-orbit tests. After a satellite is launched into orbit, the performance of all its systems is tested to ensure that it matches design specifications, simulations, and pre-launch tests done on ground. This is important to guarantee that any problems, malfunction or damage that occurred during the launch can be diagnosed and hopefully mitigated by activating backup systems or other reliability measures. In-orbit testing of large satellites can take several months, since there are many complex systems that need to be tested remotely.

In the case of the Amateur radio payload of Es’hail 2, MELCO is carrying out the tests, since the payload was built by MELCO according to the design specifications by AMSAT-DL. The kind of tests they are performing are related to the performance of the bent-pipe transponders. They sweep in frequency the transponders to make sure that the passband shape is as expected. They transmit carriers of different power levels to check for linearity of the transponder and AGC performance, and they try different gain/power level settings of the transponder power amplifier to make sure it performs correctly over all its working range.

This is a rough account of the tests that were made yesterday, using my tweets as a sort of activity log.

Improving phase noise performance of the DF9NP 27MHz PLL

In some of the latest posts, I’ve being talking about the phase noise performance of 10GHz receivers, and in particular, of 27MHz references for Ku-band LNBFs (1, 2, 3, 4). Indeed, this started when I checked the performance of my new 10MHz GPSDO and 27MHz PLL by DF9NP and I wasn’t too happy with the phase noise.

After working with Dieter DF9NP in investigating this problem and performing several tests, Dieter found that the problem was likely in the loop bandwidth of the 27MHz PLL. The loop filter bandwidth is 50kHz. He proposed the following component modifications to change the bandwidth to 300Hz.

Update 2018-10-21: Dieter tells me that this problem has been solved in the new units he is selling, so the performance of the new units should be good.

Modification of the PLL loop (new values in red) — Modification of the PLL loop filter (new values in red)

After I performed the modifications, I was quite surprised and happy with the results. As always, I’ve used the beacon of BADR-5 at 11966.2MHz to test the phase noise performance. Linrad’s AFC is in use. The result is below. As you can see, it is as good as the best references that I had tested before.

For comparison, this was the performance before the modification. The difference is huge. Many thanks to Dieter for his effort and to Luis EA5DOM, who also participated in the discussion and gave some good advice.