18 Dec
2017
18 Dec
'17
7:43 p.m.
Yep, that's happened to me as well. I had to dive deep into gpredict's database and remove the file for the old satellite number. Re-update from network, and it should fetch the right info. I think what happens is that the change in satellite number is not updated in the file, so it continues to reference the TLE info from before the change. If the surgical approach doesn't work, you can just remove (rename for safe keeping) the entire satdata directory and refetch everything anew.
On my OpenSuSE Leap system, it's all stored under ~/.config/Gpredict/satdata
Greg KO6TH
Koos van den Hout wrote:
I have had my own issues in gpredict of newly launched objects changing not being updated, so this is not a complete surprise to me on a new object.