AS6 and mappCockpit

I’ve been testing out AS6, and I noticed an issue with mappCockpit. Its not showing the axes I have configured in my project.
In my ‘component overview’ screen, where i expect to see the axis references, its blank.
Just me?

Hi,

I haven’t tested by my own until now, but I got the following information:

Since 6.0, read access authorisations are required
to access the controller in the mapp Cockpit.
This means that you must log in and the logged-in user must be in the ‘Observer and/or Engineer’ role.

1 Like

That didn’t seem to have any affect on what I’m seeing.
I know in AS 4.x, there was a role for ‘write’ access, and if it wasn’t met, you could still see the axis component, you just couldn’t perform any move commands. In this case, the axis isn’t even showing up.

Hi,

I’m not sure why it isn’t working at your side.
In my test project (it’s the mappView Highlight project plus one axis, ArSim) it looks good.

The change from AS4 / mappCockpit5 to AR6 / mappCockpit6 is, that you even have to be logged in with a user having at least read access to see anything.

Before login, I also can’t see any components:

After login, I see all the components:

The user I’ve used has the roles “Everyone” and “BR_Engineer” (for write access):

image

For preparation to use mappCockpit, I more or less followed this guide from the help.

Best regards!

2 Likes

Hello bjacot:

Another thing necessay for the cockpit to work for me was to to configure the BR_Engineer as an authorized user role, for this in the UaCsConfig.uacfg file:
image

Open the advanced configuration
image

And In the authorization add the BR_Engineer role:

After adding this, I was able to log in and have all the components.
I assume that since @alexander.hefner used the mappView Highlight, chances are that those configuration are already established.

Hope it works for you.

3 Likes

@wenbo.ruan,

you’re completely right, thanks for this hint! :clap:
My project wasn’t setup from scratch, so this setting was already included and I forgot to mention it.

As Automation Studio 6 follows the Security-by-Default approach, if starting from “new project”, all the neccessary and / or wanted settings have to be done by the user on purpose.

great - that fixed my issue.
Thanks.

1 Like