Doppler.SQF for SatPC32


[amsat-bb] Doppler.SQF
David Worboys
Sat Jun 6 14:56:25 UTC 2020

Morning all,

Would anyone be kind enough to send me a copy of their up to date
Doppler.SQF file for SatPC32 ? I have a funny feeling that I am more than
likely to "fat-finger" the manual input of the satellites that are not
already loaded and would like to avoid that headache if at all possible!

Many thanks

David
KG4ZLB

-------------------------------------------------------------------------

[amsat-bb] Doppler.SQF
Mark L. Hammond
Sat Jun 6 15:14:30 UTC 2020

Hi David,

Here is a link worth bookmarking! Thanks to Mineo JE9PEL.

http://www.ne.jp/asahi/hamradio/je9pel/Doppler.sqf

73,
Mark N8MH

-------------------------------------------------------------------------

[amsat-bb] Doppler.SQF
David Worboys
Sat Jun 6 15:30:34 UTC 2020

Many thanks to Mark, N8MH

-------------------------------------------------------------------------

[amsat-bb] Active Satellites Doppler.SQF File
Les Rayburn
Sat Jun 6 15:55:06 UTC 2020

The link to Mineo's updated Doppler.SQF file is a great resource.
Thanks also to Mark for sharing it. I frequently take long breaks from
the hobby when work demands, and getting active on satellites again
after a hiatus is always a challenge. This helps a lot.

I'm most active on voice satellites, linear birds and FM.
Which satellites are the most active currently to look for contacts?

73,

Les Rayburn, N1LF
Maylene, AL
EM63nf

-------------------------------------------------------------------------

[amsat-bb] Doppler.SQF
Mineo Wakita
Sat Jun 6 15:59:18 UTC 2020

Please let me know if I make a miss_typo.

JE9PEL / Mineo Wakita

-------------------------------------------------------------------------

[amsat-bb] Active Satellites Doppler.SQF File
Mark L. Hammond
Sat Jun 6 16:04:37 UTC 2020

Hi Les. This is one of the best places to see what is operational.
Another good one to bookmark. Or make it your browser's startup page ;)

https://www.amsat.org/status/

73,
Mark N8MH

-------------------------------------------------------------------------

[amsat-bb] Doppler.SQF
David Worboys
Sat Jun 6 16:12:42 UTC 2020

I copied the file and rebooted but some frequencies are still
not showing in the main window so maybe I missed a step somewhere
- thank you for providing the file though!

David
KG4ZLB

-------------------------------------------------------------------------

[amsat-bb] Doppler.SQF
Dave Webb KB1PVH
Sat Jun 6 16:19:59 UTC 2020

You need to make sure the satellite name in doppler.sqf match
the name in the keps EXACTLY.

Also, knowing how to add or modify entries in the doppler.sqf file is
a good skill to have if you plan on using SatPC32. AMSAT has a page that
will generate the the lines for you from info you input.
https://www.amsat.org/doppler-sqf-line-generator/

Dave-KB1PVH

-------------------------------------------------------------------------

[amsat-bb] Doppler.SQF
Bill Booth
Sat Jun 6 16:31:04 UTC 2020

On 2020-06-06 12:12 p.m., David Worboys via AMSAT-BB wrote:
> so maybe I missed a step somewhere

No you did not. Some of the sats on that list are not the same names
as in the Amsat published list for tracking.
I just used it and found the same.

Bill Booth VE3NXK
Sundridge ON, Canada
FN05ns

-------------------------------------------------------------------------

[amsat-bb] Doppler.sqf
Bob
Sat Jun 6 17:33:33 UTC 2020

If I have to manually update the doppler text files what is
the purpose of the Update Keps button in SatPC ?

Bob

-------------------------------------------------------------------------

[amsat-bb] Doppler.SQF
bernd1peters
Sat Jun 6 19:54:29 UTC 2020

Give an example of which ones are not showing up, that might make it
a little easier to help you.

73,
Bernd - KB7AK

-------------------------------------------------------------------------

[amsat-bb] Doppler.sqf
Charles Reiche
Sat Jun 6 23:27:40 UTC 2020

