vFlash 2.1

Functions

vFlash utilizes flash projects to save and exchange the configuration to program individual ECUs. Flash projects contain all relevant settings and reference the data files to be programmed. If the focus is on flexibility in changing the flash data, the referenced data files can simply be exchanged in background, e.g. as part of an automated software build process. In this case, the flash project remains unchanged.

If the focus is on a process-safe exchanging of flash configurations, the flash projects may be exchanged in the Pack&Go format. In this case, all relevant settings together with the data files are packed in an archive file.

The user creates flash projects based on flash templates. A flash template defines the diagnostic services and presettings that are relevant to the flash process for a group of ECUs of a specific automotive OEM (e.g. for a vehicle platform). In practice, the flash specifications of automotive OEMs differ enormously, not least of all due to the differences in diagnostic protocols and in-house flash standards. The advantage of flash templates concept is that the differences described above remain largely hidden from the user.

The reference flash process from Vector is also available as source code (C#). This lets end users modify the flash sequence themselves as necessary. All that is needed for this is Microsoft Visual Studio for C#; the Express Edition can be obtained from Microsoft free-of-charge.

Transfer rate
Programming of 100kByte data in 4.1s (24.4kByte/s) into an idealized reference ECU over CAN at 500kBit/s with STmin = 0, BS = 0

OEM-specific flash templates
Vector offers prepared flash templates for a number of different automotive OEMs.
Request a list of supported manufacturers!

Did you find this page helpful?
E-Mail:

Please comment: