Rebuilding a HALCON workflow around the AI Vision Solver now would be planning too early: MVTec announced it as a prototype for VISION 2026, and its documents reviewed here give no release date, price or licensing. What HALCON users can act on is the separate, scheduled change underneath it: HDevelopEVO arrives as an Early-Adopter version with HALCON 26.11 on 18 November 2026 and, according to MVTec, gradually replaces the current IDE starting in 2027.
If you build or maintain HALCON applications, treat the AI Vision Solver as a preview of direction, not a product to evaluate. MVTec’s 28 September 2026 release describes AI agents that take a task written in plain language plus images, pick HALCON operators, and generate an executable application in HDevelopEVO; the demo examples it names are barcode reading, matching and OCR. As of 7 October 2026, the MVTec documents reviewed give no release date, AI models, hosting (local or cloud) or licensing. The dated item is HALCON 26.11 on 18 November 2026, which brings the HDevelopEVO Early-Adopter version.
In short:
- The AI Vision Solver has no published commercial plan in the documents reviewed.
- The HDevelopEVO Early-Adopter version is planned with HALCON 26.11 on 18 November 2026.
- Now is the time to inventory HDevelop projects and ask MVTec about models, data and licensing.
Product facts come from MVTec’s releases and HDevelopEVO page; the trade-press report rewrites the September release, and we have not used the prototype. This site is an independent publication with no tie to the vendors it covers; see about this site.
What did MVTec announce for VISION 2026?
MVTec announced, in a pre-show release, that it would show an AI prototype, the AI Vision Solver, at VISION 2026 in Stuttgart (6–8 October 2026, Hall 8, booth 8C56). Three days later it announced HALCON 26.11 for 18 November 2026. The two announcements are linked through HDevelopEVO but are not the same thing.
| Event | Date | Source | Nature of source |
|---|---|---|---|
| Press release: AI Vision Solver prototype to be shown at VISION | 28 Sep 2026 | MVTec | Vendor release |
| Press release: HALCON 26.11 release date and HDevelopEVO Early-Adopter version | 1 Oct 2026 | MVTec | Vendor release |
| Trade-press rewrite of the VISION release | 5 Oct 2026 | Instrumentation Monthly | Same release, not an independent check |
| VISION 2026 trade show | 6–8 Oct 2026 | MVTec release | Event |
| HALCON 26.11 release (Progress and Steady editions) | 18 Nov 2026, planned | MVTec | Vendor schedule |
| HDevelopEVO begins gradually replacing the current IDE | From 2027, per MVTec | MVTec | Vendor plan |
Takeaway: Put 18 November 2026 in your calendar for HALCON 26.11; put no date against the AI Vision Solver.
How does the prototype work, according to MVTec?
According to MVTec, a developer describes the task in natural language and with images; AI agents interpret the request, choose operators from the HALCON library, and generate an executable application in HDevelopEVO. The system detects syntax errors and logical gaps and feeds them back to the agents, which revise their result. The agents draw on a knowledge base that MVTec defines and provides.
MVTec also states the limit itself: the AI does not take full responsibility for the industrial application, and the final assessment stays with the user. MVTec says users get shorter development times but gives no figure. The demo examples MVTec names are barcode reading, matching and OCR; other task types are not described.
Common mistake: Treating announced demo examples of barcode, matching and OCR tasks as evidence that the same approach handles your inspection. They are the only scenarios MVTec has named.
However the code is produced, confirm separately how results reach your PLC or plant network; our interface comparison for industrial sensors lists the usual options, and its OPC UA and Ethernet rows cover system-to-system links.
Takeaway: Read the prototype as a description of MVTec’s direction, with validation still on your side.
What has MVTec announced, and what has it not disclosed?
MVTec has announced the concept, demo examples and the IDE it runs in. The commercial and technical details a buyer would check are not in the documents reviewed.
| Announced by MVTec | Not disclosed as of 7 Oct 2026 |
|---|---|
| Prototype status, to be shown at VISION 2026 (pre-show release) | Whether and when it becomes a product |
| Plain-language and image input; agents choose HALCON operators | Which AI models are used |
| Executable application generated in HDevelopEVO | Whether it runs locally, self-hosted or in the cloud |
| Error feedback loop to the agents | How images and code are handled and stored |
| MVTec-provided knowledge base | Price and licensing |
| Demo examples named: barcode reading, matching, OCR | Task scope beyond the named examples |
| User keeps final assessment | Accuracy of generated applications; time saved |
| — | North American availability and support |
The same split between a vendor’s claim and what you can check appears in our BactoSense ID explainer and the profileGAUGE C.ODC spec reading.
Common mistake: Repeating “quantum leap” or “disruptive” from the release as an assessment. They are MVTec’s words, not test results.
Takeaway: Keep every item in the right-hand column on your question list until MVTec answers it in writing.
What changes for HDevelopEVO, and when?
HDevelopEVO is the part with dates. MVTec says it becomes an Early-Adopter version with HALCON 26.11, complements the current HDevelop for now, and is set to gradually replace the current IDE starting in 2027.
| Item | What MVTec says | Planning note |
|---|---|---|
| HALCON 26.11 | Release planned for 18 Nov 2026 in Progress and Steady editions | Steady runs a two-year cycle; Progress a six-month cycle |
| HDevelopEVO Early-Adopter version | Ships with HALCON 26.11 | Does not yet provide the full functionality planned |
| MCP server in HDevelopEVO | Integrated by default; gives the built-in AI assistant broader HALCON knowledge, including operator descriptions | Separate from the AI Vision Solver prototype |
| HALCON Script Engine | Adds multithreading to support migrating parallel applications | Relevant if you run parallel HDevelop programs |
| Free update for 26.11 customers | Planned for 2027; scope and timing to be announced | Needs checking |
| Replacement of the current IDE | Gradual, starting in 2027 | No end date given |
Takeaway: Flag projects with parallel programs or Steady-edition licences; they need the most planning for the IDE change.
Who is affected?
HALCON developers and integrators are affected first, through the IDE change; for buyers of finished inspection systems, the announcements alone do not justify changes to purchases.
| Reader | Impact | Basis |
|---|---|---|
| HALCON application developers | IDE change from 2027; Early-Adopter version from 18 Nov 2026 | MVTec release, 1 Oct 2026; HDevelopEVO page |
| Vision integrators maintaining many HDevelop programs | Migration effort to plan; parallel programs touched by Script Engine changes | HDevelopEVO page |
| Teams using the Steady edition | Two-year cycle; timing of HDevelopEVO adoption to confirm | MVTec release, 1 Oct 2026 |
| Plant engineers buying finished vision systems | Our suggestion: ask your integrator whether its tool plans change project support | MVTec releases (no commercial plan published) |
| Teams with data or cloud restrictions | Model and hosting details not disclosed | MVTec releases |
Takeaway: If you maintain HDevelop code, the IDE dates matter to you now; the AI prototype does not yet.
When should you act?
Act on the HALCON 26.11 schedule, not on the prototype. A short, dated plan is enough.
| When | Action | Status |
|---|---|---|
| Now | List your HDevelop projects, external procedures and any parallel programs | Your data |
| Now | Send MVTec the undisclosed items below | Open |
| From 18 Nov 2026, planned | Try the HDevelopEVO Early-Adopter version on a copy of one project | Planned by MVTec |
| 2027, per MVTec | Watch the scope of the planned free update and the replacement steps | Needs checking |
| When announced | Evaluate the AI Vision Solver, if it becomes a product | No date |
Takeaway: Run one controlled HDevelopEVO trial after 18 November 2026 and keep the AI prototype on a watch list.
What should HALCON users ask MVTec?
Ask about the product plan, the AI models and hosting, data use, licensing and how long the current IDE stays supported. Each item names who can answer.
| Question | Who can answer | What to ask for |
|---|---|---|
| Will the AI Vision Solver become a product, and when? | MVTec | Roadmap statement |
| Which AI models run behind the agents, and where? | MVTec | Architecture and hosting description |
| How are prompts, images and generated code stored and used? | MVTec | Data-handling terms |
| How will it be licensed alongside HALCON editions? | MVTec or your distributor | Licensing terms |
| Which tasks beyond barcode, matching and OCR are supported? | MVTec | Supported-task list |
| How long will the current HDevelop remain supported after 2027? | MVTec | Support policy |
| What does the 2027 free update for 26.11 customers include? | MVTec | Scope announcement |
Takeaway: Get the hosting, data and licensing answers in writing before any AI-assisted workflow touches customer images.
When does this not apply?
- You do not use HALCON; the IDE timeline does not affect you.
- You only buy complete vision systems; your integrator handles the development tools.
- You need a product comparison; this page does not rank vision software.
- You need performance figures; MVTec has published none for the prototype.
Takeaway: Check whether you write HALCON code before spending time on any of this.
Our reading
MVTec’s AI Vision Solver signals where HALCON development is heading: agents that draft applications from a described task, inside an IDE MVTec controls, with the user still accountable for the result. The concrete news for working teams is the Early-Adopter IDE with an AI assistant hooked to HALCON knowledge. Judging the prototype itself has to wait for a product and data. For the vision station’s place in a wider data system, see the machine-vision row in our industrial IoT sensor examples; more articles are under automation, sensors and DAQ and test and measurement.
Takeaway: Separate the dated IDE change from the undated prototype in your planning documents.
Related reading
Next reads for the integration side of a vision project:
- Industrial IoT sensors — Choose outputs and networks for data that leaves the vision station.
- profileGAUGE C.ODC specs — See how a non-camera inline gauge states its accuracy.
- BactoSense ID explainer — Another launch where vendor claims and checkable facts differ.
Takeaway: Start with the interface guide if your vision results must reach a PLC.
Method and update log
Compiled on 7 October 2026 from MVTec’s press releases of 28 September and 1 October 2026 and its HDevelopEVO product page. The Instrumentation Monthly report rewrites the September release and counts as one source. We have not used the prototype. This page will be updated when MVTec announces product details or HALCON 26.11 ships. Last reviewed 7 October 2026.
