Sorensen XG 40-21 communications crash

[Rawhyde]

Hi,

I inherited a LabView application that controls 30 Sorensen power supplies.  It has a communications crash about once a week that is driving me nuts.  See the attached image for an overview of the communications architecture. The application communicates with the supplies to turn them on/off and once on, polls constantly for supply status: current, voltage, interlock. 

When it crashes, I’m able to stop and restart the LabView app OK, but it doesn’t resolve the problem.  A PC reboot is required.  I don’t have to touch the supplies to recover. Once the error occurs, it cannot talk to any of the supplies.  It starts with an error code: 0xBFFF0000. I've also attached a text file of the IOTrace.  It almost seems like the FTDI driver is getting locked up. 

As far as I can tell, it doesn't use the Sorensen LabView drivers.  I don't know if it's a home rolled version or leveraged from something else.  A zip of those are attached as well. 

System particulars:

 - Windows 7 PC

 - FTDI driver 2.8.28.0

 - LabView 2011

 - Visa 5.1.2

I appreciate any ideas and help. 

Kind regards

Mike

[margasan]

Hello Raw

You mentioned the app is crashing, do you have a DMP file fromthe crash that may help us to determine what is going on behind scenes??

Regards

Mart G

[Rawhyde]

Hi Mart,

Thanks for the reply.  Sorry, I don't think I was very clear.  The LabView application doesn't crash.  It has a 'Stop' button to force an orderly shutdown and that works OK.  It also starts back up OK.  The application PC also seems fine. It's only the communications that crashes and it seems to require a reboot to recover. 

The communications failed again this past weekend (in fact, the last three have all been on the weekend?!?!?).  I used the sysinternals procexp to create a dmp file and looked at it in Visual Studio.  It didn't seem that interesting and it's quite large (240MB).  I will post it if need be. 

What I did notice was that USBView looks different during the communications failure.  The Bad attachment shows 2 pipes but only one set of end points.  Without rebooting the PC this time, we unplugged and plugged the cable back in again.  The application is now communicating OK and the USBView shows two sets of endpoint descriptors. 

Kind regards

Mike