Error: Hex 0xBFFF000E PM100D

[greenious]

Hi,

I got an error message "Driver Status:  (Hex 0xBFFF000E) The given session or object reference is invalid." when I tried to test Thorlabs PM100D PowerMeter and use built in vi called Identification Query.vi. The instrument is detected both on VISA and MAX. I've also installed the instrument driver, so I don't know what went wrong. Anybody has ever got the same problem? 

Thanks a lot.

[Dennis_Knutson]

Where did you get this driver and what kind is it? The error message seems to indicate that it is an IVI driver. Did you install the IVI Compliance Package and did you add the logical name and configure the driver session in MAX? When all is configured correctly with an IVI driver, you should be able to select it by clicking on the arrow of the IVI Logical Name control.

[Yanggao]

I have the same problem. Only I'm using Thorlabs PM300E.

The thing is first I instaled Labview 2009.

Then I Instaled drivers for pm300 series from the oficial website. http://www.thorlabs.de/software_pages/ViewSoftwarePage.cfm?Code=PM300

Then I tried a PM300 Get Power Range.vi, and in a result I got an error that says : Driver Status:  (Hex 0xBFFF000E) The given session or object reference is invalid.

I checked MAX, and the thing is... I can't find PM300E in "Devices and interfaces", nor in software.

I also downloaded software from the official website, and it works perfectly. But I can only get the results from PM300E, I can't configure it from computer.

How do I get rid of this error?

[Peter-E]

The first step here is to make sure that Measurement and Automation Explorer (MAX) can communicate with your device. Since you have the device drivers installed, go through the steps in this KnowledgeBase article:

http://digital.ni.com/public.nsf/allkb/0819391CA91B3EB38625731D00024649

After that, see if the device shows up in MAX. From there, we know that the software can communicate with your device and there may be some settings on the computer/device that needs to be changed to get it working for you!

[Yanggao]

Thank you for the advice.

I did like it was described in the article, but still it doesn't see th PM300E Power and Energy meter.

My guess is that it should be in the "Devices and Interfaces " list, but it's empty.

What else might be wrong?

What puzzles me is that PM300E datalog works perfectly and reads the measurments from the PM300E, but any atempt to configure it from a computer end up being in an error [(Hex 0xBFFF000E) The given session or object reference is invalid.]

[Peter-E]

I see that you downloaded the official software on thorlabs.com. Is this the software you were referring to here:

http://www.thorlabs.de/software_pages/ViewSoftwarePage.cfm?Code=PM300

You must also download and install our NI-VISA drivers here (this link takes you to the Windows download):

http://joule.ni.com/nidu/cds/view/p/id/2659/lang/en

These are the drivers that interface third party devices with our National Instruments software.

[Yanggao]

Yes, that is the software, that I downloaded. It doesn't have problems.I also downloaded the Instrument comunicator, but like I said, it reads only a small fraction of its functions. Most of  them return errors.

Ok, thanks to NI VISA drivers, MAX now sees the PM300 multimeter, but the error (Hex 0xBFFF000E) doesn't go away. MAX reads two PM300E - "Raw" and "Instr".

I opened the VISA test panel for both of them.

1)The "Raw" one gives me error - (Hex 0xBFFF003A) Unable to start operation because setup is invalid (due to attributes being set to an inconsistent state);

2)The "Instr" one does some basic I/O, but sometimes gives an error -  (Hex 0xBFFF0015) Timeout expired before operation completed.

[Peter-E]

Here is something to try:

Whenever you open the VI you are testing with, right click on the "VISA Resource Name" control and select "I/O Name Filtering". Under "Show Aliases" select "All defined aliases for resources of this class" from the drop down menu. After this, make sure you select the correct VISA name (the "Instr" one) and see if you continue to get the 0xBFFF000E error.

I have seen this fix this error in the past. The timeour error that you were receiving in VISA test panels may have to do with the settings of your device not matching MAX/Computer's settings (baud rate, stop bit, parity, etc.).

[Yanggao]

Thank you for your support.

The challenge is still on.

I changed vi instrument handle to " All defined aliases for resources of this class", but regardles he gives me this error. 

[Peter-E]

Hi Yanggao,

In the thorlabs software, what does it call the device? For example, in the manual it has its device string as "USB0::0x1313::0x8020::E00510504::INSTR".

Also, what are the options for the VISA resource name (or IVI Logical Name control) selections in LabVIEW and what do you select?

As mentioned before by Dennis in response to the original post, did you add a IVI logical name for the driver session in MAX? After that, then you should be be able to select it in LabVIEW.