I’m doing a conversion of a project from AS 4.8.7.28 to AS 6.3.2.2 (passing through AS 4.12.8.41).
I’m having issues with the safety part: after opening the SafeDesigner 6.4.0.0 and changing what is necessary, I’m unable to compile the safety program due to the errors that you see in the picture
I have tried to recompile the software (on the Automation Studio side), delete the BusNavigator files, change the safety CPU, and re-do the safety software from scratch, but nothing. The only thing I have noticed is that it seems to be connected with the safety motion library (openSAFETY_BuR_Motion_SF).
Any ideas about the cause of the issue?
(Useful info: the original SafeDesigner was 4.4.1.0, the motion library mentioned before is a replacement for the now unsupported PLCopen_Motion_SF_2)
Hello,
it looks like the community does not have much experience with Safety project Conversion to AS6.x. . I would recomment to contact local B&R Support to get help.
If the SafeDesigner projekt is not to large, you can just reprogram it, instead of converting it. It might be some issue generated by the differences in your Motion libraries.
If you will find a solution we will be happy to read about it.
I am already in contact with B&R local support for a meeting to have some help with the migration from AS4 to AS6. We will see what they will explain to us.
The safety project is kinda big. I have tried to rewrite a portion, but it seems like the issue is connected with the motion safety library. The brand new project compiles until a motion object is inserted…
I have found no solution to that, even creating a brand new safety project return the same issue.
At the moment we are keeping the upgrade to AS6 in stand-by. Also one “bad” but “not so bad” idea is to completely re-write all the software but I have not put time on that for now.
I am hoping B&R release a new version of the safe designer that fix this (and maybe a better UI?)
in regards of better UI.
The SafeDesigner will stay as is, and become one last Update at the end of the year to solve some topics with CRA on Runtime. SafeDesigner itself will not becomme CRA complient.
The successor of mappSafety will be Safety+ which was anounced on SPS2025/2026 Exibition. Safety+ will have a complete Different UI. Safety+ is sheduled to release in mid 2026. Currently it is not planed to have a conversion tool for mappSafety Projects.
So before rewriting the whole projekt in MappSafety6.x it might be good to discuss the timelines with local support if you can switch to Safety+.
Meanwhile i hope that someone can find a solution to your current issue.
Just wanted to give you an outlook in regards to UI.
.