[amsat-bb] Satellite Hiatus--Doppler.SQF
Alan
wa4sca at gmail.com
Sun Jun 7 20:54:43 UTC 2020
Devin,
Notice I said that the functionality is there, not the identical
implementation. You need to call the satellite something. While you could
certainly used the catalog name, something more user friendly is better.
See my replies below.
73,
Alan
WA4SCA
<-----Original Message-----
<From: Devin L. Ganger [mailto:devin at thecabal.org]
<Sent: Sunday, June 7, 2020 3:39 PM
<To: Alan <wa4sca at gmail.com>; AMSAT bbs <amsat-bb at amsat.org>
<Subject: RE: [amsat-bb] Satellite Hiatus--Doppler.SQF
<
<Alan,
<
<I'm looking at the documentation and the format of the Doppler.SQF file.
<Perhaps I'm misunderstanding something here, but what you're talking about
<does not seem to be what I suggested.
<
<Column 1 in Doppler.SQF is still the *name* of the satellite, rather than
the
<satellite number or international identifier or some other invariant
attribute of
<the satellite.
Correct. The problem is that the various tle providers are not consistent
about that. What you want to do is to be able to pick something, anything,
and then use whatever source you want without having to redefine several
files.
<
<Does that name have to match up to what is in the TLE file, or what is in
the
<AmsatNames.txt file?
It needs to match whatever you have defined in AmsatNames.txt, as does the
name in the priority and tone files.
<
<That is, if I am using the AmsatNames.txt file and define a custom name for
a
<given satellite, do the rest of my data files (other than the TLEs) then
need to
<be modified to use the name I defined in AmsatNames.txt?
Yes. One time operation.
Does the
<AmsatNames.txt file permit SatPC32 to ignore the name that my selected TLE
<source is using for that same satellite?
<
Yes, that is its purpose. It substitutes your preferred name for all
internal operations. IE, it completely ignores the 1st line of the 3 line
elements.
<Thanks in advance,
<
<
<--
<Devin L. Ganger (WA7DLG)
<email: devin at thecabal.org
<web: Devin on Earth
<cell: +1 425.239.2575
<
<> -----Original Message-----
<> From: AMSAT-BB <amsat-bb-bounces at amsat.org> On Behalf Of Alan via
<> AMSAT-BB
<> Sent: Sunday, June 7, 2020 4:34 AM
<> To: AMSAT-BB <amsat-bb at amsat.org>
<> Subject: Re: [amsat-bb] Satellite Hiatus--Doppler.SQF
<>
<> Devin,
<>
<> <If that's the case, then why wouldn't it be possible to have a small
tweak
<> <made to SatPC32 -- perhaps as an option at first to facilitate testing
and
<> <backwards compatibility -- to use the satellite number *instead of the
<name*
<> <as the key column for the DOPPLER.SQF file (and any other configuration
<> files) <that refer to satellites?
<>
<> Great news. That functionality has been in SatPC32 for years. Look at ?
|
<> Auxiliary Files |AmsatNames.txt. It does what you describe by allowing
you
<to
<> define a name for a satellite to be used with a catalog number (or
<> international identifier) and substitutes your chosen name for all
internal
<> operations such as the CTCSS tone, tracking priority, Doppler
calculations,
<etc.
<> Very handy since AMSAT, CelesTrak, Space-Track, and often the individual
<> satellite operators, use slightly different names. It is also handy when
there
<is
<> a "shotgun launch" and everybody is trying to sort out which satellite
<matches
<> which object number. One change with each object number, and you are
<> ready.
<>
<> 73,
<>
<> Alan
<> WA4SCA
<>
<>
<>
<>
<> _______________________________________________
<> Sent via AMSAT-BB at amsat.org. AMSAT-NA makes this open forum
<available
<> to all interested persons worldwide without requiring membership.
<Opinions
<> expressed are solely those of the author, and do not reflect the official
<views
<> of AMSAT-NA.
<> Not an AMSAT-NA member? Join now to support the amateur satellite
<> program!
<> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
More information about the AMSAT-BB
mailing list