USB-8473s Bus Monitor Won't Start

[Bauer_CT]

Hello

I have an 8473s USB CAN module I am trying to get working.

I have MAX 5.5 and CAN 2.7.5 on Windows 7

The 8473s sometimes starts with a nice yellow USB light, sometimes with one that flashes green-yellow, sometimes one that flashes in a pattern yellow two short two long (I think, it's been a while since this one happened and I didn't take good notes on the pattern)

I can expand Devices and Interfaces, and then NI-CAN Devices, and then USB-8473s. Then in the right pane I click on Bus Monitor. And that's the last thing I can do before I have to task kill MAX.

Sometimes I am able to Self Test the unit, sometimes not. Bus Monitor used to take a long time then pop up a confusing message: "NI-CAN: (Hex 0xBFF62103) The firmware of the CAN or LIN hardware no longer responds to commands from the Windows driver, usually due to frequent CAN/LIN or timer interrupts. Solution: For CAN, use comparator/mask (filter) properties to reduce received trafic." After that the Bus Monitor would show it's user interface, but if I tried to Start, it would go Not Responding and never come back (or at least not after a half an hour).

I have two 8473s units, and both respond the same. I have tried different USB ports with no difference. I have tried to repair the CAN 2.7.5 driver, and it did not help.

What else should I do to get Bus Monitor to work?

I wish I had a PCI CAN interface. I don't trust the USB.

Thanks

Keith

[Hooovahh]

Yeah the USB ones can be a bit difficult to get going at times.  But still that doesn't mean they shouldn't work at all.  Do you have another PC to try the devices on?  When the device is seen in MAX, what does the glyph look like?  Is there  a red X or a yellow question mark?  These are signs that the device is there but not quite right, or missing all together.

Only other thing I could suggest is updating MAX to the newest but I'm not confident this would fix it, since NI-CAN is what is actually talking to the device, and making the test panel.  And that version is fine.

[tcap]

Hello Keith,

What does the USB-8473 device show up as in Windows Device Manager?

I am interested to see if this issue occurs on another computer. If you have another computer with the software installed, can you please try to use the device on that computer?

Have you ever had this device working on this computer?

Is it possible to upgrade to the version 14.0 drivers? This might fix the issue.

Regards,

[Bauer_CT]

Thanks for the input.

The machine that is the subject of the original post is the customer equipment. It is an Advantech industrial PC.

I tried it on my development system, a Lenovo Laptop, and it works perfectly.

My current best guess is an incompatibility with the Advantech, some kind of motherboard driver or USB thing. Ugh.

Unfortunately at the moment there's a different fire pulling me away for a little bit here.

I did get an "nicanerr.txt" dump, if it is useful:

[OSINFO_SECTION]
OS=
Workstation
Service_Pack=Service Pack 1 (Build 7601)

[DRIVER_VERSION_SECTION]
NICAN.DLL_VERSION=12.6.2f3
NICANFRM.DLL_VERSION=12.6.2f3
DRIVERS\NICANPK.DLL_VERSION=12.6.2f3
NICANPU.DLL_VERSION=12.6.2f3
NICANTSK.DLL_VERSION=12.6.2f3
NICANCFQ.DLL_VERSION=2.6.0f0
NCVI.DLL_VERSION=2.7.4.12288
NICAN_S1.NFW_VERSION=2050300
NICAN_S2.NFW_VERSION=2050300

[CURRENT_SECTION]
Section_Index=5

[INDEX_0]
Local_Time=
Err_Status=
Function=
[INDEX_1]
Local_Time= 11/13/2014 16:46:27.130
Err_Status= Status:0xb1080002-Location:0x30000000-Internal:0x01080000
Function= ncConfig-CAN0
[INDEX_2]
Local_Time= 11/13/2014 16:47:47.131
Err_Status= Status:0xb1080002-Location:0x30000000-Internal:0x01080000
Function= ncConfig-CAN0
[INDEX_3]
Local_Time= 11/13/2014 16:49:07.132
Err_Status= Status:0xb1080002-Location:0x30000000-Internal:0x01080000
Function= ncConfig-CAN0
[INDEX_4]
Local_Time= 11/14/2014 08:49:01.922
Err_Status= Status:0xb1340103-Location:0x30000000-Internal:0x01340000
Function= ncAction-CAN0
[INDEX_5]
Local_Time= 11/14/2014 09:02:41.046
Err_Status= Status:0xb2e70002-Location:0x30000000-Internal:0x02e70000
Function= ncConfig-CAN0

Thanks again

Keith

[GPIB_Guru]

Are you connecting this to a USB 2.0 port or a USB 3.0 port? We have seen issues on USB 3.0 ports with Windows 7 as the drivers don't ship with Windows and can be buggy. If you have a USB 2.0 port on the industrial PC, you can try that to see if it makes a difference. You may be able to force a USB 3.0 port to use USB 2.0 drivers, but we can investigate this if indeed this is a USB 3.0 issue. (USB 3.0 ports are typically colored blue)