LabVIEW code problem proving tough

[CRoebuck]

Hi all

OK here's my problem. I worked on a LabVIEW code project for 3 years from version 1.0 thru version 15.3 (Started in LabVIEW 7.0 and is now 8.2). The project is an RX and TX Test for an RF module. The code uses many GPIB instruments (VISA) and some Serial (VISA) and also 2 IVI drivers (Arb and DMM) and also an external DAQ board that comes supplied with a "LabVIEW" driver (Actually VI wrapper around naked DLL calls but hey....it works). About 12 months ago I handed off the project another developer. Recently he came to me with this problem having made lots of changes....

Sometimes when launching the code WIndows displays a dialog stating that "MWU Test has encountered a problem an needs to close"......then the software closes. This is a windwos dialog not a LabVIEW message.

This can happen 5 or 6 times in a row but at different points during the test, sometimes after 1 minute sometimes after 3 minutes, sometimes never !

Once the test has run through once the site remains stable for weeks or months at a time with no repeat of the error. When installed on high spec PC's the problem seems to get worse.

IF the code is run using the LabVIEW IDE then the problem never occurs, only when using LVRT.

The last time I saw the error I captured the Windows error log which was as follows;

Anybody familiar with these error logs.....does it say what is causing my problem ?

<?xml version="1.0" encoding="UTF-16"?>

<DATABASE>

<EXE NAME="MWU Test.exe" FILTER="GRABMI_FILTER_PRIVACY">

<MATCHING_FILE NAME="MWU Test.exe" SIZE="7458816" CHECKSUM="0x372712AF" BIN_FILE_VERSION="16.2.0.0" BIN_PRODUCT_VERSION="16.2.0.0" PRODUCT_VERSION="16.2" COMPANY_NAME="Filtronic ICS" PRODUCT_NAME="MWU Test" FILE_VERSION="16.2" INTERNAL_NAME="MWU Test" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="16.2.0.0" UPTO_BIN_PRODUCT_VERSION="16.2.0.0" LINK_DATE="07/27/2006 10:04:02" UPTO_LINK_DATE="07/27/2006 10:04:02" VER_LANGUAGE="English (United States) [0x409]" />

<MATCHING_FILE NAME="data\lvanlys.dll" SIZE="892928" CHECKSUM="0x7B041BCE" BIN_FILE_VERSION="8.2.0.0" BIN_PRODUCT_VERSION="8.2.0.0" PRODUCT_VERSION="8, 2, 0, 0" FILE_DESCRIPTION="AAL for Win32" COMPANY_NAME="National Instruments" PRODUCT_NAME="LabVIEW" FILE_VERSION="8, 2, 0, 0" ORIGINAL_FILENAME="lvanlys.dll" INTERNAL_NAME="lvanlys.dll" LEGAL_COPYRIGHT="Copyright @ 2005" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="8.2.0.0" UPTO_BIN_PRODUCT_VERSION="8.2.0.0" LINK_DATE="07/12/2006 03:44:01" UPTO_LINK_DATE="07/12/2006 03:44:01" VER_LANGUAGE="English (United States) [0x409]" />

<MATCHING_FILE NAME="data\lvsound.dll" SIZE="24576" CHECKSUM="0xCC0527F4" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="11/22/2002 22:11:37" UPTO_LINK_DATE="11/22/2002 22:11:37" />

<MATCHING_FILE NAME="data\LVWUtil32.dll" SIZE="33280" CHECKSUM="0x4A7372B6" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="11/05/1998 17:14:06" UPTO_LINK_DATE="11/05/1998 17:14:06" />

