Subject: Error Analysis: "Protocol Not Found" – Kess V2 Master Date: October 26, 2023 Device: Alientech Kess V2 (Master/Slave Unit) ** Software:** K-Suite (Version subject to specific installation)
Genuine KESS V2 units cost over €1,000. Most hobbyists use clones (China-made). Many clones have poor soldering, counterfeit FTDI chips, or incorrect firmware. These clones often fail to handle modern protocols like CAN FD or DoIP, resulting in protocol errors.
The "KESS V2 protocol not found" error is a solvable puzzle, not a death sentence for your tuning session. By systematically checking ECU selection, hardware integrity, software version, and vehicle gateway restrictions, you can restore communication in 15–30 minutes.
Remember: Always try the same ECU on a bench if OBD fails. If bench works, your OBD wiring or vehicle gateway is the culprit. If bench also fails, your KESS V2 clone may need a firmware rollback or replacement.
Tuning is a game of patience and problem-solving. Master the "Protocol Not Found" fix, and you’ll save hours of frustration and costly tow truck bills.
Have you solved a strange "Protocol Not Found" case? Share your ECU model and fix in the comments below!
When you see the "Protocol Not Found" error on a Kess V2, it essentially means the hardware and the software are having a "handshake" failure
. This usually happens because the tool can't find the specific instructions needed to talk to your car's ECU. Here is a breakdown of why this happens and how to fix it: 1. The SD Card Issue (Most Common)
The Kess V2 stores its protocol files on an internal SD card. Over time, these cards can become corrupted or dislodged.
Open the unit, remove the SD card, and clean the contacts. If the card is dead, it needs to be reformatted with the specific image file for your firmware version (often 5.017). 2. Software & Firmware Mismatch If you are using a newer version of the
software with an older firmware (or a "clone" unit), the software might try to call a protocol that doesn't exist in your hardware’s database.
Stick to the software version that originally came with your device. Avoid updating K-Suite online if you are using a clone tool, as this can "grey out" protocols or lock the device. 3. Missing "Protocols" Folder Sometimes the installation itself is the culprit. If the
folder in your K-Suite directory is empty or missing files, the software has nothing to load. Reinstall K-Suite or manually copy the
folder from your installation CD/download back into the main directory. 4. Vehicle Selection Error Kess V2 is specific. If you select a car model that uses a
protocol, but your specific hardware version doesn't support that protocol family, it will return this error.
Double-check the ECU type (e.g., Bosch EDC17C64) rather than just the car model. Try selecting the ECU directly through the "Protocols" menu rather than the "Car" menu. 5. Grayed Out Options If the protocol appears in the list but is grayed out
, it usually means your device is "out of tokens" or the protocol hasn't been "unlocked" for your specific serial number. Always run K-Suite as an Administrator and ensure your isn't deleting the
files in the protocol folder, as it often flags tuning software as a false positive. or check your specific firmware version
Troubleshooting the "Kess V2 Protocol Not Found" Error: A Complete Guide
If you’re working with a Kess V2 ECU programmer, encountering the "Protocol Not Found" error can be a major roadblock. This message typically pops up when the KSuite software fails to communicate with the hardware or cannot locate the specific instructions required to read or write to a vehicle's ECU.
Whether you are using an original Alientech tool or a Kess V2 Master clone, this guide will walk you through the primary causes and the step-by-step solutions to get your tuning project back on track. What Causes the "Protocol Not Found" Error?
Before diving into the fixes, it’s important to understand why this happens. The error usually stems from one of four areas:
SD Card Corruption: The Kess V2 hardware relies on an internal SD card to store protocol files. If these files are missing or corrupted, the "Protocol Not Found" error is inevitable.
Software/Hardware Mismatch: Using a version of KSuite that is too new (or too old) for your firmware version.
Greyed-Out Buttons: Often, if the protocols aren't "active" in the software, the tool won't see them.
Internet Connectivity: For clone units, being connected to the internet can sometimes "lock" the device or cause protocol synchronization issues. Step-by-Step Solutions 1. Refresh or Replace the SD Card (Most Common Fix)
Most "Protocol Not Found" issues are solved by re-initializing the internal SD card.
The Fix: Open the Kess V2 unit (carefully remove the screws). Remove the small SD card. Format it (FAT32) and reload the clean "SD Card Files" specific to your firmware version (e.g., Firmware 5.017).
Pro Tip: If you are using the original card that came with a clone, consider replacing it with a high-quality, branded 4GB or 8GB card. Cheap cards often fail during data transfer. 2. Check the "Protocols" Folder in KSuite Sometimes the software is looking in the wrong place.
Navigate to your KSuite installation directory (usually C:\KSuite).
Ensure there is a folder named "protocols" and that it isn't empty.
If you recently reinstalled the software, you may need to copy the protocol files from your installation CD or backup folder into this directory. 3. Disable Internet and Antivirus
If you are using a Kess V2 clone, the software can be extremely sensitive.
Internet: Turn off your Wi-Fi or unplug your ethernet cable. Some versions of KSuite try to "call home" to validate protocols; if they reach the Alientech servers with a clone ID, the protocols may be disabled.
Antivirus: Security software often flags the DLL files required for protocols as false positives. Whitelist the KSuite folder or disable your antivirus during the session. 4. Reinstall Visual C++ Redistributables
KSuite relies on specific Windows libraries to execute protocol scripts. If your computer is missing the Microsoft Visual C++ 2005, 2008, or 2010 Redistributables, the software might launch but fail to "find" the protocol logic when you click a vehicle. 5. Check Your Power Supply
Kess V2 needs a stable voltage to communicate with the ECU. If the vehicle's battery is low or the USB cable is faulty, the handshake might fail, resulting in a generic "Protocol Not Found" or "Connection Not Established" error. Always use a battery maintainer when flashing an ECU. When to Seek Professional Help
If you have reformatted the SD card, reinstalled KSuite, and checked your cables but still see the error, your NXP chip (the "brain" of the Kess V2) may be locked or damaged. At this stage, the device might need to be reflashed with a J-Link programmer, or the chip might need replacement.
The "Kess V2 Protocol Not Found" error is rarely a sign of a broken tool; it’s usually a data synchronization issue. Start with the SD card—it is the heart of the device's protocol library. Keep your files organized, stay offline if using a clone, and ensure your Windows environment has the necessary libraries to run the software.
Are you seeing this error on a specific vehicle model, or does it happen with every car you try to connect to?
The "Protocol not found" or "Invalid protocol" error on a KESS V2 device is typically caused by a corrupted microSD card on the unit's internal board or a mismatch between the firmware and software versions. Most Common Fixes kess v2 protocol not found
Rewrite the MicroSD Card: The most effective solution is to remove the internal microSD card and rewrite it with a fresh image. For "Red Case" clones, the image size should be exactly 69 megabytes; smaller images often cause "Protocol not found" or "Wake-up" errors.
Check Hardware Integrity: Inspect the internal board for loose or poorly soldered chips (especially the NXP chip) that may prevent the device from reading the SD card properly.
Software Clean Install: If the error states "Protocol not compatible with version FW," follow these steps: Disconnect the internet. Uninstall current K-Suite software and drivers.
Reinstall a compatible version (e.g., K-Suite 2.06 or 2.23, depending on your firmware) along with Microsoft Visual C++ 2005 SP1. Troubleshooting Steps
SD Card Slot: Clean the card slot and ensure the card has proper contact. Some users find that simply reseating the card resolves temporary read errors.
Power Supply: Ensure your vehicle battery is stable or connected to a charger, as low voltage can trigger communication protocols to fail during the "wake-up" phase.
Connectivity: If the protocol fails specifically over K-Line, try connecting via CAN bus if the ECU supports it, as some clone devices have weak K-Line drivers.
For detailed visual instructions on rewriting the SD card, you can view this repair guide on YouTube.
Are you using a clone or original device, and which K-Suite version are you currently running?
The "Protocol Not Found" error in KESS V2 usually indicates a failure to read the device's internal SD (TF) card or a corruption of the firmware/files stored on it
. This is a common issue with "clone" units when the card becomes loose or degraded over time. Quick Fix Checklist Reseat the SD Card
: Open the KESS V2 casing, remove the internal SD card, clean the contacts, and reinsert it firmly. Hardware Inspection
: Check the SD card slot pins on the PCB. In some units, the soldering is poor and may need a quick touch-up with a soldering iron. Software Compatibility
: Ensure you are using the correct KSuite version for your firmware (e.g., KSuite 2.23 or 2.80 for firmware 5.017). Full Repair Procedure (SD Card Reflash)
If the card is corrupted, you must re-image it. Simply copying files is often insufficient because the card contains hidden partitions or specific file structures. Get a New Card : Purchase a high-quality 2GB or 4GB industrial-grade SD card
. Avoid larger cards (like 32GB+), as they may not be compatible with older firmware. Format and Re-image : Use a tool like BalenaEtcher to write a clean image file ( ) to the card. Update Tool
: Some repairs require running an "Update Tool" within KSuite while the device is connected to refresh the protocols. Troubleshooting Scenarios Likely Cause Greyed out protocols SD card files missing or corrupted Reflash the SD card with a clean image. "Wake Up Error" Poor connection to ECU or SD card Check cables and check the SD slot's metal shrapnel. Device not detected Driver or USB port issue
Reinstall drivers or try a Windows 7 machine (legacy support).
: If you are using a genuine Alientech device, do not attempt to open it or reflash the card yourself; contact Alientech Support to avoid voiding your warranty. step-by-step guide for a particular firmware version?
If none of the above works, capture the OBD traffic.
Result interpretation:
Q: Can a low car battery cause "Protocol Not Found"?
A: Yes. Below 11.5V, many ECUs go into power-save mode and disable OBD communication. Always connect a charger.
Q: Does KESS V2 support CAN FD protocol?
A: Only genuine KESS V3 or KESS V2 with latest firmware (2.50+) supports CAN FD. Clones will show "Protocol Not Found" on CAN FD cars.
Q: How do I know if my ECU requires a gateway bypass?
A: If you try 3 different tools (KESS, K-TAG, PCMFlash) and all say "no communication," your vehicle has an active gateway.
Q: Is there a software patch to force a protocol?
A: Yes. In C:\Alientech\KSuite\System\ProtocolOverride.ini, you can manually assign a protocol. Use this only if you know the exact protocol (e.g., ISO15765-4, 11bit ID, 500kbps).
If none of the above works:
Note for clone users: The "protocol not found" error is extremely common with cheap KESS v2 clones because the manufacturer never fully reverse-engineered the protocol detection. Many users report that switching to Kess v2 5.017 or 5.029 firmware (clone-specific) helps, but results vary.
If you need a specific fix for your vehicle model (e.g., VAG EDC17, BMW MSV90), provide the ECU details for targeted advice.
The "Protocol Not Found" error in KESS V2 often indicates a mismatch between the hardware's firmware and the software version, or a failure in the device's internal storage. Why Does This Error Happen?
SD Card Corruption: The microSD card inside the KESS V2 main board may have failed or corrupted files. This card stores the protocol data; if it can't be read, the software can't find the protocols.
Incompatible K-Suite Version: Using a software version (like K-Suite 2.80) that is too new for your firmware (like 5.017) can lead to greyed-out or missing protocols.
Missing System Files: Your PC might lack necessary drivers or "patch" files, preventing the software from communicating properly with the device.
Internet Interference: For clone devices, connecting to the internet can sometimes lock the device or cause it to lose protocol licenses. How to Fix the "Protocol Not Found" Error 1. Refresh or Replace the Internal SD Card
This is the most common fix. Many original cards in clone devices are low quality and fail.
Open the KESS V2: Carefully unscrew the casing to access the green or red PCB. Locate the MicroSD Card: Remove it from the slot.
Rewrite the Card: Use a high-quality 2GB or 4GB brand-new TF card. Format it and write the specific protocol image files (often found in "Token Reset" folders or provided by vendors) using an image-writing tool.
Hardware Check: While inside, ensure the chip near the SD card slot is properly soldered and hasn't come loose. 2. Reinstall Software and Drivers
A clean installation can resolve "Protocol not compatible with version FW" errors.
Disable Internet: Ensure your computer is offline before starting.
Uninstall Everything: Remove the current K-Suite and all USB drivers. Connect a CAN logger (e
Install K-Suite 2.06 (or lower): Start with an older, stable version including the USBDEVICEDRV 1.00.011 and Microsoft Visual C++ 2005 SP1.
Manual Update: Once the base version works, you can sometimes manually copy files from newer versions into the installation folder to "unlock" more protocols without a full update. 3. Fix Greyed-out Protocol Buttons If you see the protocols but can't click them:
Re-launch without Skipping: When opening K-Suite, do not click "SKIP" on the loading screen. Let it finish its check to properly initialize the tool.
Reset Tokens: Some versions of KESS V2 hide protocols once the "token" count reaches zero. You may need to use a token reset tool or replace the SD card files to reset the count. Quick Troubleshooting Checklist
KESS v2 Protocol Not Found: A Comprehensive Guide to Troubleshooting and Solutions
The KESS v2 (K-Line Emulated Software System) protocol is a widely used communication standard in the automotive industry, particularly for diagnostics and reprogramming of vehicle control units (ECUs). However, encountering a "KESS v2 protocol not found" error can be frustrating for technicians and enthusiasts alike. This blog post aims to provide an informative overview of the KESS v2 protocol, common causes of the error, and step-by-step troubleshooting guides to help you resolve the issue.
What is KESS v2 Protocol?
KESS v2 is a software system developed by Alientech, a leading provider of automotive diagnostic tools. The protocol emulates the K-line communication standard, which is used for diagnostics and reprogramming of ECUs in modern vehicles. KESS v2 allows users to connect to a vehicle's ECU, read and write data, and perform various diagnostic functions.
Causes of "KESS v2 Protocol Not Found" Error
The "KESS v2 protocol not found" error typically occurs when the software is unable to establish a connection with the vehicle's ECU. Some common causes of this error include:
Troubleshooting Steps
To resolve the "KESS v2 protocol not found" error, follow these step-by-step troubleshooting guides:
Conclusion
The "KESS v2 protocol not found" error can be a challenging issue to resolve, but by understanding the causes and following the troubleshooting steps outlined in this blog post, you can diagnose and fix the problem. Remember to always verify hardware connections, check software configuration, and ensure ECU compatibility to prevent future errors. If you're still experiencing issues, consult the manufacturer's documentation or contact their support team for further assistance.
Additional Resources
By following this comprehensive guide, you'll be well-equipped to troubleshoot and resolve the "KESS v2 protocol not found" error, ensuring efficient and effective diagnostics and reprogramming of vehicle ECUs.
The "Protocol not found" error in KESS V2 usually stems from corrupted data on the internal microSD card or a version mismatch between your hardware and software. Common Fixes
Rewrite or Replace the MicroSD Card: The most effective solution is rewriting the internal SD card with a working image or replacing it with a high-quality (Class 10) card.
Version Synchronization: If you see "Protocol not compatible with version FW," you may need to install an older K-Suite version first (like 2.06), update it to 2.08 using files from a "Token Reset" folder, and then move to newer versions.
Hardware Inspection: A loose chip or poor soldering on the main board can prevent the device from reading the SD card programs, leading to protocol errors.
Driver Reinstallation: Ensure drivers from the "ksuite" folder are correctly installed. Some users find success by restarting their PC and enabling "Airplane Mode" to prevent the software from checking for online updates. Troubleshooting Resources
Otomotiv Forum: Offers specific advice on replacing "Chinese junk" SD cards with 4-16GB high-speed versions.
OBDExpress Guide: Provides a step-by-step walkthrough for clearing the file path and updating FW protocols.
YouTube Fix Video: Visual guide on rewriting the microSD card located on the electronic board.
Are you using a clone or original device, and which firmware version (e.g., 5.017) is currently shown in your K-Suite? Fix "Protocol not found" error on KESS V2
The "Protocol Not Found" error on KESS V2 typically indicates a communication failure between the K-Suite software and the device's internal firmware or microSD card
. This often happens due to corrupted files on the card, a faulty microSD card, or software version mismatches. Step 1: Basic Software Troubleshooting
Before opening the device, ensure the software environment is stable: Disable Internet
: Many KESS V2 clone devices will "lock" or lose protocol access if they connect to the internet while the K-Suite software is running. Reinstall K-Suite
: Uninstall your current software and drivers. Reinstall a compatible version (e.g., K-Suite 2.08 or 2.11) with the internet disconnected. Check Drivers : Ensure the USBDEVICEDRV is correctly installed through your device manager. Step 2: Replace or Rewrite the MicroSD Card
This is the most common fix for "Protocol Not Found". The internal card holds the protocol libraries; if these are missing or corrupted, the software cannot see them. Open the KESS V2 Unit
: Carefully unscrew the casing to access the electronic board. Remove the MicroSD Card : Locate the TF/microSD card slot on the main board. Use a New Card
: It is highly recommended to use a brand-new 2GB or 4GB TF card rather than re-formatting the old one. Rewrite Firmware Files Use a tool like HDD Raw Copy Tool
to write the correct image file for your firmware version (e.g., FW 5.017) onto the card. Alternatively, format the card to and copy the required folders ( ) into the root directory. Re-insert and Sync
: Place the card back into the KESS V2 and launch K-Suite. The software should automatically begin updating the protocol families. Step 3: Check Hardware Connections
If software and SD card fixes fail, the issue may be physical: Fixing KESS V2 Wake Up Errors | PDF | Computers - Scribd
The "Protocol not found" or "Protocol not compatible" error on KESS V2 typically indicates a mismatch between the software version and the device firmware, or a corrupted internal SD card. Quick Fixes
Disable Internet: Always run K-Suite with your internet connection turned off and antivirus disabled, as these can interfere with or delete essential patch files.
Driver Check: Ensure drivers from the KSuite/Drivers folder are correctly installed. Sometimes re-installing them while in "Airplane Mode" and restarting the PC resolves connection issues. Core Solution: The "Clean Install" Method
If the error persists, you likely have a file mismatch. This guide helps align your software version with your firmware: Result interpretation :
Uninstall Everything: Remove the current K-Suite software and all associated USB drivers.
Install Base Version: Install K-Suite 2.06 Full Version (including Microsoft Visual C++ 2005 SP1). Do not connect the KESS device yet.
Configure Environment: Open the installed K-Suite, select your language, and then immediately close it. Patch the Folder:
Right-click your K-Suite desktop icon and select Open file location. Delete all files inside this folder.
Copy all contents from your "Token Reset" or "K-Suite 2.08" folder and paste them into the empty directory.
Copy the Help folder from your original CD and paste it there as well.
Connect Device: Plug in your KESS V2 via USB and let Windows automatically install the drivers before launching the software. Hardware Solution: SD Card Recovery
If the above fails, the internal 2GB TF (MicroSD) card inside the KESS unit may be corrupt:
Replace the Card: Use a 100% brand new 2GB TF card (do not reuse formatted cards).
Rewrite Image: You must rewrite the firmware image to the SD card. This often requires specific image files (.img) and a key file (.key) specific to your firmware version (e.g., v5.017).
Tools: Use a tool like XorFiles or a dedicated SD formatter to prepare the card before inserting it back into the KESS electronic board. Summary Table: Error Scenarios Likely Cause Primary Action Protocol Not Found Software/Firmware Mismatch Follow "Clean Install" steps Invalid Protocol Corrupt SD Card Replace and rewrite internal MicroSD Connection Not Established Driver or Port Conflict Reinstall drivers in Airplane Mode Fix "Protocol not found" error on KESS V2
If you see the "Protocol Not Found" error on your KESS V2 device,
it usually means there is a mismatch between the software database, the firmware on the SD card, or the physical connection to the vehicle 1. Check SD Card Integrity
The KESS V2 stores its protocol library on an internal SD (TF) card. If this card is corrupted or loose, the device cannot "find" the necessary protocols to communicate with the ECU. Reseat the Card
: Open the KESS V2 casing and carefully remove and re-insert the SD card. Clean the Pins
: Use a brush or contact cleaner on the card slot's shrapnel to ensure a solid connection. Format and Reflash
: If the error persists, you may need to format the SD card (FAT32) and copy the protocol files back onto it. Do
place files inside a new folder; they must be in the root directory. 2. Verify Software Version (KSuite)
This error often occurs when you are using a newer version of KSuite than your firmware supports. Match Versions
: Ensure your KSuite version is compatible with your hardware (e.g., KSuite 2.23 vs. 2.47/2.80). Internet Connection
: Disable your internet connection and antivirus before launching the software, as these can block or delete the protocol drivers required for operation. 3. Connection and Power Issues
If the hardware cannot "wake up" the ECU, it may report that the protocol is not found. Voltage Check
: Ensure the vehicle battery is stable (at least 12.5V–13V). Low voltage can cause communication timeouts that trigger protocol errors. Wake Up Error
: If you see "Wake up error" alongside protocol issues, it may indicate a soldering problem on the main board, specifically the four pins of the chip responsible for reading the SD card. 4. Vehicle Compatibility Unsupported ECU
: Double-check that the specific ECU and vehicle model are listed in your device's supported list. If the ECU is too new for your firmware version, the protocol simply won't exist in the database. Further Exploration Read a technical walkthrough on solving KESS V2 "Wake Up" and SD card errors Learn about common protocol failure causes in tuning tools HP Tuners Support What is the exact firmware version of your KESS V2, and which vehicle model/ECU are you trying to read? Fixing KESS V2 Wake Up Errors | PDF | Computers - Scribd
If you are a professional tuner or a car enthusiast using the Alientech KESS V2, seeing the "Protocol Not Found" error can be incredibly frustrating. This specific error message typically pops up when you attempt to communicate with an ECU (Engine Control Unit), effectively halting your remapping or diagnostic work.
Understanding why this happens is the first step toward a solution. Here is a comprehensive guide on diagnosing and fixing the KESS V2 "Protocol Not Found" error. Common Causes for the Error
Hardware Connection IssuesThe most frequent culprit is a physical connection problem. If the OBD-II cable is loose, or if the USB cable connecting the KESS V2 unit to your laptop is faulty, the software will fail to identify the necessary communication protocol.
Outdated Software or FirmwareKESS V2 relies on a synchronization between the K-Suite software version and the firmware on the device. If you are trying to work on a newer vehicle model but your software hasn’t been updated, the specific protocol for that ECU might not exist in your current database.
Incompatible ECU or Missing SubscriptionIf you are using an original Alientech tool, your protocols are tied to an active subscription. If the subscription has lapsed or if the specific protocol for that car hasn't been purchased/downloaded, you will receive this error. For those using clone devices, this error often occurs when trying to access grayed-out protocols that the hardware version doesn't support.
Incorrect Vehicle SelectionSometimes the error is as simple as human error. Selecting the wrong engine code, ECU type (e.g., Bosch EDC17 vs. EDC16), or year can lead the software to look for a protocol that doesn't match the hardware it's plugged into. Troubleshooting Steps
Check Physical ConnectionsDisconnect and reconnect all cables. Ensure the pins in the OBD port are not bent or recessed. If possible, try a different USB cable, as the ones provided with many units are often of lower quality and prone to interference.
Verify the ECU TypeDon't rely solely on the K-Suite car list. Physically check the label on the ECU if possible. Many car models use different ECU manufacturers depending on the specific production month or region. Ensure you are selecting the exact protocol mentioned on the ECU sticker.
Voltage StabilityThe KESS V2 requires a stable voltage to communicate with the ECU. If the vehicle battery is low (below 12.5V), the protocol handshake may fail. Always use a high-quality battery maintainer or charger while performing tuning operations.
Software Update and ReinstallationIf you are using an authentic tool, ensure K-Suite is updated to the latest version. If you are using a clone, try "Updating" the protocols folder by copying a known working "Protocols" directory into your K-Suite installation folder (be careful, as this can sometimes brick clone units if done incorrectly).
Check the SD CardThe KESS V2 unit contains an internal SD card where protocol data is stored. Over time, these cards can become corrupted or vibrate loose. Some users find success by opening the unit, removing the SD card, cleaning the contacts, or replacing it with a high-quality industrial-grade SD card loaded with the correct files. The Clone vs. Original Factor
It is important to note that "Protocol Not Found" is a hallmark issue for "Red PCB" or "Green PCB" clone units. These devices often claim to be "Master" versions with all protocols unlocked, but the internal components often lack the necessary chips to handle specific communication lines (like K-Line or CAN-bus) for certain vehicles. If you consistently get this error on a specific set of cars, it is likely a hardware limitation of the clone device. Conclusion
The KESS V2 "Protocol Not Found" error is usually a bridge between a hardware limitation and a software mismatch. By systematically checking your connections, ensuring your battery voltage is high, and verifying that you’ve selected the correct ECU type, you can resolve the majority of these issues.
If you'd like to troubleshoot a specific vehicle or ECU model: Provide the car make, model, and year Share the ECU brand and model (e.g., Bosch EDC17C64) Mention if you are using an original or clone device
Advanced users can force a protocol by editing the protocol.ini file inside the KSuite folder. You need to know the exact ECU ID.
Example: For a Bosch MED9.1, you can manually add:
[ECU_XXXX]
Protocol = CAN_11bit_500k
EcuID = 0x1234
Warning: This is risky. One wrong setting can corrupt the ECU.