| |
CX2SA > SATDIG 13.03.13 20:02l 405 Lines 12519 Bytes #999 (0) @ WW
BID : AMSATBB883
Read: GUEST
Subj: AMSAT-BB-digest V8 83
Path: IZ3LSV<IK2XDE<ON4HU<CX2ACB<CX2SA
Sent: 130313/1902Z @:CX2SA.SAL.URY.SA #:4316 [Salto] FBB7.00e $:AMSATBB883
From: CX2SA@CX2SA.SAL.URY.SA
To : SATDIG@WW
Today's Topics:
1. Re: We-Wish decay (Nico Janssen)
2. Unix command line Kepler manager (PE0SAT | Amateur Radio)
3. Re: Unix command line Kepler manager (Gus)
4. Re: Unix command line Kepler manager (PE0SAT | Amateur Radio)
5. ISS digital packets (transbets@xxxxx.xxxx
6. Disregard my ISS packet question. I MADE IT IN!
(transbets@xxxxx.xxxx
7. Re: SatPC32 Update for Tone Control of Yaesu FT-857/897 (Alan)
----------------------------------------------------------------------
Message: 1
Date: Tue, 12 Mar 2013 20:51:13 +0100
From: Nico Janssen <hamsat@xxxxxx.xx>
To: Mike Rupprecht <mail@xxxxxxxxxxxxxx.xx>
Cc: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: We-Wish decay
Message-ID: <513F8731.8020301@xxxxxx.xx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Mike,
XATCobeo? Do you mean object 38082, 2012-006F? If this cubesat
continues to drop with its current decay rate, I don't expect it
to decay before the second half of 2015.
73,
Nico PA0DLO
On 2013-03-12 06:56, Mike Rupprecht wrote:
> Hi Nico,
>
> XATCobeo will be the next one - I think end of March.
>
> 73 Mike
> DK3WN
>
>
>
> Nico Janssen <hamsat@xxxxxx.xx> hat am 11. M?rz 2013 um 21:02 geschrieben:
>>
>> We-Wish decayed this morning, March 11, probably around 02:59 UTC near
>> 48 degrees North, 119 degrees East.
>>
>> Next cubesat TechEdSat 1 (38854, 1998-067CQ) will burn up in the
>> Earth's atmosphere, probably by the end of April.
>>
>> 73,
>> Nico PA0DLO
>>
>>
>> On 2013-03-10 14:30, Nico Janssen wrote:
>>>
>>> Solar activity has not increased. The decay of We_Wish may be expected
>>> on March 11 around 04:00 UTC (+/- 4 hours).
>>>
>>> The satellite is still transmitting.
>>>
>>> 73,
>>> Nico PA0DLO
>>>
>>>
>>> On 2013-03-08 15:54, Nico Janssen wrote:
>>>>
>>>> As solar activity will likely increase slightly in the coming days,
>>>> the decay of We-Wish may already occur on Sunday, March 10 (UTC).
>>>>
>>>> 73,
>>>> Nico PA0DLO
>>>>
>>>>
>>>> On 2013-03-05 20:58, Nico Janssen wrote:
>>>>> All,
>>>>>
>>>>> Cubesat We-Wish (38856, 1998-067CS) will soon burn up in the atmosphere.
>>>>> Probably the decay will occur on March 13. Of course this depends on how
>>>>> solar activity develops.
>>>>>
>>>>> 73,
>>>>> Nico PA0DLO
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>> _______________________________________________
>> 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
> _______________________________________________
> 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: 2
Date: Tue, 12 Mar 2013 22:29:05 +0100
From: PE0SAT | Amateur Radio <pe0sat@xxxxx.xx>
To: Amsat bb <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Unix command line Kepler manager
Message-ID: <7602b403b94b77259610495fa72177ac@xxxxx.xx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi,
Thanks for reading this message.
Can somebody help me with a command line Kepler manager for Unix?
The idea is to create my own TLE files where source files come from
Celes-track and
Space-track.
I thought to give the list a try before if go the script way ;)
73 Jan PE0SAT
--
With regards PE0SAT
Internet web-page http://www.pe0sat.vgnet.nl/
------------------------------
Message: 3
Date: Tue, 12 Mar 2013 18:22:37 -0400
From: Gus <8p6sm@xxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: Unix command line Kepler manager
Message-ID: <513FAAAD.7030903@xxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
What exactly do you need to do?
Download the elements from celestrack with wget or Perl's LWP::Simple.
Use grep with the --files option to select satellites of interest and
write them out to whatever destination you want. What else do you need?
A modest Perl script would go a long way...
On 03/12/2013 05:29 PM, PE0SAT | Amateur Radio wrote:
> Hi,
>
> Thanks for reading this message.
>
> Can somebody help me with a command line Kepler manager for Unix?
>
> The idea is to create my own TLE files where source files come from
> Celes-track and
> Space-track.
>
> I thought to give the list a try before if go the script way ;)
>
> 73 Jan PE0SAT
>
--
73, de Gus 8P6SM
Barbados, the easternmost isle.
------------------------------
Message: 4
Date: Wed, 13 Mar 2013 08:00:44 +0100
From: PE0SAT | Amateur Radio <pe0sat@xxxxx.xx>
To: Gus <8p6sm@xxxx.xxx>
Cc: Amsat bb <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: Unix command line Kepler manager
Message-ID: <7e081bf43f6625551adad108fe7f8522@xxxxx.xx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Gus,
As I mentioned "I thought to give the list a try before if go the
script way"
Do you have such a script?
Make an input variable with the desired SATS read from input files and
output to
my own output file that I can use with my favorite tracking software.
73 Jan PE0SAT
On 12-03-2013 23:22, Gus wrote:
> What exactly do you need to do?
>
> Download the elements from celestrack with wget or Perl's
> LWP::Simple. Use grep with the --files option to select satellites of
> interest and write them out to whatever destination you want. What
> else do you need?
>
> A modest Perl script would go a long way...
>
>
>
>
> On 03/12/2013 05:29 PM, PE0SAT | Amateur Radio wrote:
>> Hi,
>>
>> Thanks for reading this message.
>>
>> Can somebody help me with a command line Kepler manager for Unix?
>>
>> The idea is to create my own TLE files where source files come from
>> Celes-track and
>> Space-track.
>>
>> I thought to give the list a try before if go the script way ;)
>>
>> 73 Jan PE0SAT
>>
--
With regards PE0SAT
Internet web-page http://www.pe0sat.vgnet.nl/
------------------------------
Message: 5
Date: Wed, 13 Mar 2013 05:49:12 -0400
From: "transbets@xxxxx.xxxx <transbets@xxxxx.xxx>
To: Amsat-bb@xxxxx.xxx
Subject: [amsat-bb] ISS digital packets
Message-ID:
<CAA=qQdKahemDNKq=9JJiqwE-ta04n-fmvbC9ejiTV64Ey2SLQg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1
Hello all
I have recently been unsuccessful in sending digital packets to the ISS
since the change in radios on the station.
I use an Elk with my Yaesu VX8DR and the path I use is ARISS. I have
recently tried adding a WIDE to that path to see if I could get gated, but
have been largely unsuccessful except for one day, but haven't been able to
get back on, even with a relatively high pass.
Does anybody know if the path has changed since they are now using the
Ericsson instead of the Kenwood, or if there are any significant changes I
can make?. It could possibly be just the 5 watt HT can't do the job with
the Ericsson.
Any help appreciated. Thanks in advance.
73,
Elizabeth
WB3U
------------------------------
Message: 6
Date: Wed, 13 Mar 2013 08:12:03 -0400
From: "transbets@xxxxx.xxxx <transbets@xxxxx.xxx>
To: Amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Disregard my ISS packet question. I MADE IT IN!
Message-ID:
<CAA=qQdJPM4mYm4VKnA8NBHAwc22S5gqep8uxwVk9r4021qw-Rw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1
Hi all
Well, I made it onto the ISS this morning using my Elk on a 60+ degree
pass. It's all good, and thanks for reading my question. I shall now go
back to jumping around my living room in joy!
73,
Elizabeth (Betsy)
WB3U
------------------------------
Message: 7
Date: Wed, 13 Mar 2013 11:52:39 -0500
From: Alan <wa4sca@xxxxx.xxx>
To: "'Tom Deeble - KA6SIP'" <ka6sip@xxx.xxx>, <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: SatPC32 Update for Tone Control of Yaesu
FT-857/897
Message-ID: <4749600A29C143DFA6A68871816CE900@xxxxxx>
Content-Type: text/plain; charset="us-ascii"
Just found the patch Tom mentioned is now on the WWW.DK1TB.DE site.
73s and thanks to Erich,
Alan
WA4SCA
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Tom Deeble - KA6SIP
Sent: Tuesday, March 12, 2013 12:30 PM
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] SatPC32 Update for Tone Control of Yaesu FT-857/897
Recently I bought a new Yaesu FT-897D to replace a FT-817ND to give me a
little more xmit power when operating portable, but still using
internal batteries. When I tried to use SO-50 I found that I couldn't get
thru the sat. Back home I traced the problem to the CTCSS tone not
being set in the FT-897D via SatPC32 "T1" & "T2". My FT-817 worked without
a problem.
I contacted Erich Eichmann who quickly sent me a modified version to test.
It worked! Erich will be putting a patch version on his website
shortly: www.dk1tb.de See the English page and then Download page. I
thank Erich for making the change & so quickly - much quicker than
me in sending this to the AMSAT BB!
Detailed Description - for those interested:
The set CTCSS tone frequency is apparently the only CAT command that is
different for the FT-857/897 from the FT-817. The 5-byte
command for the FT-817 contains the tone frequency in bytes #1 & 2, and the
command Opcode "0B" in byte five. Bytes #3 & 4 are only
place holders and are set to ASCII code zero by the SatPC32 program. For
the FT-857/897 bytes #3 & 4 are used to set the receive CTCSS
tone frequency. Apparently even if the receive tone is not being used,
bytes #3 & 4 must contain a valid tone frequency. It looked like with
ASCII code zero in bytes #3 & 4 that the radio would interpret the command
as invalid and never set the Tx tone. There is no clarification of
this in the user manual. Erich has now sent the Tx tone in both the Tx tone
bytes and the Rx tone bytes (byte 1 = byte 3, byte 2 = byte 4).
This appears to correct the problem of tone not being set.
Now in SatPC32, for SO-50, when "T0" is clicked to get "T1", the CTCSS tone
of 67.0 is set in the FT-897 (as seen in Menu Mode 083). When
"T1" is clicked to get "T2" to enable SO-50, the CTCSS tone of 74.4 is set
in the radio (as seen in Menu Mode 083). When "T2" is clicked to get
"T0" for tone OFF, the CTCSS tone encoder is turned off but the tone of 74.4
still remains in Menu Mode 083 even though it is not being used.
So now the CTCSS tone control function in SatPC32 works on the FT-897 (and
should on the FT-857) just like it worked on the FT-817.
The CAT commands on all three radios to turn ON CTCSS encoding is (4A xx xx
xx xx 0A) and to turn OFF is (8A xx xx xx xx 0A). The tone
ON/OFF function always has worked for all three radios. On the FT-897 I
could see "TEN" on the display when the CTCSS tone encoder was
ON either "T1" & "T2" in SatPC32), and then "TEN" would disappear from the
display when the tone encoder was OFF ("T0" in SatPC32).
For testing the transmitted CTCSS tone I found that the "Tone Search
Scanning" function (tone decoder) built into the Yaesu VX-6R HT,
the FT-817ND and the FT-897D, worked well and was just what I needed!
Thanks again to Erich for a great program, his program support & support of
AMSAT!
73's - Tom, KA6SIP
Tom Deeble - KA6SIP
Mt. Diablo Amateur Radio Club Membership Chairman
ka6sip@xxx.xxx
PACIFICON - Oct 11-13, 2013
_______________________________________________
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
------------------------------
_______________________________________________
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 8, Issue 83
***************************************
Read previous mail | Read next mail
| |