<MATCHING_FILE NAME="data\lvzlib.dll" SIZE="55296" CHECKSUM="0x646D2CF9" BIN_FILE_VERSION="1.1.4.0" BIN_PRODUCT_VERSION="1.1.4.0" FILE_DESCRIPTION="zlib data compression library" PRODUCT_NAME="ZLib.DLL" FILE_VERSION="1.1.4.0" ORIGINAL_FILENAME="zlib.dll" INTERNAL_NAME="zlib" LEGAL_COPYRIGHT="© 1995-2002 Jean-loup Gailly & Mark Adler" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x1000E" UPTO_BIN_FILE_VERSION="1.1.4.0" UPTO_BIN_PRODUCT_VERSION="1.1.4.0" LINK_DATE="11/08/2002 19:49:34" UPTO_LINK_DATE="11/08/2002 19:49:34" VER_LANGUAGE="English (United States) [0x409]" />

<MATCHING_FILE NAME="data\tc0832.dll" SIZE="67584" CHECKSUM="0xE51DA08F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="03/14/2035 01:15:49" UPTO_LINK_DATE="03/14/2035 01:15:49" />

<MATCHING_FILE NAME="PLL\lmx2330x.exe" SIZE="99154" CHECKSUM="0xCA65A81D" MODULE_TYPE="DOS" />

<MATCHING_FILE NAME="PLL\lmxload.exe" SIZE="15218" CHECKSUM="0xF701B28" />

</EXE>

<EXE NAME="lvrt.dll" FILTER="GRABMI_FILTER_THISFILEONLY">

<MATCHING_FILE NAME="lvrt.dll" SIZE="10406400" CHECKSUM="0x476318B9" BIN_FILE_VERSION="8.2.1.4002" BIN_PRODUCT_VERSION="8.2.1.4002" PRODUCT_VERSION="8.2.1" FILE_DESCRIPTION="LabVIEW 8.2.1 Run-Time Engine" COMPANY_NAME="National Instruments Corporation" PRODUCT_NAME="National Instruments LabVIEW Run-Time Engine" FILE_VERSION="8.2.1" ORIGINAL_FILENAME="lvrt.dll" INTERNAL_NAME="LVRT DLL" LEGAL_COPYRIGHT="Copyright © 2007 National Instruments Corporation" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="8.2.1.4002" UPTO_BIN_PRODUCT_VERSION="8.2.1.4002" LINK_DATE="02/21/2007 23:10:47" UPTO_LINK_DATE="02/21/2007 23:10:47" VER_LANGUAGE="English (United States) [0x409]" />

</EXE>

<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">

<MATCHING_FILE NAME="kernel32.dll" SIZE="984064" CHECKSUM="0xF12E1D4A" BIN_FILE_VERSION="5.1.2600.2945" BIN_PRODUCT_VERSION="5.1.2600.2945" PRODUCT_VERSION="5.1.2600.2945" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2945 (xpsp_sp2_gdr.060704-2349)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF724D" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2945" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2945" LINK_DATE="07/05/2006 10:55:00" UPTO_LINK_DATE="07/05/2006 10:55:00" VER_LANGUAGE="English (United States) [0x409]" />

</EXE>

</DATABASE>

Cheers

Chris

[orko]

QUOTE(CRoebuck @ Jul 17 2007, 03:41 AM)

The code uses many GPIB instruments (VISA) and some Serial (VISA) and also 2 IVI drivers (Arb and DMM) and also an external DAQ board that comes supplied with a "LabVIEW" driver (Actually VI wrapper around naked DLL calls but hey....it works).

This is just a wild stab in the dark...

The one driver that stands out for me in your above error dump is the tc0832.dll, which is a datalogging interface used by Pico hardware (serial thermocouple, by chance?). The latest version of this driver (which is dated Jan 03 2006), according to its documentation was "tested using LabVIEW for Windows 95 version 4.0". I don't know if you are using the latest driver, since it appears this project is a few years old and I'm not sure if you've updated it. Even if you have the latest, it looks like LabVIEW support for it isn't very high on the priority list for Pico.

Is there a way to isolate this driver call out of your program and see if your error still occurs? Like I said, this is just a guess at this point with the info you've given us.

BTW, did you notice that the "LINK_DATE" on the tc0832.dll line is way off in the future?

LINK_DATE="03/14/2035 01:15:49" UPTO_LINK_DATE="03/14/2035 01:15:49"