Automotive and Embedded Networks

cancel
Showing results for 
Search instead for 
Did you mean: 

NI 9862 comes us as unsupported module in MAX

Solved!
Go to solution

Understood.  Thanks for clarifying.

0 Kudos
Message 21 of 33
(6,177 Views)
I have had similar behaviour on 3 separate cdaq systems (rubbing a mix of xp and win7).
When updating divers with disk that shipped with lv14 any 9862 can devices appear as unsupported devices.
Manually updating the drivers through control panel and device manager, selecting the device allows the 9862/hs device to be selected and the can module then works fine.
Despite having the cdaq chassis connected (with can module installed) during the update the new install option for xnet cdaq support has to be manually selected, which is OK if you know about it...

Probably the poorest driver update experience I've had in 12 years of doing them.
0 Kudos
Message 22 of 33
(5,820 Views)

Hi,

I had the ploblem and I solved it.

If you still have problem let it know here I will help you.

0 Kudos
Message 23 of 33
(3,589 Views)

I have same problem and then need solve method

please reply to  me, I want to your help

 

OS is windows 10 homepack

 

 

0 Kudos
Message 24 of 33
(3,232 Views)

Hi,

Your computer is 32bits or 64bits?

Jerome

0 Kudos
Message 25 of 33
(3,227 Views)

For me, my problem was on XP SP3 32bits comuter.

In the device manager the board was with a yellow triangle...

A section is missing  in a nixntcdq.inf file to install the driver on X86 machin.

I send you the folder in a zip. Go in the device manager and click on update driver then select this folder.

Try and let me know the result..

Jerome

 

0 Kudos
Message 26 of 33
(3,225 Views)

thank you for reply

 

my computer is 64bits.

0 Kudos
Message 27 of 33
(3,226 Views)

Just an idea: You have installed XNET drivers?

0 Kudos
Message 28 of 33
(3,221 Views)

Hi.

I installed NI-XNET 16.1 driver and NI DAQmx Device Driver 16.0.1.

 

 

drivers.jpg

0 Kudos
Message 29 of 33
(3,207 Views)

Have you tried going into windows device manager and manually assigning the XNET driver to the "unsupported device"? Which steps of this forum post have you tried to no avail?

0 Kudos
Message 30 of 33
(3,159 Views)