VBAI2010 on CVS1454 possible bugs

[Rockhead]

I am running VBAI2010 on a CVS1454. I have noticed 2 items that may be bugs with the new version of VBAI. These problems have been duplicated on 2 seperate CVS units.

#1. The CVS time cannot be set from Target-Options. I am able to set the time zone. I can also set the clock to the host computer time but the "set time" button does not update the CVS clock. When these CVS units were targeted with VBAI2009 setting the time was not a problem.

#2. I am seeing different results using the Read/Write I/O (NI-IMAQ I/O) VI. Using the detect rising edge option on an ISO input in VBAI2010 does not function at all. The inspection state will reach this I/O step and stop (no pass or fail) even though the ISO input is transitioning from off to on. This is transitioning is confirmed by observing the NI-IMAQ I/O Test Panel and Monitor screen. This same setup in VBAI2009 works as expected. The rising edge causes the inspection step to complete and the inspection state moves on to the next inspection step.

I will attach my test program for #2 when I get to work tomorrow.

[Rockhead]

Attached are the test programs that demonstrate the difference in the way VBAI responds to a rising edge ISO input. The 2009 version works correctly. The 2010 version does not leave the 1st inspection state because it does not respond to the rising edge input. Both programs tested on the same CVS using the appropriate VBAI version.

I really like some of the improvements in VBAI2010 (especially the custom UI editor) but cannot use this version if the Read/Write I/O step does not work as in previous versions. I don't want to change the way I trigger my inspection to work around this issue. Getting the correct time set is also critical for our inspection and I can't do that right now in VBAI2010 on a CVS.

[Brad]

Thanks for reporting these issues. I confirmed issues #1 and made a simple Run LabVIEW VI to set the timestamp. Unzip the attached Set Time Stamp.zip and put the VI and the data folder on the CVS under c:\User VIs. Call the VI from a Run LabVIEW VI step to update the targets time. We will work on fixing this for an upcoming SP1. You only need to call the Run LV step once, so delete the step after you set the time and CVS will be updated.

I also confirmed issue #2. I will look into a way to fix this and get back to you.

Thanks,

Brad 

[Brad]

So it looks like there's an offset issue with the change detection code for the ISO Input lines. For example, if you specify ISO IN 8 as the line to look for changes, it is actually looking for the change on ISO In 10. Because ISO In 8, 9, and 10 are the only ISO lines that support change detection, this means you will only be able to use 1 line (configure ISO 8, but actually use ISO In 10). Let me know if this prevents you from using Vision Builder AI 2010 for your application.

Thanks,

Brad

[Rockhead]

Brad,

Thanks for the quick response. Unfortunately I will have to wait to use VBAI 2010 until the input offset issue is resolved. We use input 9 & 10 for other functions and I will not be able to rewire the inputs to use this workaround. VBAI 2009 is working well for us currently so I will stick with that. I will continue to use 2010 on my test and prototype system so that I can get familiar with the new features.

Mark

[Brad · Accepted solution]

Hey Mark,

Here is a recompiled llb for the CVS which fixes the problem. Put this file on the CVS under c:\vbai\plugins\ and reboot the CVS and this will fix the problem with the change detection on the ISO lines.

Hope this helps,

Brad

[Rockhead]

Brad,

The new llb fixed the change detection on the ISO line. My test program runs as expected. Thanks again.

I tried the set time VI. I followed your instructions and put the VI and data folder in the user VI folder on my CVS. It seems to partially work. The time is reset to 12AM not the current time.

Mark

[Brad]

Glad to hear the ISO Change Detection works now. When you call the VI in a Run LabVIEW step, you have to go to the VI Controls tab, click on the Configure button and set the VI controls so the year/month/day/hour/minute/second controls have the correct value before you run the VI.

Hope that helps,

Brad

[Rockhead]

Brad,

That's all it was. Got the time set correctly now.

Thanks for all the assistance.

Mark

[Brad]

Here's the updated llb for Windows for anyone using Vision Builder AI 2010 and an 8254/8255 and want Edge Detection to work for the ISO Inputs.

Vision Builder AI 2011 already has this fix, but this is for users that don't want to upgrade to get it. Put this LLB in your Vision Builder AI 2010/Plugins folder (you can rename your existing file to have a .bak extension if you don't want to lose the original llb).

Hope this helps,

Brad