On Tue, Nov 22, 2011 at 10:09 AM, Grant Edwards wrote:
> On 2011-11-21, Grant Edwards wrote:
>
>> Like the old joke:
>>
>> There are 10 kinds of people in the world: those who understand
>> binary numbers, and those who don't.
>
> OK, it's not _much_ of a joke, but I don't get to use it very
On 2011-11-21, Grant Edwards wrote:
> Like the old joke:
>
> There are 10 kinds of people in the world: those who understand
> binary numbers, and those who don't.
OK, it's not _much_ of a joke, but I don't get to use it very often,
so I couldn't let it go (for one thing, it only works in "p
On 2011-11-21, David Riley wrote:
> On Nov 21, 2011, at 2:29 PM, Matthew Lenz wrote:
>
>> Another thing I noticed is that the & and | appear to give the same result
>> as adding or subtracting 128 from the ordinal value. I'm assuming that
>> isn't coincidence. :)
>
> It's not, though the differ
On Nov 21, 2011, at 2:29 PM, Matthew Lenz wrote:
> Another thing I noticed is that the & and | appear to give the same result as
> adding or subtracting 128 from the ordinal value. I'm assuming that isn't
> coincidence. :)
It's not, though the difference is important. They're binary ANDs (&)
On 2011-11-21, Matthew Lenz wrote:
> Another thing I noticed is that the & and | appear to give the same
> result as adding or subtracting 128 from the ordinal value.
Nope, that's only true for some values.
If we're limiting ourselves to byte values, then we're talking
modulo-256 arithmetic, so
Another thing I noticed is that the & and | appear to give the same result as
adding or subtracting 128 from the ordinal value. I'm assuming that isn't
coincidence. :)
--
http://mail.python.org/mailman/listinfo/python-list
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 purpos
On 21/11/2011 16:52, Matthew Lenz wrote:
Ahh. Ok. So how would I go about doing that with python? I think in
perl (sorry for the naughty word) I could use the tr// (translate)
but is there a quick way to do so with python? Is it going to be
necessary to convert commands I SEND to the device or
On Nov 21, 2011, at 12:59 PM, Matthew Lenz wrote:
> Thanks, this will be a great help.
>
> Just wanted to confirm that you meant to use [ .. for x in ord_str] in the
> example conversion? Got a TypeError using the received_str.
Yes, I probably should have double-checked that. ord_str is indee
Thanks, this will be a great help.
Just wanted to confirm that you meant to use [ .. for x in ord_str] in the
example conversion? Got a TypeError using the received_str.
--
http://mail.python.org/mailman/listinfo/python-list
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
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 els
On Nov 21, 2011, at 11:52 AM, Matthew Lenz wrote:
> Ahh. Ok. So how would I go about doing that with python? I think in perl
> (sorry for the naughty word) I could use the tr// (translate) but is there a
> quick way to do so with python? Is it going to be necessary to convert
> commands I SE
Ahh. Ok. So how would I go about doing that with python? I think in perl
(sorry for the naughty word) I could use the tr// (translate) but is there a
quick way to do so with python? Is it going to be necessary to convert
commands I SEND to the device or only convert what I receive?
--
http:/
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 i
On Tue, Nov 22, 2011 at 3: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?
Using 8N1 wh
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?
--
http://mail.python.org/mailman/listinfo/python-list
2011/11/21 :
> I'm working on a project where I need to communicate with some devices via
> modem which have the possibility of using MARK and SPACE parity. These are
> not defined by POSIX and therefore are not directly supported under Linux.
>
> I've found the following discussion on the topi
I should also note that I am aware of the following discussion on the newsgroup:
https://groups.google.com/d/msg/comp.lang.python/1HyCqPSOf50/eQINFrrFKwoJ
However, I believe this refers to implementing the solution for 8M1 and 8S1.
--
http://mail.python.org/mailman/listinfo/python-list
I'm working on a project where I need to communicate with some devices via
modem which have the possibility of using MARK and SPACE parity. These are not
defined by POSIX and therefore are not directly supported under Linux.
I've found the following discussion on the topic:
http://www.lothosof
20 matches
Mail list logo
