Device for implementing hierarchical state charts and methods and apparatus useful therefor

[0002] This application is a Continuation of Ser. No. 08/868,278, filed on Jun. 3, 1997, now U.S. Pat. No. 5,995,739.

[0003] The present invention relates to computer code and to apparatus and methods for computer code generation.

[0004] Hierarchical state charts are described in “Statecharts, a visual approach to complex systems”, David Harel, Science of Computer Programming, 1987.

[0005] The disclosures of all publications mentioned in the specification and of the publications cited therein are hereby incorporated by reference.

[0006] The present invention seeks to provide improved computer code and improved apparatus and methods for computer code generation.

[0007] There is thus provided in accordance with a preferred embodiment of the present invention apparatus implementing hierarchical state charts and including a state machine engine (SME) operative to carry out repertoires of behaviors of a system, a state chart encoder operative to replicate, in computer code form, a user-defined hierarchical state chart describing a repertoire of behaviors of the system, the encoder being operative to preserve the state chart's hierarchical structure intact in a first data structure, an event list generator operative to generate, for each individual event from among a plurality of events within the repertoire, a list of at least one transition between states of the state chart which are associated with the individual event, the event list generator being operative to preserve the list in a second data structure, and a behavior implementer operative to activate the system to carry out each of the behaviors in its repertoire.

[0008] Further in accordance with a preferred embodiment of the present invention the system includes at least one of hardware and software.

[0009] Still further in accordance with a preferred embodiment of the present invention the first data structure's size increases linearly in direct proportion to the number of branches in the hierarchical structure.

[0010] Additionally in accordance with a preferred embodiment of the present invention the second data structure's size increases linearly in direct proportion to the number of transitions in the list of at least one transition.

[0011] Moreover in accordance with a preferred embodiment of the present invention the order of the at least one transition of each of the lists corresponds to the order of evaluation of the transitions as defined by the hierarchical state chart.

[0012] Further in accordance with a preferred embodiment of the present invention the plurality of events for which the event list generator generates lists includes at least one external input event.

[0013] Still further in accordance with a preferred embodiment of the present invention the plurality of events for which the event list generator generates lists includes at least one internal data value change event, the apparatus also including a data value change event notifier operative to generate a notification to the state machine engine of each data value change event.

[0014] There is additionally provided in accordance with a preferred embodiment of the present invention a method implementing hierarchical state charts, the method including providing a state machine engine (SME) operative to carry out repertoires of behaviors of a system replicating, in computer code form, a user-defined hierarchical state chart describing a repertoire of behaviors of the system, the replicating step being operative to preserve the state chart's hierarchical structure intact, generating, for each individual event from among a plurality of events within the repertoire, a list of at least one transition between states of the state chart which are associated with the individual event, and activating the system to carry out each of the behaviors in its repertoire.

[0015] There is additionally provided in accordance with a preferred embodiment of the present invention an automatic code generation method including automatically generating code which forms, in memory, a replica of a hierarchical state chart which preserves the chart's hierarchical structure, automatically generating code which forms, for each of a first plurality of input events, a list of transitions affected by that input event, automatically generating code which forms, for each of a second plurality of internal data variables, a list of transitions affected by changes in that internal data variable, automatically generating code which notifies the state machine engine of changes in internal data variables, and automatically generating code which evaluates conditions and implements actions and activities.

[0016] Further in accordance with a preferred embodiment of the present invention the method includes the step of providing a state machine engine operative, upon receipt of notification regarding occurrence of an event, to evaluate a list of transitions affected by the event so as to select transitions to be performed, and to perform the transitions.

[0017] There is additionally provided in accordance with a preferred embodiment of the present invention a method for computing a state for a hierarchical state machine, the method including providing a state machine engine operative to receive notification regarding occurrence of at least one event, providing a hierarchical state chart describing a repertoire of behaviors of a system, providing a list of at least one transition between states of the state chart for each of the events with which the at least one transition is associated, evaluating the list of at least one transition so as to select a transition to be performed in response to the at least one event, and evaluating the hierarchical state chart to compute the state that corresponds to the selected transition.

[0018] The present invention will be understood and appreciated from the following detailed description, taken in conjunction with the drawings in which:

[0019] FIG. 1 is a simplified block diagram of a software system constructed and operative in accordance with a preferred embodiment of the present invention which includes automatically generated code which interfaces with a state machine engine (SME);

[0020] FIG. 2 is a simplified flowchart illustration of a preferred method of operation for the state machine engine of FIG. 1;

[0021] FIG. 3 is a simplified flowchart illustration of a preferred method for generating high level computer code from hierarchical state charts;

[0022] FIG. 4 is a pictorial illustration of a computer screen generated in the course of automatically generating computer code from hierarchical state charts in a particular example;

[0023] FIG. 5 is a pictorial illustration of a computer screen, generated in the course of processing the example of FIG. 4, which shows all modes making up the state chart of the example;

[0024] FIG. 6 is a pictorial illustration of a computer screen, generated in the course of processing the example of FIG. 4, which shows an alternative presentation of the state chart of FIG. 5; and

[0025] FIG. 7 is a simplified flowchart illustration of an automatic code generation technique operative in accordance with a preferred embodiment of the present invention.

[0026] Reference is now made to FIG. 1 which is a simplified block diagram of a software system constructed and operative in accordance with a preferred embodiment of the present invention which includes automatically generated code 10 which interfaces with a state machine engine (SME) 20. An optional interface 30 to underlying hardware (not shown) is also provided.

[0027] The state machine engine 20 is a pre-built object code module that is linked, either dynamically or statically, to the automatically generated code and the interface library.

[0028] The state machine engine implements the behavior of the software system preferably as defined solely by the automatically generated code that is linked with it. That being the case, the state machine engine code is typically provided only once in object code form, and does not need to be changed per software system.

[0029] The state machine implements this behavior by converting input events and changes of data values into transitions within the hierarchical state chart, and then implementing these transitions. It does this by computing the new state associated with this transition, deactivates the relevant parts of the old state and finally activates the relevant parts of the new state.

[0030] A preferred method of operation for the state machine engine (SME) 20 is described by the flow chart of FIG. 2.

[0031] The SME begins operation by building initial data structures based on data provided by the automatically generated code 30. These data structures typically include:

[0032] a data structure that is a one to one representation of the hierarchical state chart,

[0033] a data structure that couples together any input events with the transitions that are triggered by these input events,

[0034] a data structure that couples together any data variables in the application with transitions that are triggered by changes in the value or state of these data variables, and with any expressions that must be evaluated when these data variables change, and

[0035] a pointer to all logic and activity functions within the automatically generated code.

[0036] The SME then enters its normal operating state, which is to wait for any input events or any changes in data values. It is appreciated that input events may originate from a hardware device, such as a lamp as described in greater detail hereinbelow with reference to FIG. 4, or from a software process, such as an interprocess message.

[0037] When an input event notification arrives or a data change notification arrives from the automatically generated code, SME 20 checks if the event or data structure that triggered the notification has a list of transitions or logic expressions associated with it. If not it discards the notification and returns to its normal operating state.

[0038] If the source of the notification does have such a list associated with it, the SME then checks each entry in the list and selects those entries that belong to a state that is currently active. All other entries are ignored.

[0039] The SME then iterates over the selected list and checks each entry.

[0040] If an entry is a transition, and the source state of that transition is still active, the SME performs the transition by computing the new state associated with the transition, deactivating those parts of the current state that will no longer be active in the new state, and then activating all those elements in the new state that were not active in the current state. The new state then becomes the current state.

[0041] If the entry is a logic expression, rather than a transition, the SME evaluates this expression by calling the corresponding functions in the generated code.

[0042] Once the SME has processed all entries in the list, it returns to its normal operating mode to await the next notification.

[0043] Referring back to FIG. 1, the automatically generated code 10 is a translation of a hierarchical state chart description of a system, in addition to all data elements in the system, which, when compiled and run together with the SME and the interface library, implements the behavior of the original system.

[0044] The automatically generated code 10 typically comprises some or all of the following components:

[0045] code to generate in memory, on a one to one basis, a replica of the original state chart, including the transitions and activities as defined,

[0046] code to generate the lists that link sources of input events with the transitions to be evaluated when notification of these events are received by the SME,

[0047] code to generate the lists that link data variables with the transitions and the logical expressions to be evaluated when notification of changes to these data variables are received by the SME,

[0048] code to generate the notifications to the SME whenever a data variable changes,

[0049] code to evaluate the conditions and to implement actions and activities that describe the behavior of the system described by the original state chart, including code to activate elements of hardware or software as specified by the state chart,

[0050] code to deliver to the SME any of the above as is needed by it.

[0051] The object code interface library 30 to the underlying hardware is optional pre-built object code that allows one or both of the state machine and the automatically generated code to interact with the hardware on which these elements operate.

[0052] This object code interface library is specific to the hardware on which the system is to be run.

[0053] Conventional technology for generating high level code from state charts has entailed generating a static representation of all the possible transitions and states as described by the state chart, as well as generating code for the state machine that activates these various states. In general, the state and the state machine are inseparable in such generated code.

[0054] The two main techniques available for accomplishing this have been: state machines built of nested branch statements and state machines built around state transition tables.

[0055] In the first technique, code generation using branch statements, the state chart formalism is converted into a large number of typically deeply nested branch statements, where each branch statement represents one of the possible transitions. The depth of nesting is at least as deep as the deepest hierarchy in the state chart and increases non-linearly as a function of the depth of all branches in the state chart, the width of the branches and the number of possible input events.

[0056] Branch statements are statements of the type “if-else” or “switch-case”.

[0057] For simple programs this may be adequate, but in general, because of the large amount of code needed to code the nested branch statements, this technique produces overly large programs.

[0058] Every possible input event is typically represented by some sort of flag. When an input event occurs, the corresponding flag is set to indicate this. The state machine mechanism involves continuously cycling through all the branch statements in the search for any branches that involve flags which may have been set before the current cycle as well as any condition statements that may have become true due to a variable changing value. This has the inevitable result that such code is very slow, especially since every cycle has to go through the deeply nested branch points that make up the code. This makes this type of code big and too slow for any application that requires a fast response time or modest memory requirements.

[0059] In the second technique, code generation using state transition tables, a procedure or function is generated for every possible transition and state, together with a state transition table that is used by the generated state machine for choosing which procedure to call for every possible external input. This state transition table is, in effect, a two-dimensional array whose indices are “input event” and “current state” and whose value is the new state.

[0060] The state here is not a hierarchical state, but rather a state in a normal linear state diagram, which is derived from the state chart by “flattening out” the original state chart.

[0061] When an input event arrives at the state machine, the state machine uses it, together with the current state to look up the next state. This use of tables results in much better response times than the nested branch statements to input. On the other hand, condition statements must still be evaluated by cycling through all such statements in search of any that evaluates to “true.” This, of course, is still very slow.

[0062] In addition, because of the need to “flatten out” or linearize the original state chart, the size of the table explodes exponentially as a function of the number of possible input events, of depth of the state chart and the width of each branch. Hence, programs generated this way are normally so large as to make the generated code impractical for commercial products.

[0063] In contrast, the code generation technique of the present invention preferably has some or all of the following features:

[0064] It does not try to reproduce the hierarchical state machine in the generated code, but rather generates code that, after compilation and linkage, is run by a pre-built, optimized state machine engine.

[0065] It does not generate a static representation of all possible states and the transitions in the state chart, but rather generates code that reproduces the actual hierarchical state structure of the original state chart. The pre-built state machine engine then dynamically computes the required new state in response to every input event, or change in conditions.

[0066] It is completely event driven, even in the case of conditions. Every source of events and every variable can have a list of logic associated with it. This list points to any statement that must be evaluated if and when that event is triggered or that variable changes value. In general, the statements in the list represent transitions, and the order of the statements expresses the order of evaluation of these transitions. As soon as an input event arrives, or a variable changes value, the transition dependent upon it is immediately identified and evaluated.

[0067] The size of the generated code is linear in the number of branches and the number of transitions between the branches. The size is independent of the width of the branches and the number of possible input events.

