{"sections":[{"heading":"Recognise the checked case","paragraphs":["Extraction can finish successfully while warning that no back-annotation was performed. The reproduced warning is: Back-annotate command has moved to the main IXI file \"$CONTROL\" block. Ignored in netlist.","The older manual describes the command in the netlist .control block. The checked 8.0.1 Windows runtime ignores that location. This answer records the tested recovery; it does not assign the same behaviour to every earlier release."]},{"code":"$CONTROL\n  BACK-ANNOTATE \"transfer.cir\"\n$END","heading":"Move the request to the project","steps":["Work on a complete project copy in a fresh writable folder. Keep the existing target JoSIM/SPICE template beside the IXI file.","Remove the legacy BACK-ANNOTATE request from the extraction netlist .control block. Preserve unrelated control statements.","Add the following top-level block to the IXI file, using the actual template filename.","Keep an explicit target element mapping on each extraction branch to be transferred. For the linked example, L1 1 2 3.9e-12 [LTRANSFER] maps extraction L1 onto simulation LTRANSFER.","Run extraction again, inspect warnings and locate the new annotated deck in the run output directory. Compare the mapped value with the new solution before simulation."]},{"heading":"Check the result and remaining causes","paragraphs":["For the checked local template transfer.cir, output/transfer_annotated.cir was created and the original template was unchanged. Its LTRANSFER value agreed with the extraction solution at printed precision; JoSIM then ran that new deck successfully.","If the file is still missing, verify the template exists relative to the IXI project, the requested target name is correct and the output directory is writable. Read the actual licence warning too: current source allows automatic back-annotation for SUPER/QUANTUM, and can skip it when that entitlement is unavailable.","If a new deck exists but an element was not updated, inspect its bracket mapping and the target element name. A successful extraction does not establish that every requested template target was replaced. Use fresh output names so an earlier annotated deck cannot be mistaken for a new result.","Retain version/build identity, the generalised diagnostic, extraction circuit, IXI control block and a shareable template when escalating. Exclude licence details and private fabrication/customer files."]}],"canonical_url":"https://www.sun-magnetics.com/knowledge-base/inductex-backannotation-no-output","url":"/knowledge-base/inductex-backannotation-no-output","known_issues":[{"disposition":"verified_workaround","id":"KB-DOC-001","title":"Back-annotation control location differs from the manual","public_notice":"On the checked InductEx 8.0.1 route, place BACK-ANNOTATE in the main IXI $CONTROL block, preserve the template and verify the fresh annotated deck and mapped values.","claim_scope":"Only the affected claim and recorded build/input; not whole-guide or final-release acceptance"}],"search_record":{"execution":true,"relatedProducts":[],"version_tags":["InductEx 8 preview"],"text":"InductEx finishes but does not create a back-annotated deck On the checked InductEx 8.0.1 runtime, move BACK-ANNOTATE from the circuit netlist into the main IXI $CONTROL block, then verify the template, element mapping and fresh annotated output. InductEx InductEx 8.0.1 Windows CLI Troubleshooting BACK-ANNOTATE backannotate annotated deck missing $CONTROL Ignored in netlist SUPER Recognise the checked case Extraction can finish successfully while warning that no back-annotation was performed. The reproduced warning is: Back-annotate command has moved to the main IXI file \"$CONTROL\" block. Ignored in netlist. The older manual describes the command in the netlist .control block. The checked 8.0.1 Windows runtime ignores that location. This answer records the tested recovery; it does not assign the same behaviour to every earlier release.  Move the request to the project Work on a complete project copy in a fresh writable folder. Keep the existing target JoSIM/SPICE template beside the IXI file. Remove the legacy BACK-ANNOTATE request from the extraction netlist .control block. Preserve unrelated control statements. Add the following top-level block to the IXI file, using the actual template filename. Keep an explicit target element mapping on each extraction branch to be transferred. For the linked example, L1 1 2 3.9e-12 [LTRANSFER] maps extraction L1 onto simulation LTRANSFER. Run extraction again, inspect warnings and locate the new annotated deck in the run output directory. Compare the mapped value with the new solution before simulation. $CONTROL\n  BACK-ANNOTATE \"transfer.cir\"\n$END Check the result and remaining causes For the checked local template transfer.cir, output/transfer_annotated.cir was created and the original template was unchanged. Its LTRANSFER value agreed with the extraction solution at printed precision; JoSIM then ran that new deck successfully. If the file is still missing, verify the template exists relative to the IXI project, the requested target name is correct and the output directory is writable. Read the actual licence warning too: current source allows automatic back-annotation for SUPER/QUANTUM, and can skip it when that entitlement is unavailable. If a new deck exists but an element was not updated, inspect its bracket mapping and the target element name. A successful extraction does not establish that every requested template target was replaced. Use fresh output names so an earlier annotated deck cannot be mistaken for a new result. Retain version/build identity, the generalised diagnostic, extraction circuit, IXI control block and a shareable template when escalating. Exclude licence details and private fabrication/customer files. ","id":"inductex-backannotation-no-output","keywords":"BACK-ANNOTATE backannotate annotated deck missing $CONTROL Ignored in netlist SUPER","kind":"Troubleshooting","title":"InductEx finishes but does not create a back-annotated deck","product":"InductEx"},"version":"InductEx 8.0.1 Windows CLI","id":"inductex-backannotation-no-output","related":["/knowledge-base/cross-tool-extracted-circuit","/knowledge-base/inductex-first-microstrip","/knowledge-base/inductex-missing-input"],"downloads":[],"publication_status":"published","numerical_output":null,"provenance":{"execution_checks":[{"routes":["cli"],"scope":"Legacy-location warning, IXI-control recovery, template-preserving single-L back-annotation and two-step transient handoff","result":"passed","articles":["cross-tool-extracted-circuit","inductex-backannotation-no-output"],"purpose":"cross-tool-backannotation","version":"InductEx 8.0.1 Windows catalog CLI and JoSIM-Pro 2.9.0 Windows review CLI","id":"VAL-013","records":["handoff-inductex-version","handoff-josim-version","handoff-legacy-command-location","handoff-back-annotation","handoff-josim-coarse","handoff-josim-refined"],"limit":"Single ideal branch and CLI routes only. Analytic transient agreement does not establish extraction accuracy, mesh convergence, broadband model validity, subcircuit/coupling back-annotation, GUI or final-package qualification.","observed":{"ramp_voltage_V":0.00019482395315000004,"annotated_inductance_H":3.896479063e-12,"refined_transient_matches_analytic_branch":true,"all_simulation_commands_succeeded":true,"solution_inductance_H":3.89648e-12,"annotated_value_matches_solution_rounding":true,"fresh_extraction_completed":true,"coarse_transient_matches_analytic_branch":true,"annotated_output_created":true,"coarse_samples":1001,"refined_samples":2001,"original_examples_and_executables_preserved":true,"target_template_preserved":true,"legacy_location_warns_without_annotated_output":true}}],"figure_evidence":[],"review_notes":["VAL-013 records the exact Windows CLI scope and executable identities. Final release/platform applicability and any GUI route remain pending.","The older netlist-control instruction conflicts with the checked 8.0.1 runtime. KB-DOC-001 retains the source discrepancy; the knowledge-base steps follow the exercised IXI control path."],"scope":"Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate.","verification_requirements":{"gui_method":"not-required-for-this-answer","illustrations":"not-required-for-this-answer","required":["technical-review","release-applicability","execution","recovery"],"status":"review-incomplete"},"sources":[{"id":"inductex:docs/manual/ix_netlist.tex","section":"Historical BACK-ANNOTATE location, target mapping and annotated filename"},{"id":"inductex:src/Netlist.pas","section":"ReadControlBlock ignored-location warning"},{"id":"inductex:src/IX_FileIn.pas","section":"ReadControlFromIXI current command processing"},{"id":"inductex:src/IX_FileOut.pas","section":"WriteSimDeck entitlement check"},{"id":"validation:cross-tool-windows-20261103","section":"VAL-013: ignored legacy command and successful IXI recovery"}]},"title":"InductEx® finishes but does not create a back-annotated deck","type":"Troubleshooting","markdown_url":"/_functions/kbResource?path=markdown%2Finductex-backannotation-no-output.md","summary":"On the checked InductEx® 8.0.1 runtime, move BACK-ANNOTATE from the circuit netlist into the main IXI $CONTROL block, then verify the template, element mapping and fresh annotated output.","product":"InductEx"}