Posts by pe1hzg

    I found I was able to reproduce the "non lock" with an eval board, and I have a theory of what is happening

    Looking closer at the datasheet of the ADF4351, it seems that "programming the registers" does more than just load values it it, a number of circuit selections happen inside the chip while the programming process is happening. This is why the registers must be programmed in a certain sequence: R5, then R4, then R3, ... last R0.

    If there is no reference frequency during the process then it will fail.

    If you power-up the adf4351 with a reference, then remove it, then connect it again, the PLL will lock. The problem is if the PLL is that if the PLL is programmed when the reference frequency is missing, the programming doesn't seem to work.

    My suggestion would be to make sure that your programming includes correct programming of the Lock Detect output, then change the programming of the 12F675 so that after programming you wait a bit, wait for Lock Detect to go active, and if not, re-start the programming process. I have not tried it, but your "touch the MCLR" suggest this will work.

    I'm nervous about the "touch MCLR" comment. Does this pin have a pull-up resistor?

    Hi Roberto,
    If you do not connect the 10MHz, power on, see that the PLL doesn't lock, then pulse the MCLR on the 12F675, does the PLL lock then?

    I've made something similar, but with attiny13, it can be found elsewhere on this forum. I don't have the problem you have: PLL always locks when 10MHz is connected.

    The uplink uses circular polarisation so the line-up does not matter.

    That is not true for the receiver which is vertical for the NB transponder and horizontal for the WB transponder. For this reason, the angle of the LNB *does* matter. What makes things worse is that unless your azimuth is 180 degrees, your view to the sat will be squinted. For this reasons, for optimal performance, the LNB must be twisted a little bit. You can use sites like to find the "LNB skew".
    Note: there is an easier way: it is easier to find the null of the signal and the max is 90 degrees away. So, turn the LNB to "null" the signal (for instance, beacon), then turn the LN exactly 90 degrees CW or CCW and you are set.

    The 3rd issue is the distance between the base of the POTY and the black plastic carrier of the dish. I think your POTY sticks out much too far: I think it should be flat (but someone please correct me!). You will run into two problems if you do things this way:

    1. the SMA connector is in the way. From the picture I think you have a TRIAX dish. Instead of the plastic bracket, metal brackets do exist and those just need a small bit filed away and then the SMA connector goes.
    2. The edge of the POTY base plate may interfere with the pipe that carries the LNB. LNB brackets assume a diameter of 40mm, and the POTY pipe is 22mm so you use a spacer. BAMATECH has spacers that are off-center which solves this problem

    Hope this helps!

    When I cannot depend on long-term stability of the setup, long enough stable to let a GPSDO do it's thing, I now use a OCXO like

    It is a OCXO, the casing gets warm, but the thermal mass isn't big and the temperature / frequency stabilizes stabilizes in 90 seconds.

    I've done tests comparing with a GPSDO, doing lissajous tests at power up, but after 90 seconds this really is "plenty good enough" for SSB use (my whole station, not DXpatrol btw, is GPS-locked).

    I would recommend to put the PCB+module in an enclosure for additional thermal isolation in case of e.g. wind.

    Nevertheless, it was frightening to see how much work Leila had to do now that she is back in operation. Some stations seemed to ignore Leila completely, maybe because they can't do full duplex? Others even felt disturbed.

    This morning I had Leila trigger on signals that (confirmed on some WebSDR's) were clearly below beacon level.

    I made some signals myself to measure (signals that never triggered Leila before) but even signals 5dB lower would trigger it. So, Leila wasn't deaf, it was having morning temper issues.

    I should note that, at this time, the Goonhilly WebSDR cannot be used for beacon signal levels because the beacons are significantly below level (compared to the middle beacon at least). Right now, the middle beacon measures -72.4 dB. On the same Goonhilly, the lower beacon measures -80.1dB and the upper beacon -80.7 dB. So, the lower and higher beacon measure 8dB below the middle beacon.

    Looking at the IS0GRB WebSDR, the middle beacon is -70.2dB, the lower beacon -71.5 dB, and so is the upper beacon.

    This is how I remember the signals from a few months back .

    That (relatively) matches my own signal measurements, and that means the Goonhilly WebSDB cannot be used to qualify signal levels. This problem started after fix of the recent "GPS lock" issues; in any case, it makes the "signal measurement" thing a lot more complex.

    Another issue is that if one sends a carrier, Leila zero-beats on the carrier. If the carrier is made using a SSB radio, then Leila is outside the passband of the radio and I can't even hear it; it is 300 Hz below the low-end of the SSB passband.

    I would appreciate not having another "full duplex" discussion. There clearly are a number of other issues at play here too. It is volunteers who are keeping all this alive and Corona makes working on these things even more complex. Who is without sin throws the first stone!

    I am kind of saddened by this discussion. It is easy to fault someone, but it will result in bands that are empty and perhaps that is not what we want.

    The duplex discussion has been done before on this forum.

    Personally, I don't think that "monitoring one's signals" must mean listening to one's own signal when transmitting.

    You can easily recognize the stations that listen-to because hearing your own voice with the sat delay makes you stutter:

    you cannot .... speak well .... while you .... are hearing .... your own .... voice.

    Many of these stations also respond 1 kHz off or more when they respond to a call.

    For me, monitoring means just that, monitoring. Seeing if someone tries to break into your QSO. Seeing if LEILA is asking attention. Monitoring the signal levels.

    And for that, watching one's signal via some SDR spectrum thing is fine.

    A simple approach I've used often is to have a laptop that shows the Greenhilly WebSDR page. With proper font size and a but of scrolling the page can be used as a transponder scope. And when enabling the signal strength plot (on "slow") you can really monitor your own signals. This isn't bad: broadcast stations use remote receivers to monitor their signals.

    When you cannot / do not want to use Greenhilly for monitoring, there are several approaches still. I have a Megasat Diavolo twin LNB and use one port to receive and the other just gets 12V and I use SDR console with a RTL-SDR dongle to monitor the signals.

    Another approach is to tap the receive port signal and feed it to the SDR dongle. Unfortunately, with the DXpatrol that results in a few issues: 1. on the DXpatrol unit, the clock on the LNB is switched off when the unit is transmitting so the LNB does not function during transmits; 2. one needs to look at the frequencies for conflicts.

    As to the latter problem: in my station (based on the praised PE1CMO kit) the LNB gives 739 MHz out and there is a separate PLL to convert 739 MHz to 432 MHz using a 307 MHz PLL. So it was easy to add a 739 MHz tap and that is what I have. However, in my case, the transmit signal (also on 432 MHz) was leaking on the receiver and was mixed with the same PLL signal to (also) result in 739 MHz. I spent weeks puzzling why I had this big signal on SDR console during transmit: was the 13cm overloading the SDR? In my case, the leakage of the 432 MHz transmit signal, over the TX/RX relay, over the mixer, gave a big signal on 739 MHz (credits to Rene CMO for the clue!).
    On my setup, I mitigated this by disabling the oscillator of the 307 MHz signal during transmit.

    Unfortunately, the DXpatrol unit has some challenges here. The LNB clock disappearing during transmit is not helping. The LNB outputting directly to 432 MHz is not helping either because it is very hard to keep this signal out of the receive chain. So, self-monitoring may be a challenge with this unit

    Should DXpatrol consider an upgraded design that does not have these issues (perhaps with a "739 MHz out" connector, which my PE1CMO unit has now) then the unit would be even more attractive. But the current unit can be made to work - just watch Goonhilly when you operate and you're done.

    Let me re-visit this, because when I ask in a QSO, it turns out that people did monitor their signal levels when setting up, but generally no longer monitor afterwards:

    When working over QO100 NB transponder, one's signals are not supposed to be stronger than the lower CW beacon on 10489.500.

    And the AMSAT-DL website strongly pushes the Goonhilly WebSDR.

    Until recently, the CW beacons (10489.500 and 104900.000) had a signal strength of typically -70dB, and the middle PSK beacon was typically -73dB. Signals raising above that would be yelled at by Leila.

    The signal strengths have roughly the same levels on the Italy WebSDR, and my own equipment gives the same (relative) signal levels.

    However, recently, the strength of the CW beacons on the Goonhilly WebSDR have dropped significantly and are now -80dB. This only applies for the CW beacons, the PSK beacon as well as user signals have normal signal level.

    Signals have normal levels when measured over the Italy WebSDR, or on my own receiver.

    Only the CW signals are weaker, and only over the Goonhilly WebSDR!

    I have measured over days to make sure it's not a weather issue - it isn't. And to the best of my knowledge all three beacon signals are made from the same earth station. If weather would be obscuring, then I'd expect all signals to be weaker - they aren't, only the CW beacons! - and if the Bochum / Doha ground station would be covered by weather, then all three beacons would be weaker, on all receivers - they aren't, ONLY the CW beacons, and ONLY via the Goonhilly WebSDR.

    If people can confirm that would be grand. I've included screenshots of my measurements of 10489.500, 10490.000 and 10489.750; note that the signal history indicates that the signal strength is constant.

    Clue appreciated!

    I found your signal even more useful than expected, while testing link margin during a thunderstorm. I know I lost at least 15dB at its worst, and that happened while the streets were still dry. I could "see" the thunderclouds drifting towards the sat path. When the rain started, signals went up ;-)

    Using WebSDR, I saw that my own signals were not attended as much which is strange (2.4 is the max water absorption frequency ?!?)

    Having longer signals at a level would be useful. "zero" is short to measure.

    Is 0dB the beacon level? I don't think it is, but propagation is strange right now.

    I any case, this is useful, but perhaps t needs to be there structurally. Good stuff!

    Without wanting to play my own harp, see

    I don't know if Megasat has a good representation in the UK, the BRexit has caused a deep ditch to the mainland but let's keep the forum technical please!

    However, brand and type doesn't matter that much. Keep in mind that if you buy a certain type of LNB, and you order the same type 3 months later, you will likely find completely different electronics inside. In that regard, what does matter is to "buy a few at once". If you break one, you have learned the construction and the next one will be easier to modify\; you also have "one to look at" which I find, helps a lot.

    The key is to get a LNB with crystal reference. The good news is that these are cheaper than older models with DRO. My suggestion is you buy a few, open one, if it is a DRO-type, send the other ones back unopened. Personally I find it difficult to ind DRO LNB's these days; PLL is much more common

    Also, something that is not covered in that document, and I had problems with, is cutting the wiggly line going to the voltage regulators and adding an SMD inductor. That wiggle line is enough inductance to block the IF going into the regulators, but is not enough to block a 25M signal, and the decoupling caps at the input of the regulator were eating all of my 25M reference preventing the LNB from locking. Once I added an external inductor (820 nH IIRC) it locked just fine.

    The proper way, IMHO, is to make a parallel resonance circuit on 25 MHz. That will keep the reference where it is supposed to be.
    Personally I use 150nH and 270pF. Note that with SMD these can be "stacked" making it easier to find space for them.

    It is sunday afternoon and it shows, on the spectrum waterfall. Carriers come and go, drift all over the place, people calling "test... test".

    We've all seen it and we've all cursed it, but what is someone to do who just want to test his signals? Aren't callsigns not given not just out of disinterest, but also to avoid being called for QSO? If I want to test, where should I test?

    I wonder if it makes sense to set aside a small segment (20 kHz or so) just for testing. "if you must test, test in the test segment; no QSO in test segment",

    I guess most of us know that the most often used feature of a terrestial FM repeater is testing. "click-boing": doesmy radio still work? I think the same applies on our bird.

    I guess the good news is that the test signals most often happen during EU daytime. That means it's humans doing this, and perhaps these humans can be guided

    Just a thought,

    Geert Jan

    Actually, you can't use the TV splitter modelled because it does have filters in it (it has to, because otherwise LNB noise would interfere with TV signals).

    Strange as it may sound, the one you want is:

    This is "just a TV splitter" but if you open it, it actually has a transformer inside to do the impedance thing correctly. You will see that it passes DC on all three ports, so voltage supply for the LNB "just works". Disadvantage: this splitter uses Belling-Lee connectors, though adapters to F and BNC exist.

    Note that this splitter really is different from the typical "plastic" splitter which uses resistors. Check your ohm meter.

    I would like to stress that this works for the specific use case you have. NB and WB have different polarisations, so this trick can't be used to receive NB and WB on the same single LNB. For those cases, I recommend dual LNB's, I have good experiences with the Megasat Diavolo Twin LNB, giving me two independent ports can can do each polarisation as I want for the experiment du jour.

    Geert Jan

    While making adjustments to my station I must admit being guilty to triggering LEILA (I'm sorry, guys!).

    But, I found that I didn't hear LEILA, I only saw LEILA on monitoring. So I investigated closer.

    When sending a carrier, my radio sends a carrier on "carrier frequency" of the USB signal. Using USB means that the modulation will be above the carrier frequency.

    When LEILA triggered, I found it sends a carrier on the frequency it "discovered" and a lower frequency. That means the LEILA signal will be outside my filter, which explains why I didn't hear it.

    My question: why does LEILA use the "discover frequency" and a lower frequency for signalling instead of using a higher frequency so it would be in the passband of my receiver?


    I recently purchased

    This is an OCXO, so it is with an oven. It takes 90 seconds to stabilize (and the casing gets warm as the oven heats up).

    I got these as frequency reference for by QO100 setup if GPS isn't available or if I want to test something quick - GPSDO takes more time to synchonize.

    Mind you, this thing does 10 MHz, not 40. But if stability is an issue - give it a spin!


    Geert Jan PE1HZG

    For those wondering, the goonhilly crew is having bad luck and is now reporting issues with the GPS antenna. The GPSDO is still stable but a few kHz off. Maintaining some repeater sites myself, I feel for the crew because Corona generally makes access to these sites very complicated if not impossible. The webSDR is still very usable but keep in mind it is a few kHz off.

    Status info is given on the info on top of the page (yup, the info I skipped too)

    This actually gives an interesting side effect. When looking at the upper beacon, I always heard an extra carrier (have the same problem in my setup). This is probably related to the reference frequency sent to the LNB. Because the reference is now slightly off, the reference harmonic and the beacon signal are now on different frequencies. You may want to study the upper beacon while this situation persists.

    I'm using CH3+8 (2.4GHz) and 5GHz as well. My Antenna is 10m away from my house. No problems so far using the NB transponder (2W+POTY+1.2m offset dish).

    WB and more power could be different...

    Keep in mind that with the higher wifi speeds, the channels are wider and hence channels overlap. If you are using channel1 then channel 2,3 are unusable. Industry practice therefore is to (only) use channel 1, 6, and 11. WIth QO100 activity that leaves channel 6 and 11. Use of channel 3 and 8 is like transmitting on 145.505: you block 145.500 and 145.5125.

    I realize that signals are local but I still remember when I was the only one with wifi - these days I see 30-40 SSID's easily and unfortunately not all of them use this scheme. wifi on 13cm in city areas is a zoo.

    I realize this is out of scope for this forum but if people tinker with these settings they might as well know.

    Not intending to kick up a lot of dust, I am asking:

    In some local QSO's there has been, for a number of days, a discussion on QO100 frequency accuracy.

    On my own station, i find that I typically need to tune 70-100 Hz down to be on frequency. I blamed that on my own equipment (even if every single component is GPS-locked), though I wasn't sure where it would come from.

    All that, until I heard in the discussion that others are reporting same.

    People using the beacons for reference are OK and don't report anything.

    We know that the LO in QO100 is spot-on (see the NDA discussion elsewhere).

    Without wanting to blame others: can anyone confirm the correctness of the frequencies of the beacons?

    I know there have been issues in the past and realize that maintenance in Corona days is a challenge, but a brief "yup, we know" helps me to stop searching my own kit.

    There also have been discussions on a small offset in BG7TBL references, but that offset is constant and for this issue, the numbers don't add up, so I don't think it is that.

    Clue appreciated,

    Geert Jan

    Sorry for playing my own harp but as to frequency stabilisation, have a look at this discussion on the forum: 432/28 MHz transverter from

    As to the Anglian converters, they are good but parts may be an issue.

    Keep in mind that for QO100 the dynamic range is limited. On WebSDR, the beacons are less than 20dB above the noise floor and stronger signals than that yield QSL's from LEILA. My suggestion is to focus on reciprocal mixing given the relatively high noise floor. In my experiments, I find that receivers that are quoted to have good LO's give me better signals.