[prev in list] [next in list] [prev in thread] [next in thread]
List: rxtx
Subject: [Rxtx] RXTX 20/01/2005 version on Win32 Problems
From: Thanasis Delenikas <tdelenik () gmail ! com>
Date: 2006-01-18 20:56:23
Message-ID: 310a1a930601181256j77f6a1f6vc5b28233942adc6 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi all.
(I've subscribed again from my other email account).
Trent,
You are right. Linux *always* works, no matter what flow control you set.
Windows *works only* with hardware flow control (I haven't tested what
happens with software XON/XOFF flow control).
I assume (but I am not certain) that even with no flow control at all, all
platforms should work. Without flow control, you have the risk of bumping
into overflow or framing errors, but that's your (the end programmer, I
mean) problem.
>From my side, I shouldn't be working without flow control. That was a bug
too... It was some code forgotten from the old times, when I used to work
with phone emulation drivers which didn't support flow control. The correct
way is to have some flow control enabled and that's why I suppose this is a
low-severity bug for RxTx.
I have no idea which platform shows the correct behaviour, since
my knowledge about Linux and the inner workings of these low-level i/o
operations is limited.
Regards,
Thanasis Delenikas.
> Message: 2
> Date: Tue, 17 Jan 2006 12:24:39 -0700 (MST)
> From: Trent Jarvi <tjarvi@qbang.org>
> Subject: Re: [Rxtx] RXTX 20/01/2005 version on Win32 Problems
> To: RXTX Developers and Users <rxtx@qbang.org>
> Message-ID: <Pine.LNX.4.61.0601171214550.12445@www>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
> On Tue, 17 Jan 2006, jSMSEngine Admin wrote:
>
> > Hi all,
> >
> > Trent, I have found something.
> > I read your comment about flow control, so I experimented a bit.
> >
> > If you remember, in my sample program I've used no flow control at all (
> i.e.
> > Java constant FLOWCONTROL_NONE).
> >
> > Now, during testing, I've switch to hardware inbound flow control (i.e.
> Java
> > constant FLOWCONTROL_RTSCTS_IN) and everything seems to work
> beautifully!
> >
> > I think I will switch to H/W flow control and test things for a while,
> but
> > up to now (a few hundred test read cycles) everything runs smoothly.
> >
>
>
> Hi Thanasis,
>
> I'm fairly sure you have identified a bug. I would not worry too much
> about what Sun CommAPI w32 defaults are. I think they did more or less
> whatever the port opened with. Just a guess. Linux tries to stomp on
> ports so they are all the same.
>
> So this started out with Linux worked, Windows XP/.. did not as I recall.
> Something is wrong in rxtx. Do I understand this right?
>
> FLOWCONTROL_RTSCTS_NONE: Linux worked, Windows did not.
> FLOWCONTROL_RTSCTS_IN: Linux worked, Windows worked.
>
> Perhaps there is something Wayne or I did not understand when we wrote
> that code. I wasnt programming back in the BBS days so modems are not my
> thing. I have a few questions.
>
> Is the above matrix confirmed by observation?
> Linux just always worked?
> Which one _should_ work? I'm guessing modems work with hardware flow
> control. I'll have to dig around.
>
> The windows flow control changes a couple things with hardware flow
> control. Following the w32 API documentation is confusing sometimes.
> But it looks like Linux could have a bug too.
>
>
>
[Attachment #5 (text/html)]
<div>Hi all.</div>
<div>(I've subscribed again from my other email account).</div>
<div> </div>
<div>Trent,</div>
<div> </div>
<div>You are right. Linux *always* works, no matter what flow control you set.</div>
<div>Windows *works only* with hardware flow control (I haven't tested what happens \
with software XON/XOFF flow control).</div> <div> </div>
<div>I assume (but I am not certain) that even with no flow control at all, all \
platforms should work. Without flow control, you have the risk of bumping into \
overflow or framing errors, but that's your (the end programmer, I mean) problem. \
</div> <div> </div>
<div>From my side, I shouldn't be working without flow control. That was a bug \
too... It was some code forgotten from the old times, when I used to work with \
phone emulation drivers which didn't support flow control. The correct way is to have \
some flow control enabled and that's why I suppose this is a low-severity bug for \
RxTx. </div>
<div> </div>
<div>I have no idea which platform shows the correct behaviour, since \
my knowledge about Linux and the inner workings of these low-level i/o \
operations is limited.</div> <div> </div>
<div>Regards,</div>
<div>Thanasis Delenikas.</div>
<div><br> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; \
BORDER-LEFT: #ccc 1px solid">Message: 2<br>Date: Tue, 17 Jan 2006 12:24:39 -0700 \
(MST)<br>From: Trent Jarvi <<a href="mailto:tjarvi@qbang.org"> \
tjarvi@qbang.org</a>><br>Subject: Re: [Rxtx] RXTX 20/01/2005 version on Win32 \
Problems<br>To: RXTX Developers and Users <<a \
href="mailto:rxtx@qbang.org">rxtx@qbang.org</a>><br>Message-ID: \
<Pine.LNX.4.61.0601171214550.12445@www ><br>Content-Type: TEXT/PLAIN; \
charset=US-ASCII; format=flowed<br><br>On Tue, 17 Jan 2006, jSMSEngine Admin \
wrote:<br><br>> Hi all,<br>><br>> Trent, I have found something.<br>> I \
read your comment about flow control, so I experimented a bit. <br>><br>> If \
you remember, in my sample program I've used no flow control at all (i.e.<br>> \
Java constant FLOWCONTROL_NONE).<br>><br>> Now, during testing, I've switch to \
hardware inbound flow control (i.e
. Java<br>> constant FLOWCONTROL_RTSCTS_IN) and everything seems to work \
beautifully!<br>><br>> I think I will switch to H/W flow control and test \
things for a while, but<br>> up to now (a few hundred test read cycles) everything \
runs smoothly. <br>><br><br><br>Hi Thanasis,<br><br>I'm fairly sure you have \
identified a bug. I would not worry too much<br>about what Sun CommAPI w32 \
defaults are. I think they did more or less<br>whatever the port opened \
with. Just a guess. Linux tries to stomp on <br>ports so they \
are all the same.<br><br>So this started out with Linux worked, Windows XP/.. did not \
as I recall.<br>Something is wrong in rxtx. Do I understand this \
right?<br><br>FLOWCONTROL_RTSCTS_NONE: Linux worked, Windows did not. \
<br>FLOWCONTROL_RTSCTS_IN: Linux worked, Windows worked.<br><br>Perhaps \
there is something Wayne or I did not understand when we wrote<br>that \
code. I wasnt programming back in the BBS days so modems are not \
my<br>thing. I have a few questions. <br><br>Is the above matrix confirmed \
by observation?<br>Linux just always worked?<br>Which one _should_ \
work? I'm guessing modems work with hardware \
flow<br>control. I'll have to dig around.<br><br>The windows flow control \
changes a couple things with hardware flow <br>control. Following the w32 \
API documentation is confusing sometimes.<br>But it looks like Linux could have a bug \
too.<br><br><br></blockquote>
_______________________________________________
Rxtx mailing list
Rxtx@qbang.org
http://mailman.qbang.org/mailman/listinfo/rxtx
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic