[amsat-bb] SO-50's ELEVENTH Birthday!

2013-12-18 Thread Mani
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: w...@isac.gov.in
   vu2wmy_m...@yahoo.com
   isroh...@yahoo.com

--
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.
--

___
Sent via AMSAT-BB@amsat.org. 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


[amsat-bb] SO-50's ELEVENTH Birthday!

2013-12-18 Thread Clint Bradford
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/



___
Sent via AMSAT-BB@amsat.org. 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


[amsat-bb] Re: Object IDs

2013-12-18 Thread Ted
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-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org] On
Behalf Of Rick Tejera
Sent: Wednesday, December 18, 2013 7:15 AM
To: 'Nico Janssen'; 'Mike Rupprecht'; amsat-bb@amsat.org
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-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org] On
Behalf Of Nico Janssen
Sent: Wednesday, December 18, 2013 7:00 AM
To: Mike Rupprecht; amsat-bb@amsat.org
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-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org] Im 
> Auftrag von Nico Janssen
> Gesendet: Dienstag, 17. Dezember 2013 14:32
> An: amsat-bb@amsat.org
> 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 

[amsat-bb] CAPE-2

2013-12-18 Thread PY5LF
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

 

___
Sent via AMSAT-BB@amsat.org. 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


[amsat-bb] help with cape ii

2013-12-18 Thread Roland Zurmely
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.
___
Sent via AMSAT-BB@amsat.org. 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


[amsat-bb] Re: Object IDs

2013-12-18 Thread Graham Shirville

Hi all,

The story so far!

The first object number that was issued for the contents of ISIPOD-1 - ie 
HinCube, FUNcube-1 and ZAcube was 2013-066B


Some days later, 2 new objects were identified  -2013-66AE and 2013-066AF.

Generally we thought that the best fit for FUNcube-1 was object 2013-066AF 
but more recent evaluations by our expert trackers now shows that FUNcube-1 
is most probably  2103-066AE.


They are still only about 100km apart after almost a month in orbit. So we 
have been correct to hang back a bit before making any claims!


The FUNcube team will monitor results for just a little longer before doing 
so.


thanks

Graham
G3VZV

-Original Message- 
From: Rick Tejera

Sent: Wednesday, December 18, 2013 3:15 PM
To: 'Nico Janssen' ; 'Mike Rupprecht' ; amsat-bb@amsat.org
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-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org] On
Behalf Of Nico Janssen
Sent: Wednesday, December 18, 2013 7:00 AM
To: Mike Rupprecht; amsat-bb@amsat.org
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-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org] Im
Auftrag von Nico Janssen
Gesendet: Dienstag, 17. Dezember 2013 14:32
An: amsat-bb@amsat.org
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 wh

[amsat-bb] Re: Object IDs

2013-12-18 Thread Mike Rupprecht
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:ham...@xs4all.nl] 
Gesendet: Mittwoch, 18. Dezember 2013 15:00
An: Mike Rupprecht; amsat-bb@amsat.org
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-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org] Im 
> Auftrag von Nico Janssen
> Gesendet: Dienstag, 17. Dezember 2013 14:32
> An: amsat-bb@amsat.org
> 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

[amsat-bb] Re: CAPE-2 spoke to me with the voice of Darth Vader!

2013-12-18 Thread carles

Hi all,
Roland, good work¡¡ thanks for the info, today I also heard the CAPE-2 with 
good signals,  AX.25,  CW and voice message.

The information is in Spanish language, but it is easy;-)

http://espaysat.blogspot.com/


Carles Roy

http://espaysat.blogspot.com/
eb...@eb3sa.com
www.eb3sa.com


- Original Message - 
From: "Roland Zurmely" 

To: "AMSAT" 
Sent: Monday, December 16, 2013 9:29 PM
Subject: [amsat-bb] CAPE-2 spoke to me with the voice of Darth Vader!



Please see here, CAPE-2 responding to a "Send Text to Speech" command:
"Hello P Y 4 Z B Z"

http://www.qsl.net/py4zbz/cape.htm#d


73 de Roland PY4ZBZ.
___
Sent via AMSAT-BB@amsat.org. 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@amsat.org. 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


[amsat-bb] Re: *AMSAT* on Echolink

2013-12-18 Thread Paul Williamson
On Dec 17, 2013, at 4:52 PM, Bruce  wrote:

> it appears that the conference *AMSAT* on Echolink is no longer working.

Fixed. The Echolink conference server had to be manually restarted after a 
reboot.

73  -Paul
kb...@amsat.org



___
Sent via AMSAT-BB@amsat.org. 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


[amsat-bb] Re: Object IDs

2013-12-18 Thread Rick Tejera
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-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org] On
Behalf Of Nico Janssen
Sent: Wednesday, December 18, 2013 7:00 AM
To: Mike Rupprecht; amsat-bb@amsat.org
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-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org] Im 
> Auftrag von Nico Janssen
> Gesendet: Dienstag, 17. Dezember 2013 14:32
> An: amsat-bb@amsat.org
> 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  Ardu

