LabVIEW
LabView VI Optimization
Hi amp,
Could anyone suggest me a way to make this smaller? i tried using sub VIs but they help only to an extent.
- Start from scratch and use a better architecture, like state machines or producer-consumer schemes.
- Separate device IO into their own loops/subVIs.
- Use Subpanels for those different tab pages to move FP elements into their own (sub)VIs.
- Use event structures to handle things like those "Visible" properties - instead of setting the same properties in each iteration…
- Remove Rube-Goldbergs like that inner case structure in the 2-Punkt-Hysterese-Regler…
- When those charts should be cleared upon stopping the while loop then you should call those "History" property nodes AFTER the loop… (Why do you need to clear charts upon stopping a VI at all???)
- …
(Ihr habt doch an eurer Hochschule bestimmt auch eine Informatik-Abteilung, die dir bei sowas helfen könnte!?)
You can start by removing the 3 inches on the left, with ctrl-alt-drag. That's the easy one 
.
I'd start by removing all the silliness. Most case structures can be replaced by one or two selectors. Some even by a or\and function. I'd do this mostly to get to know the application a bit.
To be honest, this one is borderline "start all over". It would depend on the content of the subVIs, which we don't have.
Search LabVIEW like a graph!
@GerdW wrote:(Ihr habt doch an eurer Hochschule bestimmt auch eine Informatik-Abteilung, die dir bei sowas helfen könnte!?)
Unless they made it in the first place 
. I've seen enough professional programmer groups without any standards.
Hi Wiebe,
I've seen enough professional programmer groups without any standards.
And more than enough students just being taught to usage of ExpressVIs… 🙂
@amp:
Forgot to mention: implement a better data handling, mabye even based on key-value-pairs (or maps nowadays)…
