SequenceState it´s a number

[runtimevic]

Hello
SequenceState it´s a number
I think it would be better for the program if it were not a number type variable, but rather a Local enumeration or an Enumeration

• https://infosys.beckhoff.com/content/1033/tc3_plc_intro/2529504395.html?id=1958379849120335737
• https://alltwincat.com/2021/11/16/local-enumerations/

My proposal would be to remove the SequenceState variable from FB_packML_BaseModule of SPT_Libraries...

In this way, I think we would have more advantages, such as knowing what sequence is being carried out implicitly with its enumeration and not with a numerical value whose meaning we do not know...

[albertgoodwin]

I personally find the sequence and descendant sequence states very useful, as they can be used in many pack ml states and mean different things. They help to increment through a sequence of motion commands (reset - enable - home - move). An enumeration would add value if you planned to jump between cases out of numerical order, but I don't think that is the intent.

[runtimevic]

I personally find the sequence and descendant sequence states very useful, as they can be used in many pack ml states and mean different things. They help to increment through a sequence of motion commands (reset - enable - home - move). An enumeration would add value if you planned to jump between cases out of numerical order, but I don't think that is the intent.

@albertgoodwin ,
I think we need to strive for clarity and transparency, so that the program explains itself as best as possible, and I don't think a sequence number can achieve that...