Will the "error cluster from error code.vi" found on the RT "Dialog & User Interface" palette work as intended in an RT app?

[WNM]

The "error cluster from error code.vi" is available for inclusion in an RT application but it contains a "FP.Title" VI property node and an RT application does not contain any front panels, except when run in a debug mode. Will this vi.lib VI work properly in an RT app running on a cRIO?

[Aix-La-Chapelle]

Hi WNM,

You are correct that the "FP.Title" VI property node would not work with an RT applications, thus it does not look like this particular VI will work correctly on RT systems.  It is likely that most of the VIs in the "Dialog & User Interface" palette will not work, as they are intended for use with a front panel, thus user interface.  Thanks!

[CMal · Accepted solution]

The Error Cluster From Error Code VI does work propertly on RT targets, but the behavior will be slightly different when the calling VI has a front panel title that is different from its qualified name.  Notice that there is a Select function that checks for an error coming out of the FP.Title property node.  If there is no front panel title, then it will simply use the VI's name instead, so this VI definitely does work on RT.

Keep in mind that the act of opening a VI reference and reading a property is relatively time consuming, so there is a significant performance impact when calling this VI on RT.  This performance concern has been reported to R&D in CAR 384767, but it can usually be avoided by making sure to only call this VI when there is an error that needs to be reported to the user.

Chris M

[WNM]

---

@CMal wrote:

Keep in mind that the act of opening a VI reference and reading a property is relatively time consuming, so there is a significant performance impact when calling this VI on RT.  This performance concern has been reported to R&D in CAR 384767, but it can usually be avoided by making sure to only call this VI when there is an error that needs to be reported to the user.

Chris M

---

That's good to know, thanks for pointing it out. As I am only using the VI in the default state of state-machine VIs to report the unexpected execution of the default state, then I should be safe from the performance hit except in cases of a coding error and by then things have run off the rails anyway.

[Jeff-P]

CAR 384767 discussed in this thread has been fixed in LabVIEW 2013. For a more complete list of bugs fixed in LabVIEW 2013, check the LabVIEW 2013 Bug Fixes. You can download an evaluation copy of LabVIEW 2013 at https://www.ni.com/en/support/downloads/software-products/download.labview.html or if you have an earlier version of LabVIEW installed and an active SSP subscription, you will be able to download the latest version of LabVIEW through NI Update Service.

Jeff Peacock

Product Support Engineer | LabVIEW R&D | National Instruments