Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.022 X-Spam-Evidence: '*H*': 0.96; '*S*': 0.00; 'subject:Python': 0.05; ':-)': 0.06; 'ascii': 0.07; 'imply': 0.07; 'indeed,': 0.07; '21,': 0.09; 'it;': 0.09; '9600': 0.16; 'gene': 0.16; 'saying.': 0.16; 'soap,': 0.16; 'cc:addr:python-list': 0.16; 'meant': 0.17; 'wrote:': 0.18; 'seems': 0.20; 'cc:no real name:2**0': 0.20; 'cheers,': 0.20; 'trying': 0.21; 'header:In-Reply-To:1': 0.22; 'cc:2**0': 0.24; 'settings': 0.24; 'tech': 0.25; 'code': 0.25; 'beyond': 0.28; 'bit': 0.28; "he's": 0.29; 'cc:addr:python.org': 0.29; 'nov': 0.29; 'pm,': 0.29; 'times.': 0.30; 'anyone': 0.31; 'capture': 0.32; 'pretty': 0.32; 'header:User-Agent:1': 0.33; 'normally': 0.34; 'setting': 0.34; 'occurs': 0.34; 'subject:/': 0.35; 'subject:with': 0.36; 'david': 0.36; 'think': 0.37; 'using': 0.38; 'monday,': 0.38; 'getting': 0.38; 'being': 0.39; 'else': 0.39; 'data,': 0.39; 'subject: (': 0.40; 'extremely': 0.40; '2011': 0.61; 'header:Message-Id:1': 0.62; 'love': 0.62; 'high': 0.67; 'noise': 0.67; 'receive': 0.68; 'low': 0.74; '"there': 0.84; '12:25': 0.84; 'cables': 0.84; 'riley': 0.84; '8th': 0.91; 'received:66.118': 0.91; 'subject:Serial': 0.91 X-Spam-Status: No, score=-2.1 required=5.0 X-Spam-Level: From: gene heskett To: David Riley Subject: Re: Non-POSIX parity (mark/space) with Python-Serial on Linux. Date: Mon, 21 Nov 2011 13:33:17 -0500 User-Agent: KMail/1.13.7 (Linux/2.6.38.8-pclos2.pae.bfs; KDE/4.6.5; i686; ; ) References: <27511132.925.1321884055247.JavaMail.geo-discussion-forums@yqnf38> <201111211225.54775.gheskett@wdtv.com> <2A18CB23-4EDC-46E9-A49D-DEDE28C7FBEF@gmail.com> In-Reply-To: <2A18CB23-4EDC-46E9-A49D-DEDE28C7FBEF@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1256" Content-Transfer-Encoding: 7bit Cc: python-list@python.org X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 34 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1321900402 news.xs4all.nl 6958 [2001:888:2000:d::a6]:48045 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:16040 On Monday, November 21, 2011 01:28:16 PM David Riley did opine: > On Nov 21, 2011, at 12:25 PM, gene heskett wrote: > > And that is 9600 baud 8n1 on both ends. Ascii is normally 7 bit and > > will have a low 8th bit if fed normal ascii data, so how is the 8th > > bit getting set other than purposely setting 7M1 on the other end of > > the cable? > > That's what I thought the OP was doing; it sounds like he's trying to > receive 7M1 in Minicom using 8N1 on the terminal and getting garbled > data because the high bit is set (because the other end is sending > 7M1). I never meant to imply that 8N1 would give garbled data if both > ends were set to it; indeed, that's pretty much standard communications > settings for short cables in low to moderate noise environments. If > anyone else read it that way, that's not what I meant. :-) > > - Dave I think that getting the other end off 7M1 was what I was saying. Trying to attack the bad data after capture by writing code always seems extremely masochistic to me. The amount of miss-understanding that seems to pervade rs-232 communications is mind boggling at times. The tech itself is so old it is being forgotten! Cheers, Gene -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) My web page: Whatever occurs from love is always beyond good and evil. -- Friedrich Nietzsche