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.
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.
05-06-2009 03:38 PM
I am currently trying to generate a waveform on an FPGA using a program to initialize a Look-up Table (LUT). When I select Call Initialization VI, then select the path and hit OK, Labview begins to consume a bunch of CPU time but nothing seems to happen - none of the buttons function except the Open File dialog box and the close icon (red box with an x in the upper right hand corner) is greyed out. Does anyone have any thoughts? Maybe I am doing something wrong, but there is a dearth of documentation on this function. I have attached the VI that I am using to try to initialize my table.
Any thoughts would be great.
Cheers, Matt
Solved! Go to Solution.
05-07-2009 06:25 PM
Take a look at this Tutorial: Waveform Generation with CompactRIO
and this example: Continuous Waveform Generation with a Look-Up Table on CompactRIO
05-08-2009 10:19 AM
Thanks for the reply, Huter. I have already gone over this tutorial and I believe that I am following all the steps that are given in the example for generating the LUT. I am outputting 40960 (the size of the largest memory block for the PXI-7841R) I16 elements (ranging from -32768 to 32767) into an array called Init Data Out (I have been unable to find documentation on this but both of the examples that I have been able to find indicate this is the name of the array from which the LUT will be populated). I am given no indication that anything is wrong when I try to load the table, the controls just become unresponsive. Can anyone tell me if I am doing something incorrectly?
The fact that the control becomes unresponsive without throwing an error also suggests that the functionality is not behaving as desired and should be corrected in future releases. But, first I need to know what is happening.
05-12-2009 02:10 PM
05-18-2009 12:08 PM
Thanks, Hunter. Some point soon, I will be getting directly in touch with the FPGA folks at NI. I will let you know what I find out.
Cheers, m
05-20-2009 06:39 PM
m;
While I was able to reproduce this hang with your code, I do not see the problem if I recreate the same code. It might be that this particular VI is corrupted. Do you see the pop up hang from any other VI's?
Let me know.
05-21-2009 10:24 AM
Hunter,
I haven't tried it with any other VIs run over that large of a set of numbers. I will give that a go. What do you mean by "corrupted"? How did you recreate the same code? I have used this VI previously to produce a signal on an AO 6733 and it worked just fine.
Thanks, Matt
05-22-2009 05:03 PM
If I open the Configure Loop-Up Table 1D window and select define table»call Initialization VI and open one for the example LUT maker VI's it works fine for me. If we can get that one to work then we should be change it into your current VI piece by piece so we can find what about your VI might be causing this problem.
In any case I will file a CAR, because even with a "bad" initialization VI we would never expect the non responsive buttons.
06-01-2009 11:34 AM
This must have something to do with the complexity of the LUT initialization VI. As a work around, I have simply written the data to a file which I then read for the LUT initialization. I have attached the new VIs.
The lack of responsiveness is a problem as well as the lack of any indication of an error.
06-04-2009 01:58 PM
I filed a CAR (corrective Action Report) for this issue with LV R&D. This bug is only a problem with certain kinds of programiticly called VI's In your case the inverse FFT wich has a call library function node in it and casues the LUT Initilization dialog to hang. Another user came accross this bug when using mathscrip in the Initilization VI. You can use the CAR number below to track this issue to see when it will be fixed in futire version
This was reported to R&D (# 171812) for further investigation