Keps set where the satellite is in its orbit.
The doppler file sets the frequencies and modes that the satellite
operates on.
The two together are used by SatPC32 to put your radio uplink and
downlink frequencies in the right place at the right time.

73
N3CRT
Charles Reiche

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
Les Rayburn
Sun Jun 7 02:01:37 UTC 2020

So I cut and pasted the new Doppler.SQF file from
JE9PEL / Mineo Wakita site. Restarted, but none of the satellites will
track frequency. I assume this is due to a difference in the naming
conventions in the Kep file. 

I use "NASA ALL" for my keps. Not certain which version Mineo uses for
his. Hate to complain about software when the proceeds are going to
support AMSAT (much appreciated). But why does this have to be so
difficult?
It really should be as easy as "update Keps" and everything syncs.

Two pet peeves-

- The lack of standardization in how satellites are named. And then they
  change names. This causes confusion and incompatibility with software,
  tracking apps, etc. Why not settle on a standard and stick to it? 

- The lack of modern GUI and user-friendly software for the amateur
  satellite community.   If someone suggests open-source nonsense,
  my head might explode. Happy to pay handsomely for anyone who codes
  something to make this all easier. 

When I find another few hours with nothing to do, I'll try to edit the
Doppler.SQF file to match, troubleshoot until it works, etc. 

Thanks anyway. Probably won't see me back on the birds this weekend.
My hobby time is too limited. 

73,
Les Rayburn, N1LF
Maylene, AL
EM63nf

-------------------------------------------------------------------------

[amsat-bb] Doppler.SQF
Mineo Wakita
Sun Jun 7 02:38:32 UTC 2020

OK, I will improve my SQF file.
Please wait for a while.

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
Stefan Wagener
Sun Jun 7 02:59:37 UTC 2020

Les and others,
Sorry, but why is this so difficult?

Kepplerian elements are numerical data describing the orbit of a
satellite. Math based on certain algorithms presented in 2 line format
via service providers like Spacetrak and Celestrak generated by NORAD.

These "keps" will never include any information on what frequencies a
satellite uses, since this is totally irrelevant and useless information
for describing the orbit of a satellite. NORAD the originator of our
orbital data does not, will not and should not care about a certain
satellite frequency on 2m or 70cm. They just track orbital objects.

SatPC32 will use any 2 line element source you tell it to use and track
the satellite just fine. For tracking it just needs that information.
Now, SatPC32 also allows for doppler correction and radio control of
frequencies. It is handled by a small text file called doppler.sqf. That
file will need someone to tell it what the new frequencies are and for
what satellite. The author of SatPC32  "Erich Eichman" has no idea, or
crystal ball or visions in his dreams of which frequency a new satellite
will use. That's why he has given us the ability to edit the file as we
seem fit.

The only requirement is that the name of the satellite matches the name
of the satellite that you selected with your keps. How else would the
software know? Any and all satellite tracking software that does doppler
control will require some sort of that input. SatPC32 does not have a
magical wand or AI to do that for you.

As of this moment we have maybe around 20 satellites that have some sort
of amateur transponder and folks are finding it difficult editing a
simple text file to match a satellite name and add some frequencies?
All this information is available online.

Copying someone's doppler.sqf file is also not a good idea! That file
is customized by someone based on the keps and satellite name they are
using and sometimes even specific for their location since SatPC32 lets
you adjust the doppler control based on your location and satellite and
internally adjust the doppler.sqf frequencies.

The author of SatPC32 has spent thousands of hours working on this
program and he gets no financial return. He has donated the software
to AMSAT and still updates it for new radios and features!
Complaining about that is just not right!

Hope that helps.
73 Stefan VE4SW

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
Les Rayburn
Sun Jun 7 05:58:00 UTC 2020

If one has unlimited time, nothing is difficult. Most of us don't.
Some of us have very limited time for hobby activities and would rather
spend it making contacts rather than editing text files. 

There seem to be two fixes for this problem:

- Standardize on a single name for a given satellite. Then it will
  agree across multiple pieces of software and avoid confusion. 

- Write a subroutine that will ensure that the naming convention of your
  Doppler.SQF file agrees with the Keps that you're using in SatPC32,
  and correct it if necessary. 

This would say thousands of hams from editing text files—saving crazy
amounts of hours for the hobby overall. I'd be more than willing to
support anyone who wants to write that code. 

