| |
CX2SA > SATDIG 28.07.15 03:18l 1251 Lines 42441 Bytes #999 (0) @ WW
BID : AMSATBB10223
Read: GUEST
Subj: AMSAT-BB-digest V10 222
Path: IW8PGT<IZ3LSV<IW0QNL<VE2PKT<CX2SA
Sent: 150728/0109Z @:CX2SA.SAL.URY.SOAM #:24813 [Salto] FBB7.00e $:AMSATBB10223
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Re: QIKCOM-2 SPoken Messages (DOVE-17's speech?) (Robert Bruninga)
2. Re: QIKCOM-2 SPoken Messages (Valid Contacts) (Robert Bruninga)
3. Re: QIKCOM-2 SPoken Messages (Valid Contacts) (Paul Stoetzer)
4. Re: Rotor Controllers (Mark Johns)
5. Re: QIKCOM-2 SPoken Messages (DOVE-17's speech?) (Jim White)
6. Re: QIKCOM-2 SPoken Messages (Valid Contacts - DONE!)
(Robert Bruninga)
7. Re: QIKCOM-2 SPoken Messages (Valid Contacts) (Bruce)
8. Re: QIKCOM-2 SPoken Messages (Valid Contacts - DONE!) (Bruce)
----------------------------------------------------------------------
Message: 1
Date: Mon, 27 Jul 2015 08:35:22 -0400
From: Robert Bruninga <bruninga@xxxx.xxx>
To: amsat bb <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] QIKCOM-2 SPoken Messages (DOVE-17's speech?)
Message-ID: <7cabec06b14634a759a83ef584adbef5@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
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@xxxx.xxxx
*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@xxxx.xxx> 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@xxxx.xxx> 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
------------------------------
Message: 2
Date: Mon, 27 Jul 2015 08:48:33 -0400
From: Robert Bruninga <bruninga@xxxx.xxx>
To: amsat bb <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] QIKCOM-2 SPoken Messages (Valid Contacts)
Message-ID: <48f4f6084cd73764e9fdfe1f62fa9d39@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
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@xxxx.xxxx
*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@xxxx.xxx> 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@xxxx.xxx> 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
------------------------------
Message: 3
Date: Mon, 27 Jul 2015 09:05:13 -0400
From: Paul Stoetzer <n8hm@xxxx.xxx>
To: Robert Bruninga <bruninga@xxxx.xxx>
Cc: amsat bb <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] QIKCOM-2 SPoken Messages (Valid Contacts)
Message-ID:
<CABzOSOri9vqV+3vH6w_wRv_CJYjzrQDJAEr5S8EqfU384nKwGg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
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@xxxx.xxx> 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@xxxx.xxxx
> *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@xxxx.xxx> 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@xxxx.xxx> 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@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: 4
Date: Mon, 27 Jul 2015 13:05:53 +0000 (UTC)
From: Mark Johns <mjohns166@xxxxx.xxx>
To: Bill Booth <ve3nxk@xxxxx.xxx>, AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Rotor Controllers
Message-ID:
<1624300238.2914585.1438002353663.JavaMail.yahoo@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
The K3NG Rotator Controller is an Arduino project that may require getting
your hands dirty or (horrors!) plugging in a soldering iron. But it can be
programmed for a wide range of rotators and input software.
http://blog.radioartisan.com/yaesu-rotator-computer-serial-interface/
--
Mark D. Johns, K?MDJ
Decorah, Iowa USA EN43
-----------------------------------------------
"Heaven goes by favor; if it went by merit,
you would stay out and your dog would go in."
---Mark Twain
----- Original Message -----
From: Bill Booth <ve3nxk@xxxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Cc:
Sent: Sunday, July 26, 2015 7:05 AM
Subject: [amsat-bb] Rotor Controllers
Wanting to upgrade my ham computer from XP/P4 to something newer and faster.
Have
used Nova, AEA ST-1, and Yaesu G-5500 for ever. Have a nice HP quad core
machine
with W7, that I cannot get to work with the ST-1, says cannot initialize port.
Tried a couple of other units with same results, so I suspect it has
something to
do with the newer parallel ports.
So what am I missing ???
I would prefer to use a USB port of course, but cannot find any controllers
now
that are ready to go, or will work with Nova. I am trying to stay with Nova
and
the Yaesu G-5500
What is everyone else using these days?
--
Bill Booth VE3NXK
Sundridge ON, Canada
79.23.37 W x 45.46.18 N
FN05ns
Visit my weather WebCam at http://www.almaguin.com/wxcurrent/weather.html
Organ and Tissue Donation - The Gift of Life
Talk to your family. Your decision can make a difference.
_______________________________________________
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: 5
Date: Mon, 27 Jul 2015 07:24:26 -0600
From: Jim White <jim@xxxxxxxxxxxxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] QIKCOM-2 SPoken Messages (DOVE-17's speech?)
Message-ID: <55B6310A.20101@xxxxxxxxxxxxxxxxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed
Bob,
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.
Jim
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@xxxx.xxxx
> *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@xxxx.xxx> 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@xxxx.xxx> 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@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: Mon, 27 Jul 2015 10:25:17 -0400
From: Robert Bruninga <bruninga@xxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] QIKCOM-2 SPoken Messages (Valid Contacts -
DONE!)
Message-ID: <6460f1ece8b61a79254e3c8dcc4b8de7@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
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@xxxxx.xxx [mailto:prstoetzer@xxxxx.xxxx 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@xxxx.xxx> wrote:
> Maybe what I really need to know, is whether a grid exchange is
> required to constitute a valid sn 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@xxxx.xxx>
> 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@xxxx.xxx>
> wrote:
> Inviting proposed standard messages for the next APRS _______________________________________________
> 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: 7
Date: Mon, 27 Jul 2015 09:28:48 -0500
From: Bruce <kk5do@xxxxx.xxx>
To: Robert Bruninga <bruninga@xxxx.xxx>, amsat bb <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] QIKCOM-2 SPoken Messages (Valid Contacts)
Message-ID: <55B64020.1080104@xxxxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed
I might chime in here. A contact with a satellite does not qualify as
a contact for ARRL purposes. A contact through a satellite does. For
example, as Bob suggests, you say here I am and the satellite says here
I am. That is not a contact as it is not two hams making a contact
THROUGH a satellite. We had this same discussion back in the RS robot
satellite days in the 90's. If you were lucky enough to get your signal
into the RS robot just right, it came back and talked to you and gave
you a contact number. But, it was not a two-way contact.
If we apply the ARRL Worked All States rules....
"Contacts made through repeaters or any other power relay method cannot
be used for WAS credit. A WAS award is available for Satellite contacts.
All stations contacted must be ?land-based stations.? Contacts with
ships, anchored or otherwise, and aircraft cannot be counted."
Then the satellite talking would not count as both stations are not
land-based.
If we look at the ARRL VUCC rules....
"No contacts through active repeaters are permitted, except for
Satellite Awards."
Thus, both stations did not operate "through" a satellite, one was the
satellite.
ARRL DXCC rules are the same...
"*6. All contacts*must be made with amateur stations working in the
authorized amateur bands or with other stations licensed or authorized
to work amateurs. Contacts made through "repeater" devices or any other
power relay methods (other than satellites for Satellite DXCC) are not
valid for DXCC credit. "
It is like the little Sputnik that went up for the 50th anniversary and
gave out messages from all over the world. If you copied it, you got a
certificate. However, had they added your call sign to the message, you
could not have been able to use it for an award (VUCC, WAS, DXCC)
because the contact was not through the satellite but with the satellite.
Now, I might suggest that we offer an AMSAT award for this satellite or
one be sponsored by a group. For AMSAT to offer an award, it must be
available to be earned by any ham worldwide and not be a contest.
73...bruce
On 7/27/2015 7:48 AM, Robert Bruninga 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@xxxx.xxxx
> *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@xxxx.xxx> 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@xxxx.xxx> 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@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
--
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
------------------------------
Message: 8
Date: Mon, 27 Jul 2015 09:30:00 -0500
From: Bruce <kk5do@xxxxx.xxx>
To: Robert Bruninga <bruninga@xxxx.xxx>, amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] QIKCOM-2 SPoken Messages (Valid Contacts -
DONE!)
Message-ID: <55B64068.6080706@xxxxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed
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@xxxxx.xxx [mailto:prstoetzer@xxxxx.xxxx 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,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@xxxx.xxx>
>> 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?.
>> ------------------------
>> WA1t 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@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
--
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
------------------------------
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 222
*****************************************
Read previous mail | Read next mail
| |
