Tracing ParIDs - Ultimate Guide

[chris.hairston]

Table of Contents

• Overview
• Determining Motion System
  • From SDM or System Dump
  • From Project
• Trace Workflows
  • Using ACP10 Trace Window
  • Using Mapp Cockpit
  • Using MC_BR_ParTrace

Overview

A trace logs the value of a data-point or data-points over time. The B&R Support Team may occasionally request a trace or traces if the customer issue warrants it.

Here are some example scenarios where a trace may be helpful:

• Variable value is changing too fast to be observed in real time.
• Temperature model not matching the temperature detected by sensor.
• Track the position of an axis over the time of a movement.

Determining Motion System

From SDM or System Dump

Requirements

• Web browser (such as Chrome, Firefox, Edge, etc.)
• Connection to B&R PLC/PC (IP address must be known)

If ACP10 is used, it’s version will appear under System → General under the “Software Versions” section in the “Motion Control” field. If mapp Motion is used, nothing will appear in this field.

From Project

Requirements

• Automation Studio
• Access to Automation Studio project

In AS, go to Project → Change Runtime Versions.

Trace Workflows

Using ACP10 Trace Window

Requirements

• Motion System: ACP10 only
• Automation Studio
• Connection to B&R PLC/PC (SNMP must be activated for browsing or IP address must be known)

Creating a Dummy Project

If you already have the project, you may skip to “Tracing a ParID in the Trace Window”

1. Create a project starting with the main target (PLC/PC)
   

   

2. Add the relevant motion hardware to the project. You can use the SDM to ensure the position(s) (station number) is/are the same. Keep in mind that you may need to enable legacy hardware depending on how old the hardware is. If you do not know what exact model your motor is, or are not using a B&R motor, select one of the generic motors.
   The online hardware comparison may not have the motion hardware listed but the SDM should.
   

   
   
   
   
   
   
   

3. Ensure you choose “ACP10 ARNC0 (Motion)” when prompted for your motor system choice.
   

   

4. Define an axis or axes.
   

   

5. Ensure the settings in the “Configuration summary” are correct. In my instance I am using an ACOPOS 1016 powered by DC so it is very important this is properly configured.
   

   

Tracing a ParID in the Trace Window

You can access the trace feature in AS 4 via the Trace or Test window by right-clicking on the relevant drive and axis in the Physical View:

Right-click on the Trace window and select Configuration:

You can try to use the search to search for specific parID’s:

But if you know the number of the ParID, then it is easier to right-click in the configuration window and add them:

The Show Common checkbox is also useful for finding commonly used parID’s:

Once you have selected all the parID’s you would like to trace, check the box next to the ParID you would like to use as a trigger (if any).

Then, go to the Timing Tab and set up the trigger as desired. It is generally recommended to set your sampling time as desired and check the maximum box.

In this example we are capturing 0.5 seconds before the trigger occurs. The trigger occurs when the Position Controller Actual Speed goes within the Window and then out of the window.

When the speed goes below 4990, then the trigger will be activated.

The trigger always occurs at 0s, but you can buffer data before the trigger using a negative delay (-0.5s in this case).

To run the trace as configured with a trigger, you can use the following button:

To run the trace without considering the trigger, then use this button instead:

Once the trace completes (trigger occurred or trace buffer was filled with no trigger configured), you will have the option to keep or remove old charts.

As long as you no longer need the old chart data already displayed, you can select Remove old.

To save the data to be sent to another user, always use the Save Chart Data functionality:

Mapp Cockpit (Must Be Present in Project)

Requirements

• Motion System: ACP10 or mapp Motion
• Web browser (such as Chrome, Firefox, Edge, etc.)
• Connection to B&R PLC/PC (IP address must be known)

Determining if Mapp Cockpit is Present

In the SDM or a system dump, go to the “Software” page. Sort alphabetically by “Module” and look for “mCoWebSc”. If this is listed, mapp Cockpit should be present on the system.

Tracing ParIDs in Mapp Cockpit

From AS Help: B&R Online Help

Open the web-based mapp Cockpit HMI application and switch to the Trace overview.

Open the trace configuration with button Configuration.

Click on button Add in area Data points.

Select desired data point from dialog box. Add data points that appears.

Example: PCTRL_S_ACT - This data point describes the current position value of the axis in the position controller.

Add this data point to the trace configuration by double-clicking on it.

Enable the trace with button Activate.

Button Save trace configuration can be used to save the current trace configuration on the target system as protected against a cold restart.
This can then be imported in Automation Studio via the online comparison of automation components in a detailed comparison.

Wait until the trace status changes to Data available.

Open the trace analysis from the trace overview with button Analysis.

The trace data should be loaded automatically.

The corresponding graph can be opened by double-clicking on the ACOPOS data point. If a graph from group node “Recent” is opened, as shown here, it is updated by the controller each time it is loaded. For additional information about the different group nodes and their behavior, see here.

Using MC_BR_ParTrace

Requirements

• Motion System: ACP10 only
• Automation Studio
• Access to Automation Studio project

Configuring the Function Block

The trace is configured using a MC_PARTRACECONFIG_REF type (structure) variable. This variable type contains two types within it. DatObj of type MC_DATOBJ_REF and ParTrace of type MC_PARTRACE_REF.

MC_DATOBJ_REF

MC_PARTRACE_REF

'MC_TRACETRIGGER_REF`

'MC_TRACEPARAM_REF`

Operation of MC_BR_ParTrace

When you start a trace with MC_BR_ParTrace Execute and command mcSTART (260), you will see the following in the NWCT. It looks like it stops the currently active trace when you do so:

…

The NWCT will list the trace configuration parameters as separate entries.

…

You can also expect to see “Trace is running” in the test window:

After the trigger occurs, the trace goes to the state ncTR_REST until the trace time is complete at which point it goes to ncTR_END. Note the last error which occurs if you have the test window trace pane open.

It is strongly recommended not to use the ACP10 Trace and the MC_BR_ParTrace at the same time.

You can read the current trace status with parID STATUS_TRACE (129). This is useful in your program to know when the trace has completed and you can save the trace:

If you are triggering on an automatic trigger, you do not need to send the trace stop command mcSTOP (261) from the MC_BR_ParTrace function block.

You can instead go ahead save the trace with mcSAVE (341) once you reach state ncTR_END.

[kovarj (Jaroslav Kovar)]

This is really ultimate one, thanks for sharing