[amsat-bb] Re: Object IDs

2013-12-18 Thread Nico Janssen

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/?key=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-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org] Im
Auftrag von Nico Janssen
Gesendet: Dienstag, 17. Dezember 2013 14:32
An: amsat-bb@amsat.org
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@amsat.org. Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: ht

[amsat-bb] Re: satellite average elevation & new birds

2013-12-18 Thread Robert Bruninga
> ... asking Bob to comment  on his earlier thoughts on using antennae at
fixed elevations?

The geometry of LEO satellites has not changed.  The optimum angle for a
fixed tilt modest gain YAGI is about 15 degrees (assuming you have a
decent horizon).  See:
http://aprs.org/LEO-tracking.html

That said, if your antenna is seriously blocked from all directions below
say 10 degrees, then you are not going to hear anything down there anyway.
So bump it up to say 20 or 25.  But 70% of all LEO passes are below 22
degrees so just recognize that you are giving up most of your operations.

Bob, Wb4aPR

-Original Message-
From: amsat-bb-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org] On
Behalf Of Clayton Coleman
Sent: Tuesday, December 17, 2013 8:35 PM
To: Ted
Cc: AMSAT-BB
Subject: [amsat-bb] Re: satellite average elevation & new birds

Just a short time ago after I moved into a new shack, I operated for a
month with an Elk at 15 degrees on a tripod.  Armstrong rotor.  I worked
all the current satellites right up through the first week we had AO-73's
transponder available.

Pay close attention to comments WB4APR has made about setting the fixed
elevation based on the lowest horizon you can work.  For example, if it
takes ten degrees for you to clear a mountain, twenty five degrees is
probably okay.  If you have a clear horizon view, fifteen is probably
okay.  The goal is to have as much gain available at your lowest elevation
to increase your available range.  YMMV

PS A preamp goes a long way in a fixed elevation setup.

73
Clayton
W5PFG
 On Dec 17, 2013 7:24 PM, "Ted"  wrote:

> I'm kind of looking for an update from Bob, but can't find his email
> right now...
>
> But the question is, in view of what appears to be some renewed
> interest in working the new cube sats, et al, is asking Bob to comment
> on his earlier thoughts on using antennae at fixed elevations. For me,
> I'm using my Elk on a Rat Shack rotor at a fixed el per Bob's
> recommendations. (I'm still struggling with PCSAT32...!!!%^&*!!) but,
> this antenna set up is very cost effective and seems to perform pretty
well.
>
> For example, Joel Black has asked for some advice in an earlier
> posting. My concern is that new operators or those returning run out
> and spend a bunch of $$$ on a new setup. No one knows how long the
> current crop will last or if a new crop is in the future, so probably
> some caution on the Visa is warranted.
>
> Just asking  (and especially Bob)
>
> 73, Ted
> K7TRK
>
>
> -Original Message-
> From: amsat-bb-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org]
> On Behalf Of Bob Bruninga
> Sent: Tuesday, April 12, 2011 8:23 AM
> To: amsat-bb@AMSAT.Org
> Subject: [amsat-bb] Re: satellite average elevation
>
> > we used a horizontally polarized yagi fixed at 30 degrees above the
> > horizon.  That worked very well..
>
> Thanks for the confirmation.  Yes, elevation rotation is simply not
> needed at all for LEO spacecraft and modest beams.  A mild, fixed tilt
> modest beam is just perfect.
>
> But, the "30 degree" angle myth is very pervasive throughout amsat,
> whereas, the optimum angle is more like 15 degrees.
>
> A 30 degree up-tilt gives up too much gain (-3 dB!) on the horizon
> where signals are weakest and where satellites spend most of their
> time, and puts the gain in an area of the sky where the satellite is
> already 6 dB stronger and is rarely there (giving you max beam gain
where you need it least).
>
> If you look at the sketches on the web page, the optimum angle is more
> like
> 15 degrees up-tilt.  It preserves max gain on the horizon within 1 dB
> (where it is needed most) and focuses the breadth of its gain on the
> area of the sky where the satellites spend something like 95% of their
> time.  For the missing 5%, the satellite is right on top of you and
> almost 10 dB stronger without any beam at all.  Oh, and the 15 degree
> up-tilt beam is also perfect for Terrestrial operations as well.
>
> See the sketch on: http://aprs.org/rotator1.html
>
> In some future life, if we ever get back to HEO's and huge OSCAR
> arrays, then elevation rotors have a place.  These high-gain beams
> have such narrow gain patterns, that higher precision tracking is a
> must.  (Though it is complete overkill for LEO's).
>
> Using these OVERKILL arrays for LEO's adds significant complexity to
> LEO operation requiring higher precision tracking, elevation rotors,
> better timing, fresher element sets and automated operation.
>
> Using a TV rotator and 15 degree fixed tilt beam is much more
forgiving...
>
> Bob, Wb4APR
>
>
> ___
> Sent via AMSAT-BB@amsat.org. 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@amsat.org. Opinions expressed are those of the a