| |
CX2SA > SATDIG 07.06.20 23:13l 744 Lines 25479 Bytes #999 (0) @ WW
BID : AMSATBB15188
Read: GUEST
Subj: AMSAT-BB-digest V15 188
Path: IW8PGT<I3XTY<I0OJJ<EA2RCF<CX2SA
Sent: 200607/2108Z @:CX2SA.SAL.URY.SOAM #:33126 [Salto] FBB7.00e $:AMSATBB15188
>From cx2sa%cx2sa.sal.ury.soam@i0ojj.ampr.org Sun Jun 7 23:09:54 2020
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0n) with SMTP
id AA115080 ; Sun, 07 Jun 2020 23:09:54 +0200
Message-Id: <AMSATBB15188@ea2rcf.bbs>
>From: cx2sa@cx2sa.sal.ury.soam
X-JNOS-User-Port: Telnet (ea2rcf @ 94.177.237.192) -> Sending message
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Re: Satellite Hiatus--Doppler.SQF (Les Rayburn)
2. Re: Satellite Hiatus--Doppler.SQF (PE0SAT | Amateur Radio)
3. Re: Satellite Hiatus--Doppler.SQF (Alan)
4. Re: PacsatGround Software (Chris Thompson)
5. Re: Satellite Hiatus--Doppler.SQF (KD2NFC, Joe Puma)
6. Re: Satellite Hiatus--Doppler.SQF (Mike Diehl)
7. TEST (Joseph Trombino, Jr)
8. Re: Satellite Hiatus--Doppler.SQF (Devin L. Ganger)
9. Re: Satellite Hiatus--Doppler.SQF (Alan)
10. Re: Satellite Hiatus--Doppler.SQF (KD2NFC, Joe Puma)
----------------------------------------------------------------------
Message: 1
Date: Sun, 7 Jun 2020 04:27:21 -0500
From: Les Rayburn <les@????????????.???>
To: "Devin L. Ganger" <devin@????????.???>
Cc: AMSAT bbs <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Satellite Hiatus--Doppler.SQF
Message-ID: <8393951D-6876-4D84-955D-3214F3AC373A@????????????.???>
Content-Type: text/plain; charset=utf-8
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
<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 #38965, ARRL Life Member, CVHS Life Member, SVHF Member
------------------------------
Message: 2
Date: Sun, 07 Jun 2020 12:13:36 +0200
From: PE0SAT | Amateur Radio <pe0sat@?????.??>
To: Les Rayburn <les@????????????.???>
Cc: AMSAT bbs <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Satellite Hiatus--Doppler.SQF
Message-ID: <907cf06f1c328b97a41b9291add47185@?????.??>
Content-Type: text/plain; charset=UTF-8; format=flowed
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
On 07-06-2020 11:27, Les Rayburn via AMSAT-BB wrote:
> 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
> <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 #38965, ARRL Life Member, CVHS Life Member, SVHF Member
>
--
With regards PE0SAT
Internet web-page http://www.pe0sat.vgnet.nl/
DK3WN SatBlog http://satblog.dk3wn.info/
Online Telemetry Forwarder: https://db.satnogs.org/stats/
irc://chat.freenode.net #Cubesat - Twitter @??????
------------------------------
Message: 3
Date: Sun, 7 Jun 2020 06:33:58 -0500
From: "Alan" <wa4sca@?????.???>
To: "AMSAT-BB" <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Satellite Hiatus--Doppler.SQF
Message-ID: <001a01d63cbf$890059d0$9b010d70$@?????.???>
Content-Type: text/plain; charset="utf-8"
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
------------------------------
Message: 4
Date: Sun, 7 Jun 2020 10:34:25 -0400
From: Chris Thompson <g0kla@????.???>
To: Kevin <wa7fwf@?????.???>
Cc: AMSAT <amsat-bb@?????.???>
Subject: Re: [amsat-bb] PacsatGround Software
Message-ID:
<CAJOf0+sXH58DbDP8WQ5gQaVHE5o0PrLVpJhWSSdZnNNZsWJ3ng@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
Kevin,
Let me know any more details on the COM port bug. It should not do that :)
I logged it on github and will try to fix at some point.
73
Chris
On Sat, Jun 6, 2020 at 3:02 PM Kevin via AMSAT-BB <amsat-bb@?????.???>
wrote:
> Mike I tried replying privately but it bounced as "address couldn't be
> found, or is unable to receive mail".
>
> so here it is again
>
> Hi Mike,
> I run a 9612+ with pacsatground try this...
>
> Using putty or any other terminal program issue the following
>
> port 2
> cd ext/ext
> fulldup off/on
> mon off/on
> maxusers 0/1
> int kiss
> reset
>
> once you enter the reset you will now be in kiss mode and can no longer
> issue commands
>
> exit your terminal program
>
> now startup pacsatground and you should be in business
> make sure in pacsatground you turn off toggle out of kiss mode on exit
> or you will have to go through these steps each time you start it
>
> also I have noticed a bug where you exit pacsatground and the next time
> you start it says it cannot open the com port
> I'm thinking it leaves it in a odd state, to fix just go into windows
> device mgr and disable and then enable the com port and it should now work.
>
> Let me know if this does it for you.
>
>
> 73
> Kevin WA7FWF
>
>
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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
>
--
Chris E. Thompson
chrisethompson@?????.???
g0kla@????.???
------------------------------
Message: 5
Date: Sun, 7 Jun 2020 15:10:36 -0400
From: "KD2NFC, Joe Puma" <kd2nfc@?????.???>
To: Stefan Wagener <wageners@?????.???>, amsat-bb@?????.???
Subject: Re: [amsat-bb] Satellite Hiatus--Doppler.SQF
Message-ID: <EEE074E3-5036-4E41-82EC-16249E585D62@?????.???>
Content-Type: text/plain; charset=utf-8
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
Sent from my iPad
> On Jun 6, 2020, at 11:05 PM, Stefan Wagener via AMSAT-BB
<amsat-bb@?????.???> wrote:
>
> 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!
------------------------------
Message: 6
Date: Sun, 7 Jun 2020 16:13:19 -0400
From: Mike Diehl <diehl.mike.a@?????.???>
To: "KD2NFC, Joe Puma via AMSAT-BB" <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Satellite Hiatus--Doppler.SQF
Message-ID: <B35065CE-31DC-4E76-92C8-E0965E8E01EE@?????.???>
Content-Type: text/plain; charset=utf-8
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
> On Jun 7, 2020, at 15:13, KD2NFC, Joe Puma via AMSAT-BB
<amsat-bb@?????.???> wrote:
>
------------------------------
Message: 7
Date: Sun, 7 Jun 2020 16:24:15 -0400
From: "Joseph Trombino, Jr" <w2kj@?????????.???>
To: amsat-bb@?????.???
Subject: [amsat-bb] TEST
Message-ID: <F404436D-2764-44DE-8C43-E98D1A915E8F@?????????.???>
Content-Type: text/plain; charset=us-ascii
TEST
Testing to verify if account is still working.
73, Joe W2KJ
------------------------------
Message: 8
Date: Sun, 7 Jun 2020 20:39:13 +0000
From: "Devin L. Ganger" <devin@????????.???>
To: Alan <wa4sca@?????.???>, AMSAT bbs <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Satellite Hiatus--Doppler.SQF
Message-ID:
<MWHPR01MB235296DAE43168CFA746B7F4CA840@?????????????.????.????????????.???>
Content-Type: text/plain; charset="iso-8859-1"
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)
email:?devin@????????.???
web:?Devin on Earth
cell:?+1 425.239.2575
> -----Original Message-----
> From: AMSAT-BB <amsat-bb-bounces@?????.???> On Behalf Of Alan via
> AMSAT-BB
> Sent: Sunday, June 7, 2020 4:34 AM
> To: AMSAT-BB <amsat-bb@?????.???>
> 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@?????.???. 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
------------------------------
Message: 9
Date: Sun, 7 Jun 2020 15:54:43 -0500
From: "Alan" <wa4sca@?????.???>
To: "'Devin L. Ganger'" <devin@????????.???>
Cc: AMSAT-BB <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Satellite Hiatus--Doppler.SQF
Message-ID: <001501d63d0d$df6c8a70$9e459f50$@?????.???>
Content-Type: text/plain; charset="iso-8859-1"
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@????????.????
<Sent: Sunday, June 7, 2020 3:39 PM
<To: Alan <wa4sca@?????.???>; AMSAT bbs <amsat-bb@?????.???>
<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@????????.???
<web:?Devin on Earth
<cell:?+1 425.239.2575
<
<> -----Original Message-----
<> From: AMSAT-BB <amsat-bb-bounces@?????.???> On Behalf Of Alan via
<> AMSAT-BB
<> Sent: Sunday, June 7, 2020 4:34 AM
<> To: AMSAT-BB <amsat-bb@?????.???>
<> 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@?????.???. 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
------------------------------
Message: 10
Date: Sun, 7 Jun 2020 16:58:24 -0400
From: "KD2NFC, Joe Puma" <kd2nfc@?????.???>
To: Mike Diehl <diehl.mike.a@?????.???>
Cc: amsat-bb@?????.???
Subject: Re: [amsat-bb] Satellite Hiatus--Doppler.SQF
Message-ID: <0929AADB-50B1-42CB-9313-9C4BE3539522@?????.???>
Content-Type: text/plain; charset=utf-8
?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? lol
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
Instagram.com/kd2nfc
Sent from my iPad
> On Jun 7, 2020, at 4:16 PM, Mike Diehl via AMSAT-BB <amsat-bb@?????.???>
wrote:
>
> ?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
>
>> On Jun 7, 2020, at 15:13, KD2NFC, Joe Puma via AMSAT-BB
<amsat-bb@?????.???> wrote:
>>
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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
------------------------------
Subject: Digest Footer
_______________________________________________
Sent via amsat-bb@?????.???.
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 member? Join now to support the amateur satellite program!
https://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
End of AMSAT-BB Digest, Vol 15, Issue 188
*****************************************
Read previous mail | Read next mail
| |
