PCI-CAN/XS2 Single wire causing fatal error

[Haagen-Dazs]

Hi Rich_G,

From what you described and linked it does not appear to be a memory leak. Would it be possible to catch that exception in your code? Also, what is the TNDRVIER from and is this driver causing the exception?

[Rich_G]

Hello Haggen-Dazs,

Our IT guys searched for TNDRIVER, Aside from Tennessee Drivers license, It appears to be an HP driver dealing with an X-Window function. Beyond that, it is still a mystery. 

Trying to catch the exception is a challenge. At least at my level. This is a former unix program running in an x-window. We updated the Exceed to eliminate this as a cause of the exception. I have opened another ticket at Aeroflex ATE support, requesting updated API calls from their CAN library. I am hoping this will help. We are not standing still, but you need to chalk the floor to measure our progress...

[Dave.C]

Hi Rich,

Thanks for the update about the open ticket with AeroFlex.  Please keep us posted on any related information they are able to provide. 

[Rich_G]

This is the most recent errors occuring in the event log.

[Rich_G]

Finally got the files to attach

[Dave.C]

Hi Rich,

For the WMI error I'd recommend checking the Microsoft Community Forum.  It appears that they have a fix for that error.

Are you using any touch screen computers?  I found some information about TNDRIVER and some third party industrial computers.

[Rich_G]

We had a touch screen on the old controller/computer, we did not install any support for this on the new controller. We only transferred the one directory tree for the Aeroflex In Circuit Tester. This directory did not include any touch screen files.

I will look to see if any of my colleagues  attempted to install the touch screen software. I should be able to pull it out with the add remove software that comes with the operating system.