SatNOGS is one of the projects we have been following with excitement for some time now. With SatNOGS, users contribute to create a freely accessible open source global satellite network. This is a great alternative to the traditional satellite service networks, which are expensive and hard to access.
There is a SatNOGS station in Trondheim, LA1NGS, which is operated by NTNU Small Satellite Lab and Orbit NTNU. We have eagerly followed and used its recordings for various things, such as listening to QSOs on amateur radio satellites and viewing NOAA weather satellite images.
This fall we noticed that their rotor had stalled, so we reached out to them to ask if we could assist with solving the problem. After some discussion, we agreed on helping them replace a Yaesu G-5500 rotor with a new model, namely the SPID SPX-02 . There were some concerns with wear on the older model, as it had been in operation for quite some time, so a full replacement was desirable to ensure a long lifetime for the station.
To install the rotor, we had to lower the mast and remove some coaxial cables from the service box that contains LNAs and phasing harnesses.
Full parallelization was achieved by simultaneously assembling the rotor controller for installation into the ground station rack.
The last step before mounting the new rotor was running new control cables, and soldering/assembling the connectors.
Finally we attached the rotor to the mast and gave it a spin.
We were lucky enough to be given the old Yaesu rotor as spoils of war. The plan is to repair the rotor, and use it to build a SatNOGS station of our own. Another blogpost is probably due on this if we get the rotor working.
As for the newly installed SPX-02, it operated smoothly for about a week of continuous operation. After that, however, there has been a number of hiccups. The MD-01 controller complains about time-outs on the sense lines after some time in operation. The jury is out on whether this is a hardware or software issue, but either way it is something that should be resolved. We feel a bit bad about leaving the system in a broken state after “fixing” it, hopefully we will get to the bottom of this soon.