search

RobotML / RobotML-SDK

RobotML-SDK is an implementation of the Robot Modeling language. It is based upon Papyrus modeling tool (http://www.papyrus.org) which is itself based upon Eclipse framework (http://www.eclipse.org).
2 stars 1 forks source link

Orocos and deployment plan #152

Closed patinusb closed 10 years ago

patinusb commented 11 years ago

orocos should use deployment plan. This is linked and details Issue #8

SelmaKchir commented 11 years ago

In the AirOARP model, the motion controller component is allocated to Orocos. In I understood well, motion controller is a hardware component. Other components, for instance Obc should be allocated to Orocos.

SelmaKchir commented 11 years ago

screenshot at 2013-10-28 15 06 06

Farges commented 11 years ago

I have different allocation links. Are you using the model at https://github.com/RobotML/RobotML-SDK/blob/master/robotml-kepler/dsl-papyrus/robotml/org.eclipse.papyrus.robotml.templaterepository/resource/AirOARP.di ?

Farges commented 11 years ago

In https://github.com/RobotML/RobotML-SDK/blob/master/robotml-kepler/dsl-papyrus/robotml/org.eclipse.papyrus.robotml.templaterepository/resource/AirOARP.uml#L720 :

m_motion is _5M6LwDvzEeOv9Pb7uiE8Hg

In https://github.com/RobotML/RobotML-SDK/blob/master/robotml-kepler/dsl-papyrus/robotml/org.eclipse.papyrus.robotml.templaterepository/resource/AirOARP.uml#L734 :

_5M6LwDvzEeOv9Pb7uiE8Hg is allocated to morse.

sdhouib commented 11 years ago

This is the deployment plan. Allocation links are created with reference to this deployment plan: screenshot049

SelmaKchir commented 10 years ago

I wasn't using the right deployment plan, problem fixed. Thank you.