|
Re: rtBound signal is not shown in message list [message #1763943 is a reply to message #1763923] |
Tue, 23 May 2017 09:07 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Peter Cigehn![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=peter.cigehn%40gmail.com) Messages: 49 Registered: September 2014 |
Member |
|
|
Hi,
How did you create your model? Did you use the "UML-RT for C++" template when creating the model? Or is this an existing model that was not based on this (or any other) template?
If so, have you set the default action language of the model to "C++"? You can do that in the properties view on the root element of the model, in the UML-RT sub-tab "Language". When you have done this, then the UML-RT run-time model library (UMLRT-RTS) library is being loaded and makes the rtBound and rtUnbound protocol messages available for selection when creating a trigger.
Keep in mind also that the "Is Notfication" property needs to be enabled on the port to ensure that the rtBound and rtUnbound notifications are generated for that specific port during run-time.
And finally, although this might be obvious, keep also in mind that SAP ports based on system protocols from the run-time model library, e.g. Log, Timing, Frame, does not have the rtBound and rtUnbound (and neither can you set the "Is Notification" property), since system ports are by definition always bound. So for these types of ports you will never see rtBound and rtUnbound protocol messages when creating a trigger (which in practice only is made for the timeout protocol message for Timing ports).
Hope this helps,
/Peter Cigéhn
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02776 seconds