myRIO FPGA FFT Error code

[ddddd212]

Hello everyone! I'm currently working on a microphone signal processing project where I can read time-domain data from 16 microphones. I then transfer the data via FIFO to another timed loop for FFT operations. However, I'm encountering the following error code when I try to compile and run the program, and I can't figure out why. Could anyone help me understand the reason for this? I'd really appreciate it!

Details:

An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
NiFpgaHandleCallbackError.vi
<APPEND>

<b>Complete call chain:</b>
NiFpgaHandleCallbackError.vi
niFpgaNodeInformation.lvclass:Get Array Term Size.vi
niFpgaFFTEmitDFIR.vi:2350002
niFpgaFFTEmitDFIR.vi.ProxyCaller

[Bob_Schor]

This is a Good News/Bad News response to your question.

First, the Bad News.  As wonderful as the myRIO is (or "was"), it has reached "End of Life" and is no longer "widely available".  In addition, the most recent version of the myRIO Software Toolkit is for LabVIEW 2021 (I don't remember the suffix, but I'm pretty sure it is 32-bit LabVIEW), and can be tricky to install.  Plus LabVIEW 2019 is not "officially" supported with Windows 11 (though that doesn't mean it won't work -- I still have a WIndows 10 PC handy with LabVIEW 2019 and the 2019 version of the myRIO Toolkit if I need it).

Now for the Good News.  If you do a Web search for "NI myRIO Fast Fourier Transform", you are led to the LabVIEW Forums (that's "right here") where @Ipfy asked how to do this, and answered it in his (or her) next post using LabVIEW 2019 (and the myRIO 2019 version of the Toolkit).  So simply search the Forum.

I'll note that the "solution" uses Express VIs, which I like to avoid, which also means that I don't have to deal with DDT (the aptly-named Dynamic Data Type, deadly poison for LabVIEW developers).  You can right-click the Express VI and "open its Front Panel" (after you've wired it up) and it will "stop being Express" and show you the underlying LabVIEW code, which probably has several "unnecessary" functions to handle "all possible cases", and which you can "prune" to make "clean" LabVIEW code.

Anyway, give it a try.

Bob Schor

[ddddd212]

Hey Bob Schor,

Thanks a lot for the ideas! I checked lpfy's post and realized we're doing FFT in totally different environments - he's probably using real-time (RT) setup while I'm working with FPGA. The processing logic might be different between these two (just guessing), but I'll keep digging into it.

Thanks again!