ECU Tracker Logo
  • Installation
    • How and Where to Install
      • Manual Install
      • Tool Auto Update
  • Troubleshooting
    • Verify Permission Level
    • Can’t Build a Package
    • Can’t Promote a Package
  • Glossary
  • Usability
    • User Access
      • What
      • Why
      • How
      • Permission Levels
      • How to get permission
      • How to log-on
      • Use Re-Login and Logout
    • Email Settings
      • To Start
      • Edit Email List
      • Edit Email Address
      • Email List Usage
    • Email Sender
      • To Start
      • Select Receipts
      • Attachments
      • Send Email
    • Error Reporting
      • Report Usage
      • To Start
      • Report Information
      • Report Post
    • Generate Enovia CSV
      • CSV File Usage
      • To Start
      • Enovia CSV Window
    • Generate Enovia Package Configuration
      • Introduction
      • How
      • Command Line Usage
    • Generate OTA Configuration CSV
      • To Start
      • Generate OTA Configuration CSV Window
      • Generated CSV Files
    • Line of Inheritance Editor
      • Instruction
      • Menu Access
      • Window Layout
    • Miscellaneous Features
      • Copy Pasting Software
      • Change Window Style
      • CPKG Manifest Viewer
  • Tracker Overview
    • BOMS
      • BOM Creation/Inheritance
      • Vehicles
      • Domain Variants
      • ECU Assemblies
      • ECUs
      • BOM Objects are Version-less
      • BOM Objects show acceptable configurations
      • Manifests
      • Vehicle
      • Domain Variant
      • ECU Assembly
      • Manifests are versioned
      • Software can be reused
      • OTA vs CSV Manifests
      • Packages
      • Vehicle
      • Domain
      • ECU Level
      • Exported Package
      • Packages are Supersets of manifests
      • Packages are versioned
      • Groups
      • Packages have RC numbers
    • Process Flow
  • Variant Management
    • Introduction
    • DRE: ECU Configuration for Assemblies
      • Software Addresses
      • HW Revisions
      • Software List Types
    • DRE: Creating or Editing ECU Assemblies
      • ECU Assembly Version Control
      • Specifying Software List Types and Software Addresses
      • Specifying Hardware Revision
    • Domain Owner/ Vehicle Owner: Adding / Editing Bill of Materials Objects
      • Adding a BOM object
      • Editing a BOM object Details
      • Bom Version Control
      • Adding items to the BOM
      • Sorting items included in the BOM
      • Removing items from the BOM
      • Video Tutorials
  • Package Creation and Building
    • Vehicle Package Inheritance
      • Inheritance Editor
    • Introduction
    • Which instructions to follow
    • Rules with multiple assemblies
    • DRE: (with components built by Jenkins) Creating a Package
      • Specify Software
      • Specify Software List
    • Guidelines or priorities with multiple assemblies
      • One branch
      • More than one branch built by Jenkins
      • Manual Upload
    • DRE (supplier based, or in house built separately) Creating a Package
      • Uploading .zip files using Jenkins
      • Uploading supplier .zip files from tracker
      • Adding the software components to the tracker
      • Adding A Software List
    • Reusing a Package
    • Using the Package Page
      • Find any existing packages
      • Create/Build a Package
    • Software Fields Details
      • Pre-Conditions
    • How to Add Release Notes
    • TroubleShooting
      • Information in the tracker is not correct, it does not kick off any Jenkins jobs
      • The Jenkins Job for a component is failing
      • The Jenkins Job is creating a component but not updating the tracker
      • The Package Building Job is failing
      • Other errors
      • No jenkins jobs listed for start_string:
      • No package with package name [package_name] found:
  • Package Validation
    • Introduction
    • Finding a Package on the P: Drive
    • Exporting a Package
    • Using the .csv manifests
    • Using the OTA manifests
    • Validating a Manifest
    • Promoting or Failing a Package
      • Find a Package
  • Package Signature
    • Introduction
    • Key Setting (Customize Key Files)
    • Add Signature with Package Creation
      • Release Package Signature
      • OTA Custom Package Signature
  • Package Status
    • Introduction
      • Status Tree
      • Exporting an early .csv to see status
      • Find a Package
    • Package Status Chart
      • Usage
      • Tips
  • Package Build Log
    • Introduction
    • User Last Build Log
    • Package Last Build Log
    • Usage
  • Package Diagnostic
    • Instruction
    • Pre-Settings
    • Usage
      • Add ODX software to ECU
      • Add ODX software to software list for building
      • Add Jenkins Job for ODX component
      • BV and EV
    • Accessibility
      • ODX information access from UI
      • Package ODX Export
    • Reference
  • Package Test
    • Package Automate OTA Test
    • Assembly OTA Test Setting (Admin Only)
  • Release Notes
    • Release Note Checker
      • Where
      • How
      • Usage
    • Release Note Generator
      • Where
      • How
      • Usage
      • Result
      • Output
    • Creation
    • Usage
    • Valid Scenarios
    • Invalid Scenarios
    • Examples
      • Release Notes Inside zip
      • Generated Release Notes
  • Develop Testing Packages
    • Introduction
    • OTA Package Window Layout
    • Process
  • UDS Flasher (Experimental Feature)
    • UDS Flasher Setting
    • Flash Package Manifest
    • Flash Assembly
  • Test Report
    • Instruction
    • Add Test Report
    • Test Report Viewing
  • In House ECU Software Logistics
    • Instruction
    • Field Structure
    • Software Version Format
    • Single Software Format
    • Multiple Software Format
  • Developer Tools
    • Developer Tools Access
    • User Log Search Tool
    • Update User Log
    • Developer Settings (Jenkins Job)
    • OTA Automate Test
  • ECU Tracker Error Codes
    • System Error Codes
      • [0-0] Error code not defined
      • [0-1] Jenkins Connection Error
      • [0-2] Network Drive Not Accessible
    • Package Build Error Codes
      • [1-0] Package not created
      • [1-1] Software not needed
      • [1-2] Software not zip or mcu file
      • [1-3] Software get bad file input
      • [1-4] Software type [MCU] get bad input file type
      • [1-5] Software is not built
      • [1-6] Software file is not specified
      • [1-7] Child package is not built and promoted
      • [1-8] More than one software list is used
      • [1-9] Software list type is empty
      • [1-10] Software list type is missing
      • [1-11] Software address is missing
      • [1-12] Software list is empty
      • [1-13] The software specified is missing
      • [1-14] Hardware Rev definition is missing
      • [1-15] ECU Assembly is included in multiple Boms
      • [1-16] Duplicate start string is used by multiple softwares
      • [1-17] Package not found
      • [1-18] Duplicate package found
      • [1-19] Promoted package exist
      • [1-20] Multiple target packages found
      • [1-21] Built package exist and not yet been failed
      • [1-22] Package Creation Failed
      • [1-23] Package Ram storage created failed
      • [1-24] Package creation rejected
      • [1-25] Package logistics update error
      • [1-26] ECU does not exist
      • [1-27] Software component build job missing
      • [1-28] Software component build job failed
      • [1-29] Software version invalid
      • [1-30] Package build output folder creation failed
      • [1-31] Package build ecm/ec2 creation failed
      • [1-32] Package build manifest cpkg creation failed
      • [1-33] Package build manifest cpkg verification failed
      • [1-34] Package build failed due to unexpected Exception
      • [1-35] Package release note generation failed
      • [1-36] Package status change failed
      • [1-37] Software AppLogisticsData Json Error
      • [1-38] Package LOI not defined
      • [1-39] EC2 built prior to 0.22
      • [1-40] EC2 input file error
      • [1-41] Software built file missing
      • [1-42] ODX file parsing error
      • [1-43] Assembly assigned with multiple ODX file
      • [1-44] Hex file not found in the software zip
      • [1-45] ODX EV file missing for Assembly
      • [1-46] Manifest CSV Output Error
      • [1-47] Bom Compatible Version Setting Error
      • [1-48] Package Manifest Configured Empty Error
      • [1-49] Package Signature Key Load Error
      • [1-50] Child Bom Version Capability Error
      • [1-51] Child Bom Disabled Error
    • Database Error Codes
      • [2-0] Database Connection Error
  • Development Guides
    • Dump datab to local MongoDB
    • Configuration
    • Main Conponents and Dependencies
    • User Interface and PySide
    • Package build process
    • Database(MongoDB) and ORM
    • Release and Deploy
    • MISC
ECU Tracker
  • »
  • Index

Index

B | C | D | E | F | G | I | M | P | S | V

B

  • BOM

C

  • Car/Vehicle

D

  • Domain

E

  • ECU
  • ECU Assembly
  • Electrical Device
  • Exported Package

F

  • Flashable

G

  • Group

I

  • Instance

M

  • Manifest

P

  • Package
  • Promoted

S

  • Software Component
  • Software List
  • Software List Type

V

  • Variant

© Copyright 2017, FF.

Built with Sphinx using a theme provided by Read the Docs.