ncconfigcannet.net won't execute

[pr0grammer]

In the nican.dll library, the first call ncConfigCANNet.vi will not execute and just freezes.  I have installed NI-CAN, NI-XNET drivers, CAN-XNET compatibility and it just locks up in the .dll call, no error message or anything.  BAUD rate is 125000 and I can see the card 8512 in MAX (CAN1).  CAN1 and 125000 is fed into the .dll

Funny thing is that this code worked on a different machine ... not sure what the difference is.

Thank you in advance for your help.

[pr0grammer]

UPDATE:  It is not the particular vi but the whole nican.dll library that will not execute.

Am I missing some .dll file in Windows32 ?

[pr0grammer]

Also, this is on the target machine running LV RunTime Engine 2010

[Larry_H]

Hello,

I have a couple of questions to help me further troubleshoot your issue:

1. What error code are you receiving in LabVIEW?

2. What version of the drivers are you using on the target computer that is not working?

3. What version of Windows are you using on the target computer that is not working?

4. What version of Windows, LabVIEW, and NI-CAN driver are you using on the development computer that is working correctly?

5. When you installed LabVIEW and the drivers on the target computer that is not working, what order did you install the software in?

6. When you refer to the target machine, are you implying that you're trying to run a deployed application on a machine that only has the LabVIEW run time engine installed and nothing else?

7. Is the computer that you developed your application on Windows 32 bit and the target machine Windows 64 bit? Or are they both Windows 32 bit?

[pr0grammer]

Larry,

1. No error in LabVIEW, program just locks up, I can't even abort on the STOP I have to ctl alt del

2. CAN 2.7 and XNET 1.1

3. XP embedded

4. CAN 2.7, LabVIEW 2010, Windows 7

5. I actually believe the NI CAN and XNET drivers may have been before the LV Run Time Engine 10 install

6. Basically yes, other LV drivers

7. The development machine is 64 and the deployed machine is 32

Thanks for the help!

[Larry_H]

Hello,

I see that you're using Windows 7 64-bit on your development computer, and Windows XP Embedded 32 bit on your target computer. On your development computer, were you also developing in LabVIEW 64-bit? I ask because the behavior you're seeing almost implies that the application was developed under a 64-bit environment and according to this KnowledgeBase: http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98 an application built in an 64-bit environment cannot run successfully on a 32-bit target computer.

Have you tried to running your application on another 64-bit machine?

Larry

[pr0grammer]

I am developing on 32 bit LabVIEW (x86)

[Larry_H]

Hello,

I apologize for this, but I should have asked this is in the beginning, was the applicationg ever working on your target machine? If yes, what changed in between the last time it worked correctly and now. If no, have you tried repairing your NI-CAN driver through the Add/Remove Programs under control panel.

Also, have you tried distributing this application to other computers and seen similar behavior?

[pr0grammer]

Hello,

I have 2 target machines, same exact machine, just "think" I loaded everything the same as far as drivers and everything else.  On one of them it worked but unfortunately that one crashed and now I am stuck with the 1 target machine that doesn't work for now.

Yes, I have tried re-installing the drivers.

Not the exact code because we don't have an extra PCI/XNET/CAN card to install on a machine.

[Larry_H]

Hello,

With the behavior you're seeing, our next step is to take your custom application out of the equation and see if the problem resides with your CAN/XNET driver or LabVIEW Run-Time Engine. To do this, I would suggest two things:

1. On your development computer, develop an application based around one of the example programs from the Example Finder that uses NI-CAN and is compatible with your 8512 card. Transport this new executable to your target machine and try to operate it. Do you see the same behavior?

2. After completing number 1, using your development computer, develop a basic application that utilizes basic LabVIEW functions and does not use the CAN/XNET driver. Transport this new executable to your target machine and try to operate it. Do you see the same behavior or does it work fine?

I look forward to your results.