Data Logging Issues with VBAI

[EP_LM3]

I'm having issues with the "Result Name" header that gets recorded into my log file. 

It seems that some steps will report the expected header, such as "Step Status" or "Match [1].Score" and other report "1" or "0".

Does anyone know what causes this?

Thanks

[RichieTheBard]

What log file specifically are you referring to in here, and what is generating it. It is difficult to talk about the specifics without better understanding what we are looking at in here.

[EP_LM3]

A "Data Logging" step set up to log to the Local D:\ drive. From the additional tools section of Vision builder AI, The log gets created then appended to with every cycle. 

An outside Labview program triggers each cycle. Does that help? I've attached images related to the step as well. VBAI creates the proper log file and adds rows as expected. It just seems to be the "Result Name" header that gets a value of 0,1,or whats expected. ex: Match [1].Score. 

[tr_dane]

Result Name is depending on your Measurement Log that you ticked. Data Match [1].Score available on "Match Pattern" step. Do you expect other steps is going to have the same result ?

[Brad]

Can you include a sample inspection and images to reproduce this so we can investigate what is happening?

Thanks,

Brad

[EP_LM3]

For this instance, logging is set to log all parts of every step. I do not expect a "Pattern Match" step to have the same result header as a "Color Match" Step , however I do expect two "Pattern Match" steps to have the same headers. The attached snip is from the prior attached log. "C2" and "C2 missing" are both pattern match steps, log all of their respective data but have different headers.

[Brad]

Thanks for the tip. I was able to reproduce the issue using two pattern matching steps. If I create the Data Logging step when no matches are found in one of the steps and I choose to log results for the matches (even though matches are available for one of the steps), when you OK the data logging step, the Pattern Matching result names aren't saved since there is no match results available. If you edit the step when the match is found, then it will save the result names and you won't have this problem. I will see if there is a way to get the result name even though the result isn't available, but at least there is a work around for now.

Hope this helps,

Brad