RTaW-TraceInspector Brochure

•

0 recomendaciones•474 vistas

RTaW-TraceInspector is a tool to visualize and analyze network communication traces that extracts the actual traffic characteristics from the traces and automatically diagnose possible deadline violations, departures from the specifications and other abnormal behaviors.

Tecnología

RTaW-TraceInspector - Version 2014
How RTaW-TraceInspector will
help you increase timing verification
coverage?
Extract actual traffic characteristics from
the traces — frames transmission patterns
can be complex with jitters, offsets, event-
triggered frames, segmented messages,
code upload, diagnostic requests, transmis-
sion errors, etc – in practice, there is in
many cases a gap between the “ideal” traf-
fic model considered at design-time and the
real traffic that can be observed on the bus-
es, RTaW-TraceInspector provides you with
the actual traffic characteristics,
OEMs: reduce system integration risks —
RTaW-TraceInspector checks whether the
stations behave according to their specifi-
cations – if not re-playing performance eval-
uation studies with the actual characteris-
tics using RTaW-Sim enables you to know in
advance the impacts of non-conformance,
Suppliers: ensure your ECUs meet their
specifications — make sure and provide evi-
dence that your ECUs behave as expected,
Identify abnormal timing behaviors and lo-
cate their cause — Communication networks
often do not behave at run-time as expect-
ed for instance because of sub-optimal im-
plementation choices or shortcomings in
the communication stack, because station
clocks are drifting apart or simply because
of the latencies induced by the scheduling
of the tasks that produce the data – RTaW-
TraceInspector enables you to quickly de-
tect, diagnose, and resolve network timing
performance problems.
Best value for money — tired of over-paying
for CAN timing verification tool? RTaW-Tra-
ceInspector is several times less expensive
than competitors’ solutions, but don’t take
our word for it, Contact the product man-
ager for a free fully functional evaluation
version and just compare!
Automated trace-based timing verification
RTaW-TraceInspector is a
tool to visualize and analyze
network communication trac-
es that extracts the actual
traffic characteristics from
the traces and automati-
cally diagnose possible dead-
line violations, departures
from the specifications and
other abnormal behaviors.
RTaW-TraceInspector

KEY FEATURES
• Support CAN2.0A, CAN2.0B and
ARINC825 networks,
• Determine the characteristics of
the traffic monitored by statisti-
cal analysis of the communication
traces: bus load, frame period,
priority, jitters, size, offsets, bit-
stuffing, etc,
• Automatically detect abnormal be-
haviors or departures from the
specifications: wrong frame char-
acteristic, priority inversions with-
in sending nodes, unknown mode
changes, wrong inter-frame space,
abnormal transmission error rate
or clock drifts, unknown frames,
etc,
• Powerful visualization environment
with Gantt charts to inspect the
traces,
• Convert trace analysis
results into models of
periodic traffic, event-
triggered traffic and
transmission errors that
can be directly re-used for simu-
lation in RTaW-Sim or for worst-
case schedulability analysis in
NETCAR-Analyzer,
• Import traces from most network
analyzers – import filters will be
developed free of charge if your
tracing tool is not supported yet,
• Runs on all 32 or 64 bit platforms
supporting Java – no dongle or li-
cense server protection,
• Can be extended with your own
features through a plug-in infra-
structure,
• Professional support and custom
extensions available.
We help designers build truly safe and optimized systems
Software homepage at
http//www.realtimeatwork.com/software/rtaw-traceinspector/

Más contenido relacionado

Más de RealTime-at-Work (RTaW)

