Signal input ports of SimEvents® blocks fall into these categories:
Notifying ports, which notify the preceding block when a certain event has occurred
Monitoring ports, which help you observe signal values
Reactive ports, which listen for updates or changes in the input signal and cause an appropriate reaction in the block possessing the port
The distinctions are relevant when you use the Event-Based Random Number or Event-Based Sequence block. For details, see these topics:
Notifying ports, listed in the table below, notify the preceding block when a certain event has occurred. When the preceding block is the Event-Based Random Number or Event-Based Sequence block, it responds to the notification by generating a new output value. Other blocks ignore the notification.
List of Notifying Ports
|Signal Input Port||Block||Generate New Output Value Upon|
|Set Attribute||Entity arrival|
|in||Signal Latch||Write event|
|e1, e2||Entity Departure Function-Call Generator||Entity arrival|
|Signal-Based Function-Call Generator||Relevant signal-based event, depending on configuration of block|
|t||Signal-Based Function-Call Generator||Relevant signal-based event, depending on configuration of block|
|t||Infinite Server||Entity arrival|
|Single Server||Entity arrival|
|t||Time-Based Entity Generator||Simulation start and subsequent entity departures|
|ti||Schedule Timeout||Entity arrival|
|x||X-Y Signal Scope||Sample time hit at in signal input port|
Monitoring ports, listed in the table below, help you observe signal values. Optionally, you can use a branch line to connect the Event-Based Random Number or Event-Based Sequence block to one or more monitoring ports. These connections do not cause the block to generate a new output, but merely enable you to observe the signal.
List of Monitoring Ports
|Signal Input Port||Block|
|Unlabeled||Discrete Event Signal to Workspace|
|X-Y Signal Scope|
|ts, tr, vc||Instantaneous Event Counting Scope|
|Unlabeled||Event to Timed Signal|
Reactive ports, listed in the table below, listen for relevant updates in the input signal and cause an appropriate reaction in the block possessing the port. For example, the p port on a switch listens for changes in the input signal; the block reacts by selecting a new switch port.
List of Reactive Ports
|Signal Input Port||Block||Relevant Update|
|en||Enabled Gate||Value change from nonpositive to positive, and vice versa|
|p||Input Switch||Value change|
|ts, tr, vc||Entity Departure Counter|
|Event-Based Entity Generator|
|Signal-Based Function-Call Generator|
|Signal-Based Function-Call Event Generator|
|wts, wtr, wvc, rts, rtr, rvc||Signal Latch|
|Unlabeled input port||Event Filter|
Depends on block parameter values. Choices are:
|Unlabeled input port||Initial Value||Sample time hit|
For triggers and value changes, "appropriate" refers to the direction you specify in a Type of change in signal value or Trigger type parameter in the block's dialog box.
To connect an event-based signal generator to a reactive port, you must use a workaround because you cannot connect the Event-Based Random Number block directly to a reactive input port of a SimEvents block or indirectly, via a single-input-single-output (SISO) block that supports event-based input signals. Instead, insert a Set Attribute block between the Event-Based Random Number block and a reactive port. For an example, see Invalid Connection of Event-Based Random Number Generator.