From Friday, January 17th 11 PM CDT (January 18th 5 AM UTC) through Saturday, January 18th 11:30 AM CDT (January 18th 5:30 PM UTC), ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
I am trying to call an external sequence from a step generated by the ATML toolkit. I have set the ATML customType to SequenceCall and it correctly places a Sequence call step. When I use the custom callbacks to specify the sequence to call I run into an issue. It seems no matter which method I try for loading the external sequence prototype it hangs the code generation when loading the sequence.
After correctly specifying the sequence to call I have tried:
Module.LoadPrototype() -> Hangs at this function (you have to kill TestStand then the method will complete with an error.
SequenceCallModule -> Requires you to open a refence to the sequence will then hang at Engine.GetSequenceFileEx (not matter what options I pass) or if I use SequenceAdapter.GetSequence it hangs at this function.
As far as I can tell it seems impossible to open an external sequence during ATML code generation. I have tested these methods outside of the ATML toolkit and they work fine.
Is this a known limitation of the ATML toolkit? Is there a workaround?
