OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

IW8PGT

[Mendicino(CS)-Italy]

 Login: GUEST





  
CX2SA  > SATDIG   02.06.17 18:03l 823 Lines 27496 Bytes #999 (0) @ WW
BID : AMSATBB12139
Read: GUEST
Subj: AMSAT-BB-digest V12 139
Path: IW8PGT<IZ3LSV<IW0QNL<JH4XSY<JE7YGF<7M3TJZ<CX2SA
Sent: 170602/1551Z @:CX2SA.SAL.URY.SOAM #:9171 [Salto] FBB7.00e $:AMSATBB12139
From: CX2SA@CX2SA.SAL.URY.SOAM
To  : SATDIG@WW

Today's Topics:

   1. Lilacsat-1 QSO - Could be first over US? (Robert Mattaliano)
   2. Re: Lilacsat-1 QSO - Could be first over US? (Scott)
   3. Request for assistance to revive AU02 and AU03 QB50	Cubesats
      (Joon Wayn Cheong)
   4. K6G/MM DM02 (Paul Stoetzer)
   5. FUNcube/ AO73 Mode change (Jim Heck G3WGM)
   6. K6G/MM DM02 Plans (John Papay)
   7. Re: K6G/MM DM02 Plans (Paul Stoetzer)
   8. Tracking Program Window off screen (Joe)
   9. Re: Tracking Program Window off screen (w4upd)
  10. Sat demo at 1626 UTC today (2017-06-02) on AO-85 - call	me
      (John Brier)
  11. Re: Tracking Program Window off screen (Joe)
  12. Re: Tracking Program Window off screen (w4upd)
  13. Re: Tracking Program Window off screen (Joe)


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

Message: 1
Date: Fri, 2 Jun 2017 01:28:22 -0400
From: Robert Mattaliano <n6rfm1@xxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Lilacsat-1 QSO - Could be first over US?
Message-ID:
<CAFt1opw6z8gP87aBN5e4jqz-pYes62HJkX-9u85Gg2gSrREJPA@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"

Just completed QSO with Scott K4KDR in VA (FM17) from RI (FM41) on
Lilacsat-1.  This may very well be the first digital amateur downlink QSO
over the US. Thanks Scott!

DK3WIN and GI7UGV were also successful across the pond a few days ago.
Congrats guys!


Recall that Lilacsat-1 is among the QB50 constellation recently launched
from the ISS.  This bird is has a Codec2 1300bps digital downlink.  Setting
up the decoder requires an SDR for RX on a Linux platform.

A few hints - run low power (5-10 watts), keep mic gain down for better
audio clarity, watch out for desense since 2M up and 436 down with the SDR

More information at http://lilacsat.hit.edu.cn/?page_id=257.  Tks BG2BHC
and the Harbin team.
Also, a lower latency decoder from EA4GPZ at
http://destevez.net/2017/05/low-latency-decoder-for-lilacsat-1/#more-2671.
M6SIG also has an updated ISO here https://t.co/vmARZqIBoU

Hope to hear you on,

Bob
N6RFM


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

Message: 2
Date: Fri, 2 Jun 2017 03:55:14 -0400
From: "Scott" <scott23192@xxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Lilacsat-1 QSO - Could be first over US?
Message-ID: <DE17F6A61680458F8BFC6968FB77866D@xxxxxxx>
Content-Type: text/plain;	charset="UTF-8"

Thanks Bob, a real thrill to be one of the first to have success with a new
satellite.

I know that using a computer to extract voice from a data stream on the
receive side adds complexity, but it was a fun challenge to get working. 
One side benefit is that you can record & replay the entire satellite pass
because the whole QSO is received as computer data and saved as a file.

I have uploaded a video made while replaying my contact with Bob; that can
be found at:  https://youtu.be/BjWZJBBcQfQ

Also, I re-recorded the audio recording that Bob made at his end to a .wav
file that might be easier for Windows users to play.  That can be found at:

https://www.dropbox.com/s/gazmkon1558me1v/2017-06-02--0446--LilacSat-1--audio-
from-bob.wav?dl=0

If you watch the YouTube video, you'll hear that I received Bob's signal
from the satellite much better than my own.  This is for a number of reasons
that everyone on this list is already familiar with, but I wanted to list
them anyway since using a computer to decode a voice stream from data might
be new to some.

#1, Bob knew what he was doing.  This was maybe my 4th or 5th satellite
contact

#2, the satellite was at a much higher elevation for Bob; from my house it
was much lower in the sky and it's summer in the U.S. & I'm surrounded by
trees full of leaves

#3, when you hear my audio, that is coming down from the satellite at the
same time I'm transmitting, so we're in a full-duplex situation. 
Fortunately, my SP-70 pre-amp and Airspy SDR receiver combine to block out
most of the attenuation caused by the 2-meter uplink

... I'm only going into this detail to illustrate that this isn't so
different from any other satellite QSO.  So, I hope many others will get
setup to decode this digital downlink.  I've seen many of the more
experienced folks already using SDR's for their receive radio, so this isn't
much different from that - you just need to run software that's more
involved than HDSDR or SDRSharp.

It would be a challenge to teach Linux from scratch remotely, but beyond
that with the GNU Radio portion of this, I'll be glad to help anyone who has
the basics in place and just needs a hand with the details.  There's a 100%
guarantee that you'll be much more experienced with satellites than I am,
but maybe I've done more on the computer side than a portion of the people
out there.  Anyway, glad to help if I can.

73!

-Scott,  K4KDR
Montpelier, VA  USA


===================================================

From: Robert Mattaliano
Sent: Friday, June 02, 2017 1:28 AM
To: amsat-bb@xxxxx.xxx
Cc: Scott
Subject: Lilacsat-1 QSO - Could be first over US?

Just completed QSO with Scott K4KDR in VA (FM17) from RI (FM41) on
Lilacsat-1.  This may very well be the first digital amateur downlink QSO
over the US. Thanks Scott!

DK3WIN and GI7UGV were also successful across the pond a few days ago. 
Congrats guys!


Recall that Lilacsat-1 is among the QB50 constellation recently launched
from the ISS.  This bird is has a Codec2 1300bps digital downlink.  Setting
up the decoder requires an SDR for RX on a Linux platform.

A few hints - run low power (5-10 watts), keep mic gain down for better
audio clarity, watch out for desense since 2M up and 436 down with the SDR

More information at http://lilacsat.hit.edu.cn/?page_id=257.  Tks BG2BHC and
the Harbin team.
Also, a lower latency decoder from EA4GPZ at
http://destevez.net/2017/05/low-latency-decoder-for-lilacsat-1/#more-2671.
M6SIG also has an updated ISO here https://t.co/vmARZqIBoU

Hope to hear you on,

Bob
N6RFM







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

Message: 3
Date: Fri, 2 Jun 2017 10:45:47 +0000
From: Joon Wayn Cheong <cjwayn@xxxx.xxx.xx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Cc: Elias Aboutanios <elias@xxxx.xxx.xx>, William Andrew
<w.andrew@xxxxxxx.xxx>,	"Benjamin Southwell \(Redirection\)"
<benjsouthwell@xxxxx.xxx>, Joon Wayn	Cheong <cjwayn@xxxx.xxx.xx>
Subject: [amsat-bb] Request for assistance to revive AU02 and AU03
QB50	Cubesats
Message-ID:
<SYXPR01MB16643988881EFE0FFA6568508DF70@xxxxxxxxxxxxx.xxxxxxxx.xxxx.xxxxxxx.xx
x>

Content-Type: text/plain; charset="us-ascii"

I'm part of the AU02 (UNSW-EC0) and AU03 (i-INSPIRE 2) Australian team of
QB50 cubesats, and I'm writing here to request for assistance from the
experienced and well-equipped foreign HAM amateurs experts here.

Our satellite was deployed last week and we have been unable to hear any
beacons coming from it. We had several brainstorm sessions to identify
possible configurations that could be changed to optimise the occurrence
antenna redeployment sequence. Based on this, we devised a set of commands
that reflect these changes in configurations that needs to be uplinked to
the satellite. We have attempted to uplink these commands at 50W transmit
power, but there's no response so far.

We strongly believe the satellite is still alive but has an undeployed
antenna. As such, we require sufficient transmit gain in both transmit power
and antenna gain to achieve positive uplink margin. Our problem is that we
do not have the equipment to achieve the required transmit power to overcome
the losses due to an unstowed configuration.

We have a recorded *.wav file that you can play through radio in FM mode to
perform the uplink.

Relevant technical info:

-        The sat uses Nanocom ANT430 antenna that is still stowed. The
stowed antenna is exposed on the outside of the spacecraft.

-        The sat uses Nanocom U482C transceiver.

-        The OBC might be trickling between on and off states and hence a
daytime or dusk zenith pass is optimal for the uplink.

Our ground station:

-        21 el H and 21el V yagi configured in RHCP

-        Kenwood TS-2000 in FM mode with 50W transmit power.

Hope you have a good weekend, and do not hesitate to contact me at
cjwayn@xxxx.xxx.xx<xxxxxxxxxxxxx@xxxx.xxx.xx> if you would be willing to
help. Your attention has been much appreciated..

Cheers,
Joon Wayn



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

Message: 4
Date: Fri, 2 Jun 2017 08:24:59 -0400
From: Paul Stoetzer <n8hm@xxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] K6G/MM DM02
Message-ID:
<CABzOSOpjcwDKMTj-f-_jcF=UzScVGZd9oVAtheNz_1AirVsAYw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"

AI6GS has worked quite a few stations so far this morning as K6G/MM from
DM02. He'll be there until around 17:00 UTC today.

Don't miss it! This is the rarest of the 488 continental US grids as the
only land in the grid is San Clemente Island, which is owned by the U. S.
Navy.

73,

Paul, N8HM


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

Message: 5
Date: Fri, 2 Jun 2017 13:30:27 +0100
From: "Jim Heck G3WGM" <jimlist@xxxx.xxx>
To: "AMSAT BB" <amsat-bb@xxxxx.xxx>
Cc: funcube@xxxxxxxxxxx.xx.xx
Subject: [amsat-bb] FUNcube/ AO73 Mode change
Message-ID: <64CE1BC6CF38407986FD72DD049C5E16@xxxxxx>
Content-Type: text/plain; format=flowed; charset="utf-8";
reply-type=response

Hi folks,

AO73/FUNcube-1 is now in amateur mode. Switched early this weekend to
facilitate special ops (Grid Squares) in the USA!

Switch back to educational mode will be done on Sunday PM UTC as usual.

Have FUN everyone!

Please see below for all FUNcube mission info

73s Jim G3WGM and the FUNcube team.

++++++++++++++++++++++++++++++++++
FUNcube frequencies and other details
++++++++++++++++++++++++++++++++++

AO-73 FUNcube-1

The transponder is normally operational only when the satellite is in
eclipse, ie the solar panels are NOT being illuminated. During weekends
(from pm Fridays UTC to PM Sundays UTC) the transponder is operational 24/7.

When the transponder is switched off, the telemetry beacon is on full power,
when the transponder is on the beacon it is on low power. During holidays,
eg Christmas, New Year, Easter, etc, the transponder maybe activated for
extended periods. Watch AMSAT-BB for announcements which are usually made on
Friday evenings (UTC)

The nominal transponder frequencies are:

Uplink:   435.150 - 435.130 MHz LSB (Inverting)
Downlink:   145.950 - 145.970 MHz USB
Telemetry Tx: 145.935 MHz BPSK

(The passband may be up to 15kHz higher depending on on-board temps. Lower
temperatures give higher freqs!)

FUNcube-2 (aka FUNcube on UKube)

The FUNcube-2 sub-system continues to operate autonomously and, almost
continuously, in amateur mode. The transponder is operational and the
telemetry downlink is functioning with about 70mW output. The FUNcube-1
Dashboard does not correctly display the telemetry but it does correctly
decode the data and uploads it to the FUNcube Data Warehouse from where it
can be examined. Most of the real time data channels are operational and
these include battery voltages, temperatures and ADCS data coming via the
main On Board Computer (OBC).

The transponder is interrupted for a few seconds every 2 minutes when the
other transmitter sends its CW beacon and, occasionally, for a few seconds
when the main OBC reboots (approx seven times each orbit).

The nominal transponder frequencies are:
Uplink:   435.080 - 435.060 MHz LSB (Inverting)
Downlink:   145.930 - 145.950 MHz USB
Telemetry Tx: 145.915 MHz BPSK

(The passband may be up to 10kHz higher depending on on-board temps. Low
temperatures give higher freqs!)


EO79 FUNcube-3
Due to power budget constraints the transponder cannot be operational 24/7
and an orbit specific schedule has been developed. The transponder will
commence operation 27 minutes after the spacecraft enters sunlight and will
stay on for a period of 25 minutes. This schedule may be modified in future
months as a result of experience.

The nominal transponder frequencies are:
Uplink: 435.0723-435.0473 MHz LSB (Inverting)
Downlink: 145.946-145.971 MHz USB

Further detailed info on EO79 transponder frequencies is at:
https://amsat-uk.org/2016/11/10/eo79-funcube-3-transponder-commences-regular-o
peration/


EO88/Nayif-1/FUNcube-5

EO88 is presently operating in autonomous mode. The transponder is
operational when the satellite is in eclipse, ie the solar panels are NOT
being illuminated.
When the transponder is switched off, the telemetry beacon is on full power,
when the transponder is on the beacon it is on low power.
The transponder frequencies are:

Uplink:  435.045 ? 435.015 MHz LSB (inverting)
Downlink: 145.960-145.990 MHz USB
Telemetry  Tx: 145.940MHz

All FUNcube transponders are sponsored by AMSAT-UK and AMSAT-NL. We are very
grateful for the assistance given by Innovative Solution In Space Bv, The
Netherlands.

_______________________________________________
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: 6
Date: Fri, 02 Jun 2017 09:16:11 -0400
From: John Papay <john@xxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] K6G/MM DM02 Plans
Message-ID: <20170602131618.43E2B897D@xxxxxxxxxx.xxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"; format=flowed


K6G DM02 advises he'll be QRX for a few hours. Next opportunity might
be FO-29. Good to check all passes as plans could change.
73,
John K8YSE


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



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

Message: 7
Date: Fri, 2 Jun 2017 09:18:46 -0400
From: Paul Stoetzer <n8hm@xxxx.xxx>
To: John Papay <john@xxxxxx.xxx>
Cc: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] K6G/MM DM02 Plans
Message-ID:
<CABzOSOrftEqK_j1sT-7xwBEfgSovUCJjkgR9u2Rm_5EzQke6sA@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"

There should be at least a couple more passes for everyone, coast-to-coast.

AO-73 was turned on early specifically for this operation.

73,

Paul, N8HM

On Fri, Jun 2, 2017 at 9:16 AM, John Papay <john@xxxxxx.xxx> wrote:

>
> K6G DM02 advises he'll be QRX for a few hours. Next opportunity might be
> FO-29. Good to check all passes as plans could change.
> 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: Fri, 2 Jun 2017 08:20:35 -0500
From: Joe <nss@xxx.xxx>
To: AMSAT-BB <AMSAT-BB@xxxxx.xxx>
Subject: [amsat-bb] Tracking Program Window off screen
Message-ID: <2b525f2e-5a25-2a56-1bfd-cd114b09a07f@xxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed

I know this is probably more of a Windows 10 issue,

But when I try to open HRD Sat Track, it starts up, But 90% of it is off
screen down low so that only the top 1/4 of the window is visible.

Clicking on the usual middle box thing only causes a beep, clicking
anywhere on the program just causes a beep.  even the "X" to close it,
just causes a beep. the only way to make it go away is via the task manager.

what to do?

Joe WB9SBD
--
Sig
The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com


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

Message: 9
Date: Fri, 02 Jun 2017 11:02:04 -0400
From: w4upd <w4upd@xxx.xx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Tracking Program Window off screen
Message-ID: <59317DEC.5030609@xxx.xx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I don't seem to have that problem. I am running 64-bit Windows 10 and it
seems to run. However, I am running the last "free" version (Version 5).
I do find it very slow coming up (HRD itself).

You might try running under administrator. Also, check your display
settings.

About all I can tell you. I really don't use it much due to being a cpu
hog, and stick with SatPC32 and others. I occasionally use just HRD by
itself on some of my rigs.

Reid, W4UPD


On 6/2/2017 9:20 AM, Joe wrote:
> I know this is probably more of a Windows 10 issue,
>
> But when I try to open HRD Sat Track, it starts up, But 90% of it is
> off screen down low so that only the top 1/4 of the window is visible.
>
> Clicking on the usual middle box thing only causes a beep, clicking
> anywhere on the program just causes a beep.  even the "X" to close it,
> just causes a beep. the only way to make it go away is via the task
> manager.
>
> what to do?
>
> Joe WB9SBD



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

Message: 10
Date: Fri, 2 Jun 2017 11:10:29 -0400
From: John Brier <johnbrier@xxxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Sat demo at 1626 UTC today (2017-06-02) on AO-85 -
call	me
Message-ID:
<CALn0fKO7iLk4DMTzQ-KxDCu18pi8i1qVhAqi1ArtZ44Q8kYNbg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"

I'm doing a demo at work. Give me a call if you can.

73, John Brier KG4AKV


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

Message: 11
Date: Fri, 2 Jun 2017 10:23:43 -0500
From: Joe <nss@xxx.xxx>
To: w4upd <w4upd@xxx.xx.xxx>, amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Tracking Program Window off screen
Message-ID: <394fae0f-3f21-26fd-a19d-c28d8530189c@xxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed

I have not ever had this problem either till today.

I always run it under administrator.
Every other Sat program is fine as well as any other windows. here is a
video of whats happening,, be sure to have your volume up.

https://vimeo.com/220021400

Joe WB9SBD
Sig
The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com
On 6/2/2017 10:02 AM, w4upd wrote:
> I don't seem to have that problem. I am running 64-bit Windows 10 and
> it seems to run. However, I am running the last "free" version
> (Version 5). I do find it very slow coming up (HRD itself).
>
> You might try running under administrator. Also, check your display
> settings.
>
> About all I can tell you. I really don't use it much due to being a
> cpu hog, and stick with SatPC32 and others. I occasionally use just
> HRD by itself on some of my rigs.
>
> Reid, W4UPD
>
>
> On 6/2/2017 9:20 AM, Joe wrote:
>> I know this is probably more of a Windows 10 issue,
>>
>> But when I try to open HRD Sat Track, it starts up, But 90% of it is
>> off screen down low so that only the top 1/4 of the window is visible.
>>
>> Clicking on the usual middle box thing only causes a beep, clicking
>> anywhere on the program just causes a beep.  even the "X" to close
>> it, just causes a beep. the only way to make it go away is via the
>> task manager.
>>
>> what to do?
>>
>> Joe WB9SBD
>
> _______________________________________________
> 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: 12
Date: Fri, 02 Jun 2017 11:33:29 -0400
From: w4upd <w4upd@xxx.xx.xxx>
To: Joe <nss@xxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Tracking Program Window off screen
Message-ID: <59318549.7090005@xxx.xx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed

Have you tried to bring just HRD itself up? Looks like you are bringing
up the satellite portion in stand alone. As far as I know, it requires
that HRD be in the background. I know if I bring up HRD then select the
satellite, then stop HRD but leave the satellite portion up, I have to
use task manager to stop it then.

It looks like the windows init file has saved the satellite portion off
screen, and starts it up there each time. If HRD is not running as well,
you may have this problem.

Again, I don't use it much, but that is what I have observed. I don't
run the satellite portion without HRD itself running as well. That was
one of the earlier complaints and I assume was suppose to be fixed in
later versions.

Reid, W4UPD


On 6/2/2017 11:23 AM, Joe wrote:
> I have not ever had this problem either till today.
>
> I always run it under administrator.
> Every other Sat program is fine as well as any other windows. here is
> a video of whats happening,, be sure to have your volume up.
>
> https://vimeo.com/220021400
>
> Joe WB9SBD
> Sig
> The Original Rolling Ball Clock
> Idle Tyme
> Idle-Tyme.com
> http://www.idle-tyme.com
> On 6/2/2017 10:02 AM, w4upd wrote:
>> I don't seem to have that problem. I am running 64-bit Windows 10 and
>> it seems to run. However, I am running the last "free" version
>> (Version 5). I do find it very slow coming up (HRD itself).
>>
>> You might try running under administrator. Also, check your display
>> settings.
>>
>> About all I can tell you. I really don't use it much due to being a
>> cpu hog, and stick with SatPC32 and others. I occasionally use just
>> HRD by itself on some of my rigs.
>>
>> Reid, W4UPD
>>
>>
>> On 6/2/2017 9:20 AM, Joe wrote:
>>> I know this is probably more of a Windows 10 issue,
>>>
>>> But when I try to open HRD Sat Track, it starts up, But 90% of it is
>>> off screen down low so that only the top 1/4 of the window is visible.
>>>
>>> Clicking on the usual middle box thing only causes a beep, clicking
>>> anywhere on the program just causes a beep.  even the "X" to close
>>> it, just causes a beep. the only way to make it go away is via the
>>> task manager.
>>>
>>> what to do?
>>>
>>> Joe WB9SBD
>>
>> _______________________________________________
>> 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: 13
Date: Fri, 2 Jun 2017 10:44:54 -0500
From: Joe <nss@xxx.xxx>
To: w4upd <w4upd@xxx.xx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Tracking Program Window off screen
Message-ID: <bdb18dcf-a9fd-860b-93ee-7e085cdf9a7d@xxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed

Isn't that interesting.
I have for years been running it just fine in stand alone mode and has
always worked fine till today.

I tried what you said fired up HRD first, ( never ever use it for anything )
got it opened then through it Opened the sat track part. it opened just
fine.

I closed HRD  then closed the sat track,  then tried re opening the sat
track standing alone and it opened just fine.

weird huh?

Joe WB9SBD
Sig
The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com
On 6/2/2017 10:33 AM, w4upd wrote:
> Have you tried to bring just HRD itself up? Looks like you are
> bringing up the satellite portion in stand alone. As far as I know, it
> requires that HRD be in the background. I know if I bring up HRD then
> select the satellite, then stop HRD but leave the satellite portion
> up, I have to use task manager to stop it then.
>
> It looks like the windows init file has saved the satellite portion
> off screen, and starts it up there each time. If HRD is not running as
> well, you may have this problem.
>
> Again, I don't use it much, but that is what I have observed. I don't
> run the satellite portion without HRD itself running as well. That was
> one of the earlier complaints and I assume was suppose to be fixed in
> later versions.
>
> Reid, W4UPD
>
>
> On 6/2/2017 11:23 AM, Joe wrote:
>> I have not ever had this problem either till today.
>>
>> I always run it under administrator.
>> Every other Sat program is fine as well as any other windows.  here
>> is a video of whats happening,, be sure to have your volume up.
>>
>> https://vimeo.com/220021400
>>
>> Joe WB9SBD
>> Sig
>> The Original Rolling Ball Clock
>> Idle Tyme
>> Idle-Tyme.com
>> http://www.idle-tyme.com
>> On 6/2/2017 10:02 AM, w4upd wrote:
>>> I don't seem to have that problem. I am running 64-bit Windows 10
>>> and it seems to run. However, I am running the last "free" version
>>> (Version 5). I do find it very slow coming up (HRD itself).
>>>
>>> You might try running under administrator. Also, check your display
>>> settings.
>>>
>>> About all I can tell you. I really don't use it much due to being a
>>> cpu hog, and stick with SatPC32 and others. I occasionally use just
>>> HRD by itself on some of my rigs.
>>>
>>> Reid, W4UPD
>>>
>>>
>>> On 6/2/2017 9:20 AM, Joe wrote:
>>>> I know this is probably more of a Windows 10 issue,
>>>>
>>>> But when I try to open HRD Sat Track, it starts up, But 90% of it
>>>> is off screen down low so that only the top 1/4 of the window is
>>>> visible.
>>>>
>>>> Clicking on the usual middle box thing only causes a beep, clicking
>>>> anywhere on the program just causes a beep.  even the "X" to close
>>>> it, just causes a beep. the only way to make it go away is via the
>>>> task manager.
>>>>
>>>> what to do?
>>>>
>>>> Joe WB9SBD
>>>
>>> _______________________________________________
>>> 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 139
*****************************************


Read previous mail | Read next mail


 11.05.2024 22:07:10lGo back Go up