Products & Services Solutions Academia Support User Community Company

Learn more about SimEvents   

Version 2.4 (R2009a) SimEvents Software

This table summarizes what's new in Version 2.4 (R2009a):

New Features and ChangesVersion Compatibility ConsiderationsFixed Bugs and Known ProblemsRelated Documentation at Web Site
Yes
Details below		Yes
Summary		Bug Reports
Includes fixes		No

New features and changes introduced in this version are described here:

Debugger Supports Stepping, Breakpoints, and Querying

The new SimEvents debugger lets you use MATLAB functions to suspend a simulation at each step or breakpoint, and query simulation state to assess behavior. The debugger includes these functions:

helpDisplay help for debugger functions
se_getdboptsSimEvents debugger options structure
sedb.bdeleteDelete breakpoints in discrete-event simulation
sedb.blkinfoBlock information in discrete-event simulation
sedb.blklistBlocks and their identifiers in discrete-event simulation
sedb.breakpointsList breakpoints in discrete-event simulation
sedb.contContinue simulation until next breakpoint
sedb.currentopCurrent operation in discrete-event simulation
sedb.detailCustomize debugger display in discrete-event simulation
sedb.disableDisable breakpoints in discrete-event simulation
sedb.enableEnable breakpoints in discrete-event simulation
sedb.eninfoEntity information in discrete-event simulation
sedb.evbreakSet breakpoint for execution or cancelation of event
sedb.evcalEvent calendar of discrete-event simulation
sedb.evinfoEvent information in discrete-event simulation
sedb.gcebName of currently executing block in discrete-event simulation
sedb.gcebidIdentifier of currently executing block in discrete-event simulation
sedb.gcenIdentifier of entity currently undergoing operation
sedb.gcevIdentifier of current event
sedb.quitQuit discrete-event simulation debugging session
sedb.runtoendRun until end of discrete-event simulation
sedb.simtimeCurrent time in discrete-event simulation
sedb.stepSingle step in discrete-event simulation
sedb.tbreakSet timed breakpoint in discrete-event simulation
sedebugDebug discrete-event simulation

For more information, see these resources:

Event Logging Options Removed from Configuration Parameters Dialog Box

The SimEvents pane of the Configuration Parameters dialog box no longer contains event logging options. The behavior of the event logging options in earlier versions is like the behavior of the new debugger.

Compatibility Considerations

The debugger behavior produces slightly different information, with a different format, compared to the information produced by the event logging parameters. The closest approximations to the previous behavior use the detail and runtoend functions of the debugger.

Event Logging Parameter RemovedSimilar Behavior in Debugger
Display events in event calendar

  1. At the MATLAB command prompt, start the debugger on the model called model:

    sedebug(model)

  2. At the sedebug>> prompt, configure the debugger and run the simulation until the end:

    detail none
detail('ev',1,'cal',1)
runtoend
Log events when executed

  1. At the MATLAB command prompt, start the debugger on the model called model:

    sedebug(model)

  2. At the sedebug>> prompt, configure the debugger and run the simulation until the end:

    detail none
detail('ev',1)
runtoend

The resulting log includes both execution messages and scheduling messages. Execution messages are not indented; scheduling messages are indented.

Log events when scheduled
Log entities advancing from block to block

  1. At the MATLAB command prompt, start the debugger on the model called model:

    sedebug(model)

  2. At the sedebug>> prompt, configure the debugger and run the simulation until the end:

    detail none
detail('en',1)
runtoend

The resulting log includes entity advancement messages and other information. Entity advancement messages appear indented.

To approximate the behavior that results from setting multiple parameters for the same model, you can concatenate input arguments in the detail(...) command. For example, detail('ev',1,'en',1) is like logging event scheduling, event execution, and entity operations.

Discrete Event Signal to Workspace Block Clarifies Timing

You can no longer place the Discrete Event Signal to Workspace block in an atomic subsystem. The atomic subsystem executes at time instants that conflict with the time instants at which the event-based block in the subsystem executes. In earlier versions, placing the Discrete Event Signal to Workspace block in an atomic subsystem can produce unexpected results. Function-Call Subsystem and Enabled Subsystem are examples of atomic subsystems.

Compatibility Considerations

If your legacy model includes a Discrete Event Signal to Workspace block in an atomic subsystem, update the model as follows:

  1. Move the Discrete Event Signal to Workspace block outside the atomic subsystem.

  2. Connect the block to an output signal from the subsystem.

  

Version 3.0 (R2009b) SimEvents SoftwareVersion 3.0 (R2009b) SimEvents Software Version 2.3 (R2008b) SimEvents SoftwareVersion 2.3 (R2008b) SimEvents Software

Related Products & Applications

Get Simulink trial software

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.

Get this Simulink Kit

 © 1984-2009- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS