ECS-L Home Automation and Security Archives
  learn more | view messages for this month | NetBloc® | terms of use | search

Google
 


  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects

Subject:
From:
Date:
RE: [ECS] error
dastorey
Wed, 26 May 1999 21:09:40 -0500


After I read my own posting. What I said was parity but what I mean the
whole setting ie ( 9600/E/8/1) vs. (9600/E/8/2 which is Really going with
what Bill said inability to determine your stop bits.

-----Original Message-----
From:	dastorey [mailto:dastorey@swbell.net]
Sent:	Wednesday, May 26, 1999 8:33 PM
To:	ecs-list@netbloc.com
Subject:	RE: [ECS] error

I have seen it when the problem was the opposite if you are running at 2400
increase to 9600 etc.  Now here is the one that puts the third dimension in.
On UNIX operating systems (may not apply to Window)  I have seen framing
errors when the actual problem was parity.

-----Original Message-----
From:	Bill Walters [mailto:wtwalters@home.com]
Sent:	Wednesday, May 26, 1999 12:25 PM
To:	ecs-list@netbloc.com
Subject:	Re: [ECS] error

Peter,

Try slowing down the connected baud rate.  If you're using 19.2, go to
9600...  If at 9600, try 2400 etc....

I believe that framing error indicates loss of start or stop bits and
subsequent overrun of entire byte; i.e., the uart can't figure out which
bits are the character.

Bill Walters


peter kraus wrote:
>
> what does this mean?
>
> 002b O 05/25 11:44 AM:COMM err#18:Break,RX framing err (Item "Temp port")


  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects




Services provided by [NetBloc]®! NetBloc Solutions Inc.
Terms of use. Indexing software (c) 1999 Lin-De, Inc
.