Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Tuning Software
Parent
Section level
Applies to
No ECU-specific applicability
Tool groups
Flashing and tuning tools
Manufacturers
None

← All map and hex editors

Swiftec is installed automotive software for working with control-unit files. Its features combine map and raw-data editing with predefined map packs, online databases and separately available automated modules. Swiftec describes coverage spanning engine, transmission and other vehicle control systems, with the actual functions dependent on the file and licence.

Swiftec product illustration showing several editor windows and a 3D map
The supplier’s composite illustration brings several Swiftec windows together, including a table and 3D map; it is not a single captured workspace. Image credit: Swiftec Lda.. Image source.

Map and hex editing

Swiftec lists 2D, 3D, hexadecimal and map views. A table is useful for inspecting exact cells, while a graph makes changes in shape easier to see; the hex view provides access to the underlying bytes. The supplier offers predefined and automatically detected maps and lists different levels of map pack. Check what a particular pack identifies for the exact software before relying on a label or scaling.

The product also offers tools for managing map information and a range of automated operations. An automatic operation changes a file according to its own supported logic; it should still be reviewed against the original and validated for the specific application. Availability of one module does not imply that another module or ECU is supported.

Licence and connectivity

Although Swiftec is installed locally, its published licence states that an internet connection is required to use the software. Its base packs and optional modules can differ, so check the current licence, subscriptions, support and ECU coverage before deciding which configuration to use. Do not assume that an installed copy is suitable for an offline workshop.

Practical workflow

Keep the original read, identify the control unit and software version, and review the maps or modules available for that file. Save the changes as a separate version and compare it with the original. Establish checksum correction and the correct ECU read/write method for the individual toolchain rather than assuming an automated edit covers them.

Sources