OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

IW8PGT

[Mendicino(CS)-Italy]

 Login: GUEST





  
CX2SA  > SATDIG   03.12.17 05:25l 820 Lines 29894 Bytes #999 (0) @ WW
BID : AMSATBB12318
Read: GUEST
Subj: AMSAT-BB-digest V12 318
Path: IW8PGT<CX2SA
Sent: 171203/0315Z @:CX2SA.SAL.URY.SOAM #:28392 [Salto] FBB7.00e $:AMSATBB12318
From: CX2SA@CX2SA.SAL.URY.SOAM
To  : SATDIG@WW

Today's Topics:

   1. Re: AO-85 in GPredict (Paul Stoetzer)
   2. Help with Yaesu FT-736r (KD4ZGW)
   3. Re: Help with Yaesu FT-736r (John Brier)
   4. 5K0T logged sat times (Kevin M)
   5. VUCC Awards/Endorsements for November 2017 (John Papay)
   6. Re: 5K0T logged sat times (Paul Stoetzer)
   7. Re: VUCC Awards/Endorsements for November 2017 (R.T.Liddy)
   8. Re: Help with Yaesu FT-736r (Rob Dunham)
   9. Re: Help with Yaesu FT-736r (John Brier)
  10. Re: AO-85 in Gpredict (Mac A. Cody)
  11. Re: AO-85 in Gpredict (Greg D)


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

Message: 1
Date: Sat, 2 Dec 2017 13:29:15 -0500
From: Paul Stoetzer <n8hm@xxxx.xxx>
To: "Devin L. Ganger" <devin@xxxxxxxx.xxx>
Cc: radiomb <radiomb@xxxxxxxxx.xxx>, "amsat-bb@xxxxx.xxxx
<amsat-bb@xxxxx.xxx>,	"APBIDDLE@xxxxxxx.xxxx <APBIDDLE@xxxxxxx.xxx>
Subject: Re: [amsat-bb] AO-85 in GPredict
Message-ID:
<CABzOSOpXhsjLEZYkB83EHBhX-K-WYFCFCVwNby_qqf1Va7dC1Q@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"

Security theater. Obviously all the governments that we don't want
knowing exactly what orbit the primary payload(s) on that flight are
in have their own tracking systems.

73,

Paul, N8HM

On Sat, Dec 2, 2017 at 1:08 PM, Devin L. Ganger <devin@xxxxxxxx.xxx> wrote:
> As a side note, I am trying to understand hat purpose is served by
restricting the keps to a single public distribution point. I am failing. Is
there an actual realistic rationale, or is this yet another example of
security theater?
>
>
>
> Sent from my Windows 10 phone
>
>
>
> ________________________________
> From: AMSAT-BB <amsat-bb-bounces@xxxxx.xxx> on behalf of Alan
<wa4sca@xxxxx.xxx>
> Sent: Saturday, December 2, 2017 5:18:21 AM
> To: 'radiomb'; amsat-bb@xxxxx.xxx
> Subject: Re: [amsat-bb] AO-85 in GPredict
>
> Mike,
>
> For reasons which have to do with AO-85 being launched on a NRO mission,
there are permanent restrictions on the dissemination of its Keps.  The only
place you can download them is the AMSAT list.  It is called nasabare.txt,
though your program may call it something different such as "Amateur
(amsat.org)."  I don't use GPredict so can't give you details, but the issue
exists no matter what program you are using.
>
> 73,
>
> Alan
> WA4SCA
>
> <-----Original Message-----
> <From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of
> <radiomb
> <Sent: Friday, December 01, 2017 21:55 PM
> <To: amsat-bb@xxxxx.xxx
> <Subject: [amsat-bb] AO-85 in Gpredict
> <
> <
> <Hello,   Seeing the posts I downloaded Gpredict  to give it a try. I
could not find
> <AO-85 (FOX-1A) in satellites listed. Even AO-91 is in the current list.
Can it be
> <under some other name? I found a way to add a bird but looks like a pain to
> <update. Easy way?  And if AO-91 is in the list why was AO-85 left out?TNX
73
> <Mike K4MIA
> <_______________________________________________
> <Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb


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

Message: 2
Date: Sat, 2 Dec 2017 13:17:47 -0600
From: KD4ZGW <kd4zgw@xxxxx.xxx>
To: Amsat BB <AMSAT-BB@xxxxx.xxx>
Subject: [amsat-bb] Help with Yaesu FT-736r
Message-ID: <c45819cd-c352-ef74-3297-b519defbf606@xxxxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed

Can anyone help me get my Yaesu FT-736R to run on SatPC32?? I bought a
cable that will link the radio to the pc (via USB). But all it does is
automatically puts the radio in "CAT mode" and doesn't change
frequencies, when I shut it down, my radio is locked up and have to
power cycle to get it out of CAT mode. What settings do I need to change
in SatPC32?

I have been working on this for months to figure it out, I want to get
back on birds. I am getting a little frustrated with this radio.

Thanks for any advice

73 de Rob KD4ZGW



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

Message: 3
Date: Sat, 2 Dec 2017 16:11:09 -0500
From: John Brier <johnbrier@xxxxx.xxx>
To: KD4ZGW <kd4zgw@xxxxx.xxx>
Cc: Amsat BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] Help with Yaesu FT-736r
Message-ID:
<CALn0fKNuA0HgXkY0WgoQ=tNsPZJfcx5kOQDxLOzwCZNMf8CZjw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"

This is a bit of a shot in the dark, but I was reading the Mac Doppler
manual today trying to figure out something unrelated, and it
mentioned the FT-736R had a problem related to CAT mode. Here is the
text from the manual, perhaps it is relevant:

"Due to a problem with the FT-736R (see note in FT-736R manual page 36
bottom left) you may have to take MacDoppler out of CAT mode, press
the REV key on the FT-736R front panel, and return to CAT mode when
switching between mode U/V and V/U in Full Duplex, for example:
switching from FO-20 to AO-10 and back. The SAT switch must be in one
of the full duplex positions for this to work. Alternately, you could
take MacDoppler out of CAT mode, use the VFO buttons to switch from
U/V to V/U, and then turn CAT mode back on - this will only work if
you have one VFO set to U/V and the other VFO set to V/U. If you have
other modules installed in the FT- 736R, you can set the
'BetweenPasses' frequencies in the modes editor to something these
other modules can tune and that way allow switching from U to V and V
to U automatically when the satellite changes. It does this to avoid
trying to set VFO A and B to the same band. The FT-847, as originally
delivered (before sn 8G052xxx), could not poll the radio for frequency
and mode information. This was added beginning with the 8G05
production runs."

- https://www.dogparksoftware.com/MacDopplerManual.pdf

73, John Brier KG4AKV

On Sat, Dec 2, 2017 at 2:17 PM, KD4ZGW <kd4zgw@xxxxx.xxx> wrote:
> Can anyone help me get my Yaesu FT-736R to run on SatPC32?  I bought a cable
> that will link the radio to the pc (via USB). But all it does is
> automatically puts the radio in "CAT mode" and doesn't change frequencies,
> when I shut it down, my radio is locked up and have to power cycle to get it
> out of CAT mode. What settings do I need to change in SatPC32?
>
> I have been working on this for months to figure it out, I want to get back
> on birds. I am getting a little frustrated with this radio.
>
> Thanks for any advice
>
> 73 de Rob KD4ZGW
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb


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

Message: 4
Date: Sat, 2 Dec 2017 20:35:52 +0000 (UTC)
From: Kevin M <n4ufo@xxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] 5K0T logged sat times
Message-ID: <2047498206.447320.1512246952817@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

I have checked the 5K0T clublog and see that I have 2 QSOs there (wasn't
sure he got my call on the first pass, was at LOS), but when I go to enter
the times to make a QSL request, it says the times are not correct. So I
e-mailed the QSL manager and he sent me back the log entries from Ham Radio
Deluxe. He shows the times exactly two hours ahead of what I have. So I have
checked my tracking programs and I show no passes at the times his logs
show, rather my times show as correct. Has anyone else that made a QSO with
5K0T tried to enter their times in Clublog to see if they are correct?? If
you were successful, which pass was it? My passes were 2017-11-22 2029 and
2055z.

So I e-mailed him back to tell him I think maybe there is a problem with
either the computer that the log was recorded on or with the HRD program,
etc., and his reply was simply, 'I use UTC times'. I made up some screen
shots of my Orbitron for both his times and my times and sent them to him,
but whether he will get the attachments is yet to be seen. It would just be
good to know (for confidence level) if anyone else encounters the same
problem. (Or am I just royally messed up and not seeing it.)

Thanks in advance, feel free to reply on or off list. 73, Kevin N4UFO


------------------------------------------------------------------"Control
is the need of the fearful mind. Trust is the need of the courageous heart."

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

Message: 5
Date: Sat, 02 Dec 2017 17:15:36 -0500
From: John Papay <john@xxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] VUCC Awards/Endorsements for November 2017
Message-ID: <20171202224601.3CDE9862A@xxxxxxxxxx.xxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"; format=flowed

Here are the endorsements and new VUCC Satellite
Awards issued by the ARRL for the period November 1, 2017
through December 1, 2017.
Congratulations to all those who made the list this month!

CALL	1Nov17	1Dec17

WC7V	1157	1158
N8HM	 980	1000
K4FEG	 818	 841
KG5CCI	 616	 777
N4UFO	 675	 700
N9IP	 542	 574
W5RKN	 511	 554
NJ4Y	 516	 550
W7QL	 252	 275
KA9P	 175	 212
VE7CEW	 127	 200
KE4AL	 100	 175
N4YHC	 100 	 175
G0ABI 	105	 115
HP2VX		 108 (NEW VUCC)
KB2ESY		 101 (NEW VUCC)

PT9BM, who was at 100 grids on November 1, 2017, was not on
the list dated December 1, 2017.
	

This list was developed by comparing the ARRL .pdf
listings for November 1st and December 1st, 2017.  It's a visual
comparison so omissions are possible.  Apologies if your
call was not mentioned.  Thanks to all those who are
roving to grids that are rarely on the birds.  They are
doing most of the work!

73,
John K8YSE


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



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

Message: 6
Date: Sat, 02 Dec 2017 23:17:16 +0000
From: Paul Stoetzer <n8hm@xxxx.xxx>
To: Kevin M <n4ufo@xxxxx.xxx>
Cc: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] 5K0T logged sat times
Message-ID:
<CABzOSOoT6Dtuo4piCAQxcWnAFC4G_DXspLQ6Lcwt1k=w0Sxzcw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"

My 2 QSO (1 from home, 1 from Michigan) times also didn?t match when I
checked ClubLog. I have not followed up yet.

73,

Paul, N8HM

On Sat, Dec 2, 2017 at 18:11 Kevin M via AMSAT-BB <amsat-bb@xxxxx.xxx>
wrote:

> I have checked the 5K0T clublog and see that I have 2 QSOs there (wasn't
> sure he got my call on the first pass, was at LOS), but when I go to enter
> the times to make a QSL request, it says the times are not correct. So I
> e-mailed the QSL manager and he sent me back the log entries from Ham Radio
> Deluxe. He shows the times exactly two hours ahead of what I have. So I
> have checked my tracking programs and I show no passes at the times his
> logs show, rather my times show as correct. Has anyone else that made a QSO
> with 5K0T tried to enter their times in Clublog to see if they are
> correct?? If you were successful, which pass was it? My passes were
> 2017-11-22 2029 and 2055z.
>
> So I e-mailed him back to tell him I think maybe there is a problem with
> either the computer that the log was recorded on or with the HRD program,
> etc., and his reply was simply, 'I use UTC times'. I made up some screen
> shots of my Orbitron for both his times and my times and sent them to him,
> but whether he will get the attachments is yet to be seen. It would just be
> good to know (for confidence level) if anyone else encounters the same
> problem. (Or am I just royally messed up and not seeing it.)
>
> Thanks in advance, feel free to reply on or off list. 73, Kevin N4UFO
>
>
> ------------------------------------------------------------------"Control
> is the need of the fearful mind. Trust is the need of the courageous heart."
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>


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

Message: 7
Date: Sun, 3 Dec 2017 00:51:21 +0000 (UTC)
From: "R.T.Liddy" <k8bl@xxxxxxxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] VUCC Awards/Endorsements for November 2017
Message-ID: <2110268543.459507.1512262281251@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

John,


Thanks for providing this monthly update! I recognize
quite a few A-1 Ops on that list!!

73,    Bob  K8BL
________________________________
From: John Papay <john@xxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Sent: Saturday, December 2, 2017 6:12 PM
Subject: [amsat-bb] VUCC Awards/Endorsements for November 2017

Here are the endorsements and new VUCC Satellite
Awards issued by the ARRL for the period November 1, 2017
through December 1, 2017.
Congratulations to all those who made the list this month!
CALL    1Nov17    1Dec17

WC7V    1157    1158

N8HM     980    1000

K4FEG     818     841

KG5CCI     616     777

N4UFO     675     700

N9IP     542     574

W5RKN     511     554

NJ4Y     516     550

W7QL     252     275

KA9P     175     212

VE7CEW     127     200

KE4AL     100     175

N4YHC     100      175

G0ABI     105     115

HP2VX         108 (NEW VUCC)

KB2ESY         101 (NEW VUCC)

PT9BM, who was at 100 grids on November 1, 2017, was not on
the list dated December 1, 2017.
This list was developed by comparing the ARRL .pdf
listings for November 1st and December 1st, 2017.  It's a visual
comparison so omissions are possible.  Apologies if your
call was not mentioned.  Thanks to all those who are
roving to grids that are rarely on the birds.  They are
doing most of the work!

73,  John K8YSE



---

This email has been checked for viruses by Avast antivirus software.

https://www.avast.com/antivirus


_______________________________________________

Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb


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

Message: 8
Date: Sat, 2 Dec 2017 20:34:59 -0600
From: Rob Dunham <kd4zgw@xxxxx.xxx>
To: John Brier <johnbrier@xxxxx.xxx>
Cc: Amsat BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] Help with Yaesu FT-736r
Message-ID:
<CADTkDvh7-rsjzq8gDHHv4JSba5qn6rKgMXEiMHU5za_q6PyAcQ@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"

I want to say a special thanks to Steve NS3L. I called Steve and we
determined I had the wrong cable from the radio to the pc. I bought a
programming cable instead of a CAT interface cable. He is sending me a
cable to use until I can buy a new one. Thanks to all who has given me
advice on this issue.

73 de Rob KD4ZGW

On Dec 2, 2017 3:11 PM, "John Brier" <johnbrier@xxxxx.xxx> wrote:

> This is a bit of a shot in the dark, but I was reading the Mac Doppler
> manual today trying to figure out something unrelated, and it
> mentioned the FT-736R had a problem related to CAT mode. Here is the
> text from the manual, perhaps it is relevant:
>
> "Due to a problem with the FT-736R (see note in FT-736R manual page 36
> bottom left) you may have to take MacDoppler out of CAT mode, press
> the REV key on the FT-736R front panel, and return to CAT mode when
> switching between mode U/V and V/U in Full Duplex, for example:
> switching from FO-20 to AO-10 and back. The SAT switch must be in one
> of the full duplex positions for this to work. Alternately, you could
> take MacDoppler out of CAT mode, use the VFO buttons to switch from
> U/V to V/U, and then turn CAT mode back on - this will only work if
> you have one VFO set to U/V and the other VFO set to V/U. If you have
> other modules installed in the FT- 736R, you can set the
> 'BetweenPasses' frequencies in the modes editor to something these
> other modules can tune and that way allow switching from U to V and V
> to U automatically when the satellite changes. It does this to avoid
> trying to set VFO A and B to the same band. The FT-847, as originally
> delivered (before sn 8G052xxx), could not poll the radio for frequency
> and mode information. This was added beginning with the 8G05
> production runs."
>
> - https://www.dogparksoftware.com/MacDopplerManual.pdf
>
> 73, John Brier KG4AKV
>
> On Sat, Dec 2, 2017 at 2:17 PM, KD4ZGW <kd4zgw@xxxxx.xxx> wrote:
> > Can anyone help me get my Yaesu FT-736R to run on SatPC32?  I bought a
> cable
> > that will link the radio to the pc (via USB). But all it does is
> > automatically puts the radio in "CAT mode" and doesn't change
> frequencies,
> > when I shut it down, my radio is locked up and have to power cycle to
> get it
> > out of CAT mode. What settings do I need to change in SatPC32?
> >
> > I have been working on this for months to figure it out, I want to get
> back
> > on birds. I am getting a little frustrated with this radio.
> >
> > Thanks for any advice
> >
> > 73 de Rob KD4ZGW
> >
> > _______________________________________________
> > Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>


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

Message: 9
Date: Sat, 2 Dec 2017 21:38:09 -0500
From: John Brier <johnbrier@xxxxx.xxx>
To: Rob Dunham <kd4zgw@xxxxx.xxx>
Cc: Amsat BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] Help with Yaesu FT-736r
Message-ID:
<CALn0fKNp2tvv50F4kt9JR=NQTtiOdEde=qFdB-pjDVHdKf3fgg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"

Glad you got it figured out.

Good job Steve!

73, John Brier KG4AKV


On Dec 2, 2017 21:35, "Rob Dunham" <kd4zgw@xxxxx.xxx> wrote:

I want to say a special thanks to Steve NS3L. I called Steve and we
determined I had the wrong cable from the radio to the pc. I bought a
programming cable instead of a CAT interface cable. He is sending me a
cable to use until I can buy a new one. Thanks to all who has given me
advice on this issue.

73 de Rob KD4ZGW

On Dec 2, 2017 3:11 PM, "John Brier" <johnbrier@xxxxx.xxx> wrote:

> This is a bit of a shot in the dark, but I was reading the Mac Doppler
> manual today trying to figure out something unrelated, and it
> mentioned the FT-736R had a problem related to CAT mode. Here is the
> text from the manual, perhaps it is relevant:
>
> "Due to a problem with the FT-736R (see note in FT-736R manual page 36
> bottom left) you may have to take MacDoppler out of CAT mode, press
> the REV key on the FT-736R front panel, and return to CAT mode when
> switching between mode U/V and V/U in Full Duplex, for example:
> switching from FO-20 to AO-10 and back. The SAT switch must be in one
> of the full duplex positions for this to work. Alternately, you could
> take MacDoppler out of CAT mode, use the VFO buttons to switch from
> U/V to V/U, and then turn CAT mode back on - this will only work if
> you have one VFO set to U/V and the other VFO set to V/U. If you have
> other modules installed in the FT- 736R, you can set the
> 'BetweenPasses' frequencies in the modes editor to something these
> other modules can tune and that way allow switching from U to V and V
> to U automatically when the satellite changes. It does this to avoid
> trying to set VFO A and B to the same band. The FT-847, as originally
> delivered (before sn 8G052xxx), could not poll the radio for frequency
> and mode information. This was added beginning with the 8G05
> production runs."
>
> - https://www.dogparksoftware.com/MacDopplerManual.pdf
>
> 73, John Brier KG4AKV
>
> On Sat, Dec 2, 2017 at 2:17 PM, KD4ZGW <kd4zgw@xxxxx.xxx> wrote:
> > Can anyone help me get my Yaesu FT-736R to run on SatPC32?  I bought a
> cable
> > that will link the radio to the pc (via USB). But all it does is
> > automatically puts the radio in "CAT mode" and doesn't change
> frequencies,
> > when I shut it down, my radio is locked up and have to power cycle to
> get it
> > out of CAT mode. What settings do I need to change in SatPC32?
> >
> > I have been working on this for months to figure it out, I want to get
> back
> > on birds. I am getting a little frustrated with this radio.
> >
> > Thanks for any advice
> >
> > 73 de Rob KD4ZGW
> >
> > _______________________________________________
> > Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>


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

Message: 10
Date: Sat, 2 Dec 2017 20:46:33 -0600
From: "Mac A. Cody" <maccody@xxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] AO-85 in Gpredict
Message-ID: <e11c0eb6-ee9c-4341-cbb2-66487d7b6c8e@xxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed

Greg,

I have found that the URL you provided does not appear to work with
Gpredict.? I have found that the following URL does work:

http://www.amsat.org/amsat/ftp/keps/current/nasabare.txt

I don't know why http works and https doesn't, but that is my
experience with Gpredict.

73,

Mac Cody / AE5PH
On 12/02/2017 11:58 AM, Greg D wrote:
> Hi Mike,
>
> As others have noted, AO-85's keps aren't in the default locations
> GPredict gets its information from.  I have the Linux version, but I
> expect it's similar under Windows, if that's what you're using.
>
> Go to Edit -> Preferences, and select the TLE Update tab.  Under the
> Update from the Internet section there's a list of websites, all from
> celestrak.  Click on Add TLE source, and edit the highlighted section with:
>
>      https://www.amsat.org/amsat/ftp/keps/current/nasabare.txt
>
> Be sure the box "add new satellites to local database" is checked, and
> hit OK.
>
> Then update the update the database with Edit -> Update TLE data -> from
> Network.  You should then be able to find AO-85 in the search list under
> Configure (cleverly hidden under the little triangle in the upper right
> corner).
>
> GPredict is my primary satellite prediction and tracking app.  Enjoy!
>
> Greg  KO6TH
>
>
> radiomb wrote:
>> Hello,   Seeing the posts I downloaded Gpredict  to give it a try. I
could not find AO-85 (FOX-1A) in satellites listed. Even AO-91 is in the
current list. Can it be under some other name? I found a way to add a bird
but looks like a pain to update. Easy way?  And if AO-91 is in the list why
was AO-85 left out?TNX 73 Mike K4MIA
>> _______________________________________________
>> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>



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

Message: 11
Date: Sat, 2 Dec 2017 19:10:52 -0800
From: Greg D <ko6th.greg@xxxxx.xxx>
To: "Mac A. Cody" <maccody@xxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] AO-85 in Gpredict
Message-ID: <012d1faf-7364-a172-4c24-e213fc02febe@xxxxx.xxx>
Content-Type: text/plain; charset=utf-8

Hi Mac,

Hmmpf.  No idea.

Helping another Ham, we found that his version of GPredict needed to
have the server URL on one line (without the nasabare.txt part), and the
file name (nasabare.txt) on a different line.  He has v1.4 on Windows,
I'm on v1.3.something on Linux.

The data isn't all that sensitive, so I wouldn't be too concerned about
the lack of SSL security, but it's still odd...  For what it's worth,
all the pre-configured URLs for Celestrak are http-no-s also.  I think I
just did a copy/paste from the Amsat site when configuring mine.

Enjoy!

Greg  KO6TH


Mac A. Cody wrote:
> Greg,
>
> I have found that the URL you provided does not appear to work with
> Gpredict.  I have found that the following URL does work:
>
> http://www.amsat.org/amsat/ftp/keps/current/nasabare.txt
>
> I don't know why http works and https doesn't, but that is my
> experience with Gpredict.
>
> 73,
>
> Mac Cody / AE5PH
> On 12/02/2017 11:58 AM, Greg D wrote:
>> Hi Mike,
>>
>> As others have noted, AO-85's keps aren't in the default locations
>> GPredict gets its information from.  I have the Linux version, but I
>> expect it's similar under Windows, if that's what you're using.
>>
>> Go to Edit -> Preferences, and select the TLE Update tab.  Under the
>> Update from the Internet section there's a list of websites, all from
>> celestrak.  Click on Add TLE source, and edit the highlighted section
>> with:
>>
>>      https://www.amsat.org/amsat/ftp/keps/current/nasabare.txt
>>
>> Be sure the box "add new satellites to local database" is checked, and
>> hit OK.
>>
>> Then update the update the database with Edit -> Update TLE data -> from
>> Network.  You should then be able to find AO-85 in the search list under
>> Configure (cleverly hidden under the little triangle in the upper right
>> corner).
>>
>> GPredict is my primary satellite prediction and tracking app.  Enjoy!
>>
>> Greg  KO6TH
>>
>>
>> radiomb wrote:
>>> Hello,   Seeing the posts I downloaded Gpredict  to give it a try. I
>>> could not find AO-85 (FOX-1A) in satellites listed. Even AO-91 is in
>>> the current list. Can it be under some other name? I found a way to
>>> add a bird but looks like a pain to update. Easy way?  And if AO-91
>>> is in the list why was AO-85 left out?TNX 73 Mike K4MIA
>>> _______________________________________________
>>> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>> _______________________________________________
>> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>>
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb



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

Subject: Digest Footer

_______________________________________________
Sent via amsat-bb@xxxxx.xxx.
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!
http://www.amsat.org/mailman/listinfo/amsat-bb

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

End of AMSAT-BB Digest, Vol 12, Issue 318
*****************************************


Read previous mail | Read next mail


 12.05.2024 04:59:35lGo back Go up