State Variable input communicator in an A/Car actuator function produces an error when re-opening the template.

Question

I have an issue using a variable type input communicator in an A/Car actuator function. Template builder accepts the "cis_xxx" communication without a problem, but after saving and reopening the template I receive an error message that the "cis_xxx" communicator is the wrong type. Editing the text of the template manually to push the function modify to the bottom of the file solves the error when reopening template. But the problem comes back each time the template is saved. Is there a more robust solution than editing template every time I save the template?

Thanks

greg.wheeler · Accepted Answer

Hi John. You can always save the template in binary format instead of TeimOrbit (ASCII).

However, you shouldn't have to. I think maybe the actuator should reference the "cis_*_adams_id" instead of the "cis_*".

For example, actuator function =1.0 * varval(cis_*_adams_id) + 0.0