LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application error

I believe one of the NI digital input/output VIs is causing an "Application error" on my Windows NT system running LabView 6i. It seems this occurs when the size of the array to be output is zero (empty array) and so probably occurs inside "DIO Config.vi"or "DIO Write.i". I'm frustrated because this problem has taken me a while to solve. I have to re-boot each time I get the error, which takes several minutes. OK, perhaps it's not usual to ask for zero samples out, but I expected these VIs to check for such an event and deal with it appropriately. At the very least, I would have hoped for a meaningful message in preference to an application crash.

I now have a work-around for this particular problem, but...

My questions: Is my diagnosis right? Are
there other VIs which I should view with suspicion? (Any other VIs that I cannot expect to cope with all parameters I can sling at them?). Why not offer greater 'error' checking (and reporting) - at least for the application development stage?

Richard .
0 Kudos
Message 1 of 5
(3,000 Views)
Richard

Are you using the error checking in LabVIEW by connecting the error out and error in connections of the DIO vi's? DIO Start should generate a 10010 error when trying to output an empty array. If you click on the lightbulb on the block diagram window, you can trace through your program to see where is it crashing your program.

If you are using the error checking and are still seeing this error, could you post a small vi that demonstrates this issue. I've tried, though I get a 10010 error and the program just ends.

Brian
0 Kudos
Message 2 of 5
(3,000 Views)
Brian,

Thanks for your comments. I've analysed the problem a little more in my 'spare time'. The problem definitely persists and I've narrowed it further to ‘DIO Write.vi’ using the light-bulb as you suggest and limiting my test to a single simple VI. I do use the error-out to error-in error checking procedure.

I’ve also attached my demo VI to this message. Running this VI without changing causes the problem for me. If I enter a couple of elements into the VI works fine.

It’s may not be relevant, but on booting I get the message “At least one service or driver failed during startup…” (which I haven’t tried to solve) and while starting Labview/loading my VI I get “Cannot fine the file [
…] (or one of its components). Make sure the path and filename are correct and that all required libraries are available” (which means little to me, but doesn’t seem to worry any other stuff I’ve done). It may also help to know I'm driving a PCI DIO 6533 high-speed digital IO card in my PC and have other cards installed too.

Many thanks for any further suggestions or comments you can provide.

Regards, Richard.
0 Kudos
Message 3 of 5
(3,000 Views)
Richard

I am unable to open the vi that you have attached. "Not a valid vi" What version of LabVIEW and what operating system are you using?

Brian
0 Kudos
Message 4 of 5
(3,000 Views)
Brian,

I'm using LabVIEW 6i and Windows NT. I've attached the file again in a slightly different way too. Hopefully this will be OK.

Richard.
0 Kudos
Message 5 of 5
(3,000 Views)