kewakl (Customer) asked a question.

[RESOLVED] Productivity Suite 4.4.0.60 and 4.7.0.47 MSEQ and MMSEQ 'Sequence In' and 'Sequence Out'

The 'Write Sequence Out' and 'Wait Sequence In' sequence step commands do NOT accept the provided boolean array entry.

Help topic P325 says that these tags should be 8-element Boolean arrays

MSEQ and MMSEQ act this way.

 

What am I doing wrong?

 

[Resolution: These fields only require the numeric INDEX into the specified array, not the whole array tagname.]


ADC Community_02 likes this.
  • ADC Community_02 (Automationdirect.com)

    From our developer: In the picture, the SeqIn Boolean array tag is si and the SeqOut Boolean array tag is

    so. The Param 1 column is the index into those arrays, not the arrays themselves — that's why the tag selector accepts int/float there.

     

    I just tested this in 4.7.0.47, and it works correctly with both integer and float tags in the Param 1 column.

    The third picture shows the help file with the correct requirement circled: it calls for a Boolean array index, not a Boolean array.

     

    Give it a try — it works as designed.

    Expand Post
    Selected as Best
  • ADC Community_02 (Automationdirect.com)

    I just checked mine and I can pick an int8 array tag from the dropdown.

    image

    • kewakl (Customer)

      The help topic specifies a BOOL array for Seq In and Seq Out, and that the valid states are TRUE and FALSE (and for the Seq In, a wait time in mSec)

      I can select int/float. I would prefer the BOOL() as specified in P325

      • ADC Community_02 (Automationdirect.com)

        Ok sorry about that misunderstood. Let me look into this with the developer.

         

      • kewakl (Customer)

        Thank you very much.

        I do not have the hardware to test this. I do not know if an INT array will work for me and do what I need.

  • ADC Community_02 (Automationdirect.com)

    From our developer: In the picture, the SeqIn Boolean array tag is si and the SeqOut Boolean array tag is

    so. The Param 1 column is the index into those arrays, not the arrays themselves — that's why the tag selector accepts int/float there.

     

    I just tested this in 4.7.0.47, and it works correctly with both integer and float tags in the Param 1 column.

    The third picture shows the help file with the correct requirement circled: it calls for a Boolean array index, not a Boolean array.

     

    Give it a try — it works as designed.

    Expand Post
    Selected as Best
  • kewakl (Customer)

    Thank you. I cannot test this without the hardware, but I can understand the idea behind your last post!

     

    Thanks again