Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

about error message of "MTD 0002" when connect PC DAQ card with Chasis

We have a PC Daq Card NI6036E and a 4-slot Chasis modules. In more than half times when I plug the chasis cable to the DAQ card then power up both chasis and laptop, there will pop up a message of "MTD 0002 new hardware found". If checked in MAX, then neither the card or chasis modules will show up.
What I do every time is that power down both devices, disconnect them and connect them to make sure PC card not loosed, then power up to see my luck. Sometime it works sometimes it still doesn't.
We use panasonic tough book laptop.
Are there anybody encounter same problem ?
Any solution or advice?
 
But with daq card along(leave the card inside PC and not connnect to chasis), there's never such problem. No clue at all.
 
0 Kudos
Message 1 of 10
(7,032 Views)
Hi feilong,

Have you tried this out in another laptop to see if the behavior shows up?  What version of DAQ drivers are you using on the system with the 6036E, and what model Toughbook are you using?  Because the 6036E is detected correctly without the SCXI chassis connected, it seems like there may be an issue with the BIOS of the system.  I would check to make sure that you have the latest BIOS update for your Panasonic laptop, and if you are not currently using the latest version of DAQ drivers (Traditional NI-DAQ or DAQmx, whichever applies) upgrade those as well.

Regards,
Andrew W
National Instruments
0 Kudos
Message 2 of 10
(7,021 Views)
Thanks Andrew. I tried to download the driver but it seems the ftp server not easily accessed. I also found the problem reduced when the DAQ card powered off for sometime (make it cooler).
 
0 Kudos
Message 3 of 10
(7,019 Views)
 

Hi feilong,

I did not run into any problems trying to download the drivers this morning, so your network may be keeping you from accessing the files. 

Regards,
Andrew


 
0 Kudos
Message 4 of 10
(7,007 Views)
DAQcard 6024E recognized as generic memory card MTD 0002 in device manager, unseen in MAX.  Using NIDAQ 6.9.3.  Ongoing, intermittant problem with multiple cards, multiple computers.  Using Panasonic Toughbook Models CF-M34, CF-27, CF-18, and running Windows 2000 or XP Pro.  Cards check out OK in E-series online diagnostic utility.  Have performed IRQ conflict trouble-shooting to prevent OS lock-up at moment PCMCIA DAQcard is inserted.  Currently have all USB, audio, and other IRQ 9 assignments disabled in DM. 

Once successfully was able to get Device Manager to re-designate card as DAQcard on my machine that otherwise performed OK (CF-M34 W2K), but the other 96 attempts with customer's problematic CF-18 (XP Pro) failed.

Have reinstalled NIDAQ software about 6 times in coustomer's CF-18, using MSIblast
first to purge reg, but no joy.  Am ready to go postal, my customer is in the field, dead in the water, and the meter is running.  Please!!!
0 Kudos
Message 5 of 10
(6,409 Views)

Hi jenhim,

 

 

I may suggest upgrading to the latest DAQ driver (Traditional NI-DAQ 7.4.4). I’m assuming the program is written in Traditional as you mention 6.9.3, correct? Since this is an urgent issue, are there other computers which the customer can use for now? Or other DAQ devices?

It is good that the card is recognized as a device, but what does device manager show? (Please post a screenshot as it will eliminate any ambiguity). Although the device manager does not find the drivers, can you update the cards drivers and point it to them manually? (Right-click >> Update driver >> Install from list or specific location >> ‘Don’t search. I want to….’ >> do any drivers appear on the next screen (see ‘update driver1.jpg’)? We are looking to see how much the computer recognizes about the card – does it recognize what type and model device it is, even though it cannot find the driver?

Lastly, it does not look like this is an isolated issue, as a google search results others finding the same ‘MTD 002’ issue with other computers and devices. 

 
David L.
Systems Engineering
National Instruments
0 Kudos
Message 6 of 10
(6,398 Views)
Hi David,  This is really beginning to wear me down, but I've found a few indications of what's going on.  First, to summarize: My customer bought a test system from us in February that included a Panasonic Toughbook CF-18 (XPPro, SP2) and a 6024E DAQcard.  A hard drive failure forced a warrenty return to Panasonic.  They replaced the HDD, the Motherboard and the PCMCIA sockets (I've no idea what was going on with all that).  When the machine was returned, he reinstalled NIDAQ 6.9.3.  The DAQcard from thence on is seen only as a "Generic Memory card MTD-0001" in Device Manager, and not at all in MAX.  He shipped the whole system back to me.  After bashing around with the device manager a bit,  things further deterioated to the point where insertion of any PCMCIA card locked up all input resources.  Leaving it powered down without the battery for a while helped the lock-up problem briefly. 

Following a recommendation to examine the IRQ assignments, the System Info panel indicated that the sound adapter, 4 usb ports and the 2 PCMCIA slots were all on IRQ 9.  Disabling all of the above reliably solved the lock-up on insertion problem, but the customer's 6024E still was not correctly identified, nor wereeither of my "good" DAQcards.

This was about the time (and about 12 hours of troubleshooting later) that I posted my initial request for help.  (NOTE:  I was mistaken when I said that both the "good" and the "suspect" DAQcards passed the online E-series diagnostic.  The suspect card failed detection.  Those results, such as they are, were submitted from the test panel.)

In response to your suggestion, I updated the CF-18 to NIDAQ 7.4.4 and got identical results.  In addition, both my DAQcards (6024E) that I use in my lab were also  incorrectly enumerated and unseen in  MAX. I reinstalled the entire OS from the manufacturer's OEM reocvery disc set, reinstalled NIDAQ 7.4.4 and still had the same result. 

My two 6024E DAQcards function perfectly in both of my Panasonic CF-M34s (one is Win2000 and one is XP), but my customer's DAQcard still appears as an unrecognized device MTD-0001 or similar in both of those machines!  I was able to force the DM in one of my CF-M34 machines to update the driver of the "MTD-0002" to a DAQcard 6024E, but it appears with a yellow exclaimation point, and crashes MAX instantly.

I should also note that I have at least one other customer with an identical setup - CF-18 Toughbook and 6024E that works without any problems.

From this, I am able to deduce that the customer DAQcard has a problem.  Perhaps a blown fuse?  Checking the allowable voltage limits for the CF-18 PCMCIA slots (3.3V, 400MAh and 5V, 400MAh), they should tolerate the 5v 270MAh DAQcard withoug a problem, although I've seen this mysterious MTD-0002 error discussed in fourms in relation to inadequate socket power for other devices.  Since I have a duplicate system I use as my own back-up, I will ship it off to my customer while I attempt to solve the issue with help from NI and Panasonic help desks, and the obtuse information sometimes available from Microsoft regarding how to redistribute the IRQs (They've got a terse paper with the catchy title: "How to force a hardware abstraction layer during an upgrade or installation of XP"  that appears to be next on the hit parade.

Any help you can render will be gratefully accepted.  Thanks, Jenn

0 Kudos
Message 7 of 10
(6,378 Views)
It's a month later now.  I sent the cards back to NI and the PC back to Panasonic.  Both returned last week with "no problem found".  I have the same problem now that I had a month ago (including the 15 days NI wasn't finding any problem).  PC locks up upon insertion of card, "new hardware found" declaimation of a "generic memory PCMCIA card: MTD-0000 or MTD-0001 or MTD-0002.

I have reinstalled the O/S, combed the MS support files, upgraded, rolled-back, booted safe, uninstalled, reinstalled, tweaked the registry, thrown my hands up in the air, and performed another clean install,
 
and

combed the MS support files, upgraded, rolled-back, booted safe, uninstalled, reinstalled, tweaked , thrown my hands up in the air, and performed another clean install,
 
repeat ad nauseum.

My NI tech said the issue would be resolved with a complete O/S reinstall the the latest NIDAQ drivers (7.4.4)  Not working.

There are numerous references to this MTD-000x error in the NI forums.  Can someone there (preferably with brains) figure this out once and for all?

I am tired of wasting time, wasting money and wasting my usually good humor on this problem.

Please advise.

Jennifer
0 Kudos
Message 8 of 10
(6,185 Views)

Hello Jennifer,

I am sorry for the frustrating situation.  Please let me know the RMA (return material approval) number or service request number you used to return the 6024E.  This will let me look into some specifics and be able to access your contact information.  Would it be okay to contact you directly if needed?

Samantha
National Instruments
Applications Engineer
0 Kudos
Message 9 of 10
(6,158 Views)
 


Please reference RMA 1172099 for the first half of this situation.  The application engineer I've been working with just today assigned a new service request regarding the PCI 6024 E cards showing up as MDT-0000.  That service request number is 1190715.  Please contact me directly.  It seems enevitable that bits and pieces get overlooked when one attempts to describe a troubleshooting scenerio in a forum posting. 

I can also send you a few dozen links to somewhat relevant topics from the MS suppoort KB, various web help forums and the NI support forum/KB.  In particular, I am wondering if the "core driver update", written specifically for a recognition problem an HP
BIOS will be the solution.  Please see the link below:  https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9MqSAK&l=en-US  I'm reluctant to apply a BIOS patch (if that is what it is) if is is specific to HP, since I've got a small fleet of Toughbooks.

I look forward to hearing from you. 

Jennifer

0 Kudos
Message 10 of 10
(6,145 Views)