LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

error while deploying to FPGA target

Hello everyone,

 

i'm using crio 9049 as deported chassis. My Labview version is SP1 17 I 'm also using DCAF in my project.

I'm having this errors while deploying my code.

 

eeee.PNG

 

 

any idea what can be the problem?

 

Thanks in advance.

0 Kudos
Message 1 of 9
(1,028 Views)

Hi CV,

 


@CV_ND wrote:

any idea what can be the problem? 


Using dialogs on a cRIO might be a problem…

 

Which errors are shown for those subVIs marked with a red cross in the error dialog?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 9
(1,024 Views)

Hi GerdW,

 

Thanks for your answer,

I was developing this project a 2 year ago and I didn't have this problem. Now I want to continue developing this project and I'm struggling with this error. 


It says the target is not compatible, but I have used the same versions and same modules before and that worked perfectly.

 

regards,

CV

0 Kudos
Message 3 of 9
(995 Views)

Hi CV,

 


@CV_ND wrote:

It says the target is not compatible, but I have used the same versions and same modules before and that worked perfectly.


Can you show the specific error message in the error dialog?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 9
(992 Views)

Hello GerdW,

 

Thanks for your answer,

There is no error dialog since I can't compile my code (I have a broken arrow) 

 

regards,

0 Kudos
Message 5 of 9
(965 Views)

What Gerd means is to move the selection to one of the VIs that has actually a red cross in front. This will show a hopefully more useful message as to why this VI is not executable.

 

It seems to be in two cases a dialog VI. and certain dialog functions on your real time target are not supported. So it my by actually that your project is not correctly setup to contain the right platform conditional symbols to control the Conditional Compile structure in this VIs correctly which should disable those unsupported functions for your target.

 

But without seeing the entire project and all the VIs ourself we just have to guess into the blue about this, especially since the selection you show is about a VI that is itself not broken because of an error in itself but because of subVIs that are broken. Without knowing why these VIs are broken we can keep guessing into the blue, but won't easily get at any real conclusion.

 

Proper debugging really is as simple as selecting one for one the VIs in that error dialog with a red cross in front and open them and investigate the reason for them to be broken. The two Display VIs most likely have some dialog function enabled that they should not for the RT platform, and the Service VI is most likely broken because of a similar error or something with trying to call these display VIs.

Rolf Kalbermatter
My Blog
Message 6 of 9
(960 Views)

Hello,

 

Thanks for your reply.

 

here is more details about the error.   

 

prb3.PNG

prb1.PNG

 

 

prb2.PNG

 

 

as I said previously, we was not having this issue before with the same code and same target.

 

CV

0 Kudos
Message 7 of 9
(915 Views)

Hi CV,

 


@CV_ND wrote:

here is more details about the error.


Right now the error is as suggested before: some functions aren't supported on the target system. Most likely some of those dialogs…

And you cannot load a bitfile when the FPGA VI isn't compiled properly…

 


@CV_ND wrote:

as I said previously, we was not having this issue before with the same code and same target.


Something has been changed in between…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 8 of 9
(906 Views)

Hi GerdW,

 

Thanks for your reply,

I'm trying to understand why I am not able to compile the FPGA VI now, but I was able to do that a time before.

is this error related to a specific driver? or a specific FPGA module?

 

 

 

regards, 

 

CV

 

0 Kudos
Message 9 of 9
(886 Views)