| |
CX2SA > SATDIG 22.05.15 12:40l 692 Lines 23375 Bytes #999 (0) @ WW
BID : AMSATBB10142
Read: GUEST
Subj: AMSAT-BB-digest V10 142
Path: IW8PGT<IZ3LSV<IW0QNL<JH4XSY<JE7YGF<7M3TJZ<CX2SA
Sent: 150522/1029Z @:CX2SA.SAL.URY.SOAM #:21217 [Salto] FBB7.00e $:AMSATBB10142
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. USS Langley - nil (Ken Swaggart)
2. Re: USS Langley - nil (Jerry Buxton)
3. Re: W5PFG/VE2 - FN35 & FN26 Update (Clayton Coleman)
4. Re: BRICsat now heard too! (Gregory Beat)
5. Re: Any Need for FN22? (Sean K.)
6. Star Comm Awards (wa4hfn@xxxxxxx.xxxx
7. Office Closed (Martha)
8. USNA Sat Status (day 2) (Robert Bruninga)
9. Receiving PSAT PSK31 FM downlink (Robert Bruninga)
10. Re: USNA Sat Status (day 2) (Douglas Quagliana)
11. Re: Receiving PSAT PSK31 FM downlink (Rick Tejera)
12. Error just started with SpaceTrack TLE Retriever 3 (Rick Walter)
13. Re: Error just started with SpaceTrack TLE Retriever 3
(wa4sca@xxxxx.xxxx
14. Re: Error just started with SpaceTrack TLE Retriever 3
(Rick Walter)
15. AGW Packet, UISS with TS-2000 (Ted)
----------------------------------------------------------------------
Message: 1
Date: Thu, 21 May 2015 09:38:45 -0700
From: "Ken Swaggart" <k.swaggart@xxxxxxx.xxx>
To: "AMSAT-BB" <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] USS Langley - nil
Message-ID: <5FFE942463084416B9F14DB7327992E8@xxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
Specifically listened for USS Langley during the 1627Z pass, max el 32 deg,
but nothing heard.
73,
Ken, W7KKE
CN75xa
------------------------------
Message: 2
Date: Thu, 21 May 2015 11:47:25 -0500
From: Jerry Buxton <amsat@xxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] USS Langley - nil
Message-ID: <555E0C1D.1000702@xxxx.xxx>
Content-Type: text/plain; charset=windows-1252
Seconded.
Jerry Buxton, N?JY
On 5/21/2015 11:38, Ken Swaggart wrote:
> Specifically listened for USS Langley during the 1627Z pass, max el 32
deg, but nothing heard.
>
> 73,
> Ken, W7KKE
> CN75xa
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
expressed
> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
>
>
------------------------------
Message: 3
Date: Thu, 21 May 2015 12:03:08 -0500
From: Clayton Coleman <kayakfishtx@xxxxx.xxx>
To: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] W5PFG/VE2 - FN35 & FN26 Update
Message-ID:
<CAPovOweumY+f=gkju9A=hpdpjJTzk1KAGkyo30bAk0Q8tW3sRg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Due to unforseen circumstances I will miss the SO-50 at 1755Z today but
I'll work the following FO-29's.
73
Clayton
W5PFG
On May 18, 2015 11:19 AM, "Clayton Coleman" <kayakfishtx@xxxxx.xxx> wrote:
> I'm planning to operate the following passes from FN26 near Val-David,
> QC, Canada on Thursday, 21 May:
> SO-50 @ 17:55Z
> FO-29 @ 19:40Z
> FO-29 @ 21:27Z
>
> 73
> Clayton
> W5PFG (/VE2 starting Wednesday evening)
>
> On Mon, May 4, 2015 at 7:27 AM, Clayton Coleman <kayakfishtx@xxxxx.xxx>
> wrote:
> > I'll be visiting Montreal, QC, Canada again in a couple of weeks.
> > Several individuals have asked me about operating satellites from grid
> > FN26. With those requests in mind, I will travel to FN26 for two
> > orbits of FO-29. I do not know the specific passes at this time.
> >
> > There are a few others who are looking to have FN35 confirmed. I will
> > post about those operations on Twitter @xxxxx shortly before and
> > during the US Memorial Day Weekend Holiday.
> >
> > Please email me off-BB if you are interested in the FN26 operation.
> >
> > Thank you,
> >
> > 73
> > Clayton
> > W5PFG
>
------------------------------
Message: 4
Date: Thu, 21 May 2015 12:05:41 -0500
From: Gregory Beat <w9gb@xxxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Cc: "john.brier@xxxxx.xxxx <john.brier@xxxxx.xxx>
Subject: Re: [amsat-bb] BRICsat now heard too!
Message-ID: <E6639EE7-94DA-48EF-BAFE-88EAEACA8BF2@xxxxxx.xxx>
Content-Type: text/plain; charset=utf-8
These spacecraft (and CubeSats) were onboard the Atlas V launch, yesterday:
? X-37B OTV-4 (USA 261)
? GEARRSAT 2 (GEARRS 2)
? LightSail A
? OptiCube 1 (O/C 1)
? OptiCube 2 (O/C 2)
? OptiCube 3 (O/C 3)
? USS Langley
? AeroCube 8A (IMPACT A)
? AeroCube 8B (IMPACT B)
? BRICSat-P
? PSat A (ParkinsonSat A)
http://space.skyrocket.de/doc_chr/lau2015.htm
Scroll down the AMSAT-UK web site
http://amsat-uk.org/2015/05/20/lightsail-1-launch/
for a very good picture of the Dispenser, that was attached to the Centaur
second stage.
After OTV-4, X-37B was released, the Centaur stage performed a orbital
maneuver for release of these small satellites.
--
BTW, Centaur has now been used for 51-1/2 years by USA on Atlas (and retired
Titan boosters).
w9gb
Sent from iPad Air
------------------------------
Message: 5
Date: Thu, 21 May 2015 17:36:58 +0000 (UTC)
From: "Sean K." <kx9x@xxxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Any Need for FN22?
Message-ID:
<164263715.3586827.1432229818462.JavaMail.yahoo@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
OK then. I'll be QRV from some passes. This is a vacation weekend and ham
radio is secondary.
I'll email the reflector when I know the passes I'll be on (I won't be on
every pass every day), and post activity to Twitter as well.
?Sean Kutzko
Amateur Radio KX9X
From: Glenn Miller - AA5PK <aa5pk@xxxxxxxxxx.xxx>
To: Sean K. <kx9x@xxxxx.xxx>
Sent: Thursday, May 21, 2015 10:32 AM
Subject: Re: [amsat-bb] Any Need for FN22?
Yes!
-----Original Message-----
From: Sean K. via AMSAT-BB
Sent: Thursday, May 21, 2015 9:14 AM
To: AMSAT BB
Subject: [amsat-bb] Any Need for FN22?
Hi all-
I'll be in Cooperstown, NY for the long weekend. Does anybody need FN22? If
so, I'll bring an HT/Arrow for SO-50.
Sean Kutzko
Amateur Radio KX9X
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
to all interested persons worldwide without requiring membership. Opinions
expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 6
Date: Thu, 21 May 2015 19:29:00 +0000 (UTC)
From: wa4hfn@xxxxxxx.xxx
To: AMSAT <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Star Comm Awards
Message-ID:
<1012718932.15891609.1432236540431.JavaMail.zimbra@xxxxxxx.xxx>
Content-Type: text/plain; charset=utf-8
For the new satellite operators please checkout our free awards
goto
www.starcommgroup.org we are an Amsat support group
Grid Master for working and confirming all 488 us grids
Got grids for making one contact in the 10 grid blocks in the US.
5 in em55 for working 5 stations in em55 or working 5 ops with the award
Thanks and enjoy the birds
WA4HFN em55 Damon
------------------------------
Message: 7
Date: Thu, 21 May 2015 17:22:45 -0400
From: Martha <martha@xxxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>, Board of Directors <bod@xxxxx.xxx>
Subject: [amsat-bb] Office Closed
Message-ID:
<CAPk0USxT91Rus=r2Y7uhVbqR=kEtFmab3yA5wr2-Dqn9YzG9cg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
The AMSAT Office will be closed on Friday, May 22nd through Monday, May
25th. I will be back on Tuesday, May 23rd. Time to recover from Dayton!
--
73- Martha (AMSAT's only employee)
------------------------------
Message: 8
Date: Thu, 21 May 2015 18:30:06 -0400
From: Robert Bruninga <bruninga@xxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] USNA Sat Status (day 2)
Message-ID: <12ae834a8ad362fc35c8f0b83c08cb7a@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
We now have heard 4 of 5 transmitters from our 3 spacecraft all still in a
close cluster:
* PSAT packet is OK but WOD not working (no digipeating for users yet)
* PSAT PSK31 downlink is ok [remember, it is FM!]
* BRICSAT telemetry has been heard but is cycling OFF due to low power
* BRICSAT PSK31 downlink (also FM) has also been heard barely (when ON)
* USS Langley not heard
PSAT CPU shows the 4 day-fail-safe backup reset circuit is not counting
down, so we have lost this (1 of 3) fail safe backup RESET capabilities.
Bad line of code already found. But cannot change it.
PSAT is not properly reporting WOD data and S#... STATUS packets are being
bundled until 255 byte packet length is reached and then it all comes down
at once. Noone has captured any of these long packets. Please try with
PASSALL ON so that you can receive partial packets.
Awaiting permission from BRNO University to authorize HF user uplinks on
PSAT PSK31.
BRICSAT PSK31 transponder is on identical frequencies as PSAT's. You can
tell them apart because one has PSK Telemetry on 315 Hz and the other is
on 365 Hz. Both on the UHF FM downlink 435.350 MHz
We'd LOVE to hear from USS Langley, and we'd love to capture one of those
long WOD packets from PSAT. Our ground station is only getting a few
packets compared to some submissions from others. Keep it up.
SUMMARY:
145.825 1.5U cubesat - PSAT 1200 baud AX.25
435.350 same cubesat - PSAT PSK31 FM - Brno University transponder
437.975 1.5U cubesat - BRICsat 9600 baud
435.350 same cubesat - BRICsat PSK31 FM - Brno University transponder
437.975 3.0U cubesat - USS Langley 9600 bd <not yet heard from>
ULTRASat3
1 99993U 15140.67013889 .00040043 00000-0 10235-2 0 00009
2 99993 055.0004 339.9238 0251027 182.3314 074.3075 15.12517086000014
Bob, WB4APR
------------------------------
Message: 9
Date: Thu, 21 May 2015 19:19:30 -0400
From: Robert Bruninga <bruninga@xxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Receiving PSAT PSK31 FM downlink
Message-ID: <559edf5af7ff1ac54b106687d6a580c8@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Receiving the PSAT (and BRICsat) 435.350 MHz FM downlink is as simple as
placing your PSK31 laptop microphone next to the speaker on your FM
satellite UHF receiver and just watching the waterfall.
What you see is exactly what everyone else sees (its FM). There is no
Doppler added to the tones due to your station's position relative to the
satellite. But you DO have to retune your FM radio at least 3 times
during the pass (+5 KHz, 0, -5 KHz) to stay in the FM passband.
User uplinks, however, will shift in the waterfall according to each
user's position relative to the satellite. The shift can be as low as 1
Hz per second to as high as 6 Hz per second. This is because the uplink
is on 10 meters where the Doppler rate is only 1/15th of what it would be
on UHF.
The TELEMETRY channel at 315 Hz (PSAT) or 375 Hz (BRICsat) is FIXED with
no Doppler since it is generated onboard into the FM downlink
WHAT TO DO:
1) We will need PSK31 authors to open the PSK31 frequency tracking to
accommodate more than 1 Hz per second Doppler tracking. Current
implementations can do 1 Hz/s but completely fail at 3 Hz/s. 2 Hz/s might
work a little...
2) Until then, ANY uplink user that is in line with a direct overhead pass
will have minimum Doppler at the start and end of his pass (1 Hz/sec) when
the satellite is going right at him and directly away from him. (Though
it will be MAX (6Hz/sec) when it passes over his station).
3) Just turn on MULTI CHANNEL window and let the PSK31 decode everyone.
The ones with the least Doppler at any instant may be decoded for a while!
USERS can transmit later when BRNO University says it has completed its
tests. Brno provided the transponders for use in the PSAT and BRICsat
satellites.
So start preparing your station to TX PSK31 on 10 meters SSB and to
receive the audio from an FM UHF rig on 435.350 +/- 5 KHz steps of
Doppler.
DOWNLINK Limitations: The UHF downlink signal is only 300 mW and so a UHF
beam is needed on the downlink.
UPLINK RESTRICTIONS: *NOTHING MORE THAN* a Vertical 1/4 wave or Dipole is
authorized on the 10m uplink and no more than 25 Watts (for now).
Remember a 1/4 wave vertical is the ideal antenna because it maximizes the
signal at lower angles and tapers the signal as the satellite gets closer.
This keeps user uplinks about the same during a pass. Strong stations
just drive down the AGC and ruin it for everyone.
Use minimum power!! Remember, this is crossband FULL DUPLEX so you can
see yourself in the downlink just like everyone else can see you. Act
accordingly. And of course DO NOT TRANSMIT if you cannot see the
waterfall ... Duh!
Enjoy!
Bob, WB4APR
------------------------------
Message: 10
Date: Thu, 21 May 2015 19:58:13 -0500
From: Douglas Quagliana <dquagliana@xxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] USNA Sat Status (day 2)
Message-ID: <555E7F25.7050500@xxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 5/21/2015 5:30 PM, Robert Bruninga wrote:
> PSAT is not properly reporting WOD data and S#... STATUS packets are being
> bundled until 255 byte packet length is reached and then it all comes down
> at once. Noone has captured any of these long packets. Please try with
> PASSALL ON so that you can receive partial packets.
>
Does anyone have a recording of a PSAT pass? I would like to get either
a 48k samples per
second recording or an I/Q recording. I want to try my DSP software
modem on the
long packets.
73,
Douglas KA2UPW/5
------------------------------
Message: 11
Date: Thu, 21 May 2015 20:48:04 -0700
From: Rick Tejera <saguaroastro@xxx.xxx>
To: Robert Bruninga <bruninga@xxxx.xxx>, amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Receiving PSAT PSK31 FM downlink
Message-ID: <rl591e74wktw43fiabps9dbf.1432266484466@xxxxx.xxxxxxx.xxx>
Content-Type: text/plain; charset=utf-8
Sent from my Verizon Wireless 4G LTE smartphone
-------- Original message --------
From: Robert Bruninga <bruninga@xxxx.xxx>
Date: 05/21/2015 16:19 (GMT-07:00)
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Receiving PSAT PSK31 FM downlink
Receiving the PSAT (and BRICsat) 435.350 MHz FM downlink is as simple as
placing? your PSK31 laptop microphone next to the speaker on your FM
satellite UHF receiver and just watching the waterfall.
What you see is exactly what everyone else sees (its FM).? There is no
Doppler added to the tones due to your station's position relative to the
satellite.? But you DO have to retune your FM radio at least 3 times
during the pass (+5 KHz, 0, -5 KHz) to stay in the FM passband.
User uplinks, however, will shift in the waterfall according to each
user's position relative to the satellite.? The shift can be as low as 1
Hz per second to as high as 6 Hz per second.? This is because the uplink
is on 10 meters where the Doppler rate is only 1/15th of what it would be
on UHF.
The TELEMETRY channel at 315 Hz (PSAT) or 375 Hz (BRICsat) is FIXED with
no Doppler since it is generated onboard into the FM downlink
WHAT TO DO:
1) We will need PSK31 authors to open the PSK31 frequency tracking to
accommodate more than 1 Hz per second Doppler tracking.? Current
implementations can do 1 Hz/s but completely fail at 3 Hz/s.? 2 Hz/s might
work a little...
2) Until then, ANY uplink user that is in line with a direct overhead pass
will have minimum Doppler at the start and end of his pass (1 Hz/sec) when
the satellite is going right at him and directly away from him.? (Though
it will be MAX (6Hz/sec) when it passes over his station).
3) Just turn on MULTI CHANNEL window and let the PSK31 decode everyone.
The ones with the least Doppler at any instant may be decoded for a while!
USERS can transmit later when BRNO University says it has completed its
tests.? Brno provided the transponders for use in the PSAT and BRICsat
satellites.
So start preparing your station to TX PSK31 on 10 meters SSB and to
receive the audio from an FM UHF rig on 435.350 +/- 5 KHz steps of
Doppler.
DOWNLINK Limitations:? The UHF downlink signal is only 300 mW and so a UHF
beam is needed on the downlink.
UPLINK RESTRICTIONS:? *NOTHING MORE THAN* a Vertical 1/4 wave or Dipole is
authorized on the 10m uplink? and no more than 25 Watts (for now).
Remember a 1/4 wave vertical is the ideal antenna because it maximizes the
signal at lower angles and tapers the signal as the satellite gets closer.
This keeps? user uplinks about the same during a pass.? Strong stations
just drive down the AGC and ruin it for everyone.
Use minimum power!!? Remember, this is crossband FULL DUPLEX so? you can
see yourself in the downlink just like everyone else can see you.? Act
accordingly.? And of course DO NOT TRANSMIT if you cannot see the
waterfall? ... Duh!
Enjoy!
Bob, WB4APR
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
to all interested persons worldwide without requiring membership. Opinions
expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 12
Date: Fri, 22 May 2015 01:33:21 -0400
From: Rick Walter <wb3csy@xxxxx.xxx>
To: AMSAT -BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Error just started with SpaceTrack TLE Retriever 3
Message-ID: <8191F12E-6553-4931-9E49-FDD3A482874A@xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
I usually update my Keplerian elements to track the birds with T.S. Kelso's
SpaceTrack TLE Retriever 3, stand alone Windows program. It has worked
flawlessly for many years on my laptops running XP and Windows 7. Starting
this week, I get an error on all three computers. The program downloads the
master lists fine but when I click the button to parse them out and check
for errors, I immediately get "Unhandled exception has occurred in your
application Spacetrak ....
Index and length must refer to a location within the string parameter name
length. I am using version 3.0.1.3 (2013Jul17) and even upgraded on one
computer to version 3.0.1.5 (2014 Dec18). I sent an email to T.S. Kelso and
attached a debug file but have not heard anything in several days. Any one
have the same problem or know of a fix? Thank you.
Rick
WB3CSY
Sent from Rick's iPad2
------------------------------
Message: 13
Date: Fri, 22 May 2015 05:56:44 +0000
From: <wa4sca@xxxxx.xxx>
To: Rick Walter <wb3csy@xxxxx.xxx>, AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Error just started with SpaceTrack TLE
Retriever 3
Message-ID: <555ec5fd.081c8c0a.7afc.408b@xx.xxxxxx.xxx>
Content-Type: text/plain; charset="utf-8"
Have you updated to the new password requirement, and also entered it in the
program?
Alan
WA4SCA
From: Rick Walter
Sent: ?Friday?, ?May? ?22?, ?2015 ?12?:?33? ?AM
To: AMSAT-BB
I usually update my Keplerian elements to track the birds with T.S. Kelso's
SpaceTrack TLE Retriever 3, stand alone Windows program. It has worked
flawlessly for many years on my laptops running XP and Windows 7. Starting
this week, I get an error on all three computers. The program downloads the
master lists fine but when I click the button to parse them out and check
for errors, I immediately get "Unhandled exception has occurred in your
application Spacetrak ....
Index and length must refer to a location within the string parameter name
length. I am using version 3.0.1.3 (2013Jul17) and even upgraded on one
computer to version 3.0.1.5 (2014 Dec18). I sent an email to T.S. Kelso and
attached a debug file but have not heard anything in several days. Any one
have the same problem or know of a fix? Thank you.
Rick
WB3CSY
Sent from Rick's iPad2
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
to all interested persons worldwide without requiring membership. Opinions
expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 14
Date: Fri, 22 May 2015 04:37:02 -0400
From: Rick Walter <wb3csy@xxxxx.xxx>
To: "<wa4sca@xxxxx.xxx>" <wa4sca@xxxxx.xxx>
Cc: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Error just started with SpaceTrack TLE
Retriever 3
Message-ID: <4FDDA32D-13C5-4C39-8EF3-32E9B0F5D1AF@xxxxx.xxx>
Content-Type: text/plain; charset=utf-8
Hi Alan. Is this something just recent? I know while back we had to do
something like that and then after that,we had to upgrade to a new version.
Rick
Sent from Rick's iPad2
> On May 22, 2015, at 1:56 AM, <wa4sca@xxxxx.xxx> <wa4sca@xxxxx.xxx> wrote:
>
> Have you updated to the new password requirement, and also entered it in
the program?
>
> Alan
> WA4SCA
>
>
> From: Rick Walter
> Sent: ?Friday?, ?May? ?22?, ?2015 ?12?:?33? ?AM
> To: AMSAT-BB
>
> I usually update my Keplerian elements to track the birds with T.S.
Kelso's SpaceTrack TLE Retriever 3, stand alone Windows program. It has
worked flawlessly for many years on my laptops running XP and Windows 7.
Starting this week, I get an error on all three computers. The program
downloads the master lists fine but when I click the button to parse them
out and check for errors, I immediately get "Unhandled exception has
occurred in your application Spacetrak ....
> Index and length must refer to a location within the string parameter name
length. I am using version 3.0.1.3 (2013Jul17) and even upgraded on one
computer to version 3.0.1.5 (2014 Dec18). I sent an email to T.S. Kelso and
attached a debug file but have not heard anything in several days. Any one
have the same problem or know of a fix? Thank you.
> Rick
> WB3CSY
>
> Sent from Rick's iPad2
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
expressed
> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 15
Date: Thu, 21 May 2015 17:35:53 -0700
From: "Ted" <k7trkradio@xxxxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] AGW Packet, UISS with TS-2000
Message-ID: <003b01d09427$429bda50$c7d38ef0$@xxxxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"
Anyone successfully using the built-in TNC in KW TS-2000 with AGW Packet
engine. Unsure what to select in the drop down for TNC Make.
Any help appreciated
73, Ted
K7TRK
------------------------------
Subject: Digest Footer
_______________________________________________
Sent via amsat-bb@xxxxx.xxx.
AMSAT-NA makes this open forum available to all interested persons worldwide
without requiring membership. Opinions expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT member? Join now to support the amateur satellite program!
http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
End of AMSAT-BB Digest, Vol 10, Issue 142
*****************************************
Read previous mail | Read next mail
| |