TTEthernet (TTE) is considered for use as high-speed backbone in the avionics of next-generation orbital space launchers. Given the key role of communication in launchers, the OEM must acquire a precise understanding of TTE’s functioning and its performances in nominal and error conditions. This holds especially true for the clock synchronization algorithm, the cornerstone of time-triggered communication in TTE, which involves complex distributed algorithms. In this study, we use both an experimental platform and fault-injection on a simulation model to gain quantified insights in these questions. We first describe a fine-grained simulation model of TTE model and discuss how it has been validated against communication traces recorded on the TTE platform. We then present experiments that evaluate the accuracy of the clock synchronization in TTE in the fault-free case as well as considering permanent link failure and transient transmission errors. Finally, we discuss what we have learned during the project in terms of development process and programming language support for complex simulation models used in the design of critical systems.

Simulation-Based Fault Injection as a Verification Oracle for the Engineering...

RealTime-at-Work (RTaW)

Autonomous driving requires safety considerations and the need of “fail operational” requires redundancy. In the networking portion of a car, this may mean separate networks, possibly of different technologies. Or it could mean a network topology and technology that supports scalable redundancy, like Ethernet TSN. This presentation focuses on IEEE 802.1CB-2017, which is the TSN standard that supports data redundancy through the network. Various network topologies are examined. The relative costs of adding TSN redundancy for these topologies (including some, or all of, the end-stations/ECUs & bridges) are examined for various bandwidth utilizations, along with the expected packet loss. Each topology and bandwidth will be modeled under various bit-rate error values with the results discussed. This presentation aims at providing a clear understanding of the TSN standards that support redundancy, and an understanding of the cost/benefit tradeoffs so proper engineering decisions can be made and proper expectations set.

Practical Use Cases for Ethernet Redundancy

RealTime-at-Work (RTaW)

Typical design goals of next generation architectures are future extensibility and cost optimization of the lowest-end. We propose to introduce guidance to an otherwise standard Monte-Carlo simulation by providing certain fixed points (e.g., mandated connections of ECUs to certain bridges, complete re-use of ECUs) and “hot spots” in the topology (e.g., ECUs with the highest variability pressure) that are known in advance from BMW’s experience with their vehicles in the field. Several important practical considerations must be integrated in the generation of candidate architectures: - Topological constraints: ECU proximity to sensors, daisy chain connections between ECUs to minimize cable length, number of switch ports in a certain ECU, etc. - Security and reliability requirements: segregation between mixed-criticality streams, proxy ECUs, and redundant paths. Our position statement explores the ability of algorithmic tools to synthesize Ethernet-based architectures based on a minimal fixed core TSN topology, design goals, design constraints, assumptions about next generation applications and data from past projects (capturing part of the OEM domain knowledge).

Towards Computer-Aided, Iterative TSN-and Ethernet-based E/E Architecture Design

RealTime-at-Work (RTaW)

There has been a pivotal change in the design of E/E architectures, which is that we cannot assume anymore that the functions, and thus the communication requirements, are known in advance and fixed over time. It has become crucial for OEMs to be in the position to add further functions / services during the lifetime of the vehicle: OEMs need to design E/E architectures that are future-proof. We show how design space exploration, by answering a series of design questions and proposing solutions to the designers, helps to improve an automotive E/E architecture in several dimensions. We start by estimating the total "capacity" of a baseline architecture, then, by removing bottlenecks, we obtain an "enhanced capacity" architecture. The architecture is then further optimized in terms of costs and reliability. The work is conducted on Volvo's prototype centralized E/E and domain-based E/E architectures.

Early-stage Bottleneck Identification and Removal in TSN Networks

RealTime-at-Work (RTaW)

A main issue in the design of automotive communication architectures is that the most important design choices pertaining to the topology of the networks and the technologies to use (protocols, data rate, hardware) have to be made at a time when the communication requirements are not entirely known. Indeed, many functions only becomes available along the development cycle, and vehicle platforms have to support incremental evolutions of the embedded system that may not be fully foreseeable at the time design choices are made. The problem is becoming even more difficult and crucial with the introduction of dynamically evolving communication requirements requiring network re-configuration at run-time. We present how the use of synthetic data, that is data generated programmatically based on past vehicle projects and what can be foreseen for the current project, enables the designers to make such early stage choices based on quantified metrics. The proposals are applied to Groupe Renault's FACE service-oriented E/E architecture with the use of the “Topology Stress Test” feature implemented in RTaW-Pegase.