[0068] The code generation technique of the present invention and the code structure of the present invention preferably has some or all of the following advantages:

[0069] The resultant generated code, together with the pre-built state machine engine, is very small, and has memory requirements which are comparable to equivalent code developed manually by programmers.

[0070] Whereas response time of the generated code to input events is as good as conventional automatically generated code, the response time to changes in variables is better than that for automatically generated code, and in fact, is similar to that for input events.

[0071] The code generated is guaranteed to reflect the state chart from which it was derived, rather than being a transformed version of it. As a result, the generated code behaves as described by the original state chart. In addition, because of the clarity of the state chart formalism itself, the generated code is more likely to behave as required, compared to the equivalent manually developed code.

[0072] FIG. 3 illustrates incorporation of a system for generating the code shown and described herein into the Rapid S/W tool, commercially available from Emultek Ltd., Misgav 20179, Israel.

[0073] The steps of FIG. 3 are now described:

[0074] Build Interface Library

[0075] The interface library is used by the automatically generated code to interact with the hardware on which the system to be developed runs. For example, the library code may be used to request memory allocation from the operating system, or, if the hardware controls a device such as a lamp, the library might contain the code to switch the lamp on and off, e.g., by accessing certain addresses on the hardware. The library can be written in any convenient language and is preferably pre-tested before development with Rapid begins.

[0076] Map Components to Simulation Objects

[0077] In Rapid, applications are built by assembling simulations of the hardware and/or software components on the screen and building logical expressions from functions supplied with the object simulations. These supplied functions animate the behavior of the object simulations. For example in the case of a Lamp object, the function “switchOn” would cause the simulated lamp on the screen to change to the “on” color. In order for the logical expressions be able to interact with the actual components, a mapping between the supplied functions and interface library is provided. This mapping may be hard coded into the simulated objects code. Alternatively, an external textual mapping file may be used.

[0078] Open a New Rapid Application

[0079] This is the first step in building Rapid applications, providing a “clean slate” on which to build the application.

[0080] Build Simulation of the System

[0081] The simulation is built by dragging objects from a tool palette in the Layout Editor and positioning them as required on the graphic representation of the device being simulated. Each object can be graphically customized and, to some extent, functionally customized.

[0082] Rapid State Charts

[0083] The logic in a Rapid application is described by a state chart. State charts in Rapid are built from units called “modes”. A mode is a functional state of the system and any mode can be hierarchically nested within any other mode. Therefore, the modes describe a hierarchical tree. Modes come in two “flavors”: exclusive and concurrent. For exclusive modes, only one sibling can be in the active state at any given time, while for concurrent modes all siblings must be active together. When a particular mode is active, this implies that all its ancestors are active. If the mode's children are exclusive modes, this also implies that at least one of its children are active, while if the mode's children are concurrent modes, this implies that all of the children are active. A state in a state chart is the list of all currently active modes. A mode can have lists of activities and transitions. Activities describe what the system does when it is a particular state. Activities can be entry activities, exit activities or mode activities. Entry activities are activities that are performed when the mode that contains them becomes activate. Exit activities are activities that are performed when the mode that contains them becomes inactive. Mode activities are activities that are performed when the mode becomes active and that, as long as the mode is still active, are automatically re-evaluated whenever data variables that describe them change value. Transitions define how the system evolves from one state to another. Transitions typically have a destination mode. Transitions must also have a list of input events, or a condition expression or both. Transitions may also have a list of actions. If notification of one of the input events held by a transition is received, and that transition belongs to a currently active mode, and the condition expression, if any evaluates to true, then the mode belonging to the transition is deactivated (together with its children and any relevant ancestors) and the destination mode of the transition is activated (together with its children etc.). Between the deactivation of the original mode and the activation of the destination mode, any actions in the transition are performed.

[0084] Build the State Chart

[0085] The simulation is typically built using two tools in Rapid: the Mode Tree Editor and the Logic Editor. The Mode Tree Editor allows the user to define and add modes to the hierarchical tree of modes by selecting the parent of the new mode, specifying the type of the new mode, and giving a name to the new mode. During this process, the transitions and activities can be added and edited using the Logic Editor. As each logic expression is added to the state chart it is compiled into byte codes for a virtual machine that is used to run a simulation of the system.

[0086] Run Simulation

[0087] At any time during the development process, the simulation of the system under development can preferably be run. This allows incremental development of the system and verification that the system behaves as desired.

[0088] Generate Code

[0089] Once the developer is satisfied with the system, Rapid automatically generates C++ code for that system having the characteristics described above. It is appreciated that programming languages other than C++ may be used for the automatically generated code.

[0090] Compile the Generated Code

[0091] The automatically generated code can be compiled to produce object code.

[0092] Link With State Machine and Interface Library

[0093] The object code produced by compiling the automatically generated code is then linked with the SME object code and the interface library to produce executable code for the target system.

[0094] This executable code can be downloaded and run on the target system.

[0095] Sample Application

[0096] The following is a sample application in Rapid and the code automatically generated for it:

[0097] FIG. 4 is a screen capture of the application in the Layout Editor, showing the object layout.

[0098] As can be seen the application contains five lamps, and five push buttons:

[0099] Objects

[0100] RAPID APPLICATION: TRANSITN 12/12/96 16:09:08

[0101] OBJECT DATA REPORT

[0102] Parameters:

[0103] Scope: Subtree.

[0104] Order: Hierarchy.

[0105] Content: Active objects, Nongraphic objects, Object parameters, Object properties.

[0106] 1. OBJECT: transitn

[0107] Parent: none Type: Root Object

[0108] Parameters:

[0109] Position (pxl): ‘0 @ 0’ Size (pxl): ‘393 @ 403’ Dynamic: ‘false’

[0110] Drag 'n Drop: ‘false’

[0111] 2. OBJECT: LampH

[0112] Parent: transitn Type: Round Lamp

[0113] Parameters:

[0114] Center (pxl): ‘300 @ 139’ Radius (pxl): ‘15 @ 15’ Dynamic: ‘false’

[0115] Drag 'n Drop: ‘false’

[0116] Properties:

[0117] 2.1. Name: blinkPeriod Type: Data

[0118] Parameters:

[0119] Value: 500

[0120] 3. OBJECT: LampG

[0121] Parent: transitn Type: Round Lamp

[0122] Parameters:

[0123] Center (pxl): ‘243 @ 139’ Radius (pxl): ‘15 @ 15’ Dynamic: ‘false’

[0124] Drag 'n Drop: ‘false’

[0125] Properties:

[0126] 3.1. Name: blinkPeriod Type: Data

[0127] Parameters:

[0128] Value: 500

[0129] 4. OBJECT: LampA

[0130] Parent: transitn Type: Round Lamp

[0131] Parameters:

[0132] Center (pxl): ‘72 @ 140’ Radius (pxl): ‘15 @ 15’ Dynamic: ‘false’

[0133] Drag 'n Drop: ‘false’

[0134] Properties:

[0135] 4.1. Name: blinkPeriod Type: Data

[0136] Parameters:

[0137] Value: 500

[0138] 5. OBJECT: LampE

[0139] Parent: transitn Type: Round Lamp

[0140] Parameters:

[0141] Center (pxl): ‘129 @ 139’ Radius (pxl): ‘15 @ 15’ Dynamic: ‘false’

[0142] Drag 'n Drop: ‘false’

[0143] Properties:

[0144] 5.1. Name: blinkPeriod Type: Data

[0145] Parameters:

[0146] Value: 500

[0147] 6. OBJECT: LampF

[0148] Parent: transitn Type: Round Lamp

[0149] Parameters:

[0150] Center (pxl): ‘186 @ 139’ Radius (pxl): ‘15 @ 15’ Dynamic: ‘false’

[0151] Drag 'n Drop: ‘false’

[0152] Properties:

[0153] 6.1. Name: blinkPeriod Type: Data

[0154] Parameters:

[0155] Value: 500

[0156] 7. OBJECT: BToA

[0157] Parent: transitn Type: Flat Pushbutton

[0158] Parameters:

[0159] Position (pxl): ‘57 @ 199’ Size (pxl): ‘40 @ 40’ Dynamic: ‘false’

[0160] Drag 'n Drop: ‘false’ Momentary: ‘true’ Autorepeat: ‘false’

[0161] Autorepeat period: 500

[0162] 8. OBJECT: Default

[0163] Parent: transitn Type: Flat Pushbutton

[0164] Parameters:

[0165] Position (pxl): ‘131 @ 199’ Size (pxl): ‘40 @ 40’ Dynamic: ‘false’

[0166] Drag 'n Drop: ‘false’ Momentary: ‘true’ Autorepeat: ‘false’

[0167] Autorepeat period: 500

[0168] 9. OBJECT: History

[0169] Parent: transitn Type: Flat Pushbutton

[0170] Parameters:

[0171] Position (pxl): ‘206 @ 199’ Size (pxl): ‘40 @ 40’ Dynamic: ‘false’

[0172] Drag 'n Drop: ‘false’ Momentary: ‘true’ Autorepeat: ‘false’

[0173] Autorepeat period: 500

[0174] 10. OBJECT: DeepHistory

[0175] Parent: transitn Type: Flat Pushbutton

[0176] Parameters:

[0177] Position (pxl): ‘276 @ 199’ Size (pxl): ‘40 @ 40’ Dynamic: ‘false’

[0178] Drag 'n Drop: ‘false’ Momentary: ‘true’ Autorepeat: ‘false’

[0179] Autorepeat period: 500

[0180] 11. OBJECT: History

[0181] Parent: transitn Type: Label

[0182] Parameters:

[0183] Position (pxl): ‘198 @ 244’ Size (pxl): ‘58 @ 15’ Dynamic: ‘false’

[0184] Drag 'n Drop: ‘false’ Text: ‘History’ Orientation: ‘Horizontal’

[0185] Font: ‘Fixedsys’ Line width: 1

[0186] 12. OBJECT: Next

[0187] Parent: transitn Type: Flat Pushbutton

[0188] Parameters:

[0189] Position (pxl): ‘167 @ 282’ Size (pxl): ‘40 @ 40’ Dynamic: ‘false’

[0190] Drag 'n Drop: ‘false’ Momentary: ‘true’ Autorepeat: ‘false’

[0191] Autorepeat period: 500

[0192] FIG. 5 is a screen capture of the Mode Tree Editor showing all the modes that make up the state chart of this sample application. As can be seen there are nine modes in this application.

[0193] An alternative view of the state chart can be seen in the screen capture of the Logic Chart tool shown in FIG. 6. FIG. 6 shows each mode as a rectangle and each transition as an arc. The hierarchical nature of the state is clearly seen.

[0194] Reference is now made to FIG. 7 which is a simplified flowchart illustration of a automatic code generation technique operative in accordance with a preferred embodiment of the present invention. The resulting code is useful in conjunction with a state machine engine which performs the following functions, inter alia:

[0195] a. Upon receipt of notification that an input event has occurred, the SME accesses the list formed for that input event and evaluates each transition on that list to determine, depending on the current state, which transitions are to be performed.

[0196] b. Upon receipt of notification that an internal data variable has been changed, the SME accesses the list formed for that internal data variable and evaluates each transition on that list to determine, depending on the current state, which transitions are to be performed.

[0197] To perform a transition, the SME computes the new state associated with the transition by going to the destination of the transition and looking up and activating all ancestors. All children are also looked up and activated as appropriate, e.g. in accordance with predefined defaults. Those portions of the current state that are no longer active in the new state are deactivated. Elements in the new state that were not active in the current state are activated. The new state then becomes the current state and is stored in the SME.

[0198] Alternatively, one or both of the above lists may not be provided. For example, the system may poll periodically for internal events rather than being driven thereby. Alternatively or in addition, the system may poll periodically for external events rather than being driven thereby.

[0199] Logic in State Chart

[0200] RAPID APPLICATION: TRANSITN 12/12/96 16:07:32

[0201] MODE DATA REPORT

[0202] Parameters:

[0203] Scope: Subtree.

[0204] Order: Hierarchy.

