Error 1088 after ActionVIOnLoad

[hrobitaille]

Hi,

With VeriStand 2011, we are using the ActionVIOnLoad with our Custom Device to manage the change between 2 versions of the CD.

Depending of the nivssdf updates, System Explorer displays error messages after the ActionVIOnLoad has been executed.

Error 1088 occurred at Nœud de méthode dans Tree.lvlib:Populate tree itemwise.vi->Tree.lvlib:Process Tree manipulation.vi->Tree.lvlib:Populate empty Parent Item recursively.vi->Tree.lvlib:Add Items to System Framework Tree.vi->System Explorer Framework.lvlib:Communication_UserEvent.vi->System Explorer.lvlib:System Explorer.vi->System Explorer.lvlib:System Explorer Wrapper.vi->System Explorer.lvlib:System Explorer Wrapper.vi.ProxyCaller

We have a message for each "invalid" action but the updates have been correctly executed.

Two example cases :

If we try to add new sections in the Custom Device (Add Custom Device Section), we have this error for each new sections.

If we use the Set Item GUID, we need to set the "Refresh System Explorer Tree" to false to avoid the error.

Is there a way to avoid the error messages ?

Is there "forbidden" update in the ActionVIOnLoad ?

Remark : sometimes we have too the same type of error when we suppress and recreate immediatly the Custom Device.

Regards,

Hubert Robitaille

[StephenB · Accepted solution]

Unfortunately this is a bug in NIVS 2011 and earlier whenever you add channels or sections in an action vi on load. You can look at the source of the scan engine device to see how we worked around it

[hrobitaille]

Thanks for your answer.

Your Custom Devices are always a good starting point to improve our custom devices.

We have used the AIT 429 CD to write our first ActionVIOnLoad. Now with the Scan Engine we are going to improve it : to workaround the error and too to use the version from the XML file.

Regards

Hubert Robitaille

[hrobitaille]

Now, as we are using offline version in the ActionVIOnLoad, we have a configuration llb which includes 2 VIs using the "same" sub-VI from two lvlib : Custom Device API & Custom Device Offline API.

The result of the build is the configuration llb and 2 news directories including the sub-VIs

• Custom Device API
• NI VeriStand - Add Custom Device Section.vi
• Custom Device Offline API
• NI VeriStand - Add Custom Device Section.vi

In the scan engine, I have seen that the project includes a local copy of the offline version with a different name instead of using the VI from the Custom Device Offline API lvlib.

Is there a another solution to avoid the 2 directories creation during the build ?

Regards,

Hubert Robitaille

[StephenB]

Unfortunatley two VIs of the same name cannot both be in an LLB... so we had to make our own VI and name it whatever and use the same block diagram calls