Your point is taken. But as I've said, I frequently must take hiatus
from the hobby to do my work. It requires a lot of travel and massive
hours devoted to each project that comes along. These can last weeks
or months. If we have an active "launch period" during that time,
I face this task over and over again. 

This will make at least the 10th time I've gone through this exercise.
It's tiresome. The satellite community enjoys some fo the brightest
hams in the hobby—yet we struggle with software to control our radios
and track satellites that doesn't have a modern GUI. 

73,
Les Rayburn, N1LF
Maylene, AL 
EM63nf

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
Devin L. Ganger
Sun Jun 7 07:09:32 UTC 2020

Every TLE requires the satellite number, which as I understand is in
fact a unique identifier for the satellite (once the correct ID number
has been sorted out and matched up with the appropriate satellite after
the confusion of launch). Even though the name of the satellite can vary,
this ID number is effectively the GUID for the satellite and does not
change during the satellite's lifetime. Correct?

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?

It seems to me that something like this would immediately solve a lot of
small but recurrent issues and annoyances. The name field can become
simply a human-readable label and not have to serve double-duty --
allowing users to switch between multiple TLE sources without having
to worry that they're giving satellites different names (and having to
go hunt down and replace all the entries in your various .SQF files).

Devin L. Ganger (WA7DLG)

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
Les Rayburn
Sun Jun 7 09:27:21 UTC 2020

It appears that the issue of satellite naming conventions may be coming
to a head quickly. Noted in the AMSAT Weekly News Service Bulletin: 

https://celestrak.com/NORAD/documentation/gp-data-formats.php

This may force a revision to how SatPC32 handles Kep files—and perhaps
provide the opportunity to improve things in terms of updates. 

Ideally, the software would keep any adjustments that have been made
by the operator for individual satellites but update when new birds
are launched.

73,
Les Rayburn, N1LF
Maylene, AL 
EM63nf

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
PE0SAT
Sun Jun 7 10:13:36 UTC 2020

This subject isn't new and therefor SatPC32 already has the
AmsatNames.txt config file.

Look at the AmsatNames.txt in your SatPC32 config directory.

