03-17-2014 01:34 PM
I am a complete novice to LabVIEW, I have a couple of Sorensen DLM power supplies that are controlled by GPIB. These get errors like “Sorensen Error Query.vi”, code -1074003951 and VISA Write in Sorensen Read voltage output.vi->PDFT 150V RevA1.vi. I am trying to figure out if this is a hardware or software issue, then how to fix if it is a software issue.
Sometimes the program runs for 8 hours without error sometimes 30+, but need it to run without faulting for a longer time.
Thanks for any input,
MKroll
03-17-2014 07:27 PM
03-17-2014 07:50 PM
Ignore the occasional error??? You're suggesting he settle for buggy code? What in the world?
Maybe today the error is infrequent, but if right after you go live conditions change so the program freaks out once an hour, what are you going to do then? And it doesn't even meet his (relaxed) specs now.
We can't advise anything about your code without seeing it (the VI itself, NOT a picture), and if you could also attach the LV drivers (or subVIs) for the power supplies, so we could see how it fits into the picture, it should help.
Cameron
03-18-2014 02:46 AM
03-18-2014 02:56 AM - edited 03-18-2014 03:05 AM
@Michael_78 wrote:
I would NEVER settle for buggy code! But some things are out of our control. Have you never seen a glitch on an instrument, comms cabling or even windows drivers beyond our control? Tjere could be any nomber of environmental factors. All I am saying is consider being more error tollerant. There is more to error handling than exit
I think this should be your LAST resort, not your first.
03-18-2014 03:09 AM - edited 03-18-2014 03:12 AM
Oh, does this happen with any of the power supplies or just one? I'm thinking it could be something like a cable length issue. GPIB is single-ended and fairly susceptible to attenuation. I forget what the spec is, but it might be worth checking out.
03-18-2014 03:49 AM
@billko wrote:
@Michael_78 wrote:
I would NEVER settle for buggy code! But some things are out of our control. Have you never seen a glitch on an instrument, comms cabling or even windows drivers beyond our control? Tjere could be any nomber of environmental factors. All I am saying is consider being more error tollerant. There is more to error handling than exitI think this should be your LAST resort, not your first.
Agree. it should not be the solution. I was premature in making this suggestion, but i did say the root cause should be investigated. I know my users would like it if their test kept shutting down while i found the root cause of an issue, especially if it might be 40hrs into a test. It is true we need to look at the code and see if there may be something there. The 40 hrs thing lead me to an OS/environmental glitch which may be beyond the control of the programmer, but there could be programming issues of course.
Michael.
03-18-2014 09:00 AM
@Michael_78 wrote:
@billko wrote:
@Michael_78 wrote:
I would NEVER settle for buggy code! But some things are out of our control. Have you never seen a glitch on an instrument, comms cabling or even windows drivers beyond our control? Tjere could be any nomber of environmental factors. All I am saying is consider being more error tollerant. There is more to error handling than exitI think this should be your LAST resort, not your first.
Agree. it should not be the solution. I was premature in making this suggestion, but i did say the root cause should be investigated. I know my users would like it if their test kept shutting down while i found the root cause of an issue, especially if it might be 40hrs into a test. It is true we need to look at the code and see if there may be something there. The 40 hrs thing lead me to an OS/environmental glitch which may be beyond the control of the programmer, but there could be programming issues of course.
Michael.
Sometimes it's a money thing, too - unfortunately. Sometimes management won't let you spend the necessary engineering hours to fix it. 😞
03-18-2014 09:05 AM
Hi,
I recommend checking with your instrument provider to see if there has been a new firmware release or new driver for your power supplies. It seems that this error appears when an instrument does not match to the correct software driver making the call to it.
Please refer to KB:
http://www.ni.com/support/labview/visa/verr1.htm
Hope this information is useful.
03-18-2014 09:25 AM
@luissg wrote:
Hi,
I recommend checking with your instrument provider to see if there has been a new firmware release or new driver for your power supplies. It seems that this error appears when an instrument does not match to the correct software driver making the call to it.
Please refer to KB:
http://www.ni.com/support/labview/visa/verr1.htm
Hope this information is useful.
I would think the error would be nice and consistent if that was the case. SInce the OP also reported something happening in a VISA write, think it might be more likely to be a hardware issue.