<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Fred Atkinson, WB4AEJ wrote:
<blockquote cite="mid001801c60e81$1a62a400$c80a0a0a@mishmash"
type="cite">
<blockquote type="cite">
<pre wrap="">1) At some point, MFJ dropped KISS support to make room for other
features in their firmware -- not certain when they started
non-supporting it. Test it in KISS mode and see if it works.
</pre>
</blockquote>
<pre wrap=""><!---->
Not sure how to do that. Haven't found documentation on the current
commands anywhere as yet. But according to the manual (the 1270C manual, I
couldn't find the one for the 1270B), it does indeed support KISS mode.
</pre>
</blockquote>
<br>
Some time ago when I discovered that the latest MFJ1270C's no longer
supported KISS I contacted MFJ and this was confirmed. I jokingly said
that I was sure they would reflect this change in a revision to the
manual! What actually happened is they discontinued the product
entirely. Although it was a reliable product, I have a dozen of them
in remote service, it was obviously too expensive to manufacture. Very
old technology.<br>
<br>
As to KISS, the best solution by far is to replace the eprom with a
JKISS eprom. Works perfectly with AGWPE or the new AGWtoBPQ, and thus
UIView32. The JKISS image is burned without any user configuration.
The JKISS image is in the bpq408a.zip package
<a class="moz-txt-link-freetext" href="http://www.dxspots.com/bpq32/bpq408a.zip">http://www.dxspots.com/bpq32/bpq408a.zip</a> With JKISS there are no
options to set ever, you just turn it on!<br>
<br>
As to testing KISS, there is a simple test program, TXTest, at
.http://www.tnc-x.com/documentation.htm I tried it with JKISS just
for fun and it works, however if the LED's on the 1270B/C blink 3 times
upon power up it's nearly a certainty that the software is just fine.<br>
<blockquote cite="mid001801c60e81$1a62a400$c80a0a0a@mishmash"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">The original TNC2 design (of which the MFJ is a near clone) used two 8K
static RAMS and a 27128 EPROM. These three chips filled all three
sockets. The board layout provided support for anticipated future
higher density stat RAMS. A movable jumper on the board provided for
addressing two 8K RAMS or a single (at the time horribly expensive) 32K
RAM.
Within a few years the single 32K RAM became standard, the jumper was
bridged with a PC board trace that had to be slashed with an X-acto
knife if you wanted to downgrade to the dual 8K configuration, and the
second socket has remained empty ever since.
There is no point in adding memory; indeed you CAN'T add memory. This
thing is NOT a PC capable of addressing hundreds of megabytes of RAM.
The entire memory address space of the Z-80 CPU in the TNC is only 64K!!
The 32K RAM occupies half of the memory space; the firmware in the
27256 (32K bytes) EPROM already occupies the other half. The entire
TNC firmware is hand-coded directly in Z-80 assembly code and takes a
fraction of the RAM and ROM that typical PC apps take.
</pre>
</blockquote>
</blockquote>
<br>
<blockquote cite="mid001801c60e81$1a62a400$c80a0a0a@mishmash"
type="cite">
<pre wrap=""><!---->
According to the manual, memory can be increased to 512 kilobytes. I'm
still trying to find the specifics on the type of memory required.
</pre>
</blockquote>
<br>
With KISS (or JKISS) there is no need whatsoever to add more memory!
It wouldn't (couldn't) even be used.<br>
<br>
Ron Stordahl, N5IN<br>
<blockquote cite="mid001801c60e81$1a62a400$c80a0a0a@mishmash"
type="cite">
<pre wrap="">
Fred, WB4AEJ
</pre>
</blockquote>
<br>
</body>
</html>