<div>Looks the like Jason's beat me to the punch.</div>
<div> </div>
<div>With a cellphone, I have an LCD display and can correct my boo boo's. When I played with APRS TT back in 2001 time frame, I got mic-fright with it. I had to really concentrate to figure out what I wanted to type in before I keyed up and started. It was very intimidating. (honestly).</div>
<div> </div>
<div>If we had a way to see the numbers we've entered, or somehow compose a message / posit packet offline, then have a pic processor spit out the DTMF string for us, we'd have a winner. But then again, why not have the little pic processor spit out a normal packet? the answer may be that a 1200 baud AFSK packet can't be squirted in by holding a small device close to a microphone... the DTMF's can. So I could use this little cigarette sized black box with an lcd display on it to compose a position report "off line",then it would build the DTMF tones needed to convey my info. I would hold this near the mic of any radio or HT and vollia. This would be the deal maker. Preprogramming DTMFs in one or two memories is close, but no cigar. Along the same lines, we *could* compose aprs packets by hand, but we all use software to build the packets for us. This should be no different. The true "hacker"/ "uber geek" types can certainly punch all the right DTMF sequence, but to reach the masses, a helper device would go a long way toward general acceptance / useage.</div>
<div><br clear="all">Wes<br>---<br>God help those who do not help themselves.<br><br><br></div>
<div class="gmail_quote">On Fri, Jan 29, 2010 at 17:50, Robert Bruninga <span dir="ltr"><<a href="mailto:bruninga@usna.edu">bruninga@usna.edu</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">>> I have been trying for a few years to get<br></div>>> Echolink to add DTMF callsign decoding<br>
<div class="im">>> (with then a copy sent over to the<br>>> APRS-IS each time somone checks in using it)<br>><br></div>> Furthermore, [APRStt] has always been marketed as<br>
<div class="im">> "kludgy thing for this local grid in the event area".<br><br></div>Thanks for the feedback. I need to find out where that old<br>impression is coming from. For the past three years the<br>
emphasis has been completely on CALLSIGN encoding only. And<br>that requires the user to store his DTMF callsign in his DTMF<br>memory once. Then he can report his "position" anytime,<br>anywhere by pressing at most maybe 2 buttons. 1 to call up DTMF<br>
memory and the other to selct the memory. Done.<br><br>For the purpose of the global APRS system, a DTMF callsign is<br>all we need to hear. It gives us this info:<br><br>1) CALLSIGN<br>2) Date and Time of availability<br>
3) Location (to nearest RF area)<br>4) Frequency he reported in on<br>5) Type of system, and range<br>6) Echolink or IRLP or other call-back node nuumber or other<br>info.<br><br>For the purpose of facilitating comunicaiton between hams, the<br>
callsign, heard by an APRStt system is all we need.<br><br>And doing this two-button thing, and have the APRStt engine come<br>back with "Welcome WB4APR" is just as efficient as me picking up<br>the microphone and saying "WB4APR Mobile". But the big<br>
difference is that the 2 button DTMF report is MACHINE readable<br>and goes locally and globally. Where the voice report falls on<br>mostly deaf ears on one mostlly inactive repeater and goes<br>nowhere.<br>
<div class="im"><br>>> I am frustrated because these are trivial additions<br>>> that could seamlessly crossconnect info between these<br>>> two very powerful ham radio systems!<br>><br>> Sometimes your "trivial" is far from it. Next thing<br>
> is that you will hotly cry out and want bi-<br>> directionality for that "trivial" thing.<br><br></div>Absolutely. Once the report goes in, I want VOICE response.<br>Heck, I did it in 2000 and 2001 using BASIC and I had<br>
synthesized voice using only 8 resistors on the parallel port.<br>These days DTMF decoding by sound card and Voice synthesis by<br>sound card is something that lots of programmers can do. I just<br>need to find someone that wants to do it. And is motivated to<br>
stick with it...<br>
<div class="im"><br>> Sometimes old e-waste junk is just that, and<br>> not worth to turn specifications into prezels<br></div>> to try to support them.... but without a supply<br>
<div class="im">> of hundreds of pagers and all that device<br>> programming support hardware I see<br>> absolutely no point to spend time on it.<br><br></div>Yes, the pager idea is just one more potential side project.<br>
But the DTMF keypad is never going to go away and 99% of every<br>mobile or handheld operators has one. That is why I think that<br>APRStt is well worth the investment of time for someone that can<br>do it.<br>
<div class="im"><br>> I do not see APRStt as IMPROVEMENT of any kind.<br><br></div>Ah, too bad. Every kid with a cell phone can use a keypad to<br>communicate, Every ham radio has one. I simply canot see why<br>in 9 years it is so hard to find someone to tie the DTMF keypad<br>
to the local/global APRS communication system.<br><br>Still looking for talent...<br>Bob, Wb4APR<br>
<div>
<div></div>
<div class="h5"><br><br><br>_______________________________________________<br>aprssig mailing list<br><a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br><a href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
</div></div></blockquote></div><br>