March 2013 - AMSAT-BB - mailman.amsat.org

Re: AMSAT-BB Digest, Vol 8, Issue 83
by Thomas Frey 13 Mar '13

13 Mar '13

amsat-bb-request(a)amsat.org schrieb: > Date: Tue, 12 Mar 2013 22:29:05 +0100 > From: PE0SAT | Amateur Radio<pe0sat(a)vgnet.nl> > To: Amsat bb<amsat-bb(a)amsat.org> > Subject: [amsat-bb] Unix command line Kepler manager > Message-ID:<7602b403b94b77259610495fa72177ac(a)vgnet.nl> > 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 > > Hello Jan This is my script running under OS/2-eComStation: /* begin of CMD file */ /* access with WGet */ 'wget -i oscarkep.url -O kepler-w.txt' /* file with URL's */ /* access with Curl */ 'curl -c cookies.txt -b cookies.txt -k https://www.space-track.org/ajaxauth/login -d "identity=USER&password=Pa$$w0rd"' /* login via cookie */ 'curl --cookie cookies.txt -k https://www.space-track.org/basicspacedata/query/class/tle_latest/favorites… -o kepler-c.txt' 'copy kepler-w.txt + kepler-c.txt kepler.txt' /* end of CMD file */ May it help. -- Mit freundlichen Grüssen, Regards, 73 Thomas Frey, HB9SKA ______________________________________________________________________ Thomas Frey, Holzgasse 2, CH-5242 Birr, Tel. + Fax: 056 444 93 41 http://home.datacomm.ch/th.frey/

1 0

SatPC32 Update for Tone Control of Yaesu FT-857/897
by Tom Deeble - KA6SIP 13 Mar '13

13 Mar '13

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(a)aol.com PACIFICON - Oct 11-13, 2013

2 2

Disregard my ISS packet question. I MADE IT IN!
by transbets＠gmail.com 13 Mar '13

13 Mar '13

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

1 0

ISS digital packets
by transbets＠gmail.com 13 Mar '13

13 Mar '13

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

1 0

We-Wish decay
by Nico Janssen 12 Mar '13

12 Mar '13

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

6 9

Satellite hit by debris from weapon test
by Trevor M5AKA 12 Mar '13

12 Mar '13

CNN are reporting the BLITS satellite was rendered inoperable after being impacted by debris from a 2007 weapon test. http://edition.cnn.com/2013/03/09/tech/satellite-hit/index.html Wiki says the weapon test created 2,317 pieces of trackable size (golf ball size and larger) and an estimated 150,000 debris particles so there's clearly potential for more impacts. 73 Trevor M5AKA

18 17

Re: Satellite hit by debris from weapon test
by Nitin Muttin 11 Mar '13

11 Mar '13

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]

1 0

Re: Satellite hit by debris from weapon test
by Robert Coppock 11 Mar '13

11 Mar '13

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.

1 1

Re: WiSP under Windows 7
by Mineo Wakita 11 Mar '13

11 Mar '13

I wrote an article called "How to setup WiSP32 in Vista" in my HP several years ago. I think this method is similar in "WiSP under Windows 7". http://www.ne.jp/asahi/hamradio/je9pel/wispvist.htm JE9PEL, Mineo Wakita

1 0

WiSP under Windows 7
by tokens＠myranch.com 10 Mar '13

10 Mar '13

Can WiSP be run under Windows7 and if so how? Many thanks, Al W8KHP

2 2