Modbus Server Event Trigger

This block triggers a Simulink Function-Call subsystem after Modbus Client has accessed a register within a set of registers in Modbus Server Function Definition block.

Block ID

Library

Woodward Custom Modbus

Description

More then one trigger may be placed in a model raising the same event.
Execution Order parameter can be used to order these multiple triggers.

Block Parameters

Parameter Field	Values	Comments/Description
Trigger Name	Alpha-numeric text, quote enclosed	Set the text that will be appended to code generated function name. This is useful when using a difference tool to compare the difference from one build to another. If this is left as an empty cell the appended value will be generated at build time, and can change from build to build.
Event	Drop-down list	The event to trigger on.
Reference Function Definition Name	Alpha-numeric text, quote enclosed	Associates this trigger with Modbus Server Function Definition.
Execution Order within Task	Numeric (Integer)	More than one trigger may be placed in a model that is driven by the same event. Use the Execution Order within Task attribute to define the execution order of these triggers relative to one another. The triggers will execute from the lowest value to the highest. Only triggers with the same Trigger Tasking Priority will be guaranteed to execute in the defined order.
This trigger is inside another triggered subsystem	Checkbox	Enable if trigger is inside another triggered subsystem. Trigger attempts to simulate the block inside of another triggered rate. The trigger from this block may occur in bursts, synchronized to the outer rate, while simulating, but will perform as expected on the target. Do not enable on top-level triggers, otherwise the block will not simulate at all.
Trigger even when containing subsystem is disabled	Checkbox	If this trigger is used inside of a containing subsystem, normally the triggered subsystem will pause and resume based on the enable/disable status of the containing subsystem. Checking this causes triggers to occur even while the parent is disabled. Note that this feature will not simulate, but will execute correctly on the target.
Trigger even when Application Monitor pauses or stops	Checkbox	When checked this trigger will fire even when the Application Monitor indicates that execution is paused or stopped. Note that this feature will not simulate, but will execute correctly on the target.
User Task Name	Alpha-numeric text, quote enclosed	The name of the task where this trigger will execute. The task must exist elsewhere in the model.