[0205] Includes: User Functions, Activities, Transitions, Triggers, Actions.

[0206] USER FUNCTIONS

[0207] 1. MODE: transitn

[0208] Parent: none Type: root

[0209] Note:

[0210] 2. MODE: A

[0211] Parent: transitn Type: exclusive

[0212] Entry Activities:

[0213] a. LampA on

[0214] Exit Activities:

[0215] a. LampA off

[0216] Transitions:

[0217] a. Destination: B Entry type: Default

[0218] a1. Trigger: Default in &

[0219] b. Destination: B Entry type: History

[0220] b1. Trigger: History in &

[0221] c. Destination: B Entry type: Deep history

[0222] c1. Trigger: DeepHistory in &

[0223] 3. MODE: B

[0224] Parent: transitn Type: exclusive

[0225] Transitions:

[0226] a. Destination: A Entry type: Default

[0227] a1. Trigger: BToA in &

[0228] 4. MODE: C

[0229] Parent: B Type: exclusive

[0230] 5. MODE: E

[0231] Parent: C Type: exclusive

[0232] Entry Activities:

[0233] a. LampE on

[0234] Exit Activities:

[0235] a. LampE off

[0236] Transitions:

[0237] a. Destination: F Entry type: Default

[0238] a1. Trigger: Next in &

[0239] 6. MODE: F

[0240] Parent: C Type: exclusive

[0241] Entry Activities:

[0242] a. LampF on

[0243] Exit Activities:

[0244] a. LampF off

[0245] Transitions:

[0246] a. Destination: G Entry type: Default

[0247] a1. Trigger: Next in &

[0248] 7. MODE: D

[0249] Parent: B Type: exclusive

[0250] 8. MODE: G

[0251] Parent: D Type: exclusive

[0252] Entry Activities:

[0253] a. LampG on

[0254] Exit Activities:

[0255] a. LampG off

[0256] Transitions:

[0257] a. Destination: H Entry type: Default

[0258] a1. Trigger: Next in &

[0259] 9. MODE: H

[0260] Parent: D Type: exclusive

[0261] Entry Activities:

[0262] a. LampH on

[0263] Exit Activities:

[0264] a. LampH off

[0265] Transitions:

[0266] a. Destination: E Entry type: Default

[0267] a1. Trigger: Next in &

[0268] Generated Code

[0269] Header File

[0270] #ifndef_include_transitn

[0271] #define_include_transitn

[0272] #include “applic.h”

[0273] #include “task.h”

[0274] #include “object.h”

[0275] #include “mode.h”

[0276] class Application;

[0277] class myApplication;

[0278] typedef bool (myApplication:: *MyApplicationMethod)();

[0279] #define cNumberDependencies 8

[0280] #define cNumberDependencyIndices 6

[0281] #define cNumberChildren 18

[0282] #define cNumberObjects 20

[0283] #define cNumberTriggers 5

[0284] #define cNumberTransitions 8

[0285] #define cNumberModes 9

[0286] #define cNumberActivities 10

[0287] class myApplication: public Application

[0288] {

[0289] private:

[0290] // Objects

[0291] enum objectID

[0292] {

[0293] cOB_RootObject=0,

[0294] //PushButtons

[0295] cOB_Default, //1

[0296] cOB_History, //2

[0297] cOB_DeepHistory, //3

[0298] cOB_BToA, //4

[0299] cOB_Next, //5

[0300] //Lamps

[0301] cOB_LampA, //6

[0302] cOB_LampE, //7

[0303] cOB_LampF, //8

[0304] cOB_LampG, //9

[0305] cOB_LampH, //10

[0306] //Modes

[0307] cOB_RootMode, //11

[0308] cOB_ModeA, //12

[0309] cOB_ModeB, //13

[0310] cOB_ModeC, //14

[0311] cOB_ModeD, //15

[0312] cOB_ModeE, //16

[0313] cOB_ModeF, //17

[0314] cOB_ModeG, //18

[0315] cOB_ModeH //19

[0316] };

[0317] enum modeID

[0318] {

[0319] cMO_RootMode=0,

[0320] cMO_ModeA, //1

[0321] cMO_ModeB, //2

[0322] cMO_ModeC, //3

[0323] cMO_ModeD, //4

[0324] cMO_ModeE, //5

[0325] cMO_ModeF, //6

[0326] cMO_ModeG, //7

[0327] cMO_ModeH, //8

[0328] };

[0329] enum ActivityIndices

[0330] {

[0331] cAC_ModeA_entry,

[0332] cAC_ModeA_exit,

[0333] cAC_ModeE_entry,

[0334] cAC_ModeE_exit,

[0335] cAC_ModeF_entry,

[0336] cAC_ModeF_exit,

[0337] cAC_ModeG_entry,

[0338] cAC_ModeG_exit,

[0339] cAC_ModeH_entry,

[0340] cAC_ModeH_exit,

[0341] };

[0342] enum ConcreteIndices

[0343] {

[0344] eConcrete1=0,

[0345] cConcrete2,

[0346] cConcrete3,

[0347] cConcrete4,

[0348] cConcrete5,

[0349] cConcrete6,

[0350] cConcrete7,

[0351] cConcrete8,

[0352] cConcrete9,

[0353] cConcrete10,

[0354] };

[0355] public:

[0356] void init (RapidTask *t);

[0357] // Objects:

[0358] RootObject rootObject;

[0359] PushButton pbDefault;

[0360] PushButton pbHistory;

[0361] PushButton pbDeepHistory;

[0362] PushButton pbNext;

[0363] PushButton pbBToA;

[0364] RapidLamp LampA;

[0365] RapidLamp LampE;

[0366] RapidLamp LampF;

[0367] RapidLamp LampG;

[0368] RapidLamp LampH;

[0369] // Modes:

[0370] RootMode rootMode;

[0371] XMode ModeA;

[0372] XMode ModeB;

[0373] XMode ModeC;

[0374] XMode ModeD;

[0375] XMode ModeE;

[0376] XMode ModeF;

[0377] XMode ModeG;

[0378] XMode ModeH;

[0379] // Logic Methods:

[0380] bool ModeA_entry();

[0381] bool ModeA_exit();

[0382] bool ModeE_entry();

[0383] bool ModeE_exit();

[0384] bool ModeF_entry();

[0385] bool ModeF_exit();

[0386] bool ModeG_entry();

[0387] bool ModeG_exit();

[0388] bool ModeH_entry();

[0389] bool ModeH_exit();

[0390] // Dynamic State Machine Data:

[0391] RapidObject *FrameTable[cNumberObjects];

[0392] ModeP buffer1[cNumberModes];

[0393] ModeP buffer2[cNumberModes];

[0394] ModeP buffer3[cNumberModes];

[0395] unsigned char_ModeFlags[3*cNumberModes][1];

[0396] // Static State Machine Data:

[0397] // Each object has a list of dependency records, sorted

[0398] // by property and event, and referencing pairs of

[0399] // (modes, activity/condition, index), or a transition index

[0400] static DependencyRecord dependencies[cNumberDependencies];

[0401] // For each object/property pair, there is a dependency index record

[0402] // that includes the first & last dependency record pertaining to the

[0403] // object/property pair.

[0404] static DependencyIndexRecord dependencyIndicies[cNumberDependencyIndices];

[0405] // Each transition has an index and an associated record that includes

[0406] // the indices of the source and destination, type, condition, and action

[0407] static TransitionRecord transitionRecords[cNumberTransitions];

[0408] // Each transition has an index and an associated record that includes

[0409] // the indices of the source and destination, type, condition, and action

[0410] static TriggerRecord triggerRecords[cNumberTriggers];

[0411] // Activity methods are indexed through the following array

[0412] // subroutine methods are NOT indexed here.

[0413] static MyApplicationMethod activityRecords[cNumberActivities];

[0414] // Each mode record includes entry and exit activities, if any,

[0415] // and the start index and length of the mode activities. Can the mode activities

[0416] // be merged? Also, the number of transitions, to facilitate flag allocation.

[0417] static ModeRecord modeRecords[cNumberModes];

[0418] // Each object record includes

[0419] static ObjectRecord objectRecords[cNumberObjects];

[0420] // Array to hold all of the children for the objects

[0421] static int childrenArray[cNumberChildren];

[0422] // General Data on this APplication

[0423] static ApplicationRecord applicationRecord;

[0424] };

