[amsat-bb] more from the Satpc32 aggravation file
tomdoyle1948 at gmail.com
Fri Aug 22 18:26:29 UTC 2014
Alan is correct, ignore my previous post and stick with Notepad. Just be
very careful, do everything right and you will not have any problems.
73 W9KE Tom Doyle
On Fri, Aug 22, 2014 at 12:36 PM, Alan <wa4sca at gmail.com> wrote:
> Hi Norm,
> I regularly edit the DOPPLER.SQF file using Notepad. Whenever there is an
> issue such as you mention,
> I always find that there is some subtle difference between the actual
> satellite name and that which I
> typed. Sometimes a space, for instance. You might well find that with a
> hex editor. Using the
> AMSATNAMES.TXT file is a good way to make certain the satellite name is
> exactly what you want it to
> You do needed to close and restart SatPC32 for the change to be
> recognized. Also, if you are adding a
> new entry at the end of the DOPPLER.SQF file, make certain you hit return
> at the end before saving. I
> have noticed in some places that if you don't to that, the last line is
> not parsed.
> Good luck,
> <-----Original Message-----
> <From: amsat-bb-bounces at amsat.org [mailto:amsat-bb-bounces at amsat.org] On
> Behalf Of Lizeth Norman
> <Sent: Friday, August 22, 2014 11:04 AM
> <To: <,amsat-bb at amsat.org>,
> <Subject: [amsat-bb] more from the Satpc32 aggravation file
> <Why would altering the doppler.sqf file not work with direct
> <modification via Windows Notepad?
> <The symptom is that the frequency is not recognized, although the line
> <in the doppler.sqf file is apparently correct.
> <Going over to the .tle file to check the spelling, spacing and so
> <forth on the satellite name, the bright idea overcame me to find out
> <what happens when I copy and paste the name (obviously the same to the
> <EYE!!!) from the .tle file to the doppler.sqf file.
> <Low and behold, it worked. Nothing in the rest of the line in the
> <doppler.sqf file was altered.
> <I surmise that even though the displayed characters are the same,
> <somehow they are not.
> <What is the formatting issue that I'm running into? This has happened
> <before AND I have not, until today found out why.
> <How do I fix this? I have spent a fair amount of headbanging here.
> <This is just the latest episode.
> <If I looked at the file in a hex editor, I am sure I would not know
> <what to look for. Probably break more than I fix.
> <Norm n3ykf
> <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
> <Not an AMSAT-NA member? Join now to support the amateur satellite program!
> <Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
> Sent via AMSAT-BB at amsat.org. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
> are solely those of the author, and do not reflect the official views of
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
Sent from my computer.
More information about the AMSAT-BB