Early-stage topological and technological choices for TSN-based communication...

RealTime-at-Work (RTaW)

The idea of using TCP in cars has been around for some time, as the first specification of Autosar TCP/IP stack dates back from early 2013. However, TCP has not been popular yet in cars and there has not been much published works on using TCP for in-vehicle communications so far. TCP – the Transmission Control Protocol – provides connection-oriented reliable transmission between network applications. TCP is the cornerstone of the Internet – a hugely successful protocol over the last 40 years – if it is certainly a fine piece of engineering but it is definitely a complex one. The question we explore in this study is what can we expect from TCP for on-board in-vehicle communication in terms of latencies & throughput and how to best configure TCP in a context for which it has not been conceived. In particular, we will show that TCP configuration on the ECU sides should consider the amount of memory available in the switches and that traffic shaping policy, as available in TSN, can provide a nice performance boost for TCP communication.

Insights into the performance and configuration of TCP in Automotive Ethernet...

RealTime-at-Work (RTaW)

Switched Ethernet is profoundly reshaping in-car communications. To meet the diverse real-time requirements in automotive communications, Quality-of-Service protocols that go beyond the mere use of priorities are required. In this work, the basic questions that we investigate on a case-study with diverse and demanding communication requirements is what can we expect from the various protocols aimed at providing a better timing Quality of Service on top of Ethernet? And how to use them? Especially how to use them in a combined manner. We will focus on the Credit-Based Shaper of AVB, the Time-Aware Shaper of TSN and the use of priorities as defined in IEEE802.1Q. The performance metrics considered are the distributions of the communication latencies, obtained by simulation, as well as upper bounds on these quantities obtained by worst-case schedulability analysis. If there have been over the last 5 years numerous studies on the performance of AVB CBS, the literature on comparing AVB to TSN and other candidate protocols is still sparse. To the best of our knowledge, this empirical study is the first to consider most protocols currently considered in the automotive domain, with the aim to gain insights into the different technological, design and configurations alternatives. In particular, an objective of this study is to identify key problems that need to be solved in order to further automate network design and configuration.

Insights on the Performance and Configuration of AVB and TSN in Automotive Ap...

RealTime-at-Work (RTaW)

Switched Ethernet is a technology that is profoundly reshaping automotive communication architectures as it did in other application domains such as avionics with the use of AFDX backbones. Early stage timing verification of critical embedded networks typically relies on simulation and worst-case schedulability analysis. When the modeling power of schedulability analysis is not sufficient, there are typically two options: either make pessimistic assumptions or ignore what cannot be modeled. Both options are unsatisfactory because they are either inefficient in terms of resource usage or potentially unsafe. To overcome those issues, we believe it is a good practice to use simulation models, which can be more realistic, along with schedulability analysis. The two basic questions that we aim to study here is what can we expect from simulation, and how to use it properly? This empirical study explores these questions on realistic case-studies and provides methodological guidelines for the use of simulation in the design of switched Ethernet networks. A broader objective of the study is to compare the outcomes of schedulability analyses and simulation, and conclude about the scope of usability of simulation in the desi gn of critical Ethernet networks

Timing verification of real-time automotive Ethernet networks: what can we ex...

RealTime-at-Work (RTaW)

Scalable Service-Oriented Middleware on IP (SOME/IP) is a proposal aimed at providing service-oriented communication in vehicles. SOME/IP nodes are able to dynamically discover and subscribe to available services through the SOME/IP Service Discovery protocol (SOME/IP SD). In this context, a key performance criterion to achieve the required responsiveness is the subscription latency that is the time it takes for a client to subscribe to a service. In this paper we provide a recap of SOME/SD and list a number of assumptions based on what we can foresee about the use of SOME/IP in the automotive domain. Then, we identify the factors having an effect on the subscription latency, and, by sensitivity analysis, quantify their importance regarding the worst-case service subscription latency. The analysis and experiments in this study provide practical insights into how to best configure SOME/IP SD protocol.