[0425] class myTask : public RapidTask

[0426] {

[0427] public:

[0428] myTask();

[0429] ˜myTask()

[0430] {

[0431] removeContext(&_mainApp);

[0432] };

[0433] private:

[0434] myApplication_mainApp;

[0435] };

[0436] #endif

[0437] Body File

[0438] /*

[0439] Rapid Application:

[0440] Objects:

[0441] Transitn

[0442] |-->BToA (Square Pushbutton)

[0443] |-->Default (Square Pushbutton)

[0444] |-->History (Square Pushbutton)

[0445] |-->DeepHistory (Square Pushbutton)

[0446] |-->Next (Square Pushbutton)

[0447] |-->LampA (Round Lamp)

[0448] |-->LampE (Round Lamp)

[0449] |-->LampF (Round Lamp)

[0450] |-->LampG (Round Lamp)

[0451] |-->LampH (Round Lamp)

[0452] Modes:

[0453] Transitn

[0454] |-->A (D)

[0455] |

[0456] |--B

[0457] |-->C(D)

[0458] | |-->E(D)

[0459] | |

[0460] | |--F

[0461] |

[0462] |--D

[0463] |-->G(D)

[0464] |

[0465] |--H

[0466] Logic:

[0467] 1. MODE: Transitn

[0468] Parent: none Type: root

[0469] Note:

[0470] 2. MODE: A

[0471] Parent: Transitn Type: exclusive

[0472] Entry Activities:

[0473] a. LampA on

[0474] Exit Activities:

[0475] a. LampA off

[0476] Transitions:

[0477] a. Destination: B Entry type: Default

[0478] a1. Trigger: Default in &

[0479] b. Destination: B Entry type: History

[0480] b1. Trigger: History in &

[0481] c. Destination: B Entry type: Deep History

[0482] c1. Trigger: DeepHistory in &

[0483] 3. MODE: B

[0484] Parent: Transitn Type: exclusive

[0485] Transitions:

[0486] a. Destination: A Entry type: Default

[0487] a1. Trigger: BToA in &

[0488] 4. MODE: C

[0489] Parent: B Type: exclusive

[0490] 5. MODE: D

[0491] Parent: B Type: exclusive

[0492] 6. MODE: E

[0493] Parent: C Type: exclusive

[0494] Entry Activities:

[0495] a. LampE on

[0496] Exit Activities:

[0497] a. LampE off

[0498] Transitions:

[0499] a. Destination: F Entry type: Default

[0500] a1. Trigger: Next in &

[0501] 6. MODE: F

[0502] Parent: C Type: exclusive

[0503] Entry Activities:

[0504] a. LampF on

[0505] Exit Activities:

[0506] a. LampF off

[0507] Transitions:

[0508] a. Destination: G Entry type: Default

[0509] a1. Trigger: Next in &

[0510] 6. MODE: G

[0511] Parent: D Type: exclusive

[0512] Entry Activities:

[0513] a. LampG on

[0514] Exit Activities:

[0515] a. LampG off

[0516] Transitions:

[0517] a. Destination: H Entry type: Default

[0518] a1. Trigger: Next in &

[0519] 6. MODE: H

[0520] Parent: D Type: exclusive

[0521] Entry Activities:

[0522] a. LampH on

[0523] Exit Activities:

[0524] a. LampH off

[0525] Transitions:

[0526] a. Destination: E Entry type: Default

[0527] a1. Trigger: Next in &

[0528] Generated Code:

[0529] */

[0530] #include “transitn.h”

[0531] #include “emtrace.h”

[0532] #include “ekernel.h”

[0533] /*

[0534] struct DependencyRecord

[0535] {

[0536] DependencyClass dependencyclass; // event, condition, mode activity

[0537] int mode; // Frame Table index

[0538] int eventID; // eventID, if any

[0539] int index; // Index of transition or mode Activity

[0540] };

[0541] */

[0542] DependencyRecord myApplication::dependencies[cNumberDependencies]=

[0543] {

[0544] {cEvent, cOB_ModeA, cPushButtonIn, 0}, // 0 A->B on Default in

[0545] {cEvent, cOB_ModeA, cPushButtonIn, 1}, // 1 A->B on History in

[0546] {cEvent, cOB_ModeA, cPushButtonIn, 2}, // 2 A->B on DeepHistory in

[0547] {cEvent, cOB_ModeB, cPushButtonIn, 0}, // 3 B->A on BToA in

[0548] {cEvent, cOB_ModeE, cPushButtonIn, 0}, // 4 E->F on Next in

[0549] {cEvent, cOB_ModeF, cPushButtonIn, 0}, // 5 F->G on Next in

[0550] {cEvent, cOB_ModeG, cPushButtonIn, 0}, // 6 G->H on Next in

[0551] {cEvent, cOB_ModeH, cPushButtonIn, 0}, // 7 H->E on Next in

[0552] };

[0553] /*

[0554] struct DependencyIndexRecord{

[0555] PropertyEntry_propertyId;

[0556] int flags=0;

[0557] unsigned int_firstElement;

[0558] }

[0559] */

[0560] DependencyIndexRecord myApplication::dependencyIndicies[cNumberDependencyIndices]={

[0561] {cSelf, 0, 0}, // pbDefault self

[0562] {cSelf, 0, 1}, // pbHistory self

[0563] {cSelf, 0, 2}, // pbDeepHistor self

[0564] {cSelf, 0, 3}, // pbBToA self

[0565] {cSelf, 0, 4}, // pbNext self

[0566] {cNone, 0, cNumberDependencies} // Sentinel for last index record

[0567] };

[0568] // children listed grouped by common parent

[0569] int myApplication::childrenArray[cNumberChildren]=

[0570] {

[0571] cOB_Default, // 0

[0572] cOB_History, // 1

[0573] cOB_DeepHistory, // 2

[0574] cOB_BToA, // 3

[0575] cOB_Next, // 4

[0576] //Lamps

[0577] cOB_LampA, // 5

[0578] cOB_LampE, // 6

[0579] cOB_LampF, // 7

[0580] cOB_LampG, // 8

[0581] cOB_LampH, // 9

[0582] //Modes

[0583] cOB_ModeA, // 10

[0584] cOB_ModeB, // 11

[0585] cOB_ModeC, // 12

[0586] cOB_ModeD, // 13

[0587] cOB_ModeE, // 14

[0588] cOB_ModeF, // 15

[0589] cOB_ModeG, // 16

[0590] cOB_ModeH // 17

[0591] };

[0592] /*

[0593] struct ObjectRecord

[0594] {

[0595] ObjectIdentifier name;

[0596] int parent;

[0597] int id; // Id within type . . . e,g, modes are numbered 1-n, concretes are numbered 1-m

[0598] int numChildren;

[0599] int firstChild;

[0600] int firstDependentIndex;

[0601] int numDependentIndex;

[0602] };

[0603] */

[0604] ApplicationRecord myApplication::applicationRecord=

[0605] {

[0606] cNumberModes,

[0607] cNumberActivities

[0608] };

[0609] /*

[0610] struct TriggerRecord

[0611] {

[0612] int objectID;

[0613] int propertyID;

[0614] int eventID;

[0615] };

[0616] */

[0617] // NOTE: Could get sophisticated, and reuse trigger records . . .

[0618] TriggerRecord myApplication::triggerRecords[cNumberTriggers]=

[0619] {

[0620] {cOB_Default, cSelf, cPushButtonIn}, // 0

[0621] {cOB_History, cSelf, cPushButtonIn}, // 1

[0622] {cOB_DeepHistory, cSelf, cPushButtonIn}, // 2

[0623] {cOB_BToA, cSelf, cPushButtonIn}, // 3

[0624] {cOB_Next, cSelf, cPushButtonIn}, // 4

[0625] };

[0626] /*

[0627] struct TransitionRecord

[0628] {

[0629] int triggerStart; // index of first trigger record

[0630] int triggerLength; // number of trigger records

[0631] int sourcemode; // object index of source mode

[0632] int destinationMode; // object index of destination mode

[0633] int condition; // index of condition method

[0634] int action; // index of action method

[0635] unsigned int type:3;

[0636] unsigned int IsConditionOnly: 1;

[0637] unsigned int toAncestor: 1;

[0638] unsigned int toDescendant: 1;

[0639] unsigned int sourceEqualsDestination: 1;

[0640] };

[0641] */

[0642] /*

[0643] struct ModeRecord

[0644] {

[0645] ObjectIdentifier name;

[0646] int defaultChildID; //ObjectID of default child, cNone if none

[0647] // For parents of AndModes, first child

[0648] int entry;

[0649] int exit;

[0650] int modeActivityStart;

[0651] int numModeActivities; // N/A, condition index, activity index

[0652] int transitionStart; // First transition record pertaining to this mode

[0653] int numTransitions; // Number of transitions

[0654] };

[0655] */

[0656] MyApplicationMethod myApplication::activityRecords[cNumberActivities]=

[0657] {

[0658] &myApplication::ModeA_entry,

[0659] &myApplication::ModeA_exit,

[0660] &myApplication::ModeE_entry,

[0661] &myApplication::ModeE_exit,

[0662] &myApplication::ModeF_entry,

[0663] &myApplication::ModeF_exit,

[0664] &myApplication::ModeG_entry,

[0665] &myApplication::ModeG_exit,

[0666] &myApplication::ModeH_entry,

[0667] &myApplication::ModeH_exit,

[0668] };

[0669] bool myApplication::ModeA_entry()

[0670] {

[0671] LampA.turn_on(); // LampA on

[0672] return false;

[0673] }

[0674] bool myApplication: ModeA_exit()

[0675] {

[0676] LampA.turn_off(); // LampA off

[0677] return false;

[0678] }

[0679] bool myApplication::ModeE_entry()

[0680] {

[0681] LampE.turn_on(); // LampA on

[0682] return false;

[0683] }

