6pack query

Hello learned members of the list,

I'm contemplating changing my KISS only EPROMs for 6PACK (to perhaps improve matters on my 0k3 HF ports)

The kernel (2.2.20) has been compiled to include 6PACK - compiled in, not as a module.

Given that there is no equivalent of kissparms for 6PACK, how does one set parameters such as txd, slottime, etc?

In my mind, given that spattach is symbolically linked to kissattach, the parameters are set with kissparms in the same way as they are with KISS TNCs.

Am I correct in my thinking, or way off target?

Ray Wells VK2TV

Ray,
I am running it and that appears to be the way it works. I have set up my kissparms and when i change them I can see the changes in the way the TNC operates.

--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."

Thanks Chuck,

I appear to have guessed that part correctly. However, I may have bombed out in believing that spattach was "ready to go".

Upon close inspection of kissattach.c I find that a change as per /.../6pack.txt hasn't been implemented.

So, for my next question, if I make the change and recompile kissattach, and rename it spattach, can I still use the original kissattach for KISS applications?

Ray

I would assume that is the token ring type of operation with multiple TNC's on a single port, which is not implemented. (I wish it was as it sure would make life easier for some of our sites)

I do not know, I have been running it as is, and it appears to work just fine for one TNC.

--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chuck> I would assume that is the token ring type of operation Chuck> with multiple TNC's on a single port, which is not Chuck> implemented. (I wish it was as it sure would make life Chuck> easier for some of our sites)

In fact, I implemented it years ago in userspace. I don't know why, but the ax25-utils maintainers never put it on the stock version (even though I sent them the patch).

Get a copy of ax25-tools-0.0.8 from ax25.sourceforge.net, and save it somewhere (say /home/myuser/ax25-tools/). Get a copy of my patch from:

http://www.escomposlinux.org/iarenaza/hamradio/m6pack/files/ax25-tools-0.0.8-m6pack.diff.bz2

and save it in the same directory. Now untar the tools and patch them:

        cd /home/myuser/ax25-tools
        tar xzf ax25-tools-0.0.8.tar.gz
        bzip2 -dc ax25-tools-0.0.8-m6pack.diff.bz2 | patch -p0

and build the m6pack binaries (you have to build libax25 previously, or have it installed somewhere in your system --maybe it's the package called libax25-dev--):

        cd ax25-tools-0.0.8
        ./configure
        cd kiss
        make m6pack

now you've got a new executable, called m6pack (and it's associated manual page).

Now, let's suppose you've got your 6pack TNC ring attached to /dev/ttyS0 and your TNCs are configured for 19200 bps on the serial port. You've got 4 TNCs on your ring, so you execute:

m6pack -s 19200 /dev/ttyS0 /dev/ptyq0 /dev/ptyq1 /dev/ptyq2 /dev/ptyq3

This "splits" your 4 TNC ring into 4 separate "pseudo-ports", each one talking to a different TNC on your ring.

Now you use spattach to attach each one of them. Let's supppose your radio ports (as configured in axports file) are called 6pack0, 6pack1, etc:

spattach /dev/ttyq0 6pack0
spattach /dev/ttyq1 6pack1
spattach /dev/ttyq1 6pack2
spattach /dev/ttyq1 6pack3

- From here on, everything works the same as usual.

73's de EB2EBU.

- --
Get PGP/GPG Keys at http://www.escomposlinux.org/iarenaza/pgpkey.php
I use free software / Yo uso software libre
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFDZjO3ZXLnGT1HLgcRAizUAKCP2of5dntxMvQPpNzyMlgK0/iqdwCfZBma 2VCXW39O4VhBeotDqfYS6pk=
=xnN3
-----END PGP SIGNATURE-----

Craig was only keeping the packages alive but not more - for whatever reasons - but he made that pretty clear on top of ax25.sourceforge.net. Then a week ago I approached him and since then I've taken over maintenance of libax25, ax25-tools and ax25-apps together with DL9SAU.

So since there is basically now a new team running the show it's probably safe to say that many of the old bug reports, feature request, patches etc. have been lost in the noise of history. Give us a little time to catch up, then start resubmitting patches again and we'll take it from there.

73 de DL5RB op Ralf

--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ralf> Craig was only keeping the packages alive but not more - for Ralf> whatever reasons - but he made that pretty clear on top of Ralf> ax25.sourceforge.net.

I just wanted to say that the patches have been available for some time, really. Given that English is not my mother tongue, maybe I sounded a little to harsh. I apologize.

73's de EB2EBU

- --
Get PGP/GPG Keys at http://www.escomposlinux.org/iarenaza/pgpkey.php
I use free software / Yo uso software libre
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFDZnCNZXLnGT1HLgcRAtvEAJ9MxJ1JNEeaFRtwpGExH8ZKlNRlVwCePJiE XSnIRe20CNLxv6ylj1nlxes=
=5QAR
-----END PGP SIGNATURE-----

Not harsh but more for well understandable reasons complaining why your patches were never integrated.

And btw, English is just a second language for me as well.

Ralf
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

This is great, as soon as I get my floating dock project done (hope to have it in the water today) I will pull those patches and do it, and give it a try.

I do have a question, I assume that since it is RS-232 the usual distance (wire requirements) hold. Is there any timing limitation that I should be aware of over a long (15-30m) wire? This will allow me to place the TNC's near the radios and not down where the switch is located, reducing the amount of signal loss in the coax. (and keeping cost of coax down.

By way English is my second language too, I speak a variant of Cracker as first language and Spanish and English as second ones... B=]

In a more serious mind... I would not worry much about the language, I murder the mother tongue about as much as anyone, and will hold it against no one...

--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

The RS-232 limit is given by the electric properties of your wiring and also the drivers. Modern PCs frequently seem to have rather marginal RS323 port receiver & drivers. Starting a certain length you may also have to worry if they're potencially are a receiving antenna for a shortwave station nearby ...

My every other word is "bloody" so I guess my British accent is quite perfect ;-)

73 de DL5RB op Ralf

--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21

OK, so there are no timing issues if I used a line driver on each end and ran say 40m of wire between them? I can handle signalling levels no problem, I just do not want to find out that the timing is such that a long wire would cause
a issue there.

Ahh so you can then murder it officially... B-b;;;

--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."