Error: Details Display Dialog.vi and Not Found Dialog.vi

[Calvin_Q]

Hi everyone,

I'm trying to deploy my code to the PXI controller. However, I ran into the following two errors.

Then I tried the methods mentioned in this post:

https://forums.ni.com/t5/LabVIEW/cRIO-build-error/td-p/3192704?profile.language=en,

but they didn't work.

Wondering how to solve these two errors. Can anyone shed some light on them? Thank you so much!

[Bob_Schor]

I suggest that you attach (all of) the code that you tried to deploy to the PXI controller.  It might be helpful to have some idea of what you are trying to accomplish with this code.

Bob Schor

[GerdW]

Hi Calvin,

---

@Calvin_Q wrote:

Then I tried the methods mentioned in this post:

https://forums.ni.com/t5/LabVIEW/cRIO-build-error/td-p/3192704?profile.language=en,

but they didn't work.

Wondering how to solve these two errors. Can anyone shed some light on them?

---

You are using functions/VIs not supported on your target - exactly as the error messages say.

Did you try the suggestion given in message #2 of the linked thread?

I repeat that suggestion: don't use those functions in your target!

[billko]

If I'm not mistaken, PXI doesn't allow for front panel interaction.

[Bob_Schor]

---

@billko wrote:

If I'm not mistaken, PXI doesn't allow for front panel interaction.

---

Not entirely -- NI charges (or, rather, at one time charged) extra to put the Real-Time OS on the PXI Controller's drive instead of Microsoft Windows!  Given how expensive a PXI controller can be (compared to a generic PC running Windows), why you'd pay a premium for a Windows-based "DAQ Box" (as opposed to putting a few NI DAQ cards in your PC) and sacrifice the RT-backplane and capabilities of the PXI box just speaks to the wonderful Sales Talk that clouds the minds of the gullible customers (I encountered at least one colleague who spent >$10K for a PXI setup that I don't think is yet working after 3-4 years, with a Windows OS on the Controller ...)

Bob Schor

[pcortes2]

Hi @Calvin_Q.

The image shows that the Details Display Dialog.vi and Not Found Dialog.vi have problems. Both LabVIEW functions are not supported on real-time targets. The caller of these functions is the General Error Handler.vi and the Simple Error Handler.vi.

Try to find these functions in your code and use the Unbundle By Name LabVIEW function to get the boolean, code (integer), or the string error (source), since you don't want to get any dialog in a real-time target (PXI, cRIO, myRIO, etc.).

I hope this helps.