From: Tomi Manninen (uxv@roskapostia.tunk.net)
Date: Fri Dec 27 2002 - 22:14:33 EET
On Fri, 27 Dec 2002 cqwyq.mratoc@harrow.ac.uk wrote:
> OK, I shoudl check this. Worth nothing that other transmissions (ax25) do
> work, and also, va3am was able to connect fine. So perhaps the problem is
> more likely to be on the va3mvw side. Not sure what to look for but
> that's where my efforts will now concentrate.
Ok,
That would seem like the txdelay at VA3OAK is enough for it's TX chain but
unfortunately on a shared channel you will have to go by the weakest link.
It might be that the TX-to-RX switching delay of the TRX or the synch
delay of the TNC at VA3MVW might be too long.
Then agin, the problem might be something else just as well...
/Tomi
> On Fri, 27 Dec
> 2002, Tomi Manninen wrote:
>
> > On Fri, 27 Dec 2002 terhi.victor@logonet.com wrote:
> >
> > > But when I open by bbs, the first
> > > packet is 255 characters long, and is never heard, The next packets are
> > > shorter and are always heard.
> >
> > This is just a guess, but the lenght of the packet might not be the issue.
> > It could be that the txdelay at VA3OAK is too short, thereby distroying
> > the start of the packet. That would cause behaviour like this. (I'm
> > assuming both packets are sent in one go.)
> >
> >
>
>
-- Tomi Manninen Internet: hke@jyu.fi OH2BNS AX.25: terhi.victor@logonet.com KP20ME04 Amprnet: kmeyaqa.fmlghivrb@charter.com- To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to terhi.victor@logonet.com More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Fri Dec 27 2002 - 22:33:52 EET