LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Mysterious function ReNIFFTH appears instead of ReFFTH for lvanlys.dll

We have a test app written in LV 7.1, and some of the subVIs use RealFFT.vi.  The app was released as an executable years ago and still runs fine today.  However, today I went out to the same machine and looked at the original source code.  I opened the top level VI and it was broken because several subVIs were not executable.  I drilled down through subVIs to RealFFT.vi which was broken because the library interface node referred to a non-existent function (ReNIFFTH() in lvanlys.dll).  There were other subVIs that were broken for other non-existent functions in dll's.  Just for the heck of it I closed all the VIs and then opened RealFFT.vi alone.  It was no longer broken.  I looked at the configuration of the library interface node to see what dll it was looking at and the function name.  It was ReFFTH().  I then opened the top-level VI again and it was broken again for exactly the same reason as the 1st time.  In the configuration of RealFF.vi's library node I could see it was looking at the same dll, but the function name just wasn't correct.  I then scrolled down and selected ReFFTH(), and then the subVI was OK.  How could the same subVI be showing me different functions depending on how it is being opened?  Where is the the function name ReNIFFTH() coming from?  I did a search on it and there were 0 hits.  Any idea what I'm seeing here?

 

Thanks,

Brad 

0 Kudos
Message 1 of 2
(2,535 Views)
Hello Brad, I have a quick question for you. Did changing the subVI in the top level VI resolve the problem for good? In other words, if you open the top level VI again is it still broken or will it now run? If it will now run, it is likely that the subVI that you changed the first time was actually a different subVI than the VI in your application. As for how this function name got changed in the first place I have no idea. Perhaps the function name in your VI never changed. Instead, maybe the function name inside of the dll changed if the dll was replaced somehow. Hope this helps!
0 Kudos
Message 2 of 2
(2,501 Views)