<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
I would be more then happy to sit down with you and your system on the other side of<br>a telephone conversation, and hack our way through it. When is good for you?<br><br>Jim WB6NIL<br><br>> Date: Sun, 4 May 2008 22:07:00 -0700<br>> From: dpowellwilliams@shaw.ca<br>> To: app_rpt@lists.illiana.net<br>> Subject: [App_rpt] Kenwood TM-271<br>> <br>> Hello Group:<br>> <br>> Anybody out there interfaced a TM-271 (or 471) as a remote base with<br>> app_rpt?<br>> <br>> I had hoped that modern Kenwood mobile radios would share a common<br>> programming protocol. The app_rpt mentions the TM-G707 as an example of a<br>> radio that can be used with the rpt.conf option 'remote=kenwood'. However,<br>> it does not work for me using the TM-271.<br>> <br>> I built up a RS-232 to TTL interface which works fine with the Kenwood<br>> programming software but not with app_rpt. Recalling a memory channel or<br>> setting a VFO frequency results in an 'invalid frequency' callout from<br>> Asterisk.<br>> <br>> Looking through the app_rpt source function 'setkenwood', I see the string<br>> 'VMC 0,0' is sent to the radio initially. When I monitor the serial data<br>> from Asterisk to the radio, this string is sent but the radio's response is<br>> '?' (0x3F). One suspects this isn't the right answer.<br>> <br>> Does anyone have experience or suggestions with the TM-217 on app_rpt?<br>> <br>> 73,<br>> <br>> Dave<br>> VE7MQ.<br>> <br>> _______________________________________________<br>> App_rpt mailing list<br>> App_rpt@lists.illiana.net<br>> http://lists.illiana.net/mailman/listinfo/app_rpt<br></body>
</html>