Jump to content

Engine In-cylinder Pressure w/ cRio


Recommended Posts

Basic Strategy:

I'm trying to measure in-cylinder pressure of an IC engine using a cRio (NI 9205 for pressure, NI9411 for encoder). We're using a quadrature encoder so pressure data can be recorded with respect to engine time (ie crank angle degrees). The FPGA writes pressure data to a FIFO each time it receives an A pulse (720/revolution). One engine cycle is two revolutions so a complete data set is 1440 points in the FIFO buffer. The RT VI waits until there are the correct number of points in the buffer and then reads the FIFO.

Issue:

This strategy works when the engine speed is less than 1600 rpm and a display on the RT shows a perfect pressure trace for each cycle. At anything greater than 1600 rpm the pressure trace begins to drift wrt crank angle degrees. To me this indicates that the FPGA is missing an A pulse meaning it takes longer for the FIFO buffer to reach 1440 data points.

Questions:

Is it possible that the FPGA/9205 is not fast enough to capture each A pulse and write a data point?

Is this a sound strategy for transferring data from the FPGA to the RT VI?

Is it possible that the FPGA is sensing every A pulse but cannot write data because the RT is querying the FIFO?

Any suggestions for how to fix this would be greatly appreciated. Thank You.

FPGA_Main.vi

rt_main.vi

Link to comment

Basic Strategy:

I'm trying to measure in-cylinder pressure of an IC engine using a cRio (NI 9205 for pressure, NI9411 for encoder). We're using a quadrature encoder so pressure data can be recorded with respect to engine time (ie crank angle degrees). The FPGA writes pressure data to a FIFO each time it receives an A pulse (720/revolution). One engine cycle is two revolutions so a complete data set is 1440 points in the FIFO buffer. The RT VI waits until there are the correct number of points in the buffer and then reads the FIFO.

Issue:

This strategy works when the engine speed is less than 1600 rpm and a display on the RT shows a perfect pressure trace for each cycle. At anything greater than 1600 rpm the pressure trace begins to drift wrt crank angle degrees. To me this indicates that the FPGA is missing an A pulse meaning it takes longer for the FIFO buffer to reach 1440 data points.

Questions:

Is it possible that the FPGA/9205 is not fast enough to capture each A pulse and write a data point?

Is this a sound strategy for transferring data from the FPGA to the RT VI?

Is it possible that the FPGA is sensing every A pulse but cannot write data because the RT is querying the FIFO?

Any suggestions for how to fix this would be greatly appreciated. Thank You.

Your VIs here need some other necessary parts, but you don't give. We can't open these VIs successfully.

mcniko311, You should know the maximal sampling rate of your system and what is the number of FIFO' s bytes. you need make sure that an overflow doesn't happen.

Lodestar

Edited by Lodestar
Link to comment
  • 3 years later...
i'm just trying to read the engine in-Cylinder pressure with the CAD, and plot them in a graph.

 

Well, as far as the LabVIEW code is concerned it is just an anolog read possibly with the use of a FIFO together with a digital read for the encoder. So you will have to find what cRIO module can do the task, based on your requirements for voltage or current range of your sensor and the sample speed you need to get your data with. Then, based on the module type, you look for LabVIEW example VIs that come with the FPGA toolkit. Study them, try to make small changes to them to understand how they work and go from there.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.