[amsat-bb] QIKCOM-2 SPoken Messages (Valid Contacts - DONE!)

Bruce kk5do at amsat.org
Mon Jul 27 14:30:00 UTC 2015


This would work... after all the looking up of the rules on the previous 
message.

73...bruce

On 7/27/2015 9:25 AM, Robert Bruninga wrote:
> Frank K5HS  (ex KR1ZAN) came up with an excellent suggestion.  Simply add
> the revolving QSO number to the downlinked GRID report!
>
> Then we need only the QSL message so that both stations can QSL each others
> grid!...  So the DTMF grid will come down now as:
>
> "Grid FM19 from WB4APR QSO number X."
>
> A reply DTMF QSL message from someone else will be "W3ADO says QSL QSO
> number _. Thanks for the contact".
>
> Done.  And this is an elegant simple solution that fits and the CPU only has
> 8 bytes of program memory left! (but 12k of message memory left)...
>
> Bob, Wb4APR
>
> -----Original Message-----
> From: prstoetzer at gmail.com [mailto:prstoetzer at gmail.com] On Behalf Of Paul
> Stoetzer
> Sent: Monday, July 27, 2015 9:05 AM
> To: Robert Bruninga
> Cc: amsat bb
> Subject: Re: [amsat-bb] QIKCOM-2 SPoken Messages (Valid Contacts)
>
> Generally a QSO is considered to be an exchange of calls and one other piece
> of information - whether that's a signal report, grid square, serial number,
> name, etc.
>
> 73,
>
> Paul, N8HM
>
> On Mon, Jul 27, 2015 at 8:48 AM, Robert Bruninga <bruninga at usna.edu> wrote:
>> Maybe what I really need to know, is whether a grid exchange is
>> required to constitute a valid satellite contact, or just an exchange of
>> calls?
>>
>>
>>
>> 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
> _______________________________________________
> 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


-- 

Bruce Paige, KK5DO
                      
AMSAT Director Contests and Awards
   
ARRL Awards Field Checker (WAS, 5BWAS, VUCC), VE
           
Houston AMSAT Net - Wed 0100z on Echolink - Conference *AMSAT*
Also live streaming MP3 at http://www.amsatnet.com
Podcast at http://www.amsatnet.com/podcast.xml or iTunes
               
Latest satellite news on the ARRL Audio News
http://www.arrl.org

AMSAT on Twitter http://www.twitter.com/amsat




More information about the AMSAT-BB mailing list