Does LabVIEW_Eval_7.0_xxx_cur.txt tell me about an internal error caused by call library function?

[Marilie Randewijk]

I am having trouble using a third party's dll and found the file LabVIEW_Eval_7.0_myusername_cur.txt in my Local Settings\Temp directory.

File contents:
####
#Date: 01 Dec 2004 11:31:16
#OSName: Windows NT
#OSVers: 5.0
#AppName: LabVIEW_Eval
#Version: 7.0
#AppKind: FDS


Is there any info about the internal error stored in above mentioned file?

The LabVIEW_Failure_Log.txt file was not updated after the crash...

I downloaded Eval_7.0 from the web, but still have LVIEW 6.1 installed. I am trying to rewrite the 7.0 VI in 6.1. Cannot add an event to an Event structure in 6.1 - but can do in 7.0?

Should I re-install LVIEW 6.1?

Kind regards,
Marilie

[chrisger]

hi

well, i think with a quite high probability there's something wrong with the parameters or settings of the CallLibrary Node. because the app crashes inside the dll LV has no chance to log anything at all. please post some code or screenshot, so we can see. what function do you call?

best regards
chris

[Marilie Randewijk]

Hi Chris. Thanks, it helps to know why the error log is not updated.

I include the VI with the library call function for your info. Will check the settings again.

Regards,
Marilie

[chrisger]

hi

well, concentrate your search on the arrays, especially the size and datatype. that's my favorite mistake!

just a little hint: remove the wait function and connect the 500 ms constant with the event structure (the event structure will do the waiting for you)

good look
chris

[Marilie Randewijk]

I was wondering wether the 500ms wait could rather be wired to the event structure! I recon'ed wiring the wait to the event structure would keep the VI focused on waiting for front panel activity - which I do not neccesarily want, rather than releasing most of the processor power -idling - so that the USB and other stuff have priority.... I will change that, thank you.