INCHRON - think real-time

Did you know that trace files with detailed timing information can help validate critical timing requirements such as CPU load, task slack time, and end-to-end latency of event chains? At INCHRON, we believe timing and performance should be evaluated regularly – ideally with every software release. With modern CI/CD workflows, many customers generate trace files automatically as part of their development processes. Using chronVIEW, these trace files can be automatically analyzed within your CI/CD pipelines. To support this, INCHRON provides both Linux and Windows versions of its chronSUITE that can also be used in batch/CLI mode for seamless automation. But you don’t need to do all this yourself. Thanks to your ECU Performance Monitoring service, INCHRON’s experts can analyze your trace files and deliver detailed reports with recommendations for improvements that ensure your system always operates optimally. Let’s elevate your system performance together! #TimingAnalysis #PerformanceOptimization #EmbeddedSystems #CI/CD #chronSUITE

The average load of each CPU in an automotive ECU can be an indicator of pending problems. That’s why it’s necessary to regularly check these values during software development. This allows issues to be detected early and addressed before they become larger problems during software integration. An overview of the ECU under different scenarios is a great starting point and can be implemented using traffic lights on a dashboard. During team meetings, the current status in terms of timing and dynamic behavior is thus available at a glance. Such metrics are available through INCHRON’s ECU Performance Analysis service, regularly delivering metrics in detail, allowing developers to perform an in-depth analysis. Trends can also be monitored over several software versions using this approach by reviewing the delta changes. All of this integrates seamlessly in your existing automated CI/CD workflow. A REST API is also available. If keeping tabs on CPU load in your ECU sounds beneficial, reach out to us here on LinkedIn or via our website.

Why are operational design domains (ODD) critical for autonomous vehicles? And how do they relate to ISO 21448? While students can build a vehicle that drives around a track autonomously, the complexity grows enormously as real life is added to the task. For example, how should the vehicle behave when it is raining? Or, when it is in a tunnel, can all of its sensors be relied upon in the same manner as when in free space? Then, there is bright sunlight that could stop reliable image delivery from cameras. And how should driving through roadworks be handled? ODD breaks down a function, like autonomous driving, into operating conditions that are described by factors such as time of day, geography, environment, and traffic and roadway characteristics. Should the operating conditions not fall into one of the ODDs, control of the vehicle has to pass back to the driver. Some examples of Level 3 autonomous driving deployments in operation today follow this ODD approach. ISO 21448 provides guidance on the suitable design of such systems and how they should be verified and validated. Of course, changing between these different ODDs changes the code execution and the chain of events from sensors through processors to actuators. It could be necessary for the vehicle to operate in different modes, depending on the current ODD. Development teams need to ensure that response times remain within prescribed limits in all cases. INCHRON’s team and their chronSUITE tools help simulate and model such systems, providing timing tests that sit alongside the functional tests once the hardware is available. If you’d like to learn more about getting automotive software timing challenges under control, we’d be happy to hear from you.

Why are operational design domains (ODD) critical for autonomous vehicles? And how do they relate to ISO 21448? While students can build a vehicle that drives around a track autonomously, the complexity grows enormously as real life is added to the task. For example, how should the vehicle behave when it is raining? Or, when it is in a tunnel, can all of its sensors be relied upon in the same manner as when in free space? Then, there is bright sunlight that could stop reliable image delivery from cameras. And how should driving through roadworks be handled? ODD breaks down a function, like autonomous driving, into operating conditions that are described by factors such as time of day, geography, environment, and traffic and roadway characteristics. Should the operating conditions not fall into one of the ODDs, control of the vehicle has to pass back to the driver. Some examples of Level 3 autonomous driving deployments in operation today follow this ODD approach. ISO 21448 provides guidance on the suitable design of such systems and how they should be verified and validated. Of course, changing between these different ODDs changes the code execution and the chain of events from sensors through processors to actuators. It could be necessary for the vehicle to operate in different modes, depending on the current ODD. Development teams need to ensure that response times remain within prescribed limits in all cases. INCHRON’s team and their chronSUITE tools help simulate and model such systems, providing timing tests that sit alongside the functional tests once the hardware is available. If you’d like to learn more about getting automotive software timing challenges under control, we’d be happy to hear from you.

We are proud to see how INCHRON continues to inspire and empower the next generation of engineers! Recently, our team had the opportunity to share our expertise at the Technische Hochschule Nürnberg Georg Simon Ohm , where students explored the cutting-edge challenges of automotive system design. Through hands-on exercises with our chronSUITE tool, they learned how to optimize real-time systems and ensure critical requirements like timing, safety, and reliability. Thanks to Prof. Friedhelm Stappert and the students for the great collaboration. Together, we’re driving innovation and inspiring the next generation of engineers!

EDAG Group and INCHRON - think real-time are joining forces! We are thrilled to announce our partnership with EDAG Group to tackle the challenges of latency and timing in Software-Defined Vehicles (SDV). Our combined strengths: -         EDAG: Comprehensive know-how in EE architecture and vehicle development -         INCHRON: Industry-leading expertise in timing simulation and event- chain analysis Our approach involves timing simulation at three stages during project development: -         Early Design Validation: Defining realistic event-chain timing requirements that suppliers can reliably meet. -         Simulation using field data from test vehicles to ensure event-chain timing requirements are met and identifying corrective actions if deviations occur. -         Data-Driven Decision Making: Enabling smarter design choices through insights based on event chain engineering. Together, we are committed to ensuring that every real-time function – from braking systems to advanced driver-assistance features – operates reliably and efficiently. By achieving precise timing, we offer a critical tool to manage the growing complexity in vehicle development and set new standards for system integrity in the automotive industry. The partnership was celebrated in the photo, from right to left: Andreas Hecker, Vice President E/E Systems Engineering at EDAG, and Dr. Ralf Münzenberger, CEO and co-founder of INCHRON. Let’s drive the future of safe, connected, and efficient vehicles! #INCHRON #EDAG #AutomotiveEngineering #TimingExcellence #SDV #SoftwareFirst #Collaboration

Team Inspiration Day: Exploring Teufelsberg and Berlin’s Culinary Scene At INCHRON AG, we love drawing inspiration from unexpected places – and our recent Christmas trip to Berlin's Teufelsberg was no exception! This historic Cold War listening station was once a hub for espionage, where intelligence agencies intercepted global communications. Today, it’s a fascinating mix of history, urban art, and nature. Walking through the graffiti-covered towers and learning about the site’s secretive past gave us a lot to reflect on – from the importance of communication to the value of adapting in a changing world. To wrap up the day, we enjoyed fantastic food in a cozy, modern setting – the perfect way to spark some great team discussions. Exploring Berlin reminded us how history and creativity can inspire fresh ideas. Where do you find inspiration?

Why was the invention of accurate chronometers so important for naval ships? Seafaring anywhere was a treacherous undertaking until well into the 17th Century. Latitude, a north-south position, could be determined relatively accurately using the sun or other celestial bodies. But longitude, the east-west position, was calculated using dead reckoning. Crude methods for determining speed, coupled with the direction offered by a compass, led to little more than a guess in many cases. As a result, ships would get lost for weeks or even strike an island’s rocks in bad visibility despite being only a few miles from their intended destination. A considerable challenge is that longitude distance varies with latitude. One degree is sixty-eight miles at the Equator but drops to zero at the Earth’s poles. Using time, a difference of one hour between the time at your starting point and your current location, as indicated by the sun’s zenith, indicates 15 degrees of longitude at any latitude. Thus, it follows that an accurate watch, or chronometer, would benefit sailors greatly. Many governments offered prizes to anyone who could build an accurate seafaring chronometer to solve this issue. The British Parliament offered £20,000, equivalent to £5.5m today, to the person who could build such a timepiece. The eventual winner was the carpenter and clock-maker John Harrison. His work determined a method for temperature compensation and that circular balances could cancel out the impact of a ship’s motion. He also realized that a pocket watch could be as accurate as a larger timepiece, as demonstrated by his H4 chronometer. During trials, it enabled a longitude calculation with an error of fewer than ten miles between Greenwich, England, and Bridgetown, Barbados. Harrison’s chronometer for naval navigation took many decades to establish itself, competing with the cost of the devices and an alternative – the use of lunar tables. However, by the early 19th Century, barely anyone would consider setting to sea without one.

ACC24: Innovation in Focus We’re excited to see our colleague Dr. Ralf Münzenberger share his key takeaways from this year’s ACC24. The event was a fantastic platform for exchanging ideas, exploring solutions for Software-Defined Vehicles (SDVs), and diving into technical challenges. Key insights included the importance of a multidisciplinary approach, systems engineering with “shift-left,” and the courage to embrace innovation. A big thank you to everyone who made ACC24 such an inspiring event. Let’s continue shaping the future together!

Thank you @Arm, for welcoming us into your global partner ecosystem! As a member of the Arm Partner Program, we're able to showcase our solutions, collaborate with experts, and scale our efforts for a better future built #onArm. https://lnkd.in/ei-TFHsv