FPGA - Vibration Analysis

Why do you want to this ?

Will the user of the instrument look at the screen and make decisions based on  the DFT of the incoming data.

Or will you store the data and need to process it later.

Why not just buy some kit that is ready sorted and can do it all for you - there is a huge amount of work in getting the boards you discuss suitable package with batteries etc to take out into the field.

Will you want to do order tracking - if so then you'll need additional sensors and inputs.

Is this a commercial project or for education.

Is the primary aim to protect the machine, gather data or design some data acquisition hardware.

Why might you wish to use an FPGA to do the Fourier Transforms - some FPGAs are very capable but unless you know how to use them you will need to do a lot of work to get as far as you would running  a Python library on a Raspberry Pi or using C/C++  on a PC.

The accelerometer you quote has a working bandwidth of about 10kHz to you would not need a very high sampling rate - 50k s/s should be enough.

The MCC board would do fine -  Jan Cumps has reviewed that part on E14. You should be able to display results on the Pi's display - no tablet required.

MK

Thank you so much for the reply.

I am a Mechanical / Marine Engineer with some knowledge of electronics. We operate several diesel engines and often run into problems with huge financial effects. Though we strictly implement planned maintenance routines but engines do suffer frequent breakdowns. The purpose is to put in place a "Condition based monitoring" plan. The latter is my motive to develop such a monitoring system. Perhaps that answers the first question.

Idea is to capture the FINGERPRINT of a good engine and keep track while it runs, continually comparing it with the FINGERPRINT. Any anomaly ie a rise in amplitude or a new frequency popping up / frequency harmonics, would mean that engine needs to be checked for possible issues. Yes, indeed I do need to store date to view FFT / Frequency domain graphs later. 

Honestly, never used FPGAs. My colleague at work has done work on FFT related to RF Receivers. But  tying up a suitable FPGA to a LCD is under thought. Same reason seeking help from friends on this forum. 

Raspberry Pi is not powerful enough. PC is the solution but difficult to place around engine room spaces. Tablet / Dell i7 type should work for their higher resolution.

I am planning to go for the CN0540 by Analog Devices which has a similar sampling rate of 50k samples/ sec.

I shall discuss with Jan Cumps too.

At present the Project remains  within the confines of my garage. If I am successful in distinguishing between the fingerprint and subsequent running FFTs of the engines, then will go commercial. As yet, there is many a slip between the cup and the lip.

Thank you so much for the reply.

I am a Mechanical / Marine Engineer with some knowledge of electronics. We operate several diesel engines and often run into problems with huge financial effects. Though we strictly implement planned maintenance routines but engines do suffer frequent breakdowns. The purpose is to put in place a "Condition based monitoring" plan. The latter is my motive to develop such a monitoring system. Perhaps that answers the first question.

Idea is to capture the FINGERPRINT of a good engine and keep track while it runs, continually comparing it with the FINGERPRINT. Any anomaly ie a rise in amplitude or a new frequency popping up / frequency harmonics, would mean that engine needs to be checked for possible issues. Yes, indeed I do need to store date to view FFT / Frequency domain graphs later. 

Honestly, never used FPGAs. My colleague at work has done work on FFT related to RF Receivers. But  tying up a suitable FPGA to a LCD is under thought. Same reason seeking help from friends on this forum. 

Raspberry Pi is not powerful enough. PC is the solution but difficult to place around engine room spaces. Tablet / Dell i7 type should work for their higher resolution.

I am planning to go for the CN0540 by Analog Devices which has a similar sampling rate of 50k samples/ sec.

I shall discuss with Jan Cumps too.

At present the Project remains  within the confines of my garage. If I am successful in distinguishing between the fingerprint and subsequent running FFTs of the engines, then will go commercial. As yet, there is many a slip between the cup and the lip.

I think you might find that Pi is a good deal more powerful than the Arduino type boards the CN0540 is designed to connect to.

And if the MCC172 will work with the Pi4 or even better the Pi5 there is plenty of computing power for single channel of vibration.

Good luck.

MK

you are correct indeed. I have been told that Pi5 is not available yet? 

MCC172 is preferable as can be stacked if more sensors are needed to work in tandem.

Thanks.