<html><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:16px"><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yiv7030439494yui_3_16_0_1_1427657326315_2779">I have programmed other Kenwoods (TH-D7 .TH-F6 & 7, D700, TS2000)...</div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yiv7030439494yui_3_16_0_1_1427657326315_2823"> </div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yiv7030439494yui_3_16_0_1_1427657326315_2834">Generally on Kenwoods, they haven't had but one tone for T & R and the last command is what you will get, but the 72 has "Cross-Tone capability, though the manual didn't seem to explain setting it up very well.</div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_4071"> </div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_4072">I'll be interested to see if anyone has the commands. The info I have for the D710 from LA3QMA Kai Gunter Brandt et. al. does't have the isolated Subaudible commands, but should be the same/similar. I don't have a 710 or 72. </div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_4409"> </div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_4410">If anyone knows, I would think the CHIRP folks know:</div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_4412"><a id="yui_3_16_0_1_1427658595750_4411" href="http://chirp.danplanet.com/projects/chirp/wiki/Home">http://chirp.danplanet.com/projects/chirp/wiki/Home</a> </div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_4448">Thay had lots of people feeding them info on various radios to include. I just programmed the radios I have.</div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_4413"> </div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_3944">73, Steve, K9DCI</div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_3945">My Excel Radio Control sheets:</div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_4154"><font id="yui_3_16_0_1_1427658595750_3787" face="HelveticaNeue-Roman"><font id="yui_3_16_0_1_1427658595750_3786" face="HelveticaNeue-Roman"><font face="verdana, helvetica, sans-serif"> </font><a id="yui_3_16_0_1_1427658595750_4157" href="http://k9dci.home.comcast.net/site/?/page/Amateur_Radio_Control/"><font id="yui_3_16_0_1_1427658595750_4338" face="verdana, helvetica, sans-serif">http://k9dci.home.comcast.net/site/?/page/Amateur_Radio_Control/</font></a> </font></font></div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_4153"><font id="yui_3_16_0_1_1427658595750_4235" face="HelveticaNeue-Roman"><font id="yui_3_16_0_1_1427658595750_4234" face="HelveticaNeue-Roman"> </font></font></div><font id="yui_3_16_0_1_1427658595750_4155" face="HelveticaNeue-Roman"><font id="yui_3_16_0_1_1427658595750_4156" face="HelveticaNeue-Roman"><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_3788"></div></font><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_3788"></div></font><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" dir="ltr" id="yui_3_16_0_1_1427658595750_3788"> </div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" id="yiv7030439494yui_3_16_0_1_1427657326315_2790"></div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" id="yiv7030439494yui_3_16_0_1_1427657326315_2824"> </div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" id="yiv7030439494yui_3_16_0_1_1427657326315_2826"><div id="yiv7030439494yui_3_16_0_1_1427657326315_2825">--
<br clear="none">Regards, Steve Noskowicz
<br clear="none">Science & Technical Adviser
<br clear="none"> http://www.challengerillinois.org/
<br clear="none"></div></div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" id="yui_3_16_0_1_1427658595750_3865"><br clear="none"> </div><div class="qtdSeparateBR"><br><br></div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);" id="yiv7030439494yqt47746" class="yiv7030439494yqt7962408854"><div style="font-family: verdana, helvetica, sans-serif; font-size: 16px;" id="yiv7030439494yui_3_16_0_1_1427657326315_2870"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yiv7030439494yui_3_16_0_1_1427657326315_2869"> <div dir="ltr" id="yiv7030439494yui_3_16_0_1_1427657326315_2875"> <hr SIZE="1"> <font id="yui_3_16_0_1_1427658595750_3864" size="2" face="Arial"> <b><span style="font-weight: bold;">From:</span></b> Kenneth Finnegan <kennethfinnegan2007@gmail.com><br clear="none"> <b><span style="font-weight: bold;">To:</span></b> TAPR APRS Mailing List <aprssig@tapr.org> <br clear="none"> <b><span style="font-weight: bold;">Sent:</span></b> Saturday, March 28, 2015 10:16 PM<br clear="none"> <b><span style="font-weight: bold;">Subject:</span></b> Re: [aprssig] APRS freq spec questions<br clear="none"> </font> </div> <div id="yiv7030439494yui_3_16_0_1_1427657326315_2868" class="yiv7030439494y_msg_container"><br clear="none">To answer one of my own questions on this, testing the T vs C access<br clear="none">commands with K4JH on his THD72a, it appears that I guessed correctly.<br clear="none">T100 will configure your radio to only encode a PL of 100Hz, where<br clear="none">C100 configures your radio to both encode and decode 100Hz. I would be<br clear="none">interested in seeing how radios respond to both at once ("T100 C127").<br clear="none">--<br clear="none">Kenneth Finnegan<br clear="none"><a href="http://blog.thelifeofkenneth.com/" shape="rect" rel="nofollow" target="_blank">http://blog.thelifeofkenneth.com/</a><br clear="none"><br clear="none"><br clear="none">On Mon, Mar 16, 2015 at 2:17 PM, Kenneth Finnegan<br clear="none"><<a href="mailto:kennethfinnegan2007@gmail.com" shape="rect" rel="nofollow" target="_blank" ymailto="mailto:kennethfinnegan2007@gmail.com">kennethfinnegan2007@gmail.com</a>> wrote:<br clear="none">> Greetings fellow APRSers,<br clear="none">><br clear="none">> First, a quick note: my master thesis on APRS has been defended and<br clear="none">> accepted, so you can now retrieve the final draft of my thesis online<br clear="none">> here: <a href="http://digitalcommons.calpoly.edu/theses/1341/" shape="rect" rel="nofollow" target="_blank">http://digitalcommons.calpoly.edu/theses/1341/ </a>There are still<br clear="none">> some issues/typos in that document, but it has been set in stone and<br clear="none">> I'm moving on with life.<br clear="none">><br clear="none">> Having taken a hiatus from APRS and writing for a few months in the<br clear="none">> search for a job (which still hasn't born fruit yet...), I'm starting<br clear="none">> to again poke at my notes from my thesis where topics didn't make the<br clear="none">> cut for the limited scope of my thesis. I completely ignored the<br clear="none">> contents of APRS packets, so now that I'm FREE of the reigns of an<br clear="none">> academic institution dangling a piece of wallpaper over my head, I can<br clear="none">> start look at APRS with much smaller brush strokes.<br clear="none">><br clear="none">> Let us talk about the frequency spec:<br clear="none">> <a href="http://www.aprs.org/info/freqspec.txt" shape="rect" rel="nofollow" target="_blank">http://www.aprs.org/info/freqspec.txt </a>What follows is a few point by<br clear="none">> point interpretations, questions, and suggestions based on a casual<br clear="none">> reading of the 9 May 12 freq spec.<br clear="none">><br clear="none">><br clear="none">> The way I read it, the freq spec consists of a 10 octet frequency,<br clear="none">> followed by a number of optional five or ten octet modifiers. The spec<br clear="none">> seems to imply that these modifiers are limited to two, but that seems<br clear="none">> arbitrary and limiting to me. I would suggest that an arbitrary number<br clear="none">> of modifier fields be explicitly allowed. Clients MUST parse at least<br clear="none">> two fields, but may continue to parse modifier fields until they reach<br clear="none">> the end of the comment text or a modifier that they do not understand/<br clear="none">> appears to have a syntax error.<br clear="none">><br clear="none">> The freq is expressed via "###.###MHz", or "###.## MHz" if the ones of<br clear="none">> kHz doesn't need to be specified. This seems odd to me to complicate<br clear="none">> this spec by allowing a space. When would a user only want to specify<br clear="none">> a frequency to 10kHz instead of 1kHz resolution?<br clear="none">><br clear="none">> What is the expected behavior below 100MHz? Should the number be zero<br clear="none">> padded ("052.525MHz"), space padded (" 52.525MHz"), or left justified<br clear="none">> ("52.525MHz")? This last one violates the 10 octet rule for the<br clear="none">> primary frequency term.<br clear="none">><br clear="none">> What is the expected behavior for frequencies >1GHz? Should they<br clear="none">> continue to be expressed to one hundredths of MHz? ("1286.200MHz" -<br clear="none">> This violates the ten octet rule) Should they be allowed to float the<br clear="none">> decimal place? ("1286.20MHz" - This is a bloodly mess for static<br clear="none">> parsers) Should they be allowed to specify their frequency in GHz to<br clear="none">> the least significant digit that isn't zero? ("1.2862GHz" - Often<br clear="none">> violates the ten octet rule and a freaking disaster for stupid<br clear="none">> parsers) I would suggest we allow higher frequencies to break the ten<br clear="none">> octet rule and keep everything in MHz.<br clear="none">> Edit: I now finally see the MICROWAVES section at the bottom... I<br clear="none">> don't know how I feel about this solution vs those considered above...<br clear="none">> This plus the delimiter issue (" ", "/", or "" after 7 octet data<br clear="none">> extensions) means to me that pretty much the only way to find the<br clear="none">> start of a freq spec is to scan the entire comment field for [0-9A-O<br clear="none">> ]?[0-9][0-9]\.[0-9][0-9][0-9 ][MG]Hz and start there...<br clear="none">><br clear="none">> Moving on to the modifier terms... Every modifier term consists of a<br clear="none">> space, one identifier, and three octets of payload (with the exception<br clear="none">> of the rx freq term).<br clear="none">><br clear="none">> I would suggest that FFF.FFFrx follow the same convention as the<br clear="none">> primary frequency in that it is always expressed in MHz, allowed to<br clear="none">> violate the ten octet rule for >1GHz frequencies, and follow the same<br clear="none">> conventions for <100MHz padding.<br clear="none">><br clear="none">> There are three squelch access modifiers: T, C, and D. The case of<br clear="none">> this identifier specifies the channel bandwidth, so uppercase TCD<br clear="none">> indicates 25kHz channels, and lowercase tcd indicates 12.5kHz<br clear="none">> channels. I'm ok with limiting this to those two bandwidths.<br clear="none">><br clear="none">> What is the difference between the T tone and C CTCSS terms? I'd guess<br clear="none">> that it means that a T repeater has tone access but carrier squelch,<br clear="none">> where CTCSS allows the users to both encode and decode PL. Is this<br clear="none">> correct?<br clear="none">><br clear="none">> What about repeaters with split PLs? (Which I deal with regularly due<br clear="none">> to passive intermod issues) I would suggest that we allow two access<br clear="none">> modifiers, where the first is the user encode frequency, and the<br clear="none">> second is the user decode frequency.<br clear="none">> For example, the W6BHZ VHF repeater (which has a 91.5Hz input and<br clear="none">> 127.3Hz output) would then be expressed as "146.760MHz T091 C127<br clear="none">> -060". The UHF side uses 127.3Hz on both input and output, and should<br clear="none">> be expressed as "442.300MHz C127 +500"<br clear="none">> A repeater using digital input and PL output would be "FFF.FFFMHz D023<br clear="none">> C127", PL input and digital output as "FFF.FFFMHz T127 D023", a<br clear="none">> repeater using identical digital codes be "FFF.FFFMHz D023" and split<br clear="none">> codes as "FFF.FFFMHz D023 D754" (not that I think anyone would want to<br clear="none">> do that... but that's a mechanism vs policy issue)<br clear="none">><br clear="none">> Are all tone bursts >1kHz? 1750Hz is the only one I've heard of. I<br clear="none">> dislike the replacing a 1 with an l trick...<br clear="none">><br clear="none">> I'm ok with limiting the +### and -### to 10kHz-9.99MHz splits.<br clear="none">> Anything beyond that includes a FFF.FFFrx modifier instead. Sucks to<br clear="none">> be a 23cm repeater on APRS, I guess... (i.e. W6PIY/1.2GHz becomes<br clear="none">> "1286.200MHz 1274.200rx C100") I'd be more comfortable with saying<br clear="none">> "implicit offsets are implicit" if the freq spec included that list of<br clear="none">> standard repeater offsets, but that's another whole can of worms...<br clear="none">><br clear="none">> I look forward to any comments. I'm sorry I keep showing up just to<br clear="none">> stir the pot around here.<br clear="none">> --<br clear="none">> Kenneth Finnegan, W6KWF<br clear="none">> <a href="http://blog.thelifeofkenneth.com/" shape="rect" rel="nofollow" target="_blank">http://blog.thelifeofkenneth.com/</a><br clear="none">_______________________________________________<br clear="none">aprssig mailing list<br clear="none"><a href="mailto:aprssig@tapr.org" shape="rect" rel="nofollow" target="_blank" ymailto="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br clear="none"><a href="http://www.tapr.org/mailman/listinfo/aprssig" shape="rect" rel="nofollow" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br clear="none"><br clear="none"><br clear="none"></div> </div> </div></div><div style="color: rgb(0, 0, 0); font-family: verdana, helvetica, sans-serif; font-size: 16px; background-color: rgb(255, 255, 255);"> </div></div></body></html>