Part of tagger problem

[mnolte]

Hi there,

since downgrading from NI-DAQ 8.3 to NI-DAQ 8.0 due to problems with USB2.0 cameras, we experience several problems:

1. On computer startup, sometimes the message "Part of tagger" appears and offers to send an error report. In this case the USB-6501 is shown as not available in Measurement & Automation explorer. If you disable and re-enable it in the device manager it is available again.

2. Using the device sometimes leads to a point where the device doesn't respond (even in the Measurement & Automation exporer). A self test done within this programm yields an error. Once I tried to reset the device there and received an error -50004.

I noticed that installing drivers also installs a firmware loader in the USB-6501. Maybe the drivers, firmware and firmware loader have to match and this may now not be true due to downgrading.

Does anybody experience the same problems or maybe know a solution without reinstalling the whole PC?

Thanks,

Markus

[mnolte]

Some additional information. After enabling assertions in the registry I was shown a message with the following content on computer startup:

---------------------------------------------------------------------------------
Unexpected Program Condition!

An unexpected condition occured. Contact National Instruments with this information.

Module: C:\Programme\National Instruments\Shared\Tagger\tagserv.exe:
File: C:\Penguin\jak\tagger\stable\ni\tagger\config\Subsystem.cpp
Line: 192

Message:
Unexpected std::exception caught
Description: ImxsStorage::EnumObjects
---------------------------------------------------------------------------------


Maybe this help.

Markus

[mnolte]

After clicking the OK button, even more information (roughly translated to english language):

The instructions at "0x00446620" points to memory location "0x00000000". The process "read" couldn't be performaed on memory.

Markus

[mnolte]

And here another happy startup message. Same as above, but the message part is different:

Message:
Unexpected ni::dsc::exception caught
Thrown From File C:\Pengui\jah\tagger\stable\ni\tagger\config\mxs\MXSAccess.cpp
Thrown From Line: 69

Description: COM error


This time, the device is present in Measurement & Automatiion Explorer. A self test yield -88705 (The device is either not present or not active).


Have fun,

Markus

[Christian Mergl]

Hello mnolte,

You downgraded from NI-DAQmx version 8.3 to 8.0. Could you please explain the steps how you did it? Which OS do you have and which other NI software?

Regards, Christian

[mnolte]

Hi Christian,

steps how I downgraded:
- Uninstalled all software via SystemControl -> Software
- Restartet computer
- Installed NI-DAQmx version 8.0

The OS is Windows XP (Professional).

There is no other software from national instruments except the software provided by the NI-DAQmx-CD.
If you choose "National Instruments-Software" there and select "Change" you see the following sofware installed:

NI LabVIEW Runtime Engine 7.1.1
NI Measurement & Automation Explorer 4.0
NI Measurement Studio Common .NET Language Assemblies for the .NET Framework 1.1
NI Measurement Studio for VS2003 Update 7.1.0.308
NI PXI Platform Services for Windows 1.5.1
NI VI Logger 2.0.1
NI-DAQmx 8.0

All the best,

Markus

[Christian Mergl]

Hi mnolte,

There is other NI-SW installed on your system, besides those provided from the NI-DAQmx driver CD. You have installed Measurement Studio for VS 2003 support.

The NI-DAQmx 8.0 driver also supports the USB-6501, so "normaly" this should work without problems!

In your first post you said, after resetting you device in the HW-manager it was present in MAX. Then you did a self test, what generated an error. Do you know the

error message and if there was one also the error number?

Also in your first post you talked about problems with USB cameras, maybe this was the reason of the strange behaviour of the USB-6501.

Are you able to install the DAQmx driver on another system and try to run the USB-6501 there?

BR, Christian

Message Edited by Christian_M on 11-23-2006 11:28 AM

[mnolte]

Hi again,

ok, there is other NI software installed, but it all came from the NI-DAQmx driver CD.

After starting the computer, the device didn't work in my program so I started MAX. The USB-6501 showed up as "Dev1" and the serial number shown was 0x0.

A self test yielded error number -88705:
Possible reasons: The device is not present or not active in the system. The device is either not installed, has been disconnected or is not corretly installed.
Device: Unknown device

In this case, de- and reactivating the device in the device manager does not change the situation.

Due to this message I already uninstalled all NI software and reinstalled everything. Unfortunaltely the problem still remains.

The mentioned cameras worked properly until upgrading to the software on the NI-DAQmx 8.3 CD. So we decided to go back to the working configuration, but now cope with the mentioned problems.

Right now, all system do both have cameras and USB-6501 installed. This problem is not that severe on the other systems.

My guess is still that the software installation and deinstallation didn't word properly. Do you know a way to definitely get rid of all installed NI software and then reinstall it?

Cheers,

Markus

[mnolte]

To add to my previous message:

On restarting the computer, I got the same message and errors as mentioned im my second message. Starting MAX shows the device "Dev1" as not present or disabled and MAX only gives you the option to delete it.

If you now use the device manager to de- and reactivate the device, it will show up as present and the self test runs successfully (although the serial number is still 0x0, but this is a minor issue, which is solved by restarting MAX).

Markus

[Christian Mergl]

Hi mnolte,

There are many reasons for this error, but in 99 out of 100 it is due to a bad installation of the driver!

And yes, there is another way to uninstall NI-SW, the MSI-Blast. You will find it under ftp://ftp.ni.com/outgoing/ as a zip file.

Please uninstall all NI SW using MSI-Blast from your System and reinstall it again.

BR, Christian