| |
CX2SA > SATDIG 13.03.09 22:24l 334 Lines 11579 Bytes #999 (0) @ WW
BID : 16647-CX2SA
Read: GUEST
Subj: AMSAT-BB-digest V4 121
Path: IZ3LSV<IQ3GO<SR1BSZ<ON4HU<PY4WVZ<CX2SA
Sent: 090313/2018Z @:CX2SA.LAV.URY.SA #:16647 [Minas] FBB7.00e $:16647-CX2SA
From: CX2SA@CX2SA.LAV.URY.SA
To : SATDIG@WW
Today's Topics:
1. PREDICT for DOS configuration question (Alan P. Biddle)
2. Re: QSL Etiquette (Kent Frazier)
3. QSL Etiquette (Darin Cowan)
4. The Goce Satellite Ion Engine (Bill Ress)
5. iss packet (Mr Jeffrey L Ross)
6. QSL Etiquette (John W Lee)
----------------------------------------------------------------------
Message: 1
Date: Fri, 13 Mar 2009 06:47:03 -0500
From: "Alan P. Biddle" <APBIDDLE@xxxxxx.xxx>
Subject: [amsat-bb] PREDICT for DOS configuration question
To: "AMSAT-BB" <amsat-bb@xxxxx.xxx>
Message-ID: <F739561BDA604166B9F079AF6CC5E116@xxxxxx>
Content-Type: text/plain; charset="us-ascii"
I have been looking at PREDICT for DOS, and have a question about
configuring individual satellites. A typical entry looks like this:
AO-16
07530
No alat/alon
Mode VU Transponder
145.850, 145.950
29.500, 29.400
No weekly schedule
No orbital schedule
end
That seems to imply that you can enter schedules, but none of the examples
provided provide any format information. Can someone confirm this, and if
so, give me a pointer to documentation, or even an example with weekly and
orbital schedule shown? Also, if you have an alat/alon, do you just enter
the numbers such as 0/0, or does it require something else on the line?
TNX,
Alan
-----------------------------------
Who is John Galt?
------------------------------
Message: 2
Date: Fri, 13 Mar 2009 07:16:28 -0500
From: Kent Frazier <k5knt.kent@xxxxx.xxx>
Subject: [amsat-bb] Re: QSL Etiquette
To: amsat-bb@xxxxx.xxx
Message-ID:
<92f8f1580903130516q6b3cf82y7a4519a3578cdabc@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Here is my experience from a newbie with 34 logged contacts, 16 confirmed.
I've received a couple of QSL cards (e and paper) that I didn't have any log
entries for or my log data was different. I record, or at least try to, all
my contacts and save the recordings as an .mp3 file. In the cases above, I
have attempted to email the sender and explain the discrepancy and ask if
they have an audio recording they could send in the case of it not being in
my log. If it is a data discrepancy I explain that and ask that they double
check their log. In one case the sender replied that he had indeed listed
the wrong satellite and would send me a new card.
I've also been on the other side. Last April my HD crashed, I lost my
logbook and I was unable to find any backup. Getting involved in other
things, I was "off the air" until this February when I happened across a
backup of my logbook in an old CD-R I was searching. I noticed that there
were some contacts I hadn't sent QSLs for nor received. I sent the QSLs
along with a note explaining the delay. Reading some of the responses I now
understand why I haven't received any replies <grin>. I did receive one card
returned explaining that the QSO was not in the log.
In the past, I have trimmed my recordings to only the time I make contact.
What I think I'm going to do now is also save the raw recording for a couple
of months incase I need to verify a questionable QSL either sent or
received.
73, Kent K5KNT
AMSAT #36765
ARRL
Sent from: San angelo TX United States.
------------------------------
Message: 3
Date: Fri, 13 Mar 2009 08:33:47 -0400
From: "Darin Cowan" <yet.another.squid@xxxxx.xxx>
Subject: [amsat-bb] QSL Etiquette
To: <amsat-bb@xxxxx.xxx>
Message-ID: <49ba52c1.9c53f10a.1595.ffffbabb@xx.xxxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"
If you didn't log the QSO, then reject the eQSL with a note that says "not
in my log"... That's what I do.
It happens sometimes when condx are marginal, like you're describing. It's
probably a bit disappointing for
the person at the other end, but sometimes that's just the way things work.
I'd rather keep my logs
relatively accurate.
Whether or not the request is truly bogus is sometimes hard to judge. Did
the person make this up, or did
he mis-copy the callsign: maybe he had a QSO with VE3OIG and wrote J in his
log by mistake? Or because I
mostly work digital modes, maybe noise munged the call a bit on his end and
he didn't notice. Don't chalk up
to malice what can be easily explained by error or incompetence :) For
satellite contacts, a person like me
who has less-than-perfectly-functional hearing may misinterpret an E for an
A, an F for an S, an M for an N
and so on. This is exascerbated when people don't use proper phonetics, so
it happens that I mis-copy
callsigns far too often for me to be happy with. I've had QSLs sent back
from people who didn't know what
the card was for simply because It went to KW#XXX instead of KD#XXX or
DE#YYY instead of DA#YYY. And that's
not calls I think are questionable... those are honest errors where I'm
convinced I got it right.
If conditions are marginal and I'm not truly sure, I tend not to QSL and
will leave a sticky note on my
desk for about a month. If I get a QSL with information matching a note, I
give the benefit of the doubt.
Otherwise, I periodically clean up the notes and then the information is
forever gone as if it never
happened.
I've only ever received a handful of truly bogus QSLs, and they've all been
SWL. In each case, the sender
clearly read spots I put on the DX cluster and sent me a QSL as if he heard
me in a QSO with the station
I spotted. Those go straight into the shredder without comment. Now I
reject SWL QSLs for anything that
shows up on a cluster, even if it is valid.
73 de VE3OIJ
-Darin
-----Original Message-----
From: "Ian" <Ian@xxxxxxxxxxxxx.xxx>
Subject: [amsat-bb] QSL Etiquette
Message-ID: <E06287B5F4054BFC8818E16E99D2FDF0@xxxxxxxxxxxxxx>
I was wondering what others may be doing when they receive an
"questionnable" request for a QSL. Last week while on vacation in Orlando I
attempted to make some AO51 contacts with a handheld station. Althought I
was receiving many stations, I was unsuccesful in establishing a contact and
never heard anyone call me back. I must have been getting out though as I
have received an eQSL request from a South American station. Is it normal
practice to ignore the request or to reply with refusal to QSL. If it were a
mistaken callsign situation I would reply with a "sorry" but in the case of
a bogus request I was wondering what others may be doing.
Next time I will use a better antenna hi hi.
Thanks & 73
Ian VE9IM
------------------------------
Message: 4
Date: Fri, 13 Mar 2009 08:24:50 -0700
From: Bill Ress <bill@xxxxxxxxxxx.xxx>
Subject: [amsat-bb] The Goce Satellite Ion Engine
To: amsat-bb@xxxxx.xxx
Message-ID: <49BA7AC2.8090305@xxxxxxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Following up on David's (G0MRF) post about the ion engine, the ESA Goce
satellite mission, due to launch next week, uses a nifty ion engine
which you can see at:
http://news.bbc.co.uk/1/hi/sci/tech/7935621.stm
I believe these engines will soon become "practical" for use in
satellite orbital modification. David presented a fine paper at the 2008
AMSAT Symposium in Atlanta showing how it would be possible to launch
(relatively inexpensively) to LEO and then over time, using small thrust
engines, modify the orbit to MEO. He also shows how the MEO orbit could
provide a significant portion of a HEO's orbit visibility time.
Possibly a reduced cost way to achieve extended satellite visibility at
a price tag much less than the $8 to $10 million dollar GTO launch cost.
If any of our members/readers have leads/contacts with folks doing ion
engine development work that might be looking for a satellite test
vehicle, please contact me off list.
Regards...Bill - N6GHz`
------------------------------
Message: 5
Date: Fri, 13 Mar 2009 12:12:11 -0400
From: "Mr Jeffrey L Ross" <radiooperator@xxxxxxx.xxx>
Subject: [amsat-bb] iss packet
To: "amsat" <amsat-bb@xxxxx.xxx>
Message-ID: <3B3463EB56554B89B757DF373525B4CD@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
hi folks, looks like she is on. I even got myself on the map, neat. 73 all,
come on up
kc8gkf
145.825 1200 baud
------------------------------
Message: 6
Date: Fri, 13 Mar 2009 09:11:52 -0800
From: John W Lee <k6yk@xxxx.xxx>
Subject: [amsat-bb] QSL Etiquette
To: amsat-bb@xxxxx.xxx
Message-ID: <20090313.092509.3580.1.k6yk@xxxx.xxx>
Content-Type: text/plain; charset=us-ascii
Guys,
As a little background, I have been a ham for over 50 years and
QSL'ing has been a big part of my activities since they are required
for awards. And I just plain like QSL cards! I respond to every
card that comes to me.
There are so many messages from people who say they don't have time
to QSL, etc. When I was a QSL manager (see below) I was working
full-time, had a 2 hour each way commute, was married with 2 kids to
raise.
I was one of the QSL managers for the YASME DXpeditions of the
1970's. W6KG and W6QL went to many countries during that period
and made between 8000 and 10,000 QSO's at each place. The logs
were all hand-written and in 3 ring binders for each location.
QSL cards would come in the mail in big bundles with rubber bands around
them daily, and the bureau cards would come in cardboard boxes of maybe
25-30 pounds via UPS!
I found LOTS of people who were NOT in the log! And I really tried to
help them by looking at different days, different times because they put
the wrong
time/date on them, etc. And I was able to find a lot of them that way.
Some people have not yet learned to use UTC time/date. This is a must.
If I couldn't find them anywhere in the log, I'd just write "Sorry, not
in the log"
on their card and send it back. That way they would know that their card
made it
to the manager and didn't get lost in the mail.
Of course good logging is a must also. I have every logbook from day one
of my ham
career. They are archived in boxes but I can pull one out and check for
something if
I need to. And I have received cards 10 years or more after the QSO.
I keep about
5 year's logs handy, as well as having a log in the computer which I
back up at least
monthly.
If you work somebody and you don't get the call or don't think you have
it correct,
by all means ask the person to give it again (slowly or in phonetics,
whatever it takes)!
A legal QSO should contain the time and date, other station's callsign
and some other
bit of information such as a signal report, grid locator, name, QTH, etc.
What did we do before E-mail? We copied everything down correctly !
We did not write to somebody asking for their callsign or wondering if we
made a QSO.
Regarding E-QSL and LOTW, with E-QSL, if the QSO information matches,
you get a
confirmation. You can "fudge" and confirm a contact that is not in the
log. This is not good.
With LOTW you can't. If the information does not match.
If you are new to QSL'ing or new to ham radio, I hope this helps you.
73,
John K6YK
then there is no confirmation. That's the way it should be.
____________________________________________________________
Free information on Digital Photography. Click Now!
http://thirdpartyoffers.juno.com/TGL2141/fc/BLSrjpTDvmQzkOdsfjz315gMfwcMZqYgHk
KkiBZ4eVrGCUXDK2GyQUPnDPa/
------------------------------
_______________________________________________
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 4, Issue 121
****************************************
Read previous mail | Read next mail
| |
