Function not supported on current target error

[dbrother]

Hello, I am working on a project using the sample "LabVIEW FPGA Control on CompactRIO". When I open up the RT Main VI, for some reason I get a lot of errors. One of them is that the subVI "Details Display Dialog.vi" has the error, "Get Help Window Status: Function not supported for current target". Similarly, another subVI "Not Found Dialog.vi" has the error, "Control Online Help: Function not supported for current target". So, it seems my RT CompactRIO Target cannot use this function, but I don't think this error should be happening at all in a sample project meant for a CompactRIO system. Can anyone help me get to the bottom of this?

Possibly related is that "General Error Handler Core CORE.vi" is what calls both these two VIs, and if you keep following the hierarchy up, it leads to "ABAPI Dist Create Directory Recursive.vi", which also has an error, "Recursive reference in non-reentrant VI".

[GerdW]

Hi dbrother,

---

@dbrother wrote:

When I open up the RT Main VI, for some reason I get a lot of errors. One of them is that the subVI "Details Display Dialog.vi" has the error, "Get Help Window Status: Function not supported for current target".

---

Which RT target do you use?

Are you really opening an RTMain example VI? Or do you try to open a WindowsPC target VI on your RT target?

As in your other thread: attach the whole project as ZIP…

[dbrother]

Hi GerdW,

I'm sorry, I'm not exactly sure what you mean by your questions (I'm a little new to programming with LabView). I believe my target is an FPGA, which is on a cRIO-9054. I suppose I am not opening the original RT Main VI, but a copy of it. In the project explorer, it is listed under RT CompactRIO Target, and not My Computer.

As in my other thread, I am attaching my project as a zip here too.

[GerdW]

Hi dbrother,

---

@dbrother wrote:

I'm sorry, I'm not exactly sure what you mean by your questions (I'm a little new to programming with LabView). I believe my target is an FPGA, which is on a cRIO-9054. I suppose I am not opening the original RT Main VI, but a copy of it. In the project explorer, it is listed under RT CompactRIO Target, and not My Computer.

---

In the project (I took the one from your other thread) the target is listed as cRIO-9074.

And usually the RT targets don't support any functions, which require an UI - as they run (mostly) headless!

[dbrother]

Hi GerdW,

That is really interesting! Because I'm pretty sure I have a 9054. I see this in NI MAX under Remote Systems. Could this be the cause of these problems? (or perhaps that of my other thread). How do I make sure that the project is using the actual target I want?

[Bob_Schor]

So you attached code targetted for a cRIO-9074, but the hardware that is attached to the PC on which you are developing the code is a cRIO-9054.  And you are getting an error message saying a function is not supported by the current (9054) target!

When you program in the LabVIEW-RealTime environment, you, sooner or later, will want to deploy your code to your (in your case, a cRIO).  To do this, the Target must be attached (usually through TCP/IP).

Bob Schor

[dbrother]

Hi Bob,

Thanks for your reply. I added the cRIO-9054 as a new Target, moved all the files and folders that was previously listed in the old target to this new one. I'm still getting the errors though.

In fact, I found on these two articles (x)(x) that these functions cannot run on RT targets anyway. I don't want to say that this is a mistake in the sample project, but I have no idea how to rationalize that, even though it was the wrong target for me, the sample project still intended to run VIs on a target that can't use these functions.

[cbutcher · Accepted solution]

Hi,

When I loaded your project in my 2019 SP1 installation, I got a warning about a changed path for one of the VIs.

I believe this was related to the Error Code handling (I didn't know it was going to be important at the time, so I didn't make a note or read very closely).

It relinked to the vi.lib version, but the other path mentioned an NI System Manager directory or similar. It may be that this other version would have not used these subVIs?

For reference with moving code (and you might have already seen this), you could take a look at Moving Examples to a Different FPGA Target which discusses some of the key points when moving example code.

It's worth noting that the operation they describe is in some cases not just drag and drop (although it looks like sometimes, that should be fine).

In your case, your example came from a 9074 (VxWorks OS) and you're using a 9054 (Linux-RT OS) so I could believe it might be a little trickier... (see Real-Time Controllers and Real-Time Operating System Compatibility for a source)

[dbrother]

Hi cbutcher,

I followed the steps in your first link to duplicate the project template and moving the files to my own target. I have to remake my control algorithm on the FPGA VI, but it does not take long. This seems to have fixed the issue. Thank you very much for your help. Thank you GerdW and Bob as well for pointing out that I had to wrong target in the first place.