NI PCI 5102 not visible in MAX

[becktho]

Hi all

I've got a problem on a testrig. I use a PCI 5102 high speed digitizer to acquire a signal. Since this morning, the acquisition and processing of this signal has slowed down and now it takes twice as long as before.

What could be the cause of this problem?

During searching for a solution on the system, I found that the device is not visible in MAX. Two weeks ago, I updated the testrig to LV8.0, which means that I made a single installer - more information to this can be found in this thread:

http://forums.ni.com/ni/board/message?board.id=170&message.id=164285&view=by_date_ascending&page=1

As said, I installed this approximately two weeks ago and it ran without any problems until this morning. So I wanted to test the card in MAX so that I maybe find something, but firstly it took a relative long time to open the Items and Interfaces node and secondly there was no item in. No PCI 5102, no Fieldpoint modules, no serial ports - although I use these devices in this app.

Is this maybe related to my original problem of the massively slowed down acquisition?

Any fast answer that helps to solve the problem is really highly appreciated, as this testrig is part of a production line.

Thomas

[Travis_W]

Thomas,

I'm not sure why your 5102 measurements are slowing down, but I do have a likely solution to your issues with MAX.  Hopefully fixing MAX will remedy both problems.

1) Browse to C:\Program Files\National Instruments\MAX.  There is a folder named "Data" that has the configuration info for MAX.

2) Delete the "Data" folder after making a copy on your desktop (it is rare, but in some cases it may be useful to recover old configurations).  If Windows won't let you delete the folder, try ending the nimxs.exe process from task manager.  If you have any tasks or scales saved in MAX, they will be deleted in this step.

3) Reboot your computer and open up MAX.  This will force a refresh of all configuration information for your system, and will most likely clear up your problems with MAX.


Please let me know if this works for you, and if this fixes the issue with your digitizer as well.  If this doesn't help, there are other debugging steps that we can try.

Thanks,
Travis W

[becktho]

Hi Travis

Thanks for you answer - I'll give it a try on Wednesday and inform you if it helped.

Thomas

[becktho]

Hi Travis

20 minutes ago I made what you suggested and, as it seems, the problem is solved. Last week I coded time measuring of the vi where I acquire data and I almost could no believe - time has decreased dramatically from about 13.5s per execution to 1.3s per execution.

May the behaviour described earlier have occured due to SW updates of Win XP? Are there any known issues?

Thanks