Vasco Dias

From single-core to multicore — but you don’t have to start from scratch. 🚗⚙️ In automotive embedded systems, the shift to multicore is inevitable. But with safety-critical legacy code and real-time constraints, migrating from single-core isn’t just plug-and-play. That’s where our AUTOSAR expertise comes in. We contributed to the introduction of multicore into AUTOSAR with release 4.0.1 in 2009 and simultaneously developed the ETAS RTA-CAR BSW stack: a robust, field-proven solution that fully supports any customer use case. Built by engineers, for engineers —RTA-CAR at a glance: 🔧 Compact & efficient - Optimized for resource-constrained, low-latency real-time environments. 🛡️ Safety & security - Complies with industry standards like ISO26262 and ISO/SAE21434, along with MISRA-C & CERT-C guidelines. 🛠️ Versatile compatibility - Suitable for all ECU types, from smart sensors to vehicle computers, and adaptable for single and multi-OEM projects. ⚡Wide device support - Compatible with various target devices and integrates seamlessly with third-party MCALs and security solutions. 🚀 Proven success - Deployed on over 4 billion ECUs globally. We’ve summed up more exclusive insights and real-world cases to help you navigate the transition in a white paper. Download it now: https://brnw.ch/21wSQG3 #YourAmbitionIsOurMission #AUTOSARClassic

53

Today, Webasto Portugal (WBS) partnered with the Portuguese Institute of Blood and Transplantation (IPST) to host a community blood donation campaign, utilizing a mobile unit that visited their premises. The initiative invited participation from all WBS employees and staff from other companies within the building, which mobilized several donors and contributed to helping restore IPST blood reserves. 💪 ❤️

55

Two Initiatives, One Goal: Stronger Processes and Stronger Skills At KIRCHHOFF Automotive Portugal, we recently completed two training initiatives that support this direction. The Digital Design Tools Training enabled the Hardware team to align workflows, unify tool structures and strengthen shared best practices. This creates transparency, reduces redundant work and increases efficiency in our industrialization processes. In parallel our Production colleagues completed a Welding Process Technology Training - combining theoretical insights with practical application to deepen technical expertise. Both initiatives reflect a clear leadership principle: Building strong capabilities within our teams creates long‑term stability and performance. #KIRCHHOFFAutomotive #MakingMobilitySafe #DigitalTransformation

14

I had the opportunity to test GLIWA T1 4.0 recently. Thanks to Cristian Garzón and Germano Brunacci for the oportunity. GLIWA T1 4.0 is not “new.” It’s just less friction. And that matters. And honestly: it’s hard to improve an already great tool without just adding noise. This feels like the opposite, same fundamentals, fewer steps, faster loops. What stood out in my quick test: - Overall it feels faster (less waiting, quicker iterations) - A new page that puts the key information in one place, no more tab switching between cont / scope / … just to keep context - A very practical one: T1.flex across all functions at once, no more manual work selecting each function, starting measurements, repeating the same setup cycle Why this matters in real projects: timing/resource closure isn’t blocked by “lack of data”, it’s blocked by workflow friction. Reducing manual steps increases cadence and makes it easier to keep integration disciplined. What’s your biggest time sink today in timing analysis: setup/selection, running measurements, or turning results into decisions?

24

1 comentário

Why is the CAN Protocol Essential in Automotive Engineering? In modern vehicles, seamless communication between hundreds of Electronic Control Units (ECUs) is critical. That’s where the Controller Area Network (CAN) protocol comes in. Originally developed by Bosch, the CAN protocol allows microcontrollers and devices to communicate with each other without a host computer, making it ideal for real-time, robust, and efficient communication across vehicle systems. Why is CAN so vital? Reliability: It ensures fault-tolerant data transmission, even in harsh environments. Efficiency: Reduces wiring complexity, minimizing vehicle weight and cost. Real-Time Performance: Crucial for time-sensitive operations like engine control, braking, and airbag deployment. Scalability: Easily integrates new ECUs and features without overhauling the entire system. As vehicles become smarter and more connected, the CAN protocol remains a cornerstone of in-vehicle communication, paving the way for future mobility innovations. #AutomotiveEngineering #CANProtocol #VehicleNetworking #MobilityTech #EngineeringInnovation

168

1 comentário

