LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Open FPGA Vi Reference strange behaviour

Hi
 
 
On LvRT when I put an open FPGA Vi Reference and select open bitfile everything goes well.
 
But If I select open vi then there is a problem. The arrow is not broken and everything seems to work. if I check the Fpga Vi reference Out wire the enum is weird. see above the beginning of the enum:
 
.....
HW Exec Ref
{HW Refnum, <00><00><00>FPGA.vi<00><00><00>.........}
.........
 
When I run my program, the fpga doesn't start.
 
So I can work by selected Open Bitfile but Does anyone no why there is this problem?
 
 
thanks
 
James
 
0 Kudos
Message 1 of 13
(9,217 Views)
Message 2 of 13
(9,135 Views)

Hello,

I apologize for asking a question that has nothing to do with FPGA, but I have a question for you julesjay : I have seen that you asked a question a long time ago : how to convert an XY Graph into a Waveform ? So I guess you did it ! Would you mind showing me your VI ? Because that's exactly what I need to do !   😉

Thank you very much in advance !

Julien

0 Kudos
Message 3 of 13
(8,973 Views)

That's OK I did it !

Best,

J.

0 Kudos
Message 4 of 13
(8,954 Views)
Hi,

I wonder if you ever solved this problem, because I am currently having the same problem.  The linked article suggested that it was a problem in switching from FPGA 1.x to 8.2, but I haven't done that lately.

My trouble started when I made a new project and tried to reuse some of the same subvi's.  I have exactly the same chain of Open FPGA Reference->subvi as in a working program, (I copy/pasted) but in the new project this gives me the same mismatch error you got.

I have a workaround, too: I could just put the new stuff I am doing in a folder in the old project, but I'd rather not, since, except for using some of the same code, it's not really related.  Plus now I want to know what subtlety I'm missing!

I'll continue to poke at it, but if anyone has some insight it would be much appreciated!

-Allison
0 Kudos
Message 5 of 13
(7,691 Views)
Hello,
I do not really understand what your problem is. References to the VI are lost? This phenomena can happened if you copy/paste property nodes or invoke nodes. Is the same behaviour with a ctrl+ mouse click to paste a new object? If you manually select the VI does it works?
Regards.

Message Edité par ManuelR le 08-20-2007 07:06 AM

Manuel R
AE dans une autre vie
0 Kudos
Message 6 of 13
(7,515 Views)
I have a top-level vi which opens an FPGA reference, then passes the reference to a series of sub-vi's.  It works fine.

I made a new project and loaded it up with the same FPGA vi and the relevant host vi's.  Then I made another top-level vi in that project to open the same FPGA vi reference and pass that reference to the same first sub-vi.  This resulted in a broken wire between the "Open FPGA Reference" and the first subvi.  The desired FPGA vi is selected in the "Open Reference" node.  The error I get is this:

"You have connected clusters with different elements.  Cluster FPGA VI Reference out->HW Exec Ref->(Unnamed), a unsigned word [16-bit integer (0 to 65535)] enum{HW Refnum, <00><00><00>FPGA Top Level.vi<00><00><00>FPGA Target<00><00><00><00>PTH0<00><0"

I get the same behavior whether I copy/paste from the functional vi or just put the nodes in by hand from the functions palette.  My VI's are pretty complicated- they call subvi's and use FIFOs and memory objects.  I am fiddling with reproducing the problem with simpler VI's.  The simplest possible combination of one top-level, one sub, and one FPGA vi did not reproduce the problem, so it must be something a little more subtle.

I hope that is a bit more clear.  Thanks for responding!
0 Kudos
Message 7 of 13
(7,494 Views)
Is there a work around for this problem?  I'm getting fed up fixing my subvis everytime I want to try a different bitfile!!!!!
0 Kudos
Message 8 of 13
(6,125 Views)

bscout,

I think what your looking for is to bind to typedef using the FPGA Open Reference VI.  If you use the control created in all of your subVIs it will propagate through when ever you use a different bitfile. 

I believe it should be docuemented in the LabVIEW FPGA help if you need more information.

Bassett

Message Edited by Bassett Hound on 09-19-2007 03:06 PM

0 Kudos
Message 9 of 13
(6,120 Views)
Thanks for the quick reply.  I right clicked on my vi reference as you have shown in the jpg and select bind to Typdef...  A dialog come up asking for a file name.  I type a name and hit save, but when I go to the folder where it saved nothing is there??  What gives?
 
0 Kudos
Message 10 of 13
(6,115 Views)