-
Type: Task
-
Status: Won't Fix (View Workflow)
-
Priority: Normal
-
Resolution: Won't Fix
-
Component/s: ics_ccdActor, ics_enuActor, ics_xcuActor
-
Story Points:3
-
Sprint:SM1-2019 L, SM1-2019 M, SM1-2019 N
While listing the meta-keywords for sps, we realized with fmadec that it would be much simpler if all the sps actors (enu, ccd, xcu ..) and their devices would have the same state machine mechanism.
As as they all inherit from tron_actorcore.ICC, if would be worth putting the code which handle the state machine directly the in the actorcore, with prototyped (functions, callback ...) which are called when passing from one state to the other .
It would be still up to the developer to fill those functions, but the machinery behind would do most of the work and generate the useful keywords .
If everybody agree, we think it would be a good idea.
I will join the basic design that we have in mind.
- relates to
-
INSTRM-425 Implement state engine in ccdActor
- Open
-
INSTRM-426 Implement state engines in xcuActor
- Open
-
INSTRM-265 List and describe meta keywords for sps
- Won't Fix