The current transponder files show Noaa15 frequency as 137.500 Mz whereas that satellite has been using 137.620 for a long time. Can it be corrected?
For which software?
GPREDICT.
Thanks
I have 2 PCs both running Windows 10 Pro, I’m using Gpredict 2.3.37 to link with SDR# and Wxt2img for tracking and downloading APT from Noaa 15,18 & 19 but Gpredict defaulrts Noaa 15 to 137.500 instead 137.620.
Apologies if this has been covered before but at age 85 I’m easily confused 
73 Fred
It looks like that Gpredict has two issues when downloading the transmitters/transponders:
-
Transmitters with the same name can not be differentiate, that means that if two transmitter have the same name then the one overwrite the other. This is your case as the “APT” at 137.500 MHz has been written over the “APT” at 137.620 MHz. I’ve changed the name of the 137.500 one and now both show up if you perform update on the transmitters/transponders. However this needs to be fixed in the software as we usually have transmitters with the same name but different characteristics.
-
Inactive transmitters are handled as active. There isn’t any indication that a transmitter downloaded is marked as inactive. This also needs to be updated in the software.
PS I moved this topic in the Gpredict category
1 Like
To answer your question, yes, you can fix any errors or update the transponder data.
When a new satellite is designated to be an OSCAR, that name doesn’t always appear in the Gpredict configuration. I end up going into the appropriate directories, find the files corresponding to that spacecraft’s original ID number, and edit the text.
It can be a bit of a nuisance sometimes, but I finally get it set up that I’m looking for OSCAR XYZ. There have been occasions when the transponder data’s not available from the repository, so I end up creating a file that has all the frequencies and modes and putting that in the directory. It’s generally worked for me so far, unless I made a mistake in creating and editing the file.
1 Like