Hi Jim,
SatPC32 doesn't use a space as data deliminator in Doppler.SQF. The satellite name is contained in the first of the 3 lines of data sets in Nasa 3-line format. The program reads the complete text in this line. The other parameters (lines 2 and 3) are separated by commata. The error you get will not be sent by SatPC32, I think.
I don't have the source file with "OBJECT C" or "CAPE 3", but nasabare.txt contains satellite names like "NOAA 6" or "S-Net B". The program works flawlessly with these sat names with both options in menu Satellites > SatNames:  "Use Sat Names from Source File"  and "Use AMSAT Names if Available".

The SatPC32 DDE string outputs the name in the same format as it appears in the program.

As Jan, PE0SAT, mentioned already you can also add the relevant satellite to the aux. file AmsatNames.txt (that can be opened from menu "?"). Add the 5 digit identifier (contained in all Keps files). Then you can give the satellite any name you want. With the option "Use AMSAT Names if Available" the satellite will then appear with that name everywhere in the program.

73s, Erich, DK1TB

Am 04.02.2021 um 10:21 schrieb James Jipping:
Good Morning:

I recently wrote a Raspberry Pi application that uses the UDP transmission from SatPC32.  Works like charm,.  It selects the correct antenna (2M or 70cm) combos. It controls my crystal controlled WX receiver (auto selects the correct WX channel), selects the correct SDR / software setup for telemetry, etc.

Well, it worked like a charm until I encountered "OBJECT C" and "CAPE 3" in the elements.  SatPC32's UDP uses a space as a data deliminator, so I get an error ( the satellite string has one too many pieces of data, 9 instead of 8)  when SatPC323 starts to track one of these.    That's OK.  I just edit the keps file to read "OBJECT-C" and "CAPE-3" (which, by the way, is what it's called in all the literature).  Well, it's NOT OK .  It is pain in the  neck. Every time I want to update my keps I have to remember to edit the file.

Do I have to live with this anomaly ?   Or will the names become something without the space when they get their "official" designation?

Thank you, stay safe, Corvid free, and 73

Jim Jipping, W8MRR
AMSAT #5512



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

Sent via AMSAT-BB(a)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!

View archives of this mailing list at
https://mailman.amsat.org/hyperkitty/list/[email protected]
To unsubscribe send an email to amsat-bb-leave(a)amsat.org
Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org