NIScope_init message on PCI-5102

[Macromer]

I was running with a PCI-5102 and a 1200 board in a computer which periodically was giving me conflicts.  Once in a while the system would reboot.  We had seen this with other systems and had purchased another board to correct the problems (6025E).

I removed the 1200 board and installed the latest version of NIScope (3.5.1) for the PCI-5102.  The software in this set up does not require the 1200 board.   Now the system is just returning a message NIScope_init when I try and run the same software.  I have reloaded the software, rebuilt the entire software on the system and swapped boards with another system that was running.  Nothing has worked and I am just getting the same message returned.

On the second system I swapped boards with, the board from the 5102 from other system needed to have the driver reloaded.  Now the software in this system is also returning the same NIScope error message and I can not run this system either.

In measurement and automation explorer I can access either 5102 board and obtain a signal back from the boards.

Help!!!!

[Lars_L]

Hey Macromer,

Could you give us a little more information on what happens when you run your program? Specifically, are you seeing and error and if so, then what is the error code, description and when does it occur?

Also, it sounds like you are running an executable on a deployed system. Is this the case or do you have the LabVIEW development environment on these machines?

Also, you mentioned that you are getting this error after removing the PCI-1200 board. Does this error go away when you replace the board?

Finally, have you tried running any of the NI-Scope shipping examples on these machines?  If you don't have the development environment then you could build a simple distribution with a generic example and deploy it. Here is the location of the examples: C:\Program Files\National Instruments\LabVIEW 8.6\examples\instr\niScope

Let me know!

Lars

[Macromer]

John P of NI and I have been working on this.  The only message I get back is the NIScope_init in a box.  I do not get any code back on the screen.  The message appears to return as soon as I access the board in the program to collect data.

Both machines Labview on the systems but not the development environment.  I don't believe our program is getting to the Labview sequences, but appears to be crashing on the initial NIScope initialization.  The sequence in the program the checks if the board is talking to the system.

I am getting the message after the board driver has been reinstalled.  The boards are back in the systems and the systems are recognising the boards.  I can access the boards through the NI test software.  I am concerned that the problem relates to the sequence of the board installation?

I have not tried the shipping examples.  I will attempt this.

[Lars_L]

Hey Macromer,

After talking to John P about the history of your issue, it sounds like you are dealing with compiled code and thus you cannot see how your executable is referring to your devices.  If this behavior starting appearing after removing and reinstalling devices, then you are most likely running into issues because the devices are being given new names (Dev1 or Dev2 for example) in your driver and the program is most likely looking for the wrong name. 

To fix this without editing the source code I think you have two options. The first option is to open up Measurement and Automation Explorer (MAX) and check what the devices are named and see if it is obvious what the program expects them to be. If the program goes with the default device names then you might just be able to switch them back. If it doesn't use the default names then you will have to get more information about the source code to find out what the program is expecting. 

Lars

Message Edited by Lars_L on 05-11-2009 12:50 PM