'StatesDefined' in sma

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
'StatesDefined' in sma
#1
wondering about this field in the sma.

in all the example protocols I have, all values = 1.

what is the intended use of 'referenced' versus 'added' states?

is there an example protocol that makes use of this functionality?
Reply
#2
Hi Justin


I'm assuming you're referring to comments about the fields sma.StatesDefined and sma.Manifest
'Referenced' means that a state has been referenced in a different state's declaration. In the first call to the AddState() function, I can say (in pseudocode)

Name: MyState
Timer: 0
StateChangeConditions: BNC1High, Go to MyOtherState
OutputActions: None

Here, I Added MyState to the state machine. I Referenced MyOtherState, but I haven't added it yet. That will happen in a future call to AddState.

When you send a state machine, the system uses sma.StatesDefined and the manifest to make sure you eventually defined all of the states you referenced.
Reply
#3
(03-14-2017, 03:47 AM)Josh Wrote: Hi Justin


I'm assuming you're referring to comments about the fields sma.StatesDefined and sma.Manifest
'Referenced' means that a state has been referenced in a different state's declaration. In the first call to the AddState() function, I can say (in pseudocode)

Name: MyState
Timer: 0
StateChangeConditions: BNC1High, Go to MyOtherState
OutputActions: None

Here, I Added MyState to the state machine. I Referenced MyOtherState, but I haven't added it yet. That will happen in a future call to AddState.

When you send a state machine, the system uses sma.StatesDefined and the manifest to make sure you eventually defined all of the states you referenced.

I see, just a 'housekeeping' field then. Thanks!
Reply
#4
Nice Topic and nice information
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)