FAQ

The application does not start or Windows warns about the file

Current builds are unsigned. SmartScreen may show a warning on first run. Verify that the file came from the official download page, then use More info → Run anyway. The x86 Visual C++ 2015–2022 Redistributable is required.

The application can also run directly from a build folder without installation; project data still goes to the selected workspace and global settings to %APPDATA%\BlackMagic.

My J2534 adapter is not in the list

Install the vendor driver first, then reopen Settings → PassThru Interface. The list is built from the J2534 libraries registered on the system. Switching the driver reconnects the application. If the adapter still does not appear, check that the driver architecture matches the x86 build.

The status bar says connected, but the ECU does not answer

The status only proves that the adapter opened. Check:

• request and response CAN IDs in the ECU definition;
• bit rate (125/250/500/750 kbit/s or 1 Mbit/s) and 11/29-bit mode;
• ignition state and whether another tester holds the session;
• the log for the raw request and the timeout.

DoIP discovery finds nothing

• Confirm that the PC and the vehicle are on the same subnet.
• Check Own IP, Netmask, Destination IP and port 13400.
• Set the Tester Address expected by the vehicle, usually 0x0E80.
• A vehicle may answer only after the ignition is on and the gateway is awake.
• Try ECU Address From / To with Scan if Discover sees nothing.

Security access is rejected

The project needs the correct auth level and Seed2Key DLL in data/auth/. A wrong level or a key computed with a different algorithm produces a negative response. The log contains the response code. Manual seed/key exchange is available in UDS Tools → Authorization 0x27 with Get Seed / Send Key.

A write returns a negative response

Common causes: the ECU is in the wrong session, security access was not performed, the parameter is read-only in the project, or the value length does not match the view. For Writable Values, check writeable: true, the View and the optional write_auth level. Read the parameter back after every successful write.

A parameter is missing from Writable Values

• writeable must be true in .bmecu;
• the parameter must have a View;
• an ioctl parameter with writeable: true also appears in IO Control, using 0x2F there and 0x2E here.

Measurement Values does not draw a graph

• Only uint and int are graphable; ascii, hex, enum and combined show Not graphable.
• No data means the value has not been read; No samples means history has not accumulated.
• After Start, wait at least one polling period.
• If Start is pressed with an empty list, nothing happens.
• A long series of link errors stops the measurement; check the log.

Why does the measurement CSV have no timestamps or header?

That is by design: the file contains "Name","DID","Value Unit" lines for the selected parameters. Use the log for request timing and .bmdump for full state.

Where are the logs?

In <workspace>/logs/. The Log & Console panel shows the same events live. A saved log starts with a [build] line containing the version, configuration and build date.

A DTC shows "Unknown DTC"

The code was read, but no description exists in the loaded database. Add a .json or .txt entry under data/dtc/ or select a local file in Project Properties. TXT lines are CODE description; lines starting with # or ; are ignored.

Does the application need internet?

No. Diagnostics, projects, logs and reports work locally. AI chat needs a configured HTTP endpoint or ACP; MCP clients connect through the local server.

The AI chat does not answer

• Check the backend (HTTP OpenAI-compatible endpoint or OpenCode ACP) and the API key; the key is stored in Windows Credential Manager.
• Look for HTTP: and CHAT: lines in the log.
• A stalled request times out; press Stop and retry.
• Project changes and live ECU writes are separate permissions in Settings → Automation.

Can I move the workspace to another PC?

Yes. Copy the folder and open it as a workspace. ECU files are referenced by name inside the project folder. The global preferences are separate and can be recreated.

The UI is English only — can I use Cyrillic or Chinese data?

Yes. ECU names, DTC descriptions and parameter text in Cyrillic or Simplified Chinese display correctly. The interface labels themselves are English.

Where is the flashing window?

Vehicle-specific flashing modules are included only in builds where that module is present. The generic path is the Lua firmware and flashing API. See Flashing.

How do I report a problem?

The forum is not open yet. For now, keep the session log, the project dump and the exact steps; they are the minimum needed to reproduce a transport or ECU issue.

Related

• Install
• Connect to a vehicle
• File formats