Fronius Package-State Checklist

This annex is for Fronius platforms where the reported fault may actually belong to package state, licensed function set, remote ecosystem, or cooler or feeder integration.

Use it with:

iWave
iWave Multiprocess Pro
TransSteel 2200 C
TransSteel 3500
TransSteel 5000 Pulse
TransPocket 180 TIG

Core rule

On Fronius platforms, configuration state is part of troubleshooting.

Do not assume a missing process, odd behavior, or repeated control complaint proves hardware failure until package state is simplified.

Package-state checklist

1. Identify the exact machine context

full model and output class
active process
installed package or option set
feeder package if present
cooler and remote hardware present

2. Reduce to the lowest-complexity baseline

for TIG: simple DC TIG with no unnecessary advanced package interaction
for MIG/MAG: conservative baseline with known wire and gas
for MMA: direct-output baseline with simple leads

3. Strip away ecosystem complexity

disconnect or isolate optional remote hardware
isolate feeder package from core output if possible
verify cooler function and hose routing independently
avoid judging the machine from one advanced stored job alone

4. Rebuild one layer at a time

re-enable one package or advanced function
reconnect one accessory branch
document the exact point where the fault returns

Symptom map

Symptom	Most likely package-state branch	First move
Process appears unavailable	wrong active package or configuration state	verify installed package and active process
TIG start abnormal only in one job or mode	stored state or advanced package drift	rebuild a plain DC TIG baseline
MIG or feeder behavior abnormal while base output seems normal	feeder ecosystem or configuration mismatch	isolate feeder and test simplified output
Repeated control text or integration complaint	remote, cooler, or software-state branch	capture exact message and simplify hardware stack

Model-family notes

iWave

Best split: basic DC TIG, AC package behavior, cooler or remote integration.
Capture exact fault wording before power cycle.

iWave Multiprocess Pro

Best split: licensed or configured capability, active process subsystem, shared power or control layer.
Do not diagnose through the feeder ecosystem until direct process baseline is proven.

TransSteel families

Best split: synergic or stored-state behavior, feeder and gas path, core output.
Pulse-capable or higher-duty versions should be judged in their own operating context, not as compact feeder systems.

Escalate sooner when

the same process remains hidden or rejected after configuration verification
exact control text repeats from a cold start after baseline reduction
the fault remains across multiple processes with simplified hardware attached

Source posture

This annex is synthesized from the Fronius model guides in this repository.
Exact package entitlement, interface behavior, and service interpretation should still be checked against Fronius documentation for the affected system.