ASCET Links: Addressable Objects

The following objects can be addressed via ASCET links:

• folders

• ASCET components

  • projects
  • modules
  • AUTOSAR software components and interfaces
  • classes (including state machines, Boolean tables, conditional tables)
  • CT blocks
  • records
  • enumerations
  • signals

• model elements

  • messages
  • variables
  • parameters
  • constants and system constants
  • arrays and matrices
  • characteristic lines and maps
  • resources
  • complex elements (i.e. included components)

  • AUTOSAR elements (inter-runnable variable, mode group, etc.)

  Note
  The basic <target object> for these elements is /element=<element name>.

• interface elements

  • methods (including triggers, actions and conditions in state machines)
  • processes
  • runnables and server runnables

  • method signatures in ClientServer interfaces

    Note
    Basic <target object> for methods (including method signatures), processes, runnables: /diagram=<diagram name>/signature=<method\process\runnable name>

  • method elements (argument, return value, method-local variable)
  • process-local variables
  • runnable-local variables, arguments of server runnables

  • method signature elements (argument, return value)

    Note
    Basic <target object> for elements of methods (including method signatures), processes, runnables: /diagram=<diagram name>/signature=<method\process\runnable name>/element=<element name>

• diagrams

  Note
  The basic <target object> for a diagram is /diagram=<diagram name>.

• implementations and datasets of components/projects

  Note
  Implementation sets of components/projects are accessed via a basic <target object> plus context information: /element=self&action=editImplementation[/implementation=<implementation set name>] Data sets of components/projects are accessed via a basic <target object> plus context information: /element=self&action=editData[/data=<data set name>]

• in block diagrams: graphical objects

  • occurrences of model elements
  • literals
  • operators
  • control-flow elements
  • graphical hierarchies
  • statement blocks
  • sequence calls and connectors with sequence number > 0
  • connection lines
  • comments
  • process/method/runnable ports

  Note
  The basic <target object> for these elements is /goid=<n>. The number <n> of a graphical element is given in the status bar of the editor, provided Mouse Over Info is activated in the Editors node of the ASCET options window. In addition, you can open hierarchies and statement blocks via /diagram=<diagram name>/hierarchy="<1st-level hierarchy name>"[/hierarchy="<lower-level hierarchy name>"]

• in state machines: state machine elements and state/transition editors

  • states
  • junctions

  • transitions

    Note
    The basic <target object> for states, junctions and transitions is /goid=<n>. The number <n> of a state, junction, or transition is given in the status bar of the editor, provided Mouse Over Info is activated in the Editors node of the ASCET options window.

  • in-/outputs

    Note
    The basic <target object> for in-/outputs is /element=<in/output name>.

  • triggers
  • conditions

  • actions

    Note
    The basic <target object> for triggers, conditions, and actions is /diagram=<diagram name>/signature=<trigger\condition\action name>.

  • Entry, Static and Exit tabs (state editor)

    Note
    Basic <target object> for a tab in the state editor: /diagram=<diagram name>/goid=<state ID>/state=<state name>

  • Action and Condition tabs (transition editor)

    Note
    Basic <target object> for a tab in the transition editor: /diagram=<diagram name>/goid=<transition ID>/transition=<tab name>

  • ESDL code of actions/conditions

    Note
    Basic <target object> for a tab in the transition editor: /diagram=<diagram name>/goid=<transition ID>/transition=<tab name>/start=<i>@<j>/end=<k>@<l>

• in ESDL and C code components: code parts, external C and H code (C code components only)

  Note
  Basic <target object> for a part of ESDL or C code: /diagram=<diagram name>/signature=<method/process name>/start=<i>@<j>/end=<k>@<l>

  Note

  Basic <target object> and necessary context information for external C code without project context: /codeSource=externalCode[/start=<i>@<j>/end=<k>@<l>]&implementation=<implementation>&target=<target>&generator=<arithmetic> Basic <target object> and necessary context information for external header code without project context: /codeSource=externalHeader[/start=<i>@<j>/end=<k>@<l>]&implementation=<implementation>&target=<target>&generator=<arithmetic> Basic <target object> and necessary context information for external object code without project context: /codeSource=externalCode&implementation=<implementation>&target=<target>&generator=<arithmetic> Basic <target object> and necessary context information for external C code or object code with project context: /codeSource=externalCode[/start=<i>@<j>/end=<k>@<l>]&implementation=<implementation set>&data=<dataset>&target=<target><code generator>&generator=&project=<project> Basic <target object> and necessary context information for external header code with project context: /codeSource=externalHeader[/start=<i>@<j>/end=<k>@<l>]&implementation=<implementation set>&data=<dataset>&target=<target>&generator=<code generator>&project=<project>

• in Boolean tables and conditional tables: table cells

  Note
  The basic <target object> for a cell in a Boolean or conditional table is /x=<column nr>/y=<row nr>.

• in AUTOSAR SWC: events and mappings

  Note
  The basic <target object> for events is /event=<event name>.

  event= may remain empty. In that case, the link opens the appropriate SWC editor in the Event Specification view.

  Note

  Basic <target object> for an AUTOSAR mapping: /mapping=<mapping tab name>/sourceName=<ASCET element name>to select the source of a mapping /mapping=<mapping tab name>/targetName=<AUTOSAR element name>to select the target of a mapping You can provide both /sourceName=<ASCET element name> and /targetName=<AUTOSAR element name> to select the entire mapping. If you provide neither /sourceName nor /targetName, the mapping tab opens, but no mapping is selected. An empty /targetName= selects all unmapped entries in the mapping table. An empty /sourceName= produces an error.

• objects in projects

  • tasks

    Note
    The basic <target object> for tasks is /task=<task name>.

    task= may remain empty. In that case, the link opens the project editor in the "OS" tab of the Specification view.

  • formulas

    Note
    The basic <target object> for formulas is /formula=<formula name>.

  • implementation types

    Note
    The basic <target object> for implementation types is /impltype=<impl.type name>.

  • project properties nodes

    Note
    The basic <target object> for a node in the Project Properties window is /option=<node path> e.g., Project Properties\Build for the Build node.

    For EHOOKS projects only:

  • bypass functions

    Note
    The basic <target object> for bypass functions is /scheduling=<bypass function name>.

  • mappings

    Note

    The basic <target object> for an EHOOKS mapping is /mapping=<mapping tab name>/sourceName=<ASCET message name> or /mapping=<mapping tab name>/targetName=<ECU variable name>. You can provide both /sourceName=<ASCET message name> and /targetName=<ECU variable name> to select the entire mapping. If you provide neither /sourceName nor /targetName, the mapping tab opens, but no mapping is selected. An empty /targetName= selects all unmapped entries in the mapping table. An empty /sourceName= produces an error.

See also

ASCET Links

ASCET Links: Examples