I’m trying to build a project and transfer to target (ARsim) via command line ( B&R Online Help ). My approach is:
Build project via command line
Start AR sim
Transfer project to target via PVITransfer.exe
This worked worked for Automation Studio 4, but not for Automation Studio 6.
During transfer, the following error occurs:
I’ve also tried doing the ARsim installation via “Offline commissioning” in Runtime Utility Center, but with the same result (Error in file structure: same group in different classes)
Any advise on further troubleshooting would be greatly appreciated.
Hi @Emil_Hjelm ,
Which Automation Studio version are you using (6.1/6.2/…mine is 6.5.0.306)? And which PVI (mine is 6.5.0.104)?
Normally in this situation I try to reduce the problem, Have you tried to do the same with all your tasks disabled? If that works, Can you try to re-enable one task each time and repeat your sequence of commands?
I don’t see any error ID/number in the error message so it’s hard to see which component RUC/PVI/… is responsible for that issue
I did a test with more complex prj I have at the moment on my pc and no issue:
Normally my laptop is a collector of issues, and this feature works in my case…I recommend to call the local Support in your area because to me the issue is related to your prj.
Please update us regarding the cause of the problem
We have seen a similar issue reported by a customer in the US, they were attempting to do an Offline Commissioning via RUC package and ran into the same “Error in file structure: same group name in different classes” error. This is actively being troubleshooted in a support CASE, will report back once we have a solution.
Hi Emil, quick question: if you create a new AS 6.5.0.306 project and follow the steps you mentioned (build via command line, start ARsim, and transfer via RUC (PVI 6.5.0.104)), do you still see the issue? Or is it just with this project?
@rafael.laury Did you find any more information or cause for the “Error in file structure: same group name in different classes” in the support CASE? I have tried to isolate the error but have had no success so far.
Hi @Emil_Hjelm ,
I saw in our internal channel one colleague has reported the same issue, below his workaround:
”When reverting back to PVI 6.0.2 the transfer command is executed without any issue.”
Could you do a test with PVI 6.0.2?
Not easy test I see…you have to uninstall PVI 6.5 first then install PVI 6.0.2, make a test and then if you want reinstall 6.5…
Hi all, this issue has been confirmed as a bug. It will be fixed in Automation Studio / PVI version 6.5.2, which is planned to be released on 13 March 2026.
@rafael.laury When is the PVI upgrade to be expected?
The service pack upgrade was released 26th March 2026. But shouldn’t there be a upgrade for PVI as well or is it already included?
We installed the Automation Studio Version 6.5.2 with the PVI 6.5.0.104 but its not working for a colleague so we assume, that there should be a upgrade for PVI Development Setup.
Has anyone still has the same bugs after the new update?
Hi @VishalSaini, you are correct, the new PVI/RUC version is not included in the AS 6.5.2 Service Pack, but rather will be included in the Automation NET/PVI 6.5.2 update, which will be released by the end of this week (by 3 April 2026).
