I am experiencing what may be a problem with my Kansas City Tracker card. I am using the latest version of N4HY's QuickTrack with the KCT and Yaesu rotator. The rotator works fine in all directions. The tracker card is seated tightly in its slot in the computer. The cable connecting the KCT with the rotator is firmly connected. When I boot up I get an indication that the kct is stalled in azimuth. That is what the cw readout tells me. Elevation works fine. I re installed the software driving the KCT and this doesn't seem to help. In addition I re installed Bob's software. I still get a stalled azimuth. This leads me to believe that the KCT has a problem. Does anyone have any ideas? Any information would be appreciated>
I know LL Grace isn't in business and the KCT isn't manufactured. Does anyone know where a used one can be obtained? Is anyone involved in repairing the KCT cards?
Dave Marthouse N2AAM
last 25th october, I has received UO-11 signals and I can record a nice pass over Natal HI24jd. I has used mixw to decode telemetry and results in a lot of text data, show after. using a yagi 4 elements the signal was constant but never over S-1 (only open SQL).
today 28th the UO-11 pass in silent.
who be interest I can send the total file with 40 telemetry frames or the audium file.
73, Joca PS7JN
UOSAT-2 060=590033427 000000010001020002030003040004050005060006070007080008090009 100001110000120003130002140005150004160007170006180009190008 20000221000322000023000124000625000726000427000528000A29000B 30000331000232000133000034000735000636000537000438000B39000A 40000441000542000643000744000045000146000247000348000C49000D 50000551000452000753000654000155000056000357000258000D59000C 60800E615FC1620105633305644402651E0C662AC467000168000E69000F
UOSAT-2 060=590033431 00000001000102000203000304000405000506000 070007080008090009 10000111000012000313000214000515000416000W170006180009190008 20000221000322000023000124000625000726000427000528000A29000B 30000331000232000133000034000S35000636000537000438000B 000A 40000441000542000643000704000045000146000247000348000C49000D 50000551000452000753000654000155000056000357000258000D59000C 60800E615FG1620105633305644402651E0C662AC467000168000E69000F
Música para ver e ouvir: You're Beautiful, do James Blunt
> > Key the PTT line of your UHF FM transmitter for a CW uplink. Turn the
> > mic gain down or remove the mike all together.
> > It will chirp a bit, but it can be copied.
> If your HT does odd splits and has wide coverage, you might be able to reduce
> or eliminate this. Generally, the VFO has to switch from receive to transmit
> by the amount of the IF. That's probably where the chirp comes from. I have
> not done this experiment with a service monitor to see exactly what happens,
> but you might try an odd split such that the RX frequency has been shifted by
> the IF frequency (you might have to try both +/- to see which works for your
> rig). Then when you key the rig, the VFO doesn't have shift very far (if at
> all) and that might make the chirp go away. If you try the experiment, please
> let me know.
I was doing some testing here at home with this. I used an IC-W32A and IC-T7H
with a straight key plugged into the mic jack on each radio. Nothing fancy from
the key, just an adapter to fit the 3/32" (2.5mm) jack, and I could key the
transmitter. When I did this, listening on another radio, I could
hear only the
carrier. No audio was coming from the HTs' built-in mics.
I might try this on FO-29 this evening, and maybe VO-52. One additional
drawback with an HT for a CW transmitter is the fact that most HTs
(including these two I tried this morning) have 5 kHz as the smallest tuning
step. I also have an FT-817ND, but I only have one of those radios.
Otherwise, I would be trying all of this with a pair of FT-817s and making
some CW and SSB contacts.
Can anyone verify the reception of signals from this old satellite?
The BBC TV programe Coast visited the Black Arrow test site on the Isle of White.
This was the location for a static firing test site, part of the sucessful UK rocket program in the 1960's-70's
On the programe they demonstrated reception of short pulses which were claimed to be from the satellite Prospero.
Object number 5580. Is this genuine, or did they pick up something else which they attributed to Prosopero.
An AOR scanner was shown but I was not quick enough to see the frequency display. Did anyone record it on video?
The antenna was a small yagi hand held.
The only reference to a recent reception report I can find on the net dates to 2002 and a frequency of 137.560.
Element sets for Prospero are available from the Space-Track web site.
(see the Space Page, RadCom January 2006.
73 John G7HIA
PS/ I listened on numerous day light orbits early in the year and heard nothing.
When I was in the Regulatory Affairs group at Orbcomm from 1996-2001, we
had an issue with Prospero occasionally showing up in the Little LEO
downlink band of 137-138 MHz.
I contacted some folks in Farnham who were involved with that satellite
(launched from Woomera, Australia, if I'm not mistaken), and was able to
collect some documentation on the satellite, long considered dead, and
most of those involved retired.
The long and short of it was that the problem went away, everyone was
pleased, and I had some interesting documents. It's been some time
since that happened; I've moved on twice (first to Iridium Satellite and
am now with the US Government), and all that's left of Propero is the
backup satellite and Black Arrow rocket, both of which which sit in the
Science Museum in London. I haven' a clue where the documentation I
had is -- it may be in the boxes of material I donated a couple of
years ago to the Historic Electronics Museum outside Baltimore. If I get
a chance, I'll sift through the debris in my basement and see if they
rise to the surface.
Can anyone tell my why Celestian bbs changed it kep format from something
simple and easy to use to something that don't work!!!!
Again today I have downloaded the new keps, then in Word Pad deleted the
satellites I don't want and the +- that I don't want and resaved the file.
But once again my sat programs reject these new files.
I may start using the Amsat keps that are in the NASAbare files as these
are text without extra stuff.
The problem with these keps are the sat names are different from what I
have in my programs now (nova and Uni-trak) and as a result
I will have to re enter all the satellites.
As a result I am very ticked off that things were changed that cause all
Why can't the sat keps be simple text files that all use the same names and
no extra stuff.
This should not be this much of a problem.
I went through the keps that I receive each Friday and did not see vo-52
listed. Is it listed by another name. I can do 2&440 ssb and would like to
try to work it. I have 22C & pair 18C's on az/el rotor. Thanks for any info.