[amsat-bb] QIKCOM-2 SPoken Messages (DOVE-17's speech?)

Jim White jim at coloradosatellite.com
Mon Jul 27 13:24:26 UTC 2015


As I recall that was the only message that I left in DOVE for any period 
of time.  The memory fades but I think I had some other messages loaded 
for just a couple of minutes while testing and trying to get that one to 
sound right.  I just dug through my hard drive archives from the DOVE 
days and did not find any other messages.  Those test messages would 
have been transmitted only briefly while over my Colorado QTH.

It took a couple of hundred hours to get that message to sound right.  
Some of that was learning curve, but DOVE voice message creation was a 
slow, iterative multi-step process of hand entering hex codes 
representing phonemes strung together to make words, along with other 
hex codes to change inflection and pitch (like the "down" inflection at 
the end of the word "space"), then assembling them into 68HC11 op codes.

Unfortunately that message was only on DOVE for a few months before it 
died.  I received a call one day that the voice was garbled.  I reset 
the voice hardware and reloaded the hex file that drove it but it never 
pronounced phoneme strings after that.  We presumed at the time that a 
single event upset or cumulative radiation dose had permanently damaged 
the voice hardware.


On 7/27/2015 6:35 AM, Robert Bruninga wrote:
> Did DOVE OSCAR-17 ever say anything other than the “Hi, this is Dove in
> Space” as recorded here:
> http://www.dd1us.de/sounds/DO-17.mp3
> That’s from a fantastic page I just found that has sounds from many
> satellites!
> http://www.dd1us.de/spacesounds%202c.html
> I’d like to put ananniversary copy of its best known announcement on QIKCOM
> I remember copying its telelmetry all the time, but I just don’t remember
> the voice.
> Bob
> *From:* Robert Bruninga [mailto:bruninga at usna.edu]
> *Sent:* Sunday, July 26, 2015 4:12 PM
> *To:* amsat bb
> *Cc:* Robert Bruninga
> *Subject:* Re: QIKCOM-2 SPoken Messages
> AMSAT Armchair "contact" lawyers:
> Continuing with the DTMF message ideas. What kind of exchange "counts" for
> satellite contacts?  (where counting matters)?  Does it really have to be
> CQ... QSL... and then QSL ...?
> For the DTMF Voice system, we could have two more messages:
> " CQ Satellite, my number is *"  (the satellite assigns the digit *)
> " QSL number _, my number is *" (station enters the _ in his reply)
> Usage would be:
> A station sends a DTMF uplink message "WB4APR says CQ Satellite my number
> is X".
> A responding station sends "W3ADO says QSL number X, my number is Y"
> Finishing it off with "WB4APR says QSL number Y, my number is X.
> Another station joins in "W4XYZ says QSL number X, my number is Z
> and the reply could be "WB4APR says QSL Number Z, my number is X...
> WB4APR made two valid contacts with XYZ and ADO.
> In otherwords is that  required for an exchange?  The number for "My number
> is *." is assigned sequencially for the pass, so that it is unique.  The
> QSL station always has to enter the number of the matching station to which
> he is responding.
> Just a thought.  Or does anyone give a hoot about counting satellite
> "contacts"?
> Bob, Wb4APR
> On Sun, Jul 26, 2015 at 2:02 PM, Robert Bruninga <bruninga at usna.edu> wrote:
> In addition to all of the numbered ARL messages, we have now implemented all
> of these additional messages (as adjusted to fit) and found it was trivial
> to include a "0-9" modifier in messages... wherever a " _" appears.  There
> is still some room.
> Remember, for the sender using DTMF the message and callsign always fits
> into 16 digits from the DTMF keypad.  The format is:
>    CeMMxCCCCCCpppp#
> Where e is an emergency flag which, along with x, must be 9 if this is a
> true emergency message otherwise it says "TEST ... "
> Where MM is the message number (00 to 99)
> Where x is a numeric modifier for messages with a "_" in them.
> Where CCCCCC is the callsign in DTMF and pppp is the key position codes for
> the 6 letters
> See http://aprs.org/qikcom-2.html
> Here are the new  ones implemented.
> ------------------------
> W2JV suggested: “Greetings from AMSAT.  Keeping ham radio in space over 44
> years”.
> ------------------------
> WA1KAT suggested:
> There is no cell service here.
> Cell battery is dead.
> Cell power charging is limited.
> Radio power charging is limited.
> Next contact time available in 90 minutes.  (time of one full orbit)
> Next contact time is tomorrow.
> Contact me on _ Meter band. (interpret as 1=160, 2=2m, 3=30, 8=80, etc)
> --------------------------
> Bob added:
> Demonstrating APRStt at Hamfest
> Demonstrating APRStt to friends
> I am on schedule.
> I may be delayed _ hours
> I may be delayed _ days
> I may be early _ hours
> I May be early _ days
> I may quit early  _ stops
> I may go farther _ stops
> We are camping and enjoying it greatly.
> We are hiking and enjoying it greatly.
> Call me on my cell.
> Call my cell on the hour.
> Please Send items number _.     (1=Money,2= food, water, supplies, shoes,
> sleeping bag, blanket,fuel)
> We are operating on emergency power.
> We are operating on solar power.
> Just thinkin...
> Bob, WB4APR
> On Wed, Jul 22, 2015 at 11:11 PM, Robert Bruninga <bruninga at usna.edu> wrote:
> Inviting proposed standard messages for the next APRS Satellite:
> Our next QIKCOM-2 APRS satellite will accept 2 digit uplink DTMF messages to
> be spoken on the downlink.  We have already programmed all of the ARRL
> standard radio grams and emergency messages.
> But there is room for more.  So think....  What kind of message would you
> want to send (that is not included in the existing ones) from your HT out in
> the wilderness.  At a hamfest?  or any other HAM Radio event or opportunity.
> Keep them simple and of the same order of length as the existing ones.
> The existing ones are listed here:
> http://nts.ema.arrl.org/node/30
> But the implementation cannot include blanks for fill-in like the regular
> ones.  But any sentence that stands alone can work.
> Just thought I'd open it up.  Plenty of RAM and only 1 week before
> delivery...
> Serious considerations only.  Thanks
> Bob, WB4APR
> _______________________________________________
> Sent via AMSAT-BB at amsat.org. 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

More information about the AMSAT-BB mailing list