[0684] bool myApplication::ModeE_exit()

[0685] {

[0686] LampE.turn_off(); // LampA off

[0687] return false;

[0688] }

[0689] bool myApplication::ModeF_entry()

[0690] {

[0691] LampF.turn_on(); // LampA on

[0692] return false;

[0693] }

[0694] bool myApplication::ModeF_exit()

[0695] {

[0696] LampF.turn_off(); // LampA off

[0697] return false;

[0698] }

[0699] bool myApplication::ModeG_entry()

[0700] {

[0701] LampG.turn_on(); // LampA on

[0702] return false;

[0703] }

[0704] bool myApplication::ModeG_exit()

[0705] {

[0706] LampG.turn_off(); // LampA off

[0707] return false;

[0708] }

[0709] bool myApplication::ModeH_entry()

[0710] {

[0711] LampH.turn_on(); // LampA on

[0712] return false;

[0713] }

[0714] bool myApplication::ModeH_exit()

[0715] {

[0716] LampH.turn_off(); // LampA off

[0717] return false;

[0718] }

[0719] void myApplication::init (RapidTask *t)

[0720] {

[0721] setTask(t);

[0722] Application::dependencies=dependencies;

[0723] Application::dependencyIndicies=dependencyIndicies;

[0724] Application::transitionRecords=transitionRecords;

[0725] Application::triggerRecords=triggerRecords;

[0726] Application::activityRecords=(ApplicationMethod *)activityRecords;

[0727] Application::objectRecords=objectRecords;

[0728] Application::modeRecords=modeRecords;

[0729] Application::objects=FrameTable;

[0730] Application::applicationRecord=&applicationRecord;

[0731] Application::children=childrenArray;

[0732] rootObject.init(cOB_RootObject, this);

[0733] pbDefault.init(cOB_Default,this);

[0734] pbHistory.init(cOB_History,this);

[0735] pbDeepHistory.init(cOB_DeepHistory,this);

[0736] pbBToA.init(cOB_BToA,this);

[0737] pbNext.init(cOB_Next,this);

[0738] LampA.init(cOB_LampA,this);

[0739] LampE.init(cOB_LampE,this);

[0740] LampF.init(cOB_LampF,this);

[0741] LampG.init(cOB_LampG,this);

[0742] LampH.init(cOB_LampH,this);

[0743] rootMode.init(cOB_RootMode, this,

[0744] _ModeFlags[(3*cMO_RootMode)],

[0745] _ModeFlags[(3*cMO_RootMode)+1],

[0746] _ModeFlags[(3*cMO_RootMode)+2]);

[0747] ModeA.init (cOB_ModeA, this,

[0748] _ModeFlags[(3*cMO_ModeA)],

[0749] _ModeFlags[(3*cMO_ModeA)+1],

[0750] _ModeFlags[(3*cMO_ModeA)+2]);

[0751] ModeB.init (cOB_ModeB, this,

[0752] _ModeFlags[(3*cMO_ModeB)],

[0753] _ModeFlags[(3*cMO_ModeB)+1],

[0754] _ModeFlags[(3*cMO_ModeB)+2]);

[0755] ModeC.init (cOB_ModeC, this,

[0756] _ModeFlags[(3*cMO_ModeC)],

[0757] _ModeFlags[(3*cMO_ModeC)+1],

[0758] _ModeFlags[(3*cMO_ModeC)+2]);

[0759] ModeD.init (cOB_ModeD, this,

[0760] _ModeFlags[(3*cMO_ModeD)],

[0761] _ModeFlags[(3*cMO_ModeD)+1],

[0762] _ModeFlags[(3*cMO_ModeD)+2]);

[0763] ModeE.init (cOB_ModeE, this,

[0764] _ModeFlags[(3*cMO_ModeE)],

[0765] _ModeFlags[(3*cMO_ModeE)+1],

[0766] _ModeFlags[(3*cMO_ModeE)+2]);

[0767] ModeF.init (cOB_ModeF, this,

[0768] _ModeFlags[(3*cMO_ModeF)],

[0769] _ModeFlags[(3*cMO_ModeF)+1],

[0770] _ModeFlags[(3*cMO_ModeF)+2]);

[0771] ModeG.init (cOB_ModeG, this,

[0772] _ModeFlags[(3*cMO_ModeG)],

[0773] _ModeFlags[(3*cMO_ModeG)+1],

[0774] _ModeFlags[(3*cMO_ModeG)+2]);

[0775] ModeH.init (cOB_ModeH, this,

[0776] _ModeFlags[(3*cMO_ModeH)],

[0777] _ModeFlags[(3*cMO_ModeH)+1],

[0778] _ModeFlags[(3*cMO_ModeH)+2]);

[0779] rootMode.initActiveChild();

[0780] ModeA.initActiveChild();

[0781] ModeB.initActiveChild();

[0782] ModeC.initActiveChild();

[0783] ModeD.initActiveChild();

[0784] ModeE.initActiveChild();

[0785] ModeF.initActiveChild();

[0786] ModeG.initActiveChild();

[0787] ModeH.initActiveChild();

[0788] _currentState.init(buffer1,cNumberModes);

[0789] _nextState.init(buffer2,cNumberModes);

[0790] _tempState.init(buffer3,cNumberModes);

[0791] Application::rootMode=&rootMode;

[0792] Application::rootObject=&rootObject;

[0793] }

[0794] myTask::myTask()

[0795] {

[0796] _mainApp.init(this);

[0797] setMainApplication(&_mainApp);

[0798] setupKernelTask (this);

[0799] };

[0800] // declare one task

[0801] myTask GlobalTask;

[0802] It is appreciated that the software components of the present invention may, if desired, be implemented in ROM (read-only memory) form. The software components may, generally, be implemented in hardware, if desired, using conventional techniques.

[0803] It is appreciated that various features of the invention which are, for clarity, described in the contexts of separate embodiments may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment may also be provided separately or in any suitable subcombination.

[0804] It will be appreciated by persons skilled in the art that the present invention is not limited to what has been particularly shown and described hereinabove. Rather, the scope of the present invention is defined only by the claims that follow: