InductEx® · Get started
Run your first microstrip extraction in Studio
Copy the complete microstrip example to a writable folder, open microstrip.ixi, check its inputs and run the extraction from Studio.
Read guide →PRACTICAL GUIDANCE
Find setup instructions, complete examples and troubleshooting guidance for our tools. Start with your task, then check the version and expected result before applying the steps to your own model.
125 guides
InductEx® · Get started
Copy the complete microstrip example to a writable folder, open microstrip.ixi, check its inputs and run the extraction from Studio.
Read guide →InductEx® · Worked example
This parameterised example uses inline IXI geometry and EQS mode to calculate capacitance between two labelled conductors. It does not require a circuit netlist.
Read guide →InductEx® · Troubleshooting
Select an IXI project, check its inputs and licence, and resolve the issues reported by Check and run.
Read guide →InductEx® · Troubleshooting
Check the file reference relative to the saved IXI project. Copy the complete example directory so its referenced inputs remain together.
Read guide →JoSIM®-Pro · Get started
Open the installed JTL_Example.cir netlist, run it and inspect the resulting traces. The manual recommends this self-contained example for a first simulation.
Read guide →JoSIM®-Pro · Troubleshooting
Check the License Manager, configured licence path and service availability. Correct the reported issue, then retry the licence check before simulating.
Read guide →JoSIM®-Pro · Troubleshooting
Check the .include reference and preserve the files used by the project. The installed AND example requires base_cells.cir alongside the main example.
Read guide →Shared licensing · Troubleshooting
Check the licence file, product grant and daemon status separately. A responding local daemon does not establish that a particular product is authorised.
Read guide →Shared licensing · Troubleshooting
The daemon setting identifies an executable; the licence setting identifies a file. Keep these paths separate and use absolute paths.
Read guide →Shared licensing · Troubleshooting
Generate the identifier on the intended host and in the account/context that will run the software. Transfer the generated file digitally through private support.
Read guide →Shared licensing · Troubleshooting
Check active licensed work and broker status. An interrupted session can retain a seat until its lease is released or expires.
Read guide →Shared licensing · Troubleshooting
Separate local broker discovery from outbound HTTPS, proxy and certificate problems. Use the underlying error to choose the next check.
Read guide →Shared licensing · Troubleshooting
Finish dependent jobs and restart the broker through the supported upgrade procedure. Replacing files does not update an existing process.
Read guide →Shared licensing · Troubleshooting
Install the target-platform package and check entitlement for the new context. Copying an executable or an old key does not establish that it will be licensed there.
Read guide →InductEx® · Troubleshooting
InductEx® Core and Studio request a TTH product grant. Check that grant and the running daemon's support for additional licence files.
Read guide →InductEx® · Troubleshooting
Read the earliest failure in the current run log. A missing intermediate file can be a consequence of an earlier failure to reach the solver.
Read guide →InductEx® · Troubleshooting
Check the extraction cell, text-layer definition and whether the labels are inside child cells.
Read guide →InductEx® · Troubleshooting
Inspect the terminal geometry and the electrical path it actually excites. Check version-specific modelling rules before changing mesh settings.
Read guide →InductEx® · Troubleshooting
Check agreement between the circuit model and layout, port orientation, coupling and solution quality before accepting the extracted element values.
Read guide →InductEx® · Explanation
Historical output uses a combined series branch when the individual component values cannot be identified independently.
Read guide →InductEx® · Troubleshooting
Compare the exact inputs, process, engine versions and meshing settings before assuming a regression.
Read guide →InductEx® · Troubleshooting
Use controlled refinement and solution-quality checks. More elements alone do not establish a more accurate or stable extraction.
Read guide →InductEx® · Troubleshooting
Review the complete manufactured stack and via rules. A new resistor or isolation layer can change connections elsewhere in the model.
Read guide →InductEx® · How to
Sigma is bulk conductivity in inverse ohms per model length unit. Convert thickness to the LDF length unit before using sheet resistance.
Read guide →InductEx® · Troubleshooting
Use the actual dielectric stack and extraction mode. Check EpsilonR and the environment above and below the structure.
Read guide →InductEx® · How to
Mark auxiliary ground-plane layers with the documented IsGP parameter and check their actual geometry and connections.
Read guide →InductEx® · Troubleshooting
Check the failing executable and its required runtime against the supported package target. A newer OS name or copied binary does not guarantee ABI compatibility.
Read guide →InductEx® · Troubleshooting
First establish whether the licence is valid for the current host. Historical path lookup and installation settings differ from InductEx® 8.
Read guide →JoSIM®-Pro · Troubleshooting
Check installation features and use the provided Linux wrapper. GUI shortcuts and command-line PATH discovery are separate concerns.
Read guide →JoSIM®-Pro · Troubleshooting
Save the path with the documented CLI option alone, then restart the GUI. Combining the path-setting command with version display prevents it being saved.
Read guide →JoSIM®-Pro · Troubleshooting
Check .MODEL spelling, model names and parameters before changing device physics or simulation settings.
Read guide →JoSIM®-Pro · Troubleshooting
Check the complete inductance matrix for passivity. Keeping each coupling factor between -1 and 1 is necessary but does not guarantee a valid multi-inductor model.
Read guide →JoSIM®-Pro · Troubleshooting
Reduce the circuit and check its reference, topology, model values and initial conditions before treating the error as a numerical tuning problem.
Read guide →JoSIM®-Pro · Troubleshooting
Distinguish thermal-noise settings from an explicit NOISE waveform and from temperature-dependent junction model parameters.
Read guide →JoSIM®-Pro · Explanation
Check the selected junction model and RTYPE. Noise temperature and temperature-dependent junction behaviour are separate settings.
Read guide →JoSIM®-Pro · Explanation
The maintained syntax documents explicit line models with different assumptions. Match the physical model and data format before planning a simulator handoff.
Read guide →JoSIM®-Pro · Troubleshooting
Use the documented analysis/integration combination and check whether the selected line model supports variable stepping.
Read guide →General support · How to
Include the first error, exact environment and a minimal reproducible example. Review logs and bundles before sharing them privately.
Read guide →Optimum™ · Explanation
A margin is defined by its acceptance rule. Compare the verification criteria, time resolution and nominal pass before comparing percentages.
Read guide →Optimum™ · Get started
Use the CLI for verification and margin analysis, then inspect generated results in the GUI. Keep the TOML configuration and referenced inputs together.
Read guide →General support · Troubleshooting
Find the executable selected by your shell, then check its version. Multiple installations can leave a legacy directory earlier on PATH.
Read guide →InductEx-LVS™ · Get started
Run the complete shipped JTL example, read the current comparison report and keep topology success separate from process exit status, graph rendering and electrical accuracy.
Read guide →InductEx-LVS™ · Troubleshooting
Check the graph-output switches and Graphviz path separately from the connectivity result.
Read guide →InductEx-LVS™ · Troubleshooting
A reduced circuit can use a different basis from the drawing. Inspect connectivity, coupling thresholds and the validation report before redrawing the model.
Read guide →TetraHenry® · Explanation
The documented TetraHenry® entry file is JSON. It connects the mesh to materials, excitation, calculation settings and outputs.
Read guide →InductEx® · How to
Keep the calibration source, process revision and model assumptions with each result. A file with the same layer names is not necessarily the same physical model.
Read guide →JoSIM®-Pro · Explanation
Check the model-card critical current and effective instance area. Instance IC can select a scale factor rather than changing only one isolated value.
Read guide →JoSIM®-Pro · Troubleshooting
Choose a separate results filename. The checked CLI and current-source GUI run reject identical input and output paths to preserve the netlist.
Read guide →InductEx® · How to
Create a draft IXI, supply the complete physical inputs, and preserve or repair its references when saving elsewhere or copying the project.
Read guide →InductEx® · How to
Match the requested quantity to its formulation and electrical declarations. Inspect what a mode change actually edits, then verify the corresponding model before solving.
Read guide →InductEx® · How to
Run a saved project through Initialise / Reset, Premesh, Mesh and Run solver; inspect the current generated mesh and rebuild the staged session after source edits or restart.
Read guide →InductEx® · How to
Start with the IXI Results page and current Output Log, then open the associated numerical files through Artifacts. A file left in the output directory may belong to an earlier run.
Read guide →InductEx® · How to
Use the S-Parameters view for the intended response, select traces and a frequency band, then export PNG for a figure or CSV for complex numerical samples.
Read guide →InductEx® · How to
Open generated mesh or VTK field output in Studio. Group visibility, clipping and display controls help inspect the model; they do not refine the numerical calculation.
Read guide →InductEx® · How to
Run a complete saved teaching model in a fresh directory, record the actual CLI/solver identities and accept only current checked artifacts and diagnostics.
Read guide →InductEx® · How to
Record the process outcome and the printed controlled diagnostic separately. Use the current log and complete documented reference to choose the correction.
Read guide →JoSIM®-Pro · How to
Run the intended josim-pro-cli executable on a complete working copy of the netlist and select an explicit numerical output filename with -o.
Read guide →JoSIM®-Pro · How to
Make the matching josimpro extension importable, construct Input and Matrix from a saved circuit, validate readiness and execute Simulation.
Read guide →JoSIM®-Pro · How to
Inspect the resolved plan, choose explicit overrides only where intended, and verify fresh numerical output with a complete three-case Python example.
Read guide →JoSIM®-Pro · How to
Run simulation from a netlist tab and resolve save/external-change decisions first. Imported result files can be inspected but cannot be simulated.
Read guide →JoSIM®-Pro · How to
Open Plot export studio from the waveform/result view. Choose a figure format for presentation or CSV/TSV to retain numerical trace data.
Read guide →JoSIM®-Pro · How to
Find current source and include problems, follow their exact locations, and distinguish a clean check from filtered-empty, stale or incomplete results.
Read guide →JoSIM®-Pro · How to
Arrange a complete RC hierarchy, save scope-specific layout comments and export the intended schematic; keep circuit statements, numerical results and reproduced visualizer limits separate.
Read guide →InductEx® · How to
Install the shared licence daemon and the Windows MSI, start InductEx® Studio, then check the installation with a writable copy of the microstrip example.
Read guide →InductEx® · How to
Use the supplied package for your distribution, launch Studio through its installed entry and run copied examples from a writable directory.
Read guide →InductEx® · How to
Install the daemon and the matching macOS package, open the installed Studio application and copy the complete example before generating results.
Read guide →JoSIM®-Pro · How to
Install the supported License Manager and Windows MSI, select the shortcut/PATH options you need, then check a copied JTL example.
Read guide →JoSIM®-Pro · How to
Install the supplied DEB or RPM with dependency resolution, then start JoSIM®-Pro through josim-pro-gui or its desktop entry.
Read guide →JoSIM®-Pro · How to
Use the supplied package for your Mac architecture, open JoSIM®-Pro.app or its GUI wrapper, and validate a copied first circuit.
Read guide →JoSIM®-Pro · How to
Use Results for stored solver-state arrays and Output for named traces and their formatted time axis. Keep each set of values with its matching axis before exporting or plotting.
Read guide →General support · How to
Map each extraction branch to the intended simulation element, retain its physical units and use a new annotated simulation deck. The worked example transfers one microstrip inductance and checks its transient voltage.
Read guide →InductEx® · Troubleshooting
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.
Read guide →JoSIM®-Pro · How to
Start with a small circuit containing sources, components, analysis and output requests. Save a complete plain-text deck, run it to a separate result file and check quantities against a simple reference.
Read guide →JoSIM®-Pro · How to
Define the cell pin order and a named parameter, reference that parameter inside the cell, then set it on the intended X instance. Keep the library beside the main deck and inspect instance-specific output.
Read guide →JoSIM®-Pro · How to
Refine the integration step while keeping a common output grid, then compare the quantities that matter. A denser plot export alone does not establish a more accurate simulation.
Read guide →JoSIM®-Pro · How to
Add named .MEASURE TRAN statements to a buffered transient run. Read their values and units from the normal diagnostic output, and handle missing events as failed measurements.
Read guide →JoSIM®-Pro · How to
Use a nonzero fixed seed, preserve the complete input/settings/runtime and compare the same named traces on the same time grid. Seed zero requests automatic seeding.
Read guide →JoSIM®-Pro · How to
Choose explicit CSV/DAT destinations for streamed text, use gzip for supported text output, and distinguish file output from retaining interactive GUI arrays.
Read guide →JoSIM®-Pro · How to
Declare global parameters, add .STEP LIST or linear dimensions, preview the expanded cases and retain each case’s assignments, seed and output identity.
Read guide →JoSIM®-Pro · How to
Pair .MEASURE TRAN statements with a josim-testbench/1 JSON definition, write each run to a new directory and inspect the completed report and process verdict.
Read guide →JoSIM®-Pro · How to
Use standalone .OP for one equilibrium or .DC for independent source-bias points. Inspect scalar values or the swept-source axis; these are not time-domain or hysteresis results.
Read guide →JoSIM®-Pro · How to
Use one .AC analysis, explicit nonzero AC source attributes and .PRINT AC selectors. Read magnitude and phasor angle against frequency, while retaining typed real/imaginary data for numerical work.
Read guide →InductEx® · How to
Build a complete three-file MQS strip using explicit IXI variables, a teaching process and matched circuit ports, then check the current extraction.
Read guide →InductEx® · How to
Separate layout layer numbers, stack order, physical dimensions, material properties and result units using a complete three-layer teaching example.
Read guide →InductEx® · How to
Describe the branch model and port-to-node topology that InductEx® fits, with consistent design units and a complete microstrip netlist.
Read guide →InductEx® · How to
Connect each named port to its positive/negative material layers, an actual terminal edge and the corresponding circuit nodes.
Read guide →InductEx® · Troubleshooting
The checked Studio candidate can retain the earlier Completed result after a saved source edit. Save the intended inputs, use Run again and check the new verdict and values.
Read guide →InductEx® · How to
Refine a complete fixed MQS example in separate directories, compare current inductance and diagnostics, and measure the cost before choosing the next mesh.
Read guide →InductEx® · How to
Prepare the visible mesh, export its canvas as PNG and check the companion report. If the destination fails, choose an existing writable folder and retry without rerunning the calculation.
Read guide →InductEx® · How to
Request B and J from a complete MQS strip, inspect the emitted excitation arrays in Studio and choose field displays and ranges with their coordinate and metadata limits explicit.
Read guide →InductEx® · How to
Inspect the layout layers, replace a plain-TEXT port label, save a complete derived project and recover its matching netlist. Decorated-text limits remain explicit.
Read guide →JoSIM®-Pro · How to
Build a complete C11 or C++17 client, run a circuit, read named transient arrays and release owned handles. Matching SDK components and current error diagnostics keep integration predictable.
Read guide →Optimum™ · How to
Select a consumed parameter, verify the nominal circuit and read both margin sides against known bounds. Search resolution, parameter dependence and verification tolerances have distinct roles.
Read guide →Optimum™ · How to
Define the acceptance rule and three-sigma spread, run a finite seeded sample population and distinguish its observed pass fraction from model probability and fabrication yield.
Read guide →Optimum™ · How to
Search for a better critical-margin centre, inspect the stopping outcome and separately verify the numeric circuit that was actually saved.
Read guide →Optimum™ · How to
Use the native C API from a complete Python client, distinguish readiness from execution and handle owned study results and verified artifacts without parsing console summaries.
Read guide →InductEx® · How to
Sweep a complete microstrip teaching model over length and width, retain each extraction and reject incomplete studies. Recognise the legacy SWEEP warning and its exit-zero trap.
Read guide →InductEx® · How to
Run nested frequency grids on a complete two-port teaching line, compare complex responses and understand what Studio zoom and CSV export can interpolate.
Read guide →InductEx® · How to
Preserve relative input names and selected numerical files, verify their hashes, and rerun the complete teaching project in a separate directory.
Read guide →InductEx® · How to
Choose saved documents and raw logs explicitly, understand what the ZIP contains, and recover from an export failure without confusing it with a runnable project.
Read guide →TetraHenry® · Get started
Run a complete JSON and modified FastHenry conductor example with the bundled TTH executable, check its signed current against a known DC resistance and retain each run separately.
Read guide →TetraHenry® · Troubleshooting
Check the process verdict, current-generation output, diagnostic fields and an independent reference together. Conflicting DIRECT/GMRES summaries are tracked on one TTH 1.1.50 DC example.
Read guide →InductEx® · How to
Review the outbound conversion, resolve explicit layer choices, inspect omissions and save a new JSON file and conversion report without rewriting the LDF.
Read guide →JoSIM®-Pro · Worked example
Run a complete .IV model, read voltage/current coordinates and bias order, then check the model assumptions and numerical reference before accepting its behaviour.
Read guide →JoSIM®-Pro · Troubleshooting
Separate the resistance law, bias grid, helper transient and record metadata before attributing a mismatch to a simulator failure or accepting software completion as numerical accuracy.
Read guide →InductEx® · How to
Set the main-process passkey through the visible Studio controls, distinguish licence/key/expiry failures and account for two reproduced protected-file compatibility limits.
Read guide →JoSIM®-Pro · How to
Use Outline, Peek and exact reference targets without losing unsaved source; inspect the same source graph from a complete agent client.
Read guide →JoSIM®-Pro · How to
Complete local parameters and quoted include paths, fill a linked subcircuit template and recover through current diagnostics and Undo.
Read guide →InductEx® · How to
Generate a complete first-order bar mesh, assign its material and port surfaces, inspect it in Studio and verify units, transforms, refinement and current failure recovery.
Read guide →InductEx® · How to
Run complete bump, wedge and ball-and-stitch examples, check transformed die/pin contacts and material units, refine the bump and recover a reproduced coarse-wire failure.
Read guide →JoSIM®-Pro · How to
Identify the effective editor layer, distinguish active-tab run settings and recover first project Save or invalid JSON.
Read guide →JoSIM®-Pro · How to
Compare a complete six-case serial and parallel study, inspect worker admission and recover from rejected or interrupted runs.
Read guide →JoSIM®-Pro · How to
Select current matching cases, subtract their voltage traces, apply a scalar and record a mean while preserving the original data.
Read guide →JoSIM®-Pro · How to
Understand the Touchstone import limit, preserve port/reference conventions and validate a supplied passive real-pole WIDEBAND model against a complete two-port example.
Read guide →JoSIM®-Pro · How to
Keep buffer, disk, index and HEAD distinct; review staged replacements, recover local index actions and resolve a conflict without confusing syntax review with simulation evidence.
Read guide →InductEx® · How to
Reopen saved work, verify panel sizes, back up preferences and distinguish layout reset, settings import and session reset—including the checked recovery limits.
Read guide →JoSIM®-Pro · How to
Review exact token replacements before applying them to unsaved buffers. Cancel, changed-source rejection and linked Undo/Redo preserve a deliberate editing boundary.
Read guide →JoSIM®-Pro · How to
Use the explicit licensed setup check for saved root/include files. Its result is separate from live diagnostics and from numerical simulation output.
Read guide →JoSIM®-Pro · How to
Keep amplitude samples, time spacing, interpolation and repeat behaviour explicit; load the complete external files and verify their timing and units with a checked example.
Read guide →JoSIM®-Pro · How to
Use a D model with explicit temperature, area and charge parameters. Run the complete OP/DC/AC/transient inputs, retaining two known diode reference limits.
Read guide →JoSIM®-Pro · How to
Use the Y designator and a POLY model, keep current and charge coefficient units explicit, and compare static, complex and transient outputs with independent equations.
Read guide →JoSIM®-Pro · How to
Choose E/G/F/H with explicit gain units and control terminals. Check input loading, current direction and loaded output signs using a complete ideal network.
Read guide →JoSIM®-Pro · How to
Use Local save history to review an earlier version, restore its text and format to the editor, then choose deliberately when disk should change.
Read guide →JoSIM®-Pro · How to
Control when named sources are written, resolve blocked autosave deliberately and recover checkpointed edits as unsaved copies.
Read guide →JoSIM®-Pro · How to
Find literal matches in current buffers and saved sources, review selected files and apply one reversible editing group before saving deliberately.
Read guide →