gpredict-discussion — Gpredict discussion

Re: [Gpredict-discussion] AO-91 TLEs

[Charles P. <ch...@sp...>]

Dan -

It sounds like the software is NOT your issue, but you are having trouble finding Fox-1B. It is in the Celestrak list, under Amateur.txt so if you got that it should be in your files. Check Preferences, TLE Update, and make sure that you are getting amateur.txt along with the rest of them. 

Did you look for FOX-1B (AO-91) ?? I see it in Gpredict, satellite 43017.

Charles Phillips
Spaceflight Research, LLC
Houston, Texas
713-882-4578
sites.google.com/site/spaceflightresearchprojects/


> On June 30, 2018 at 11:27 AM "Daniel R. Marlow" <ma...@Pr...> wrote:
> 
> 
> Hello,
> 
>    I am having troubles with something that is quite basic.   In particular, I am trying display AO-91.   I see that the OSCAR TLEs are listed in the Celestrak DB, and they are also listed on the AMSAT website.    I tried an “Edit->Update TLE->From Network,” which I assume gets the Celestrak TLEs.     I also did an Edit->Update TLE->From local files and pointed at a directory containing the file nasabare.txt.   Neither command resulted in AO-91 (Fox-1B) appearing in the list that appears when I try to update the preferences for the module that I am using.  As noted, I must be missing something basic.   Help would be appreciated.
> 
> Sincerely,
> Dan Marlow K2QM

Re: [Gpredict-discussion] AO-91 TLEs

[Alexandru C. <oz...@gm...>]

Hi Dan

A default installation of the latest version (2.2.1) should include AO-91.

Alex


On Sat, Jun 30, 2018 at 7:27 PM, Daniel R. Marlow <ma...@pr...> wrote:
> Hello,
>
>    I am having troubles with something that is quite basic.   In particular, I am trying display AO-91.   I see that the OSCAR TLEs are listed in the Celestrak DB, and they are also listed on the AMSAT website.    I tried an “Edit->Update TLE->From Network,” which I assume gets the Celestrak TLEs.     I also did an Edit->Update TLE->From local files and pointed at a directory containing the file nasabare.txt.   Neither command resulted in AO-91 (Fox-1B) appearing in the list that appears when I try to update the preferences for the module that I am using.  As noted, I must be missing something basic.   Help would be appreciated.
>
> Sincerely,
> Dan Marlow K2QM
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Gpredict-discussion mailing list
> Gpr...@li...
> https://lists.sourceforge.net/lists/listinfo/gpredict-discussion

[Gpredict-discussion] AO-91 TLEs

[Daniel R. M. <ma...@Pr...>]

Hello,

   I am having troubles with something that is quite basic.   In particular, I am trying display AO-91.   I see that the OSCAR TLEs are listed in the Celestrak DB, and they are also listed on the AMSAT website.    I tried an “Edit->Update TLE->From Network,” which I assume gets the Celestrak TLEs.     I also did an Edit->Update TLE->From local files and pointed at a directory containing the file nasabare.txt.   Neither command resulted in AO-91 (Fox-1B) appearing in the list that appears when I try to update the preferences for the module that I am using.  As noted, I must be missing something basic.   Help would be appreciated.

Sincerely,
Dan Marlow K2QM

Re: [Gpredict-discussion] Gpredict-discussion Digest, Vol 74, Issue 4

[Fred H. <fmh...@co...>]

If you tried it yesterday, it didn't work due to a problem with the database
(fix in my AM). Now, if you do a Update transponders it will pull good data
and you will see it.

Best regards,
Fred N7FMH


-----Original Message-----
From: Dexter N Muir [mailto:de...@xt...] 
Sent: Wednesday, June 27, 2018 3:56 PM
To: gpr...@li...
Subject: Re: [Gpredict-discussion] Gpredict-discussion Digest, Vol 74, Issue
4

Afterthought to my previous: maybe rather than a module a query of 
satnogs. Right-click on the satellite, the menu includes Satellite Info, 
with a tab "Transponders". It's already there, but blank. Why does 
opening the Satellite Info menu (or that tab) not query satnogs to fill 
that tab in?

Hopefully helpfully ...
Dex, ZL2DEX

----------------------------------------------------------------------------
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Gpredict-discussion mailing list
Gpr...@li...
https://lists.sourceforge.net/lists/listinfo/gpredict-discussion


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

Re: [Gpredict-discussion] Gpredict-discussion Digest, Vol 74, Issue 4

[Dexter N M. <de...@xt...>]

Afterthought to my previous: maybe rather than a module a query of 
satnogs. Right-click on the satellite, the menu includes Satellite Info, 
with a tab "Transponders". It's already there, but blank. Why does 
opening the Satellite Info menu (or that tab) not query satnogs to fill 
that tab in?

Hopefully helpfully ...
Dex, ZL2DEX

Re: [Gpredict-discussion] Gpredict-discussion Digest, Vol 74, Issue 3

[Dexter N M. <de...@xt...>]

On 27/06/18 00:07, gpr...@li... wrote:
> Date: Mon, 25 Jun 2018 21:29:26 -0400
> From: "Fred Hillhouse"<fmh...@co...>
> To:<gpr...@li...>
> Subject: [Gpredict-discussion] gpredict for windows
> Message-ID:<066901d40ced$1fb9f4d0$5f2dde70$@comcast.net>
> Content-Type: text/plain;	charset="us-ascii"
>
> Greetings,
>
>   
>
> I just downloaded gpredict for Windows again today and have a couple of
> questions.
>
> 1.       If I click on satellite info, it says there are no transponders. I
> have clicked on update transponders and it looks like something is happening
> but again, there are no transponders. How do I get frequencies assigned to
> satellites?
>
> 2.       I set up radio control. It I click on engage, the frequency updates
> for 2-3 seconds then turns off. Is this because I don't have hamlib running?
> I started rigctld and that seemed to fix it.
>
> 3.       What do you all do when starting hamlib / gpredict? Create a batch
> file and start hamlib then gpredict?
>
>   
>
> Thanks for this cool looking application! I have been using Orbitron for a
> long time and this appears to have improved better features.
>
>   
>
> Best regards,
>
> Fred N7FMH
That's funny, Fred. (more funny-peculiar than funny-haha). I run 
Orbitron under Wine, it works better for me - just for (ISS) prediction. 
It shows Sun, Moon, Greyline - and the map can be re-centred - just grab 
and pan. I put 30deg East at the edges, NZ to the middle.
I don't have RF - situational restriction - so can't comment that way - 
but re-organising the modules in gpredict I found the same lack and 
oddity: update transponder info, but no display module :(

73 de ZL2DEX

Re: [Gpredict-discussion] gpredict for windows

[Alexandru C. <oz...@gm...>]

On Tue, Jun 26, 2018 at 3:29 AM, Fred Hillhouse <fmh...@co...> wrote:
> Greetings,
>
> I just downloaded gpredict for Windows again today and have a couple of
> questions.
>
> 1.       If I click on satellite info, it says there are no transponders. I
> have clicked on update transponders and it looks like something is happening
> but again, there are no transponders. How do I get frequencies assigned to
> satellites?

The information comes from the StNOGS database, see https://db.satnogs.org/
Not all satellites are in the database, and not all satellites in the
database have transmitter info.
You can suggest an update to the database or create local files. Note
that the local files will be overwritten when there will be
information in the database.

As for the other questions, I hope somebody else who already uses
windows can help.

Alex

Re: [Gpredict-discussion] gpredict for windows

[Sims, W. H. (MSFC-EV41) <her...@na...>]

    2.       I set up radio control. It I click on engage, the frequency updates
    for 2-3 seconds then turns off. Is this because I don't have hamlib running?
    I started rigctld and that seemed to fix it.
Yes
    
    3.       What do you all do when starting hamlib / gpredict? Create a batch
    file and start hamlib then gpredict?
I do, and with a Mac you have to take it one step further and kill the background processes for the rigctld and rotctld.    
     
    

[Gpredict-discussion] gpredict for windows

[Fred H. <fmh...@co...>]

Greetings,

 

I just downloaded gpredict for Windows again today and have a couple of
questions.

1.       If I click on satellite info, it says there are no transponders. I
have clicked on update transponders and it looks like something is happening
but again, there are no transponders. How do I get frequencies assigned to
satellites?

2.       I set up radio control. It I click on engage, the frequency updates
for 2-3 seconds then turns off. Is this because I don't have hamlib running?
I started rigctld and that seemed to fix it.

3.       What do you all do when starting hamlib / gpredict? Create a batch
file and start hamlib then gpredict?

 

Thanks for this cool looking application! I have been using Orbitron for a
long time and this appears to have improved better features.

 

Best regards,

Fred N7FMH

 



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

Re: [Gpredict-discussion] Strange Behavior for RS 4D WTF ?

[Jim <k6...@co...>]

Sorry Fellows this post went to the wrong addressee. 

Jim, K6BPT 

----- Original Message -----

From: "Jim" <k6...@co...> 
To: "GPredict" <gpr...@li...> 
Sent: Wednesday, June 6, 2018 6:10:10 PM 
Subject: [Gpredict-discussion] Strange Behavior for RS 4D WTF ? 

- Jerry - 

Hmmmm for some strange reason, my Shake went titsup, don't know for how long but when I went to check the SD card usage 
it wouldn't respond when I used the Local IP address. I went out to the battery/generator shed to check on it and everything it 
"looked" OK so I pulled the power cord and re-plugged it in and everything is now working. Since this dude is running off of my 
2 KW pure-sine inverter with enough battery capacity to run it for many, many moons.... I'm stumped. I looked to the "Stations" 
map and the device still showed but NO traces were shown running. 

Have you ever had that happen before ? Maybe it was dumping old data but there isn't any way I can confirm that..... 

Jim, K6BPT 
------------------------------------------------------------------------------ 
Check out the vibrant tech community on one of the world's most 
engaging tech sites, Slashdot.org! http://sdm.link/slashdot 
_______________________________________________ 
Gpredict-discussion mailing list 
Gpr...@li... 
https://lists.sourceforge.net/lists/listinfo/gpredict-discussion 

[Gpredict-discussion] Strange Behavior for RS 4D WTF ?

[Jim <k6...@co...>]

- Jerry - 

Hmmmm for some strange reason, my Shake went titsup, don't know for how long but when I went to check the SD card usage 
it wouldn't respond when I used the Local IP address. I went out to the battery/generator shed to check on it and everything it 
"looked" OK so I pulled the power cord and re-plugged it in and everything is now working. Since this dude is running off of my 
2 KW pure-sine inverter with enough battery capacity to run it for many, many moons.... I'm stumped. I looked to the "Stations" 
map and the device still showed but NO traces were shown running. 

Have you ever had that happen before ? Maybe it was dumping old data but there isn't any way I can confirm that..... 

Jim, K6BPT 

Re: [Gpredict-discussion] Gpredict-discussion Digest, Vol 73, Issue 6

[Dexter N M. <de...@xt...>]

On 01/06/18 00:11, Alexandru Csete <oz...@gm...> wrote:
> Date: Wed, 30 May 2018 22:28:24 +0200
> From: Alexandru Csete <oz...@gm...>
> To: Gpredict discussion <gpr...@li...>
> Subject: Re: [Gpredict-discussion] Pi 3 update?
> Message-ID:
> 	<CAHG=S_c...@ma...>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi Dex,
>
> I just found out that you can install the binary package from the
> Ubuntu PPA manually. I have written down the steps here:
> https://community.libre.space/t/installing-gpredict-binary-on-the-raspberry-pi-3/2145
>
> I will try to set up a Debian repository later, but I don't have time right now.
>
> Alex
>
Thanks Alex!

Binary installed with only one hiccup: libgoocanvas 2 not installed. 3 
was, but 2 installed fine beside it, and all plain sailing from there.
If you have hamradiomenus installed, gpredict will appear there too! I 
already had that for Xastir (manually installed).
I'll try your steps as above later.

73,
Dex ZL2DEX

Re: [Gpredict-discussion] Pi 3 update?

[Alexandru C. <oz...@gm...>]

Hi Dex,

I just found out that you can install the binary package from the
Ubuntu PPA manually. I have written down the steps here:
https://community.libre.space/t/installing-gpredict-binary-on-the-raspberry-pi-3/2145

I will try to set up a Debian repository later, but I don't have time right now.

Alex




On Tue, May 29, 2018 at 11:36 PM, Dexter N Muir <de...@xt...> wrote:
>    I have gpredict installed on my Raspberry Pi, and have enjoyed it for
> quite a while. I recently had to re-do from start, which meant reinstall
> gpredict. I ran into an annoying cosmetic hitch that has plagued me from the
> first: the Preferences dialog does not re-size to be accommodated in screen
> size(s) of 720p (and below?). I have to reset to 1080p to gain access to the
> full dialog and its 'save and exit' button. I have 20" monitors, and 720p
> works best there: text is crisp and easily read. Re-sizing to 1080p can
> work, but is likely to require slower (24Hz) refresh and text is fuzzy and
> small - readable with difficulty - with a small and elusive cursor. I revert
> to 720p.
>       A further issue which may be worth pursuing: default Module Layout.
> With modern 9:16 aspect ratio, I find this layout better:
> 1;0;3;0;4;2;3;4;0;2;3;3;4;2;4.
>    I tried to emulate your view by adding ;4;0;3;3;4 but couldn't get to the
> right side far enough to grab the column edge to re-size "AOS/LOS" parked
> there. En/Disabling columns didn't seem to have any effect.
>    And each change in Preferences requires an Exit and re-start to view: is
> no auto-refresh possible?
>
>    The above is in the repository's version 1.3 - quite dated. I've just
> tried installing 2.2.1 from source - what a marathon! First try was by
> install.sh: dependency errors cropped up. The first was easy to cancel: the
> item was in the repository though not installed by default. Then stumped for
> two more, not there! ./configure brick-walled with libglib-dev missing, and
> again not in repository.
>
> A Raspberry Pi 3 to try it on shouldn't be too expensive, and they're
> getting mighty popular (I run mine 24/7 pretty much for APRS). Meanwhile
> fuhgeddit!
>
> Dex ZL2DEX
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Gpredict-discussion mailing list
> Gpr...@li...
> https://lists.sourceforge.net/lists/listinfo/gpredict-discussion

Re: [Gpredict-discussion] Pi 3 update?

[Lisa R. N. <lis...@gm...>]

I'm running Ubuntu 18.04, and just built gpredict from source, the 
version I have is 2.3.12

Lisa

On 5/29/18 3:36 PM, Dexter N Muir wrote:
>    I have gpredict installed on my Raspberry Pi, and have enjoyed it for
> quite a while. I recently had to re-do from start, which meant reinstall
> gpredict. I ran into an annoying cosmetic hitch that has plagued me 
> from the
> first: the Preferences dialog does not re-size to be accommodated in 
> screen
> size(s) of 720p (and below?). I have to reset to 1080p to gain access 
> to the
> full dialog and its 'save and exit' button. I have 20" monitors, and 720p
> works best there: text is crisp and easily read. Re-sizing to 1080p can
> work, but is likely to require slower (24Hz) refresh and text is fuzzy 
> and
> small - readable with difficulty - with a small and elusive cursor. I 
> revert
> to 720p.
>       A further issue which may be worth pursuing: default Module Layout.
> With modern 9:16 aspect ratio, I find this layout better:
> 1;0;3;0;4;2;3;4;0;2;3;3;4;2;4.
>    I tried to emulate your view by adding ;4;0;3;3;4 but couldn't get 
> to the
> right side far enough to grab the column edge to re-size "AOS/LOS" parked
> there. En/Disabling columns didn't seem to have any effect.
>    And each change in Preferences requires an Exit and re-start to 
> view: is
> no auto-refresh possible?
>
>    The above is in the repository's version 1.3 - quite dated. I've just
> tried installing 2.2.1 from source - what a marathon! First try was by
> install.sh: dependency errors cropped up. The first was easy to 
> cancel: the
> item was in the repository though not installed by default. Then 
> stumped for
> two more, not there! ./configure brick-walled with libglib-dev 
> missing, and
> again not in repository.
>
> A Raspberry Pi 3 to try it on shouldn't be too expensive, and they're
> getting mighty popular (I run mine 24/7 pretty much for APRS). Meanwhile
> fuhgeddit!
>
> Dex ZL2DEX
>
>
> ------------------------------------------------------------------------------ 
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Gpredict-discussion mailing list
> Gpr...@li...
> https://lists.sourceforge.net/lists/listinfo/gpredict-discussion

[Gpredict-discussion] Pi 3 update?

[Dexter N M. <de...@xt...>]

    I have gpredict installed on my Raspberry Pi, and have enjoyed it for
quite a while. I recently had to re-do from start, which meant reinstall
gpredict. I ran into an annoying cosmetic hitch that has plagued me from the
first: the Preferences dialog does not re-size to be accommodated in screen
size(s) of 720p (and below?). I have to reset to 1080p to gain access to the
full dialog and its 'save and exit' button. I have 20" monitors, and 720p
works best there: text is crisp and easily read. Re-sizing to 1080p can
work, but is likely to require slower (24Hz) refresh and text is fuzzy and
small - readable with difficulty - with a small and elusive cursor. I revert
to 720p.
       A further issue which may be worth pursuing: default Module Layout.
With modern 9:16 aspect ratio, I find this layout better:
1;0;3;0;4;2;3;4;0;2;3;3;4;2;4.
    I tried to emulate your view by adding ;4;0;3;3;4 but couldn't get to the
right side far enough to grab the column edge to re-size "AOS/LOS" parked
there. En/Disabling columns didn't seem to have any effect.
    And each change in Preferences requires an Exit and re-start to view: is
no auto-refresh possible?

    The above is in the repository's version 1.3 - quite dated. I've just
tried installing 2.2.1 from source - what a marathon! First try was by
install.sh: dependency errors cropped up. The first was easy to cancel: the
item was in the repository though not installed by default. Then stumped for
two more, not there! ./configure brick-walled with libglib-dev missing, and
again not in repository.

A Raspberry Pi 3 to try it on shouldn't be too expensive, and they're
getting mighty popular (I run mine 24/7 pretty much for APRS). Meanwhile
fuhgeddit!

Dex ZL2DEX

Re: [Gpredict-discussion] Satellite priority

[lisa50469 <lis...@gm...>]

Thanks, today I was on a satellite that was working well, but manually switched too my priority satellite after it got over 4 degrees.   I guess the 4 degrees would be some setting in the code, not on a per - satellite setting. 
73
Sent from my Galaxy Tab® S2
-------- Original message --------From: Jaime Robles <ja...@ro...> Date: 5/29/18  1:27 PM  (GMT-07:00) To: Gpredict discussion <gpr...@li...> Subject: Re: [Gpredict-discussion] Satellite priority 
+1
Great idea the priority!

El mar., 29 may. 2018 21:21, Lisa R. Nelson <lis...@gm...> escribió:

> Gpredict needs to have a satellite priority file where you can list the
> priority satellites in order for those times two are in range at the
> same time.
>
> SUPER Feature would be to also make those decisions given an Elevation
> number such as 4 degrees.  That way you can specify at what elevation
> the priority satellite should be switched to.  Or switching FROM.
>
> Lisa
>
> AK7WS
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Gpredict-discussion mailing list
> Gpr...@li...
> https://lists.sourceforge.net/lists/listinfo/gpredict-discussion
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Gpredict-discussion mailing list
Gpr...@li...
https://lists.sourceforge.net/lists/listinfo/gpredict-discussion

Re: [Gpredict-discussion] Satellite priority

[Jaime R. <ja...@ro...>]

+1
Great idea the priority!

El mar., 29 may. 2018 21:21, Lisa R. Nelson <lis...@gm...> escribió:

> Gpredict needs to have a satellite priority file where you can list the
> priority satellites in order for those times two are in range at the
> same time.
>
> SUPER Feature would be to also make those decisions given an Elevation
> number such as 4 degrees.  That way you can specify at what elevation
> the priority satellite should be switched to.  Or switching FROM.
>
> Lisa
>
> AK7WS
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Gpredict-discussion mailing list
> Gpr...@li...
> https://lists.sourceforge.net/lists/listinfo/gpredict-discussion
>

[Gpredict-discussion] Satellite priority

[Lisa R. N. <lis...@gm...>]

Gpredict needs to have a satellite priority file where you can list the 
priority satellites in order for those times two are in range at the 
same time.

SUPER Feature would be to also make those decisions given an Elevation 
number such as 4 degrees.  That way you can specify at what elevation 
the priority satellite should be switched to.  Or switching FROM.

Lisa

AK7WS

Re: [Gpredict-discussion] Autotrack bug

[Alexandru C. <oz...@gm...>]

On Mon, May 28, 2018 at 3:41 PM, Lisa R. Nelson <lis...@gm...> wrote:
>
> Also, on that note, I hate that I have to always change the tolerance from
> 5.00 to 0.50 all the time, please either have Gpredict retain the setting,
> or put it in the configuration.

I have added it to the todo list but I am very busy at the moment and
it will take several months before I can work on the next release. In
the meanwhile, I am curious wheather you really need that low motion
threshold. A typical UHF yagi has 3 dB beamwidth of ~30 degrees...

Alex

[Gpredict-discussion] Autotrack bug

[Lisa R. N. <lis...@gm...>]

Today I was tracking AO-85, and had autotrack on.

After AOS, I was looking at the AZ/EL, and noticed the tolerance was at 
5.00.  I use 0.50, so I changed it, but at some point, the system 
changed tracking to the next satellite that would be up.  I clicked 
AO-85 again and even turned off autotrack, but had to exit Gpredict and 
restart it to track AO-85 while it was between AOS and LOS.

Also, on that note, I hate that I have to always change the tolerance 
from 5.00 to 0.50 all the time, please either have Gpredict retain the 
setting, or put it in the configuration.

I'll work on finding more about this tracking bug.  It's done it to me 
before, but I'll find the sequence of events that cause it.

Lisa AK7WS

Re: [Gpredict-discussion] Custom Devices Support

[chuck <chu...@gm...>]

I agree it would be nice to have the sat name passed. But all the other
info is passed. Maybe you know that already.

Also you say passing about 1 per second. This is already in the program,
you can adjust the freq. of updates.

chuck

On Sat, May 26, 2018 at 5:09 PM Lisa R. Nelson <lis...@gm...> wrote:

> Gpredict is a great program, but those of us who build custom hardware
> and devices would like to see some support that is easy to access.
>
> I've built a antenna rotator, and also wrote a program to control my
> kenwood radio (because it's not supported by hamlib)
> If you could add a feature to Gpredict that would be on the 'Interface'
> settings screen for a simple generic output, that would be great. Then
> anyone interested in writing code or building projects related to
> Gpredict could very easily.
> Here's what I personally would like to see:
>
> Whenever anything changes such as the radio frequencies because of
> doppler or a new satellite (autotrack) or the azumith/elevation, you
> would send the following to a port like you do for rotators or radios.
> Once per second is often enough.
>
> Sat Name, Uplink freq including doppler, Downlink freq including
> doppler, Azumith, Elevation
>
> AO-85,435.176817,145.981086,280.43,12.5
>
> With that info, both the radio control program and the antenna control
> program can take care of everything. Blindly sending this info to a
> specified port would be simple and allow anyone to customize interfaces.
>
> I've got two custom programs running right now to do this using your
> data that was meant for rigctl and rotctl. But the satellite name is not
> included in any of the data sent from Gpredict. Therefore the PL tones
> etc., that are specific to each satellite can't be programmed from the
> data from Gpredict.
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Gpredict-discussion mailing list
> Gpr...@li...
> https://lists.sourceforge.net/lists/listinfo/gpredict-discussion
>

[Gpredict-discussion] Custom Devices Support

[Lisa R. N. <lis...@gm...>]

Gpredict is a great program, but those of us who build custom hardware 
and devices would like to see some support that is easy to access.

I've built a antenna rotator, and also wrote a program to control my 
kenwood radio (because it's not supported by hamlib)
If you could add a feature to Gpredict that would be on the 'Interface' 
settings screen for a simple generic output, that would be great. Then 
anyone interested in writing code or building projects related to 
Gpredict could very easily.
Here's what I personally would like to see:

Whenever anything changes such as the radio frequencies because of 
doppler or a new satellite (autotrack) or the azumith/elevation, you 
would send the following to a port like you do for rotators or radios. 
Once per second is often enough.

Sat Name, Uplink freq including doppler, Downlink freq including 
doppler, Azumith, Elevation

AO-85,435.176817,145.981086,280.43,12.5

With that info, both the radio control program and the antenna control 
program can take care of everything. Blindly sending this info to a 
specified port would be simple and allow anyone to customize interfaces.

I've got two custom programs running right now to do this using your 
data that was meant for rigctl and rotctl. But the satellite name is not 
included in any of the data sent from Gpredict. Therefore the PL tones 
etc., that are specific to each satellite can't be programmed from the 
data from Gpredict.

Re: [Gpredict-discussion] GPredict and SatNOGS rotor

[Sims, W. H. (MSFC-ES63) <her...@na...>]

    
    - What is the total amount of azimuth rotation in the SATNOGS rotator?
    Traditionally az rotors were either 360 or 450 degrees.
In theory it is infinite as it uses a worm gear and has no mechanical stop.  It does however, have an endstop SWITCH.  I am not sure what the rotor controller would do if you send it an azimuth value greater than 360 degrees...that is something that I'll have to check into...

    - Does the azimuth rotor have rotation stops? If so, where are they
    positioned?  North (0 deg) and South (+/- 180 deg) are the most common, but
    really anything would work.
There is a endstop switch, but nothing that mechanically stops it from rotating farther

    - Does the rotator expect to be fed only positive azimuth values (eg
    0->360), or positive and negative values (eg. -180->0->180)?  Or does it
    work well with either one?
I am not sure, I tried the -180-0-180 yesterday and it didn't seem to work.  I do know that I can send it commands via a UART terminal program and it will accept negative values.
    
    Basically, I suspect you've got a problem with the defined azimuth stops in
    gpredict.  For example, if your rotator has stops in the South, but
    gpredict thinks they're in the North, or visa-versa.  If they don't agree,
    then you have the swing-around problem, even when you wouldn't think it
    would.
That is what I was thinking.  The endstop switch is set to 0 degrees (when the switch is enabled it zeros out both the azimuth and elevation values and goes from there) - so that would imply - I believe - it is a 0-180-360 degree rotor and not the -180 - 0 - 180
    
    
    (LONG-WINDED EXPLANATION ALERT)
    
    Let me explain in more detail.
    
    For example, if your *actual* stops are in the North (0 deg), but gpredict
    *thinks* they're in the South (+/- 180 deg), then you have these two
    scenarios:
    - When a pass crosses the North azimuth, gpredict assumes that it can just
    go directly, and doesn't do anything weird. But, for example, when the
    rotator is currently just west of north, and gpredict feeds it an azimuth
    that's just east of north (assuming that it's only a few degrees to
    change), the rotator will end up swinging all the way around to get there
    from the other side.
    - When a pass crosses the South azimuth, gpredict thinks it needs to do
    avoid the rotation stops in the south, and so it does a flipped pass.  This
    means that instead of tracking across the South azimuth, at some elevation
    E, gpredict flips the antenna over and tracks across the North azimuth, at
    an elevation of (180 degrees - E).  And so again, when gpredict feeds your
    rotator something that crosses the North azimuth, it has to swing all the
    way around again.
    
    If you choose a 0->180->360 rotator in gpredict, it will assume the
    rotation stops are in the North (0/360 deg), though that can be changed.
    Similarly, if you choose a -180->0->180 rotator in gpredict, it will assume
    the rotation stops are in the South (+/- 180 deg), but again, that can be
    adjusted.
    
    So, in the end, the simple answer is to make sure that gpredict correctly
    knows where your azimuth rotation stops are, and it will work much better.

That was my thinking as well - I _believe_ that I need to have 0-180-360 since my endstop is at 0 degrees when it "homes" on power up.
    
    Lloyd
    
    
    
    On Fri, May 11, 2018 at 8:28 AM, Sims, William Herb (MSFC-ES63) <
    her...@na...> wrote:
    
    > Guys and Gals,
    >
    > Two questions for the group.
    >
    > First, is there a way within GPredict to determine if TWO ground stations
    > can see the same satellite at the same time?  Along a work related question
    > we (Marshall Space Flight Center, MSFC) are doing some experiments on the
    > International Space Station (ISS) RF test-bed and due to licensing issues
    > on the station we cannot downlink data while NOT over pre-determined ground
    > stations (in our we are NOT one of those ground stations but Glenn Research
    > Center, GRC, is).  What we want to do is determine when both MSFC and GRC
    > can see ISS at the same time.  Is it possible with GPRedict?  I realize we
    > can use something Like Satellite Tool Kit but that requires funding other
    > NASA people so I am trying to save our project some money (since I’m
    > already on it).
    >
    > Second, I am using a SatNOGS rotor (AZ/EL) and was simulating tracking a
    > satellite yesterday and noticed something that concerns me.  The satellite
    > started on the horizon at say 10 degrees azimuth and during the pass went
    > from 10 – 360 – 350 – 340 to finally close to 190 degrees.  The question I
    > have is that once the projected azimuth hit 360 the SatnOGS rotor spun all
    > the way around (went clockwise from 0.1 degrees to 180 to 359 degrees)
    > instead of continuing in a counter-clockwise direction (this is, I believe,
    > because I had the rotor controller set to 0-180-360).  I believe had I set
    > the controller to -180-0-180 that it would have worked as expected.  The
    > problem is, if I get a scenario of another satellite track that goes from
    > 170 – 180 - -170 - -160, etc. and I was set up for the -180-0-180 it would
    > do the same thing (i.e. go 170, 179.9 then swing all the way around
    > counter-clockwise to -179 etc.).  Is that something that one “just has to
    > live with” or should the rotor be capable of doing a full 720 degrees (2 *
    > 360) too keep this from happening?  I realize that it would then wrap the
    > coax around the system, but I just want to make sure that I am not missing
    > something here.
    >
    > Thanks,
    >
    > Herb
    >
    >
    > Dr. Herb Sims
    > EV41
    > Bldg. 4600 / Room 4113
    > Control Systems Design & Analysis Branch
    > MSFC, AL 35812
    > 256-961-3214
    > ------------------------------------------------------------
    > ------------------------------------------------------------
    > -------------------
    > I want to tell the whole world that I love my wife and kids - what better
    > way than one email at a time
    >
    > Ich will der ganzen Welt sagen, dass ich meine Frau und Kinder liebe – wie
    > ist das besser zu machen als Mail für Mail,
    > eine nach der anderen.
    > ------------------------------------------------------------
    > ------------------------------------------------------------
    > -------------------
    >
    >
    >
    > ------------------------------------------------------------
    > ------------------
    > Check out the vibrant tech community on one of the world's most
    > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    > _______________________________________________
    > Gpredict-discussion mailing list
    > Gpr...@li...
    > https://lists.sourceforge.net/lists/listinfo/gpredict-discussion
    >
    ------------------------------------------------------------------------------
    Check out the vibrant tech community on one of the world's most
    engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    _______________________________________________
    Gpredict-discussion mailing list
    Gpr...@li...
    https://lists.sourceforge.net/lists/listinfo/gpredict-discussion
    

Re: [Gpredict-discussion] GPredict and SatNOGS rotor

[Sims, W. H. (MSFC-ES63) <her...@na...>]

Thomas,

I will look into this software that you recommend.  If I do run into problems and have questions I'll take you up on your offer.  But like they say, be careful of what you wish for. LOL

Thanks!

Herb

 
Dr. Herb Sims
EV41
Bldg. 4600 / Room 4113
Control Systems Design & Analysis Branch
MSFC, AL 35812
256-961-3214
-------------------------------------------------------------------------------------------------------------------------------------------
I want to tell the whole world that I love my wife and kids - what better way than one email at a time
 
Ich will der ganzen Welt sagen, dass ich meine Frau und Kinder liebe – wie ist das besser zu machen als Mail für Mail, 
eine nach der anderen.
-------------------------------------------------------------------------------------------------------------------------------------------
 
 
 
On 5/11/18, 9:50 AM, "Thomas J Murphy" <tjm...@mi...> wrote:

    Hi Herb,
    
    I'm not super well-versed in GPredict, but I know for certain that PyEphem is able to do what you ask.
    
    PyEphem is a free package which you can install for use in Python (which is also free!). It allows you to do all sorts of celestial calculations. You can use the next_pass() function to find when an orbiting body will be visible from a given ground station. It should be pretty simple to write up a script to find when the body is visible to both ground stations.
    
    If you like this option, but are not confident in your ability to code it up, I would be willing to do the coding for you. Let me know!
    
    Thomas Murphy
    ________________________________________
    From: Sims, William Herb (MSFC-ES63) [her...@na...]
    Sent: Friday, May 11, 2018 10:28 AM
    To: gpr...@li...
    Subject: [Gpredict-discussion] GPredict and SatNOGS rotor
    
    Guys and Gals,
    
    Two questions for the group.
    
    First, is there a way within GPredict to determine if TWO ground stations can see the same satellite at the same time?  Along a work related question we (Marshall Space Flight Center, MSFC) are doing some experiments on the International Space Station (ISS) RF test-bed and due to licensing issues on the station we cannot downlink data while NOT over pre-determined ground stations (in our we are NOT one of those ground stations but Glenn Research Center, GRC, is).  What we want to do is determine when both MSFC and GRC can see ISS at the same time.  Is it possible with GPRedict?  I realize we can use something Like Satellite Tool Kit but that requires funding other NASA people so I am trying to save our project some money (since I’m already on it).
    
    Second, I am using a SatNOGS rotor (AZ/EL) and was simulating tracking a satellite yesterday and noticed something that concerns me.  The satellite started on the horizon at say 10 degrees azimuth and during the pass went from 10 – 360 – 350 – 340 to finally close to 190 degrees.  The question I have is that once the projected azimuth hit 360 the SatnOGS rotor spun all the way around (went clockwise from 0.1 degrees to 180 to 359 degrees) instead of continuing in a counter-clockwise direction (this is, I believe, because I had the rotor controller set to 0-180-360).  I believe had I set the controller to -180-0-180 that it would have worked as expected.  The problem is, if I get a scenario of another satellite track that goes from 170 – 180 - -170 - -160, etc. and I was set up for the -180-0-180 it would do the same thing (i.e. go 170, 179.9 then swing all the way around counter-clockwise to -179 etc.).  Is that something that one “just has to live with” or should the rotor be capable of doing a full 720 degrees (2 * 360) too keep this from happening?  I realize that it would then wrap the coax around the system, but I just want to make sure that I am not missing something here.
    
    Thanks,
    
    Herb
    
    
    Dr. Herb Sims
    EV41
    Bldg. 4600 / Room 4113
    Control Systems Design & Analysis Branch
    MSFC, AL 35812
    256-961-3214
    -------------------------------------------------------------------------------------------------------------------------------------------
    I want to tell the whole world that I love my wife and kids - what better way than one email at a time
    
    Ich will der ganzen Welt sagen, dass ich meine Frau und Kinder liebe – wie ist das besser zu machen als Mail für Mail,
    eine nach der anderen.
    -------------------------------------------------------------------------------------------------------------------------------------------
    
    
    
    ------------------------------------------------------------------------------
    Check out the vibrant tech community on one of the world's most
    engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    _______________________________________________
    Gpredict-discussion mailing list
    Gpr...@li...
    https://lists.sourceforge.net/lists/listinfo/gpredict-discussion
    
    ------------------------------------------------------------------------------
    Check out the vibrant tech community on one of the world's most
    engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    _______________________________________________
    Gpredict-discussion mailing list
    Gpr...@li...
    https://lists.sourceforge.net/lists/listinfo/gpredict-discussion
    

Re: [Gpredict-discussion] GPredict and SatNOGS rotor

[Lloyd B. <som...@gm...>]

I'm not sure I can address the first question at all, but I can give a
little info about the second one, the one about the rotation stops.

I'm only vaguely familiar with the SATNOGS project rotator, though I'd like
to build one some time.  So, let me as a couple of questions;

- What is the total amount of azimuth rotation in the SATNOGS rotator?
Traditionally az rotors were either 360 or 450 degrees.
- Does the azimuth rotor have rotation stops? If so, where are they
positioned?  North (0 deg) and South (+/- 180 deg) are the most common, but
really anything would work.
- Does the rotator expect to be fed only positive azimuth values (eg
0->360), or positive and negative values (eg. -180->0->180)?  Or does it
work well with either one?

Basically, I suspect you've got a problem with the defined azimuth stops in
gpredict.  For example, if your rotator has stops in the South, but
gpredict thinks they're in the North, or visa-versa.  If they don't agree,
then you have the swing-around problem, even when you wouldn't think it
would.


(LONG-WINDED EXPLANATION ALERT)

Let me explain in more detail.

For example, if your *actual* stops are in the North (0 deg), but gpredict
*thinks* they're in the South (+/- 180 deg), then you have these two
scenarios:
- When a pass crosses the North azimuth, gpredict assumes that it can just
go directly, and doesn't do anything weird. But, for example, when the
rotator is currently just west of north, and gpredict feeds it an azimuth
that's just east of north (assuming that it's only a few degrees to
change), the rotator will end up swinging all the way around to get there
from the other side.
- When a pass crosses the South azimuth, gpredict thinks it needs to do
avoid the rotation stops in the south, and so it does a flipped pass.  This
means that instead of tracking across the South azimuth, at some elevation
E, gpredict flips the antenna over and tracks across the North azimuth, at
an elevation of (180 degrees - E).  And so again, when gpredict feeds your
rotator something that crosses the North azimuth, it has to swing all the
way around again.

If you choose a 0->180->360 rotator in gpredict, it will assume the
rotation stops are in the North (0/360 deg), though that can be changed.
Similarly, if you choose a -180->0->180 rotator in gpredict, it will assume
the rotation stops are in the South (+/- 180 deg), but again, that can be
adjusted.

So, in the end, the simple answer is to make sure that gpredict correctly
knows where your azimuth rotation stops are, and it will work much better.

Lloyd



On Fri, May 11, 2018 at 8:28 AM, Sims, William Herb (MSFC-ES63) <
her...@na...> wrote:

> Guys and Gals,
>
> Two questions for the group.
>
> First, is there a way within GPredict to determine if TWO ground stations
> can see the same satellite at the same time?  Along a work related question
> we (Marshall Space Flight Center, MSFC) are doing some experiments on the
> International Space Station (ISS) RF test-bed and due to licensing issues
> on the station we cannot downlink data while NOT over pre-determined ground
> stations (in our we are NOT one of those ground stations but Glenn Research
> Center, GRC, is).  What we want to do is determine when both MSFC and GRC
> can see ISS at the same time.  Is it possible with GPRedict?  I realize we
> can use something Like Satellite Tool Kit but that requires funding other
> NASA people so I am trying to save our project some money (since I’m
> already on it).
>
> Second, I am using a SatNOGS rotor (AZ/EL) and was simulating tracking a
> satellite yesterday and noticed something that concerns me.  The satellite
> started on the horizon at say 10 degrees azimuth and during the pass went
> from 10 – 360 – 350 – 340 to finally close to 190 degrees.  The question I
> have is that once the projected azimuth hit 360 the SatnOGS rotor spun all
> the way around (went clockwise from 0.1 degrees to 180 to 359 degrees)
> instead of continuing in a counter-clockwise direction (this is, I believe,
> because I had the rotor controller set to 0-180-360).  I believe had I set
> the controller to -180-0-180 that it would have worked as expected.  The
> problem is, if I get a scenario of another satellite track that goes from
> 170 – 180 - -170 - -160, etc. and I was set up for the -180-0-180 it would
> do the same thing (i.e. go 170, 179.9 then swing all the way around
> counter-clockwise to -179 etc.).  Is that something that one “just has to
> live with” or should the rotor be capable of doing a full 720 degrees (2 *
> 360) too keep this from happening?  I realize that it would then wrap the
> coax around the system, but I just want to make sure that I am not missing
> something here.
>
> Thanks,
>
> Herb
>
>
> Dr. Herb Sims
> EV41
> Bldg. 4600 / Room 4113
> Control Systems Design & Analysis Branch
> MSFC, AL 35812
> 256-961-3214
> ------------------------------------------------------------
> ------------------------------------------------------------
> -------------------
> I want to tell the whole world that I love my wife and kids - what better
> way than one email at a time
>
> Ich will der ganzen Welt sagen, dass ich meine Frau und Kinder liebe – wie
> ist das besser zu machen als Mail für Mail,
> eine nach der anderen.
> ------------------------------------------------------------
> ------------------------------------------------------------
> -------------------
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Gpredict-discussion mailing list
> Gpr...@li...
> https://lists.sourceforge.net/lists/listinfo/gpredict-discussion
>