Eclipse Community Forums: Newcomers » Protocol message specifications

Home » Newcomers » Newcomers » Protocol message specifications(Can a protocol assigned to external port contain both external and relay messages)

Show: Today's Messages :: Show Polls :: Message Navigator

Protocol message specifications [message #1797514]

Thu, 01 November 2018 01:57

Dimo Ditchev

Messages: 33
Registered: September 2018

Member

As Ernesto Posse explains in "PapyrusRT Modelling and Code Generation" there are certain limitations in the implementation.

"A port in the outer boundary of a capsule can be connected to an internal
part, in which case it is called a relay port, as it simply relays messages to and
from the internal part. A boundary port not connected to an internal part is
called an external port, and messages arriving there are handled by the capsule's state machine. Similarly, it is through external ports that the capsule's state machine can send messages outside. Non-boundary ports are called internal, and are used by the capsule's state machine to communicate with the capsule's internal parts."

I want to understand if I can design a protocol that contains both external messages that determine the state machine in he capsule and then also messages that are relayed to internal sub-states that may have sub-state machine, or do I need to have separate protocols for external messages and internal messages relayed to sub-states (and eventually sub-state machines).

Report message to a moderator

Re: Protocol message specifications [message #1797515 is a reply to message #1797514]

Thu, 01 November 2018 02:42

Charles Rivet

Messages: 219
Registered: May 2014
Location: Canada

Senior Member

Hi Dimo,

What you describe is a concept that was often requested in legacy tooling: the concept of a cable the can contain multiple connectors, each with their own protocol. It was discussed as a potential addition to the language, but it was never assigned to an MVP - mostly a matter of prioritization where parity with legacy tooling was primordial.

However, you could define a protocol that would do what you want by, for example, have a "forward" property that would specify on which port the message would be forwarded. This means that, on reception, it would process this (or these) elements to be forwarded to their final destination. You may still have to handle synchronisation in some way, as the semantics of the state machines will still process one message, to completion, at the time.

/Charles Rivet

Report message to a moderator

Re: Protocol message specifications [message #1797547 is a reply to message #1797515]

Thu, 01 November 2018 16:15

Dimo Ditchev

Messages: 33
Registered: September 2018

Member

Charles,

Thank you for the quick response and the clarification.

Report message to a moderator

Re: Protocol message specifications [message #1797562 is a reply to message #1797547]

Thu, 01 November 2018 17:56

Charles Rivet

Messages: 219
Registered: May 2014
Location: Canada

Senior Member

You're welcome,

By the way, Papyrus for Real Time has its own forum where you have a better chance of interacting with the Papyrus-RT experts out there. Not every one 06 them monitors the newcomers (this) forum.

/Charles Rivet

Report message to a moderator

Previous Topic:	Displaying full Hierarchical State Diagram
Next Topic:	Photon update problem

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Apr 24 23:37:57 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter