| |
CX2SA > SATDIG 12.03.13 21:01l 484 Lines 16927 Bytes #999 (0) @ WW
BID : AMSATBB882
Read: GUEST
Subj: AMSAT-BB-digest V8 82
Path: IZ3LSV<IK2XDE<ON4HU<CX2SA
Sent: 130312/1901Z @:CX2SA.SAL.URY.SA #:4285 [Salto] FBB7.00e $:AMSATBB882
From: CX2SA@CX2SA.SAL.URY.SA
To : SATDIG@WW
Today's Topics:
1. Re: We-Wish decay (Nico Janssen)
2. Re: Satellite hit by debris from weapon test (Alan)
3. Re: Satellite hit by debris from weapon test (Robert Coppock)
4. FW: Satellite hit by debris from weapon test (Robert Coppock)
5. Re: Satellite hit by debris from weapon test (Nitin Muttin)
6. Re: We-Wish decay (Mike Rupprecht)
7. Re: Satellite hit by debris from weapon test (Gus)
8. SatPC32 Update for Tone Control of Yaesu FT-857/897
(Tom Deeble - KA6SIP)
9. Re: SatPC32 Update for Tone Control of Yaesu FT-857/897 (Alan)
----------------------------------------------------------------------
Message: 1
Date: Mon, 11 Mar 2013 21:02:35 +0100
From: Nico Janssen <hamsat@xxxxxx.xx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: We-Wish decay
Message-ID: <513E385B.8050006@xxxxxx.xx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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
>>
>>
------------------------------
Message: 2
Date: Mon, 11 Mar 2013 15:46:08 -0500
From: Alan <wa4sca@xxxxx.xxx>
To: "'Dennis Griffin'" <eagleeyedennis@xxxxx.xxx>,
<amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: Satellite hit by debris from weapon test
Message-ID: <8AC034311F6B4CEAB945B98A63A2944B@xxxxxx>
Content-Type: text/plain; charset="us-ascii"
Dennis,
Dashboard cameras. OK, you asked a serious question, but I couldn't resist.
The real answer is that it comes down to an array of radars, and lots of
computing power at Space Command, or other similar agencies. Ordinary
launches are fairly obvious, as are the "dropped" gloves, tool kits,
washers, etc from the ISS or other such operations. They track these, and
can predict close approaches very accurately. We get close approach
warnings periodically for AMSAT spacecraft.
In this case, it was the remains of a weapons test. That is a lot messier.
All the debris radiates outward from the initial impact/explosion, and there
are often large numbers of them. The source can be identified since the
debris can be projected/calculated backward in time to the initial point.
After that, it is just a matter of continuous updates over the years.
73s,
Alan
WA4SCA
------------------------------
Message: 3
Date: Mon, 11 Mar 2013 16:32:10 -0700
From: Robert Coppock <robertinorbit@xxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: Satellite hit by debris from weapon test
Message-ID: <SNT131-W33B727E2E48E56126D4341A0E10@xxx.xxx>
Content-Type: text/plain; charset="iso-8859-1"
i heard on the medford,OR news that a guy waskilled on I-5 by a wrong way,
drunk driver. theunfortunate driver was from oakland, OR. i recallan amsat
guy from there, cannot remember his nameor call. anyone know if he is ok ?
are you out there ? k f 0 g cn81 73 ~too bz for ham radio
lately, sorry.
------------------------------
Message: 4
Date: Mon, 11 Mar 2013 16:40:08 -0700
From: Robert Coppock <robertinorbit@xxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] FW: Satellite hit by debris from weapon test
Message-ID: <SNT131-W321B3217899192C339AEF1A0E10@xxx.xxx>
Content-Type: text/plain; charset="iso-8859-1"
now i remember, Wayne Estes ? i thinkFrom: robertinorbit@xxxxx.xxx
To: amsat-bb@xxxxx.xxx
Subject: Re: Satellite hit by debris from weapon test
Date: Mon, 11 Mar 2013 16:32:10 -0700
i heard on the medford,OR news that a guy was
killed on I-5 by a wrong way, drunk driver. the
unfortunate driver was from oakland, OR. i recall
an amsat guy from there, cannot remember his name
or call. anyone know if he is ok ? are you out there ?
k f 0 g cn81 73
~too bz for ham radio lately, sorry.
------------------------------
Message: 5
Date: Tue, 12 Mar 2013 11:17:20 +0800 (SGT)
From: Nitin Muttin <vu3tyg@xxxxx.xx.xx>
To: Amsat - B Bs <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: Satellite hit by debris from weapon test
Message-ID:
<1363058240.63920.YahooMailNeo@xxxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=iso-8859-1
I have always found the informaton shared by Trevor interesting and
informative and I waterfall such?information?on the amsatindia group and
many have appreciated the content shared. Thanks Trevor for taking the time
and effort to bring such information to us.
?
73
Nitin [VU3TYG]
------------------------------
Message: 6
Date: Tue, 12 Mar 2013 06:56:29 +0100 (CET)
From: Mike Rupprecht <mail@xxxxxxxxxxxxxx.xx>
To: amsat-bb@xxxxx.xxxx Nico Janssen <hamsat@xxxxxx.xx>
Subject: [amsat-bb] Re: We-Wish decay
Message-ID:
<456861659.1087611.1363067789751.JavaMail.open-xchange@xxxxxxxxxxxx.xxxxxx.xx>
Content-Type: text/plain; charset=UTF-8
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
------------------------------
Message: 7
Date: Tue, 12 Mar 2013 02:03:12 -0400
From: Gus <8p6sm@xxxx.xxx>
To: Trevor M5AKA <m5aka@xxxxx.xx.xx>
Cc: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: Satellite hit by debris from weapon test
Message-ID: <513EC520.1060506@xxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I've got no problem with Trevor's posts. I would prefer they continue
rather than stop.
But for those who AREN'T interested, perhaps Trevor could add some
easily recognizable mark to the news posts, to make it easier to filter
them out while not blocking his other posts? Like adding FYI:: to the
subject or something?
If Trevor decides to do something like that to accommodate those who
don't want the news, they should consider that he is paying them a
courtesy. If it were me, I sure wouldn't bother.
--
73, de Gus 8P6SM
Barbados, the easternmost isle.
------------------------------
Message: 8
Date: Tue, 12 Mar 2013 13:29:58 -0400 (EDT)
From: Tom Deeble - KA6SIP <ka6sip@xxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] SatPC32 Update for Tone Control of Yaesu
FT-857/897
Message-ID: <8CFED5E5A075CAD-37C-69DD@xxxxxxxxxxxx.xxxxxx.xxx.xxx>
Content-Type: text/plain; charset="us-ascii"
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
------------------------------
Message: 9
Date: Tue, 12 Mar 2013 13:06:01 -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: <CFE2F4C1CF9C407D92E3E81044A875ED@xxxxxx>
Content-Type: text/plain; charset="us-ascii"
Tom,
Congratulations on the local detective work. Thanks for posting this, and as
always, to Erich for his remarkable level of support!
73s,
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 82
***************************************
Read previous mail | Read next mail
| |
