180 likes | 589 Views
Volvo CE Software Control. AB Volvo. Business Areas within Volvo Group. Mack Trucks. Renault Trucks. Volvo Trucks. Buses. Construction Equipment. Penta. Aero. Financial Services. ARTICULATED HAULER. EXCAVATOR. MOTOR GRADER. WHEEL LOADER. COMPACT EQUIPMENT.
E N D
AB Volvo Business Areas within Volvo Group Mack Trucks Renault Trucks Volvo Trucks Buses Construction Equipment Penta Aero FinancialServices ARTICULATED HAULER EXCAVATOR MOTORGRADER WHEEL LOADER COMPACT EQUIPMENT Business Lines withinVolvo Construction Equipment Business Areas CUSTOMER SUPPORT RENTAL
Braås, Sweden; Pederneiras, Brazil ± 600 empl. Eskilstuna, Sweden Arvika, Sweden ± 1100 empl. Asheville, North America ± 250 empl Changwon, Shanghai,China ±1300 empl. Goderich, Ontario, Canada ± 700 empl. Eskilstuna, Sweden ±900 empl. Pederneiras, Brazil ± 250 empl. Belley, France Konz-Könen, Germany Wroclaw, Poland ± 950 empl. Hallsberg, Sweden ± 500 empl. R&D Plant 11
Instrument control unit(I-ECU) Cab control unit (C-ECU) Vehicle control unit (V-ECU) PROSIT VCADS Pro MATRIS Engine control unit (E-ECU) Transmission control unit (T-ECU) Electronic Control System
Rubus OS Red Kernel Green Kernel Blue Kernel Basic Services Rubus OS Supports Different Execution Paradigms
Rubus Implementation Pre-runtime Generated Execution Schemes 95% of Functionality is Pre-runtime Scheduled
C 1 C 1 C 1 C 2 Rubus Component Designer Software Components Separated Temporal Configuration Component Interface Re-useable Component Library
What VOLVO CE use Red thread Almost everything 95% (including none time critical) Better temporal behavior we know what happened Pre-runtime dispatch table make it easy to plan when things should happen Blue thread Slow buss Diagnostic to service tools Driver information (display) Green threads Small interrupt that is hard to avoid
What VOLVO CE use Queue between red and blue threads None or almost none semafor/mutex (not needed due to the red threads). Max time dump to be able to see the execution time estimate. Poor usage of read error report (only romPOD) Simple reboot on red error Mode shifting (warm up, drive, shut down and test)
Good things Simple and strait forward When the schedule is created and the time is good then one have a stable system Small RTOS No per unit cost Close co-operation Possibility to make component library
Bad things No “plug-in” ( can buss) Easy to have a high schedule without having it in practice Close co-operation (Some think that TUE make to much debugging) Small company. Make it risky Only C167 support Lack of develop tools (online tracing, max time from target) A lot of overhead work with component and the connections ( better tool under evaluation)