Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Polarsys » Capella workbench » Data Bus Interface Definition and Instantiation(How to create a data bus structure and instantiate multiple times)
Data Bus Interface Definition and Instantiation [message #1820969] Mon, 03 February 2020 16:50 Go to next message
Kevin Heaton is currently offline Kevin HeatonFriend
Messages: 2
Registered: February 2020
Junior Member
Hi Everyone,

Having defined the functional and logical interfaces between my System of Interest and the interfacing systems, I am now trying to define the Exchange Item Elements.

My system interfaces with an external system via an ARINC 429 data bus. All messages on the data bus are constructed of the following parameters, each of which has some properties e.g. Least Significant Bit (LSB), Most Significant Bit (MSB) etc.:


  • Label
  • SDI
  • Payload
  • SSM
  • Parity


I am expecting to be able to define this structure only once and then instantiate it as many times as required to define the complete set of messages (which thankfully is only 3 in this instance).

I have created a Capella Library element of the data bus structure (See "Data Bus Structure" attachment)

I have then incorporated it into my system model, defined the three messages as Exchange Items and related them through Exchange Item Elements (See "Data Bus Instantiation" attachment).

I have also related the Exchange Items to each of the associated Function Exchanges (See "Allocated Exchange Elements" attachment.

However, I don't know how to instantiate the data bus properties for each message (Exchange Item). You may see in the "Data Bus Instantiation" attachment that I have used Literal Numeric Values to define the label properties, but I can't find a way to associate them with associated Exchange Item.


Am I going about this the right way and just missing something or have I gone completely in the wrong directly?

Any advise would be greatly appreciated.

Re: Data Bus Interface Definition and Instantiation [message #1821162 is a reply to message #1820969] Thu, 06 February 2020 12:46 Go to previous messageGo to next message
Jakub Mazur is currently offline Jakub MazurFriend
Messages: 4
Registered: February 2020
Junior Member
Hi Kevin,

perhaps constraint (where you can provide your class element as owned specification) added to every exchange item element (belonging to given exchange item) would work for you.

index.php/fa/37306/0/

[Updated on: Thu, 06 February 2020 15:01]

Report message to a moderator

Re: Data Bus Interface Definition and Instantiation [message #1821274 is a reply to message #1821162] Mon, 10 February 2020 08:31 Go to previous messageGo to next message
Kevin Heaton is currently offline Kevin HeatonFriend
Messages: 2
Registered: February 2020
Junior Member
Hi Jakub,

Thanks for the response.

This could work for now and I will have to see how I get on before I can provide any more insightful feedback.

I'm still in the early stages of learning Capella and I'm still trying to figure out precisely what it is I'm trying to get out of it and so it is quite the iterative process.

Thanks again!
Re: Data Bus Interface Definition and Instantiation [message #1821412 is a reply to message #1821274] Wed, 12 February 2020 17:19 Go to previous message
Navas Juan is currently offline Navas JuanFriend
Messages: 49
Registered: January 2020
Member
Hello,

Just my 2 cents: you can define Data Values as well, and refer to them in the Owned Specification of the constraint. This way, if you have several constraints that refer to the same value, and this value changes, you will only need to change it in one place.

index.php/fa/37353/0/
  • Attachment: Capture.PNG
    (Size: 32.21KB, Downloaded 376 times)
Previous Topic:csv exports
Next Topic:sub functions allocation
Goto Forum:
  


Current Time: Thu Nov 07 01:28:01 GMT 2024

Powered by FUDForum. Page generated in 0.04063 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top