Integrations (PTC products, 3rd party products and code) > Code integration (Ada, ARINC 653, C, C#, C++, IDL, Java, SQL and VB) > ARINC 653 for PikeOS 653 code > ARINC 653 for PikeOS 653 profile items > Port usage (ARINC for PikeOS code)
  
Port usage (ARINC for PikeOS code)
A Port Usage is not an ARINC item, but on the Configuration Diagram's toolbar there is a Port Usage button that creates a UML Association between an Application Part and a Port on a Configuration Diagram. When generated, a Port Usage results in an APEX queuing port or APEX sampling port being generated.
A Port Usage link between an Application Part and a Port results in that port being created in the application startup code that is generated for the Application Part.
/* Header File */
#include <apex_queuingports.h>
...
extern QUEUING_PORT_ID_TYPE QueuingPort1_id;

/* Implementation File */
QUEUING_PORT_ID_TYPE QueuingPort1_id;
...
CREATE_QUEUING_PORT("QueuingPort1", 256, 32, SOURCE, FIFO, &QueuingPort1_id, &rc);
ASSERT(rc == NO_ERROR); ASSERT(rc == NO_ERROR);
To define port usage on a Configuration Diagram: click the Port Usage toolbar button, and the click the following items:
• An Application Part , and then a Source Queuing Port or Source Sampling Port on the Application Part's parent Partition Part.
• A Destination Queuing Port or Destination Sampling Port on a Partition Part, and then an Application Part within that Partition Part.
When shown on a Configuration Diagram a Port Usage's (Association's) notation is as follows:
A Port Usage is a UML Association.
The following sections provide information about how a Port Usage is used in the model.
Shown on these diagrams
Configuration Diagram
ARINC properties
None.