MAX error insufficient location information or the device is not present

[SteveFeeser]

Hello,

    We have been getting this error once in a while on our test system.  (See attachment)  Our system is running Windows 7, MAX 5.5.0f0, TestStand 4.2.1 and LabView 2010 SP1. 

   To get the error to clear and the system to run we have to go in and rename each VISA to a bogus name and save it.  Then go back and rename them back to what they should be and save again. 

   We get this error maybe once every 3 or 4 months, but it does stop production until we get in and fix it.  What is going on and how do we fix it?

Thanks,

Steve Feeser

[dnchen]

Hey Steve,

The error typically occurs when you try and open or communicate to an incorrect resource name. Seems kind of odd that this is happening only every 3-4 months. Couple of questions here:

Which program is this error occuring in? (Teststand or LabVIEW?)

How long do you run the program until the error occurs? (Are you running it the entire 3-4 months?)

What are the names of your VISA resources?

Are you referencing the VISA resources using the ASRL::INSTR aliases in your program, or something else?

~Daniel

[SteveFeeser]

Which program is this error occuring in? (Teststand or LabVIEW?)

   I am running a TestStand sequence and it is calling a LabView vi to set the power supply.

How long do you run the program until the error occurs? (Are you running it the entire 3-4 months?)

   The system is typically run during 1st shift each day.   Powered off at night.

What are the names of your VISA resources?

   "DCPS1" the power supply

   "DMM"  the multimeter

   "FREQ-CNTR"   frequency meter

Are you referencing the VISA resources using the ASRL::INSTR aliases in your program, or something else?

   The vi specifies the VISA session. 

NI recommended the method of temporary renaming of the handles, but they never gave a long term fix or root cause of the problem.  When it happens we rename each VISA by adding an additional character to the name and Save it.  Them delete the character and Save it again, as the original name.  We do that for each VISA then the TestStand sequence will run with no problems.

Thanks,

Steve

[dnchen]

When you are opening your VISA session with VISA Open, are you referencing the resources names you posted above? I know there have been some issues using the name of the resource instead of the VISA Resource Name. If you click on the resource in NI MAX, under the settings, there should be a parameter for "VISA Resource Name" that is typically in the format of "ASRL#::INSTR". I would try using that name to open the reference instead of "DCPS1" or "FREQ-CNTR".

As for why this is happening, I personally don't know. Is this your only test system? If not, does this occur in other test systems? Has this error ever occured in LabVIEW (or outside of TestStand?)

[SteveFeeser]

We are using the name of the resource and not the VISA Resource Name when working with the equipment.  Is there any white papers or other resources to read on this topic?

We are only having problems with the Windows 7 based test system.  We have a couple test systems running Windows XP and they do not show this problem.  Both are using the same Test Stand and LabView.  All of our tests are running in TestStand and calls to LabView VIs. 

Thanks,

Steve

[dnchen]

In terms of using the VISA Resource Name instead of the name of the resource, there is not much documentation in relation to this particular error, but here is an article briefly discussing using the two. In a sense, the VISA Resource Name should always work.

http://digital.ni.com/public.nsf/allkb/DB5E81EAFC9A463886256AA8005EA2B1?OpenDocument

Here's a documented instance where using the ASRL name solved this issue for another customer:

http://forums.ni.com/t5/LabVIEW/Error-1073807343/td-p/615687