Good question Johan. We currently don't have support for this unless you're acquiring in Listener mode. This is a feature we will look into for future releases. A workaround would be to use product select to close the inspection and load a new one that doesn't have any acquisition. Then you could load a simple one that has 1 acquisition step and and you keep switching back and forth between the simple acquisition inspection an the empty inspection using product select until the simple acquisition inspection doesn't fail on image acquisition. Then you know you can load your real inspection and the acquisition will be good again....not very elegant, but a brute force way to get something working for now.
Sorry I forgot about that dialog. You could just have a simple Run LV step that checks if your camera is available. All you would need is this one "Reset" inspection that keeps calling a Run LabVIEW step until the camera of interest is back online. The Run LV VI would just try opening a session and then close it and report if the driver could open a session (maybe enumerating would be faster, but I'm not sure). Once the driver successfully detects your camera again, then product select can reload your real inspection.
Everything has a solution, the problem is that it always involves Labview in some way. This run labview vi works (enumerate camera) but we are not going to have Labview installed on the machine that is supposed to run the Vision Application. So please provide us with a custom step for distribution as we are not able create our own.
You need to build your VI into an LLB with all dependencies (including vi.lib). The info in the FAQ of the Run LV step describes how to package your VI for distribution. Once you follow those instructions, everything the VI needs will be in the LLB and you can move it to systems without LV and VBAI will be able to run it without problems. Feel free to send me your LLB if you continue to have problems and I'll see why it's not working.
