About 433,000 results
Open links in new tab
  1. DataReceivedEventAUTOSAR 0.4.0 documentation

    DataReceivedEvent Factory Methods Attributes Event ExclusiveArea InitEvent ModeSwitchEvent OperationInvokedEvent RunnableEntity SwcInternalBehavior TimingEvent Component Constant DataType Element Mode Workspace Package Port PortInterface

  2. Configure AUTOSAR Runnables and Events - MathWorks

    The component configures an event to activate each runnable – for example, a timing event, data received, a client request, a mode change, component startup or shutdown, or a trigger. In Simulink ®, you can configure these types of AUTOSAR events.

  3. autosar - WaitPoint and Event - Stack Overflow

    Mar 21, 2016 · An Event in AUTOSAR has two different meanings regarding software components. Either it triggers a RunnableEntity or it resolves a WaitPoint. If a RunnableEntity is triggered e.g. by a DataReceivedEvent the Rte will activate your RunnableEntity and then you can call Rte_Read () to read the data.

    Missing:

    • Data

    Must include:

  4. AUTOSAR Component Behavior - MathWorks

    The component configures an event to activate each runnable – for example, a timing event, data received, a client request, a mode change, component startup or shutdown, or a trigger. Runnables can be interconnected using AUTOSAR inter-runnable variables (IRVs).

  5. Programmatically Configure AUTOSAR Runnables and Events

    This example shows how to programmatically configure AUTOSAR runnables and events. This examples uses example model autosar_swc_expfcns using the autosar.api.getAUTOSARProperties and autosar.api.getSimulinkMapping objects and functions.

  6. Overview of Events - AutosarToday

    An event is a trigger to an action, which in Autosar, is usually a runnable, that defines (part of) the internal behavior of a component.

  7. Configure AUTOSAR Runnables and Events - MATLAB

    The component configures an event to activate each runnable – for example, a timing event, data received, a client request, a mode change, component startup or shutdown, or a trigger.

  8. DataReceivedEvent — AUTOSAR 0.3.9 documentation

    DataReceivedEvent Factory Methods Attributes Event ExclusiveArea InitEvent ModeSwitchEvent OperationInvokedEvent RunnableEntity SwcInternalBehavior TimingEvent Component Constant DataType Element Mode Workspace Package Port PortInterface

  9. Autosar Software Component - Stack Overflow

    Mar 11, 2016 · Especially the loop to wait for new data is busy waiting meaning that it could block the whole ECU. For this you should use DataReceivedEvents or configure a blocking Rte_Receive (Rte will wait via WaitEvent () instead of busy waiting).

    Missing:

    • Event

    Must include:

  10. Configure AUTOSAR Sender-Receiver Communication

    In AUTOSAR sender-receiver communication between software components, the Runtime Environment (RTE) raises a DataReceiveErrorEvent when the communication layer reports an error in data reception by the receiver component.

  11. Some results have been removed