Hi, We have a LV program that numbers 100s of VIs. It was written in a "patches" method: A basic program was written, then the customers wanted a new feature and a "patch" was added, and then another, etc. The result is... a horrendous program, that is almost impossible to update without changing everything. We are now changing our hardware and want to rewrite the software as well. Now there are a lot more tools then there were. Do any of you have any tips on how to design it and what tools to use? We have a lot of features, a lot of variables, and everything is subject to change. The tips I have seen so far:1) Plan in advance (but how do I plan in advance for changes I don't know yet?)2) use typedefs3) do NOT use globals - use action engines or queues4) split the program into modules by functionality (what if many modules need to use the same basic function? won't that cause a problem? How best to pass data between modules?) Do you have any other ideas? Some requirements:- a wizard (as we have lots of options, a user wanting to perform a simple function usually gets confused)- Memory efficient (the current program gets hung up on memory). I have read up on managing large data sets in labview, I am just not sure how to incorporate it in a large program. to ALWAYS have in and out pins of an array in a subvi so it won't copy? to allocate in advance and adjust the size of arrays in blocks? use queues and not arrays?- we scan images of size up to 5000x5000 16 bit pixels, 16 channels. How best to store such data? Any ideas and tips would be welcome!!! Danielle

LabVIEW

Danielle,

Your e-mails are bouncing back.

Ben

Message 31 of 31

(498 Views)