Real Time Scheduling Issues in Powertrain Controls

advertisement

Real Time Scheduling Issues in

Powertrain Controls

James B. Kolhoff

Engineering Group Manager

Front Wheel Drive Controller Team

General Motors Powertrain

James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation 01OC2000 Slide 1

Overview of Presentation

n n n n n

GMPT Electronics Integration & SW - Group & Product

Scheduling Requirements and Problem

Solution

Distributed architecture

Next step

James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation 01OC2000 Slide 2

Group and Product Background

Group

GMPT is a division of General Motors, responsible for engine, transmission, powertrain controls engineering and manufacture

Electronics Integration & Software (EI&S) is a product engineering team responsible for the electronics and software for powertrain controls

Product

EI&S end product is an embedded microprocessor control module(s) that controls and diagnoses engine, transmission, and vehicle functions.

n n

Multiple end products (ECM, TCM, PCM) with different feature content

(internal GM and external customers)

Multiple controller and compiler suppliers n n n

Other vehicle module interfaces

Development and production tool interfaces

Controller: 32bit uc, 1Mb ROM, 150+ pins

James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation 01OC2000 Slide 3

Scheduling requirements

n n n

Two categories of task - time synchronous, engine event synchronous u u

Time: 3.125ms, 6.25, 12.5, 25, 100 ms

Engine: crankshaft synchronous, cam synchronous

The engine event tasks cause the processing power to be consumed in direct proportion to engine speed

Engine event synchronous tasks have harder deadlines and higher priorities than time based tasks u u u

8 cylinder engine engine, event sw task execution time 1ms

600 rpm: 25ms event rate, 4% available processor thruput

7000 rpm: 2.1ms event rate, 48% available processor thruput

01OC2000 Slide 4 James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation

Task scheduling

ISRs

E N G I N E P O S I T I O N T A S K

P E R I O D I C T A S K 1

P E R I O D I C T A S K 2

B A C K G R O U N D

O S & H W I O O V E R H E A D

G M P T C O D E

P R E - E M P T I O N T I M E

E V E N T

James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation 01OC2000 Slide 5

Scheduling Problems

n n n n n n

Most critical scheduling problem was task deadlines missed at higher engine speeds

Basic root cause: Limited processing power u u u

Using low cost microprocessor

Low clock speed for EMC performance

Too late in program to make processor change

ROM limited so we can’t do ROM tradeoffs for thruput

Fixed point math operations u

Library not optimized for performance

Requirement of ANSI-C for code portability u

Not designed for performance

SW Design and Coding Standards u

Designed for reuse and readability, not performance

James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation 01OC2000 Slide 6

Solutions applied

n n n n

Re-design software for improved efficiency u

Significant work effort, potential loss of function, repeat verification

Optimize libraries to take advantage of processor specifics u

Significant work effort, reduces reuse, increases verification requirements

Revise coding standards to maximize efficiency u u

At the expense of portability and reuse

Rework and revalidation across large number of engineers

Biggest bang for the buck - dynamic scheduling u u

Can localize redesign at areas of maximum benefit

Time tasks slower than 25ms rates are insignificant to the problem

James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation 01OC2000 Slide 7

Dynamic scheduling

n n n n

Objective: Reduce execution requirements at higher engine speeds u

Difficult to individually disable or redesign functions

Developed engine speed zones approach u u

Different function level in each zone

Simplifies coordination of scheduling change

In middle engine speed range, divide function across multiple engine events u

Balance load across multiple cylinder events

At highest engine speeds, significantly simplify some functions u

Engine states don’t change every cylinder

01OC2000 Slide 8 James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation

Effect of Dynamic Scheduling

Engineering

Processor Utilization

110.00

100.00

90.00

80.00

70.00

60.00

50.00

40.00

30.00

20.00

10.00

0.00

0 1000 2000 3000 4000 5000

Engine Speed (RPM)

6000 7000

01OC2000 Slide 9 James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation

8000

Controller System Topologies

Powertrain Control Module

Vehicle

Electrical

System

PCM

Engine

Electrical

System

Transmission

Electrical

System

Engine/Transmission Control Modules

ECM

Engine

Electrical

System

Vehicle

Electrical

System

TCM

Transmission

Electrical

System

Legend

Electrical System

Control Module

Electrical Interface

James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation 01OC2000 Slide 10

Distributed architecture

n n n

Controller systems architecture for GMPT is changing to separate engine controller / transmission controller u

For reasons of powertrain portfolio management

This architecture reduces the computing power needed in any single controller

Scheduling and thruput still needed to be carefully managed u u

System partitioning plays a key role

Inter-module Communications uses some of the freed up thruput

James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation 01OC2000 Slide 11

Future

n n n n

Microprocessor power has grown dramatically over the past 5 years

At the same time, costs have fallen dramatically for this power

With the microprocessors available for the projects planned, thruput will not be the significant problem it has been in the past

Simulation and schedule/thruput budgets are the next steps

James B. Kolhoff james.kolhoff@gm.com

© 2000 General Motors Corporation 01OC2000 Slide 12

Download