Editing a runtime or compiled labview project

[gccustom]

About 7 years ago a customer had a guy write a labview program for him. It reads some data from a scope does some calculations puts the new waveform on the labtop and then puts a error on the screen. We are not sure what the error means. We cannot get a hold of the guy that wrote the program to look at the source to see where the error is coming from. Is there a way to open the runtime or compiled program we got.

Thanks

[altenbach]

It simply means that a filter has incompatible settings. Check your sampling frequency and high/low filter frequencies.

Unfortunately we really can't tell where that would be looking at a clipped photograph of your screen.

[gccustom]

Thanks for the reply we will check what you mentioned. So about opening the runtime or compiled version that we have to figure out exacting what parameter is the issue. Is there any way to do that or do we need the source file.

Thanks

[Bob_Schor]

---

@gccustom wrote:

So about opening the runtime or compiled version that we have to figure out exacting what parameter is the issue. Is there any way to do that or do we need the source file.

---

There is basically no practical way to do that.  You need the source file, or you need to create another LabVIEW (or C++ or Python or whatever) routine to do what your current compiled routine does.  Do the LabVIEW sources exist anywhere?  Can you contact the original developer?

Bob Schor

[altenbach]

You only have access to the controls exposed to the user on the front panel. The graphical code gets stripped out when building an executable (by default).

If the filter parameters are hardwired, maybe you are using a sampling frequency that is way different than ever intended by the programmer. Do you know who wrote the program? A correct program should be able to check all user inputs for sanity and conflicts before they get thrown at the algorithm.

What are the default values for all user controls? That should give you a hint. (Maybe there is a control to enter frequency and it is still at zero!)

I would not trust any code where "a customer had a guy write a labview program for him" (sic), unless that "guy" had at least CLD certification. It happens way too often that problems gets thrown at a summer intern or some high school dropout with little experience. That "guy" should have also provided all source code at the conclusion of the project.

[gccustom]

Thanks for the reply. So far we have not been able to find him. I was trying to find our options like if we could open it somehow but i know now we cant. So we will look at settings on the scope and continue trying to find the guy if we cant find something wrong in settings.