Insights on the Configuration and Performances of SOME/IP Service Discovery

RealTime-at-Work (RTaW)

Slides of a paper at ERTSS'2014 co-authored by Nicolas NAVET (University of Luxembourg), Shehnaz LOUVART (Renault), Jose VILLANUEVA (Renault), Sergio CAMPOY-MARTINEZ (Renault) and Jörn MIGGE (RealTime-at-Work). Early stage timing verification on CAN traditionally relies on simulation and schedulability analysis, also known as worst-case response time (WCRT) analysis. Despite recent progresses, the latter technique remains pessimistic especially in complex networking architectures with gateways and heterogeneous communication stacks. Indeed, there are practical cases where no exact WCRT analysis is available, and merely upper bounds on the response times can be derived, on the basis of which unnecessary conservative design choices may be made. Simulation, on the other hand, does not provide anyguarantees per se and, in the context of critical networks, should only be used along with an adequate methodology. In this paper, we argue for the use of quantiles of the response time distribution as performance metrics providing an adjustable trade-off between safety and resource usage optimization. We discuss how the exact value of the quantile to consider should be chosen with regard to the criticality of the frames, and illustrate the approach on two typical automotive use-cases.

Timing verification of automotive communication architecture using quantile ...

RealTime-at-Work (RTaW)

There is today more than 20 years of experience in automotive CAN applications, and CAN has certainly proven very successful as a robust, cost effective and all-around network technology. But the use of CAN in vehicles is evolving, in particular because of more complex and heterogeneous architectures with FlexRay or Ethernet networks, and because of recent needs like hybrid, electric propulsion or driver assistance that involves more stringent real-time constraints. Besides, there are other new requirements on CAN: more fine-grained ECU mode management for energy savings, multi-ECU splitted functions and huge software downloads. In parallel, safety issues request more and more mechanisms to protect against potential failures and provide end-to-end integrity. The development process is also evolving with the advent of multi-domain cooperation, Autosar, ISO2626-2 and the always shorter time-to-market requirements. In this landscape, CAN has now to be used at much higher bus load level than in the past, and there is less margin for error. What does it imply in terms of verification and validation? What are the characteristics of the communication stacks that should be paid attention to? This article is intended to shed some light and share our views on these issues.

CAN in Automotive Applications: a Look Forward

RealTime-at-Work (RTaW)

PEGASE – a robust and efficient tool for worst-case network traversal time ev...

RealTime-at-Work (RTaW)

Automotive embedded systems now include numerous software-intensive functions that are critical from a safety point of view (e.g., braking, assisted driving, etc). These functions are distributed on the Electronic Control Units and they need to exchange large amount of data with real-time constraints. In this context, the communication system plays a major role and it has to respect stringent dependability constraints. Security, especially with the widespread of wireless networks, is now becoming a serious matter of concern too. In this talk, we will review the main threats to dependability and security in automotive communication systems, the existing technical solutions to attain them, and, highlight areas where developments might be needed.

Automotive communication systems: from dependability to security

RealTime-at-Work (RTaW)

This presentation focus on advances on Model Based System Engineering that fUML [1] brings. fUML, better known has Executable UML, provide a formalization of a subset of UML. UML, and with some extensions and adaptations SysML, can now be analysed in a formal way. That was main grief made by researchers. First part of the presentation illustrates what is now possible by picking ideas from existing tools, notably Alloy [1] and OWL [3]. Following this path will enlighten what still must be done from researchers. It also points out how UML/SysML editors and tools can be enhanced. Indeed in current tools you can modelize activities that are not executable, you can describe Class/Block that cannot be instantiated, and so on. The second part is about current implementation of previous ideas. It starts with a panorama of tools that can be combined, reused or adapted for the new desired features. For instance, it is possible to generate random instances of a model. Doing so helps to be confident in the model constraints. Moreover details will be given on how Topcased ease or not the integration of such a tool in its suite. For instance, it will be shown how Acceleo and ATL are used, but further details will also be given on how it integrates deeply with Topcased Editors for warnings, quick-fixes and so on.

