Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting a Default transponder in Radio Control? it always defaults to First transponder in the drop-down list #191

Open
dxblouie opened this issue Feb 12, 2020 · 3 comments
Milestone

Comments

@dxblouie
Copy link

Hi all,

so i'm not sure if this is a bug, a feature, or simply not something addressed..
I'm tracking NOAA 15, 18 and 19.. using prediction and auto tracking to tune SDR# and handle doppler shift for the 3 satellites when in range.

i record APT signal to get low-res weather imagery, which works perfectly with NOAA18 and 19, both of which have APT Transponder on top of the list.

image

NOAA15 however has "ARGOS-3 DCS" on top, and whenever NOAA15 is in range, radio control tunes to ARGOS-3 transponder..

image

the issue is simple, if i'm not there to change the transponder to APT, gpredict tunes my receiver to the wrong transponder, and i miss the pass..

am i missing something? a setting so the selected transponder would be the default for the satellite?

Thanks in advance!

@srcejon
Copy link

srcejon commented Feb 13, 2020

I don't think there is a way in the GUI, but you can change the order by editing the corresponding trsp file in a text editor. For NOAA 18, look for trsp/28654.trsp

@dxblouie
Copy link
Author

i did contemplate that idea, but figured an automatic update would take me back to square 1 :)

i edited 25338.trsp (for NOAA 15) to move this transponder to the top.. it works, till the next update!

[APT]
DOWN_LOW=137620000
MODE=APT

@csete
Copy link
Owner

csete commented Mar 22, 2020

I think it will be useful to save which transponder was used last time and select that one by default the next time the radio controller is opened. Will try to have this done in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants