Dear friends!
Thank you for the discussion. It was really helpful. As mentioned, it
was necessary to have a longer delay. Previously I have used a delay
of 5 and 10 s but it was not long enough. Now it is 25 s and
everything works fine.
Thank you again!
Best,
AS
--
Am 26.10.2011 17:58, schrieb spintronic:
Thank you for the discussion. It was really helpful. As mentioned, it
was necessary to have a longer delay. Previously I have used a delay
of 5 and 10 s but it was not long enough. Now it is 25 s and
everything works fine.
If you use the correct sequence
)
mw.write(CALC1:DATA? FDATA)
a=mw.read()
print a
===
(That is really all!)
PS In this case I use Python Enthought for Windows, but I am not an
expert in Windows (I work usually in Linux but now I need to run this
data acquisition under Windows).
--
http://mail.python.org
= None)
mw.write(*RST)
mw.write(CALC1:DATA? FDATA)
a=mw.read()
print a
===
(That is really all!)
PS In this case I use Python Enthought for Windows, but I am not an
expert in Windows (I work usually in Linux but now I need to run this
data acquisition under Windows
but now I need to run this
data acquisition under Windows).
--
http://mail.python.org/mailman/listinfo/python-list
Shot in the dark: could it be that you have to add delays to give the
instrument time to adjust? When you do it from the python shell, line by
line, there is a long delay between one
In 362e368f-829e-4477-bcfc-c0650d231...@j7g2000yqi.googlegroups.com
spintronic sidorenko.and...@gmail.com writes:
Any ideas? Why there is a difference when I run the script or do it
command by command?
Are you running the same python program in both cases?
Are you in the same directory in
On Oct 25, 6:29 pm, Nick Dokos nicholas.do...@hp.com wrote:
Shot in the dark: could it be that you have to add delays to give the
instrument time to adjust? When you do it from the python shell, line by
line, there is a long delay between one line and the next.
Nick
Hi, Nick!
Thanks! You
On Oct 25, 6:43 pm, John Gordon gor...@panix.com wrote:
Thanks, John!
Are you running the same python program in both cases?
Yes, the same.
Are you in the same directory in both cases?
Does PYTHONPATH and/or sys.path have the same value in both cases?
It looks that yes but how can it
not an
expert in Windows (I work usually in Linux but now I need to run this
data acquisition under Windows).
Just in case you have a local installation of visa and it silently fails
on some import,
try to add at the begining of your script:
import sys
sys.path.append('')
When using
In 86e6bfb8-17e1-4544-97ba-7299db8a8...@p16g2000yqj.googlegroups.com
spintronic sidorenko.and...@gmail.com writes:
Are you in the same directory in both cases?
Does PYTHONPATH and/or sys.path have the same value in both cases?
It looks that yes but how can it matter? All I need it is to
Am 25.10.2011 19:22, schrieb spintronic:
On Oct 25, 6:29 pm, Nick Dokosnicholas.do...@hp.com wrote:
Shot in the dark: could it be that you have to add delays to give the
instrument time to adjust? When you do it from the python shell, line by
line, there is a long delay between one line and
for Windows, but I am not an
expert in Windows (I work usually in Linux but now I need to run this
data acquisition under Windows).
I'm almost certain that there is a turnaround timing issue that is causing
the problem. These are common problems in data aquisition systems. The
simplest solution
Hi,
I'm building a little application, which the goal is to:
1./ Collect data via Serial line and or via a file (for playback).
2./ Display these data as graph, oscilloscope, ...
How manage this ?
1./ Is each display must responsible to acquire/read the data ?
2./ Or an engine collect the data
StepH wrote:
1./ Is each display must responsible to acquire/read the data ?
2./ Or an engine collect the data then send them to each display ?
I'd keep it simple:
- DataCollector class
asociated with one or more display instances (implemented as a list of
display subscribers)
it collects
Alex Verstraeten a écrit :
StepH wrote:
1./ Is each display must responsible to acquire/read the data ?
2./ Or an engine collect the data then send them to each display ?
I'd keep it simple:
- DataCollector class
asociated with one or more display instances (implemented as a list of
StepH wrote:
a simple loop could do it
- handle user events
- collect data
- update displays
- sleep
Here i've a prob. (due to the fact that I start both with Python
TkInter). In TkInter, you run your app by launching a mainloop()
routine, right ? So, how, in my forever loop
16 matches
Mail list logo
