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
Good morning Jim,
SatPC32 has a solution for this and it called AmsatNames.txt.
Click "?" -> Auxiliary Files -> AmsatNames.txt, this will give you the option the use alternative names.
I hope this is helpful.
Jan PE0SAT
On 04-02-2021 10:21, James Jipping wrote:
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
Object names with spaces are not exactly uncommon in the space-track catalog. In fact, just looking at the first few entries shows: 0 VANGUARD 1 1 00005U 58002B 21029.28808560 -.00000076 00000-0 -11346-3 0 9994 2 00005 34.2570 252.5344 1847877 288.6483 52.2921 10.84858932229781 0 VANGUARD 2 1 00011U 59001A 21029.82316623 .00000343 00000-0 18757-3 0 9993 2 00011 32.8666 285.4967 1467471 89.4624 287.3328 11.85740568643606 0 VANGUARD R/B 1 00012U 59001B 21029.61362424 .00000164 00000-0 81891-4 0 9992 2 00012 32.9013 279.6520 1666175 185.0152 173.1560 11.44390876305899
Even the example TLE at space-track ( https://www.space-track.org/documentation#tle ) has a space in it...
So... if the protocol you are using (or the code to handle it) does not handle object names with spaces correctly... maybe it's time for that protocol or code to be re-thought somewhat?
73 Mark VK5QI
On Thu, Feb 4, 2021 at 7:52 PM James Jipping [email protected] wrote:
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
On 2/4/21 3:21 AM, James Jipping wrote:
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.
This sounds like a great article for the Journal. I'm interested in learning more!
--- Zach N0ZGO
BTW, MacDoppler also outputs data in UDP. I don't know if the format is anywhere close to the same.
On Thu, Feb 4, 2021 at 9:54 AM Zach Metzinger [email protected] wrote:
On 2/4/21 3:21 AM, James Jipping wrote:
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.
This sounds like a great article for the Journal. I'm interested in learning more!
--- Zach N0ZGO
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
Hi folks--I thought SatPC32 uses DDE. Is that what is being used with the RPi? I don't recall any UDP network traffic being supported...but I'm a nucleic acids biochemist, what do I know ;)
Mark L. Hammond [N8MH] AMSAT Director and Command Station
On Thu, Feb 4, 2021 at 9:55 AM Zach Metzinger [email protected] wrote:
On 2/4/21 3:21 AM, James Jipping wrote:
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.
This sounds like a great article for the Journal. I'm interested in learning more!
--- Zach N0ZGO
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
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
Hi Greg,
Basically the current TLE structure is the main problem and I hope that the new structure, that is right at the corner, will provide in some of these issues.
Looking at NAYIF all the names make sense: NAYIF-1 is name used during development, FUNcube-5 is the name of a payload on NAYIF-1 and EO-88 is its Oscar designation.
This is very common but we are not able to register all these names with the current 3 line elements.
Your second remark is more difficult, every time after launch there is the TLE lottery, what satellite belong to what object, so in my opinion it would make sense to create a unique id that won't change and match its orbital elements when they are determined.
Lets see what the new TLE structure will bring on the this page https://celestrak.com/NORAD/elements/gp-index.php you can already see what is coming.
@Erich Eichmann, is there already development being done to adopt these new element structures in SatPC32, if so, and you need a beta tester, let me know.
All the best,
Jan PE0SAT
On 04-02-2021 18:38, Greg D wrote:
Human-readable names will always be a problem, spaces or not. Consider how many different names each bird has over time. EO-88, Funcube-5, and Nayif-1 are all the same thing, as are AO-91, RadFxSat, and Fox-1B. TLEs have only a single slot for name; which one do you use?
Worse, PSAT2 and PSAT-2 are two different objects.
Given the need is for an application, the appropriate name to use is the machine-readable one. That would be the catalog number. It's globally unique. Why not use that?
Greg KO6TH
Erich Eichmann wrote:
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
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
-----------------------------------------------------------
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
Am I missing something?
For more than 50 years AMSAT has been issuing OSCAR numbers to satellites that qualify. More than 100 have been issued to date. Is someone suggesting that we stop doing that? I hope not. What qualifies for an OSCAR number? Google "OSCAR Numbers Policy" and see for yourself. 73 Ray W2RS
-----Original Message----- From: PE0SAT | Amateur Radio via AMSAT-BB [email protected] To: Greg D [email protected] Cc: Erich Eichmann [email protected]; James Jipping [email protected]; AMSAT-BB [email protected] Sent: Thu, Feb 4, 2021 11:01 am Subject: [AMSAT-BB] Re: Satellite names in nasabare.txt
Hi Greg,
Basically the current TLE structure is the main problem and I hope that the new structure, that is right at the corner, will provide in some of these issues.
Looking at NAYIF all the names make sense: NAYIF-1 is name used during development, FUNcube-5 is the name of a payload on NAYIF-1 and EO-88 is its Oscar designation.
This is very common but we are not able to register all these names with the current 3 line elements.
Your second remark is more difficult, every time after launch there is the TLE lottery, what satellite belong to what object, so in my opinion it would make sense to create a unique id that won't change and match its orbital elements when they are determined.
Lets see what the new TLE structure will bring on the this page https://celestrak.com/NORAD/elements/gp-index.php you can already see what is coming.
@Erich Eichmann, is there already development being done to adopt these new element structures in SatPC32, if so, and you need a beta tester, let me know.
All the best,
Jan PE0SAT
On 04-02-2021 18:38, Greg D wrote:
Human-readable names will always be a problem, spaces or not. Consider how many different names each bird has over time. EO-88, Funcube-5, and Nayif-1 are all the same thing, as are AO-91, RadFxSat, and Fox-1B. TLEs have only a single slot for name; which one do you use?
Worse, PSAT2 and PSAT-2 are two different objects.
Given the need is for an application, the appropriate name to use is the machine-readable one. That would be the catalog number. It's globally unique. Why not use that?
Greg KO6TH
Erich Eichmann wrote:
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
-----------------------------------------------------------
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
-----------------------------------------------------------
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
participants (9)
-
Burns Fisher -
Erich Eichmann -
Greg D -
James Jipping -
Mark Jessop -
Mark L. Hammond -
PE0SAT | Amateur Radio -
Ray Soifer -
Zach Metzinger