Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

NI 9802; issues with write

Hello,

      I have seen some examples and posts about writing to the NI 9802.  I have been able to mount an SD card and ftp to the drive (u: in my case) using MAX and SecureFX.  I have also been able to write and read using the NI 9802 example included with LabVIEW on the real-time side.  However,I have not been able to directly write to the SD card using the FPGA and then find a CRIO-X##.BIN afterwards.  When I remount the drive, I can see files previously written, but I am not able to see a bin file.  It should be visible, correct?  I'll also note that I have to abort execution to get this vi to stop.  Thank you for your time.

 

Aaron

 

FrontPanel_DOE_FPGAv2.jpg

 

DOE_FPGAv2.jpg

FYI  During compilation, I get the following: The design might fail to meet timing constraints because one of the estimated maximum clock rates is less than the requested rate. Refer to the 'Estimated timing (synthesis)' report for more details.

 

After successful completion:

Compilation completed successfully.

Device Utilization
---------------------------
Total Slices: 12.3% (5037 out of 40960)
Flip Flops: 10.4% (4266 out of 40960)
Total LUTs: 32.7% (6694 out of 20480)
Block RAMs: 32.5% (13 out of 40)

Timing
---------------------------
MiteClk (Used by non-diagram components): 33.04 MHz (60.91 MHz maximum)
40 MHz Onboard Clock: 40.41 MHz (40.83 MHz maximum)
80MHz (Used by non-diagram components): 80.00 MHz (81.37 MHz maximum)

Actual Xilinx Options
---------------------------
Synthesis Optimization Goal: Speed
Synthesis Optimization Effort: High
Map Overall Effort Level: High
Place and Route Overall Effort Level: High

Start Time: 4/22/2010 10:55:52 PM
End Time: 4/22/2010 11:13:17 PM

0 Kudos
Message 1 of 5
(3,846 Views)

Hi amazzeo,

 

Have you tried the example for writing to the File in an FPGA VI?  The two major differences between yours and the example are the use of shift registers for the error wires and FileRef and a check for errors during the loop.  Also, do you have anything else in your VI other than this part?  Usually this warning occurs when you're using a single-cycle timed loop.

Jared S.
Applications Engineering
National Instruments
0 Kudos
Message 2 of 5
(3,820 Views)

Thank you for the response.  I have tried the NI 9802 Write example, and it worked for me.  However, when I modified the write example to the following (attached image).  It no longer works.  The vi does not write a bin file, and the vi does not automatically stop (I have to abort).  Any ideas?  I must be doing something silly.  Thank you again.

 

Aaron

 

NI 9802 Modified Write Front Panel.jpg

 

NI 9802 Modified Write.jpg

0 Kudos
Message 3 of 5
(3,814 Views)

Hi Aaron,

 

It looks like that should work fine.  Try wiring the for loop iteration count to an indicator.  If the index continues to grow, then you should change the equal to a less than or equal to.  Also, is there a reason you have the Close File inside the case structure, while the Open File is outside the structure?  What happens in the other case?

Jared S.
Applications Engineering
National Instruments
0 Kudos
Message 4 of 5
(3,786 Views)

Jared,

      Thank you for the reply.  For the given application I am working on, I decided to not use the NI 9802.  This decision came after some frustrating tinkering and the realization that it might not be necessary for this particular application.  If/when I decide to go back to the NI 9802, I might have a new post.  Thanks again.

 

Aaron

0 Kudos
Message 5 of 5
(3,773 Views)