Ni 5102-PCI Initialize failed at resource name

[Labview Resistance Measurement]

I got a error on Ni-5102-PCI when i run niScope Initialize.vi.

Error is "resource name is not assigned to a Ni ossciloscope even I set driver session for the right resource name: DAQ::1::INSTR

From Max, hardware device is showed and run Test Panel (soft front panel) OK!

all soft. drivers installed as following:

-Traditional Ni-Daq ver.7.4.1f

-Ni visa 4.0

-Ni Scope 2.9

Please help me to solve the problem!

Thanks!

Tran

[Matt_A]

Hello Tran,

The first thing that I would suspect is your naming convention for the resource name. If you examine the help file for niScope Initialize with Options here, you will notice a chart that shows the correct format for the resource name input. The chart shows that for Traditional NI-DAQ devices the correct format is: "DAQ::1 (1=device number)". I believe what you have shown is the VISA device name for the device, which is of the format "PCIn::y::INSTR" for PCI bus n and PCI device number y.

If you continue to experience this error, it may be helpful to post some more specifics of the problem. The error number or description would be very helpful, and a screenshot of the pop-up window would be even better. I hope this information is helpful. Let me know you need anything else.
 

[Labview Resistance Measurement]

Hi Max,

Thank you very much for your recommendation. However, the name of resource I set is the same as your suggestion as following:

DAQ::1

but it sill did not work.

I attached some srceenshots below:

Thanks again!

Tran

[Matt_A]

Hello Tran,

It sounds like LabVIEW is not getting the correct device name, but I am not sure why. It is possible that there are extra characters (like a line break) in the "resource name" control that we cannot see. I would recommend that you delete the "resource name" control and place a new control for the resource name input to the ni-Scope Initialize.vi. Then re-type "DAQ::1" into the new control so that we can be sure that there are no additional characters in the string. If you still get an error after this option, I would recommend the following steps:

If possible,

1. Try the same code with a different PCI-5102.

2. Try the same code with a different NI digitizer.

3. Try the same code with the same PCI-5102 on a different computer.

This should tell us if there is a problem with this specific device. I would also suggest:

4. Try running a shipping example to determine if the problem persists with every LabVIEW program, or just this one. I would recommend niScope EX Getting Started.vi.

Let me know if these steps help or if you continue to experience the problem.

[DFGray]

One other thing you can try - run the NI-SCOPE Soft Front Panel.  If you can run your device from the Soft Front Panel, your software is configured correctly.  Look at the device name reported by the Soft Front Panel and use that.

Note for the future - these devices will not work correctly unless you have run MAX once since installation, but you have done that.

Let us know if you are still having problems.

Message Edited by DFGray on 02-20-2007 08:02 AM

[Labview Resistance Measurement]

Thanks for all your suggestions. the error caused by niscope.dll located on the incorrect path file that stored old ver. of niscope.dll. now, I can run niScope initialize.vi without any error. however, when i run niScope multi read cluster.vi, it failed at exceeding time operation.(even i setup more timeout at 100ms)

Do you have any idea to solve this problem ?

attached is block diagram and front panel for overview.

software version:

niscope.dll ver. 2.9.1

labview ver. 6.1

Thanks for your help!

Tran.

[Labview Resistance Measurement]

Thanks for all ! I finally fixed them.

[lgenerali@vicr.com]

Hi, I'm having a handful type of problems with the NI PCI-5102. I had the problem with the niScope Initialize.vi but that is ok now that I open M&A before using it. Right now, my main problem is that I get the niScope Multi-Read Cluster.vi 'Max Time Exceeded' error sometimes, as well as the niScope Multi Fetch Measurement Stats.vi 'Hasn't crossed middle level 3x' error. Sometimes I don't get the error, but the card still reads higher peak input voltage than our other cards (>2V higher). This was happening on another card, so we sent that one back for calibration and couldn't be calibrated. So maybe this card is damaged, but it feels like a driver-type issue. Any help would be greatly appreciated. Leo

[lab_boy]

Hey,

Try reducing the number of records fetch per cycle or reduce the sampling rate and see if the error still persists. Also try running the example VI for continous acq using NI-Scope this might help you see too.

Good luck

-lab

[lgenerali@vicr.com]

Hi,

Thanks for the ideas...turns out our cards are damaged (I suspect we might have overdriven the inputs).  I put a known good 1khz 5Vpp square wave in, ran the Soft Front Panel application and it only captured some of the waveforms, then dropped to some negative voltage reading.  So our frequency measurement still worked sometimes when there were enough midpoint crossings.  But our peak to peak voltage measurement never read correctly, because of the drop to a negative voltage (would give us a faulty high Vpkpk reading).

thanks for your help.

Leo