-nuts] "PYLT" Python LabTools
Dear Poul,
Excellent! Looking forward to playing with it more.
On a related note, O'Reilly has a new book out on developing
instrument control software
using Python:
Real World Instrumentation with Python: Automated Data Acquisition and
Control Sy
Dear Poul,
Excellent! Looking forward to playing with it more.
On a related note, O'Reilly has a new book out on developing
instrument control software
using Python:
Real World Instrumentation with Python: Automated Data Acquisition and
Control Systems by
John M. Hughes
http://oreilly.com
That would be my preferred method.
-Chuck Harris
Poul-Henning Kamp wrote:
...
Create a pylt_site.py containing something like:
import hp34401a
import hp33120a
def hp34401a():
return hp34401a.hp34401a(name="/dev/ttyfoo", adr=11)
def hp33120a():
In message <20110116221429.af8d5800...@ip-64-139-1-69.sjc.megapath.net>, Hal Mu
rray writes:
>How about a config file?
Yeah, that bit is obvious, the trouble is all the "something like" :-)
I'm a firm beliver in Gettys principles for software development,
number 3 of which says:
3.The o
p...@phk.freebsd.dk said:
> Where to find the instruments is obviously something that should be
> abstracted once more people starts to use this, I'm open to both suggestions
> and patches in that respect.
How about a config file?
I think it needs something like:
A symbolic name (used by top
In message , Kevin Rosenber
g writes:
>On Jan 16, 2011, at 3:00 AM, Poul-Henning Kamp wrote:
>Probably the next thing I'd add to your system is the ability to
>select my Prologix ethernet controller, rather than the USB controller.
>I'll send you a patch when that is done (unless I just buy a
>Pro
On Jan 16, 2011, at 3:00 AM, Poul-Henning Kamp wrote:
> I have created a Github project for the Python Labtools I'm using
> to deal with my instruments.
Looks nice. While GUI tools like LabView have their role, I'm more often
interested in remote
monitoring and control.
Probably the next thing I
In message <4d32fef2.5000...@erols.com>, Chuck Harris writes:
>I was
>a little more back-of-the-envelope with my stuff, and basically kept
>the low level stuff with the upper level control functions.
Yeah, that's how I started out also, and then I ended up in the
"now where did I put that functi
Hi Poul,
I sure am glad someone other than just me is using python to control
their GPIB instruments. What you have done looks quite nice. I was
a little more back-of-the-envelope with my stuff, and basically kept
the low level stuff with the upper level control functions. Your way
is better.
I have created a Github project for the Python Labtools I'm using
to deal with my instruments.
https://github.com/bsdphk/pylt
What ?
==
This is a set of python classes for communicating with IEEE488/GPIB
instruments which I use in my private lab.
The base class is "pylt" - PYthon L
10 matches
Mail list logo
