Quote:
Originally Posted by Levansic
Well, we fixed the problem. We made a change to our motion filter sub-vi.
I think the issue is that although we set sensible default values that should have given a sane size for the array at compilation, there was no error checking to catch insane values or sizes that may be undefined or not a number. The array initializer wants an integer input for the size, rather than an unsigned int. For all I know, the value the compiler could have been accounting for may have been a very large negative number.
We coerced the array size to between 1 and 10 elements, which is generous for all of our anticipated use cases. We can always bump up the upper limit if we need a slower ramp rate.
If you are interested, the code is at our git repository, posted above.
|
Did you make the VI re-entrant? You seem to instantiate it more than once, each instance needs its own, unique memory for the eight feedback nodes:
File->VI properties->Execution->Preallocated Clone Reentrant Execution
Good luck,
Tim