You're starting a job in the software team at Shapeways. You'd expect to be diving into the code, right? Not so fast. When new engineers join Tiago São José's team at Shapeways, they don’t start by writing code. Instead, they spend a day in production — packing boxes, shipping orders and using the tools they’ll be developing. Because developing the best software comes from understanding how its used in the real world, and knowing the people who use it. ▶️ In this clip, Tiago explains why empathy is at the heart of engineering. See the full video on our blog: https://lnkd.in/e_QZQKC8

40

3 comentários

In automotive EE, I used to think “𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲” was a single blueprint. Then I realized ; it’s not one architecture. It’s 𝘁𝘄𝗲𝗹𝘃𝗲. Each one answers a different 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻. Each one has its own constraints, tools, and failure modes. When they drift apart, the system breaks down ; not visibly at first, but quietly, deeply, and expensively. Esteemed colleagues Here’s the full stack we now treat as standard in EE system design: 1. 𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 🧠 𝘞𝘩𝘢𝘵 𝘴𝘩𝘰𝘶𝘭𝘥 𝘵𝘩𝘦 𝘷𝘦𝘩𝘪𝘤𝘭𝘦 𝘥𝘰? Defines the system’s intent at feature level , no hardware yet. Just behavior. 2. 𝗟𝗼𝗴𝗶𝗰𝗮𝗹 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 🔌 𝘏𝘰𝘸 𝘢𝘳𝘦 𝘣𝘦𝘩𝘢𝘷𝘪𝘰𝘳𝘴 𝘣𝘳𝘰𝘬𝘦𝘯 𝘪𝘯𝘵𝘰 𝘣𝘭𝘰𝘤𝘬𝘴? Structures the logic: what talks to what, through what signal or state. 3. 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 📦 𝘞𝘩𝘦𝘳𝘦 𝘥𝘰𝘦𝘴 𝘦𝘢𝘤𝘩 𝘭𝘰𝘨𝘪𝘤𝘢𝘭 𝘣𝘭𝘰𝘤𝘬 𝘭𝘪𝘷𝘦? Maps functions to ECUs, sensors, and actuators. 4. 𝗣𝗵𝘆𝘀𝗶𝗰𝗮𝗹 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 🧱 𝘞𝘩𝘦𝘳𝘦 𝘪𝘴 𝘦𝘷𝘦𝘳𝘺𝘵𝘩𝘪𝘯𝘨 𝘭𝘰𝘤𝘢𝘵𝘦𝘥? Real-world layout: harness routing, grounding zones, zone distribution. 5. 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 🧬 𝘏𝘰𝘸 𝘪𝘴 𝘤𝘰𝘥𝘦 𝘰𝘳𝘨𝘢𝘯𝘪𝘻𝘦𝘥 𝘪𝘯𝘴𝘪𝘥𝘦 𝘌𝘊𝘜𝘴? Defines SWCs, runnables, ports, OS scheduling ; especially in AUTOSAR. 6. 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 🌐 𝘏𝘰𝘸 𝘥𝘰𝘦𝘴 𝘥𝘢𝘵𝘢 𝘮𝘰𝘷𝘦? Bus topology (CAN, LIN, Ethernet), signal routing, timing, wake-up paths. 7. 𝗣𝗼𝘄𝗲𝗿 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: ⚡ 𝘏𝘰𝘸 𝘪𝘴 𝘱𝘰𝘸𝘦𝘳 𝘥𝘦𝘭𝘪𝘷𝘦𝘳𝘦𝘥 𝘢𝘯𝘥 𝘱𝘳𝘰𝘵𝘦𝘤𝘵𝘦𝘥? Fuse logic, smart PDUs, load prioritization, crank-safe strategy. 8. 𝗦𝗮𝗳𝗲𝘁𝘆 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 🛡️ How does the system stay safe under failure? ASIL levels, redundancy, fail-operational modes, watchdogs. 9. 𝗗𝗶𝗮𝗴𝗻𝗼𝘀𝘁𝗶𝗰 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 🔍 𝘏𝘰𝘸 𝘥𝘰 𝘸𝘦 𝘥𝘦𝘵𝘦𝘤𝘵 𝘢𝘯𝘥 𝘳𝘦𝘱𝘰𝘳𝘵 𝘧𝘢𝘶𝘭𝘵𝘴? UDS, DTCs, snapshot logic ; crucial for service and warranty. 10. 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 🔐 𝘏𝘰𝘸 𝘪𝘴 𝘵𝘩𝘦 𝘴𝘺𝘴𝘵𝘦𝘮 𝘱𝘳𝘰𝘵𝘦𝘤𝘵𝘦𝘥 𝘧𝘳𝘰𝘮 𝘢𝘵𝘵𝘢𝘤𝘬? Secure boot, cryptographic keys, ECU authentication, firewalls. 11. 𝗧𝗶𝗺𝗶𝗻𝗴 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: ⏱️ 𝘞𝘩𝘦𝘯 𝘥𝘰 𝘵𝘩𝘪𝘯𝘨𝘴 𝘳𝘶𝘯 ; 𝘢𝘯𝘥 𝘩𝘰𝘸 𝘱𝘳𝘦𝘤𝘪𝘴𝘦𝘭𝘺? Execution cycles, jitter control, event chains — especially for ADAS or braking. 12. 𝗩𝗮𝗿𝗶𝗮𝗻𝘁 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 🧩 𝘏𝘰𝘸 𝘥𝘰 𝘸𝘦 𝘮𝘢𝘯𝘢𝘨𝘦 𝘮𝘶𝘭𝘵𝘪𝘱𝘭𝘦 𝘵𝘳𝘪𝘮𝘴 𝘢𝘯𝘥 𝘳𝘦𝘨𝘪𝘰𝘯𝘴? Feature toggles, inheritance rules, SWC inclusion logic. 🔍  You don’t manage one architecture ; you manage twelve. And when they’re aligned, they create 𝗰𝗼𝗻𝘁𝗿𝗼𝗹. When they’re not, they create 𝗰𝗵𝗮𝗼𝘀. Thank you. #EEArchitecture #AutomotiveEngineering #SystemsEngineering #SoftwareDefinedVehicle #ModelBasedDesign #ZonalArchitecture #VehicleArchitecture #FunctionalArchitecture #AUTOSAR #VModel #EmbeddedSystems

