LabVIEW
Exception: Noncontinuable exception (0xC0000025) at EIP=0x00000000 immediately after running VI
Solved!
@bpick17 wrote:
Hello,
My group has recently purchased a hall sensor readout device from Paragraf and they sent us several VIs, an example program, and DLL code to run it. However, when I run the example code labview immediately crashes giving me the the Exception: Noncontinuable exception (0xC0000025) at EIP=0x00000000 error message.
If a DLL is involved this is always the first culprit to look at. A wrong configuration of the Call Library Node for some of the functions is a possible reason. A bug inside the DLL is just as possible.
Just because they sent you a VI library and DLL does not mean that someone with the necessary knowledge has created them. Quite often it is done by some intern as a side project "so we have a solution to give to all those pesky LabVIEW users demanding support for our hardware". And sometimes that person knows enough to be dangerous but not enough to know that they are dangerous.
We would need the DLL, its header file and the VIs under scrutiny to say anything more.
It seems they forgot to tell you that they try to open a file at C:\Temp\MiST_LabVIEW_output.txt and simply try to use that without checking if it was successful. The C runtime can't create files in non-existing directories so returns an error and the next log entry simply crashes. Of course the quick and dirty solution they may try to come up with for this would be to create the C:\Temp directory first, but that's not a proper solution. On restricted user accounts you can't create anything in the volume root.
If you create that folder yourself by hand, you can run the discoveryInit function successfully. No guarantee for anything else in that DLL. It looks complex, specifically created for LabVIEW and might present you many more surprises.
Also, why they go through the trouble of creating a DLL to create a LabVIEW specific DLL (some functions use LabVIEW manager function to deal with LabVIEW native datatypes and also have LabVIEW in their name) is difficult to understand. It uses TCP/IP and possibly RS-232 to communicate with the device and I would bet that creating a LabVIEW native instrument driver using VISA functions would have been most likely less work in the longer term than trying to shoehorn an existing driver written in C(++) to be used from LabVIEW.
If they document the command set properly, it may still be the better solution to rewrite that driver from scratch in LabVIEW.
Try to attach the file C:\Temp\MiST_LabVIEW_output.txt.
And would you mind attaching your VI in an older version? Preferably 2020 or earlier! You can use Safe for Previous from the file menu.
As to their answer about Max not being able to connect to their device, that's a pretty lame explanation. However it is correct that without a Programmer Reference Manual for the device, you are pretty much lost. There is no simple way to "guesstimate" which port you need to open, nor what you would need to send to the device that it even would start to answer anything.
