11-18-2009 09:59 AM
Whenever I use close.vi (which was included with the instrument drivers), the power supply's voltage immediately drops and the CC LED lights up. If I decide to not use close.vi, there is a minute delay before the same behavior occurs.
Does anyone know what may be causing this?
11-18-2009 10:20 AM
11-18-2009 11:54 AM
I have included my VI, in which I run a simple Read then Write test. This VI uses Set Voltage/Current.vi and Read Output Voltage/Current.vi
11-18-2009 12:38 PM
That VI does not call a 'Close' function and I still have no idea which driver you are using so that I can check it.
It appears that you are not using the latest driver because I did download the project style driver and your funcion names are different.
11-18-2009 01:03 PM - edited 11-18-2009 01:10 PM
I got rid of the close function since either way, the behavior still occured.
The drivers I have are hp66xxa. I didn't realize there was another set of drivers.
I run in CC issues while still running the test with this set of drivers.
11-18-2009 01:26 PM
There are 3 drivers. You should be able to provide the details on the one you actually downloaded but by preocess of elimination, I figured it out. If there is a next time, provide the details.
I don't see anything in the code that would reprogram the supply when you stopped the program. I'm unsure what the CC light indicates.
Why don't you run an NI-Spy capture?
11-18-2009 01:39 PM
The CC light indicates constant current. It's not a huge problem, but rather inconvenient, that I have to restart the instrument after every test instead of just resetting to the initial value.
As far as I can tell, I can set and read the voltage just fine as long as they are separate VIs. Once they are together in the case structure, the CC problem occcurs.
I can't run a NI-Spy capture. Could this be because I am still using the demo version?
11-18-2009 01:46 PM
11-18-2009 01:51 PM
Yes, I am using GPIB. I have a GPIB-LAN gateway that I use in order to communicate with the instrument.
11-19-2009 03:37 PM
Why do you say you cannot run NI Spy? Here is a helpful KnowledgeBase on how to perform a good NI Spy capture.
Which step is giving you trouble?