Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!ecngs!feeder2.ecngs.de!newsfeed.freenet.ag!news2.euro.net!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.031 X-Spam-Evidence: '*H*': 0.94; '*S*': 0.00; 'python.': 0.04; 'subject:Python': 0.05; 'ascii': 0.07; 'used.': 0.07; 'python': 0.08; '21,': 0.09; 'commonly': 0.09; 'garbage': 0.09; 'output': 0.10; 'am,': 0.12; '"space"': 0.16; '9600': 0.16; 'gene': 0.16; 'soap,': 0.16; 'trs-80': 0.16; 'wrote:': 0.18; 'cheers,': 0.20; 'header:In-Reply-To:1': 0.22; 'path,': 0.23; 'settings': 0.24; 'shell': 0.24; 'asking': 0.28; 'bit': 0.28; 'print': 0.29; 'error': 0.29; 'nov': 0.29; 'example': 0.29; 'correct': 0.29; 'controlled': 0.30; 'rarely': 0.30; 'yes.': 0.30; 'header:User- Agent:1': 0.33; 'there': 0.33; 'done': 0.34; 'to:addr:python- list': 0.34; 'normally': 0.34; 'setting': 0.34; 'set.': 0.34; 'which,': 0.34; 'running': 0.35; 'something': 0.35; 'subject:/': 0.35; 'problem.': 0.36; 'connection': 0.36; 'device': 0.36; 'subject:with': 0.36; 'david': 0.36; 'using': 0.38; 'monday,': 0.38; 'getting': 0.38; 'characters': 0.39; 'should': 0.39; 'else': 0.39; 'data,': 0.39; 'mark': 0.39; 'subject: (': 0.40; "it's": 0.40; 'to:addr:python.org': 0.40; 'once': 0.60; 'more': 0.61; '2011': 0.61; 'your': 0.61; 'header:Message-Id:1': 0.62; 'ever': 0.65; 'high': 0.67; 'low': 0.74; 'hand,': 0.76; '"there': 0.84; 'low,': 0.84; 'parity': 0.84; 'riley': 0.84; '8th': 0.91; 'ascii.': 0.91; 'received:66.118': 0.91; 'subject:Serial': 0.91 X-Spam-Status: No, score=-0.4 required=5.0 X-Spam-Level: From: gene heskett To: python-list@python.org Subject: Re: Non-POSIX parity (mark/space) with Python-Serial on Linux. Date: Mon, 21 Nov 2011 12:25:54 -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> <2723247.1219.1321892899941.JavaMail.geo-discussion-forums@yqzz20> <5074B814-C5A1-4B42-8F89-3B7406C91F49@gmail.com> In-Reply-To: <5074B814-C5A1-4B42-8F89-3B7406C91F49@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1256" Content-Transfer-Encoding: 7bit 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: 50 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1321896759 news.xs4all.nl 6924 [2001:888:2000:d::a6]:38539 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:16032 On Monday, November 21, 2011 11:58:53 AM David Riley did opine: > On Nov 21, 2011, at 11:28 AM, Matthew Lenz wrote: > > Using 8N1 under minicom with this device resulted in garbled text when > > once connected. Connection using 7M1 resulted in the correct text. > > So there must be something else that needs to be done in my python > > program correct? > > Under minicom in 8N1, it's going to look garbled because the high bit > will always be set. Minicom will try to spit out those characters > anyway, which will print out whatever extended ASCII garbage your > terminal supports in the 0x80-0xFF range. Programmatically, though, you > can strip off the high bit when you're receiving it in Python. I have been using 8n1 in minicom for years, never ever had such a problem. In fact, I don't even know if I can set the path to mark parity as it is so rarely used. E or O as error detectors are much more commonly used. Example copy/paste from minicom, talking to a trs-80 Color Computer 3 running a shell under nitros9, which is a bit like unix. I am asking it for the settings of its own output path, .1=stdout: {t2|07}/DD/NITROS9/dw3install/6309L2/SCRIPTS:tmode .1 /t2 upc=00 bso=01 dlo=00 eko=01 alf=01 nul=00 pau=01 pag=18 bsp=08 del=18 eor=0D eof=1B rpr=09 dup=01 psc=17 int=03 qut=05 bse=08 ovf=07 par=01 bau=06 xon=00 xof=00 {t2|07}/DD/NITROS9/dw3install/6309L2/SCRIPTS: 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? > "Space" parity, on the other hand, should look normal under Minicom > because the high bit will always be low, giving you standard 7-bit > ASCII. > Yes. > - Dave 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: Everything is controlled by a small evil group to which, unfortunately, no one we know belongs.