AcoposMulti Power Supply with mappMotion

[FIH-RSB (Hannes Fisch <°///---<)]

Goal

Controlling an AcoposMulti power supply module involves a number of specific considerations that must be taken into account, which are either sparsely covered, scattered throughout, or not described at all in the Automation Studio help.

Axis-Link

When creating an axis object in the Configuration-View, a real axis contains a globally available axis link of type (McAxisType).
An AcoposMulti power supply module, on the other hand, requires an axis link of type McPSMAxisType for control.

Printscreen AS-Help

Unlike most other objects, this object is not created by adding an object in the Configuration-View, but by entering a link on the axis in the Physical-View.
This means that no drop-down menu appears for selecting the link; instead, a link must be created here manually.

This has been the case since version 5.4.0 and is described in the AS Help.

This step creates a global structure of type McPSMAxisType, which can then be used in the LogicalView within programmes.

Use in libraries

The power supply module can be controlled and switched on using either the Core Libraries (MC_Power) or the Technology Libraries (MpAxisBasic).

Even though the function blocks in the descriptions each define a reference to the McAxisType as an input, the reference can be passed to the McPSMAxisType.

Printscreen AS-Help

Alarm-Handling

A power supply module can also report many errors, which must be handled in MpAlarmX’s event handling.

This can be done only with shared alarms. There is no object in the configuration view where axis-specific alarms can be configured.
The AS Help explains that SharedAlarms can be used for AcoposMulti power supply modules.

Real axis on channel 2

In addition to the power section on channel 1, a power supply module also features a complete axis (reel and virtual) on channel 2.

This is confusing in this case, as the real axis here is more of a “virtual real axis”.
This axis cannot be used to control motors. Its purpose is to enable the processing of encoder signals from the optional interfaces or SPT-Fubs.

Cockpit integration

Once the axis link has been defined in the power supply module configuration in Physical-View, the module is displayed with the basic functions of a power supply and can be fully diagnosed and controlled from there.

Note that the power supply will be displayed in the cockpit only if it has been used somewhere in the code in the locical view.

[kovarj (Jaroslav Kovar)]

thanks for sharing

[FIH-RSB (Hannes Fisch <°///---<)]

During the implementation of the Acopos power supply module, another interesting insight was gained.
The object of type McPSMAxisType can also be used directly in a MpComExtLink object. This ensures that the power supply alarms are also routed to the correct MpAlarmXCore.

[FIH-RSB (Hannes Fisch <°///---<)]

In the meantime, we have been able to resolve the outstanding issue regarding the unique EventCodes of multiple AcoposMulti Power supplies with B&R.

Problem

Power supply modules can only be connected to MpAlarmX via shared alarms in the MappMotion configuration. There is no own axis-object where the alarms can be defined.
As a result, when multiple power supply modules are used, unique EventCodes cannot be assigned.
All modules therefore have the same code and must be distinguished by their text or scope.
According to B&R, this is technically the case because all power supplies use the same configuration in the background.

Solution approach

An approach developed in collaboration with B&R involves assigning the axis to an AlarmCore using MpComExtLink.
This core then escalates all alarms to a higher-level alarm list.
This escalation can now be used to replace the alarms for this axis during escalation, using Aggregate and escalate alarm, with another locally declared alarm with a unique EventCode.

This makes it possible to use shared alarms and replace them in such a way that they remain unique throughout the entire project.