I passed my radio amateur exam in March 2013 and I registered the callsign PD4KH (pappa delta four kilo hotel!). PD4KH on qrz.com
I am usually located around maidenhead locator: JO22NC
I like receiving and sending QSL cards. Paper cards via the QSL bureau and digital QSL cards via eQSL.cc.
For now this page contains just the 'hamradio' items from my homepage.
D-Star digitale amateur radio (Nederlands)
Tuesday evening I was at the Veron region A08 club meeting and I watched as someone else played with the radio for a while. We noticed some interesting activity on the HF bands: people making DX contacts from as far as Costa Rica mixed with people clearly having a very local contact. People working distant stations (DX) usually just want to exchange callsigns and a signal report and maybe some niceties and get on to the next contact, people having a very local contact can chat on for a while talking about the weather, their car, the upcoming visit to the dentist and other items, usually called 'ragchew'. It's very funny to hear the different styles mixed.
I created the simplest possible antenna for use in the 10 meter HF bands: a dipole from recycled utp wire using some turns of coax as 'ugly balun'. I used this Wire antenna calculator to calculate the needed lengths. The choice for the 10 meter band was for a purely practical reason: this is the length I can put up under our roof easily. So I am trying PSK31 on the 10 meter band, around 28.120 MHz. The first results the past evenings was a constant S6/S7 noise level, which leaves little space for other signals. And absolutely no response to my CQ calls. But conditions can change, and this evening I am hearing some PSK31 traffic, and IZ3ZOW managed to copy my callsign in Italy but we couldn't make it a whole QSO. I also tried various setting for the noise reduction in the FT-857 radio to see whether that has a positive or negative influence on PSK31. I am seeing other traffic, so the 10 meter band must be opening a bit. I spotted OM0AST calling CQ from the Slovak Republic but he could not hear my signals. Update: For me that opening didn't last longer than about 20 minutes.
In a few documents about the FM transponder on the SO-50 I noticed the use of the term PL tone where I expected the term CTCSS, for example in Operating SO-50 by Howard Long, G6LVB. I started wondering about the origins of PL tone and read the explanation on Continuous Tone-Coded Squelch System - en.wikipedia.org:CTCSS is often called PL tone (for Private Line, a trademark of Motorola) In amateur radio, the terms PL tone, PL and simply tone are still used somewhat commonly.I'll keep calling it CTCSS.
Some more work on the digimode interface for the FT-857 radio: setting it up on a real circuit board, to be built into a plastic casing. This time I heard a strange ticking sound when recording audio from PI3UTR but again it seems this clicking sound is a local problem normally filtered out from the audio path of the radio. When I picked up PI3UTR on the Wouxun KG-UVD1P radio I heard the same ticking noise. New respect for the audio filtering in the FT-857, but things like this make me question the digimode interface every time I'm testing it.
Friday evening I had time to work on the 'digimode' interface for the FT-857 radio. I set up a breadboard with the audio transformers and started making cables from the transformers to the USB audio interface. Then I added the cable to the radio on the other side. All of the earlier mentioned interfaces had resistors to regulate the signal level so I started with 12K resistors between the radio and the transformer in the radio to computer audio path. This gave me a weak signal when recording the result with audacity on the computer so I switched to a 6k8 resistor which improved audio but it still wasn't great. So the resistor was replaced by a simple wire which gave me good audio when recording from the PA00NEWS transmission on the PI3UTR repeater. I did notice some low hum while recording, but I realized that was just the CTCSS tone on the repeater output. Normally this tone is filtered out when hearing the audio through the speaker of a radio.
I listened to a satellite pass today of the AO-7 satellite. This is the first time I tried listening to a single side band (SSB) satellite transponder. This adds a whole new set of problems to 'trying to hear callsigns and other information in the noise' : the very nature of single side band (there is no carrier for the receiver to lock to, it just works from the frequency the operator sets) combined with doppler shift makes it hard for me to hear anything. And there is a 100 kHz wide passband on the transponder in which multiple QSOs can be active in different fitting modes. I did hear some morse (which I can't decode) and something which sounded like a conversation but I could not make out callsigns or anything. Better luck next time, I will keep trying!
The cable and parts for a 'digimode' interface for the new FT-857 radio are on their way. Such an interface will allow me to get audio from the radio directly into a computer and audio from the computer directly into the radio. This will allow digital radio modes such as PSK31, RTTY or AFSK. These modes allow bits (text, or databits) to be exchanged over radio. The simplest interface like FT-817 AFSK cable couples these directly but based on the advice of fellow radio amateurs I will use audio transformers to decouple the computer and radio and keep stray radio signals out of my computer and any interference from the computer out of my radio and I decided to use a cheap USB audio interface. What I will build is based on Digital VOX sound card interface but without the 'VOX' part and iPhone / Baofeng interface (schema) and El Cheapo AFSK (e.g. RTTY) USB interface (for FT-8×7) - remco.org. Update: Parts have arrived, time to build something on a development board first.
Good catch this morning on a southwest - northeast pass of SO-50: I managed to have a QSO with R1AO who operates from St. Petersburg in Russia! A distance of 1778 kilometers. This was the first QSO on satellite with the new FT-857 radio. Update: Thanks to eQSL.cc I already have the QSO confirmed.
And a non-catch: I tried receiving the AO-73 Funcube-1 amateur satellite but no go. I thought it would be in eclipse mode after 23:00 localtime which would mean the inverting transponder would be available. I noticed gpredict was reacting weird to the AO-73 Funcube-1 transponder file I found earlier so I checked again and found a better source, installed it 3 minutes before the pass.
New catch: I heard the UO-11 amateur satellite this evening. It transmits telemetry as an AFSK signal (bits as audio within an FM signal, more info at Frequency-shift keying - Wikipedia English), although very weak. When I have a working audio interface on the FT-857 I'll try to record some telemetry signals and decode the data.
Another SO-50 amateur satellite pass early this afternoon so I had the FT-857 radio set up with the laptop. I added two ferrite cores to the CAT cable and locked them in place with tie-wraps. The cable kept working even when I transmitted a few times during the pass. Getting the radio tuned to the satellite downlink once and then having the software doing the rest of the doppler correction is quite nice. But, no luck in making a QSO on the satellite. I heard at least M0SAT loud and clear and responded to his CQ but no contact.
Yesterday evening I tried to make some contacts during an SO-50 amateur satellite pass and twice the CT-62 USB interface to the radio crashed, with messages like:Aug 1 20:33:15 machiavelli kernel: [48075.216289] hub 6-0:1.0: port 2 disabled by hub (EMI?), re-enabling... Aug 1 20:34:45 machiavelli kernel: [48165.984146] hub 6-0:1.0: port 2 disabled by hub (EMI?), re-enabling...I had to unplug and replug the cable every time to get /dev/ttyUSB0 available to rigctld again. A few hours later the proverbial light above my head went on: EMI means electromagnetic interference, maybe transmitting quite close to the laptop is the problem. So this evening I created the same setup and tried transmitting so I could attack the problem and see if some ferrite cores would help. The problem decided to not return, even with the CAT cable and the antenna cable laying parallel. I'm still going to use at least one ferrite core to try to keep the USB interface from crashing.
I brought the Wouxun KG-UVD1P radio today on my bicycle and listened to the PI3UTR repeater on both parts of the cycling commute. In the afternoon I heard KM6DU active via echolink on the repeater and answered his call, giving a nice QSO. It was 99% Internet and 1% amateur radio, but it was nice to be able to do this thanks to echolink. KM6DU reported my sound was a interrupted a lot, so I stopped my bicycle and raised my radio from belt level (about 1 meter above the ground on my recumbent bicycle) to holding it up (somewhat more than 2 meters above ground) which changed the signal from lots of interruptions to clearly understandable. It's amazing what a bit of antenna height can do!
This evening I tried another pass of the SO-50 amateur radio satellite. It wasn't as high as the afternoon pass, only 66⁰ maximum elevation. The experiences from the afternoon pass learned me to search around a bit for the downlink signal. I did not hear a lot of activity, it almost sounded to me like the transponder wasn't "armed" with the 74.4 Hz ctcss tone. This tone activates the transponder for 10 minutes, but to actually use the transponder you need to use a 67.0 Hz ctcss tone. Switching tones on the fly isn't easy when the FT-857 is controlled by gpredict, so I'll either have to control that via the computer assisted tuning (CAT) interface and rigctld or temporary switch to manual and use the memory in the FT-857 which has the different ctcss tone. Browsing the rigtctl(1) manpage suggests a script which can set ctcss tones is quite doable. Update: Indeed, it can be done. Hamlib can't read the current ctcss tone, but it can set it on this radio. Model 2 in rigctl is the connection to a running rigctld on localhost.koos@machiavelli:~$ rigctl -m 2 -h Usage: rigctl [OPTION]... [COMMAND]... Send COMMANDs to a connected radio transceiver or receiver. .. Commands (some may not be available for this rig): .. C: set_ctcss_tone (CTCSS Tone) c: get_ctcss_tone () D: set_dcs_code (DCS Code) d: get_dcs_code () ?: set_ctcss_sql (CTCSS Sql) ?: get_ctcss_sql () ?: set_dcs_sql (DCS Sql) ?: get_dcs_sql ()and it works:koos@machiavelli:~$ rigctl -m 2 C 744 koos@machiavelli:~$ rigctl -m 2 C 670 koos@machiavelli:~$And the ctcss frequency on the radio indeed changes with what I set. And I can do this while gpredict is tuning the radio.
I soldered the cable for a stereo headphone on the mono phone output on the FT-857 this morning and went to listen for the SO-50 pass with tuning done by gpredict. And I missed half of the satellite pass because gpredict has the 'preprogrammed' frequency and the satellite downlink frequency seems to be drifting away from this frequency, far enough to fall out of the FM receiver passband. I kept hearing nothing so I switched back to manual frequency control with the doppler-shifted frequencies preprogrammed in the radio and I found it again, somewhat shifted. I switched back to letting gpredict control the frequency but used the tuning dial on the radio to find the right spot, after which gpredict kept track of what I did. I still find this an awesome feature in gpredict, the two-way tracking of frequencies. It was as busy as could be expected on an FM satellite on a Sunday afternoon pass with nice weather, so I could not find a 'hole' in which to call CQ or answer some call I heard. The headphones do help with hearing the audio from the radio, so a good thing I made that cable.
I also managed to get CHIRP working with the Yaesu FT-857 radio. I had to RTFM: CHIRP does not use the normal CAT commands, it uses the clone mode of the radio.
First thing to try with the new Yaesu FT-857 amateur radio: get it working with gpredict for amateur satellites. What gpredict can do is control the radio via rigctld, part of Hamlib to set downlink (receive) and uplink (transmit) frequencies automatically to the doppler-shift correct frequency. I bought a CT-62 USB cable for this which is the cable for the Computer Aided Tuning (CAT) interface on this range of radios with a FTDI based serial interface on the side of the computer. I added a new radio in gpredict with:
So I installed libhamlib-utils and tried to get rigctld working. At first it gave errors on communicating:
- Radio type: FT817/857/897 (auto)
- PTT status: Read PTT
- VFO Up/Down: Not applicable$ rigctld -m 122 -r /dev/ttyUSB0 -v -v Opened rig model 122, 'FT-857' ft857: error reading ack ft857: error reading ackAnd I found out the default baudrate of rigctld is 38400 bps and the FT-857 was set to 4800 bps. I tested first with 4800 bps and later changed the rate on the radio to 38400 bps and tested again. Now running:$ rigctld -m 122 -r /dev/ttyUSB0 --set-conf=serial_speed=38400 -v -v Opened rig model 122, 'FT-857'The radio needs to be in 'split' mode so VFOa and VFOb can be set sepately and receiving is on the VFOa frequency and transmitting on VFOb. The good part, especially for SSB satellite work is that gpredict will follow frequency adjustments on the transciever and will track from the adjusted frequency. With the 'lock' function enabled (L button) this will also make the uplink frequency follow downlink changes. Change the (receiving) frequency on the transciever and the transmitting frequency will be updated accordingly. This should make SSB satellite work with one simplex transciever easier. Sofar in tests without actual satellite communication things seem to work. Next is a test with SO-50 in FM mode, probably on the high pass I see coming Sunday afternoon. A test with an SSB satellite (first trying to receive) will probably be possible later this week with the Funcube-1 (AO-73). I found a
gpredict trsp file for FUNCUBE from G0HWWwhich has a low and a high swapped and confuses gpredict. The one at Funcube AO-73 transponder file for gpredict has this correct.[FUNCUBE BPSK Telem] DOWN_LOW=145935000 [FUNCUBE U/V] UP_LOW=435130000 UP_HIGH=435150000 DOWN_LOW=145950000 DOWN_HIGH=145970000 INVERT=true
For a while I have been considering my wishes for a more elaborate amateur radio. What I want to do with it is continue and expand the use of amateur satellites, and try to get into PSK31 on HF, starting on the 20m band. So a list of must haves and should haves arose: all-mode, portable, computer assisted tuning, HF support, 2 meter and 70 centimeter and an increas of power from 5W. Adding it all up and looking for a reasonable price I ended up considering the Yaesu FT-857(D). It's in the middle between the FT-817 (too low power, still 5 watts) and the FT-897 (too heavy: 3.9 kilograms). And a reasonable pricetag, were other amateur radio brands have nothing comparable or at a much higher pricetag. I went looking for a second-hand one and when we got back from holiday a nice one (FT-857 with DSP and installed filter, and a remote control+DTMF hand microphone) showed up from Communicatie Centrum Venhorst - Hilversum and I bought it. Picked it up this week, and I am learning using it. I listened to SO-50 this evening using this radio with a lot of wires on the table in the backyard.
Yesterday evening I gave it another try to make a contact via the SO-50 satellite. It was hard since someone was trying very hard to work the satellite with 95% transmitting and at most 5% not transmitting which did not leave much room for an answer. I heard that person loud and clear with a repeated and somewhat bored "CQ satellite" and testing noises like whistling, but I never heard a callsign! Trying to answer that person didn't work (clearly he had a reception problem somehow) so I just started calling CQ on my own when he left a gap. Someone answered but I had a hard time understanding the callsign, I think it started with a D (German callsign) and I am sure it ended with BBE (Bravo Bravo Echo). Looking up the callsign options on QRZ showed me the most likely candidate is DG0BBE so I e-mailed him to confirm. During our holiday in Denmark I also tried to work a few SO-50 passes. Being on a campsite with a wide open view in all surrounding directions should make things easier for lower passes which I skip at home. I tried a pass with a 55⁰ elevation and one with a 62⁰ degree elevation and I heard the satellite loud and clear. The downside was someone was whistling and calling 'o la', probably the same person as I heard here at home. And another downside is that with lower passes the distance is a lot higher and therefore my 5 watts on VHF don't make it across the FM receiver on the satellite. I also had a look at possible LituanicaSAT-1 passes but in Denmark those all stayed low to the Southern horizon. Update 2014-07-25: DG0BBE mailed me back, I was right I heard him, but he made a very valid point the QSO was not valid: in a QSO at least call signs and a signal report need to be exchanged. In amateur satellite work a locator is also good to have.
Friday evening I recorded the Amateur Radio on the International Space Station (ARISS) contact between the International Space Station in space and Focus Camp, Candriai, Italy / Euro Space Center, Redu, Belgium. I used the Arrow satellite antenna on a tripod and my Commtel com225 scanner to tune in to the downlink signal since that scanner has both an internal speaker and a line output for a tape recorder.
Recording ARISS contact - Laptop, recording ARISS contact, scanner, Arrow satellite antenna on tripod
A pass of the radio amateur satellite SO-50 this morning in which I concentrated on the probable shift in downlink frequency. It turned out the shift is probably not more than 5 kHz (my radio has no 2.5 kHz steps). I tried calling CQ but no answers. In general I am noticing now that usable passes are rare at the moment. With my limited setup and other things taking my time I have a lot of wishes for a usable pass: elevation must be over 70⁰ and the pass must be at a reasonable time in the evening or on a weekend day with no other plans. I'm not a nightowl like a lot of radio amateurs seem to be. So the week in which I made my first satellite contact with GS3PYE/P was quite special: there were 2 passes in that week matching all requirements for both locations.
A bit more luck on a LituanicaSAT-1 pass Saturday evening: this time I could understand at least one callsign. Hearing a known callsign helps: it was Peter Goodhall 2E0SQL. I tried answering but this failed. A mail exchange later confirmed I heard him calling so at least I heard it all right.
Success: I made a contact via SO-50 with PD5DJ. This was on a high (88⁰ degree elevation) pass of SO-50. The output frequency of SO-50 seems to have shifted a bit so I had to select the 'next' downlink frequency earlier than gpredict was showing them. I will send a card via the QSL bureau to PD5DJ, this is my second amateur satellite radio contact.
There are great things happening at the moment: the NASA ISEE-3 satellite from 1978 is going to pass earth again in August 2014. Due to budget cuts and cleanups at NASA they decided to not do anything with the satellite. International Cometary Explorer - Wikipedia. The first signals from this satellite were received in March: AMSAT-DL and Bochum Observatory Detect ISEE-3 Transmitters - Space College and since that moment people have been busy with it. The satellite was supposed to be switched off but it wasn't completely switched off and it receives enough solar power to overcome the lack of energy storage. A project was started named the ISEE-3 Reboot Project - Space College to get in touch with the satellite again and control it to make the course correction to return to the original orbit. With crowdfunding this project was able to get started quickly and the project received the control keys from NASA to be able to command the satellite. The first commands were succesfull: Happy Dance Video: First Successful ISEE-3 Commanding - Space College when the satellite was ordered to send more telemetry data. I'm following this story as I think it's great: commanding a satellite that has been in space for 36 years. The amateur radio angle is that recent developments in amateur radio have made this possible: the kind of specialized equipment that was needed in 1978 is now done with software defined radio and really good amplifiers.
Around midnight last night there was a pass of LituanicaSAT-1. After my earlier attempts and the announcement it would switch off the transponder at around 01:00 UTC on 5 June I decided to give it a go at this late hour. Original announcement: LituanicaSAT-1 FM Transponder Active until June 4 - amsat UK. I did hear traffic but it was very hard to understand callsigns (so I couldn't respond to a callsign I just heard) and I got no response to calling CQ. So not much luck in working this satellite, but at least I heard it this time.
I was looking for options for a pre-amplifier to amplify the incoming antenna signal for receiving amateur satellites in the 70cm band (430-440 MHz). Commercially available units seem to be quite expensive like this one: DBA 270 Duo-Band-Preamp. 2m + 70cm - SSB for 298 euro. A cheap option seemed to be Low Cost 440 MHz Receiver Preamplifier Kit - Ramsey Electronic Kits for US dollar 9.95. Oh, and US dollar 57 for shipping it to the Netherlands. I'll skip. Other options sofar seem to be quite expensive or require SMD soldering. I decided I have enough problem seeing normal soldering with a magnifying glass so I'll skip SMD soldering for now. A cheap but not ideal trick is (ab)using a cable TV amplifier: those include the 70cm band because they include everything from around 88 MHz to 1000 MHz. I found this suggested at KickSat Ground Station. So I walked into the local electronics store and found a cheap cable TV amplifier with a special sticker "does not support digital interactive TV" which means it doesn't support the returnchannel. Good, just a simple amplifier. The specific impendance in cable TV networks is 75 Ohm and I want 50 Ohm so that will probably have to be fixed too. It came with a small power supply which will be replaced with a battery like in the kicksat page.
Club evening at the Veron Centrum Radio Club and I walked into the radio shack and heard W1AW calling CQ on the 12meter band from New York. It was pure coincidence the radio was tuned to that frequency and I don't know who tuned it or left it in SSB mode. I checked DXHeat DX-Cluster but did not see W1AW spotted at that frequency. I should register at DXHeat so I could have posted my spot. The reception of W1AW was mostly ok, sometimes fading a bit. I answered the CQ using the club callsign PI4UTR. The W1AW callsign is doing a tour of the US states at the moment as the ARRL centennial qso party. It was fun to be a small part of this. The New York part is organized from W1AW/2 Operating Event Calendar - Rochester DX Association.
An SO-50 pass came up this morning at 07:46 local time (05:46 UTC) and it looked workable: a maximum elevation of 85 degrees. So even in the busy morning schedule before work I tried working it, after preparing everything in advance to fit in the schedule. I called CQ and I heard F0FIG clearly and called him but no responses.
I was able to buy a real Garmin GPS 18 LVC secondhand. It's now on the roof of our shed. The first thing I want to do is repeat my plotting of GPS satellite positions from $GPGSV messages and plotting of GPS satellite positions and signal strengths from $GPGSV messages measurements with data from this unit. After that has run for a while I'll configure ntpd to get the correct time from the GPS unit and the PPS signal. And again, the resulting plot of gps satellite positions versus signal strength is not very helpful in finding out which part of the sky is obscured.
I saw an announcement that Artsat1 Invader CO-77 aka ITF 1 was going to make a pass over Europe. I recorded it by having the laptop with the gpredict software also run audacity to record the audio from my handheld transceiver, so the audio isn't brilliant, but it's something. I reported the pass and the recorded audio to the Artsat team. This satellite is even in a lower orbit: the entire pass horizon to horizon was in 7 minutes. In the end I have 1 minute 40 seconds of usable audio, with everything the satellite offers: morse, the digitalker and AX.25 frames. The voice says: "Konnichiha Uchu" which translates to Hello, space!. Update: with fldigi I decoded the morse code:*HELLO, SPACE*Update: the pass was also recorded by PE0SAT and DK3WN: INVADER Digi-Talker active - DK3WN SatBlog including decodes of the AX.25 frames. And the transponder file I used: /home/koos/.config/Gpredict/trsp/39577.trsp with:[FM Downlink] DOWN_LOW=437200000 MODE=FMNow I have adding frequencies for an existing satellite covered, I wonder about adding an entire satellite.
Weer een overgang van LituanicaSAT-1 waarbij ik geen succes had met contact leggen vanmorgen. Ooit gaat het lukken! De satelliet overgangen zijn momenteel niet op handige tijden, dus ik ben al zover gegaan om te zorgen voor een piepje om op tijd wakker te zijn voor een overgang om 08:25 lokale tijd. Achteraf weer alles nagekeken op de radio, en daarbij ontdekte ik dat de geheugens die ik geprogrammeerd heb voor de LituanicaSAT-1 in wide-FM mode stonden. Uit de discussie op de Amsat-bb lijst begrijp ik dat wide-FM zeker een verkeerde instelling is LITUANICASAT-1 experience - Amsat-bb (nu niet meer gearchiveerd). Direct gecorrigeerd, volgende kans beter dus. De overgang van SO-50 aan het eind van de zaterdagmiddag heb ik goed gehoord maar het lukte me niet om erdoor te komen, volgens mij zat ik iedere keer dubbel met een ander. Ik hoorde haarscherp G0JMI over de SO-50 komen, maar terugroepen werkte niet. Een van de eigenschappen van FM is dat als een ontvanger twee signalen binnenkrijgt op dezelfde frequentie dat het sterkere signaal dan het andere signaal verstoort of wegdrukt. Update: De LituanicaSAT-1 satelliet is ook weer uit transponder mode: LituanicaSAT-1 Telemetry Reports Requested - Amsat UK. Door onverwachte reboots is de satelliet weer terug in de instelling waarbij er alleen een telemetrie signaal is waarin digitaal de metingen aan boord van de satelliet verzonden worden. Misschien toch eens proberen die telemetrie te ontvangen.
An interesting development in software defined radio for amateur satellite use: Controlling gqrx from a remote host - Gqrx SDR which allows gpredict to control the frequency, mode and audio recording of Gqrx. I was wondering recently whether it was possible to record the right signal in Gqrx, correcting for doppler shift. Now this can be done.
Momenteel weinig geluk met de amateur satellieten: de mooie hoge SO-50 overgangen zijn op tijden dat ik slaap of op mijn werk zit. En het lukt me nogsteeds niet om iets te doen met LituanicaSAT-1. Vandaag twee overgangen gehad volgens gpredict (met als het goed is de gecorrigeerde baangegevens) maar beide keren niets ontvangen via de FM transponder en niets via de baken frequentie. Nu lopen de berichten over het baken ook uiteen: op de ene plek wordt het beschreven als puur CW wat ik natuurlijk niet kan ontvangen met mijn radio, op de andere plek als FM CW waar ik in ieder geval piepjes verwacht op mijn radio. Of de LituanicaSAT-1 FM transponder aan staat is mij ook niet duidelijk, volgens een bericht van vorige week zou deze constant aan staan LituanicaSat-1 transponder remains on - Amsat-bb maar volgens een ander bericht is er nu een watchdog-reset geweest LituanicaSAT-1 reboot test - reports requested - Amsat-bb en dan kan ik me voorstellen dat de FM transponder niet automatisch ingeschakeld wordt na reboot. Update: De radio zenders op LituanicaSAT-1 zijn momenteel helemaal gestopt om de accuspanning weer te laten stijgen volgens Re: LituanicaSAT-1 reboot test - reports requested - Amsat-bb (nu niet meer gearchiveerd). Ik denk dat een reboot nogal veel vermogen kost. De satelliet zal dus eerst wat rondjes in de zon moeten draaien voor er weer dingen ingeschakeld worden.
Vandaag een paar satelliet momenten. Met de SO-50 satelliet lukt het me al beter om callsigns te verstaan. Maar ondanks proberen op passages vanmiddag en een vanavond geen reacties gehad. Dus wel conversaties van anderen gehoord, onder andere van PD5DJ die ook al reageerde op het onderwerp op zendamateur.com over callsigns verstaan bij satelliet overgangen waar PD5DJ ondertussen ook wat mooie foto's van zijn satelliet acties geplaatst heeft. Ook kwam LituanicaSAT-1 een keer voorbij, maar daar hoorde ik helemaal niets van en kreeg ik ook geen reactie op mijn oproepen.
Vanavond was er een overkomst van de SO-50 satelliet die redelijk te doen was. Ideaal is als de satelliet recht over komt, maar dat gebeurt natuurlijk niet al te vaak. Deze overkomst had als maximale elevatie 54 graden boven de horizon, waardoor de periode waarin ik een contact zou kunnen leggen redelijk kort was (ongeveer 5 minuten). Alleen waren die minuten gevuld met succesvolle contacten door andere radio amateurs waarvan ik het meeste goed kon verstaan. Een mooi moment om te luisteren en er niet doorheen te roepen. Achteraf weet ik de roepletters die ik gehoord heb alleen niet meer, misschien toch eens een manier vinden om deze sessies op te nemen.