6. When a test does not run
The cabinet always shows the exact reason. Most reasons are fixed by changing the file and uploading it again.
6.1. Rejected images
| Reason | What to do |
|---|---|
| The file size does not match any supported unit | Upload a full flash image of the unit (§2.1) |
| The file is not a raw binary image | Upload a .bin file, not HEX, S19 or an archive |
| The software is not on the supported list | Check the Program ID against §1.3 |
| The software is recognized, but there is no vehicle model for it yet | Wait until the vehicle is added to the list |
| The checksums do not match | Correct them and upload again (§2.2) |
| Only stock images are accepted for this software | Upload the stock image |
6.2. Tests that did not finish
| Reason | What to do |
|---|---|
| The vehicle model is temporarily unavailable | Try again later |
| An internal emulator error, or the test took longer than allowed | Start the test again; if it repeats, contact support |
| The tests finished, but the report could not be built | Start the test again; if it repeats, contact support |
| The queue is full | Try again later |
| The limit of tests at a time is reached | Wait until one of your tests finishes (§3.5) |
| The test waited in the queue for more than 24 hours | Start it again |
Updated November 14, 2026 · for TCEPro 0.54.1