What fUML can bring to MBSE?

RealTime-at-Work (RTaW)

As the demand for computing power is quickly increasing in the automotive domain, car manufactur-ers and tier-one suppliers are gradually introducing mul-ticore ECUs in their electronic architectures. Additionally, these multicore ECUs offer new features such as higher levels of parallelism which eases the respect of the safety requirements introduced by the ISO 26262 and can be taken advantage of in various other automotive use-cases. These new features involve also more complexity in the design, development and verification of the software applications. Hence, OEMs and suppliers will require new tools and methodologies for deployment and validation. In this paper, we present the main use cases for multicore ECUs and then focus on one of them. Pre- cisely, we address the problem of scheduling numerous elementary software components (called runnables) on a limited set of identical cores. In the context of an automotive design, we assume the use of the static task partitioning scheme which provides simplicity and better predictability for the ECU designers by comparison with a global scheduling approach. We show how the global scheduling problem can be addressed as two sub- problems: partitioning the set of runnables and building the schedule on each core. At that point, we prove that each of the sub-problems cannot be solved optimally due to their algorithmic complexity. We then present low complexity heuristics to partition and build a schedule of the runnable set on each core before discussing schedulability verification methods. Finally, we assess the performance of our approach on realistic case-studies.

Multicore scheduling in automotive ECUs

RealTime-at-Work (RTaW)

This talk is about temporal verification in real-time communication systems. Early in the design cycle, the two main approaches for verifying timing constraints and dimensioning the networks are worst-case schedulability analysis and simulation. The aim of the talk is to demonstrate that both provide complementary results and that, most often, none of them alone is sufficient. In particular, it will be shown that response time distributions that can be derived from simulations cannot replace worst-case analysis. This will be done on automotive case-studies using RTaW analysis and simulation software tools.

Frame latency evaluation: when simulation and analysis alone are not enough

RealTime-at-Work (RTaW)

Virtualization in Automotive Embedded Systems: an Outlook

RealTime-at-Work (RTaW)

Prototypage virtuel à partir de SysML

RealTime-at-Work (RTaW)

Slides of a talk given at the Workshop on Specialized Networks held in Conjunction with ETFA 2009. The use of networks for communications between the Electronic Control Units (ECU) of a vehicle in production cars dates from the beginning of the 90s. The specific requirements of the different car domains have led to the development of a large number of automotive networks such as LIN, J1850, CAN, FlexRay, MOST, etc.. This talk first introduces the context of in-vehicle embedded systems and, in particular, the requirements imposed on the communication systems. Then, we highlight future trends in the development of automotive communication systems.

In‐Vehicle Networking: a Survey and Look Forward

RealTime-at-Work (RTaW)

AUTOSAR OS est amené à devenir le nouveau standard pour les systèmes d’exploitation d’exploitation dans l’embarqué automobile, Un des objectifs premiers du projet AUTOSAR est de permettre à des applications provenant de différentes sources de s’exécuter sur un même calculateur. Ce document fait un tour d'horizon des mécanismes de protection, par exemple protection mémoire et temporelle, qui permettent à des applications multi-sources de s'exécuter sur un même calculateur avec une sûreté de fonctionnement importante. Slides d'une conférence donnée au salon RTS'2009 à Paris.

Mécanismes de protection AUTOSAR OS

RealTime-at-Work (RTaW)

Más de RealTime-at-Work (RTaW) (20)