Problems with VI after integrating into robot project.

[tcjinaz]

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

[Levansic]

Originally Posted by tcjinaz

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:

Hi Tim. Yes, we made them re-entrant. That's standard practice for us for sub-vi's, as we tend to make utility functions that can be used in multiple places. The motion filter used here is such a vi, as we are using it in our autonomous to generate acceleration and deceleration for more repeatable robot placement.

This problem was hard to diagnose, because we couldn't get to a running state, except in a non-interactively deployed running of all of our robot code. I think we tried every iteration that we could find on the execution pane of VI preferences, just to try to shake out any clues.

[tcjinaz]

Schooled. I didn't finish reading the thread. I had been trying to teach re-entrant lately, and had array initialization problems for a while...

After the season's over question:

Did you really need 4 state bits (well, 5, there's an integer masquerading as a state bit)? I love programming; there are so many answers to a question

Stack'm high,
Tim