From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

FIFO arbitration set incorrectly after copying. Bug?

I am using LabView 8.0.1 with the FPGA module 8.0.0. I have noticed a problem where I will copy a FIFO in the project explorer (usually by selecting the FIFO and holding control as I drag). The new FIFO appears and seems to inherit the same parameters as the original FIFO, except for the name, as expected. In particular, I need the FIFO to inherent the "never arbitrate" option as all of my FIFOs are used in single-cycle timed loops. The problem happens when I try to place the new FIFO inside a single cycle timed loop, I get a pre-compile arbitration error. It is not clear if it is the original FIFO arbitration that is incorrect or the new one. According to the FIFO properties dialog the arbitration is correct, but the vi won't compile.


My fix is to set the arbitration to something else, click OK, and then set it back to "never arbitrate" for all FIFOs in the vi. Then everything compiles without a hitch. Is this a known bug?

Cheers,
Daniel
0 Kudos
Message 1 of 4
(2,742 Views)

Hello,

Thank you for filing this.  You have indeed found a bug.  We are investigating a solution.  As a workaround you should open the property page of any copied FIFOs and click OK.

Regards,

Joseph D.

Message 2 of 4
(2,728 Views)
Thanks for your reply. This gets me out of trouble.

Slightly off topic, it would be great to have the arbitration error dialog box tell me which component is the problem by using it's LabView name instead of the rather more obscure code that is used someone downstream. Is there an easy way to identify block diagram components from this error message?

Daniel
0 Kudos
Message 3 of 4
(2,725 Views)

Unfortunately there is nothing in FPGA 8.0 that will tell you which component is invalid.  I hope you will find future versions of FPGA more helpful Smiley Wink

Regards,

Joseph D.

0 Kudos
Message 4 of 4
(2,701 Views)