OpenBCM V1.08-5-g2f4a (Linux)

Packet Radio Mailbox

IZ3LSV

[San Dona' di P. JN]

 Login: GUEST





  
CX2SA  > SATDIG   14.07.12 21:03l 571 Lines 17815 Bytes #999 (0) @ WW
BID : AMSATBB7222
Read: GUEST
Subj: AMSAT-BB-digest V7 222
Path: IZ3LSV<IW0QNL<ON4HU<CX2SA
Sent: 120714/1902Z @:CX2SA.SAL.URY.SA #:63073 [Salto] FBB7.00e $:AMSATBB7222
From: CX2SA@CX2SA.SAL.URY.SA
To  : SATDIG@WW

Today's Topics:

   1. DM23/DM24 (Patrick STODDARD (WD9EWK/VA7EWK))
   2. Re: DM23/DM24 (Bob DeVarney W1ICW)
   3. Behind NASA Video on Rover Landing (Clint Bradford)
   4. Fw: Update: DELFI C3 Close Approach Message (Peter Portanova)
   5. Thank you (Matt Severin)
   6. SatPC32 12.8b and Win7 (Matt Severin)
   7. Re: SatPC32 12.8b and Win7 (Jim Jerzycke)
   8. Re: SatPC32 12.8b and Win7 (Matt Severin)
   9. Re: SatPC32 12.8b and Win7 (Jim Jerzycke)
  10. aprs via ariss (Lizeth Norman)
  11. low hanging fruit:portable antenna setup (Lizeth Norman)
  12. Re: aprs via ariss (Bob Bruninga )
  13. Re: DM23/DM24 (Patrick STODDARD (WD9EWK/VA7EWK))
  14. W0PHD de W9KE (Thomas Doyle)


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

Message: 1
Date: Fri, 13 Jul 2012 12:46:59 -0700 (PDT)
From: "Patrick STODDARD \(WD9EWK/VA7EWK\)" <amsat-bb@xxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] DM23/DM24
Message-ID:
<1342208819.34611.BPMail_high_carrier@xxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii


Hi!

After working FO29 & AO27 in the last hour, I'm back for
the passes on these birds in the next 45 minutes. It
is about 96F/36C, cloudy & humid. My glasses fogged up
when I got out of my car a little while ago.

Hope to work you on these upcoming passes... 73!





Patrick WD9EWK/VA7EWK - southeast of Parker, Arizona
http://www.wd9ewk.net/




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

Message: 2
Date: Fri, 13 Jul 2012 16:13:43 -0400
From: Bob DeVarney W1ICW <we1u@xxxxxxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: DM23/DM24
Message-ID: <50008177.5040706@xxxxxxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Heard you FB here in FN34 Patrick, but couldn't get the old computer
booted up fast enough to work you on FO-29.

On 7/13/2012 3:46 PM, Patrick STODDARD (WD9EWK/VA7EWK) wrote:
> Hi!
>
> After working FO29 & AO27 in the last hour, I'm back for
> the passes on these birds in the next 45 minutes. It
> is about 96F/36C, cloudy & humid. My glasses fogged up
> when I got out of my car a little while ago.
>
> Hope to work you on these upcoming passes... 73!
>
>
>
>
>
> Patrick WD9EWK/VA7EWK - southeast of Parker, Arizona
> http://www.wd9ewk.net/
>
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
>




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

Message: 3
Date: Fri, 13 Jul 2012 14:58:48 -0700
From: Clint Bradford <clintbradford@xxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Behind NASA Video on Rover Landing
Message-ID: <38E78F88-B47A-4833-923A-9CB6F4A1E959@xxx.xxx>
Content-Type: text/plain; CHARSET=US-ASCII

L.A. TIMES article - Behind JPL's "Seven Minutes of Terror" video on risky
rover landing ...

http://soc.li/8graWEB

And don't forget to watch the launch of astronauts to the ISS Saturday
morning!

Clint K6LCS


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

Message: 4
Date: Fri, 13 Jul 2012 19:40:03 -0400
From: "Peter Portanova" <wb2oqq@xxxxxxx.xxx>
To: <AMSAT-BB@xxxxx.xxx>
Subject: [amsat-bb] Fw: Update: DELFI C3 Close Approach Message
Message-ID: <C04F34CBD26645BAB3CBA5D450328DB6@xxxxxxx>
Content-Type: text/plain; format=flowed; charset=iso-8859-1;
reply-type=original

Hello,

FYI

73 WB2OQQ

Subject: Update: DELFI C3 Close Approach Message

Sir/Ma'am,

The United States Joint Space Operations Center (JSpOC) has updated a
predicted conjunction between DELFI C3 (SCC# 32789) and SCC# 23657.

Primary Object: DELFI C3 (SCC# 32789)
Secondary Object: SCC# 23657
Time of Closest Approach: 15 JUL 2012 21:21 UTC

Overall miss distance: 748 meters
Radial (dU) miss distance: -179 meters
In-Track (dV) miss distance: -382 meters
Cross-track (dW) miss distance: -619 meters

Primary Radial Error (U): 26 meters
Primary In-track Error (V): 898 meters
Primary Cross-track Error (W): 11 meters

Secondary Radial Error (U): 8 meters
Secondary In-track Error (V): 208 meters
Secondary Cross-track Error (W): 2 meters

Very Respectfully,

JSpOC Orbital Protection Team
Joint Space Operations Center
Vandenberg Air Force Base, California USA

NO WARRANTIES: The United States provides the enclosed Space Situational
Awareness (SSA) services or information "as is" and makes no warranty,
either express or implied, as to the condition or suitability of the
information and services, nor its fitness for a particular purpose.

IMMUNITY: The United States, any agencies and instrumentalities thereof, and
any individuals, firms, corporations, and other persons acting for the
United States, shall be immune from any suit in any court for any cause of
action arising from the provision or receipt of SSA services or information,
whether or not provided in accordance with 10 USC 2274, or any related
action or omission.





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

Message: 5
Date: Fri, 13 Jul 2012 19:53:52 -0400
From: Matt Severin <mtseverin@xxxxx.xxx>
To: amsat-bb <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Thank you
Message-ID:
<CAF7cmSTVWOvfaac2CML2rxwQf=nFg3Dhe_TBVSVmCWq3ozVZmQ@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1

Thank you to all of the hams that helped to make the ARRL Teachers'
Institute II a success.  I had 8 teachers this past week at the Dayton
Amateur Radio Assoc. club house learning how to set up and operate a
satellite station, and by the first part of Day 3 all 8 had made their
first satellite qso!  By the week's end many had made multiple contacts
with the satellite community.   Thank you for your patience and
stick-with-it-ness with this group.  They are very excited to get home and
set up their station, and even more excited to share satellites with their
students.

73

Matt, N8MS


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

Message: 6
Date: Fri, 13 Jul 2012 20:02:32 -0400
From: Matt Severin <mtseverin@xxxxx.xxx>
To: amsat-bb <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] SatPC32 12.8b and Win7
Message-ID:
<CAF7cmSRLR6wD_MW97Ccxva6K3GgLjOAVqq7czh04HbR9qwusPg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1

While working with the 8 teachers at Teachers' Institute II, I had a
variety of computer operating systems.  We had some odd behavior with the
Win7 machines, but I am not sure if this was a fluke or a pattern.

We were using SatPC32 v12.8b with the SAEBRTrackBox setting in the
software, and the students with issues were running Win7.  The G5500's did
not always respond as expected.  For example, if we commanded it to move to
45 degrees elevation, it would, but if we manually entered 179 degrees it
would drop down to about 25 degrees.  The fix seemed to be to set the
turning point of azim rotor under the 'Rotor Setup" to S instead of N.  I
am running v12.8a and have not trouble with the exact same set up and I am
set to 'N".

Has anyone else experienced this?  In my trouble shooting, I believe I was
able to trace it back to the computers/software.  Any thoughts?

Thanks in advance.

Matt, N8MS


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

Message: 7
Date: Sat, 14 Jul 2012 01:13:47 +0000
From: Jim Jerzycke <kq6ea@xxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: SatPC32 12.8b and Win7
Message-ID: <5000C7CB.8080207@xxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

What rotor interface are you using?

Jim  KQ6EA

On 07/14/2012 12:02 AM, Matt Severin wrote:
> While working with the 8 teachers at Teachers' Institute II, I had a
> variety of computer operating systems.  We had some odd behavior with the
> Win7 machines, but I am not sure if this was a fluke or a pattern.
>
> We were using SatPC32 v12.8b with the SAEBRTrackBox setting in the
> software, and the students with issues were running Win7.  The G5500's did
> not always respond as expected.  For example, if we commanded it to move to
> 45 degrees elevation, it would, but if we manually entered 179 degrees it
> would drop down to about 25 degrees.  The fix seemed to be to set the
> turning point of azim rotor under the 'Rotor Setup" to S instead of N.  I
> am running v12.8a and have not trouble with the exact same set up and I am
> set to 'N".
>
> Has anyone else experienced this?  In my trouble shooting, I believe I was
> able to trace it back to the computers/software.  Any thoughts?
>
> Thanks in advance.
>
> Matt, N8MS
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
>




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

Message: 8
Date: Fri, 13 Jul 2012 21:40:27 -0400
From: Matt Severin <mtseverin@xxxxx.xxx>
To: Jim Jerzycke <kq6ea@xxxxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: SatPC32 12.8b and Win7
Message-ID:
<CAF7cmSS_QFa6B7Axg0SWysVVLGw+rHiWtSfJQtR25wqrKDK0RQ@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1

A Sat688 rotor interface.

Matt

On Fri, Jul 13, 2012 at 9:13 PM, Jim Jerzycke <kq6ea@xxxxxxx.xxx> wrote:

> What rotor interface are you using?
>
> Jim  KQ6EA
>
>
> On 07/14/2012 12:02 AM, Matt Severin wrote:
>
>>  While working with the 8 teachers at Teachers' Institute II, I had a
>> variety of computer operating systems.  We had some odd behavior with the
>> Win7 machines, but I am not sure if this was a fluke or a pattern.
>>
>> We were using SatPC32 v12.8b with the SAEBRTrackBox setting in the
>> software, and the students with issues were running Win7.  The G5500's did
>> not always respond as expected.  For example, if we commanded it to move
>> to
>> 45 degrees elevation, it would, but if we manually entered 179 degrees it
>> would drop down to about 25 degrees.  The fix seemed to be to set the
>> turning point of azim rotor under the 'Rotor Setup" to S instead of N.  I
>> am running v12.8a and have not trouble with the exact same set up and I am
>> set to 'N".
>>
>> Has anyone else experienced this?  In my trouble shooting, I believe I was
>> able to trace it back to the computers/software.  Any thoughts?
>>
>> Thanks in advance.
>>
>> Matt, N8MS
>> ______________________________**_________________
>> Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
>> Not an AMSAT-NA member? Join now to support the amateur satellite program!
>> Subscription settings:
http://amsat.org/mailman/**listinfo/amsat-bb<http://amsat.org/mailman/listinfo
/amsat-bb>
>>
>>
>
> ______________________________**_________________
> Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings:
http://amsat.org/mailman/**listinfo/amsat-bb<http://amsat.org/mailman/listinfo
/amsat-bb>
>


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

Message: 9
Date: Sat, 14 Jul 2012 02:51:49 +0000
From: Jim Jerzycke <kq6ea@xxxxxxx.xxx>
To: Matt Severin <mtseverin@xxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: SatPC32 12.8b and Win7
Message-ID: <5000DEC5.8020008@xxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

OK, that's identical to the Fox Delta ST1 kit.

Have you calibrated it?

The procedure is here, on the Fox Delta page:

http://www.foxdelta.com/products/st1.htm

Scroll down to *Setup Guideline for SatPC & Nova for Windows**

*

On 07/14/2012 01:40 AM, Matt Severin wrote:
> A Sat688 rotor interface.
> Matt
> On Fri, Jul 13, 2012 at 9:13 PM, Jim Jerzycke <kq6ea@xxxxxxx.xxx
> <mailto:kq6ea@xxxxxxx.xxx>> wrote:
>
>     What rotor interface are you using?
>
>     Jim  KQ6EA
>
>
>     On 07/14/2012 12:02 AM, Matt Severin wrote:
>
>         While working with the 8 teachers at Teachers' Institute II, I
>         had a
>         variety of computer operating systems.  We had some odd
>         behavior with the
>         Win7 machines, but I am not sure if this was a fluke or a pattern.
>
>         We were using SatPC32 v12.8b with the SAEBRTrackBox setting in the
>         software, and the students with issues were running Win7.  The
>         G5500's did
>         not always respond as expected.  For example, if we commanded
>         it to move to
>         45 degrees elevation, it would, but if we manually entered 179
>         degrees it
>         would drop down to about 25 degrees.  The fix seemed to be to
>         set the
>         turning point of azim rotor under the 'Rotor Setup" to S
>         instead of N.  I
>         am running v12.8a and have not trouble with the exact same set
>         up and I am
>         set to 'N".
>
>         Has anyone else experienced this?  In my trouble shooting, I
>         believe I was
>         able to trace it back to the computers/software.  Any thoughts?
>
>         Thanks in advance.
>
>         Matt, N8MS
>         _______________________________________________
>         Sent via AMSAT-BB@xxxxx.xxx <mailto:AMSAT-BB@xxxxx.xxx>.
>         Opinions expressed are those of the author.
>         Not an AMSAT-NA member? Join now to support the amateur
>         satellite program!
>         Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
>
>
>
>     _______________________________________________
>     Sent via AMSAT-BB@xxxxx.xxx <mailto:AMSAT-BB@xxxxx.xxx>. Opinions
>     expressed are those of the author.
>     Not an AMSAT-NA member? Join now to support the amateur satellite
>     program!
>     Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
>
>




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

Message: 10
Date: Fri, 13 Jul 2012 23:31:08 -0400
From: Lizeth Norman <normanlizeth@xxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] aprs via ariss
Message-ID:
<CAJUhCTOD4DTjXwAydz9jzG5eE4-7gOgseoQgZGVfs61FpEWMEQ@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1

Hi all,
I tried gating packets like this on 437.55 this afternoon. Is the format
right?

N3YKF-3>APTT4,ARISS,IS:/131918z2901.30N/08210.41W>288/000/n3ykf
mobile!/A=000121
!wgO!
Thanks,
Norm n3ykf


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

Message: 11
Date: Fri, 13 Jul 2012 23:53:35 -0400
From: Lizeth Norman <normanlizeth@xxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] low hanging fruit:portable antenna setup
Message-ID:
<CAJUhCTO0rB5W1E=h0KXr+jn2PGPv_fZfnFMZ8J0GqRuF0B0j5Q@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1

Hi all,
Looking to optimize my portable antenna setup for best performance.
I've got an Elk dual band and an Elk 8 el uhf log periodic for
uplink/downlink. Gain figures (from Elk) are 7db give or take for both
bands and 8db for the 8el uhf
How should these be mounted to minimize interaction with the ground,
each other and the tripod for the best results?
73 es have fun,
Norm


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

Message: 12
Date: Sat, 14 Jul 2012 07:57:14 -0400 (EDT)
From: "Bob Bruninga " <bruninga@xxxx.xxx>
To: "Lizeth Norman" <normanlizeth@xxxxx.xxx>, amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: aprs via ariss
Message-ID: <201207141157.021096@xxx.xxxx.xxx>
Content-Type: text/plain; charset=us-ascii

The key to success on a busy channel is short packets:

> N3YKF-3>APTT4,ARISS,IS:/131918z2901.30N/08210.41W>288/000/n3ykf
mobile!/A=000121!wgO!

There are 41 bytes in that  packet that are of no value in this application.

1) Remove the path "IS" (is 7 bytes in the actual protocol) and it is not
valie anyway for APRS

2) A time stamp is usually not needed, since APRS is always  LIVE, it is
valid the instant it is reecived

3) No need to repeat your call in the packet since it is in the callsign field

4) No need to say "mobile" because you are using ths symbol for a car anyway

5) When going through the iss at 7,000,000 feet high there is not much value
in reporting your altitude as 121 feet.

6) When making a thousand mile contact the PRECISE position data in the
!wgO! format to 6 inches is not needed

7) Use the !DDMM.mmN/DDDMM.mmW>... format without the time stamp.

8) Make sure your TXD is 150 or 200 ms instead of te default.

That should cut your packet timeto HALF or more and double your chance of
success.

Bob, Wb4APR


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

Message: 13
Date: Sat, 14 Jul 2012 08:55:06 -0700
From: "Patrick STODDARD (WD9EWK/VA7EWK)" <amsat-bb@xxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: DM23/DM24
Message-ID:
<CAN6TEUe7N6p2a1gMR=eNeb5Xw6NtDBe9Yh5eHKtZgVg5tu-gqA@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1

Hi Bob!

> Heard you FB here in FN34 Patrick, but couldn't get the old computer booted
> up fast enough to work you on FO-29.

It would have been nice to work you.  I was using my normal portable
SSB satellite setup - two FT-817NDs, Elk log periodic.  Hopefully we
can hook up on FO-29 or some other satellite.

73!





Patrick WD9EWK/VA7EWK
http://www.wd9ewk.net/


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

Message: 14
Date: Sat, 14 Jul 2012 12:32:12 -0500
From: Thomas Doyle <tomdoyle1948@xxxxx.xxx>
To: AMSAT-BB@xxxxx.xxx
Subject: [amsat-bb] W0PHD de W9KE
Message-ID:
<CAHnRQRKnufJAva93VCEy6SYqN5Fpc9yEx2L91sd+tTJcE3OmCQ@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1

 Heard you on the FO-29 pass around 17:20 utc today (Saturday). Good signal
on both CW and SSB. I tried calling you on both CW and SSB but no
luck. Thought you might want to know that your are getting into the sat.

73 W9KE Tom Doyle


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

_______________________________________________
Sent via amsat-bb@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT member? Join now to support the amateur satellite program!
http://amsat.org/mailman/listinfo/amsat-bb


End of AMSAT-BB Digest, Vol 7, Issue 222
****************************************


Read previous mail | Read next mail


 24.10.2024 08:18:49lGo back Go up