| |
CX2SA > SATDIG 19.12.13 19:43l 1039 Lines 31874 Bytes #999 (0) @ WW
BID : AMSATBB8464
Read: GUEST
Subj: AMSAT-BB-digest V8 464
Path: IZ3LSV<IK2XDE<DB0RES<DB0ANF<CX2SA
Sent: 131219/1838Z @:CX2SA.SAL.URY.SA #:1614 [Salto] FBB7.00e $:AMSATBB8464
From: CX2SA@CX2SA.SAL.URY.SA
To : SATDIG@WW
Today's Topics:
1. help with cape ii (Roland Zurmely)
2. CAPE-2 (PY5LF)
3. Re: Object IDs (Ted)
4. SO-50's ELEVENTH Birthday! (Clint Bradford)
5. SO-50's ELEVENTH Birthday! (Mani)
6. Adding AO-73 to SATPC32 and Nova for Windows (Les Rayburn)
7. Re: Adding AO-73 to SATPC32 and Nova for Windows (Alan)
8. DSTAR NET (wa4hfn@xxxxxxx.xxxx
9. Re: Adding AO-73 to SATPC32 and Nova for Windows
(Dave Webb KB1PVH)
10. Delfi-n3Xt Update December 19 + UK CubeSat Forum (M5AKA)
11. Re: Object IDs (Nico Janssen)
12. Re: Confirm Message (Moderator please help??) (Joe Leikhim)
----------------------------------------------------------------------
Message: 1
Date: Wed, 18 Dec 2013 12:45:30 -0800 (PST)
From: Roland Zurmely <py4zbz@xxxxx.xxx>
To: AMSAT <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] help with cape ii
Message-ID:
<1387399530.82606.YahooMailNeo@xxxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=iso-8859-1
Today I gave several commands to set green mode, but he
remained in pink ...?
He also responded to a Send Text to Spech?command:
http://www.qsl.net/py4zbz/cape.htm#e
73 de Roland PY4ZBZ.
------------------------------
Message: 2
Date: Wed, 18 Dec 2013 19:41:12 -0200
From: "PY5LF" <py5lf@xxxxxxxxxxxxx.xxx.xx>
To: <AMSAT-BB@xxxxx.xxx>
Subject: [amsat-bb] CAPE-2
Message-ID: <011901cefc39$e0b1d7d0$a2158770$@xxxxxxxxxxxxx.xxx.xx>
Content-Type: text/plain; charset="us-ascii"
Hi
Cape-2 heard today 12:30 UTC over Brazil .
https://www.youtube.com/watch?v=hcGMqaa8BPo
73
PY5LF
Luciano Fabricio
Curitiba-PR-BR GG54jm
http://www.qrz.com/db/PY5LF
------------------------------
Message: 3
Date: Wed, 18 Dec 2013 15:44:15 -0800
From: "Ted" <k7trkradio@xxxxxxx.xxx>
To: "'Rick Tejera'" <saguaroastro@xxx.xxx>, "'Nico Janssen'"
<hamsat@xxxxxx.xx>, "'Mike Rupprecht'" <mail@xxxxxxxxxxxxxx.xx>,
<amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: Object IDs
Message-ID: <005b01cefc4b$105bc700$31135500$@xxx>
Content-Type: text/plain; charset="iso-8859-1"
The Fun Cube site seems to be making every effort to provide timely info.
Logic would suggest checking that site daily. Updated info on tle's is there
in plain view
GL, Ted
K7TRK
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Rick Tejera
Sent: Wednesday, December 18, 2013 7:15 AM
To: 'Nico Janssen'; 'Mike Rupprecht'; amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: Object IDs
I'd thought that AO-73 had been confirmed as object 66B. has this been
refined? I guess I need to update my settings in SATpc
Rick Tejera
Saguaro Astronomy Club
www.saguaroastro.org
Thunderbird Amateur radio Club (K7TEJ)
www.w7tbc.org
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Nico Janssen
Sent: Wednesday, December 18, 2013 7:00 AM
To: Mike Rupprecht; amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: Object IDs
Hi Mike,
Thanks for the confirmation of the 'tbc's.
This picture shows the measured doppler curve of an overhead evening pass of
OSCAR 73, plotted against the calculated curves for objects
39444 and 39445. These objects were about 11 s apart (i.e. about 82 km).
https://thumb5.wuala.com/previewImage/SharedInfo/Space/AO73_20131216.jpg/?ke
y=IZKufoz9U1Uo
Note the temperature related frequency drift on the beacon transmitter,
which causes frequency deviations when using automatic doppler correction.
To be able to create useful doppler curves it would help if all Cubesats
would transmit a *continuous* carrier signal on a
*constant* frequency... ;-)
Still a lot of IDs are unknown. Of all the objects from the Minotaur launch,
only three are officially identified:
39380 2013-064A STPSat 3
39388 2013-064J SENSE SV1
39392 2013-064N SENSE SV2
It is suggested that Cape 2 is object 39382 (2013-064C) and that KySat 2 is
object 39383 (2013-064D). These are to be confirmed.
73,
Nico PA0DLO
On 2013-12-17 22:13, Mike Rupprecht wrote:
> Thanks Nico, PA0DLO for pointing me in the rigth direction. I agree
> with you the TLE for the cubesats:
>
> 39436 2013-066W Eagle 2 ($50Sat) ok
> 39438 2013-066Y Velox PII ok
> 39439 2013-066Z First-MOVE ok
> 39440 2013-066AA CubeBug 2 ok
> 39444 2013-066AE AMSAT-OSCAR ok :-)
> 39445 2013-066AF HiNCube ?
> 39446 2013-066AG UWE 3 ok
>
> Just made a deep analysis with the FunCube TLE (Object AE vs. AF). The
> pass was not very high but every seconds I switched between the TLE AE
> and
AF.
> You can see a slightly differnce (only a few Hz) at TCA what leads me
> to say
> - your're right. FUNCube-1 seems indeed to be Object AE.
>
> http://www.dk3wn.info/p/?p=39682
>
>
> 73 Mike
> DK3WN
>
> -----Urspr?ngliche Nachricht-----
> Von: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx Im
> Auftrag von Nico Janssen
> Gesendet: Dienstag, 17. Dezember 2013 14:32
> An: amsat-bb@xxxxx.xxx
> Betreff: [amsat-bb] Re: Object IDs
>
> All,
>
> Further doppler measurements show that TshepisoSat (aka ZACube 1) is
> object
> 39417 (2013-066B) and AMSAT-OSCAR 73 (aka FUNCube 1) is object
> 39444 (2013-066AE). Therefore HiNCube must be object 39445 (2013-066AF).
>
> It is not easy to get a good doppler curve with many Cubesats because
> of the limited transmissions and because of the frequency drift of
> their beacon transmitters.
>
> These object IDs from the Dnepr launch seem to be correct, although
> some still need to be confirmed (tbc):
>
> 39416 2013-066A Aprizesat 7
> 39417 2013-066B TshepisoSat
> 39418 2013-066C Skysat 1
> 39419 2013-066D Dubaisat 2
> 39421 2013-066F Unisat 5
> 39422 2013-066G STSat 3
> 39423 2013-066H WNISat 1
> 39425 2013-066K Aprizesat 8
> 39427 2013-066M Triton 1
> 39428 2013-066N Delfi-n3Xt
> 39429 2013-066P Dove 3
> 39430 2013-066Q GomX 1
> 39431 2013-066R BRITE-PL
> 39432 2013-066S HumSat D (tbc)
> 39436 2013-066W Eagle 2 ($50Sat) (tbc)
> 39438 2013-066Y Velox PII (tbc)
> 39439 2013-066Z First-MOVE (tbc)
> 39440 2013-066AA CubeBug 2 (tbc)
> 39444 2013-066AE AMSAT-OSCAR 73
> 39445 2013-066AF HiNCube
> 39446 2013-066AG UWE 3 (tbc)
>
> 73,
> Nico PA0DLO
>
>
> On 2013-12-01 16:25, Nico Janssen wrote:
>> All,
>>
>> An update on the satellite IDs.
>>
>> Still no IDs are available for the satellites launched from the ISS
>> (except TechEdSat 3P) and the Minotaur.
>>
>> Several IDs have been published for the objects from the Dnepr launch
>> but many need to be confirmed. Still not all TLEs are released.
>>
>> AMSAT-OSCAR 73, ZACube 1 and HiNCube were launched from the same ISIPOD.
>> As they initially were close together, the JSpOC decided to release
>> only one TLE set for this cluster under object number 39417
>> (2013-066B). Now the distances between these satellites are slowly
>> increasing. So the question is which satellite is object 39417.
>> Detailed doppler measurements show that ZACube 1 is now about 25 s
>> early compared to the TLE for object 39417, while OSCAR 73 is about
>> 11 s early. This seems to indicate that object 39417 is actually HiNCube.
>> Hopefully TLEs for OSCAR 73 and ZACube 1 will be published soon.
>>
>> 73,
>> Nico PA0DLO
>>
>>
>> On 2013-11-23 11:32, Nico Janssen wrote:
>>> All,
>>>
>>> An overview of the presently known IDs for the satellites that have
>>> been launched recently.
>>>
>>> ISS JSSOD Cubesat launches
>>> 2013-11-19 12:18 UTC
>>> 39412 1998-067DA Pico Dragon ?
>>> 39413 1998-067DB ArduSat 1 ?
>>> 39414 1998-067DC ArduSat X ?
>>> To be confirmed when the objects have more separation.
>>> 2013-11-20 07:58 UTC
>>> 39415 1998-067DD TechEdSat 3P
>>>
>>> Minotaur 1, Wallops Flight Facility
>>> 2013-11-20 01:15 UTC
>>> ORS3 & ELaNa 4: 29 satellites
>>> So far only 4 TLEs published. No IDs yet but probably:
>>> 39380 2013-064A STPSat 3
>>>
>>> Dnepr, Yasny
>>> 2013-11-21 07:10:11 UTC
>>> 32 satellites
>>> 19 TLEs published
>>> 39417 2013-066B FUNcube 1
>>> 39427 2013-066M Triton 1
>>> 39428 2013-066N Delfi-n3Xt
>>>
>>> Note that all designations may change later on.
>>>
>>> 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: 4
Date: Wed, 18 Dec 2013 17:45:47 -0800
From: Clint Bradford <clintbradford@xxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] SO-50's ELEVENTH Birthday!
Message-ID: <6398D3A4-EF6E-450B-AEFB-5C6F466EE419@xxx.xxx>
Content-Type: text/plain; charset=us-ascii
It is SO-50's ELEVENTH birthday! Read on for how YOU can celebrate!
Now known as SO-50, Saudisat 1C is a Saudi Arabian picosatellite that
was launched by a Dnepr rocket from Baikonur at 17:00 UT on December 20,
2002. SO-50 features a "Mode J" FM amateur repeater operating on a 2M
uplink and a 440 downlink.
"Most hams already own the necessary equipment to work SO-50," reports
Clint Bradford, K6LCS, who maintains a Web site devoted to working amateur
satellites with minimal equipment (http://www.work-sat.com).
"It is preferable to work SO-50 in true, full-duplex mode - so you can hear
the
downlink as you transmit. This means - for most - using a second radio or
the Kenwood TH-D72A and its true full-duplex capability. The new Puxing
PX-UV973 is currently being tested in this mode, too, to see how it works on
the satellites."
SO-50's repeater is available to amateurs worldwide, and it uses a 67.0 Hertz
PL tone on the uplink. SO-50 also has a 10 minute timer that must be armed
before use. If you know the satellite is there - but there is nothing heard
- you
may need to shoot it a PL tone of 74.4 to turn it ON!
The repeater consists of a miniature VHF receiver with sensitivity of -124dBm,
with an IF bandwidth of 15 KHz. The receive antenna is a 1/4 wave vertical
mounted in the top corner of the spacecraft. Its UHF transmitter is a mere 250
mW, and downlink antenna is a 1/4 wave mounted in the bottom corner of the
spacecraft and canted at 45 degrees inward.
"Hams just with Technician licenses can work the satellite," Clint
continues. "We
are talking about weak signals from 500 miles away - so improving both your
TX and RX antennas is critical for success on this satellite." Plans for
making tape
measure beams and other inexpensive, high-gain antennas is also on his Web
site.
"Do not forget to accommodate for the Doppler phenomenon on the 440 receive
side."
Complete details - including frequency chart and sources for knowing when the
satellite will be over your area, are also on Clint's Web site.
/end/
------------------------------
Message: 5
Date: Thu, 19 Dec 2013 07:56:15 +0530
From: Mani <wmy@xxxx.xxx.xx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] SO-50's ELEVENTH Birthday!
Message-ID: <201312190226.rBJ2Q92c011490@xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed"
Happy Birthday wishes and Greetings to SO-50. Good wishes for a long
and healthy life. May the fruitful services of SO-50 be available for
very long.
73 de
Mani [VU2WMY/KJ6LRS]
Director, Educational Relations
AMSAT-India
No:201, 2nd Main Road
Mahalakshmi Layout
Bangalore-560 086
Phone:(Office)91-80-25082598/25082054/25082192
Mobile: 91-9880 341 456
E-mail ID: wmy@xxxx.xxx.xx
vu2wmy_mani@xxxxx.xxx
isrohams@xxxxx.xxx
------------------------------------------------------------------------------
Confidentiality Notice: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
------------------------------------------------------------------------------
------------------------------
Message: 6
Date: Thu, 19 Dec 2013 03:11:00 -0600
From: Les Rayburn <les@xxxxxxxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Adding AO-73 to SATPC32 and Nova for Windows
Message-ID: <52B2B824.1020204@xxxxxxxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I've been off the air since before Thanksgiving, due to an impossible
work and personal schedule. Things are slowing down now, and I'd really
like to work some contacts through A0-73. Can someone walk me through
adding A0-73 to SATPC32? I'd like to keep it within the group of
satellites that are in the "amateur.txt" Kep file if possible.
Ditto for adding it to Nova for Windows. I know that someone posted
instructions like this shortly after the satellite was launched, but it
appears that the object number and keps may be out of date now? I'd like
to install the new bird with the latest information.
Thanks for helping the newbie!
--
--
73,
Les Rayburn, N1LF
121 Mayfair Park
Maylene, AL 35114
EM63nf
6M VUCC #1712
AMSAT #38965
Grid Bandits #222
Southeastern VHF Society
Central States VHF Society Life Member
Six Club #2484
Active on 6 Meters thru 1296, 10GHz & Light
------------------------------
Message: 7
Date: Thu, 19 Dec 2013 07:38:46 -0600
From: Alan <wa4sca@xxxxx.xxx>
To: <les@xxxxxxxxxxxx.xxx>, <amsat-bb@xxxxx.xxx>
Cc: CC <APBIDDLE@xxxxxx.xxx>
Subject: [amsat-bb] Re: Adding AO-73 to SATPC32 and Nova for Windows
Message-ID: <3227FFEAD8A5472088566C1798B4E2DF@xxxxxx>
Content-Type: text/plain; charset="us-ascii"
Les,
Remember that the Keps are provided from CelesTrak. SatPC32 does not
control which source file
contains a particular satellite. New satellites normally move over to the
regular categories in about
30 days.
You can find a discussion of adding satellites to SatPC32 and NfW here:
http://amsat-uk.org/2013/11/23/adding-new-satellites-to-satpc32/
73s,
Alan
WA4SCA
<-----Original Message-----
<From: amsat-bb-bounces@xxxxx.xxx
<[mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of Les Rayburn
<Sent: Thursday, December 19, 2013 3:11 AM
<To: amsat-bb@xxxxx.xxx
<Subject: [amsat-bb] Adding AO-73 to SATPC32 and Nova for Windows
<
<I've been off the air since before Thanksgiving, due to an impossible
<work and personal schedule. Things are slowing down now, and
<I'd really
<like to work some contacts through A0-73. Can someone walk me through
<adding A0-73 to SATPC32? I'd like to keep it within the group of
<satellites that are in the "amateur.txt" Kep file if possible.
<
<Ditto for adding it to Nova for Windows. I know that someone posted
<instructions like this shortly after the satellite was
<launched, but it
<appears that the object number and keps may be out of date
<now? I'd like
<to install the new bird with the latest information.
<
<Thanks for helping the newbie!
<
<
<--
<--
<73,
<
<Les Rayburn, N1LF
<121 Mayfair Park
<Maylene, AL 35114
<EM63nf
<
<6M VUCC #1712
<AMSAT #38965
<Grid Bandits #222
<Southeastern VHF Society
<Central States VHF Society Life Member
<Six Club #2484
<
<Active on 6 Meters thru 1296, 10GHz & Light
<
<_______________________________________________
<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: Thu, 19 Dec 2013 14:28:26 +0000 (UTC)
From: wa4hfn@xxxxxxx.xxx
To: AMSAT <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] DSTAR NET
Message-ID:
<1414622628.259835.1387463306119.JavaMail.root@xxxxxxx.xxxxxxxxxxx.xx.xxxx.xxx
xxxx.xxx>
Content-Type: text/plain; charset=utf-8
Hello all D STAR AMSAT users net tonight @ 0200 UTC on REF60B.DX Stations
welcomed.
Merry Christmas WA4HFN Damon EM55
------------------------------
Message: 9
Date: Thu, 19 Dec 2013 09:37:25 -0500
From: Dave Webb KB1PVH <kb1pvh@xxxxx.xxx>
To: Les Rayburn <les@xxxxxxxxxxxx.xxx>
Cc: AMSAT -BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: Adding AO-73 to SATPC32 and Nova for Windows
Message-ID:
<CAEMY9FdQctt9dW_vL18x6E4ecnNacS-JiHv+CaA+W_DF5g6_6Q@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1
Les,
I usually copy the keps I want from the tle-new file and paste them into
the amateur keps file. The only problem with doing it that way is that you
will have to manually add it every time you update your keps.
Dave-KB1PVH
Sent from my Verizon Wireless Droid RAZR
------------------------------
Message: 10
Date: Thu, 19 Dec 2013 14:51:37 +0000 (GMT)
From: M5AKA <m5aka@xxxxx.xx.xx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Delfi-n3Xt Update December 19 + UK CubeSat Forum
Message-ID:
<1387464697.38216.YahooMailNeo@xxxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=utf-8
Delfi-n3Xt Update December 19 - Frequency change
http://amsat-uk.org/2013/12/19/delfi-n3xt-update-december-19/
Also on the AMSAT-UK site:
Announcing: The UK CubeSat Forum
http://amsat-uk.org/2013/12/19/announcing-the-uk-cubesat-forum/
11th birthday of ham radio satellite SO-50
http://amsat-uk.org/2013/12/19/11th-birthday-of-ham-radio-satellite-so-50/
Radio Hams to Repair Faulty ISS Pump
http://amsat-uk.org/2013/12/18/radio-hams-to-repair-faulty-iss-pump/
How high-altitude balloon missions stay on track
http://amsat-uk.org/2013/12/18/how-high-altitude-balloon-missions-stay-on-trac
k/
----
73 Trevor M5AKA
AMSAT-UK website http://amsat-uk.org/
Facebook https://www.facebook.com/pages/AMSAT-UK/208113275898396
Twitter https://twitter.com/AMSAT_UK
----
------------------------------
Message: 11
Date: Thu, 19 Dec 2013 18:43:13 +0100
From: Nico Janssen <hamsat@xxxxxx.xx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: Object IDs
Message-ID: <52B33031.5020200@xxxxxx.xx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Another ID can now be added to the list:
39433 2013-066T HumSat D
73,
Nico PA0DLO
On 2013-12-18 17:07, Mike Rupprecht wrote:
> Hi Nico,
>
> Thanks. I use #39388 (Object J) for KySat-2 and 393882 (Object C) for
> CAPE-2.
>
> 73 Mike
> DK3WN
>
> -----Urspr?ngliche Nachricht-----
> Von: Nico Janssen [mailto:hamsat@xxxxxx.xxx
> Gesendet: Mittwoch, 18. Dezember 2013 15:00
> An: Mike Rupprecht; amsat-bb@xxxxx.xxx
> Betreff: Re: [amsat-bb] Re: Object IDs
>
> Hi Mike,
>
> Thanks for the confirmation of the 'tbc's.
>
> This picture shows the measured doppler curve of an overhead evening pass of
> OSCAR 73, plotted against the calculated curves for objects
> 39444 and 39445. These objects were about 11 s apart (i.e. about 82 km).
>
> https://thumb5.wuala.com/previewImage/SharedInfo/Space/AO73_20131216.jpg/?ke
> y=IZKufoz9U1Uo
>
> Note the temperature related frequency drift on the beacon transmitter,
> which causes frequency deviations when using automatic doppler correction.
> To be able to create useful doppler curves it would help if all Cubesats
> would transmit a *continuous* carrier signal on a
> *constant* frequency... ;-)
>
> Still a lot of IDs are unknown. Of all the objects from the Minotaur launch,
> only three are officially identified:
>
> 39380 2013-064A STPSat 3
> 39388 2013-064J SENSE SV1
> 39392 2013-064N SENSE SV2
>
> It is suggested that Cape 2 is object 39382 (2013-064C) and that KySat 2 is
> object 39383 (2013-064D). These are to be confirmed.
>
> 73,
> Nico PA0DLO
>
>
> On 2013-12-17 22:13, Mike Rupprecht wrote:
>> Thanks Nico, PA0DLO for pointing me in the rigth direction. I agree
>> with you the TLE for the cubesats:
>>
>> 39436 2013-066W Eagle 2 ($50Sat) ok
>> 39438 2013-066Y Velox PII ok
>> 39439 2013-066Z First-MOVE ok
>> 39440 2013-066AA CubeBug 2 ok
>> 39444 2013-066AE AMSAT-OSCAR ok :-)
>> 39445 2013-066AF HiNCube ?
>> 39446 2013-066AG UWE 3 ok
>>
>> Just made a deep analysis with the FunCube TLE (Object AE vs. AF). The
>> pass was not very high but every seconds I switched between the TLE AE and
> AF.
>> You can see a slightly differnce (only a few Hz) at TCA what leads me
>> to say
>> - your're right. FUNCube-1 seems indeed to be Object AE.
>>
>> http://www.dk3wn.info/p/?p=39682
>>
>>
>> 73 Mike
>> DK3WN
>>
>> -----Urspr?ngliche Nachricht-----
>> Von: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx Im
>> Auftrag von Nico Janssen
>> Gesendet: Dienstag, 17. Dezember 2013 14:32
>> An: amsat-bb@xxxxx.xxx
>> Betreff: [amsat-bb] Re: Object IDs
>>
>> All,
>>
>> Further doppler measurements show that TshepisoSat (aka ZACube 1) is
>> object
>> 39417 (2013-066B) and AMSAT-OSCAR 73 (aka FUNCube 1) is object
>> 39444 (2013-066AE). Therefore HiNCube must be object 39445 (2013-066AF).
>>
>> It is not easy to get a good doppler curve with many Cubesats because
>> of the limited transmissions and because of the frequency drift of
>> their beacon transmitters.
>>
>> These object IDs from the Dnepr launch seem to be correct, although
>> some still need to be confirmed (tbc):
>>
>> 39416 2013-066A Aprizesat 7
>> 39417 2013-066B TshepisoSat
>> 39418 2013-066C Skysat 1
>> 39419 2013-066D Dubaisat 2
>> 39421 2013-066F Unisat 5
>> 39422 2013-066G STSat 3
>> 39423 2013-066H WNISat 1
>> 39425 2013-066K Aprizesat 8
>> 39427 2013-066M Triton 1
>> 39428 2013-066N Delfi-n3Xt
>> 39429 2013-066P Dove 3
>> 39430 2013-066Q GomX 1
>> 39431 2013-066R BRITE-PL
>> 39432 2013-066S HumSat D (tbc)
>> 39436 2013-066W Eagle 2 ($50Sat) (tbc)
>> 39438 2013-066Y Velox PII (tbc)
>> 39439 2013-066Z First-MOVE (tbc)
>> 39440 2013-066AA CubeBug 2 (tbc)
>> 39444 2013-066AE AMSAT-OSCAR 73
>> 39445 2013-066AF HiNCube
>> 39446 2013-066AG UWE 3 (tbc)
>>
>> 73,
>> Nico PA0DLO
>>
>>
>> On 2013-12-01 16:25, Nico Janssen wrote:
>>> All,
>>>
>>> An update on the satellite IDs.
>>>
>>> Still no IDs are available for the satellites launched from the ISS
>>> (except TechEdSat 3P) and the Minotaur.
>>>
>>> Several IDs have been published for the objects from the Dnepr launch
>>> but many need to be confirmed. Still not all TLEs are released.
>>>
>>> AMSAT-OSCAR 73, ZACube 1 and HiNCube were launched from the same ISIPOD.
>>> As they initially were close together, the JSpOC decided to release
>>> only one TLE set for this cluster under object number 39417
>>> (2013-066B). Now the distances between these satellites are slowly
>>> increasing. So the question is which satellite is object 39417.
>>> Detailed doppler measurements show that ZACube 1 is now about 25 s
>>> early compared to the TLE for object 39417, while OSCAR 73 is about
>>> 11 s early. This seems to indicate that object 39417 is actually HiNCube.
>>> Hopefully TLEs for OSCAR 73 and ZACube 1 will be published soon.
>>>
>>> 73,
>>> Nico PA0DLO
>>>
>>>
>>> On 2013-11-23 11:32, Nico Janssen wrote:
>>>> All,
>>>>
>>>> An overview of the presently known IDs for the satellites that have
>>>> been launched recently.
>>>>
>>>> ISS JSSOD Cubesat launches
>>>> 2013-11-19 12:18 UTC
>>>> 39412 1998-067DA Pico Dragon ?
>>>> 39413 1998-067DB ArduSat 1 ?
>>>> 39414 1998-067DC ArduSat X ?
>>>> To be confirmed when the objects have more separation.
>>>> 2013-11-20 07:58 UTC
>>>> 39415 1998-067DD TechEdSat 3P
>>>>
>>>> Minotaur 1, Wallops Flight Facility
>>>> 2013-11-20 01:15 UTC
>>>> ORS3 & ELaNa 4: 29 satellites
>>>> So far only 4 TLEs published. No IDs yet but probably:
>>>> 39380 2013-064A STPSat 3
>>>>
>>>> Dnepr, Yasny
>>>> 2013-11-21 07:10:11 UTC
>>>> 32 satellites
>>>> 19 TLEs published
>>>> 39417 2013-066B FUNcube 1
>>>> 39427 2013-066M Triton 1
>>>> 39428 2013-066N Delfi-n3Xt
>>>>
>>>> Note that all designations may change later on.
>>>>
>>>> 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: 12
Date: Thu, 19 Dec 2013 13:34:11 -0500
From: Joe Leikhim <rhyolite@xxxxxxx.xxx>
To: Bruce <kk5do@xxxxx.xxx>, "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: Confirm Message (Moderator please help??)
Message-ID: <52B33C23.8040304@xxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Bruce;
I sent a message to paul, but no answer. Not even sure any messages from
amsat.org are getting to me at all.
On 12/16/2013 5:45 PM, Bruce wrote:
> might you deal with the administrator, paul, kb5mu. i am sure talking
> with him might be more fruitful than a lot of messages back and forth
> on the amsat-bb.
>
> i am sure all it takes is one spam message sent to the bb and the
> domain will be caught and treated as a spam site.
>
> 73...bruce
>
> Sent from Yahoo Mail for iPhone <http://overview.mail.yahoo.com?.src=iOS>
>
>
> ------------------------------------------------------------------------
> *From: * Joe Leikhim <rhyolite@xxxxxxx.xxx>;
> *To: * <APBIDDLE@xxxxxxx.xxx>; <amsat-bb@xxxxx.xxx>;
> *Subject: * [amsat-bb] Re: Confirm Message (Moderator please help??)
> *Sent: * Mon, Dec 16, 2013 9:44:17 PM
>
> I am still not receiving daily digests since Nov 26. Apparently
> SPAMCOP has blacklisted it repeatedly. Who is the adminstrator for
> AMSAT.ORG?
>
> -----
> www.amsat.org Whois: ISP University of California, San Diego
>
> 169.228.66.5 listed in bl.spamcop.net (127.0.0.2)
>
> If there are no reports of ongoing objectionable email from this
> system it will be delisted automatically in approximately 23 hours.
>
> Causes of listing
>
> * System has sent mail to SpamCop spam traps in the past week (spam
> traps are secret, no reports or evidence are provided by SpamCop)
> * SpamCop users have reported system as a source of spam less than 10
> times in the past week
>
> Additional potential problems
> (these factors do not directly result in spamcop listing)
>
> * Too many delisting requests were made. Next request might be allowed
> after 5.0 days
>
> Because of the above problems, express-delisting is not available
> Listing History
> In the past 20.1 days, it has been listed 6 times for a total of 18.4 days
> Dispute Listing
> If you are the administrator of this system and you are sure this
> listing is erroneous, you may request that we review the listing.
> Because everyone wants to dispute their listing, regardless of merit,
> we reserve the right to ignore meritless disputes.
> Dispute listing of 169.228.66.5
> <http://www.spamcop.net/w3m?action=dispute;ip=169.228.66.5>
>
> -----
>
> On 12/15/2013 6:42 AM, Alan wrote:
> > Joe,
> >
> > This is a problem which has been around for some time, and is
> getting worse. Small ISPs, and some
> > larger ones, use spam control programs such as Spam Cop and Iron
> Key. They have various ways of
> > detecting spam sources, and these are blocked at the ISP level, so
> you never see the messages sent to
> > you. Unfortunately they block entire domains, such as AMSAT.ORG,
> usually for 24 hours unless the
> > block is reset. If your ISP is blocked, you have about a 50-50
> chance of getting a bounce message
> > when you send a message.
> >
> > I have to get my internet from a small rural phone company, and
> eventually had to give up on using
> > their email. Their domain was frequently blocked, so I never knew
> whether email would go through.
> > When I found out about a problem, I could contact their tech people
> who were good about fixing it, but
> > the same thing might happen the next day. I finally moved to Gmail,
> which is so huge no one would
> > dare block them, and they have resources to handle incoming spam.
> >
> > 73s,
> >
> > Alan
> > WA4SCA
> >
> >
> > <-----Original Message-----
> > <From: amsat-bb-bounces@xxxxx.xxx <javascript:return>
> > <[mailto:amsat-bb-bounces@xxxxx.xxx <javascript:return>] On Behalf
> Of Joe Leikhim
> > <Sent: Saturday, December 14, 2013 8:01 PM
> > <To: amsat-bb@xxxxx.xxx <javascript:return>
> > <Subject: [amsat-bb] Confirm Message (Moderator please help??)
> > <
> > <I just got the following message from AMSAT-BB implying a
> > <problem sending the digest to my e-mail account. Can anyone
> > <tell me if I am alone with this problem? I had another person
> > <complain of bounces to my account. I really want to fix this
> > <if I can. My ISP Inmotionhosting claims that dome other e-mail
> > <servers are blocked globally due to spam. I have no idea how
> > <to fix this.
> > <
> > <I had to resubscribe to the BB.
> > <
> > <
> > <"Your membership in the mailing list AMSAT-BB has been disabled due to
> > <excessive bounces The last bounce received from you was dated
> > <30-Nov-2013. You will not get any more messages from this list until
> > <you re-enable your membership. You will receive 1 more reminders like
> > <this before your membership in the list is deleted.
> > <
> > <To re-enable your membership, you can simply respond to this message
> > <(leaving the Subject: line intact), or visit the confirmation page at"
> > <
> > <--
> > <Joe Leikhim
> > <
> > <
> > <Leikhim and Associates
> > <
> > <Communications Consultants
> > <
> > <Oviedo, Florida
> > <
> > <JLeikhim@xxxxxxx.xxx <javascript:return>
> > <
> > <407-982-0446
> > <
> > <WWW.LEIKHIM.COM
> > <
> > <_______________________________________________
> > <Sent via AMSAT-BB@xxxxx.xxx <javascript:return>. 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
> > <
> >
>
> -- Joe Leikhim
>
>
> Leikhim and Associates
>
> Communications Consultants
>
> Oviedo, Florida
>
> JLeikhim@xxxxxxx.xxx <javascript:return>
>
> 407-982-0446
>
> WWW.LEIKHIM.COM
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx <javascript:return>. 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
>
--
Joe Leikhim
Leikhim and Associates
Communications Consultants
Oviedo, Florida
JLeikhim@xxxxxxx.xxx
407-982-0446
WWW.LEIKHIM.COM
------------------------------
_______________________________________________
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 464
****************************************
Read previous mail | Read next mail
| |
