08-06-2014 01:16 AM
Solved! Go to Solution.
08-06-2014 01:56 AM - edited 08-06-2014 01:57 AM
Hi Mo7,
But I couldn't find a replacement for the Query and Parse command to read the output voltage
Did you grab the manual of your HP devices? There you will find any commands needed to communicate with the device(s)…
You may also try the NI Instrument Driver Network to check for pre-made drivers for your device. I found them here…
(Hint: I would search for Agilent instead of HP, but hurry up before they change their name again! :D)
08-06-2014 02:03 AM
08-06-2014 02:05 AM
08-06-2014 02:11 AM
08-06-2014 02:13 AM
08-06-2014 02:17 AM
Hi mo7,
The manual provides the way for basic language and c language but not LabVIEW
As a programmer you should be able to adapt the examples given in that manual for LabVIEW…
my supervisor told me that the pre-made drivers may slow the execution time since they take longer time to load.
How does the "loading time" influence execution time? Can you (or your supervisor) explain this?
The InstrumentIO-Assistent uses the very same underlying driver to communicate with your device as you would use on your own (or does the driver at IDNet): VISA. "Execution speed" is mainly dependend on the used connection between PC and device and on device execution/response time…
08-06-2014 04:40 AM
Thank you @GerdW
@GerdW wrote:
Hi mo7,
The manual provides the way for basic language and c language but not LabVIEW
As a programmer you should be able to adapt the examples given in that manual for LabVIEW…
my supervisor told me that the pre-made drivers may slow the execution time since they take longer time to load.
How does the "loading time" influence execution time? Can you (or your supervisor) explain this?
The InstrumentIO-Assistent uses the very same underlying driver to communicate with your device as you would use on your own (or does the driver at IDNet): VISA. "Execution speed" is mainly dependend on the used connection between PC and device and on device execution/response time…
Thank you @GerdW