I have to start MAX for recognizing an other CAN USB device

[shb]

In my project I use a USB CAN converter (NI USB-8473). I have several adapters for different customers. When I connect an other adapter than was connected before, my LabVIEW program only recognizes it when I start MAX.

The adapter receives the same address CAN0 as the previous adapter, but obviously not before MAX is started. This happens when an executable is run (on a computer without LV) or on the LabVIEW development system. I do not have to stop my program.

Why is this? Can I trigger the detection of the converter out of the program?

Greetings,

shb

[SFK · Accepted solution]

Hi shb,

I have tried to reproduce the issue that you are describing with one USB-8472 and one USB-8473. Using the LabVIEW NI-CAN example <LabVIEW folder>\examples\nican\Frame - Basic.llb\CAN Transmit - event based.vi, I could stop the VI, unplug one USB device, plug in the second and re-start the VI without causing any errors...

May I ask you which NI-CAN driver version you are using? I have used the latest one, NI-CAN 2.7, which is available as a "side installation" from NI-XNET (setup.exe can be directed to only install NI-CAN). You can find the download here:

NI-XNET 1.1 - PharLap, Windows 7 64 bit/7 x86/XP/Server 2008 x64

If upgrading does not resolve this issue, I will try to get hold of a second USB-8473 to exactly reproduce your setup...

Best regards.
Sebastian

[shb]

Hello Sebastian,

I will try NI-CAN 2.7 on Wednesday. Currently I use NI-CAN 2.6.3. I hope to mark your post as solution thereafter. Anyway, thank you verry much.

Greetings,

shb

[shb]

Hello Sebastian

This did the trick. Thank you very much. This is the solution plus a kudo at least.

But I have two questions:

- Why is NI CAN 2.7 shown as 2.6.2 when building an installer in LabVIEW? In MAX the version is shown correct.

- Why does CAN 2.7 depend on LabVIEW 8.2.1 Runtime Engine? This does not make sense to me. And I do not have this installer CD here...

Greetings,

shb

[SFK]

Hi shb,

the indicated version 2.6.2 of NI-CAN during the creation of an installer/deployment is just a cosmetic issue NI R&D already knows about. It is filed under the reference CAR# 214017 and should be fixed in an upcoming version of NI-CAN.

As for the dependency on the LabVIEW 8.2.1 run-time engine, I can only guess that maybe NI-Spy (which is included with NI-CAN) is programmed in it. If you have downloaded NI-XNET 1.1, you should find the necessary setup msi file in the following directory:

<extraction directory>\Products\LabVIEW_Runtime_Engine_82\lv82rte 

Best regards,
Sebastian