; This file contains the AMSAT names of actual amateur radio
; satellites. The auxiliary file SatRename evaluates this file
; to replace the satellite names used in Space-Track TLE
; data files with their AMSAT names.
;
; Column #1 contains the 5-digit "Identification Number" used in
; TLE files (data line #1, columns 3 - 7).
;
; Column #2 contains the satellite's 8-digit "International
; Designator" (data line #1, columns 10 - 17),
;
; Column #3 contains the satellite's AMSAT name.
;
; When a new satellie is available, it can be added to this list.
; Note, that the "Identification Number" and the "International
; Designator" must contain a fix number of digits.

07530 74089B   AO-07
14129 83058B   AO-10
20439 90005D   AO-16
22825 93061C   AO-27
26609 00072B   AO-40
27605 02058A   AO-49
28375 04025K   AO-51

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
Alan
Sun Jun 7 11:33:58 UTC 2020

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

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
KD2NFC, Joe Puma
Sun Jun 7 19:10:36 UTC 2020

Thanks for your input.

"Copying someone's doppler.sqf file is also not a good idea! That file
is customized by someone based on the keps and satellite name they are
using and sometimes even specific for their location since SatPC32 lets
you adjust the doppler control based on your location and satellite
and internally adjust the doppler.sqf frequencies."

Okay so send the matching TLE file when sending a custom Doppler.sqf
file. If they changed the name of the bird in the TLE to match the
Doppler file, than that TLE file should be made available. We do thank
the ones that provide the Doppler file but let's make it make sense.

"The author of SatPC32 has spent thousands of hours working on this
program and he gets no financial return. He has donated the software
to AMSAT and still updates it for new radios and features!
Complaining about that is just not right!"

Umm, I paid for the software so I don't know what this means.
This group is used to troubleshoot and ask questions about the program,
among other things, so that's what's being done here.  

We're at a time where everyone feels a need to add an opinion.
That's great, I just ask that it's helpful and productive.

Have a nice day everyone, 73

Joe
KD2NFC

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
Mike Diehl
Sun Jun 7 20:13:19 UTC 2020

Ok, you can't just send some TLE's along with the SQF. TLE's are dynamic,
some more than others, but still dynamic. One boost of ISS and what you
had yesterday is invalid today.

You might have paid for SatPC32 but the author gets nothing from it as far
as I'm aware. From my understanding the proceeds are a donation to AMSAT.

Could there be an interface for adding transponder details rather than
using a CSV file? Sure. Are people just lazy for not taking a few moments
to figure out how to add a line? Absolutely!

I've never used the program for tracking and tuning, it's not my interest.
I did open the manual, figured out what each filed is and then worked up
some simple PHP (something I also don't use) and made a page for the AMSAT
site for generating new lines. You can find it here
https://www.amsat.org/doppler-sqf-line-generator/

Seriously, this is a tech based hobby. We're using spacecraft to
communicate with each other. It's incredibly depressing to see so many
people stumped by a simple text file. That or they're just too lazy to
spend a minute to figure it out. I also don't want to hear
"I don't have that much time to devote to the hobby" as posted earlier.
It literally takes longer to write a post complaining than it does to
read the 1 or 2 pages in the manual that describe how to use it.

Don't like the program? Don't use it and find something else.
Install GPredict and use that. Don't like certain features or feel
something is missing? It's open source, take the time to help with
development. Plenty of people are devoting their time for everyone's
benefit with no monetary gain yet there's always complaints or a
refusal to just open the manual, it really isn't that hard. 

73,
Mike Diehl
W8LID/VE6LID

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
Devin L. Ganger
Sun Jun 7 20:39:13 UTC 2020

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.

Does that name have to match up to what is in the TLE file, or what is
in the AmsatNames.txt file?

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?
Does the AmsatNames.txt file permit SatPC32 to ignore the name that my
selected TLE source is using for that same satellite?

Thanks in advance,

Devin L. Ganger (WA7DLG)

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
Alan wa4sca
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 above.

73,
Alan
WA4SCA

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
KD2NFC, Joe Puma
Sun Jun 7 20:58:24 UTC 2020

"Seriously, this is a tech based hobby. We're using spacecraft to
communicate with each other. It's incredibly depressing to see so many
people stumped by a simple text file. That or they're just too lazy to
spend a minute to figure it out. I also don't want to hear "I don't
have that much time to devote to the hobby" as posted earlier.
It literally takes longer to write a post complaining than it does
to read the 1 or 2 pages in the manual that describe how to use it"

I don't think that's happening here. At least not by me. I recognized
that a Doppler file I found on the internet, which was pretty robust
and time consuming for the person who put it together was really helpful,
so I used it. I'm new to pcsat32 but quickly learned that I had to edit
the Doppler file because of a mismatch in names from somewhere and I'm
just learning it's from the TLE I was using which was nasabare.txt.
I'm no stranger to the function of a TLE file. 

I also got up to speed with the AMSATnames.txt file. Okay great, it could
be useful but quickest solution was to edit Doppler.sqf. Which I did for
most of the sats I use but I was still thinking that if the original
creator of the Doppler file that I found has these sats matching up with
a TLE file on his computer, well then why don't he post that as well.
If I had that my issue would be solved right? Sounds like I'm trying
to use my brain, no?

I've come to this board to ask these questions in the past but they fell
on deaf ears. I basically solve my own problems and create solutions
where there isn't any. It has nothing to do with anyone being lazy,
at least for me, I'm trying to figure out how to benefit from the file
easily which should really be a file copy and go. So if the creator made
a amsatnames.txt or changed the names in the nasabare.txt, if I had
access to those files it would be plug n play. Thats the IT guy in me,
find the solution or path of least resistance. 

Btw GPredict is a great program but I got errors in reading position
with my g5500 usb interface and the radio control doesn't change the
modes on my FT-847. I run it on a raspberry pi. I wouldn't of purchased
pcsat32 if it weren't for those issues but I've come to like pcsat32
for the old goat that it is.

Joe
KD2NFC

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
Devin L. Ganger
Sun Jun 7 21:19:56 UTC 2020

That's awesome, thank you for taking the time to answer in detail.
Why don't more responses on this list point people to this functionality?
Is it not well known?

Devin L. Ganger (WA7DLG)

-------------------------------------------------------------------------

[amsat-bb] Satellite Hiatus--Doppler.SQF
Erich Eichmann
Mon Jun 8 19:54:57 UTC 2020

Hello,
I have added the following hints  to the FAQs file
http://www.dk1tb.de/FAQ_e.htm
(sect. 5s at the end of the file):

s.  Use of different Kepler data files with different satellite names

The various Kepler data files (source files) often use different names
for the same satellite. This is e.g. the case with some of those
contained in the AMSAT file nasa.all on the one hand and the Celestrak
files (amateur.txt, cubesat.txt etc.) on the other. This can lead to a
satellite or its frequencies not being displayed when the source file is
changed although the file contains data for the relevant satellite.

A solution to the problem is an entry for the satellite in the auxiliary
file AmsatNames.txt. The file already contains a list with the
identifiers (catalog numbers) of the satellites important for radio
amateurs and the assigned satellite names and instructions on how to
make the entry.

The names from a source file, e.g. nasa.all, or even self-made ones can
be used as names. They should of course be as memorable as possible
(that's why the 5-digit identifier itself is not suitable as a name,
although that would be possible).

With the option 'Use Amsat Names if Available' the program then uses the
assigned name with all source files, regardless of a different name in
the source file. It is displayed in SatPC32 and can be used in all data
files that require a satellite name such as Doppler.SQF, Prior.SQF,
SubTone.SQF or Squint.SQF. This means that all source files containing
data for the satellite can be used.

-------------------------------------------------------------------------

Subject: Re: SatPC32 file Doppler.SQF
From: Erich Eichmann
To: Mineo Wakita
Date: Sun, 21 Jun 2020 10:06:34 +0200

Hello Mineo,
thank you for the info.

When I tried your Doppler.SQF some days ago, I noticed that my SatPC32
didn't show the frequencies, except the ones of the ISS. With my own
Doppler.SQF I'm using the AMSAT names of the popular sats
(RS-44, AO-07, SO-50 etc.). So, I modified the names of these sats to
their AMSAT names (as far as available) and then your Doppler.SQF worked.

I attach the modifed file, you can see the changes e.g. with AO-07 or
RS-44 (I entered RS-44 with that name and left also the previous entry).
In my FAQs file http://www.dk1tb.de/FAQ_e.htm#UseOfSatnames

I have descriebed how to use the satellite names with the program.
The different names in AMSAT files on one hand and Space Track/Celestrak
files on the other are no pleasure, hi. To overcome that issue I added
the file AmsatNames.txt to the program, already 2005 when we were
allowed to obtain also the Space Track files.

I intend to prefer the following solution:
In menu 'Satellites > Sat. Names' use option 'Use Amsat Names if
Available' (default). Basically I use nasa.all or nasabare.txt
(both contain same sats and same names), as source file, because
the names are more handy than the Space Track/Celestrak names.

The aux. file AmsatNames.txt contains the identifiers of ALL
satellites contained in nasa.all/nasabare.txt and the assigned
sat names from these files. Creating AmsatNames.txt is no problem.

I have a new little tool 'CreateAmsatNames.exe' which creates
AmsatNames.txt via mouse click from nasa.all/nasabare.txt
You can download it here:
http://www.dk1tb.de/CreateAmsatNames.exe
Simply copy it into the SatPC32 program folder. 

With this solution the program will work with the AMSAT Keps files
and also with the Space Track/Celestrak files. If the sat is also
contained in nasa.all/nasabare.txt the program will automatically
convert the different name of the Space Track source file into its
AMSAT name.

With satellites that are not contained in nasa.all/nasabare.txt
but only in other source files the program will use the name from
the source file  for Doppler.SQF, SubTones.SQF etc.

I hope I can soon upload a new release and hopefully then all will work.
73s, Erich, DK1TB

> Am 20.06.2020 um 16:10 schrieb Mineo Wakita:
> 
> Hello Erich, DK1TB.
> 
> I'm using the following TLE in PE0SAT's site.
> 
> http://tle.pe0sat.nl/kepler/mykepler.txt
> 
> And the satellite name is edited by myself
> referring to many sites such as NASA and Spase-Track.
> 
> I'm wondering how to make my Doppler.SQF file versatile.
> 
> http://www.ne.jp/asahi/hamradio/je9pel/satslist.htm
> http://www.ne.jp/asahi/hamradio/je9pel/Doppler.sqf
> 
> Thank you.
> JE9PEL, Mineo Wakita

>> Subject: SatPC32 file Doppler.SQF
>> From: Erich Eichmann
>> To: Mineo Wakita
>> Date: Sat, 20 Jun 2020 09:01:15 +0200
>> 
>> Hello Mineo,
>> I'm Erich, DK1TB, author of SatPC32.
>> 
>> Recently there were several posts to AMSAT-BB by users who had
>> problems with the SatPC32 file Doppler.SQF when trying to add
>> new satellites to the file.
>> 
>> I downloaded your Doppler.SQF file  
>> http://www.ne.jp/asahi/hamradio/je9pel/Doppler.sqf
>> 
>> It is an excellent file because it is uptodate and  contains almost
>> all satellite of interest for radio amateurs. The Doppler.SQF
>> that is shipped with SatPC32 doesn't contain some of the newer
>> sats. I have problems to use your file, however, due to the different
>> sat names.
>> 
>> My question:
>> What Keps file did you use, from where did you downlod the Keps?
>> 
>> Many of the satellite names in your file are different from the
>> names in AMSAT Keps files (nasa.all, nasabare.txt) and the
>> Celestrak Kepsfiles (amateuer.txt, cubesat.txt etc)
>> 
>> The satellite name for e.g. AO-07 is
>> in nasa.all: AO-07
>> in amateur.txt:  OSCAR 7 (AO-7)
>> in your Doppler.SQF: AO-7 (Phase-2B)
>> 
>> Many thanks.
>> Best regards.
>> 73s, Erich, DK1TB

-------------------------------------------------------------------------

Subject: Re: Re^2: SatPC32 file Doppler.SQF
From: Erich Eichmann
To: Mineo Wakita
Date: Tue, 23 Jun 2020 19:21:37 +0200

Hello Mineo,
thank you for the summary of the articles regarding problems with
Doppler.SQF on AMSAT-BB.

I dealt with your Doppler.SQF the past days. The file is very good,
I think, because it contains almost all satellites of interest for
radio amateurs - far more than my current one. The missing frequency
display in SatPC32 is caused by the different satellite names used
in the file. SatPC32 expects the AMSAT format for sat names in
Doppler.SQF, Prior.SQF etc.

The AMSAT source file nasa.all (nasabare.txt contains the same sats)
provides Keps for  approx. 200 sats. That are Keps for about 80% of
the sats recorded in your Doppler.SQF. So, for these satellites,
I replaced the names in your Doppler.SQF by the names from nasa.all.
With that changes the program works flawlessly with all sats contained
in nasa.all / nasabare.txt.

In menu 'Satellites > Sat.Names' option 'Use AMSAT Names if Available'
(default) should be used.


The Space Track / Celestrak source files, e.g. amateur.txt, contain
many of the satllites that are contained also in nasa.all, but the sat
names are different from the AMSAT names. So, using the sat names of
the file will not work. If you want to use these files also the program
therefore needs to convert the names used in the Celestrak files to
their AMSAT names. That is done by AmsatNames.txt. The file identifies
the satellite by its 5-digit 'identifier' (contained in the Keplerian
data set and unique with all Keps files) and assigns the corresponding
AMSAT name to the identifier. The program checks whether the identifier
from the data set of the selected satellite is includet in AmsatNames.txt.
If so, the program always uses the name assigned to the identifier in
AmsatNames.txt, regardless of the possibly different name in the source
file used. This name is displayed in the program window. It must also
be used when entering files that require a satellite name (Doppler.SQF,
Prior.SQF, SubTone.SQF, Sqint.SQF). The same applies to the programs
SatPC32ISS, Wisat32, see also

http://www.dk1tb.de/FAQ_e.htm#UseOfSatnames

I have written a little tool (CreateAmsatNames.exe) which creates
(and updates) AmsatNames.txt via mouse click from nasa.all.
So, the file contains the identifiers and assigned amsat names for
all satellites  contained in nasa.all.

If the user wants to track a satellite for which the AMSAT files don't
contain data, he has to enter  the sat name  used in the  source file
into Doppler.SQF, Prior.SQF etc., of course.

I hope, I can soon upload the modified Doppler.SQF, the modified
AmsatNames.txt and CreateAmsatNmes.exe on my website and post the
links to AMSAT-BB for users who want to test the files. I will be
best to test the files with Config III or IV. So, Configs I and II
remain unchanged.

73s, Erich, DK1TB

-------------------------------------------------------------------------

SatPC32 file Doppler.SQF update

Subject: Re: Re^2: SatPC32 file Doppler.SQF
From: Erich Eichmann
To: Mineo Wakita
Date: Thu, 25 Jun 2020 08:44:24 +0200

Hi Mineo,

attached  the modified Doppler.SQF. As you see I have completed my
file with data from your Doppler.SQF. I modied the names of the
satellites for which nasa.all / nasabare.txt contain the Keplerian
data. Also, I added a few data lines with some of the sats.

http://dl.dropbox.com/s/e8fy2ha0n18vdo8/Doppler.SQF

Your file is an execellent summary of all satellites of importance
for radio amateurs. I didn'd update my file that comes with SatPC32
for a longer time because I was too busy with other work on SatPC32
(and other issues in house and family). I would like to replace my
present file in SatPC32 by the attached one. Is that ok? I would
mention on AMSAT-BB or in the What's New file that I completed
Doppler.SQF with the data from your file.

73s, Erich, DK1TB, author of SatPC32

> Am 22.06.2020 um 21:35 schrieb Mineo Wakita:
> 
> Thank you for much information about SatPC32.
> On my next site, I have summarized all the articles
> published on AMSAT-BB. Especially look at the end.
> Thank you.
> 
> http://www.ne.jp/asahi/hamradio/je9pel/dopp2sqf.htm
> http://www.ne.jp/asahi/hamradio/je9pel/satslist.htm
> 
> JE9PEL, Mineo Wakita

-------------------------------------------------------------------------

Modified Doppler.SQF

Subject: Modified Doppler.SQF
From: Erich Eichmann
To: AMSAT-BB, Mineo Wakita
Date: Sun, 28 Jun 2020 11:27:49 +0200

Hi, I have uploaded a ZIP file, containing:

a) a  modified  Doppler.SQF file (initially for testing and complementing
   before it replaces the present one in the SatPC32 setup file).
   The file extends the previous data with the data from the Doppler.SQF
   file from JE9PEL. This excellent file contains the radio data for
   almost all satellites important for radio amateurs. To be compatible
   with other files I replaced the satellite names used in the file by
   their AMSAT names (names used in nasa.all, nasabare.txt etc.).
   The modified file therefore manages a significantly larger number of
   satellites, especially newer ones than the previous one, already upon
   installation. The user doesn't need to add the satellites to
   Doppler.SQF himself.

b) a modified AmsatNames.txt file. The file is required for use of
   Doppler.SQF with Space Track/Celestrak Keps files due to their
   different satellite names. The file contains the satellite
   'identifiers' for all satellites contained in the Keps file
   nasa.all (approx. 200) and the assigned AMSAT names of these
   satellites.

c) the tool CreateAmsatNames.exe. The little program creates and updates
   AmsatNames.txt from nasa.all via mouseclick.

The ZIP file can be downloaded here:
http://www.dk1tb.de/NewDoppler.ZIP
http://dl.dropbox.com/s/mnjh2glpfkx0mxj/NewDopper.zip

If you want to test the files it will be best to unzip Doppler.SQF and
AmsatNames.txt into the sub folders CfgIII or CfgIV of the SatPC32 data
folder (path shows up in the footline of menu 'Satellites'. Since the
folder AppData in the path is hidden by default make hidden files and
folders visible).

Then they can be tested with the SatPC32 configurations 3 or 4 and 1
and 2 remain unchanged. To keep the present files you may rename them.

Unzip CreateAmsatNames.exe into the SatPC32 program folder and start
it with the File Explorer or add an entry to aux. file Programs.SQF.

73s, Erich, DK1TB, author of SatPC32


Back to Top
Back to Home Page