The VHF/UHF/SHF contest on 2nd to 3rd of May was a good opportunity to spend a few hours trying the new AirScout version 220.127.116.11 released by Frank, DL2ALF. In principle it works like it´s predecessors, but is more stable in collecting the aircraft data. My favourite in this case is planefinder.net.
Most impressed I am by the new feature to monitor a number of paths to certain stations simultaneously! This provides more efficiency in arranging skeds, particularly in times like these, when there are a few planes only are available.
Tonight I met Salvo, DK3SE, in the ON4KST chat. Salvo recently became QRV again on 13 cm. He uses a 1.8 m dish and has about 50 W at the feed. As his location is on the southern slopes of the Black Forrest, our direct path is blocked by solid rock. Even aircraft scatter is very hard to perform. So we tried to find a reflective point at the mountain range of the Alps, but that was not very satisfying as well. Next step was to try side scatter on airplanes to the east of the Black Forrest.
We tried on a couple of planes and, as expected, on the ones, we saw the same side of the body, we received strong reflections. So we learnt, in side scatter the orientation of the plane matters! This is in opposite to the usual aircraft scatter, where the planes just have to be on the path and the bottom side of the aircraft is used as reflector.
I got up quite early today and decided to check the beacons on 23 cm. When beaming to LA1UHG, there was a noticeable signal in F1 about 1 kHz above its frequency. It was easy to read it as DB0LB from the back of the dish. But it seemed, there was another faint signal right beside the spacing carrier. With the help of my SDR radio I could set very narrow filters and after a while of listening, I identified it as LA1UHG, JO59FB, 1028 km. Wow!
But the signal faded out more and more and at least it disappeared.
Later this morning, the dish still pointing north, I heard Kurt, OE5XBL, chatting in SSB with Rudi, OE5VRL/5, both with very strong signals on 23 cm. Expecting a huge signal, I turned the antenna to Kurt, but there was no significant increase in signal strength. I called in and the three of us were talking about the conditions and to meet for a beer at the GHz convention in Dorsten next February, when Kurt was called by Dave, G4RQI. I had tried with him earlier without any success, and so, to be honest, I was a little annoyed by this. Even, when turning the dish to the UK, I couldn´t copy anything of Dave’s transmissions, while he was working Kurt and Rudi. These were enough indications, that the inversion was at a too high altitude for me, to enter it. So I went for a long walk with my XYL in the nearby vineyards.
In the evening I performed another beacon check. It was funny to see beacons, the dish was pointing to, as well as others from the back of the dish
Turning the dish, confirmed the experience I had in the the morning: Pointing southeast I saw DB0VC, JO54IF, next to DB0AAT, JN67HU. Turning the dish towards Kiel in the north, the signal of DB0VC increased just a little. Maybe, it has been reflected by a mountain range about 50 km southeast of me.
By performing my daily beacon check, I noticed a weak keyed carrier in between the spacing of the F1 signal of DB0UX on 2320.900 MHz. I assumed to see F6DWG/B, which I monitored around the .900 before. But it didn´t take long to find out, that the real signal (mark) was the lower carrier and after a while I learned, it was F5ZNI using reverse F1 keying. Later in the evening the signal increased due to good tropo conditions, as can be seen in the pictures. F5ZNI is the 34th beacon I received in the 13 cm (S) Band
I am always happy about new beacons, but this case is an example, why beacon coordination and using standards is most important. First of all, reverse F1 keying is always bad, as you are used to listen to the upper carrier of the signal. In case there is an unkeyed carrier in between the text, you can easily identify the mark, where to listen. But if there is text keyed nearly all the time, as F5ZNI does, it is rather time consuming until the mark is identified.
The DB0UX signal was strong and the frequency is locked to a reference, while F5ZNI is drifting a little. So it was obvious, that there was a second signal in place. If the french beacon would have been locked to 2320.900 MHz too and would use the standard A1 or F1 keying, there would have been no chance for me to monitor or even to take notice of it.
An excerpt from BEACONSPOT.UK shows the situation on 2320.900 MHz:
On the annual service day of the DARC districts Saarland and Rhineland-Palatinate I had the pleasure to hold a lecture about EME basics and how to get into. Afterwards I invited the audience to try a live moon bounce QSO on 432 MHz from the parking lot outside. I had prepared some standard equipment of the kind, many might have in their shacks:
Transceiver Yaesu FT-897
15-Element Yagi (YU7EF )
PA Gemini 70, ca. 200 W
LNA SHF-Elektronik, 0,8 dB NF
Unfortunately it was rainy outside, the moon close to the sun and a G2 solar storm in progress. When swithing on the transceiver, I noticed some quite massive local QRM. Nevertheless I contacted Bernd, DL7APV, who had agreed in a sked, by phone, to tell him about the noise and that we were ready to go.
As the noise level went up and down and Bernd is one of the big guns on 70 cm, we were able to decode most of his transmissions despite all adversities. Finally we completed the QSO. That was a great job, Bernd!
I enjoyed to be in Saarbrücken and would like to say thank you to Eugen, DK8VR and his team for organising DST 2019!
The last contest, I participated, was in June 2018. There wasn´t much time for amateur radio since. So I was lucky to dive into contesting this weekend mainly on 23 and 13 cm, as usual, but had some QSOs on 2 m, 70 cm and 3 cm as well.
I am happy about 60 claimed QSOs on 23 cm and 43 on 13 cm. On 3 cm I logged 7 Stations, with OE5VRL/5 as ODX via rain scatter.
There have been some new calls on 23 cm but none on 13 cm, as I had expected. Many became QRV on 2400 MHz for QO-100, using transverters, also operable on 2320 MHz. They should learn about the exitement of DX via aircraft scatter on 13 cm.
When looking for EA2TZ/B during a beacon check a couple of days ago, I mentioned a signal with strong doppler shift about a khz below. As I like the challenge to identify new beacons, I started monitoring it. It became a kind of a nightmare, trying to to catch the beacons callsign. It seems to be very chatty, transmitting a whole bunch of unuseful text. despite the fact I got a lot of good quality fragments via aircraft scatter, it took me hours to identify it as F1ZBK. At least I am pretty sure it is, as there is a second callsign in the end of the text: F1DND, maybe it´s the keepers call.
The text decoded so far is: —— beacon f1zbk jn38bp nancy … 854 khz … 5 watt … f1dnd … orange KA … ——- Where the “…” represent gaps and KA is the prosign for “Attention” or “New Message” (not to be used at the end of a message, like AR).
There are many beacons running in bad modes like reversed F2A or keying the subcarrier of F2A, but transmitting such a lot of stuff is worse.