Remove Duplicate Var Declarations.vi | Arduino Compatible Compiler for LabVIEW Discussions | Forum

Wow; actually it is the first time I see this error message related to the compiler. This is not an error message generated by the Compiler though, it is coming from LabVIEW itself. I did a quick Google search on it and got some hits (below). The LabVIEW error seems to be related to large array allocation that breaks the allocated amount of memory to LV. However, your post indicates that sometimes you are able to download your code to your Arduino target. Does the target behave correctly running your code? The reason why I am asking this is, the Arduino target has much less memory than your dev PC; therefore, if this error is indeed related to large arrays on your dev PC; it will definitely break your target memory also; which will cause the Arduino to behave not according to your code. 

http://digital.ni.com/public.n.....B5006B46E1

http://digital.ni.com/public.n.....4000834238

Hello;

I have taken a look at your code. I have tried to isolate the issue to a string SR; but that wasn't in fact the source of the issue. I have replaced the SR on case 43 of your VI with other data types and the issue persisted. I couldn't find the root cause of the problem; however, your VI is very involved for an Arduino target. There are some subVIs that are floating without data flow dependency and a large sequence structure with nested structures that also contain floating VIs. This is probably pushing the limits of what the optimizer algorithm for the compiler can do for such a small target like the Arduino.

One suggestion would be for you to try and reduce the nestness aspect of your VI and enforcing data flow whenever possible via error cluster. 

Filipe

Please consider re-architecture your VI(s).  Just like in normal LabVIEW, it is bad practice to put most of everything into one VI in one large sequence structure.  This becomes of even greater importance for a small memory target.

The way the ACC4LV compiles your code is that it process things one VI at a time and each VI gets essentially converter to a function 1 for 1.  So even if your code did compile fast, it would still be pretty sketchy on an Arduino because all the memory allocations (well most since you do have a few subVIs) would be happening on the stack level in one function so to speak.  By modularizing your code you are effectively increasing its performance and memory management since the stack can release memory as the function goes out of scope (automatic variables).  This is discussed in the Important Considerations section of the user manual.

Im guessing the long compile time problem you are facing here has to do with the extensive use of sequence frames and nested structures.  I can tell you we have very complex programs in use running upward of 60% flash usage on Arduino targets and they have very quick compile times.  But they make heavy use of modularizing functionality into smaller functional blocks and subVIs.  You also have a lot of duplicated code, which can definitely take longer to convert and compile.  I would recommend creating a reusable SubVI for similar parts of your VI (like setting the 4 digital outputs) as well as breaking apart each section of your sequence structure into smaller modules/subVIs.