1.191

17 comentários

We’re proud to announce that ZF has become the first company to locally produce an electronic control unit (ECU) for brake systems in commercial vehicle applications in Brazil, marking a significant milestone for the country! 🚛 The localized electronic control module enables key safety features that are now mandatory in commercial vehicles in Brazil, such as the Electronic Stability Control (ESC). This strategic move brings numerous benefits to OEMs across South America, including: ✅ Enhanced competitiveness ✅ Greater predictability for new projects, logistics, and support demands With this initiative, ZF reinforces its leadership also in intelligent solutions for Commercial Vehicles, aligned with the growing demand for safety, efficiency, and regulatory compliance. A major step forward for the Brazilian automotive industry and our customers, driving innovation, safety, and sustainable growth. #ZFGroup #Innovation #CommercialVehicles #Brazil

606

15 comentários

🚘🔧 Accelerating automotive development in the software-driven era As vehicles become increasingly software-driven, traditional testing methods are struggling to keep up. Static traceability fades, disconnected tools slow progress, and manual steps delay critical feedback. But testing doesn’t have to hold you back. 🌐 In this webinar, we’ll share a new approach to testing that helps you: • Speed up development without sacrificing rigor • Streamline workflows by connecting tools and teams • Ensure compliance with less manual effort • Adapt quickly as requirements and technologies change You’ll see how forward-thinking companies are reimagining their testing processes to match the speed and complexity of modern vehicle development — and how you can do the same. 👉 Reserve your spot now and learn how to accelerate your journey toward more efficient, software-driven innovation: https://lnkd.in/e94G7Vrx #AutomotiveInnovation #SoftwareDefinedVehicles #TestAutomation #CI/CD #Codebeamer #Webinar PTC Synopsys Inc

34

Traditional development approaches that prioritize hardware and mechanical systems are no longer sufficient in the era of software-defined vehicles. As the industry shifts its focus and the competition adapts, automakers must consider new strategies that emphasize agility and innovation. Read the “Don’t Get Outpaced” eBook to identify outdated approaches and learn new strategies to navigate the future of mobility: https://lnkd.in/eNf8hitn

41

FORVIA HELLA has launched “Ignite by FORVIA HELLA,” a new software-focused entity dedicated to developing software-only products. Built for speed and agility, it brings together a growing team of software experts — expected to reach 40 by year-end — to accelerate innovation in both core and new business areas. The unit is working on software closely connected to FORVIA HELLA’s strengths in lighting, electronics, and lifecycle solutions. But it’s also going further. One standout: the Traffic Rules Engine, a compliance module for SAE Level 3+ automated driving. Co-developed with TÜV Rheinland, it checks if planned vehicle maneuvers comply with traffic laws in real time. With software now central to mobility, this is a focused step forward, rooted in our electronics leadership.

282

2 comentários

⚙️ Modern vehicles are built on code, sensors, and compliance, not just components. From steering to braking, and even air quality inside the cabin, ECUs today handle far more than just control. Each one demands: ▪ Robust embedded software ▪ Custom hardware integration ▪ Safety (ISO 26262) and process (ASPICE CL2) compliance ▪ Built-in cybersecurity This is where our engineering teams come in. At Embitel Technologies, we’ve worked on: – Brake ECUs with ASIL D compliance – Steering ECUs optimized for performance and timing – Sensor-based modules like cabin air purifiers and environment monitors – Communication stacks, diagnostics, and end-to-end V&V We collaborate with Tier-1s and OEMs to take these systems from concept to production, across the entire V-cycle. 👉 https://lnkd.in/d-ZmmCVf #AutomotiveSoftware #ECUdevelopment #ISO26262 #Cybersecurity #EmbeddedEngineering #ASPICE #BrakeECU #SteeringECU #InCabinAirQuality

21

🚗 DTCs in Automotive Diagnostics — What, Why, and How If you work with automotive embedded software, you’ve definitely met DTCs (Diagnostic Trouble Codes). But in real projects, DTCs are much more than error numbers — they are a contract between software, hardware, testers, workshops, and even legislation. Let’s break it down clearly 👇 🔍 What is a DTC? A DTC (Diagnostic Trouble Code) represents a detected fault related to: - Sensors or actuators - Communication (CAN, LIN, Ethernet) - Internal ECU software or hardware - Safety, emissions, or drivability functions Each DTC has: - A unique identifier - A status byte (bit-coded life cycle) - Optional extended data (snapshots, counters, timestamps) Standards typically come from AUTOSAR and ISO 14229 (UDS). 🎯 Why DTCs Are Critical in Real Projects In production vehicles, DTCs are used to: ✔ Enable on-board diagnostics (OBD) ✔ Support workshop troubleshooting ✔ Fulfill legal and emission requirements ✔ Trigger limp-home or degradation modes ✔ Provide data for field analysis & recalls 👉 A wrongly implemented DTC can cause: - False warning lamps - Missed safety issues - Rejected vehicle homologation - Costly customer complaints ⚙️ How DTCs Are Used in Practice (Real ECU Flow) 1) Monitoring Software continuously checks conditions (timeouts, range checks, CRCs, plausibility). 2) Detection If a fault condition is fulfilled → diagnostic event fails. 3) Debouncing / Qualification Counters, time filters, or operation cycles avoid false positives. 4) DTC Storage DTC is stored with a status byte update and optional snapshot data. 5) Reporting Tester reads it via UDS services (e.g. 0x19 ReadDTCInformation). 6) Healing / Aging If the fault disappears for defined cycles → DTC may heal or age. 🧠 The Heart of a DTC: Status Byte The status byte tells the story of the fault, not just that it exists. Bit 0 TestFailed : Fault is currently present Bit 1 TestFailedThisOperationCycle: Fault occurred in the current driving cycle Bit 2 PendingDTC: Fault detected but not yet confirmed Bit 3 ConfirmedDTC: Fault confirmed after qualification Bit 4 TestNotCompletedSinceLastClear: Test hasn’t run since last clear Bit 5 TestFailedSinceLastClear: Fault happened at least once since clear Bit 6 TestNotCompletedThisOperationCycle: Test didn’t run in current cycle Bit 7 WarningIndicatorRequested: MIL / warning lamp requested 📌 Key takeaway: A DTC is not binary (present / not present). Its status byte represents its life cycle. 🏁 Final Thought A good diagnostic implementation doesn’t just detect faults — it tells a reliable story about them. If your DTCs are clean, consistent, and well-qualified: - Testing becomes easier - Workshops trust the ECU - Customers trust the brand 💬 How do you usually implement DTC qualification? Counters or time-based? Let’s exchange experiences 👇

234

6 comentários