Explanation of Accelerator mode and listener functions

I am writing a report on work that I have been doing using Simulink and matlab working together at the same time.Recently I read a comment suggesting that adding an event listener to a block when Simulink runs in accelerator mode will not work.

I would assume that this is because the function for adding an event listener is written in C++ but i can not find anything to confirm if this is true.

Does anyone have any information they can point me towards plese ?

Thanks

[Kaustubha Govind]

I don't see this in the documentation. Could you point out to the page where you read this comment?

Answer 1

[Abhishek Gupte]

Yes, event-listeners do not work in non-Normal simulation modes.

Event-listener functions are fired when the block methods that they are attached to ( eg. 'PostOutputs' ), are called. The API used is the block's Run-Time-Object (RTO). In a nutshell, an RTO is a Simulink block's proxy in MATLAB.

In Accelerator mode, a mex file of the model is generated. Instead of calling individual block methods, the corresponding block's mex counterpart is called. The API used to communicate between the mex function and the Simulink environment is called the C-Mex S-function API. This is shown here.

Since the block's methods are not directly executed, the block's RTO does not exist in Accel ( and all other non-Normal ) modes. Hence, the event listeners are never fired.

There is no workaround for this.