Stellacan diagnostic software
Stellacan application and interface
See how Stellacan connects to a vehicle, identifies control units, reads faults, monitors live data and supports coding and service work.
Required hardware
The Stellacan diagnostic interface is required
The Stellacan application is designed to operate with the Stellacan diagnostic interface. A compatible Stellacan interface is mandatory: it authenticates the application and provides the communication channel to the vehicle control units.
How the interface works
- Connect the Stellacan interface to the computer and vehicle before starting operations.
- The interface is the authentication key; a separate login inside the desktop application is not required.
- Full-access and license credits are purchased separately through the Stellacan website and are activated for the connected interface.
Before you start: Full-access is required
Stellacan is a professional desktop application for diagnostics, coding and service work on supported vehicles. An active Full-access plan is required for the application to perform diagnostic operations.
After purchasing Full-access, connect the Stellacan head to the computer, start the application and wait until the status indicator confirms that the device is ready.
Vehicle coverage and shop details are available after signing in to the website.
Recommended setup
- Purchase and activate Full-access on the website.
- Connect the Stellacan diagnostic head.
- Allow the application to download current definitions.
- Select a vehicle or use automatic VIN detection.
Automatic application updates
The application checks for new releases automatically. When an update is available, Stellacan displays a confirmation window. After you select Yes, the current application closes, the new version is downloaded and the updated application starts automatically.
Main application layout
After the application is ready, the main window is divided into navigation, vehicle selection, diagnostic workspaces, logging and account controls. The numbered areas below correspond to the colored annotations in the screenshot.
-
1
Menu bar — File manages saved diagnostic data: load a complete file, load it as reference, load it as changes, clear the current data or save data to a file. In coding views, reference and changes are loaded into their corresponding columns. Definitions provides Reload all, Reload current and Show all modules. Reload current is especially useful when a module did not load correctly after an interrupted internet connection. Show all modules creates tabs for every available module. Quick access currently returns to Global and exits economic mode. The language menu currently supports English, Français and Polski.
-
2
Workspace tabs — Switch between the application views here. Tabs are added as you open modules and workspaces. The tab-creation behavior can be configured in Settings 8.
-
3
Vehicle make filter — Filter the vehicle catalogue by brand before choosing a model.
-
4
Search and vehicle actions — Search the vehicle list by text. No vehicle opens diagnostics without a vehicle selection. Auto detect reads the VIN from the vehicle and is the recommended route. Confirm accepts the selected vehicle after the identification step.
-
5
Manual vehicle selection — Browse and select a vehicle manually when automatic detection is not available or when you are working with a known vehicle definition.
-
6
Diagnostic log — The log records connection events, diagnostic sessions, definition loading and operation results. It can be hidden in Settings 8 when a cleaner workspace is preferred.
-
7
Operation status — Green indicates that the application can operate, yellow indicates that an operation is in progress, and red indicates that the diagnostic head is not connected or communication is unavailable.
-
8
Account and utility controls — Account shows subscription status, account ownership and license purchases. Settings controls the diagnostic-head connection and application behavior or appearance. Support sends a request to technical support. Extra contains additional functions for advanced users. All four controls belong to section 8.
Vehicle identification and confirmation
Automatic VIN detection is the recommended workflow because it reduces the risk of selecting an incorrect model or vehicle group. Manual selection remains available for bench work and vehicles that cannot provide a readable VIN.
- Select Auto detect in the vehicle-selection toolbar.
- If the VIN is read successfully, check the detected VIN and select Continue. You can correct the VIN before continuing.
- If the VIN cannot be read, enter it manually and then select Continue. Cancel returns to vehicle selection.
- Review the detected make, model, VIN and group in the vehicle preview. Select Confirm to open the diagnostic workspace, or Back to selection to repeat the process.
Auto detect → verify VIN → review vehicle preview → Confirm.
Global workspace and vehicle scan
After confirming the vehicle, the workspace switches to Global. The Vehicle selection tab remains available if you need to return and choose another vehicle.
-
9
Vehicle and search toolbar — The make and model received from Vehicle selection are displayed here and can be changed, although automatic detection is preferred. Show ECU names reveals controller names below the group names. Clear the search field, search by group or ECU name, expand or collapse the error list globally, and generate a PDF report of the global scan.
-
10
Control-unit group list — Each row represents a vehicle system group. Use Scan to read a group, use the drop-down list to select a controller manually, and use the arrow to confirm and open that controller. After a scan, the list displays the detected module and the number of faults, with a green arrow to open the module workspace.
-
11
Scan action buttons — Choose groups selects strategic groups defined for the session, such as BSI, INJ or ESP. Green actions read only the selected strategic groups and are usually the fastest choice for bench work. Full read of strategic ECUs identifies and fully reads those groups; Quick scan of strategic ECUs performs identification without reading faults. Blue actions apply the same two modes to all available ECUs in the vehicle. Erase all DTCs clears faults from all controllers. Stop reading interrupts an active read operation when available.
Working inside a control-unit module
Open a controller from the global scan to create a module tab. The module workspace provides identification, Flash, Coding, Live data, DTCs and—depending on the controller—History and Operations.
Module tabs and functions
- Identification — read ECU type, supplier, hardware, software, VIN and other identification fields.
- Flash — access supported flashing procedures. A purchased Flash license applies to the selected ECU/controller and remains valid for 72 hours. Stable power and communication conditions are required.
- Coding — read current configuration, compare reference and present values, choose a coding group, optionally use AI coding and write the selected coding. Some AI operations require a one-time license fee.
- Live data — read current parameters, refresh values and select data for plots or the Logger workspace.
- DTCs — read and clear faults, search the list and open detailed information including suspect areas when available.
- History and Operations — available only for modules that provide these controller-specific functions.
Fault codes and suspect areas
The DTC view lists stored faults for the selected controller. Use the search field to narrow the list, Read DTCs to refresh the data and Clear DTCs to erase faults when the vehicle conditions and repair procedure allow it.
Coding, AI coding and live data
Coding and live-data screens use the same module workspace, but each function has its own selector and action bar.
- 1Choose a coding group — Use the top drop-down list to select the group you want to inspect. The same principle applies to live-data groups.
- 2Read and compare — Read the current coding and compare reference values with present values before making a change.
- 3AI coding — AI coding can assist with a supported coding operation. Before sending data, the application asks you to verify the VIN. Some AI operations require a one-time license fee.
- 4Write coding — Write only after checking the selected values and following the vehicle manufacturer's safety and voltage requirements.
Commercial and technical summary
Purchase access online
Choose Full-access for the time you need: 1, 3 or 7 days, or a monthly subscription. Access starts immediately after payment and activation.
Authenticate with the head
The diagnostic head authenticates the desktop application. A separate in-app login is not required, but the head must be connected and online access must be available for validation.
Use license credits when required
A purchased Flash license is tied to the selected ECU/controller for 72 hours. Some AI operations require a one-time license fee. Monthly Full-access plans can reduce the cost of additional license purchases.
Ready to use Stellacan?
Purchase Full-access or top up license credits from the website before starting a diagnostic session.