unable to connect to fieldpoint popup message

[chadj]

Hello,

I'm receiving a popup error message which says, "unable to connect to fieldpoint". This error message is extremely infrequent but when the popup appears the program stops updating. I'm trying to run this as a DAQ so this behavior is not acceptable. Is there some way to disable all popup error messages so that if an intermittent error occurs the program will continue running?

Thanks in advance,

Chad Johnson

[nathand]

Do you have Automatic Error Handling enabled in the VI properties, under Execution?  If so, turn it off.  You'll need to do this in the VI in which the error occurs, not necessarily at the top-level VI (but within your VIs, not in a Fieldpoint VI that NI provides).  Another approach would be to do proper error handling in the code, so that you don't have unwired error clusters where errors might occur.

[chadj]

Thanks for the quick reply! I have disabled automatic error handling in all VIs and all error outputs are wired to error displays. I've also used the simple error handler and set the dialog box option to "disable dialog box". Any other thoughts? It's a large program so it's possible I've made a mistake somehwere, is there a way to see which subVI or function is generating the popup? I'm using version Labview 8.6, by the way.

Chad

[nathand]

I'd search for all instances of the Simple Error Handler and make sure that there isn't one where you don't have the "No Dialog" option set.  Also, setting the No Dialog option means the error passes straight through, so if you do have a VI with automatic error handling enabled you could still get a dialog, I think (I haven't tested this).  What is the exact text in the error dialog?  You could search for all instances of the Fieldpoint functions and see what you're doing with the error outputs.  Many error functions provide the full call chain as part of the error text.

[alcava.cr]

Chad, what is the hardware that you are using? This messages pops when using a LabVIEW project or just a VI? I can only assume that you have installed a driver called NI-FieldPoint and its creating a conflict with your target  device. In this case I would recommend to uninstall this component from your PC

[chadj]

Thanks everyone! I found the problem, just an overlooked instance of a fieldpoint where the error output was not correctly wired.

Chad