extracting results from converted VBAI inspection

[reivaxseniab]

Hi everyone,

I have recently converted a VBAI inspection and migrated it to LabView. The Labview file is attached, and from this , I would to extrapollate the results I get, and put them under excel (any type of spreadsheet really).

I'm not to sure where to extrapollate the results from, but i seemed to think it was on the top left loop, on the third sector label. Everything works fine in my VI, but when I put the path to which I would like the results to be sent to, and I already created a text file in a folder, so I was selecting this text file as my new spreadsheet for these results, but nothing happens, the spreadsheet stays white.

Maybe I havent understood how to use the "write to spreadsheet" or how to actually save data, but if any one could help me, it would be greatly appreciated.

Best regards

[joaopam]

Hello friend.

First of all, I must warn you to be careful with the abuse of stacked sequence structures. Most of the time, you can achieve the same results only by using Data Flow.

Second, have you tried to probe the wire that carries the data you want to write?
Also, take a look at the spreadsheet examples in the Example Finder. This must help you.

Unfortunately I'm not able to test your VI properly since most of all subVIs could not be loaded, due to a lack of .llb file.

Regards

[reivaxseniab]

Dear Mondoni,

I shall try all these, and thanks for your quick reply :).

will probably get back to you haha.

Best regards

[Brad]

You can also use the Data Logging step in VBAI to save results from the inspection to file. If you migrate to LabVIEW, this same step will still save results to an excel spreadsheet (csv format). You could also use the API to launch a VBAI engine, run the inspection and get results (see the LabVIEW examples for this under <Vision Builder AI>/examples/API Examples/LabVIEW.

There are several advantages to using the API over migrating the inspection to LV, so it's worth considering.

Hope this helps,

Brad

[reivaxseniab]

Brad,

Thanks for the advice, I will also have a look. Thanks

Best regards

[reivaxseniab]

Although actually ideally, I would rather have everything under Labview, because the image processing... is within VBAI, but I'm using a thermal camera that is currently working with LabView but not with the VBAI inspections. This is why I prefered migrating it to LabView in order to keep everything together.

[Brad]

I'm surprised to hear the camera doesn't work with Vision Builder AI. Does it return 16-bit images that work with many of the steps (you can cast the image using a Vision Assistant step in VBAI to handle this issue)? Does it fail to acquire? If it fails to acquire, what bus are you using (CameraLink, 1394, GigE, etc.)? If you could acquire in VBAI, would you still need to migrate to LabVIEW?

Thanks,

Brad

[reivaxseniab]

The camera is a special thermal camera that was bought through a company that developped a few drivers along with it. unfortunately, I don t have the SDK, therefore     I am not sure how the drivers were written. They have developped drivers only for labview,and I can therefore not acquire the camera neither on VBAI nor on VAS. 

I would therefore like to say that if I could acquire in VBAI, no I probably wouldn't have to igrate, but I really can't unfortunately. The only way I have figured out how to use the camera, is throgh MAX, configurating it as a Visa resource and then acquiring it in the Visa resource name and then using the drivers such as "initialize"...

Sorry if that's not so clear, it's a bit hard to exlain.

Thanks very much