RobotStudio with the ArcWelding PowerPac add-in is exhibiting two linked symptoms: general sluggishness during normal use, and intermittent hard crashes that close the application immediately without offering the option to save. Because the crash bypasses the save prompt, every unsaved station change since the last manual save is lost. The intermittent, sometimes-crashing pattern indicates an unstable session rather than a consistent, repeatable failure.
Protect Work Before the Next Crash
Since the failure mode gives no recovery opportunity, treat work preservation as the first corrective action. Save the station frequently and at every meaningful milestone rather than at the end of a session. If your RobotStudio release offers an automatic save or recovery option, enable it and confirm it is actually active for the current station. Keep a second copy of the working station (for example, a Pack and Go archive taken at the start of each session) so a corrupted or unrecoverable session cannot destroy a full day of programming. Until the instability is resolved, consider doing high-effort edits such as welding path generation in short increments, saving after each one.
Isolate ArcWelding PowerPac as the Trigger
The title-level association with ArcWelding PowerPac is a hypothesis, not a confirmed root cause; confirm it before escalating or reinstalling. The definitive test is a controlled comparison of session stability with and without the add-in under an identical workload:
- Save and back up the current station, then close RobotStudio.
- Restart RobotStudio with ArcWelding PowerPac deactivated or unloaded.
- Open the same station and repeat the operations that were running when previous slowdowns and crashes occurred, for a comparable length of time.
- Note whether the sluggishness and crashes disappear, then re-enable the add-in and repeat the same sequence to see whether the symptoms return.
If stability tracks the add-in's presence, the PowerPac is implicated. If crashes continue with the add-in removed, the station itself, the RobotStudio installation, or the host environment (memory pressure, graphics driver, virtual controller resources) moves up the suspect list and should be investigated the same way, changing one variable at a time.
Capture Crash Data and Escalate
Intermittent crashes are rarely fixed without reproduction evidence, so build the record now. For each event, log the exact operation in progress (path generation, station load, virtual controller start, welding instruction edit), how long the session had been running, and the RobotStudio and ArcWelding PowerPac versions installed. Check Windows Event Viewer immediately after a crash for the application error entry and keep a copy of any RobotStudio logs available in your installation. Submit this package, including the isolation results from the comparison test, through official ABB support channels so the report ties the crash signature to a specific version combination.
FAQ
How do I avoid losing work when RobotStudio crashes without a save prompt?
Save manually at every milestone and take a Pack and Go backup copy of the station at the start of each session. If your RobotStudio release provides an automatic save or recovery option, enable it and verify it is active for the current station.
How can I tell if ArcWelding PowerPac is causing RobotStudio to run slowly?
Run the same station and the same operations with the PowerPac deactivated, then again with it re-enabled, for comparable session lengths. If the slowness and crashes track the add-in's presence, it is implicated; if not, investigate the station, installation, or host resources next.
What information should I send to ABB support about a RobotStudio crash?
Provide the RobotStudio and ArcWelding PowerPac versions, the exact operation running at each crash, session duration, Windows Event Viewer application error entries, and any RobotStudio logs from your installation, plus the results of your with/without add-in comparison test.