04-23-2015 03:34 PM
Thanks anyway. I'm using LV2014 so after AQ's post above I'm not so worried anymore.
04-23-2015 03:36 PM
Thanks for sharing your experience. This is really worrying me because our source code has a wide use of both accessor VIs and property nodes since it was coded by different developers with various preferences. I will experiment if a difference could be made by replacing all property nodes.
04-23-2015 03:54 PM
Yangyang Cheng wrote:
there a way that I can get more meaningful information from this error 1097? If all it means is an exception was thrown from a black box DLL, it hardly helps me.
In LabVIEW 2014, yes, there's a way to get more information. But not in 2011.
In 2014 (and later), if you get this error, LV will also include information in its log file. Go to your temp directory, located here on Windows:
C:\Users\<username>\AppData\Local\Temp
And find files named something like this:
LabVIEW_64_14.0_<username>_cur.txt
LabVIEW_64_14.0_<username>_log.txt
The 64/32 is the bitness of LabVIEW, followed by the version number. The "cur" file is the most recent run of LabVEW. The "log" file is the previous run.
In that text file, you'll find text like one of the following. The hex numbers are IDs so we know which message was generated by which condition even if the error text is reformatted or new info is added in future revisions. CLN means "Call Library Node."
04-23-2015 03:56 PM
ian.yeager wrote:
However, since giving them up all together, I’ve never felt like I’m missing them, and I’m still using LVOOP on a daily basis.
I don't use them either in my code. They don't fit a lot of situations that I want to be able to code (I leave out error terminals on the vast majority of my accessors), but I do understand why people like the syntax.
04-24-2015 02:37 PM
Thanks for your contribution to this post. I just want to give everyone an update that we narrowed it down to computer OS/driver problems.
04-24-2015 03:15 PM
I am glad you are making progress. I hope it works out.