<div>I'd have to look to be sure, but the first byte is comprised of a command and port number. there are 4 commands... TX (0), txdelay (1), persistence(2) and slot time (3). The upper nibble is the port number (or the upper nibble). So sending 192,0,<your packet>,192. will make the packet squirt out port 0. transmitting 192,16,<your packet>,192 should squirt a packet out port 1. Since most TNC's have only one port anyway this is pretty much a moot point since you'll always use 00 for the two command nibbles. Also, most kantronic TNCs have a separate TX delay and slot time for kiss mode, so you will need to set them if the txd is too long or so short that your packets aren't decoded.</div>
<div> </div>
<div>Also, there is a difference between TAPR 2 and KPC products on the air... I also can't recall this detail exactly, but something to do with the way multiple frames are placed into one packet. One of them adds an extra byte at the end, the other adds the extra delimiter byte only when necessary. </div>
<div> </div>
<div>And finally, you will have to watch the 192 ($c0) appearing in the packet. You'll have to encode a transposition character. See <a href="http://www.ka9q.net/papers/kiss.html">http://www.ka9q.net/papers/kiss.html</a> for the nitty gritty.</div>
<div><br clear="all">Wes<br>---<br>Hitler gave great speeches too!<br><br><br></div>
<div class="gmail_quote">On Mon, Aug 3, 2009 at 10:29, Jason Rausch <span dir="ltr"><<a href="mailto:jason@ke4nyv.com">jason@ke4nyv.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"><br>Rob,<br><br>I ran into a few things that kept me from transmitting as well. One was the port byte indicator. I would have to go back and look at the spec to tell you where it goes, but it is one of the first bytes after the first FEND. Also, when you saw "raw packet" wrapped in FENDs, does that mean you are not "encoding" it in the correct format? Just a raw ASCII packet? If you are decoding, then you understand the format that the packet is given to you and you must send a packet to the TNC in this same format.<br>
<br>Just for reference, check out the analyzer program I wrote for learning how a KISS packet works (its the last program on the page):<br><br><a href="http://www.ke4nyv.com/software.htm" target="_blank">http://www.ke4nyv.com/software.htm</a><br>
<br>Just paste in a raw KISS packet and it will break down every element for you. It is quick and dirty, but it helped me a lot.<br><br>Jason KE4NYV<br>RPC Electronics<br><a href="http://www.rpc-electronics.com/" target="_blank">www.rpc-electronics.com</a><br>
<br><br>--- On Mon, 8/3/09, Dave Haynes <<a href="mailto:dave@ep90.com">dave@ep90.com</a>> wrote:<br><br>> From: Dave Haynes <<a href="mailto:dave@ep90.com">dave@ep90.com</a>><br>> Subject: Re: [aprssig] How to send packet through a KISS modem<br>
> To: "TAPR APRS Mailing List" <<a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>><br>> Date: Monday, August 3, 2009, 4:51 AM<br>
<div>
<div></div>
<div class="h5">> Are you sending the type indicator<br>> byte before your packet? After your opening $C0, the first<br>> byte indicates the content of the message to the TNC. For a<br>> data packet, the indicator byte will usually be $00.<br>
><br>> All detailed in "The KISS TNC: A simple Host-to-TNC<br>> communications protocol" by Mike Chepponis K3MC and Phil<br>> Karn, KA9Q<br>><br>> Dave<br>> G1TVL<br>><br>> <a href="mailto:rfinesmith@aol.com">rfinesmith@aol.com</a><br>
> wrote:<br>> > Does anyone in the group have experience programming<br>> to a KISS modem to transmit? I have no problem<br>> receiving and decoding APRS packets from a TNC in KISS mode<br>> (using a my Kantronics KPC3+), but I can't figure out how to<br>
> get the TNC to send packets while in KISS mode. I am<br>> wrapping my raw AX25 packets in \xC0 prior to writing to the<br>> modem, but that doesn't work. Also, I have tried to<br>> manually send text while in kiss mode, using HyperTerminal,<br>
> also wrapping the text in \xC0 (i.e.,<br>> <ALT>-0192). No luck.<br>> ><br>> > Thanks,<br>> > Robin, AA3NJ<br>><br>><br>> __________ Information from ESET NOD32 Antivirus, version<br>
> of virus signature database 4299 (20090802) __________<br>><br>> The message was checked by ESET NOD32 Antivirus.<br>><br>> <a href="http://www.eset.com/" target="_blank">http://www.eset.com</a><br>><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>
><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>