LabVIEW
PID tuning array instance
Hi Andrew,
when opening the only lvproj file in your ZIP then the one and only VI referenced in this project is missing:
When opening some of those other VIs in that folder they also claim for missing subVIs…
What's so hard to maintain all related files in one folder and in one lvproj project file?
@GerdW wrote:when opening the only lvproj file in your ZIP then the one and only VI referenced in this project is missing:
When opening some of those other VIs in that folder they also claim for missing subVIs…
I got the same.
Search LabVIEW like a graph! 
Hi Andrew,
@AndrewIons01 wrote:
I have tried to put everything into one folder but apparently even as a zip file, it tells me that its too large. Is there another alternative?
Well, when the resulting ZIP file is too large, then you probably didn't create a "MWE"… 😉
@AndrewIons01 wrote:try this one and let me know how it goes. 🙂
I think our ideas about minimum are different 🙄.
We cannot run this code. Even if I had IMAQ installed, I wouldn't have the camera setup. How are we ever going to test values coming out of a PID without even valid inputs?
For a MWE (in this case, something that shows your error in the PID) I'd expect the PID VI and a VI that calls it. Nothing else.
BTW and OT:
At this time of your development, you might have a look at OO. It seems that the way you treat your camera (as an object) is very OO-ish. Putting all camera stuff in a camera class, and all camera data in the class's private data is pretty much what you're doing now, but with a class it will actually be nice. The camera is just one example, but very exemplary.
Once you have it working (and a good understanding of OO), it would be very (very) easy to make a child class that simulates the camera. That way, you can very easily switch between real camera input and a recording. As a bonus.
