And thanks to Martin, DM4IM for documenting and reporting this in the first place
And thanks to Martin, DM4IM for documenting and reporting this in the first place
The old QO-100 bandplan is still floating around on the internet (narrowband uplink: 2400.050 - 2400.300 MHz). I think the club chaps weren't aware of the transponder band expansion or the unusual nature of the transponder in general.
Easy mistake to make I think
Talked to one of the SK0EN chaps and they will shift the beacon up to 2400.800 MHz.
In the meantime it is QRT until then.
Somewhat sadly, my LHCP proposal didn't take fire
The frequency is quite logical, though unfortunate: SM lost their lower segment of 13cm and now only have some section above 2400 MHz. I will try to contact somebody over there, if only to suggest using an LHCP antenna for the beacon
Just to keep the thread alive, here is some info on my own implementation I have used successfully on several Venton EXL-S PLL LNB's. This particular model seems to still be available from several outlets and webshops (31.05.2021).
I had to transfer my website to a more reliable service provider, so here are the correct links to two other modification notes:
the triangular strip is propably fairly repeatable to produce without test gear, which is an obvious bonus.
Here is an old design I made for our Ilmari balloon project (weight around 40 grams) that uses an oblong shaped matching section (don't seem to have a plot of thre return loss, but it is around 20 dB for the 23cm ATV band):
Though I still prefer the bother of making the capacitive base wire loading for good broadband matching (the markers are at seemingly weird frequencies as I wanted to get an idea of the attenuation at these) :
Your connection is not secure
The owner of 73.fi has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.
the site is about as secure as possible (I am sure you did use https).
73.fi Overall Rating: A+
Your web browser must support SNI and use TLA 1.2 or TLS 1.3
Firefox version 31 will not work, but then the current version is 75...
Just in case somebody does not have immediate access to old articles and magazines, here is my writeup on AO-7 from, like, >20 years ago. I realize some of the links are now obsolete and need to overhaul this page sometime soonish. For me, the most important are the block diagrams of the transponder, especially the HELAPS transponder.
Things to do list: write an English Block Diagram...
I also really need to take some time to write something on the 2.3 GHz S band beacon that never got tested in orbit. But regardless, many thanks to the San Bernardino Microwave Society for supplying the flight hardware, eons ago.
Wrong thread and everything, but anyway
Modification proposal of older GM-201 for external referencing is now at:
Modification proposal of newer Golden Media Single for external referencing may be found at:
73 - Michael, OH2AUE
A dual band circularly polarized patch feed from the dungeons of Brno:
The very interesting thesis of OM Mirek, OK2AQ's student Aleš Maršálek may be found at:
(1270 & 2400 MHz RHCP 50Ω design for f/D of 0.4 to 0.5)
In particular, the evolution from a dual fed circularly polarized patch to a self-phasing CP patch is described in Chapter 4 with scetches of the underlying principles of dual resonances and related phasing in Figures 4.4a & b and 4.5. Otherwise there is a real lot of interesting detail in the work, but I do need to brush up my Czech somewhat
As ever, the true bible of radio engineering by Frederick Emmons Terman contains all the answers to all possible RF questions or at least the beginnings of them. Personally I prefer reading one of my original hard copies, but the 1937 edition is also downloadable at:
Figure 29 on page 56 tells it all.
Another quick duckduckgo and we have a fine example for 9 + 14 GHz: https://pdfs.semanticscholar.o…d980dbe87e13a74b35cc0.pdf
So linearly polarized 1200 + 1575 MHz should be a breeze.
Then there is always the option to stack two circularly polarized patches as in e.g. the ON6UG multiband contraption.
And Happy New Year
A couple of examples of commercial patches for the GPS L1 frequency:
Many of these commercial patches sub-perform, mostly because the design engineer will not read or implement the manufacturers instructions, especially regarding ground plane and weather protection dielectrics.
But sometimes these patches simply have not even been designed for RHCP: there are also models on the market, where dual frequency operation is claimed, one patch direction is tuned for one spot frequency and the orthogonal direction for the other.
Obviosly both are linearly polarized with the -3dB loss penalty.
But happily we mere radio amateurs are smarter
well, here in Finland we have this thing called "nollatutkimus", or zero-research, quite literally referring to putting effort into restudying something that has been evident for eons
Something like this, only this is on 7 MHz:
We all know that the polarisation ellipse of a correctly aligned POTY would on the polarimeter CRT be a perfect circle (when measured in a reflection free environment - here at the 62nd parallel north, snow melts and the garden dries to boot-comfort usually around April/May...).
Meanwhile, I am integrating a Trio CO-1303D oscilloscope into the system, more pleasing for the esthetic eye with it's vintage round CRT and all that
Trying to adhere to the topic:
From the TX viewpoint, for simple circularly polarized feeds one still needs to achieve splitting of the signal into two equal amplitude components with +-45 degrees shifts, i.e. two orthogonal fields from two virtual elements with impedances of 50+j50 ohms and 50-j50 ohms. Parallelly fed this results in a total feed impedance of 50+j0 ohms purely resistive.
These two resonances should be evident from the hardware when measuring with a VNA: there should clearly be both impedances with their relevant resonances, ideally symmetrically about the nominal center frequencies. Accomplishing all this with a simple feed plate, a single feed point and a single disturbance (the screw) is somewhat challenging and tough to replicate in a hardware duplicate. But with very tight manufactureing tolerances it IS possible over a very narrow frequency range (obviously). This is why it is so very difficult to copy mechanical drawings with good overall results. You really need to know what you are doing and also have the instrumentation. Pushing limits, I routinely measure ellipticity on HF in the confines of my small basement - figure that one out
Once you have determined the apparent crossed polarized fields of your particular CP feed, you should be able to clearly affect each resonance individually (might take a piece of dielectric on a very thin dielectric probe). I usually use small pieces of PTFE, Rexolite, plastic or even just my finger tips for this type of work.
After decades of work with CP polarization for a very wide range of applications and with quite a few years on HF too, last year I finally put together a (quadrature) dual channel polarimeter demonstrator for HF and this spring I also added a dual channel downconverter for 2.4 GHz for demonstration purposes:
Now, for my tripole antenna experiments I obviously need a three channel polarimeter. Think of this as an analogue oscilloscope CRT with magnetic deflection using external coils (e.g. Cossor 1039 or vintage radar CRT): instead of two orthogonal coil pair, only three deflection coils are needed in trigature, i.e. spaced at 120 degrees. Obviously magnetic deflection if bandwidth limited, but the display is on an arbitrary IF anyway. And I just love the dual time constant phosfors of my radar CRT
Until now I have been using vintage HP Vector and Constellation Displays with various homebrew 3 phase/2 phase RF transformers and matching three channel coherent converters depeding the on frequency band. This is all very fine for displaying CP ellipticity directly and in real time, but all the way, it is imperative to see also the complex impedances, such as (plot of the three resonances, 0 degrees and +-120 degrees with the total return loss of the trigature hybrid with imbalance load, 5dB/div):
The overall ellipticity (linear deflection) of this contraption may be seen in the last plot of the first link.
P.S. winding of CRT deflection coils is described in detail in the Bell Labs microwave series...
P.P.S. how many multipole antennas can you count in the AO-40 photo on the left?
S/N ratio is, especially for CW, a function of detection bandwidth, or in the case of an SDR, a function of sampling rate and fft size. For a regular analogue radio with real HW filters, the CW power is (hopefully!) considerably more than the noise, so the (peak) power measurement will fairly accurately depict the carrier energy level with even quite wide detection bandwidth. For noise however, we need to consider the noise bandwidth. The broadband, filter passband-filling noise power (which should be detected in RMS by the way) will be highly dependent on the bandwidth of it, i.e. how much noise energy is being integrated into a number. Increasing the detection bandwidth from e.g. a ~300Hz CW filter to a ~3kHz SSB filter will result in 10dB more (noise) power. In other words the CW carrier S/N ratio will appear 10dB worse with a 3kHz filter than a 300Hz filter
The point is, to make any kind of S/N ratio comparison, we need to know the modulation (CW is very different from 400BPS PSK) and we need to know the detection bandwidth. And in the case of SDR it is important to know the sample rate and FFT size (bin count). Only in this way can we compare apples with apples or make orange/apple conversion calculations to make comparison possible.
And for really meaningful S/N measurements, peak detection should be used for the (CW) carrier (S) and RMS detection for the noise (N).
It does not hurt to realize that the noise factor (N) is often noise + interference (I) and that a more accurate measurement would be S/(N+I), but fortunately for us, due to it's very high linearity, the QO-100 transponder noise floor has been and is pretty much random noise. In AO-7, AO-40 and the like, this was not so simple as HELAPS and other high efficiency RF amplification and other linearization and non-linearity processes resulted in noise-sounding (N+I.)
The result of all this is that 9dB SNR can easily be the same this as a 25 dB SNR. Only the measurement conditions are different.
73 - Michael, oh2aue
Not sure what you are referring to?
My frequency is is extremely stable.
What you hear in the audio pitch is Doppler due to my accelerating and decellerating?
The name of the video is "Compensating for QO-100 Doppler with Fuel Injection Rate"
Accelerating from zero to about 80 km/h will shift the received frequency up by almost 800 Hz
as I am clearly approaching the satellite. This is why copying SSB mobile is a bit touchy.
I really want to correct the fake news on Doppler Correction with Geostationary Satellites.
Sometimes Doppler Correction is mandatory for pleasant copy:
(Copying the QO-100 CW beacon mobile, so far about 50km worth of experience)
In my junk box I have a Qualcom Euteltracs/Omnitracs microwave head with stepper motor driven pillbox antenna, vertical polarization and all. This might even make SSB communication possible...
Modified "My First Venton" for single coax operation.
Needs about 0 - +3 dBm. I have 12pF + 2u7H in series from the F-connector directly to a crystal pad (crystal and caps remove). Cut a small slot in the cover wall to accomodate.
Also removed the second crystal line to improve stability. On the DC line I have 10 + 12 ohms in series. Operation is very reliable with +9Vdc.
I also modified a DX Patrol LNB PLL Reference & Bias-T unit for single coax use as per my triplexer design, but this still needs a more accurate 10 MHz external reference as the DX-P TCXO is 65kHz too low @ 10 GHz.
Heiner et al.,
just received some Venton EXL-S Rocket Single LNB's from Holland and I can cofirm they are PLL models:
The price is right, but the shipping is pretty expensive if you only buy one...
The serial numbers for mine are around EXLS-122016-005xx (December 2016?)