E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility...

12
E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM, Software Engineering Directorate Aviation & Missile RDT&E Center Bruce Bardell Chief Systems Engineer, A3 Bradley Fighting Vehicles United Defense LP, Ground Systems Div.

Transcript of E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility...

Page 1: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

Embedded Vehicle Version Identification Tracking and Compatibility Checking

Edgar DalrympleComputer Engineer, US Army AMCOM,

Software Engineering DirectorateAviation & Missile RDT&E Center

Bruce BardellChief Systems Engineer, A3 Bradley Fighting

VehiclesUnited Defense LP, Ground Systems Div.

Page 2: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

A Reprogrammable Weapon Platform

The preponderance of software-based Line Replaceable Units (LRUs) in a complex digital architecture enables cost-effective software loading by the Unit level maintainer

Platform software updates are made for a number of reasons

– Improve existing behavior

– Add new functions

– Adapt to hardware changes

Critical aspects are controlled by software

– Operational and Safety functions

– User interfaces

– Performance characteristics

– LRU interfaces

Close control of all fielded platform LRU hardware and software is impractical

Page 3: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

Achieving Planned Improvements and Compatibility with New Hardware

Planned Improvements have two levels of system impact

– Changes isolated within LRUs

– Changes that affect LRU to LRU interfaces

Introduction of new hardware must consider:

– Changes isolated within LRUs

– Degree of downward compatibility must be understood

– Establishment of a “sunset” date on legacy hardware

Page 4: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

Version Reporting Hierarchy - LRUs, Sub-LRUs, and SRUs Within the System

LRU

sub-LRUsub-LRU sub-LRU

MotorSmartSensor

Electronics

Hardware coding jumpers

SRU

Tachometer

SRU

SignalConditioning

Hardware coding jumpers CCA HardwareCCA Software

SRU

Power & Servo

CCA HardwareCCA Software

SRU

Diagnostics

CCA HardwareCCA Software

Actuator

SRU

Commu-nication

CCA HardwareCCA Software

Page 5: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

VVID and Sub-VVID Notional Example

LRU Versions contained in a few similar System VVIDs

The VVID number that is displayed when a match is discovered may in reality contain LRUs of different versions, but the platform’s behavior at a crew level is identical

Every possible combination of LRU hardware and software versions is accounted for as a unique “sub-VVID”

VVID VVID 1.01.01 VVID 1.01.02 VVID 1.01.03 sub-VVID

.01 .02 .03 .04 .05 .06 .07 .08 .01 .02 .03 .04 .05 .06 .07 .08 .01 .02 .03 .04 .05 .06 .07 .08

LRU #1

4 4 5

LRU #2

2 3 2

LRU #3

6 7 6 7 6 7 6 7 6 7 6 7 6 7 6 7 6 7 6 7 6 7 6 7

LRU #4

8 9 8 9 8 9 8 9 8 9 8 9

LRU #5

1 2 1 2 1 2

Version changes thatdrive functional impacts

Other version differences

VVID and sub-VVID

Page 6: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

Weapon Platform System Computer Collects and Assesses Data

The potential for incompatible LRUs to be introduced onto weapon platform does exist– Battle Damage Assessment and Repair– Expedient Maintenance

Version data is made available to the system computer– Data must be present during a predetermined period at system power-

up– Data must meet the formatting constraints defined in the platform

interface control drawings (ICDs)

The system computer contains the database needed to assess Vehicle-level compatibility– All known fielded LRU hardware and software versions are included– All safety-certified combinations of those LRUs are tabulated– Known undesirable combinations are also tabulated

Page 7: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

Weapon Platform System Computer Advises the Crew

The system computer reports the exact or nearest Vehicle Version Identification (VVID)

– If all LRU hardware and software exactly matches a safety-certified combination, the platform meets a valid VVID and the VVID number is displayed on the start-up screen; exact versions of all LRUs are contained on a set of screens available via the menu tree

– If not all LRU hardware and software exactly match a safety-certified combination, the system computer determines the nearest match, but displays “Invalid VVID”; expected versions of the nearest match of all LRUs are contained on a set of screens

Page 8: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

Example VVID Screen(1st of 4 Bradley A3 Screens)

ITEM REPORTED VERSIONS EXPECTED VERSIONS VEHICLE TYPE M2A3/M3A3 M2A3/M3A3

VEHICLE VERSION 7.00.00 7.00.00 LRU HARDWARE SOFTWARE HARDWARE SOFTWARE

TPU TPU-GPP CONFIG 07.00.00 = 07.00.00 . . TPU-FCP CONFIG 07.00.00 = 07.00.00 . . TPU-XWGLS 12470952-11 07.00.00 12470952-17 = 07.00.00 . . TPU-UIC 12470971-00 12479318-00 . . TPU-GPP 12470923-10 07.00.00 12479314-00 = 07.00.00 . . TPU-FCP 12470923-10 07.00.00 12479315-00 = 07.00.00 . . TPU-ASSEMBLY 12470930-00 = 12470930-00 . . SCB 0 00 = 0 = 00 . . GCU 0 01 = 0 = 01 . . FPD SLD 124660331 08 = 124660331 08 . . CTD 124660332 08 = 124660332 = 08 . . HPU HPU CONFIG 07.00.00 = 07.00.00 . . HPU-FCP 12479317-00 07.00.00 = 12479317-00 = 07.00.00 . . HPU-ASSEMBLY 12470931-00 = 12470931-00 . .

Comparison Criteria of reported and expected

version’s Ordinal Values

Comparison Results“.” = Pass, “f” = Fail

First position = hardwareSecond position = software

Ordinal sequencedoesn’t match

numeric sequence

Page 9: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

Weapon Platform System Computer Takes Action

When the system computer doesn’t detect an exact VVID match, additional actions may occur via the Compatibility Checking function

– The crew is always advised to “proceed with caution”

– For version mismatches that have been predetermined as undesirable, the degree of safety concern dictates any further action the system may take:

» Display advisories

» Disable functions

» Log faults

» Power off LRUs

» Inhibit transition to Combat State

Page 10: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

Support Equipment also uses the VVID

System Software Loader– Used for two purposes

» Bring the weapon platform up to a recently released VVID» Bring the weapon platform to a valid VVID at the conclusion of a

maintenance action

– Operates by assessing available platform hardware to determine how to create a valid VVID from its file of software

» Weapon platform type» Set of LRU hardware versions

Direct Support Benchtop Test Equipment– Used to identify faulty module in an LRU, if the LRU is incapable of full

self-diagnosis– Used to facilitate post-repair verification– Brings LRU to recent or current version that is compatible with its

hardware content, so System Software can do its job

Page 11: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

Compatibility Checking

Platform Startup

Turn On Power

Power-on alldefault loads

Run SystemController

self-test andestablish bus

communications

Report versiondata

upon request

Collect sub-LRUand SRU

version data

Collect hardwareand software

versionsacross system

DetermineSystem VVID

ValidVVID?

Yes

No

EnterCombat

State

Display VVID number,expected and

actual versions

Display “VVID Unknown”,expected and actual versions,and “Proceed with Caution”

InhibitCombat

?

PredefinedMismatches?

No

No

Yes

Provide predefined alerts,function inhibits, powershutdowns, fault reports

Yes

End

Vehicle Version

Identification

Page 12: E. Dalrymple / B. Bardell Embedded Vehicle Version Identification Tracking and Compatibility Checking Edgar Dalrymple Computer Engineer, US Army AMCOM,

E. Dalrymple / B. Bardell

Benefits to Bradley A3

• Unambiguous definition of all tested and approved fieldable platform configurations

• Concise means of referring to the current and historical platform-level hardware and software suites

– Benefit to defect-tracking metrics

– Easier targeting of problem resolution

– Becomes part of engineer, Field Service, Customer, and User/Tester jargon

• Personnel and equipment protection in the event that an unapproved configuration must be utilized

• Assistance to Government-furnished Equipment providers to clarify the required versions of their equipment