LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

cRIO compiling another code as start-up

Solved!
Go to solution

I did right click (or double clicked) on the DMA FIFO in the project window and then increased the value to the max possible. 

I think there is a better method though. 

0 Kudos
Message 11 of 15
(402 Views)
0 Kudos
Message 12 of 15
(398 Views)

Those methods do different things. When you set the DMA FIFO size in the properties page, it sets the amount of space to be used on the FPGA (and possibly, by extension, the amount of space on the host side). The Configure method determines the amount of space to be allocated to the FIFO on the host side (which usually has much more RAM available) independent of the size of the FIFO on the FPGA.

 

At regular intervals or when the FIFO is a certain amount full (I don't know the details of the mechanism), the contents of the FPGA side of the FIFO are copied into memory on the host, then cleared from the FPGA to leave room for more data. On the host side, when you read elements, that space is then freed to leave space for more data. It is normal to allocate much more space on the host than on the FPGA, and it should even be possible to read more elements on the host than there are total elements allocated for the FIFO since there could be several buffers worth of data in memory on the host at once. So, if the FIFO is filling when transferring data to the host, I recommend increasing the size of the FIFO on the host using the Configure method, and then reading more elements at a time.

Message 13 of 15
(394 Views)

I'll give it a try. 

0 Kudos
Message 14 of 15
(392 Views)

I used a FIFO configure method to increase the depth of the host-side FIFO. 

I also changed the timed while loop to a normal (not timed) while loop. 

I can read more sample points at a time with read method. 

 

It works for me. 

0 Kudos
Message 15 of 15
(367 Views)