Siva Teja Chigicherla ᯅ

Design and analysis of folding mechanism for automotive seats based on space maximization 10 key takeaways from our research and design process 1.The Goal: Maximizing Space & Comfort 2.'Stowable' vs. 'Fold-back' Seats 3.The Power of the Four-Bar Linkage 4.Design from Constraints 5.Avoiding Mechanical Jamming. 6.Kinematic Analysis for Smooth Motion 7.Dynamic Analysis for Force & Torque 8.Informing Real-World Decisions. 9.Simulation Before Prototyping 10.A Blueprint for Future Design ♻️Repost and follow Sanjeet Kumar for more   👉 Disclaimer: This content is for informational purposes only. All rights belong to the original author. No copyright infringement intended. If any issues arise, please contact us for prompt resolution. #AutomotiveEngineering #MechanicalDesign #Kinematics #VehicleDynamics #CAD #MATLAB #Innovation #AutomotiveInterior #Engineering #SpaceOptimization

308

22 Comments

KPIT MathWorks Automotive Conference 2025 We were thrilled to join India’s automotive leaders at #MAC2025 to explore how OEMs are navigating the rising complexity of Software-Defined Vehicles (SDVs).   Ritesh Goyal shared how virtual validation is helping OEMs scale smarter and faster:  • 100K+ nightly test cases • MIL to full system-level simulations • Seamless integration with OEM toolchains like Simulink With >80% virtual coverage and 100% bug detection during program increments, KPIT is enabling future-ready validation that’s built for OEM needs.   What’s your biggest challenge in SDV development today? Let’s talk about how virtualization can help you overcome it.   Divyesh Desai, Vishwajit Joshi, Sunil Motwani, Sameer Prabhu, Rashmi Rao, Sumit Pandharikar, ADITI TIWARI #SDV #AutomotiveSoftware #VirtualValidation #KPIT #MathWorks #Simulink #MAC2025 #InnovationInMotion #CloudValidation #OEMSolutions

139

2 Comments

🚦 Evolution of Automotive Software: Layered → Domain Architecture 💠 1. Layered / ECU-Centric Architecture (The Beginning) Think of early cars as cities with small independent shops. 🔹 Each function = its own ECU + its own full software stack. ▪️ ABS → dedicated ECU, with its own OS + drivers + application. ▪️ Airbag → separate ECU. ▪️ Power windows → separate ECU. 🔹 Communication = point-to-point CAN/LIN. 👉 Software inside each ECU: 🔹 Application (control logic) 🔹 Basic software (drivers, communication, diagnostics) 🔹 OS (OSEK / vendor-specific) 🔹 Hardware-specific (MCAL often custom) ⚠️ Problems: 🔹 Too many ECUs (80–100+ in premium cars). 🔹 Heavy wiring harness → cost + weight. 🔹 Same software (like diagnostics, comm stack) written again and again in every ECU. 🔹 Very hard to integrate → “software islands.” 💠 2. Domain-Based Architecture (Organized City) Now imagine the city grouped into districts (domains): 🔹 Powertrain domain: Engine, Transmission, Emissions. 🔹 Chassis domain: ABS, Brakes, Steering. 🔹 Body domain: Lights, Windows, Climate control. 🔹 Infotainment domain: Audio, Navigation, Connectivity. Each Domain Controller ECU runs software for multiple related functions. 👉 Software inside a Domain Controller: 🔹 Runs AUTOSAR Classic layered architecture. 🔹 Application software = Software Components (SWCs), each with its own interface. 🔹 RTE (Runtime Environment) = middleware, automatically connects SWCs. 🔹 BSW (Basic Software) = standardized modules (communication stack, diagnostics, memory). 🔹 MCAL = hardware abstraction, makes SW portable across MCUs. 🔹 OS = AUTOSAR OS, schedules tasks & events. 📖 Example : Imagine you want to control “brake lights when pressing the brake pedal”. 💠 Layered ECU (old): 🔹 Brake pedal ECU sends a raw CAN message to brake light ECU. 🔹 Brake light ECU has custom logic to read message switch lights ON. 💠 Domain ECU (new): 🔹 Both pedal input + brake lights are part of Chassis/Body Domain. 🔹 Application SWCs handle inputs/outputs. 🔹 RTE routes the signal between SWCs (no hardcoding). 🔹 AUTOSAR COM ensures standardized messaging. 🔹 Diagnostics & flashing → handled in the same standardized way. 👉 Easier integration, less code duplication, faster debugging. ✅ Essence 🔹 Layered ECU-Centric → Software = islands, tightly coupled to hardware, non-standard. 🔹 Domain Architecture → Software = standardized, modular, portable, built on AUTOSAR Classic. 🔹 This transition was the foundation for modern Software-Defined Vehicles (SDVs). ⚡ Next step after Domain = Zonal & Centralized Architectures, where AUTOSAR Adaptive, service-oriented communication (SOME/IP, DDS), HPCs, and OTA. #AUTOSAR #SoftwareDefinedVehicle #AutomotiveEngineering #EmbeddedSystems #DomainArchitecture #ZonalArchitecture #SDV #AUTOSAREngineer #ConnectedCars #AutomotiveSoftware

77

𝐅𝐮𝐥𝐥 𝐔𝐀𝐑𝐓 𝐏𝐫𝐨𝐭𝐨𝐜𝐨𝐥 𝐃𝐨𝐜𝐮𝐦𝐞𝐧𝐭 𝐫𝐞𝐥𝐞𝐚𝐬𝐞𝐝! 📝 Few handwritten notes → simplify complex concepts → 𝗴𝗹𝗼𝗯𝗮𝗹 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗺𝗼𝘃𝗲𝗺𝗲𝗻𝘁. 🌍 Through my handwritten series, I’ve been breaking down 𝗔𝘂𝘁𝗼𝗺𝗼𝘁𝗶𝘃𝗲 𝗘𝗺𝗯𝗲𝗱𝗱𝗲𝗱 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀 into: ✔️ Easy-to-understand visuals ✔️ Real-world automotive use cases ✔️ Interview-focused Q&A ✔️ Practical C code examples

359

2 Comments

"In the era of Software-Defined Vehicles (SDVs), Smart Vehicle Architecture is being reimagined. The foundation rests on four critical pillars — Sensors, Data, Connectivity, and Compute Power. Together, they transform vehicles from mere machines into intelligent, connected ecosystems, enabling continuous innovation, enhanced user experiences, and a faster shift toward autonomous mobility.

36

2 Comments

#30Days_Of_ModelBasedDevelopment 🚗Driving the Future of Automotive Software 🚀 #DAY13 🗂️ 𝐀𝐜𝐜𝐞𝐬𝐬𝐢𝐧𝐠 𝐕𝐚𝐫𝐢𝐚𝐛𝐥𝐞𝐬 𝐢𝐧 𝐒𝐢𝐦𝐮𝐥𝐢𝐧𝐤: 𝐃𝐚𝐭𝐚 𝐃𝐢𝐜𝐭𝐢𝐨𝐧𝐚𝐫𝐲 𝐯𝐬. 𝐌𝐨𝐝𝐞𝐥 𝐄𝐱𝐩𝐥𝐨𝐫𝐞𝐫🔍 Efficient variable management is essential in Model-Based Design, especially when working on scalable, modular automotive models. Let’s explore two powerful tools Simulink offers: 𝐌𝐨𝐝𝐞𝐥 𝐄𝐱𝐩𝐥𝐨𝐫𝐞𝐫 𝐚𝐧𝐝 𝐭𝐡𝐞 𝐒𝐢𝐦𝐮𝐥𝐢𝐧𝐤 𝐃𝐚𝐭𝐚 𝐃𝐢𝐜𝐭𝐢𝐨𝐧𝐚𝐫𝐲. 📘 1. 𝐒𝐢𝐦𝐮𝐥𝐢𝐧𝐤 𝐃𝐚𝐭𝐚 𝐃𝐢𝐜𝐭𝐢𝐨𝐧𝐚𝐫𝐲 (𝐒𝐋𝐃𝐃) A centralized repository to store design data like parameters, signals, and calibration variables. 🔹 𝐊𝐞𝐲 𝐁𝐞𝐧𝐞𝐟𝐢𝐭𝐬: • Stores global design data separate from the model. • Supports multiple configurations (e.g., for production vs. test environments). • Enables collaboration across teams and version-controlled environments. 🔹 𝐇𝐨𝐰 𝐭𝐨 𝐀𝐜𝐜𝐞𝐬𝐬: • 𝐑𝐢𝐠𝐡𝐭-𝐜𝐥𝐢𝐜𝐤 𝐲𝐨𝐮𝐫 𝐦𝐨𝐝𝐞𝐥→ Link to Data Dictionary • Or open .sldd file directly • 𝐔𝐬𝐞 𝐌𝐨𝐝𝐞𝐥 𝐖𝐨𝐫𝐤𝐬𝐩𝐚𝐜𝐞> External Data Source ✅ 𝐈𝐝𝐞𝐚𝐥 𝐟𝐨𝐫: Projects with large teams, multiple models, or integration with AUTOSAR or code generation workflows. 🧭 2. 𝐌𝐨𝐝𝐞𝐥 𝐄𝐱𝐩𝐥𝐨𝐫𝐞𝐫 A graphical interface that provides a hierarchical view of your model, workspace, and data sources. 🔹 𝐊𝐞𝐲 𝐁𝐞𝐧𝐞𝐟𝐢𝐭𝐬: • View and edit all variables from base workspace, model workspace, or data dictionary. • Filter/search specific data types, scopes, or properties. • Useful for inspecting block parameters, signals, data types, etc. 🔹 𝐇𝐨𝐰 𝐭𝐨 𝐀𝐜𝐜𝐞𝐬𝐬: • From Simulink toolbar → 📄 Modeling > Model Explorer • Or press Ctrl + H ✅ Ideal for: Debugging, verifying scope, or quickly navigating model data without switching contexts. 💡 𝐏𝐫𝐨 𝐓𝐢𝐩: Link your variables to SLDD and manage them via Model Explorer for maximum control, modularity, and clean architecture in your Simulink projects. #Simulink #MATLAB #Mathworks #ModelBasedDesign #DataDictionary #ModelExplorer #EmbeddedSoftware #AUTOSAR #ControlSystems #SimulinkTips #SoftwareArchitecture #Automotive

68

🚘 Automotive Software Testing: Precision, Safety, and Speed! 🔍 In today’s world, cars are no longer just mechanical machines — they’re intelligent, software-driven systems on wheels! 🧠💻 From ADAS to infotainment, every feature runs on millions of lines of code — and that means testing is mission-critical. ⚠️ 🚀 Software Testing Cheat Sheet – Your QA Survival Kit! 🧪 Whether you're building mobile apps or testing automotive ECUs, this quick overview helps ensure bug-free, high-quality software across domains: ✅ Testing Types – Unit, Integration, System, Acceptance 🧠 Approaches – Manual, Automated, Black & White Box 🛠️ Techniques – Boundary Analysis, Equivalence, State Transitions 📊 Metrics – Coverage %, Defect Density, Test Execution Time 📚 Documentation – Plans, Cases, Reports, Traceability ⚙️ Frameworks – JUnit, Selenium, Postman, Cucumber 🎯 Principles – Test early, automate often, never assume it’s bug-free In the automotive domain, where safety and compliance are non-negotiable, mastering these areas isn't just a checklist — it's a mindset. 💡 💬 What’s your go-to testing technique when validating automotive software? #AutomotiveTesting #SoftwareQuality #TestAutomation #EmbeddedSystems #ISO26262 #ADAS #SoftwareEngineering #QA #UnitTesting #IntegrationTesting #FunctionalSafety #LinkedInLearning

353