0% found this document useful (0 votes)

33 views320 pages

Configuration Desk Conflicts

The document outlines conflicts that may arise during the implementation of ConfigurationDesk applications, detailing various types of conflicts such as application process, bus configuration, and device conflicts. It provides contact information for dSPACE support and encourages users to download the latest software updates. Additionally, it emphasizes the importance of unique naming conventions and the resolution of conflicts through the Conflict Viewer.

Uploaded by

mohamed azarudeen

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

33 views320 pages

Configuration Desk Conflicts

Uploaded by

mohamed azarudeen

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 320

ConfigurationDesk

Conflicts
For ConfigurationDesk 2024-A (24.1)

Release 2024-A – May 2024

How to Contact dSPACE
Mail: dSPACE GmbH
Rathenaustraße 26
33102 Paderborn
Germany
Tel.: +49 5251 1638-0
E-mail: [email protected]
Web: https://www.dspace.com

How to Contact dSPACE Support

If you encounter a problem when using dSPACE products, contact your local dSPACE
representative:
§ Local dSPACE companies and distributors: https://www.dspace.com/go/locations
§ For countries not listed, contact dSPACE GmbH in Paderborn, Germany.
Tel.: +49 5251 1638-941 or e-mail: [email protected]

You can also use the support request form: https://www.dspace.com/go/supportrequest. If

you are logged on to mydSPACE, you are automatically identified and do not have to add
your contact details manually.

If possible, always provide the serial number of the hardware, the relevant dSPACE License
ID, or the serial number of the CmContainer in your support request.

Software Updates and Patches

dSPACE strongly recommends that you download and install the most recent patches
for your current dSPACE installation. Visit https://www.dspace.com/go/patches for the
software updates and patches themselves and for more information, such as how to
receive an automatic notification when an update or a patch is available for your dSPACE
software.

Important Notice
This publication contains proprietary information that is protected by copyright. All rights
are reserved. The publication may be printed for personal or internal use provided all the
proprietary markings are retained on all printed copies. In all other cases, the publication
must not be copied, photocopied, reproduced, translated, or reduced to any electronic
medium or machine-readable form, in whole or in part, without the prior written consent
of dSPACE GmbH.

© 2016 - 2024 by:

dSPACE GmbH
Rathenaustraße 26
33102 Paderborn
Germany

This publication and the contents hereof are subject to change without notice.

AURELION, AUTERA, ConfigurationDesk, ControlDesk, MicroAutoBox, MicroLabBox,

SCALEXIO, SIMPHERA, SYNECT, SystemDesk, TargetLink, and VEOS are registered
trademarks of dSPACE GmbH in the United States or other countries, or both. Other
brand names or product names are trademarks or registered trademarks of their respective
companies or organizations.
Contents

Contents

About This Document 5

Conflicts 7
Application Process Conflicts........................................................................... 9
Build Configuration Set Conflicts................................................................... 20
Bus Access Request Conflicts......................................................................... 20
Bus Configuration Conflicts........................................................................... 21
CAN Cluster Conflicts....................................................................... ............ 22
CAN Communication Controller Conflicts......................................... ............ 25
CAN Frame Conflicts..................................................................................... 26
CAN Frame Triggering Conflicts..................................................................... 27
Channel Conflicts.......................................................................................... 33
Cluster Conflicts............................................................................................ 35
Coding Conflicts........................................................................................... 37
Communication Connector Conflicts............................................................. 42
Communication Matrix Conflicts................................................................... 43
Communication Package Conflicts................................................................ 44
Contained IPDU Conflicts.............................................................................. 45
Container IPDU Conflicts............................................................................... 57
Device Block Conflicts................................................................................... 61
Device Conflicts................................................................................ ............ 62
Device Pin Conflicts....................................................................................... 63
Device Port Conflicts..................................................................................... 63
Device Port Mapping Conflicts.......................................................... ............ 64
ECU Conflicts................................................................................................ 64
Event Conflicts.............................................................................................. 65
Executable Application Conflicts.................................................................... 67
External Cable Harness Conflicts....................................................... ............ 70
Feature Conflicts........................................................................................... 71
Frame Conflicts............................................................................................. 85
Function Block Conflicts................................................................................ 92
Global Time Domain Conflicts..................................................................... 181
Hardware Resource Assignment Conflicts.................................................... 187
Hardware Resource Conflicts....................................................................... 225
Hardware Unit Slot Conflicts............................................................. .......... 227
IPDU Conflicts............................................................................................. 228
ISignal Conflicts................................................................................ .......... 247
ISignal Group Conflicts................................................................................ 253

3
May 2024 ConfigurationDesk Conflicts
Contents

ISignal-to-IPDU Mapping Conflicts............................................................... 258

J1939 Network Management Node Conflicts.............................................. 259
J1939 Transport Protocol Node Conflicts..................................................... 261
LIN Cluster Conflicts.................................................................................... 263
LIN Communication Controller Conflicts...................................................... 265
LIN Frame Conflicts..................................................................................... 266
LIN Frame Triggering Conflicts..................................................................... 271
LIN Schedule Table Conflicts........................................................................ 275
Model Conflicts........................................................................................... 276
Model Port Block Conflicts.......................................................................... 278
Model Port Mapping Conflicts..................................................................... 280
Multiplexed IPDU Conflicts.......................................................................... 284
Partial Networking Conflicts........................................................................ 294
PDU Conflicts.............................................................................................. 295
PDU Triggering Conflicts.............................................................................. 301
Processing Unit Application Conflicts........................................................... 304
Processing Unit Conflicts............................................................................. 306
Runnable Function Conflicts........................................................................ 306
Signal Chain Conflicts................................................................................. 307
Task Conflicts.............................................................................................. 309
Task Group Conflicts................................................................................... 313
Time Master Conflicts....................................................................... .......... 314
Time Slave Conflicts.................................................................................... 317

4
ConfigurationDesk Conflicts May 2024
About This Document

About This Document

Content This reference decribes the conflicts that can occur while you are implementing
a ConfigurationDesk application. The conflicts are displayed in the Conflicts
Viewer.

Symbols dSPACE user documentation uses the following symbols:

Symbol Description
Indicates a hazardous situation that, if not avoided,
V DANGER
will result in death or serious injury.
Indicates a hazardous situation that, if not avoided,
V WARNING could result in death or serious injury.
Indicates a hazardous situation that, if not avoided,
V CAUTION could result in minor or moderate injury.
Indicates a hazard that, if not avoided, could result in
NOTICE
property damage.
Indicates important information that you should take
Note
into account to avoid malfunctions.
Indicates tips that can make your work easier.
Tip
Indicates a link that refers to a definition in the
glossary, which you can find at the end of the
document unless stated otherwise.
Follows the document title in a link that refers to
another document.

Naming conventions dSPACE user documentation uses the following naming conventions:

%name% Names enclosed in percent signs refer to environment variables for

file and path names.

<> Angle brackets contain wildcard characters or placeholders for variable

file and path names, etc.

5
May 2024 ConfigurationDesk Conflicts
About This Document

Special Windows folders Windows‑based software products use the following special folders:

Common Program Data folder A standard folder for application-specific

program data that is used by all users.
%PROGRAMDATA%\dSPACE\<InstallationGUID>\<ProductName>
or
%PROGRAMDATA%\dSPACE\<ProductName>\<VersionNumber>

Documents folder A standard folder for application‑specific files that are

used by the current user.
%USERPROFILE%\Documents\dSPACE\<ProductName>\<VersionNumber>

Local Program Data folder A standard folder for application-specific

program data that is used by the current user.
%USERPROFILE%\AppData\Local\dSPACE\<InstallationGUID>\
<ProductName>

Accessing dSPACE Help and After you install and decrypt Windows‑based dSPACE software, the
PDF files documentation for the installed products is available in dSPACE Help and as PDF
files.

dSPACE Help (local) You can open your local installation of dSPACE Help:
§ On its home page via Windows Start Menu
§ On specific content using context-sensitive help via F1

PDF files You can access PDF files via the icon in dSPACE Help. The PDF
opens on the first page.

dSPACE Help (Web) Independently of the software installation, you can

access the Web version of dSPACE Help at https://www.dspace.com/go/help.
To access the Web version, you must have a mydSPACE account.
For more information on the mydSPACE registration process, refer to
https://www.dspace.com/faq?097.

6
ConfigurationDesk Conflicts May 2024
Conflicts

Conflicts

Objective ConfigurationDesk provides the Conflict Viewer, which displays any conflicts
that occurred when the signal chain was created and configured. It also helps
you to resolve these conflicts.

Where to go from here Information in this section

Application Process Conflicts..................................................................... 9

Build Configuration Set Conflicts............................................................. 20

Bus Access Request Conflicts................................................................... 20

Bus Configuration Conflicts..................................................................... 21

CAN Cluster Conflicts.............................................................................. 22

CAN Communication Controller Conflicts................................................ 25

CAN Frame Conflicts............................................................................... 26

CAN Frame Triggering Conflicts............................................................... 27

Channel Conflicts.................................................................................... 33

Cluster Conflicts...................................................................................... 35

Coding Conflicts...................................................................................... 37

Communication Connector Conflicts....................................................... 42

Communication Matrix Conflicts............................................................. 43

Communication Package Conflicts........................................................... 44

Contained IPDU Conflicts........................................................................ 45

Container IPDU Conflicts......................................................................... 57

Device Block Conflicts.............................................................................. 61

Device Conflicts....................................................................................... 62

7
May 2024 ConfigurationDesk Conflicts
Conflicts

Device Pin Conflicts................................................................................. 63

Device Port Conflicts................................................................................ 63

Device Port Mapping Conflicts................................................................. 64

ECU Conflicts.......................................................................................... 64

Event Conflicts........................................................................................ 65

Executable Application Conflicts.............................................................. 67

External Cable Harness Conflicts.............................................................. 70

Feature Conflicts..................................................................................... 71

Frame Conflicts....................................................................................... 85

Function Block Conflicts.......................................................................... 92

Global Time Domain Conflicts............................................................... 181

Hardware Resource Assignment Conflicts.............................................. 187

Hardware Resource Conflicts................................................................. 225

Hardware Unit Slot Conflicts.................................................................. 227

IPDU Conflicts....................................................................................... 228

ISignal Conflicts..................................................................................... 247

ISignal Group Conflicts.......................................................................... 253

ISignal-to-IPDU Mapping Conflicts......................................................... 258

J1939 Network Management Node Conflicts......................................... 259

J1939 Transport Protocol Node Conflicts................................................ 261

LIN Cluster Conflicts.............................................................................. 263

LIN Communication Controller Conflicts................................................ 265

LIN Frame Conflicts................................................................................ 266

LIN Frame Triggering Conflicts............................................................... 271

LIN Schedule Table Conflicts.................................................................. 275

Model Conflicts..................................................................................... 276

Model Port Block Conflicts..................................................................... 278

Model Port Mapping Conflicts............................................................... 280

Multiplexed IPDU Conflicts.................................................................... 284

Partial Networking Conflicts.................................................................. 294

PDU Conflicts........................................................................................ 295

PDU Triggering Conflicts........................................................................ 301

8
ConfigurationDesk Conflicts May 2024
Application Process Conflicts

Processing Unit Application Conflicts..................................................... 304

Processing Unit Conflicts....................................................................... 306

Runnable Function Conflicts.................................................................. 306

Signal Chain Conflicts............................................................................ 307

Task Conflicts........................................................................................ 309

Task Group Conflicts.............................................................................. 313

Time Master Conflicts............................................................................ 314

Time Slave Conflicts...................................................................... ........ 317

Information in other sections

Resolving Conflicts (ConfigurationDesk Real-Time

Implementation Guide )

Application Process Conflicts

Application process: Assigned An application process contains an SIC file that was generated for the
model contains incompatible dsrt64.tlc Run-Time Target.
code
SIC files generated for the dsrt64.tlc Run-Time Target are not supported in
real-time applications built by ConfigurationDesk. You can use these SIC files
only to generate BSC files that are used for execution on VEOS on a Linux
operating system.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – – – –

Remedy Remove the SIC file generated for the dsrt64.tlc Run-Time Target
from the application process.

Application process: Default The Provide default task checkbox in the Properties Browser of the
task provided and model application process is selected, and one or more model implementations are
assigned assigned to the application process.

Application processes whose Provide default task checkbox is activated must

not have any model implementations assigned.

9
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, perform one of the following actions:

§ Select False from the Provide default task list of the application process.
§ Clear the (Select All) checkbox from the Assigned models list of the
application process, and click OK.

Application process: Duplicate An application process contains two or more tasks with the same DAQ raster
DAQ raster name for tasks name.
within common application
DAQ raster names for the tasks in an application process must be unique.
process
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, enter unique names in the
DAQ raster name edit field for all the tasks assigned to the application process.

Application process: Duplicate An application process contains two or more timer events with the same name.
event names
The names of timer events in an application process must be unique.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, enter unique names in the
Name edit field for all the timer events in the application process.

Application process: Duplicate An application process contains two or more tasks with the same name.
task names
The names of all tasks in an application process must be unique.

10
ConfigurationDesk Conflicts May 2024
Application Process Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, enter unique names in the
Name edit field for all tasks in the application process.

Application process: The application process contains at least one model implementation that is
Incompatible target incompatible with the assigned target architecture.
architecture in assigned
Model implementations assigned to an application process must match the
model
architecture of the assigned target platform.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – – – –

Remedy Regenerate incompatible model implementations to match the

target architecture. In the Model Browser, then reload the model
implementations or replace the affected model implementations with different
ones.

Application process: Invalid The application process contains either more than one task or no task for which
number of Bus monitoring bus monitoring is activated.
tasks
If you want to use bus monitoring, it must be activated for exactly one task
within an application process.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – – – –

Remedy Make sure that bus monitoring is activated for exactly one task in
the application process.

Application process: Multiple Two or more bus configurations within the application process have identical
bus configurations with the names.
same name assigned
The names of bus configurations within an application process must be unique,
regardless of whether the bus configurations are contained in BSC files or are
available as Bus Configuration function blocks.

11
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Choose one of the following alternatives:

§ Assign the conflicting BSC files or Bus Configuration function blocks to
different application processes.
§ Rename the conflicting Bus Configuration function blocks.

Application process: Multiple There are duplicate FlexRay configuration IDs in an application process.
FlexRay configuration IDs
A configuration ID is used to identify blocks from different FlexRay
configurations. It must therefore be unique for each FlexRay bus in an application
process.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Assign unique configuration IDs to each FlexRay bus within the
application process.

Application process: Multiple Two or more model implementations that have identical global C variables are
models providing the same assigned to the same application process. This conflict is displayed in particular
global C variables assigned if you specify the names of C variables that are created for the parameters or
signals in the relevant Simulink models by setting the storage class of these
variables to ExportedGlobal, for example.

All the global C variables provided by model implementations that are assigned
to the same application process must be unique. This applies to the variables that
can be accessed at run time, i.e., the variables in the TRC file. If the conflict is
not resolved, the related variables cannot be accessed via experiment software at
run-time.

If you resolved the conflict in the model implementations, you must make sure
that the 'Conflict treatment in build process' property in the Global Build Settings
is set to 'Analyze and build models first' before you start the build process.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

12
ConfigurationDesk Conflicts May 2024
Application Process Conflicts

Remedy To resolve this conflict, perform one of the following actions in the
relevant model implementations:
§ Specify a storage class other than ExportedGlobal for the C variables for
parameters and signals.
§ Specify unique names for the C variables for parameters and signals.
If the relevant model implementations are Simulink models, start the build
process in ConfigurationDesk. If the relevant model implementations are SIC
files, create a new SIC file and reload it in ConfigurationDesk.

Application process: Multiple There are two or more BSC files assigned to the application process that contain
models with the same model implementations described by SIC files with the same name.
name assigned to multimodel
The names of all SIC files describing model implementations that are included in
application process
BSC files assigned to the same application process must be unique.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Assign the conflicting BSC files to different application processes.

Application process: Multiple The application process has two or more Simulink behavior models or SIC
MotionDesk models assigned files assigned that contain blocks from the MotionDesk Blockset with activated
to multimodel application platform support.
process
Only one Simulink model or SIC file that contains blocks from the MotionDesk
Blockset with activated platform support is allowed per application process.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Processing Resource Assignment table, delete the

assignment of all but one model implementations with blocks from the
MotionDesk Blockset from the multimodel application process using the
Delete Assignment command from the context menu of the relevant
model implementations. Create separate application processes for the model
implementations using the Create Preconfigured Application Process context
menu command of the model implementations.

Application process: Multiple You have enabled Real-Time Testing for more than one task within an application
tasks with enabled Real-Time process.
Testing
Real-Time Testing can only be allowed for exactly one task.

13
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, select False from the Real-Time Testing
list for all but one task in the application process.

Application process: No model There is no model implementation assigned to the application process and the
assigned application process has no default task. If you want to model an executable
application, you have to create at least one application process and assign a
model implementation to it. You can preconfigure the application process using
the Optimize Configuration command, or model the tasks in the application
process manually using the runnable functions that the model implementation
provides.

Another possibility is to use no model implementation in the application process

and let the application process provide a default task.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Depending on your use scenario, choose one of the following

alternatives:
§ The application process is no longer needed:
In the Conflicts Viewer, delete the application process using the Delete from
Application context menu command.
§ The required model is included in the model topology:
In the Task Configuration table, right-click the application process and assign
a model implementation using the Assign Model command. If the application
process was not configured before, create a preconfigured application process
using the Optimize Configuration context menu command.
§ The required model is not included in the model topology:
In the Task Configuration table, right-click the application process and add
the required model via the Add Model command.
§ You want the application process to run without any model implementation:
In the Properties Browser, select the Provide default task checkbox of the
application process.

Application process: No task There is no task defined in the application process.

defined
An application process must have at least one task.

14
ConfigurationDesk Conflicts May 2024
Application Process Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Choose one of the following alternatives:

§ If at least one model implementation is assigned to the application process,
right-click the application process in the Task Configuration table and
create a preconfigured application process using the Optimize Configuration
command.
§ If no model implementation is assigned to the application process, choose one
of the following alternatives, depending on your use scenario:
§ The application process is no longer needed:
In the Conflicts Viewer, delete the application process using the Delete
from Application context menu command.
§ The required model is included in the model topology:
In the Task Configuration table, right-click the application process and
assign a model implementation using the Assign Model command. If
the application process was not configured before, create a preconfigured
application process via the Optimize Configuration context menu
command.
§ The required model is not included in the model topology:
In the Task Configuration table, right-click the application process and add
the required model via the Add Model command.
§ You want the application process to run without any model implementation:
In the Properties Browser, select the Provide default task checkbox of
the application process.

Application process: No task There is no task with a specified DAQ raster in the application process.
with DAQ raster defined
At least one task must have a specified DAQ raster.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, enter a unique name in the
DAQ raster name edit field for at least one task of the application process.

Application process: No task There is no task with Real-Time Testing enabled in the application process.
with enabled Real-Time
You can enable Real-Time Testing for exactly one task.
Testing

15
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, select Real-Time Testing for
exactly one task in the application process.

Application process: Too many There are too many tasks with a DAQ raster name set in the application process.
tasks with DAQ raster name
The maximum number of tasks with a DAQ raster name set is 31.
set (max. is 31)
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, clear the DAQ raster name
edit field for excess tasks in the application process.

Application process: A model implementation or I/O function assigned to the application process is
Unresolved model or I/O unresolved. For details on unresolved model implementations, refer to Basics on
function Modeling Executable Applications (ConfigurationDesk Real-Time Implementation
Guide ). For details on unresolved I/O function blocks, refer to Basics on
Function Blocks (ConfigurationDesk Real-Time Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Choose one of the following alternatives:

§ Add the relevant model implementation to the executable application using
the Add Model context menu command in the Model Browser.
§ In the Processing Resource Assignment table, delete the assignment using
the Delete Assignment context menu command.

Application process: A BSC file created with the Bus Manager of dSPACE Release 2019-A or earlier is
Unsupported BSC assigned assigned to the multimodel application process.
to multimodel application
BSC files assigned to multimodel application processes must be created with the
process
Bus Manager of dSPACE Release 2019-B or later.

16
ConfigurationDesk Conflicts May 2024
Application Process Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Processing Resource Assignment table, delete the

assignment of the relevant BSC file via the Delete Assignment command of the
BSC file's context menu. Assign the BSC file to a separate application process.

Application process: Two or more BSC files that were created with the Ethernet Configuration
Unsupported Ethernet BSC Package are assigned to the same application process.
assigned to multimodel
Only one BSC file that was created with the Ethernet Configuration Package is
application process
allowed per application process.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Processing Resource Assignment table, delete the

assignment of the relevant BSC file using the Delete Assignment command
of the BSC file's context menu. Assign the BSC file to a separate application
process.

Application process: There are different possible causes for this conflict, depending on the Jitter and
Unsupported Jitter and latency optimization setting.
latency optimization settings
For a task configured as Low jitter, low latency in the application process, at
least one of the following conditions is met:
§ There is a task with a different Jitter and latency optimization setting and a
higher priority in the application process.
§ The task is triggered by a runnable function via a software event. The
triggering runnable function is assigned to a task with a different Jitter and
latency optimization setting.
§ The task has a runnable function assigned that triggers another task via
a software event. The triggered task has a different Jitter and latency
optimization setting.

For a task configured as No jitter, low latency in the application process, at

least one of the following conditions is met:
§ The task is not the only task in the application process.
§ The task is not triggered by a timer event.

The settings described above are not supported.

17
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy For a task configured as Low jitter, low latency make sure that:
§ There is no task with a different Jitter and latency optimization setting and
a higher priority in the application process.
§ If the task is triggered by a runnable function via a software event: The Jitter
and latency optimization setting of the task with the triggering runnable
function is also configured as Low jitter, low latency.
§ If the task has a runnable function assigned that triggers another task via a
software event: The Jitter and latency optimization setting of the triggered
task is also configured as Low jitter, low latency.
For a task configured as No jitter, low latency make sure that:
§ The task is the only task in the application process.
§ The task is triggered by a timer event.

Application process: At least one Simulink behavior model or SIC file with blocks from unsupported
Unsupported model assigned blocksets is assigned to a multimodel application process.
to multimodel application
Simulink models or SIC files that are assigned to multimodel application
process
processes must not contain blocks from the RTI CAN MultiMessage Blockset,
the RTI LIN MultiMessage Blockset, the FlexRay Configuration Package, or from
the Ethernet Configuration Package.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Processing Resource Assignment table, delete the

assignment of the relevant Simulink models or SIC files using the Delete
Assignment command of the model implementations' context menu. Create
separate application processes for the Simulink models or SIC files using the
Create Preconfigured Application Process context menu command of the
model implementations.

Application process: At least one behavior model that provides an ASAP2 interface is assigned to a
Unsupported model assigned multimodel application process.
to multimodel application
Multimodel application processes must not include assigned behavior models
process. At least one of the
that provide an ASAP2 interface.
models provides an ASAP2
interface

18
ConfigurationDesk Conflicts May 2024
Application Process Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Processing Resource Assignment table, delete the

assignment of the relevant behavior models using the Delete Assignment
command from the context menu of the model implementation. Create separate
application processes for the behavior models using the Create Preconfigured
Application Process context menu command of the model implementations.

Application process: An SIC file that was created with the Model Interface Package for Simulink 3.5
Unsupported SIC assigned or earlier was assigned to a multimodel application process.
to multimodel application
SIC files assigned to multimodel application processes must be created with the
process
Model Interface Package for Simulink 3.6 or later.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Processing Resource Assignment table, delete the

unsupported SIC file using the Delete Assignment command from the context
menu of the relevant application process. To use the SIC file in your real-time
application, choose one of the following options:
§ Create a separate application process for the SIC file using the Create
Preconfigured Application Process context menu command of the model
implementation.
§ Build the SIC file again, using the Model Interface Package for Simulink 3.6 (on
dSPACE Release 2018-A) or later. Then select the Reload command from the
context menu of the SIC file.

Application process: The assigned application process has a task with a priority that is not supported
Unsupported task priority by the assigned processor hardware.
value
The priority of the task must be in the range 0 ... 79.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, specify a priority value for the
task in the range 0 ... 79.

19
May 2024 ConfigurationDesk Conflicts
Conflicts

Build Configuration Set Conflicts

Build configuration set: The active ConfigurationDesk application contains two or more build
Duplicate name configuration sets with the same name.

The names of build configuration sets must be unique.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, enter unique names in the
Name edit field for the build configuration sets.

Bus Access Request Conflicts

Bus access request: Duplicate Two or more bus access requests have identical names.
name of bus access request
The names of bus access requests must be unique within the ConfigurationDesk
application.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify unique names for the
affected bus access requests.

Bus access request: No bus A bus access request is not assigned to a suitable bus function block (CAN, LIN).
access assigned
If you want to build a real-time application, you must specify the bus access
for each bus access request via a suitable bus function block (CAN, LIN). If you
want to generate bus simulation containers, you do not have to specify the bus
accesses.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

20
ConfigurationDesk Conflicts May 2024
Bus Configuration Conflicts

Remedy Choose one of the following alternatives:

§ Assign all bus access requests of the active ConfigurationDesk application to
bus accesses in one step: Switch to the Buses view set if necessary. On the
Home ribbon, click Assign Automatically.
§ Assign a bus access request individually to one bus access:
§ In the Bus Configurations table, select the affected bus access request and
assign it to a bus access via the Bus Access Assignment command.
§ In the Conflicts Viewer, for example, specify a bus access for the Bus
Access Request property (only possible if at least one suitable bus function
block exists in the application).

Bus Configuration Conflicts

Bus configuration: Duplicate Two or more frame gateway and/or frame capture nodes of a bus configuration
name of frame gateway or have identical names.
frame capture
The names of frame gateway and frame capture nodes must be unique within a
bus configuration.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy In the Conflicts Viewer, for example, specify unique names for the
affected frame gateway and frame capture nodes.

Bus configuration: No valid A bus configuration is assigned to no or more than one application process.
application process assigned
A bus configuration must be assigned to one application process with at least
one task.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy The conflict causes and remedies that apply to your case depend on
the use scenario. For more information, refer to:
§ Bus Manager in ConfigurationDesk: Resolving the Bus Configuration Conflict:
No Valid Application Process Assigned (ConfigurationDesk Bus Manager
Implementation Guide ).

21
May 2024 ConfigurationDesk Conflicts
Conflicts

§ Bus Manager (stand-alone): Resolving the Bus Configuration Conflict: No Valid

Application Process Assigned (Bus Manager (Stand-Alone) Implementation
Guide ).

Bus configuration: Unresolved Elements of a bus configuration use communication matrix elements that are not
communication matrix available in the active ConfigurationDesk application.
elements assigned
This conflict occurs if a communication matrix was deleted without deleting the
related bus configuration elements.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ If you do not need the conflicting bus configuration element in the executable
application, delete it from the bus configuration. In the Buses Browser, for
example, select the communication matrix that is marked as unresolved and
choose Delete Completely from the context menu.
§ If you need the conflicting bus configuration element in the executable
application, add the previously deleted communication matrix or
a communication matrix with exactly the same content to your
ConfigurationDesk application.

Tip

§ When you select the communication matrix node in the Buses

Browser, the Properties Browser displays the name and the file path
of the deleted matrix.
§ If you do not add the previously deleted communication matrix but one
with identical content to the ConfigurationDesk application, the names
of the two communication matrices can differ.

CAN Cluster Conflicts

CAN cluster: Invalid A communication matrix does not define a data phase baud rate for a CAN FD
data phase baud rate cluster, or a defined data phase baud rate exceeds the valid range.
(communication matrix)
For each CAN FD cluster, the communication matrix must define a data phase
baud rate in the range 0 … [1.6 · 107] (bit/s).

22
ConfigurationDesk Conflicts May 2024
CAN Cluster Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify a valid value for the Data phase baud rate property, for example,
in the Conflicts Viewer. This changes the communication matrix in the
active ConfigurationDesk application and all element instances in all bus
configurations of the application. The originally imported communication
matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

CAN cluster: Invalid speed A communication matrix does not define a baud rate for a CAN cluster, or a
(baud rate) defined defined baud rate exceeds the valid range.
(communication matrix)
For each CAN cluster, the communication matrix must define a baud rate in the
range 0 … [Long.max] (bit/s).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify a valid value for the Baud rate property, for example, in
the Conflicts Viewer. This changes the communication matrix in the
active ConfigurationDesk application and all element instances in all bus
configurations of the application. The originally imported communication
matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

CAN cluster: Too many A conflicting communication matrix element is assigned to a bus configuration.
channels connected (bus For an assigned CAN cluster, the communication matrix specifies more than one
configuration) channel.

23
May 2024 ConfigurationDesk Conflicts
Conflicts

For each CAN cluster, the communication matrix must not specify more than one
channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

CAN cluster: Too A communication matrix specifies more than one channel for a CAN cluster.
many channels connected
For each CAN cluster, the communication matrix must not specify more than one
(communication matrix)
channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Correct the setting in the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related Conflicts
(ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

24
ConfigurationDesk Conflicts May 2024
CAN Communication Controller Conflicts

CAN Communication Controller Conflicts

CAN communication A conflicting communication matrix element is assigned to a bus configuration.

controller: Too many channels For an assigned CAN communication controller, the communication matrix
connected (bus configuration) specifies more than one channel.

For each CAN communication controller, the communication matrix must not
specify more than one channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

§ If you do not need the conflicting element in the executable application,
remove it from the bus configuration. In the Conflicts Viewer, set the Is
assigned property to False.
§ If you need the conflicting element in the executable application, correct the
setting in the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

CAN communication A communication matrix specifies more than one channel for a CAN
controller: Too many channels communication controller.
connected (communication
For each CAN communication controller, the communication matrix must not
matrix)
specify more than one channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

25
May 2024 ConfigurationDesk Conflicts
Conflicts

CAN Frame Conflicts

CAN frame: Too many PDU- A conflicting communication matrix element is assigned to a bus configuration.
to-frame mappings connected For an assigned CAN frame, the communication matrix specifies more than one
(bus configuration) PDU-to-frame mapping.

A CAN frame must not contain more than one PDU-to-frame mapping.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

CAN frame: Too many PDU- A communication matrix specifies more than one PDU-to-frame mapping for one
to-frame mappings connected CAN frame.
(communication matrix)
A CAN frame must not contain more than one PDU-to-frame mapping.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

26
ConfigurationDesk Conflicts May 2024
CAN Frame Triggering Conflicts

CAN Frame Triggering Conflicts

CAN frame triggering: Conflicting communication matrix elements are assigned to a bus configuration.
Duplicate CAN identifier For two or more assigned CAN frame triggerings, the communication matrix
on CAN channel (bus specifies the following settings:
configuration) § The CAN frame triggerings are mapped to the same CAN channel.
§ For at least two of these CAN frame triggerings, identical settings are specified
for the following properties:
§ Extended addressing
§ Frame identifier

The tuple [extended addressing; frame identifier] must be unique for each CAN
frame triggering of one CAN channel and within the following range:
§ Extended addressing = true:
Extended frame identifier (29-bit) within the range 0 … 229 -1
§ Extended addressing = false:
Standard frame identifier (11-bit) within the range 0 … 211 -1

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

27
May 2024 ConfigurationDesk Conflicts
Conflicts

CAN frame triggering: A communication matrix specifies the following settings for two or more CAN
Duplicate CAN identifier on frame triggerings:
CAN channel (communication § The CAN frame triggerings are mapped to the same CAN channel.
matrix) § For at least two of these CAN frame triggerings, identical settings are specified
for the following properties:
§ Extended addressing
§ Frame identifier

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify unique and valid values for the Extended addressing and/or
Identifier properties, for example, in the Conflicts Viewer. This changes
the communication matrix in the active ConfigurationDesk application and all
element instances in all bus configurations of the application. The originally
imported communication matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

CAN frame triggering: A conflicting communication matrix element is assigned to a bus configuration.
Invalid frame type (bus For an assigned CAN frame triggering, the communication matrix references a
configuration) LIN frame.

Each CAN frame triggering must reference a CAN frame.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

28
ConfigurationDesk Conflicts May 2024
CAN Frame Triggering Conflicts

Remedy Choose one of the following alternatives:

CAN frame triggering: Invalid A communication matrix references a LIN frame for a CAN frame triggering.
frame type (communication
Each CAN frame triggering must reference a CAN frame.
matrix)
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

CAN frame triggering: A conflicting communication matrix element is assigned to a bus configuration.
Invalid property values (bus For an assigned CAN frame triggering, the communication matrix specifies the
configuration) following settings:

At least one of the following properties is unspecified or exceeds the valid range:
§ Extended addressing
§ Frame identifier
§ CAN FD frame support
§ Bit rate switch

For a CAN frame triggering, the communication matrix must specify the tuple
[extended addressing; frame identifier; CAN FD frame support; bit rate switch]
within the valid range.

The tuple [extended addressing; frame identifier] must be within the following
range:
§ Extended addressing = true:
Extended frame identifier (29-bit) within the range 0 … 229 -1

29
May 2024 ConfigurationDesk Conflicts
Conflicts

§ Extended addressing = false:

Standard frame identifier (11-bit) within the range 0 … 211 -1

Valid values for the CAN FD frame support and the bit rate switch are true and
false.
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

CAN frame triggering: A communication matrix specifies the following settings for a CAN frame
Invalid property values triggering:
(communication matrix)
At least one of the following properties is unspecified or exceeds the valid range:
§ Extended addressing
§ Frame identifier
§ CAN FD frame support
§ Bit rate switch

For CAN frame triggering, the communication matrix must specify the tuple
[extended addressing; frame identifier; CAN FD frame support; bit rate switch]
within the valid range.

30
ConfigurationDesk Conflicts May 2024
CAN Frame Triggering Conflicts

The tuple [extended addressing; frame identifier] must be within the following
range:
§ Extended addressing = true:
Extended frame identifier (29-bit) within the range 0 … 229 -1
§ Extended addressing = false:
Standard frame identifier (11-bit) within the range 0 … 211 -1

Valid values for the CAN FD frame support and the bit rate switch are true and
false.
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify valid values for the Extended addressing, Identifier, Bit rate
switch, and/or CAN FD frame support properties, for example, in
the Conflicts Viewer. This changes the communication matrix in the
active ConfigurationDesk application and all element instances in all bus
configurations of the application. The originally imported communication
matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

CAN frame triggering: A conflicting communication matrix element is assigned to a bus configuration.
Mismatching payload length For an assigned CAN frame triggering, the communication matrix specifies the
of referenced frame (bus following settings: The communication matrix assigns a CAN frame to the CAN
configuration) frame triggering and the frame's payload length does not match the frame
triggering requirements.

To match the requirements of a CAN frame triggering, the payload length of an

assigned CAN frame must be within the following range:
§ CAN frame triggering according to CAN 2.0: Payload length within the range
0 … 8 byte
§ CAN frame triggering according to CAN FD: Payload length within the range
0 … 64 byte

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

31
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

CAN frame triggering: A communication matrix assigns a CAN frame to a CAN frame triggering and the
Mismatching payload length frame's payload length does not match the frame triggering requirements.
of referenced frame
To match the requirements of a CAN frame triggering, the payload length of an
(communication matrix)
assigned CAN frame must be within the following range:
§ CAN frame triggering according to CAN 2.0: Payload length within the range
0 … 8 byte
§ CAN frame triggering according to CAN FD: Payload length within the range
0 … 64 byte

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify valid values for the Length and/or CAN FD frame support properties,
for example, in the Conflicts Viewer. This changes the communication matrix
in the active ConfigurationDesk application and all element instances in all
bus configurations of the application. The originally imported communication
matrix remains unchanged.

32
ConfigurationDesk Conflicts May 2024
Channel Conflicts

§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Channel Conflicts

Channel: Invalid number A conflicting communication matrix element is assigned to a bus configuration.
of LIN masters (bus For an assigned LIN channel, the communication matrix specifies more than one
configuration) LIN master. At least two of the LIN masters are assigned to the bus configuration.

For each LIN channel that is assigned to a bus configuration, only one LIN master
can be assigned.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Channel: Invalid number of A communication matrix specifies no or more than one LIN master for a LIN
LIN masters (communication channel.
matrix)
For each LIN channel, the communication matrix must specify exactly one LIN
master.

33
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Channel: No name defined A conflicting communication matrix element is assigned to a bus configuration.
(bus configuration) For an assigned channel, the communication matrix does not define a name.

For each channel, the communication matrix must define a name.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Channel: No name defined A communication matrix does not define a name for a channel.
(communication matrix)
For each channel, the communication matrix must define a name.

34
ConfigurationDesk Conflicts May 2024
Cluster Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Cluster Conflicts

Cluster: Duplicate name (bus Conflicting communication matrix elements are assigned to a bus configuration.
configuration) For two or more assigned communication clusters, the communication matrix
defines identical names.

For each communication cluster, the communication matrix must define a unique
name.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Cluster: Duplicate name A communication matrix defines identical names for two or more
(communication matrix) communication clusters.

35
May 2024 ConfigurationDesk Conflicts
Conflicts

For each communication cluster, the communication matrix must define a unique
name.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Cluster: No name defined (bus A conflicting communication matrix element is assigned to a bus configuration.
configuration) For an assigned communication cluster, the communication matrix does not
define a name.

For each communication cluster, the communication matrix must define a unique
name.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Cluster: No name defined A communication matrix does not define a name for a communication cluster.
(communication matrix)
For each communication cluster, the communication matrix must define a unique
name.

36
ConfigurationDesk Conflicts May 2024
Coding Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Coding Conflicts

Coding: Unsupported data A conflicting communication matrix element is assigned to a bus configuration.
types (bus configuration) For an assigned ISignal, the communication matrix specifies at least one of the
following settings:
§ For the coded ISignal value, no data type is specified.
§ For the coded and/or physical ISignal value, an unsupported data type is
specified.
§ For the physical ISignal value, no data type is specified. In addition, a specified
computation method is not supported.
§ The ISignal is an array signal but the specified data type of the coded and/or
physical ISignal value is not supported for array signals.

The communication matrix must specify the coding of ISignals as follows:

§ For the coded ISignal value, the communication matrix must specify a data
type that the Bus Manager supports.
§ If the communication matrix specifies a data type for the physical ISignal value,
the specified data type must be supported by the Bus Manager as well.
§ If the communication matrix does not specify a data type for the physical
ISignal value, it must either specify no computation method or a computation
method that the Bus Manager supports. In these cases, the Bus Manager
derives the physical data type from the coded data type and the computation
method.
§ If an ISignal is an array signal, the data type of the coded and physical ISignal
value must be UInt8. Other data types are not supported by the Bus Manager.

For an overview of the supported data types, refer to:

§ Bus Manager in ConfigurationDesk: Supported PDU Types and Signal Data
Types (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Supported PDU Types and Signal Data Types (Bus
Manager (Stand-Alone) Implementation Guide ).

37
May 2024 ConfigurationDesk Conflicts
Conflicts

For information on supported computation methods, refer to:

§ Bus Manager in ConfigurationDesk: Signal Conversion by the Bus Manager
(ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Signal Conversion by the Bus Manager (Bus
Manager (Stand-Alone) Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Note

Depending on the cause of the conflict, this remedy might not resolve
the conflict. For example, if the conflicting base data type is not
specified at all or the Bus Manager cannot derive it, the related Base
data type property is not available in ConfigurationDesk.

§ Resolve the conflict by correcting the original communication matrix. Refer

to:
Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Coding: Unsupported data A communication matrix specifies at least one of the following settings for an
types (communication matrix) ISignal:
§ For the coded ISignal value, no data type is specified.
§ For the coded and/or physical ISignal value, an unsupported data type is
specified.

38
ConfigurationDesk Conflicts May 2024
Coding Conflicts

§ For the physical ISignal value, no data type is specified. In addition, a specified
computation method is not supported.
§ The ISignal is an array signal but the specified data type of the coded and/or
physical ISignal value is not supported for array signals.

The communication matrix must specify the coding of ISignals as follows:

For an overview of the supported data types, refer to:

For information on supported computation methods, refer to:

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify valid values for the coded and/or physical Base data type properties,
or change the signal type via the Category property, for example, in
the Conflicts Viewer. This changes the communication matrix in the
active ConfigurationDesk application and all element instances in all bus
configurations of the application. The originally imported communication
matrix remains unchanged.

39
May 2024 ConfigurationDesk Conflicts
Conflicts

Note

Depending on the cause of the conflict, this remedy might not resolve
the conflict. For example, if the conflicting base data type is not specified
at all or the Bus Manager cannot derive it, the related Base data type
property is not available in ConfigurationDesk.

Coding: Unsupported or A conflicting communication matrix element is assigned to a bus configuration.

invalid linear scaling (bus For a linear computation method of an assigned ISignal, the communication
configuration) matrix specifies an unsupported or invalid computation scale.

To transmit or receive an ISignal via a bus, the ISignal must be encoded or

decoded according to a computation method. If the communication matrix
specifies a computation method for an ISignal, it must be valid and supported by
the Bus Manager.

For more information, refer to:

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

40
ConfigurationDesk Conflicts May 2024
Coding Conflicts

active ConfigurationDesk application and all element instances in all bus

configurations of the application. The originally imported communication
matrix remains unchanged.

Tip

The Conflicts Viewer displays the coding and the related computation
method but not the ISignal itself. To access the related ISignal,
right-click the coding and select Select Related Elements in Bus
Configurations Table from the context menu.

For information on the valid values, refer to:

Bus Manager in ConfigurationDesk: Configurable Settings of ISignals
(ConfigurationDesk Bus Manager Implementation Guide ).
Bus Manager (stand-alone): Configurable Settings of ISignals (Bus Manager
(Stand-Alone) Implementation Guide ).
§ Resolve the conflict by correcting the original communication matrix. Refer
to:
Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Coding: Unsupported or A communication matrix specifies an unsupported or invalid computation scale

invalid linear scaling for a linear computation method of an ISignal.
(communication matrix)
To transmit or receive an ISignal via a bus, the ISignal must be encoded or
decoded according to a computation method. If the communication matrix
specifies a computation method for an ISignal, it must be valid and supported by
the Bus Manager.

For more information, refer to:

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify valid values for the numerator and/or denominator arrays: Select
the related ISignal, for example, in the Buses Browser and specify
valid values for the Numerators and Denominators properties in the
Properties Browser. This changes the communication matrix in the
active ConfigurationDesk application and all element instances in all bus

41
May 2024 ConfigurationDesk Conflicts
Conflicts

configurations of the application. The originally imported communication

matrix remains unchanged.

Tip

The Conflicts Viewer displays the coding and the related computation
method but not the ISignal itself. If the names of the coding or
computation method match the ISignal name, you can use the displayed
names to search for the ISignal via the Find command, for example.

For information on the valid values, refer to:

§ Bus Manager in ConfigurationDesk: Configurable Settings of ISignals
(ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Configurable Settings of ISignals (Bus Manager
(Stand-Alone) Implementation Guide ).
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Communication Connector Conflicts

Communication connector: A communication matrix specifies no or more than one communication

Invalid number of controller for an ECU connector.
communication controllers
For each ECU connector, the communication matrix must specify exactly one
(communication matrix)
communication controller.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

42
ConfigurationDesk Conflicts May 2024
Communication Matrix Conflicts

Communication Matrix Conflicts

Communication matrix: Two or more different communication matrix nodes of a bus configuration have
Duplicate name in bus identical names.
configuration
The names of different communication matrix nodes in a bus configuration (e.g.,
all the communication matrix nodes below the Bus access requests node in the
Bus Configurations table) must be unique within the bus configuration.

Tip

The name of a communication matrix node in a bus configuration can

be user-defined. The name of a communication matrix itself cannot be
changed in ConfigurationDesk. For details on the node name, refer to:
§ Bus Manager in ConfigurationDesk: Basics on Bus Configurations
(ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Basics on Bus Configurations (Bus Manager
(Stand-Alone) Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy In the Conflicts Viewer, for example, specify unique names for the
affected communication matrix nodes.

Communication matrix: Failed A communication matrix is added to the active ConfigurationDesk application
consistency checks during and this communication matrix contains inconsistent settings (e.g., a channel
import of communication that references a coding instead of a frame triggering due to an incorrect ID).
matrix
Inconsistent settings can cause unintended behavior in ConfigurationDesk or
at run time (e.g., due to incorrectly generated tasks). To prevent unintended
behavior, the settings defined in a communication matrices must be consistent.

Tip

When you add the communication matrix to the active application,

the Message Viewer provides a warning message including detailed
information for each inconsistent setting.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

43
May 2024 ConfigurationDesk Conflicts
Conflicts

Communication matrix: Failed A communication matrix that complies with AUTOSAR or FIBEX is added to
schema check during import the active ConfigurationDesk application. This communication matrix contains
of communication matrix settings that are invalid according to the XML schema defined by the AUTOSAR
or FIBEX standard, respectively.

Invalid settings can cause unintended behavior in ConfigurationDesk or at run

time (e.g., due to incorrectly generated tasks). To prevent unintended behavior,
the settings of AUTOSAR- or FIBEX-compliant communication matrices must be
valid according to the AUTOSAR or FIBEX XML schema, respectively.

Tip

When you add the communication matrix to the active application,

the Message Viewer provides a warning message including detailed
information for each invalid setting.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Communication Package Conflicts

Communication package: The active ConfigurationDesk application contains two or more communication
Duplicate name packages with the same name.

The names of communication packages must be unique.

44
ConfigurationDesk Conflicts May 2024
Contained IPDU Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, enter unique names for the
communication packages in the Name edit field.

Communication package: The model implementations assigned to the same application process are
Existing closed loop connected via a closed loop with blocking model communication.
of blocking model
To enable ConfigurationDesk to optimize the configuration of application
communications
processes to which multiple model implementations are assigned, the following
blocks of at least one model implementation must be assigned to a
communication package with non-blocking communication:

All Data Inport blocks that are part of the closed loop of blocking
communication.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy In the Model Communication Package table, assign the following

blocks of at least one model implementation to a communication package with
non-blocking communication:
All Data Inport blocks that are part of the closed loop of blocking
communication.

Contained IPDU Conflicts

Contained IPDU: Duplicate Conflicting communication matrix elements are assigned to a bus configuration.
header ID (bus configuration) For at least two assigned IPDUs, the communication matrix specifies the
following settings:
§ The IPDUs are contained IPDUs that are included in dynamic container IPDUs
(i.e., the header type of the container IPDUs is SHORT-HEADER or LONG-
HEADER).
§ The header IDs of the contained IPDUs are not unique for the header type in
the applicable context.

45
May 2024 ConfigurationDesk Conflicts
Conflicts

According to AUTOSAR, the communication matrix must specify a header ID

for each contained IPDU that is unique for the header type (SHORT-HEADER or
LONG-HEADER) in the applicable context, i.e.:
§ If the contained IPDU is included in at least one container IPDU whose RX-
ACCEPT-CONTAINED-IPDU attribute is set to ACCEPT-ALL, the header ID must
be unique within the communication matrix.
§ If the contained IPDU is included only in container IPDUs whose RX-ACCEPT-
CONTAINED-IPDU attribute is set to ACCEPT-CONFIGURED, the header ID must
be unique within each container IPDU.

With the Bus Manager, the header ID must be unique for the header type
(SHORT-HEADER or LONG-HEADER) in each bus configuration.

If you do not resolve this conflict, default code is generated, i.e., even though
the header IDs are not unique in the applicable context, the related container
IPDUs can be transmitted and received at run time. However, it is unpredictable
which IPDU is used as contained IPDU. This might result in unexpected or
incorrect payload data of the container IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

§ Remove the conflicting element from the bus configuration: In the Conflicts
Viewer, set the element's Is assigned property to False to remove only
this conflicting element. Alternatively, set the bus configuration's Is assigned
property to False to remove all conflicting elements in one step.
Depending on the type of the conflicting element, related elements are
removed as well, e.g., all ISignals of a conflicting ISignal IPDU.
§ Correct the setting in the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Contained IPDU: Duplicate A communication matrix specifies the following settings for an IPDU:
header ID (communication § The IPDU is a contained IPDU that is included in a dynamic container IPDU (i.e.,
matrix) the header type of the container IPDU is SHORT-HEADER or LONG-HEADER).
§ The IPDU's header ID is not unique for the header type in the applicable
context.

For each contained IPDU, the communication matrix must specify a header ID
that is unique for the header type (SHORT-HEADER or LONG-HEADER) in the
applicable context, i.e.:
§ If the contained IPDU is included in at least one container IPDU whose RX-
ACCEPT-CONTAINED-IPDU attribute is set to ACCEPT-ALL, the header ID must
be unique within the communication matrix.

46
ConfigurationDesk Conflicts May 2024
Contained IPDU Conflicts

§ If the contained IPDU is included only in container IPDUs whose RX-ACCEPT-

CONTAINED-IPDU attribute is set to ACCEPT-CONFIGURED, the header ID must
be unique within each container IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Contained IPDU: Invalid offset A conflicting communication matrix element is assigned to a bus configuration.
value (bus configuration) For an assigned IPDU, the communication matrix specifies the following settings:
§ The IPDU is a contained IPDU that is included in a static container IPDU (i.e.,
the header type of the container IPDU is NO-HEADER).
§ For the contained IPDU, no offset value is specified or a specified offset value is
invalid.

For a contained IPDU that is included in a static container IPDU, an offset value
must be specified. The offset value must be within the range of the container
IPDU and must not overlap with other offset values.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

47
May 2024 ConfigurationDesk Conflicts
Conflicts

Contained IPDU: Invalid offset A communication matrix specifies the following settings for an IPDU:
value (communication matrix) § The IPDU is a contained IPDU that is included in a static container IPDU (i.e.,
the header type of the container IPDU is NO-HEADER).
§ For the contained IPDU, no offset value is specified or a specified offset value is
invalid.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Contained IPDU: Invalid A conflicting communication matrix element is assigned to a bus configuration.
update bit position (bus For an assigned IPDU, the communication matrix specifies the following settings:
configuration) § The IPDU is a contained IPDU that is included in a static container IPDU (i.e.,
the header type of the container IPDU is NO-HEADER).
§ For the update bit position of the contained IPDU, one of the following
settings is specified:
§ No update bit position is specified, and for the related static container IPDU
no unused bit pattern is specified.
§ A specified update bit position is invalid.

For a contained IPDU that is included in a static container IPDU without a

specified unused bit pattern, an update bit position must be specified. The
update bit position must be within the range of the container IPDU and must not
overlap with other update bit positions.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

48
ConfigurationDesk Conflicts May 2024
Contained IPDU Conflicts

element. Alternatively, set the bus configuration's Is assigned property to

False to remove all conflicting elements in one step.
Depending on the type of the conflicting element, related elements are
removed as well, e.g., all ISignals of a conflicting ISignal IPDU.
§ If you need the conflicting element in the executable application, correct the
setting in the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Contained IPDU: Invalid A communication matrix specifies the following settings for an IPDU:
update bit position § The IPDU is a contained IPDU that is included in a static container IPDU (i.e.,
(communication matrix) the header type of the container IPDU is NO-HEADER).
§ For the update bit position of the contained IPDU, one of the following
settings is specified:
§ No update bit position is specified, and for the related static container IPDU
no unused bit pattern is specified.
§ A specified update bit position is invalid.

For a contained IPDU that is included in a static container IPDU without a

specified unused bit pattern, an update bit position must be specified. The
update bit position must be within the range of the container IPDU and must not
overlap with other update bit positions.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

49
May 2024 ConfigurationDesk Conflicts
Conflicts

Contained IPDU: Missing A conflicting communication matrix element is assigned to a bus configuration.
collection semantics (bus For an assigned IPDU, the communication matrix specifies the following settings:
configuration) § The IPDU is a contained IPDU that is included in a container IPDU with a
dynamic container layout.
§ For the IPDU, no collection semantics is specified.

For each contained IPDU, the communication matrix must specify the collection
semantics. For contained IPDUs that are included in a container IPDU with a
dynamic layout, the collection semantics can be either queued or last‑is‑best.
According to AUTOSAR, the collection semantics of all contained IPDUs that are
included in the same container IPDU must be identical.

Tip

In contrast to AUTOSAR, the Bus Manager supports contained IPDUs with

different collection semantics in the same container IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

50
ConfigurationDesk Conflicts May 2024
Contained IPDU Conflicts

Contained IPDU: Missing A communication matrix specifies the following settings for an IPDU:
collection semantics § The IPDU is a contained IPDU that is included in a container IPDU with a
(communication matrix) dynamic container layout.
§ For the IPDU, no collection semantics is specified.

Tip

In contrast to AUTOSAR, the Bus Manager supports contained IPDUs with

different collection semantics in the same container IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify a value for the Collection semantics property, for example, in
the Conflicts Viewer. This changes the communication matrix in the
active ConfigurationDesk application and all element instances in all bus
configurations of the application. The originally imported communication
matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Contained IPDU: Mismatching A conflicting communication matrix element is assigned to a bus configuration.
header ID (bus configuration) For an assigned IPDU, the communication matrix specifies the following settings:
§ The IPDU is a contained IPDU that is included in a dynamic container IPDU (i.e.,
the header type of the container IPDU is SHORT-HEADER or LONG-HEADER).
§ For the contained IPDU, the required header ID is not specified or a specified
header ID is invalid.

A contained IPDU can have two header IDs, one for each header type (SHORT-
HEADER or LONG-HEADER). The header type of the container IPDU determines
which header ID of the contained IPDU is required. This header ID must be
specified. Valid ranges for the header IDs are:
§ Short header ID: 0 … 224-1
§ Long header ID: 0 … 232-1

51
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Contained IPDU: Mismatching A communication matrix specifies the following settings for an IPDU:
header ID (communication § The IPDU is a contained IPDU that is included in a dynamic container IPDU (i.e.,
matrix) the header type of the container IPDU is SHORT-HEADER or LONG-HEADER).
§ For the contained IPDU, the required header ID is not specified or a specified
header ID is invalid.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

52
ConfigurationDesk Conflicts May 2024
Contained IPDU Conflicts

Contained IPDU: Mismatching A conflicting communication matrix element is assigned to a bus configuration.
IPDU length (bus For an assigned IPDU, the communication matrix specifies the following settings:
configuration) The IPDU is a contained IPDU (i.e., it is included in a container IPDU) but the
IPDU's payload length is too long.

The maximum valid payload length of a contained IPDU depends on:

§ The length and the header type of the container IPDU:
§ Container IPDU with SHORT-HEADER header type:
contained_IPDU_payloadmax ≤ (container_IPDU_length - 32 bit)
§ Container IPDU with LONG-HEADER header type:
contained_IPDU_payloadmax ≤ (container_IPDU_length - 64 bit)
§ Container IPDU with NO-HEADER header type:
contained_IPDU_payloadmax ≤ (container_IPDU_length)
§ The payload lengths of the other contained IPDUs that are included in the
container IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

53
May 2024 ConfigurationDesk Conflicts
Conflicts

Contained IPDU: Mismatching A communication matrix specifies the following settings for an IPDU: The IPDU is
IPDU length (communication a contained IPDU (i.e., it is included in a container IPDU) but the IPDU's payload
matrix) length is too long.

The maximum valid payload length of a contained IPDU depends on:

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
In the Conflicts Viewer, for example, extend the length of the container
IPDU and/or reduce the length of the contained IPDUs via the related Length
property.
This changes the communication matrix in the active ConfigurationDesk
application and all element instances in all bus configurations of
the application. The originally imported communication matrix remains
unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Contained IPDU: Multiple Conflicting communication matrix elements are assigned to the Simulated ECUs
container IPDUs related (bus part of a bus configuration. For assigned TX IPDUs, the communication matrix
configuration) specifies the following settings:
§ At least one assigned TX IPDU is a contained IPDU that is included in more
than one container IPDU of the same ECU.
§ At least two of the related container IPDUs of the same ECU are assigned as
well.

For each ECU, a TX contained IPDU must be included in exactly one container
IPDU.

54
ConfigurationDesk Conflicts May 2024
Contained IPDU Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Contained IPDU: Multiple A communication matrix specifies the following settings for a TX IPDU: The TX
container IPDUs related IPDU is a contained IPDU that is included in more than one container IPDU of the
(communication matrix) same ECU.

For each ECU, a TX contained IPDU must be included in exactly one container
IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Contained IPDU: Unsupported A conflicting communication matrix element is assigned to a bus configuration.
header byte order (bus For an assigned IPDU, the communication matrix specifies the following settings:
configuration) § The IPDU is a contained IPDU that is included in a dynamic container IPDU (i.e.,
the header type of the container IPDU is SHORT-HEADER or LONG-HEADER).
§ For the header of the contained IPDU, no or an unsupported byte order is
specified.

55
May 2024 ConfigurationDesk Conflicts
Conflicts

For each contained IPDU, the byte order of the header must be specified. The
byte order must be either LITTLE_ENDIAN or BIG_ENDIAN.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Contained IPDU: Unsupported A communication matrix specifies the following settings for an IPDU:
header byte order § The IPDU is a contained IPDU that is included in a dynamic container IPDU (i.e.,
(communication matrix) the header type of the container IPDU is SHORT-HEADER or LONG-HEADER).
§ For the header of the contained IPDU, no or an unsupported byte order is
specified.

For each contained IPDU, the byte order of the header must be specified. The
byte order must be either LITTLE_ENDIAN or BIG_ENDIAN.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

56
ConfigurationDesk Conflicts May 2024
Container IPDU Conflicts

Contained IPDU: Unsupported A communication matrix specifies the following settings for an IPDU:
header ID 0 (communication § The IPDU is a contained IPDU that is included in a dynamic container IPDU (i.e.,
matrix) the header type of the container IPDU is SHORT-HEADER or LONG-HEADER).
§ At least one of the contained IPDU's header IDs is 0.

A contained IPDU can have two header IDs, one for each header type (SHORT-
HEADER or LONG-HEADER). None of the header IDs must be 0.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Container IPDU Conflicts

Container IPDU: Invalid A conflicting communication matrix element is assigned to a bus configuration.
header type (bus For an assigned IPDU, the communication matrix specifies the following settings:
configuration) The IPDU is a container IPDU (i.e., other IPDUs can be included in this IPDU) but
the IPDU's header type is not specified or a specified header type is invalid.

For each container IPDU, the communication matrix must specify the header
type. Valid header types are:
§ SHORT-HEADER
§ LONG-HEADER
§ NO-HEADER

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

57
May 2024 ConfigurationDesk Conflicts
Conflicts

Depending on the type of the conflicting element, related elements are

removed as well, e.g., all ISignals of a conflicting ISignal IPDU.
§ If you need the conflicting element in the executable application, correct the
setting in the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Container IPDU: Invalid A communication matrix specifies the following settings for an IPDU: The IPDU is
header type (communication a container IPDU (i.e., other IPDUs can be included in this IPDU) but the IPDU's
matrix) header type is not specified or a specified header type is invalid.

For each container IPDU, the communication matrix must specify the header
type. Valid header types are:
§ SHORT-HEADER
§ LONG-HEADER
§ NO-HEADER

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Container IPDU: Invalid A conflicting communication matrix element is assigned to a bus configuration.
timeout value (bus For an assigned IPDU, the communication matrix specifies the following settings:
configuration) § The IPDU is a container IPDU (i.e., other IPDUs can be included in this IPDU).
§ For the container IPDU and/or at least one of its contained IPDUs, an invalid
timeout value is specified.

If the communication matrix specifies a timeout value for a container IPDU or its
contained IPDUs, the specified value must be in the range 0 … 65,535 seconds.
However, to transmit a container IPDU according to a timeout value, at least one
timeout value must be > 0 seconds.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

58
ConfigurationDesk Conflicts May 2024
Container IPDU Conflicts

Remedy Choose one of the following alternatives:

Note

This remedy is not applicable for container IPDUs because you

cannot configure the timeout value of container IPDUs in the
ConfigurationDesk application.

§ Resolve the conflict by correcting the original communication matrix. Refer

Container IPDU: A communication matrix specifies the following settings for an IPDU:
Invalid timeout value § The IPDU is a container IPDU (i.e., other IPDUs can be included in this IPDU).
(communication matrix) § For the container IPDU and/or at least one of its contained IPDUs, an invalid
timeout value is specified.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:

59
May 2024 ConfigurationDesk Conflicts
Conflicts

If the timeout value of a contained IPDU is invalid, specify a valid value for
the Timeout property, for example, in the Conflicts Viewer. This changes
the communication matrix in the active ConfigurationDesk application and all
element instances in all bus configurations of the application. The originally
imported communication matrix remains unchanged.

Note

This remedy is not applicable for container IPDUs because you cannot
configure the timeout value of container IPDUs in the ConfigurationDesk
application.

Container IPDU: Unsupported A conflicting communication matrix element is assigned to a bus configuration.
nested container (bus For an assigned IPDU, the communication matrix specifies the following settings:
configuration) § The IPDU is a container IPDU (i.e., other IPDUs can be included in this IPDU).
§ The IPDU contains an IPDU that is a container IPDU itself.

A container IPDU can contain only IPDUs that are no container IPDUs themselves.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

60
ConfigurationDesk Conflicts May 2024
Device Block Conflicts

Container IPDU: Unsupported A communication matrix specifies the following settings for an IPDU:
nested container § The IPDU is a container IPDU (i.e., other IPDUs can be included in this IPDU).
(communication matrix) § The IPDU contains an IPDU that is a container IPDU itself.

A container IPDU can contain only IPDUs that are no container IPDUs themselves.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Device Block Conflicts

Device block: Unresolved At least one device topology element is used in the signal chain, but missing in
elements the device topology.

Such elements are unresolved and displayed with a warning symbol in the
External Device Browser. For details, refer to Basics on Device Blocks
(ConfigurationDesk Real-Time Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy The Conflicts Viewer displays the missing device topology

elements.
Choose one of the following alternatives:
§ In the Conflicts Viewer, select the higher hierarchy element of the missing
element in the Value column to resolve the conflict.
§ In the External Device Browser, right-click the missing element(s) and select
Make Resolved from the context menu.
§ Replace the device topology by a version that contains the missing elements.
§ Delete the element(s) from the signal chain of the active ConfigurationDesk
application.

61
May 2024 ConfigurationDesk Conflicts
Conflicts

Device Conflicts

Device: Duplicate name The active ConfigurationDesk application contains two or more device blocks
with the same name.

Device block names must be unique in an application. Duplicate device names

might cause problems when you import or export device data.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – ✓

Remedy In the Conflicts Viewer, for example, enter unique names for the
device blocks.

Device: Invalid pin assignment A device pin assigned to a device port is part of another device.

For more information on device pin assignment, see Basics on Configuring

External Devices (ConfigurationDesk Real-Time Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy The Conflicts Viewer displays the affected device pin.

Choose one of the following alternatives:
§ In the External Device Connectors table, move the device pin to the correct
device block.
§ In the Pins and External Wiring table, assign the device pin to a different
device port.
§ In the External Device Browser, adjust the device topology to match the
device pin assignment.

Device: Invalid port The reference port(s) of a device port are located in a different device.
assignment
You must only assign reference ports that belong to the same device.

For more information on reference ports, see Basics on Configuring External

Devices (ConfigurationDesk Real-Time Implementation Guide ).

62
ConfigurationDesk Conflicts May 2024
Device Pin Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy The Conflicts Viewer displays the affected ports and their locations
in the device topology (port group addresses).
Choose one of the following alternatives:
§ In the External Device Browser, move all ports referencing each other to the
same device.
§ Remove the port references via the Properties Browser.

Device Pin Conflicts

Device pin: Duplicate name The active ConfigurationDesk application contains two or more device pins with
the same name.

Device pin names must be unique in a connector or device. Otherwise, exported

device or pin data might become ambiguous.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – ✓

Remedy In the Conflicts Viewer, enter unique names for the device pins.

Device Port Conflicts

Device port: Duplicate name The active ConfigurationDesk application contains two or more device ports with
the same name in a port group or a device.

Device port names must be unique in a port group or a device. Otherwise,

exported device data might become ambiguous.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – ✓

63
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy In the Conflicts Viewer, for example, enter unique names for the
device ports.

Device Port Mapping Conflicts

Device port mapping: There is an unrecommended mapping between device ports or signal ports in the
Mismatching port type currently active ConfigurationDesk application.

Certain mappings between device and signal ports are not recommended, such
as mapping a bidirectional device port and a signal reference port.

For more information, see Device Port Mapping (ConfigurationDesk Real-Time

Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ In a working view, adjust the device port mapping.
§ In the Conflicts Viewer, for example, change the port type of the device port.

ECU Conflicts

ECU: Duplicate name (bus Conflicting communication matrix elements are assigned to a bus configuration.
configuration) For two or more assigned ECUs, the communication matrix defines identical
names.

For each ECU, the communication matrix must define a unique name.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

64
ConfigurationDesk Conflicts May 2024
Event Conflicts

Depending on the type of the conflicting element, related elements are

ECU: Duplicate name A communication matrix defines identical names for two or more ECUs.
(communication matrix)
For each ECU, the communication matrix must define a unique name.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Event Conflicts

Event: Delay value of delayed The Delay value of the delayed event exceeds the period limits of the timer
event exceeds limits of event that triggers the source task.
assigned source task period
The Delay value must be smaller than two times the period of the timer event
that triggers the source task.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, specify a Delay value in the
valid range.

Event: Invalid source task for An invalid source task is specified for the delayed event.
delayed event
A source task must be a task other than the task to be delayed.

65
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – – – –

Remedy In the Conflicts Viewer, for example, select a task other than the
task to be delayed as the source task from the Value list.

Event: No source task No source task is specified for the delayed event.
assigned to delayed event
A valid source task must be specified for the delayed event.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy In the Conflicts Viewer, for example, select a valid source task from
the Value list.

Event: Multiple assignments There is an event assigned to different tasks in an application process.
to different tasks
An event must be assigned to only one task in an application process.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, select exactly one task that
the event must be assigned to in the Value column (next to the Assigned to
field).

Event: Multiple timer events Two or more timer events in the executable application are configured to be
are configured to be sent via sent via Gigalink, and the same combination of Gigalink Number and Channel
the same Gigalink channel Number is used for these timer events.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

66
ConfigurationDesk Conflicts May 2024
Executable Application Conflicts

Remedy In the Conflicts Viewer, for example, configure different

combinations of Gigalink number and Channel number for the timer events.

Executable Application Conflicts

Executable application: The executable application contains two or more application processes with the
Duplicate application process same name.
names
Application process names must be unique.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, enter unique names in the
Name edit field for all application processes.

Executable application: Two or more tasks are assigned to different application processes with one of the
Duplicate DAQ raster name following modeling constellations:
for nonsynchronous tasks § Case 1: The tasks are triggered by timer events with different periods, and
have the same DAQ raster name specified.
§ Case 2: The tasks are not triggered by timer events, and have the same DAQ
raster name specified.
§ Case 3: At least one task is triggered by a timer event, and at least one task
is not triggered by a timer event. The tasks have the same DAQ raster name
specified.

If two application processes contain tasks with the same DAQ raster name, the
experiment tool interprets this as meaning that these tasks are triggered at the
same times, and that signals from the two application processes can be recorded
together via the same DAQ raster. However, if the rasters have the same name
but different trigger times, this can have side-effects on the measurement.

Effects (cases 1 and 3)

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

67
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects (case 2)

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy In the Conflicts Viewer, for example, enter unique DAQ raster
names for the tasks in the DAQ raster name edit field.

Executable application: At least two application processes with assigned SLX files or SIC files have the
Duplicate XCP service port same XCP service port specified.

XCP ports must be unique for application processes with assigned SLX files or
SIC files.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, specify unique XCP ports for
the application processes in the XCP service port edit field.

Executable application: There are two or more periodic tasks assigned to different application processes.
Mismatching DAQ raster The timer events triggering the tasks have the same period. The DAQ raster
names for tasks with same names specified for the tasks are different (not empty).
timer event periods
If two application processes contain tasks triggered at the same times, it is useful
to enter the same DAQ raster name for the tasks. In the experiment tool, the
signals from the two application processes can then be recorded together via the
same DAQ raster. A warning is issued during the build process.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy In the Conflicts Viewer, for example, enter identical names in the
DAQ raster name edit field for the tasks.

Executable application: No There is no processing unit application defined in the executable application.
processing unit application
An executable application must have at least one processing unit application
defined
with at least one application process.

68
ConfigurationDesk Conflicts May 2024
Executable Application Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Depending on your use scenario, choose one of the following

alternatives:
§ If the executable application already contains a model:
Right-click the model in the Model Browser and create a preconfigured
application process using the Create Preconfigured Application Process
command.
§ If the executable application does not contain a model:
Right-click the empty space in the Task Configuration table and add a
model using the Add Model command. ConfigurationDesk then creates a
preconfigured application process in a new processing unit application.
§ In the Task Configuration table, create an application process using the New
- Application Process or the New - Application Process (Providing default
task) command.
§ If you want to model a multi-processing-unit application, in the Processing
Resource Assignment table, create a processing unit application using the
New - Processing Unit Application or the New - Multiple Processing Unit
Applications command.

Executable application: Too There are too many processing unit applications defined in the executable
many processing unit application.
applications defined (max. is
The maximum allowed number of processing unit applications is 32.
32)
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Processing Resource Assignment table, delete excess

processing unit applications from the executable application.

Executable application: An unsupported real-time hardware, for example a MicroAutoBox III processor
Unsupported hardware board, is assigned to a processing unit application that is contained in a multi-
in a multi-processing-unit processing-unit application.
application
If you use a real-time hardware that is not supported in a multi-processing-unit
application, all application processes must be assigned to the same processing
unit application.

69
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – – – –

Remedy Choose one of the following alternatives:

§ In the Processing Resource Assignment table, assign all application
processes to the same processing unit application. Then delete all empty
processing unit applications.
§ In the Conflicts Viewer, for example, assign a processing unit that is
supported in multi-processing-unit applications to the relevant processing unit
application.

External Cable Harness Conflicts

External cable harness: The pin(s) assigned to a device port are not equivalent to the wiring information
Mismatching pin set in the external cable harness of the active ConfigurationDesk application.
assignment
For more information, refer to Calculating an External Cable Harness
(ConfigurationDesk Real-Time Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, adjust the pin set assignment to match the external
cable harness.
§ Recalculate the wiring information. Note that if you want to continue using
an existing physical cable harness, you must not recalculate the wiring
information. For instructions, refer to How to (Re)Calculate the External Cable
Harness (ConfigurationDesk Real-Time Implementation Guide ).

External cable harness: There are device port mapping lines which are not represented in the calculated
Missing wiring connections external cable harness of the currently active ConfigurationDesk application.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

70
ConfigurationDesk Conflicts May 2024
Feature Conflicts

Remedy The Conflicts Viewer displays the mapped device and/or signal
ports.
Choose one of the following alternatives:
§ In a working view, remove the mapping lines by using the context menu
command Delete from Application.
§ Recalculate the wiring information. Note that if you want to continue using
an existing physical cable harness, you must not recalculate the wiring
information. For instructions, refer to How to (Re)Calculate the External Cable
Harness (ConfigurationDesk Real-Time Implementation Guide ).

External cable harness: The external cable harness contains a connection between pins of device ports
Too many connected and/or signal ports that is not represented in the logical signal chain (i.e., the
ports (compared to device device port mapping lines are missing).
mapping)
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy The Conflicts Viewer displays the device and signal ports that need
to be mapped.
Choose one of the following alternatives:
§ Complete the mapping in a working view.
§ Recalculate the wiring information. Note that if you want to continue using
an existing physical cable harness, you must not recalculate the wiring
information. For instructions, refer to How to (Re)Calculate the External Cable
Harness (ConfigurationDesk Real-Time Implementation Guide ).

Feature Conflicts

Feature: Duplicate feature One or more bus manipulation features are added to an ISignal. For the feature
switch value switch of the ISignal, two or more identical values are available.

All the values that are available for the feature switch of an ISignal must be
unambiguous.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

71
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

§ If you need neither the conflicting features nor the ISignal in the executable
application, remove the ISignal from the bus configuration. In the Conflicts
Viewer, for example, right-click the ISignal and select Show – Show in Bus
Configurations Table on the context menu. In the bus configuration, delete
the selected ISignal.
§ If you need only one of the conflicting features in your executable application,
disable all other conflicting features. In the Conflicts Viewer, for example, set
the Enabled property of the related feature nodes to False.
§ If you need all the conflicting features in your executable application,
assign the ISignal to different bus configurations. Disable all but one of the
conflicting features for the ISignal of this bus configuration. For each of the
other bus configurations, add only one of the conflicting features to the
ISignal.

Feature: Invalid feature switch One or more bus manipulation features are added to an ISignal. The specified
value value of the feature switch references a bus manipulation feature that was
disabled for the ISignal.

The value that is specified for the feature switch of an ISignal must correspond to
a bus manipulation feature that is added to the ISignal.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

72
ConfigurationDesk Conflicts May 2024
Feature Conflicts

Feature: Invalid property The PDU User Code feature is added to a PDU. For the feature, at least one of
values for user code the following settings is specified:
(Inspection) § No user code ID is specified.
§ An ISignal is assigned to a user signal but according to the communication
matrix this ISignal is not included in the PDU.

For the PDU User Code feature, the following conditions apply:
§ A user code ID must be specified.
§ ISignals can be assigned to user signals only if they are included in the related
PDU according to the specifications of the communication matrix.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Feature: Invalid property The PDU User Code feature is added to a PDU. For the feature, at least one of
values for user code the following settings is specified:
(Manipulation) § No user code ID is specified.
§ An ISignal is assigned to a user signal but according to the communication
matrix this ISignal is not included in the PDU.

73
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Feature: Invalid property The PDU User Code feature is added to a PDU. For the feature, at least one of
values for user code the following settings is specified:
(Simulated ECUs) § No user code ID is specified.
§ An ISignal is assigned to a user signal but according to the communication
matrix this ISignal is not included in the PDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

74
ConfigurationDesk Conflicts May 2024
Feature Conflicts

feature's Enabled property to False to disable only this conflicting feature.

Feature: Invalid property The Counter Signal feature is added to an ISignal. At least one of the following
values of counter signal conflicting counter settings is specified for the feature:
(Inspection) § maximum value ≤ minimum value
§ increment value > (maximum value - minimum value)
§ initial value < minimum value
§ initial value > maximum value

The counter settings of the Counter Signal feature must be specified as follows:
§ maximum value > minimum value
§ increment value ≤ (maximum value - minimum value)
§ initial value ≥ minimum value
§ initial value ≤ maximum value

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Feature: Mismatching counter The Counter Signal feature is added to an ISignal and at least one of the
signal range or unsupported following conflicting settings is specified:
physical data type (Inspection) § The specified physical base data type of the ISignal is not supported by the
Counter Signal feature.

75
May 2024 ConfigurationDesk Conflicts
Conflicts

§ The specified counter minimum value or counter maximum value exceeds the
valid counter signal range.

To use the Counter Signal feature, the physical base data type of the ISignal
must be an integer type. Additionally, the specified counter minimum and
maximum values must be within the valid counter signal range. The valid counter
signal range is determined by the ISignal's physical and coded base data types,
and the ISignal's length.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

§ If you need neither the conflicting feature nor the related bus configuration
element in the executable application, remove the bus configuration element
from the bus configuration. In the Conflicts Viewer, for example, right-
click the bus configuration element and select Show – Show in Bus
Configurations Table on the context menu. In the bus configuration, delete
the selected element.
§ If you do not need the conflicting feature in the executable application,
disable it for the bus configuration. In the Conflicts Viewer, set the
feature's Enabled property to False to disable only this conflicting feature.
Alternatively, set the bus configuration's Enabled property to False to disable
all conflicting features in one step.
§ If you need the conflicting feature in the executable application, specify
valid values for the conflicting settings. Depending on the conflict cause, the
conflicting settings can be the following:
§ Physical base data type of the ISignal
§ Coded base data type of the ISignal
§ Length of the ISignal
§ Maximum counter value
§ Minimum counter value
You can access the settings, for example, in the Conflicts Viewer and/or in
the Properties Browser when you select the related ISignal.
Changing the physical or coded base data type or the ISignal's length
changes the communication matrix in the active ConfigurationDesk application
and all ISignal instances in all bus configurations of the application. The
originally imported communication matrix remains unchanged. Changing the
maximum or minimum counter value changes only the counter signal in the
related bus configuration. Other counter signals, bus configurations, and the
communication matrix remain unchanged.

Feature: Invalid property The Counter Signal feature is added to an ISignal. At least one of the following
values of counter signal conflicting counter settings is specified for the feature:
(Simulated ECUs) § maximum value ≤ minimum value
§ increment value > (maximum value - minimum value)

76
ConfigurationDesk Conflicts May 2024
Feature Conflicts

§ initial value < minimum value

§ initial value > maximum value

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Feature: Mismatching counter The Counter Signal feature is added to an ISignal and at least one of the
signal range or unsupported following conflicting settings is specified:
physical data type (Simulated § The specified physical base data type of the ISignal is not supported by the
ECUs) Counter Signal feature.
§ The specified counter minimum value or counter maximum value exceeds the
valid counter signal range.

77
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Feature: Mismatching port The Frame Access feature is added to a PDU. A value that is specified for the
settings (length) Length function port of the feature exceeds the value that is specified for the
Maximum length property of the feature.

For the Length funtion port of the Frame Access feature, the values of
the Initial value, Initial substitute value, Saturation minimum value, and
Saturation maximum value properties must be equal to or smaller than the
value of the Maximum length property of the feature.

78
ConfigurationDesk Conflicts May 2024
Feature Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Feature: Mismatching port The Frame Length feature is added to a PDU. A value that is specified for the
settings (length) Length function port of the feature exceeds the maximum valid length of the
related frame.

For the Length function port of the Frame Length feature, the values
of the Initial value, Initial substitute value, Saturation minimum
value, and Saturation maximum value properties must be in the range
0 byte ...<maximum valid length> of the related frame. The maximum
valid length depends on whether the frame is a classic CAN frame or CAN FD
frame:
§ Classic CAN frame: <maximum valid length> = 8 bytes
§ CAN FD frame: <maximum valid length> = 64 bytes

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

79
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

§ If you need neither the conflicting feature nor the related bus configuration
element in the executable application, remove the bus configuration element
from the bus configuration. In the Conflicts Viewer, for example, right-
click the bus configuration element and select Show – Show in Bus
Configurations Table on the context menu. In the bus configuration, delete
the selected element.
§ If you do not need the conflicting feature in the executable application,
disable it for the bus configuration. In the Conflicts Viewer, set the
feature's Enabled property to False to disable only this conflicting feature.
Alternatively, set the bus configuration's Enabled property to False to disable
all conflicting features in one step.
§ If you need the conflicting feature in the executable application, choose one of
the following alternatives:
§ Specify valid values for the Initial value, Initial substitute value,
Saturation minimum value, and Saturation maximum value properties
of the Length function port, for example, in the Conflicts Viewer.
§ Enable CAN FD support for the frame. To do so, select the related PDU, for
example, in the Conflicts Viewer. On the Bus Communication page of the
Properties Browser, set the CAN FD frame support property of the frame
to True.
This changes the communication matrix in the active ConfigurationDesk
application and all frame instances in all bus configurations of the
application. The originally imported communication matrix remains
unchanged.

Feature: Mismatching port The PDU Length inspection feature is added to a PDU. A value that is specified
settings (PDU Length, for the Length function port of the feature exceeds the maximum valid PDU
Inspection) length.

For the Length funtion port of the PDU Length inspection feature, the values of
the Initial value and Initial substitute value properties must be in the range
0 … <PDU length specified in the communication matrix>.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

80
ConfigurationDesk Conflicts May 2024
Feature Conflicts

feature's Enabled property to False to disable only this conflicting feature.

Alternatively, set the bus configuration's Enabled property to False to disable
all conflicting features in one step.
§ If you need the conflicting feature in the executable application, choose one of
the following alternatives:
§ Specify valid values for the Initial value and Initial substitute value
properties of the Length function port, for example, in the Conflicts
Viewer.
§ Extend the PDU length in the communication matrix. To do so, select the
PDU, for example, in the Conflicts Viewer. On the General page of the
Properties Browser, extend the PDU length via the Length property.
This changes the communication matrix in the active ConfigurationDesk
application and all PDU instances in all bus configurations of the application.
The originally imported communication matrix remains unchanged.

Feature: Mismatching port The PDU Length simulation feature is added to a PDU. A value that is specified
settings (PDU Length, for the Length function port of the feature exceeds the maximum valid PDU
Simulated ECUs) length.

For the Length funtion port of the PDU Length simulation feature, the values
of the Initial value, Initial substitute value, Saturation minimum value,
and Saturation maximum value properties must be in the range 0 … <PDU
length specified in the communication matrix>.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

81
May 2024 ConfigurationDesk Conflicts
Conflicts

§ Extend the PDU length in the communication matrix. To do so, select the
PDU, for example, in the Conflicts Viewer. On the General page of the
Properties Browser, extend the PDU length via the Length property.
This changes the communication matrix in the active ConfigurationDesk
application and all PDU instances in all bus configurations of the application.
The originally imported communication matrix remains unchanged.

Feature: Unsupported bus A bus configuration feature is enabled which is no longer supported for the
configuration feature enabled affected bus configuration element.

Settings of the bus configuration element have changed in the communication

matrix, e.g., because the assigned communication matrix was replaced in the bus
configuration. Due to these changes, the bus configuration feature is no longer
supported for the bus configuration element.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Feature: Unsupported The Counter Signal feature and the ISignal Value feature are added to a TX
combination of Counter ISignal.
Signal feature and ISignal
When you add the Counter Signal feature to a TX ISignal, the ISignal Value
Value feature
feature cannot be used for the ISignal. If both features are added to the ISignal,
the ISignal Value feature is ignored. At run time, only the Counter Signal
feature applies to the TX ISignal.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

82
ConfigurationDesk Conflicts May 2024
Feature Conflicts

Remedy Choose one of the following alternatives:

§ If you need neither the conflicting features nor the ISignal in the executable
application, remove the ISignal from the bus configuration. In the Conflicts
Viewer, for example, right-click the ISignal and select Show – Show in Bus
Configurations Table on the context menu. In the bus configuration, delete
the selected ISignal.
§ If you do not need the Counter Signal feature in the executable application,
disable it for the ISignal. In the Conflicts Viewer, for example, set the
Enabled property of the Counter Signal node to False.
§ If you need only the Counter Signal feature in the executable application,
disable the ISignal Value feature: In the Conflicts Viewer, set the Enabled
property of the ISignal Value feature to False to disable the feature for an
individual ISignal. Alternatively, set the bus configuration's Enabled property
to False to disable all conflicting ISignal Value features in one step.
§ If you need all the conflicting features in your executable application, assign
the ISignals to different bus configurations. Disable all but one of the
conflicting features for this bus configuration. For each of the other bus
configurations, add only one of the conflicting features to the ISignals.

Feature: Unsupported The Frame Access feature is added to a PDU while other bus simulation features
combination of Frame Access are added to the PDU or to elements that are included in the PDU.
feature and other PDU or
When you add the Frame Access feature to a PDU, all other bus simulation
signal features
features must be disabled for the PDU and its included elements. Included
elements are:
§ Contained IPDUs if you add the feature to a container IPDU.
§ ISignal PDUs that are configured as the static or dynamic part if you add the
feature to a multiplexed IPDU.
§ ISignals that are directly included in the PDU or in any of its included PDUs.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

§ If you need neither the conflicting features nor the PDU and its included
elements in the executable application, remove the PDU from the bus
configuration. In the Conflicts Viewer, for example, right-click the PDU and
select Show – Show in Bus Configurations Table on the context menu.In
the bus configuration, delete the selected PDU.
§ If you do not need the Frame Access feature in the executable application,
disable it for the PDU. In the Conflicts Viewer, for example, set the Enabled
property of the Frame Access node to False.
§ If you need only the Frame Access feature in the executable application,
disable all other conflicting bus simulation features: In the Conflicts Viewer,
set the Enabled property of a conflicting feature to False to disable only

83
May 2024 ConfigurationDesk Conflicts
Conflicts

this bus simulation feature. Alternatively, set the bus configuration's Enabled
property to False to disable all conflicting bus simulation features in one step.
§ If you need all the conflicting features in your executable application, assign
the PDU and its included elements to different bus configurations. Disable all
but one of the conflicting features for this bus configuration. For each of the
other bus configurations, add only one of the conflicting features to the PDU
and/or its included elements.

Feature: Unsupported The PDU Raw Data feature is added to a TX PDU while bus simulation features
combination of PDU Raw are added to ISignals that are included in the TX PDU. For the PDU Raw Data
Data feature and signal feature, the Access mode property is set to Write.
features
When you write raw data to a TX PDU by using the PDU Raw Data feature,
no bus simulation features can be used for the ISignals that are included in the
TX PDU. If bus simulation features are added to the ISignals, these features are
ignored. At run time, only the PDU Raw Data feature applies to the TX PDU,
i.e., raw data is written to the TX PDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

§ If you need neither the conflicting features nor the PDU and its included
ISignals in the executable application, remove the PDU from the bus
configuration. In the Conflicts Viewer, for example, right-click the PDU and
select Show – Show in Bus Configurations Table on the context menu.. In
the bus configuration, delete the selected PDU.
§ If you do not need the PDU Raw Data feature in the executable application,
disable it for the PDU. In the Conflicts Viewer, for example, set the Enabled
property of the PDU Raw Data node to False.
§ If you only want to read the raw data of the TX PDU, set the Access mode
property of the PDU Raw Data feature to Read, for example, in the Conflicts
Viewer.
§ If you only want to write raw data to the TX PDU, disable all conflicting
bus simulation features except the PDU Raw Data feature: In the Conflicts
Viewer, set the Enabled property of a conflicting feature to False to disable
only this bus simulation feature. Alternatively, set the bus configuration's
Enabled property to False to disable all conflicting bus simulation features
in one step.
§ If you want to write raw data to the TX PDU and you need all the conflicting
features in your executable application, assign the PDU and its included
ISignals to different bus configurations. Disable all but one of the conflicting
features for this bus configuration. For each of the other bus configurations,
add only one of the conflicting features to the PDU and/or its included ISignals.

84
ConfigurationDesk Conflicts May 2024
Frame Conflicts

Feature: Unsupported physical The ISignal Offset Value feature is added to an ISignal but the specified
base data type physical base data type of the ISignal is not supported by the feature.

To use the ISignal Offset Value feature, the physical base data type of the
ISignal must be an integer type.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Frame Conflicts

Frame: Exceeding PDUs A conflicting communication matrix element is assigned to a bus configuration.
and/or update bits (bus For an assigned frame, the communication matrix specifies PDU-to-frame
configuration) mappings and due to these mappings, PDUs and/or update bits exceed the
frame boundaries.

The communication matrix must specify PDU-to-frame mappings in such a way

that PDUs and update bits are within the boundaries of the frame.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

85
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

Note

Depending on the PDU-to-frame mappings, this remedy might not

resolve the conflict (e.g., if two mappings specify identical start
positions for their related PDUs).

§ Resolve the conflict by correcting the original communication matrix. Refer

Frame: Exceeding PDUs and/or A communication matrix specifies PDU-to-frame mappings for a frame and due
update bits (communication to these mappings, PDUs and/or update bits exceed the frame boundaries.
matrix)
The communication matrix must specify PDU-to-frame mappings in such a way
that PDUs and update bits are within the boundaries of the frame.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:

86
ConfigurationDesk Conflicts May 2024
Frame Conflicts

Extend the length of the frame and/or reduce the length of the conflicting
PDUs: Specify suitable values for the related Length property, for example, in
the Conflicts Viewer. If required, you can extend the maximum frame length
by enabling CAN FD support. To do so, set CAN FD frame support to True,
for example, in the Conflicts Viewer.
This changes the communication matrix in the active ConfigurationDesk
application and all element instances in all bus configurations of
the application. The originally imported communication matrix remains
unchanged.

Note

Depending on the PDU-to-frame mappings, this remedy might not resolve

the conflict (e.g., if two mappings specify identical start positions for their
related PDUs).

Frame: Invalid byte layout for A conflicting communication matrix element is assigned to a bus configuration.
PDU-to-frame mapping (bus For an assigned frame, the communication matrix specifies at least one of the
configuration) following settings:
§ For a PDU-to-frame mapping of the frame, no or more than one byte layout is
defined.
§ The position of the start bit is unspecified.
§ The endianness is unspecified or invalid.

For each PDU-to-frame mapping of a frame, the communication matrix must

define exactly one byte layout. The start bit position and endianness must be
specified. The start bit position must be ≥ 0. The endianness must be either big
endian or little endian.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

87
May 2024 ConfigurationDesk Conflicts
Conflicts

§ If you need the conflicting element in the executable application, correct the
setting in the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Frame: Invalid byte layout A communication matrix contains a frame with at least one of the following
for PDU-to-frame mapping settings:
(communication matrix) § For a PDU-to-frame mapping of the frame, no or more than one byte layout is
defined.
§ The position of the start bit is unspecified.
§ The endianness is unspecified or invalid.

For each PDU-to-frame mapping of a frame, the communication matrix must

define exactly one byte layout. The start bit position and endianness must be
specified. The start bit position must be ≥ 0. The endianness must be either big
endian or little endian.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Frame: No name defined (bus A conflicting communication matrix element is assigned to a bus configuration.
configuration) For an assigned frame, the communication matrix does not define a name.

For each frame, the communication matrix must define a unique name.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

88
ConfigurationDesk Conflicts May 2024
Frame Conflicts

Depending on the type of the conflicting element, related elements are

Frame: No name defined A communication matrix does not define a name for a frame.
(communication matrix)
For each frame, the communication matrix must define a unique name.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Frame: No payload length A conflicting communication matrix element is assigned to a bus configuration.
defined (bus configuration) For an assigned frame, the communication matrix does not define a payload
length.

For each frame, the communication matrix must define a payload length.

Tip

This rule does not apply to sporadic and event-triggered LIN frames.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

89
May 2024 ConfigurationDesk Conflicts
Conflicts

Depending on the type of the conflicting element, related elements are

removed as well, e.g., all ISignals of a conflicting ISignal IPDU.
§ If you need the conflicting element in the executable application, choose one
of the following alternatives:
§ Resolve the conflict only for the active ConfigurationDesk application:
Specify a valid value for the Length property, for example, in the
Conflicts Viewer. This changes the communication matrix in the active
ConfigurationDesk application and all element instances in all bus
configurations of the application. The originally imported communication
matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer
to:
Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Frame: No payload length A communication matrix does not define a payload length for a frame.
defined (communication
For each frame, the communication matrix must define a payload length.
matrix)
Tip

This rule does not apply to sporadic and event-triggered LIN frames.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify a valid value for the Length property, for example, in the
Conflicts Viewer. This changes the communication matrix in the active
ConfigurationDesk application and all element instances in all bus
configurations of the application. The originally imported communication
matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Frame: Overlapping PDUs A conflicting communication matrix element is assigned to a bus configuration.
and/or update bits (bus For an assigned frame, the communication matrix specifies PDU-to-frame
configuration)

90
ConfigurationDesk Conflicts May 2024
Frame Conflicts

mappings and due to these mappings, PDUs and/or update bits overlap each
other within the frame.

The communication matrix must specify PDU-to-frame mappings in such a way

that PDUs and update bits do not overlap each other within the frame.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Note

Depending on the PDU-to-frame mappings, this remedy might not

resolve the conflict (e.g., if two mappings specify identical start
positions for their related PDUs).

§ Resolve the conflict by correcting the original communication matrix. Refer

Frame: Overlapping PDUs A communication matrix specifies PDU-to-frame mappings for a frame and due
and/or update bits to these mappings, PDUs and/or update bits overlap each other within the
(communication matrix) frame.

The communication matrix must specify PDU-to-frame mappings in such a way

that PDUs and update bits do not overlap each other within the frame.

91
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Reduce the length of the conflicting PDUs: Specify suitable values for the
related Length property, for example, in the Conflicts Viewer.
This changes the communication matrix in the active ConfigurationDesk
application and all element instances in all bus configurations of
the application. The originally imported communication matrix remains
unchanged.

Note

Depending on the PDU-to-frame mappings, this remedy might not resolve

the conflict (e.g., if two mappings specify identical start positions for their
related PDUs).

Function Block Conflicts

Function block: Disabled block The function block references another function block to use one of its features,
provider assigned but the feature is disabled.

Example: The function block references a Multi-Channel PWM Out function

block to use the block's generated trigger signal as a trigger source. However,
the related I/O function trigger generation property is set to Disabled.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Enable the required feature at the referenced function block.
§ Reference a function block where the required feature is set to enabled.

92
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Function block: Duplicate The value specified at the Camshaft angles property is invalid, because at least
angle values and/or supported one of the following cases occurs:
angle range exceeded § Duplicate angle values are specified.
§ The covered angle range exceeds the angle range of the assigned master APU
provider.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify values for the
Camshaft angle property that are unique and match the angle range of the
assigned master APU provider.

Function block: Duplicate One or more properties (Initial value, Stop value, Initial substitute value) of
angle values and/or supported the related function port contain invalid values caused by the following:
angle range exceeded § One or more of the properties contain duplicate angle values.
§ The covered angle range of one or more properties exceeds the angle range of
the assigned Engine Control Setup function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify values at the affected
properties of the related function port that are unique and match the angle
range of the assigned master APU provider.

Function block: Duplicate CAN The active ConfigurationDesk application contains two or more CAN function
channel name blocks that specify identical CAN channel names.

CAN channel names must be unique.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify unique names for the
Channel name properties of the CAN function blocks.

93
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Duplicate Two or more ECU Interface Configuration function blocks are available in the
ECU interface container code active ConfigurationDesk application. ECU interface container (EIC) files with
prefix identical code prefixes are imported to these function blocks.

The code prefix of an ECU interface container must be unique within the active
ConfigurationDesk application, i.e.:
§ Each ECU interface container must be available in the application only once.
§ If several ECU interface containers are available in the application, their code
prefixes must differ.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Import different ECU interface containers to the ECU Interface
Configuration function blocks. For instructions, refer to How to Import ECU
Interface Container (EIC) Files (ConfigurationDesk Real-Time Implementation
Guide ).
§ For the affected ECU interface containers, correct the duplicate settings via the
dSPACE ECU Interface Manager. Export new EIC files and update the affected
ECU Interface Configuration function blocks with these EIC files. For more
information on updating EIC files, refer to Basics on Updating ECU Interface
Containers in ConfigurationDesk Applications (ConfigurationDesk Real-Time
Implementation Guide ).
§ In the ConfigurationDesk application, delete all ECU Interface Configuration
function blocks except for one.

Function block: Duplicate Two or more ECU Interface Configuration function blocks are available in the
ECU interface container active ConfigurationDesk application. ECU interface container (EIC) files with
identification identical container identifications are imported to these function blocks.

The container identification of an ECU interface container must be unique within

the active ConfigurationDesk application, i.e.:
§ Each ECU interface container must be available in the application only once.
§ If several ECU interface containers are available in the application, their
container identifications must differ.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

94
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Remedy Choose one of the following alternatives:

Function block: Duplicate IP The local IP addresses of at least one virtual Ethernet controller is not unique.
address
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts viewer, for example, specify unique local IP

addresses for the virtual Ethernet controllers.

Function block: Duplicate LIN The active ConfigurationDesk application contains two or more LIN function
channel name blocks that specify identical LIN channel names.

LIN channel names must be unique.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify unique names for the
Channel name properties of the LIN function blocks.

Function block: Duplicate At least one of the following cases occurs:

MAC address § The custom MAC address of the virtual Ethernet controller is the same as the
MAC address of the referenced physical Ethernet controller.
§ Two or more virtual Ethernet controllers use the same custom MAC address
and reference the same physical Ethernet controller.

95
May 2024 ConfigurationDesk Conflicts
Conflicts

If you use a MicroAutoBox III, it is recommended to specify different custom

MAC addresses for Virtual Ethernet Setup function blocks that reference the
same physical Ethernet controller.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy In the Conflicts viewer, for example, specify a different custom MAC
address.

Function block: Duplicate The active ConfigurationDesk application contains two or more function blocks
name with the same name.

Function block names must be unique.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, enter unique names in the
Name edit field for all function blocks.

Function block: Duplicate The local IP address of two or more Ethernet setup function blocks (Ethernet
network address per physical Setup, Virtual Ethernet Setup, or Data Streaming Ethernet Setup function
Ethernet adapter blocks) have the same subnetwork address and use the same physical Ethernet
controller.

To prevent unintended behavior, it is recommended that two Ethernet setup

function blocks should not reference the same physical Ethernet controller if their
local IP addresses have the same subnetwork address.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy In the Conflicts viewer, for example, specify a local IP address that
is a member of a different subnetwork. The subnet mask/subnet prefix length
indicates how many most significant bits of the local IP address are used to
specify the subnetwork address.

96
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Function block: Duplicate or Using a function block that is assigned to an Ethernet setup function block
invalid local port number of (Ethernet Setup, Virtual Ethernet Setup, or Data Streaming Ethernet Setup
assigned Ethernet clients function block), the conflict occurs in the following cases:
§ Case 1: At least two function blocks are assigned to the same Ethernet setup
function block and use a local port with the same port number, but they differ
neither in the used transport protocol nor in the data flow direction.
To use the same port number, you must use different transport protocols or
different data flow directions. For example, the TCP, UDP Transmit and UDP
Receive function blocks can use the same local port number, because they
differ in the used transport protocol or in the data flow direction.
§ Case 2: The function block is set to the default local port. The default local
port is a placeholder with no valid port number.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives depending on the case

that causes the conflict:
§ Case 1: Choose one of the following alternatives:
§ In the Conflicts Viewer, for example, set the local port number of an
affected function block to an unused port in the range 1 ... 65535.
§ In the Properties Browser, for example, assign the function blocks to
different Ethernet setup function blocks.
§ Case 2: In the Conflicts Viewer, for example, specify a local port number in
the range 1 ... 65535.

Function block: Duplicate Multiple UDP Data Replay function blocks filter out the same recorded Ethernet
recorded data destination frames to process them.
IP endpoint per physical
UDP Data Replay function blocks use the destination socket of recorded
Ethernet adapter
Ethernet frames to filter out the data to be processed. A socket is the
combination of the IP address, the transport protocol, and the port. Sockets
differ from each other if at least one parameter, such as the IP address, is
different.

UDP Data Replay function blocks that are assigned to the same physical
Ethernet adapter must not access recorded Ethernet frames with the same
destination socket.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

97
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy In the Conflicts Viewer, for example, make sure that each UDP
Data Replay function block accesses recorded Ethernet frames with different
destination sockets.

Function block: Duplicate The function block is referenced by two or more ECU Interface Configuration
settings of assigned ECU function blocks that have identical settings for the accessors grouped by
Interfaces <functional position>.

The settings for the accessors grouped by <functional position> must be

different for ECU Interface Configuration function blocks that reference the
same Ethernet Setup function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, reassign the reference between the
conflicting function block and the related ECU Interface Configuration
function blocks so that each ECU Interface Configuration function block
references a separate Ethernet Setup function block.
§ Delete one of the related ECU Interface Configuration function blocks from
the ConfigurationDesk application.
Correct the duplicate settings via the dSPACE ECU Interface Manager. Export
a new EIC file and import this file to a new ECU Interface Configuration
function block. Then assign the required Ethernet Setup function block to it.

Function block: Duplicate VLANs with the same VLAN ID are specified for the Ethernet switch.
VLAN ID
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify VLANs with different
VLAN IDs for the Ethernet switch.

Function block: Exceeding The values specified at the Measurement interval and/or the Recursion factor
measurement interval properties exceed the maximum allowed value.

Both the values specified at the Measurement interval and the Recursion
factor must be smaller than or equal to twice the number of teeth of the
crankshaft wheel specified in the imported wavetable file.

98
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify values for the
Measurement interval and/or the Recursion factor properties that match the
maximum allowed value.

Function block: Exclusive At least one Ethernet client requests access to a physical Ethernet controller
access requested that is exclusively reserved for a communication controller of a bus simulation
container (BSC).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Except for the controller group with exclusive access, remove
all other referencing configurations of Ethernet clients. The Ethernet Setup
function block can be referenced by other function blocks via their referencing
configurations or by other communication controllers via the Configuration
function port.

Function block: Interfering The Reboot board and Termination of application options of the Response
reaction activation activator property are both selected.
(application termination vs.
The system supports only one of these options at a time.
board restart)
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – – – –

Remedy In the Conflicts Viewer, for example, clear either the Reboot
board setting or the Termination of application setting.

Function block: Invalid One or more properties (Initial value, Stop value, or Initial substitute value)
assigned cylinder of the related function port contain a value that exceeds the value of the
Number of cylinders property of the assigned Engine Control Setup function
block.

99
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a value for the related
properties that does not exceed the value of the Number of cylinders property
of the assigned Engine Control Setup function block.

Function block: Invalid baud The specified value for the Baud rate property exceeds the value range of the
rate selected transceiver type and/or the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a Baud rate that matches
the value range of the selected transceiver type and the assigned hardware
resource.
If the function block is mapped to a Configuration Port block that is created
for an RTICANMM ControllerSetup block, you cannot specify the baud
rate in the Conflicts Viewer. In this case, adjust the baud rate in the
related Simulink model and analyze the model, including task information,
in ConfigurationDesk.
§ In the Properties Browser, select a Transceiver type and/or assign a
hardware resource that supports the specified baud rate.

Function block: Invalid baud The specified value for the Baud rate property exceeds the value range of the
rate assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a Baud rate that matches the
value range of the assigned hardware resource.
§ In the Properties Browser, assign a hardware resource that supports the
specified baud rate.

100
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Function block: Invalid The Lambda Pump and Lambda Nernst channel requests are assigned to
channel pair channels with a different channel number.

Both channel requests must be assigned to channels with the same channel
number.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reassign the related channels
to make the channel numbers match.

Function block: Invalid At least one value, that is specified in the Challenge response pair list is invalid.
channel response
The following rules apply:
configuration
§ In the pair list, all values for the challenges must be different. Double values
are not allowed.
§ In the pair list, all values for the responses must be different. Double values are
not allowed.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – – – –

Remedy In the Conflicts Viewer, for example, specify challenge and/or

response values that fulfill the rules above.

Function block: Invalid chip One or more Chip Select signal ports are not available to address an SPI slave for
select configuration data transmission.

The number of provided Chip Select signal ports is specified by the Number of
chip selects property.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, choose one of the following
alternatives:
§ Increase the number of chip select signals via the Number of chip selects
property.

101
May 2024 ConfigurationDesk Conflicts
Conflicts

§ Select Chip Select signals ports according to the specified number of chip
select signals via the Chip select configuration property.

Function block: Invalid clock The specified value for the Clock pause property is outside the valid range. The
pause range valid range is:

Clock pause = 1.5 / [Clock frequency] s ... 1.0 s

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a clock pause that
matches the valid range and the value required to match the configuration of the
connected encoder. Refer to the data sheet of the encoder.

Function block: Invalid The specified counter settings are not plausible. One of the following
counter range requirements are not fulfilled:
§ The specified values for counter start, end, and increment must be inside the
value range of the counter.
The value range of the counter is defined by the counter width in the
imported application-specific protocol.
§ The direction of counting must match the start and end values of the counter.
If the counter increments, the counter start value must be less than or equals
the end value. If the counter decrement, the start value must be greater than
or equals the end value.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Counter start, Counter end,
and Counter increment properties according to the requirements described
above.
§ In the application-specific protocol, increase the counter width and import the
protocol file again.

Function block: Invalid CRC The Serial message mode property setting is not compatible with the CRC
calculation mode calculation property setting.

102
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

The Enhanced Serial Message (4Bit ID, 16Bit Data) and Enhanced Serial
Message (8Bit ID, 12Bit Data) modes do not support Automatic (Legacy
Mode) CRC calculation mode.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives to make the properties

match:
§ In the Conflicts Viewer, change the CRC calculation property to Custom or
Automatic.
§ Change the Serial message mode property to Short Serial message or to
Disabled.

Function block: Invalid CRC The specified value for the at least one of the following properties is outside the
ranges valid range: CRC sum bit width, CRC sum start bit position, CRC-checked
data bit width, and CRC-checked data start bit position.
§ Valid range for CRC sum bit width: 1 ... [Transmission length]
§ Valid range for CRC sum start bit position: 1 ... 1 + [Transmission length] -
[CRC sum bit width]
§ Valid range for CRC-checked data bit width: 1 ... [Transmission length] -
[CRC sum bit width] bits
§ Valid range for CRC-checked data start bit position: 1 ... 1 + [Transmission
length] - [CRC-checked data bit width]

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify values for the affected properties
that match the valid ranges and the value required to match the configuration
of the connected encoder. Refer to the data sheet of the encoder.
§ In the Conflicts Viewer, for example, set the CRC configuration property to
Disabled.
§ In the Conflicts Viewer, for example, increase the value of the CRC sum bit
width property with respect to the value required to match the configuration
of the connected encoder. Refer to the data sheet of the encoder.

Function block: Invalid CRC The specified value for the CRC polynomial property and/or the CRC initial
values value property is outside the valid range.

103
May 2024 ConfigurationDesk Conflicts
Conflicts

§ Valid range for the CRC polynomial property: 2[CRC sum bit width] + 1 ...
2[CRC sum bit width] + 1 - 1
§ Valid range for the CRC initial value property: 0 ... 2[CRC sum bit width] - 1

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

Function block: Invalid custom The specified Custom idle value exceeds the upper limit of the wavetable value.
idle value
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reduce the specified value for
the Custom idle value property with respect to the upper limit, displayed by the
Number of values property.

Function block: Invalid The value specified for the Cylinder property or at least one value specified
cylinder for the Cylinder map property exceeds the number of cylinders defined in the
Engine Simulation Setup function block (Number of cylinders property) that
is referenced by this function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reduce the specified value
for the Cylinder or the Cylinder map property with respect to the number of
cylinders specified in the assigned Engine Simulation Setup function block.

104
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Function block: Invalid data The specified value for the Data phase baud rate property exceeds the value
phase baud rate range of the selected transceiver type and/or the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a Data phase baud rate that
matches the value range of the selected transceiver type and the assigned
hardware rescource.
If the function block is mapped to a Configuration Port block that is created
for an RTICANMM ControllerSetup block, you cannot specify the baud
rate in the Conflicts Viewer. In this case, adjust the baud rate in the
related Simulink model and analyze the model, including task information,
in ConfigurationDesk.
§ In the Properties Browser, select a Transceiver type and/or assign a
hardware resource that supports the specified data phase baud rate.

Function block: Invalid The default destination port number is a placeholder and no valid port number.
destination port number
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a destination port

number in the range 1 ... 65535.

Function block: Invalid digital A digital filter that is assigned to a function block is missing in the imported
filter digital filters list, for example, because it has been removed after the assignment.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ From the Conflicts Viewer, for example, reimport the digital filter via the
Imported Digital Filters property.

105
May 2024 ConfigurationDesk Conflicts
Conflicts

§ In the Conflicts Viewer, for example, assign a digital filter which already has
been imported to the electrical interface of the function block via Assigned
digital filter property.

Function block: Invalid The specified value of the Time chip select inactive property exceeds the
duration of inactive signal maximum value supported by the assigned hardware resource.
state
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, decrease the duration to a

value that is supported by the assigned hardware resource.

Function block: Invalid At least one of the following cases occurs:

encoder distance § The specified value of the Encoder minimum position position is greater
configuration than or equals the specified value of the Encoder maximum position
property.
The value of the Encoder minimum position must be less than the value of
the Encoder maximum position property.
§ The specified value of the Index position property is out of range for valid
encoder positions.
The Encoder minimum position and the Encoder maximum position
properties define the range for valid encoder positions.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify valid values for
the Encoder minimum position, Encoder maximum position, and the
Index position properties. Use the error description above to decide on the
appropriate settings.

Function block: Invalid engine The Initial value property of the Engine Direction function port is set to
direction value Reverse but the reverse crank mode is disabled.

The Reverse setting for the initial value is supported only if the Reverse Crank
property is set to Enabled.

106
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, select Undefined or Forward at the
Initial value property of the function port.
§ If the assigned hardware resource supports reverse rotation, set the Reverse
Crank property to Enabled in the Properties Browser.

Function block: Invalid You enabled MACsec, but the assigned Ethernet adapter does not support it.
Ethernet adapter assigned
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Disable MACsec.
§ Assign a hardware resource that supports MACsec. For instructions, refer
to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

Function block: Invalid event The value specified for the Event downsampling property is higher than the
down-sampling value specified for the Maximum message count property.

The event downsampling value must be equal or lower than the maximum
message count value.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reduce the value for the
Event downsampling property.

Function block: Invalid event The value of one or more Period angle properties does not match the angle
period angle range of the assigned master APU provider.

107
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify values for the Period
angle properties that match the angle range of the assigned master APU
provider.

Function block: Invalid event This conflict is generated in the following cases:
window(s) § The specified value for the Window end angle is greater than the value for
the Window start angle.
§ The difference between the Window start angle and the Windows end
angle exceeds 720°.
§ The Number of event windows is set to 2 and:
§ The angle range covered by both event windows exceeds 720°.
or
§ The specified values for Window start angle and Window end angle
cause the event windows to overlap.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, specify valid values for the Windows start
angle property and/or Windows end angle property. Use the error description
in the Value column to decide on the appropriate settings.

Function block: Invalid At least one of the following cases occurs:

feature configuration § The assigned Ethernet controller does not provide the settings specified for
Address resolution method.
§ The assigned Ethernet controller does not provide the settings for the
suppression of Internet group management protocol (IGMP) messages.
§ A default gateway for an IPv6 network is enabled.
Default gateways are supported only for IPv4 networks.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

108
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Remedy Choose one of the following alternatives in the Conflicts Viewer,

for example:
§ Set the Optimization and/or Address resolution method properties to
settings that match the features of the assigned Ethernet adapter.
§ Set the Internet protocol property to a version that matches the specified
features.
§ Set the IGMP suppression property to a setting that matches the requested
settings.
§ Disable the default gateway.

Function block: Invalid flag The specified position value for the at least one of the following properties is
positions outside the valid range: Error flag position, Inverted error flag position,
Warning flag position, and Inverted warning flag position.

Valid range for all listed properties: 0 ... [Transmission length]

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a position value for
the affected properties that match the valid range and the value required to
match the configuration of the connected encoder. Refer to the data sheet of
the encoder.

Function block: Invalid index The assigned hardware resource does not provide enough channels to measure
channel usage the index signal of the connected encoder. At least three channels in one
channel set are required for this use case.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Index channel use property to
Disabled.
§ Assign a hardware resource that provides at least three channels in
one channel set to support the index channel usage. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

Function block: Invalid The specified setting for the Interface type property is not supported by the
interface type assigned hardware resource.

109
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, select a setting for the Interface type
property that is supported by the assigned hardware resource.
§ Assign a hardware resource that supports the required interface type. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Invalid The specified setting for the Interface type property is not supported by the
interface type assigned hardware resource.

The assigned hardware resource does not provide the required number of
channels.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, select a setting for the Interface
type property that is supported in combination with the assigned hardware
resource.
§ Assign a hardware resource that supports the number of channels required
for the selected Interface type. For instructions, refer to How To Assign
Hardware Resources via Function Block Properties (ConfigurationDesk Real-
Time Implementation Guide ).

Function block: Invalid IP The specified IP address is not supported. The conflict occurs in the following
address cases:
§ Case 1: The function block uses the default IP address. The default IP address
is a placeholder and no valid IP address for network communication.
§ Case 2: The function block uses one of the following IP addresses as the local
IP address:
§ Multicast address (IPv4: 224.0.0.0 ... 239.255.255.255, IPv6: ff00::/8)
§ Loopback address (IPv4: 127.0.0.0 ... 127.255.255.255, IPv6: ::1)
§ IPv4: IP address with 0 or 240 ... 255 as the first octet (0.0.0.0 ...
0.255.255.255 or 240.0.0.0 ... 255.255.255.255)
§ IPv6: Link-local address (fe80::/10)

110
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Specify a supported IP address. The following IP address ranges are

recommended.
§ IPv4: 10.0.0.1 ... 10.255.255.254, 172.16.0.1 ... 172.31.255.254, and
192.168.0.1 ... 192.168.255.254
§ IPv6: fc00::1 ... fdff:ffff:ffff:ffff:ffff:ffff:ffff:ffff (fc00::/7)

Function block: Invalid low The specified setting for the Low-power mode property is not supported by the
power mode selected transceiver type.

Only the ISO 11898-2 High-Speed CAN and the ISO 11898-3 Fault‑Tolerant
CAN transceiver types support the low-power mode.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Low power mode property to
Disabled.
§ In the Conflicts Viewer, for example, select a Transceiver type that supports
the low power mode.

Function block: Invalid MAC The specified MAC address is no valid MAC address for an Ethernet controller.
address The conflict occurs in the following cases:
§ The function block uses the default MAC address. The default MAC address is
a placeholder and no valid MAC address for an Ethernet controller.
§ The specified MAC address is a multicast or broadcast address. A valid MAC
address of an Ethernet controller must be a unicast address.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy In the Conflicts viewer, for example, specify a unicast MAC address
that differs from the default MAC address. For more information on the types
of MAC addresses, refer to Configuring the Basic Functionality (Virtual Ethernet
Setup) (ConfigurationDesk I/O Function Implementation Guide ).

111
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Invalid master A custom function block (such as the FPGA custom function block), is assigned
APU provider assigned to a master APU provider on the same hardware resource to which the function
block is assigned to.

A master APU provider cannot be connected and used from a slave APU that is
located on the same board, for example, the same DS2655 FPGA Base Board.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, assign a master APU provider
from a different hardware resource to the slave APU request.

Function block: Invalid The assigned hardware resource does not support the specified maximum vector
maximum trigger angle vector size for trigger angles. The hardware resource supports 8 trigger angles for the
size 360° angle range.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify the maximum vector size for
trigger angles to 8 or less.
§ Assign a hardware resource to the function block that supports the specified
vector size for trigger angles. For instructions, refer to How To Assign
Hardware Resources via Function Block Properties (ConfigurationDesk Real-
Time Implementation Guide ).

Function block: Invalid The value specified for the Maximum vector size at the function block is
maximum vector size outside the possible value range.

The value range depends on the assigned hardware.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a value from inside the
range for the Maximum vector size property.

112
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Function block: Invalid model A function port for which Model access is set to Disabled is mapped to a model
connection for unmappable port.
port
ConfigurationDesk does not support mappings of this type.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ In a working view, remove the invalid mapping.
§ In the Properties Browser, for example, set the Model access property of the
involved function port to Enabled.

Function block: Invalid The specified value for the Multiturn bit width property and/or the Multiturn
multiturn resolution range start bit position property is outside the valid range.
§ Valid range for the Multiturn bit width property: 0 ... [Transmission length]
§ Valid range for the Multiturn start bit position property: 1 ... 1 +
[Transmission length] - [Multiturn bit width]

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify values for the affected
properties that match the valid ranges and the value required to match the
configuration of the connected encoder. Refer to the data sheet of the encoder.

Function block: Invalid The specified value of the Number of bits per word property exceeds the
number of bits per word maximum number supported by the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, decrease the number of bits
per word to a value that is supported by the assigned hardware resource.

113
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Invalid The setting of the Number of edges property exceeds the maximum value
number of edges supported by the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, decrease the Number of

edges property.

Function block: Invalid Several Engine Simulation Setup function blocks reference the same Angular
number of referencing engine Clock Setup function block.
setups
Only a single referencing Engine Simulation Setup block is allowed.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, configure the Assigned

master APU provider property so that only a single Engine Simulation Setup
function block references the affected Angular Clock Setup function block.

Function block: Invalid The specified value for the Number of steps property is outside the valid range.
number of steps
Valid settings are:
§ 0: The number of steps is derived from the value specified at the Single-turn
bit width property.
§ 2[Single-turn bit width]/(222- 1) ... 2[Single-turn bit width]

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a value with respect to
the valid range and the value required to match the value stored in the encoders
memory. Refer to the data sheet of the encoder.
If the specified values for the Single-turn bit width and the Number of
steps properties match to the data sheet of the encoder and the conflict still
is displayed, the function block does not support this encoder type.

114
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Function block: Invalid The specified value of the Number of cycles property exceeds the maximum
number of SPI cycles number supported by the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, decrease the number of SPI
cycles to a value that is supported by the assigned hardware resource.

Function block: Invalid The specified value of the Number of words property exceeds the maximum
number of words number of words per SPI cycle supported by the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, decrease the number of

words to a value that is supported by the assigned hardware resource.

Function block: Invalid The set optimization mode is not supported by the assigned Ethernet controller.
optimization
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Optimization property to a
supported optimization mode.
§ In the Properties Browser, for example, assign a different Ethernet controller
to the function block.

Function block: Invalid phase The value specified at the Minimum phase shift angle property is equal to or
shift angle values greater than the value specified at the Maximum phase shift angle property.

115
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a value at the

Minimum phase shift angle property that is smaller than the value of the
Maximum phase shift angle property.

Function block: Invalid phase At least one of the following cases occurs:
shift setting § The alignment of the PWM signals is set to edge aligned.
§ The assigned hardware resource does not support phase shifting. For
information on hardware resources supporting phase shifting, refer to
Hardware Dependencies (Multi-Channel PWM Out) (ConfigurationDesk I/O
Function Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives in the Conflicts Viewer,

for example:
§ Set the Signal alignment property to Center-aligned.
§ Set the Phase shifts property to Disabled.

Function block: Invalid port The value specified for one or more of the Initial value, Stop value or Initial
settings substitute value properties exceeds the saturation range (system saturation
values or user-configured saturation values) of the function port.

For basics on using initial and stop values, refer to Specifying Initialization and
Stop Behavior (ConfigurationDesk I/O Function Implementation Guide ).

For further details on using substitute values, refer to Configuring

Test Automation Support (ConfigurationDesk I/O Function Implementation
Guide ).

For basics on user saturation, refer to Specifying User Saturation

(ConfigurationDesk I/O Function Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

116
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Initial value,
Stop value or Initial substitute value property within the possible value
range.
§ If you have specified your own min/max. values for the saturation range,
reduce the Saturation minimum value or increase the Saturation
maximum value.

Function block: Invalid port The settings of at least one property of the Active Wavetable function port (for
settings (active wavetable) example, Initial value or Stop value) exceeds the number of wavetable files
imported to the function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a value for the related
properties that matches the value range of the Imported wavetable files
property.

Function block: Invalid port The value for the Baud Rate function port exceeds the value range of the
settings (Baud Rate) selected transceiver type and/or the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a Baud rate that matches
the value range of the selected transceiver type and the assigned hardware
resource.
§ In the Properties Browser, select a Transceiver type and/or assign a
hardware resource that supports the specified baud rate. For instructions on
assigning hardware resources, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).

Function block: Invalid port The settings of at least one property of the Encoder Speed function port or the
settings (Encoder Speed / Encoder Position function port (for example, Initial value or Stop value), is
Encoder Position) outside the possible value range.

117
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, change the specified value for
the related properties with respect to the possible value range.

Function block: Invalid The values specified for one or more of the Initial value or Initial substitute
port settings (Position value properties of the related function port are out of range for valid encoder
(Linear)/Update Position positions.
(Linear))
The Encoder minimum position and the Encoder maximum position
properties define the range for valid encoder positions.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Initial value or
Initial substitute value property within the possible value range.
§ In the Properties Browser, adapt the range for valid encoder positions
with the Encoder minimum position and the Encoder maximum position
properties.

Function block: Invalid The specified value for at least one property that defines a particular protocol
protocol settings setting conflicts with the setting of another property. At least one of the
following cases occurs:
§ A section in the protocol overlaps another section.
The protocol contains the following sections that must not overlap:
Multiturn section bit range, Single-turn section bit range, Sensor-
specific diagnostic section bit range, and CRC sum section bit range.
Each section covers the following bit range: [Start Bit Position] ... [Start Bit
Position] + [Bit Width] - 1.
§ The position of a flag collides with the position of another flag or with one of
the above listed sections.
The following positions must not collide with each other and with the above
listed sections: Error flag bit position, Inverted error flag bit position,
Warning flag bit position, and Inverted warning flag bit position.
§ The Multiturn section bit range does not precede the Single-turn section
bit range.
If the Code type property is set to Grey code, the multiturn data must
precede the single-turn data. Therefore, the value for the Single-turn start

118
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

bit position must be higher than the value for the Multiturn start bit
position.
§ The CRC-checked data does not precede the CRC checksum.
The CRC-checked data always must precede the CRC checksum. Therefore,
the value for the CRC sum start bit position must be higher than the value
for the CRC-checked data start bit position.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Function block: Invalid rated The function block sets the trigger level of the electronic fuse to an unsupported
current level.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Set the trigger level of the electronic fuse to a higher level via the Rated
current (factor) property.
§ Disable the control of the electronic fuse via the Configurable fuse property.

Function block: Invalid The Configuration port of a FlexRay function block is mapped to a
resource provider assigned Configuration Port block that was created for a FLEXRAYCONFIG UPDATE
block of a Simulink model. One or more channel sets are assigned to the
FlexRay function block that do not meet the requirements provided by the
Configuration Port block.

The FLEXRAYCONFIG UPDATE block provides requirements regarding the

simulation platform (i.e., SCALEXIO or MicroAutoBox III) and the channel type.
All channel sets that are assigned to a FlexRay function block must meet these
requirements.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

119
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, assign channel sets to the FlexRay
function block that meet the requirements.
§ Map the Configuration Port block to another FlexRay function block.
§ Change the hardware requirements for the FLEXRAYCONFIG UPDATE block
by specifying a different hardware configuration in the FlexRay Configuration
Tool.

Function block: Invalid rotary The specified value for the Rotary resolution property exceeds the maximum
resolution value of the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Specify a resolution that matches the value range of the assigned hardware
resource.
§ Assign a hardware resource that supports the specified resolution. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Invalid sample The Sample trigger source property is set to Time (sequence-aligned),
trigger configuration Trigger function, or to Angle and at least one of the following cases occurs:
§ The Digital filter property is set to Enabled.
§ The Trigger shift property is not set to 0. This means trigger shifting is
enabled.
§ The Sequence trigger source property is set to Threshold or Digital
Threshold.

Only the Time (free-running) sample trigger source supports digital filtering
and the trigger shift functionality.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify valid values for the
Sample trigger source, Sequence trigger source, Digital filter and the
Trigger shift properties. Use the error description above to decide on the
appropriate settings.

120
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Function block: Invalid The specified value for the Saturation minimum value property exceeds the
saturation range value for the Saturation maximum value property.

For basics on user saturation, refer to Specifying User Saturation

(ConfigurationDesk I/O Function Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reduce the Saturation

minimum value or increase the Saturation maximum value.

Function block: Invalid sensor- The specified value for the Sensor-specific diagnostic bit width property
specific diagnostic range and/or the Sensor-specific diagnostic start bit position property is outside
the valid range.
§ Valid range for the Sensor-specific diagnostic bit width property: 0 ...
[Transmission length]
§ Valid range for the Sensor-specific diagnostic start bit position property:
1 ... 1 + [Transmission length] - [Sensor-specific diagnostic bit width]

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Function block: Invalid The Sequence trigger source property is set to Sequence end and the
sequence length of 0 for Sequence length property is set to 0 (= infinite number of samples). In this
sequence trigger source = case, the function block ignores the zero value and internally uses the specified
'Sequence end' value of the Maximum sequence length property instead.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

121
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Sequence
trigger source property that supports sequence capture with an infinite
sequence length, for example, Model task or Threshold.
§ In the Conflicts Viewer, for example, specify a nonzero value for the
Sequence length property (= infinite number of samples).

Function block: The function block receives broadcast messages although the reception of
Invalid settings for broadcast messages is disabled.
multicast/broadcast
If you enable the reception of multicast messages, the reception of broadcast
messages is automatically enabled.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy In the Conflicts Viewer, for example, choose one of the following
alternatives:
§ Set the Receive from broadcast address property to Enabled.
To make sure that only unicast and multicast messages are taken into account,
filter out potential broadcast messages in the behavior model, for example, by
reading only messages with known source IP addresses and ports.
§ If you do not need to receive multicast messages, set the Receive from
multicast address property to Disabled.

Function block: Invalid signal The value specified for the Signal amplitude property is outside the valid range.
amplitude
The maximum value depends on the setting of the Measurement range
property (High or Low), the value specified for the Signal offset property, and
the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose at least one of the following alternatives:

§ In the Conflicts Viewer, for example, reduce the specified value for the
Signal amplitude property with respect to the specified measurement range,
the specified signal amplitude, the assigned hardware resource, and the value
required to match the signal amplitude of the connected encoder. Refer to the
data sheet of the encoder.
§ In the Conflicts Viewer, for example, change the setting of the
Measurement range property from Low to High.

122
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

§ In the Conflicts Viewer, for example, specify a value for the Signal offset
property that matches the specified signal amplitude.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

Function block: Invalid signal The distance between an angle position for the rising and/or falling edge of the
edge positions signals is too small. The distance between edge positions must be at least 1°.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify angle positions at the
Signal edge position vector property that respect the minimum distance of at
least 1° between edge positions. You have to consider both rising and falling
edges.

Function block: Invalid signal The value specified for the Signal offset property is outside the valid range.
offset
The valid value range depends on the setting of the Measurement range
property (High or Low), the value specified for the Signal amplitude property,
and the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose at least one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Signal offset
property with respect to the specified measurement range, the specified signal
amplitude, the assigned hardware resource, and the value required to match
the signal offset of the connected encoder. Refer to the data sheet of the
encoder.
§ In the Conflicts Viewer, for example, change the setting of the
Measurement range property.
§ In the Conflicts Viewer, for example, specify a value for the Signal
amplitude property that matches the specified signal offset.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

123
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Invalid The value specified for the Sine/Cosine voltage property is outside the valid
Sine/Cosine voltage range.

The maximum value depends on the setting of the Measurement range

property (High or Low), and the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose at least one of the following alternatives:

§ In the Conflicts Viewer, for example, reduce the specified value for the
Sine/Cosine voltage property with respect to the specified measurement
range, the assigned hardware resource, and the expected RMS input voltage
that is induced at the sine and cosine coils of the connected resolver. Refer to
the data sheet of the resolver.
§ In the Conflicts Viewer, for example, change the setting of the
Measurement range property from Low to High.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

Function block: Invalid single- The specified value for the Single-turn bit width property and/or the Single-
turn resolution range turn start bit position property is outside the valid range.
§ Valid range for the Single-turn bit width property: 0 ... [Transmission
length]
§ Valid range for the Single-turn start bit position property: 1 ... 1 +
[Transmission length] - [Single-turn bit width]

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Function block: Invalid size of The product of the Sequence length and Maximum sequence length
the capture values and/or the property settings exceeds 655350. The product must be equal to or less than
timestamps (size exceeds the 655350.
recommended maximum)

124
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reduce the values for the
Sequence length property and/or the Maximum sequence length property.

Function block: Invalid The setting of the Termination property does not match the selected transceiver
termination type and/or the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, change the setting of the Termination
property to match the selected transceiver type and assigned hardware
resource.
§ In the Properties Browser, select a Transceiver type and/or assign a
hardware resource that supports the specified termination.

Function block: Invalid The value specified at the Lower threshold property is equal to or greater than
threshold values the value specified at the Upper threshold property.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a value at the Lower
threshold property that is smaller than the value of the Upper threshold
property.

Function block: Invalid time The specified value of the Time after transfer property exceeds the maximum
after transfer value supported by the assigned hardware resource.

125
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, decrease the time to a value
that is supported by the assigned hardware resource.

Function block: Invalid time The specified value of the Time before transfer property exceeds the maximum
before transfer value supported by the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, decrease the time to a value
that is supported by the assigned hardware resource.

Function block: Invalid time The specified value of the Time between words property exceeds the maximum
between words value supported by the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, decrease the time to a value
that is supported by the assigned hardware resource.

Function block: Invalid time The assigned hardware resource does not provide a local time source.
source
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Time Source property to
Global.

126
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

§ Assign a hardware resource that provides a local time source. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

Function block: Invalid time A value specified at the Time Vector function port is not supported by the
vector entry assigned hardware resource.

The value range for specific properties at the Time Vector function port, for
example, the Saturation minimum value property (if user saturation is used),
changes depending on the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the affected property
that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

Function block: Invalid The specified time domain does not match the requirements of the selected PTP
time synchronization domain type. The IEEE 802.AS protocol supports only a single time domain with the
number number 0.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, set the time domain number
of the affected function block to 0.

Function block: Invalid The specified timeout value is shorter than the synchronization pulse of the SENT
timeout value messages or too long to be measured.

127
May 2024 ConfigurationDesk Conflicts
Conflicts

The value range is calculated as follows:

§ The minimum value depends on the assigned real-time hardware:
§ SCALEXIO:
Tmin = Sync pulse length · (1 - Tick period tolerance/100)
§ MicroAutoBox III:
Tmin = Sync pulse length · (1 + Tick period tolerance/100)
§ MicroLabBox II:
Tmin = Sync pulse length · (1 + Tick period tolerance/100)
Sync pulse length = (Low pulse ticks + Synchronization pulse high ticks) ·
Nominal tick period
§ Tmax = 32767 · Nominal tick period · (1 - Tick period tolerance/100)
The absolute maximum value depends on the assigned real-time hardware.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, set the Timeout,

Synchronization pulse high ticks, Low pulse ticks, Nominal tick period, and
Tick period tolerance properties according to the requirements on the timeout
value range described above.

Function block: Invalid The value specified for the Timeout limit property is equal or greater than the
timeout limit (compared to value specified for the Challenge period property.
challenge period)
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – – – –

Remedy In the Conflicts Viewer, for example, specify a value for the
Timeout limit property that is less than the value specified for the Challenge
period property.

Function block: Invalid tooth The value specified at the Tooth period ratio property exceeds the value range
period ratio of the property.

The value range depends on the crankshaft wheel and is specified in the
imported wavetable file.

128
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a value for the Tooth
period ratio property that matches the value range specified in the imported
wavetable file.

Function block: Invalid traffic The sum of the reserved bandwidths of traffic class A and traffic class B exceeds
shaping configuration the maximum data rate of the Ethernet switch port. The sum of the reserved
bandwidths must not exceed 1 Gbit/s.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, decrease the reserved

bandwidths for the traffic classes.

Function block: Invalid trigger A property value specified at the Trigger Angle Vector Size function port
angle vector size (for example, Initial value) exceeds the Maximum trigger angle vector size
specified at the function block.

The Maximum trigger angle vector size is used only when the Function
trigger property is set to Angle based at the function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, change the specified value for
the related properties with respect to the defined maximum value.

Function block: Invalid trigger The setting of the Trigger condition property is not supported by the assigned
condition hardware resource.

129
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, select a setting for the Trigger
condition property that is supported by the assigned hardware resource.
§ Assign a hardware resource that supports the selected trigger condition. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Invalid trigger At least one of the following cases occurs:
configuration § The Sequence length property is set to 0 (= infinite) and the Trigger shift
property is not set to 0.
§ The Sequence length property is set to 0 (= infinite) and the Trigger mode
property is set to Ignore.
In this case the function block ignores the setting and internally uses the
Immediate setting instead.
§ The Trigger shift property is set to < 0 and the Trigger mode property is set
to Immediate.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, for example, specify valid values for the
Sequence length and the Trigger shift or Trigger mode properties. Use the
error description above to decide on the appropriate settings.

Function block: Invalid trigger The channel set assigned to the function block and the channel set assigned to
function provider assigned the referencing trigger function provider (for example, the Trigger In function
(not on same board) block) are located on different I/O boards.

The hardware resources assigned to the function block and the referencing
trigger function provider must be located on the same I/O board.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

130
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Remedy Choose one of the following alternatives:

§ Assign hardware resources from the same I/O board to the affected
function blocks. For instructions, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).
§ Reassign the trigger function provider (for example, a Trigger In function
block), so that all assigned hardware resources are located on the same I/O
board.

Function block: Invalid trigger The value of the Trigger period angle property does not match the angle range
period angle of the assigned master APU provider.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a value at the Trigger
period angle property that matches the angle range of the assigned master
APU provider.

Function block: Invalid trigger At least one of the following cases apply:
source feature configuration § The settings for the Digital filter property and the Trigger source property
are not compatible.
You can use the digital filter only in combination with the Time (free-
running) trigger source.
§ Digital filtering is not supported by the assigned hardware resource.
§ The specified setting for the Trigger source property is not supported by the
assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, change the setting of one property to
resolve the unsupported value setting or to match the features of the assigned
hardware resource.
§ Assign a hardware resource which provides the specified feature (digital
filtering or the specified setting for the Trigger source property). For
instructions on assigning hardware resources via the Properties Browser,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

131
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Invalid turn The sum of the values specified for the Single-turn bit width and the Multi-
bit width range turn bit width properties equals 0 (applies only for EnDat Master function
blocks) or exceeds the maximum value (applies for all function block types).

A maximum value of 48 bits is supported by the function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify values for the Single-
turn bit width and the Multi-turn bit width properties with respect to the
supported values and the values required to match the values stored in the
encoders memory. Refer to the data sheet of the encoder.

Function block: Invalid UDP The UDP Data Replay function block is not directly or indirectly assigned to an
Data Replay connection to Ethernet Setup function block. The referencing configuration includes only a
Data Streaming Ethernet Data Streaming Ethernet Setup function block instead.
Setup
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, assign the Ethernet Setup
function block to the function block that outputs the replayed UDP data.

Function block: Invalid usage A physical Ethernet controller is used by Ethernet function blocks that reside
of Ethernet interface in a in application processes of different processing unit applications. An Ethernet
multi-PU application Setup or Data Streaming Ethernet Setup function block can provide access to
a physical Ethernet controller only to function blocks that are processed by the
same processing unit.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Ensure that the physical Ethernet controller is used only by function
blocks that reside in application processes of the same processing unit
application.

132
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Function block: Invalid usage A virtual Ethernet interface of a bus simulation container is used by an Ethernet
of virtual Ethernet interface function block, such as a UDP Transmit function block, that resides in a different
in a multicore application application process. Virtual Ethernet interfaces of a bus simulation container can
provide the access to a physical Ethernet controller only to function blocks that
reside in the same application process as the Ethernet Setup function block the
bus simulation container is connected to.

The assignment of Ethernet function blocks to an application process is

determined by the following factors:
§ The mapping to model port blocks of model implementations that are
assigned to application processes.
§ The manual assignment of function blocks to application processes via
function block properties. Manual assignment is only supported by certain
function blocks, such as the Ethernet Setup function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Ensure that the virtual Ethernet interfaces of a bus simulation

container are used only by function blocks that reside in the same application
process according to the factors described above.

Function block: Invalid values The settings for the Event generation property and the Number of event
(event generation vs. number windows property are not compatible.
of event window(s))
If Event generation is enabled, the Number of event windows must not be
set to 0.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, choose one of the following
alternatives to make the properties match:
§ Set the Event generation property to Disabled.
§ Adjust the Number of event windows property.

Function block: Invalid values The settings for the Event generation property and the Trigger source
(event generation vs. trigger property are not compatible. Event generation is supported only when the
source) Trigger source property is set to Function trigger.

133
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, choose one of the following
alternatives to make the properties match:
§ Set the Event generation property to Disabled.
§ Set the Trigger source property to Function trigger.

Function block: Invalid values The values of the Index position and Linear resolution properties do not
(index position vs. linear match.
resolution)
The value range for the Index position property depends on the value of the
Linear resolution property.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, increase the value range by
configuring the Linear resolution property or decrease the Index position
value to be inside the given range.

Function block: Invalid Vbat The value specified at the Vbat lower limit property is equal to or greater than
range the value specified at the Vbat upper limit property.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – ✓

Remedy In the Conflicts Viewer, for example, specify a value at the Vbat
lower limit property that is smaller than the value of the Vbat upper limit
property.

Function block: Invalid vector A property value specified at the Vector Size function port (for example, Initial
size value) exceeds the setting of the Maximum vector size property specified at
the function block.

134
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, change the specified value for
the related properties with respect to the defined maximum value.

Function block: Invalid vector The specified initial value of the Vector Size function port of the Transmit
size (compared to TX buffer function is greater than the specified transmit buffer size.
size)
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Increase the buffer size to or above the initial value of the Vector Size
function inport.
§ Decrease the initial value of the Vector Size function inport to or below the
specified buffer size.

Function block: Invalid vector The specified initial value of the Vector Size function port of the Receive
size (compared to RX buffer function is greater than the specified receive buffer size.
size)
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Increase the buffer size to or above the initial value of the Vector Size
function inport.
§ Decrease the initial value of the Vector Size function inport to or below the
specified buffer size.

Function block: Mismatching At least one of the following cases occurs:

address resolution method § The address resolution method of the bus simulation container (BSC) does not
match the setting of the Ethernet Setup function block.
§ Different address resolution methods are set for the BSC communication
controllers that are mapped to the Configuration port of the Ethernet Setup
function block.

135
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Address resolution method
property of the Ethernet Setup function block to a matching value.
§ Map the Configuration port of the Ethernet Setup function block to
Configuration ports of one or more BSC communication controllers that
request the same address resolution method.

Function block: Mismatching The captured angle sequences overlap, because the following two cases occur in
angle sequences combination:
§ The sequence trigger source and the sample trigger source are both set to
Angle.
§ The difference between two angle sequence trigger positions is below the
minimum value.

To avoid overlaps, the angle difference between two angle sequence trigger
positions must not fall below the following value:

Minimum angle position difference = (Sequence length - 1) * Angle sample

distance + Minimum angle sample distance

With the minimum angle sample distance = 2 * (360° / 215) ≈ 0.022°

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Increase the angle differences at which the capturing of a sequence is
triggered via the Angle sequence triggers property.
§ Specify an angle position difference (via the Sequence length and Angle
sample distance properties) that is higher than the required minimum value
(see formula above).
§ Specify a setting other than Angle for at least one trigger source (sequence
trigger source or sample trigger source).

Function block: Mismatching A Deadline Violation event of the FlexRay function block is assigned to a
deadline violation settings task, and the DLV of synchronization task and/or DLV of application or
communication task properties are set to Terminate.

136
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, change the deadline violation property
settings to Warn.
§ In the Executable Application table, for example, delete the assignment of
the Deadline Violation event from the task.

Function block: Mismatching The settings for the Event generation property and the Pitch counter
event generation and pitch configuration property does not match.
counter configuration setting
If Event generation is enabled, the Pitch counter configuration property
must also be enabled.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Event generation property to
Disabled.
§ In the Properties Browser, set the Pitch counter configuration property to
Enabled.
For more information on providing I/O events, refer to Configuring the Basic
Functionality (Wheelspeed Out) (ConfigurationDesk I/O Function Implementation
Guide ).

Function block: Mismatching In a CTR<n> function group of a FlexRay function block, a Feedthrough Chx
feedthrough and termination value does not match the related Termination Chx value.

Feedthrough is set to True for a channel that is set to Terminated.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, change the value for
Feedthrough Chx to False or the value for Termination Chx to Not
Terminated.

137
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Mismatching Feedthrough mode is enabled but it is not supported by the selected transceiver
feedthrough mode and type and/or the assigned hardware resource.
transceiver type
Feedthrough mode is supported only for the ISO 11898-2 High‑Speed CAN and
ISO 11898‑2 CAN FD SIC transceiver types. For information on the hardware
resources that support feedthrough mode, refer to Hardware Dependencies
(CAN) (ConfigurationDesk I/O Function Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives to make the properties

match:
§ In the Conflicts Viewer, for example, change the Feedthrough mode
property.
§ In the Conflicts Viewer, for example, change the Transceiver type property.
§ Assign a hardware resource that supports the feedthrough mode. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Mismatching A function block requests the suppression of Internet group management
IGMP suppression setting protocol (IGMP) messages, but the referenced Ethernet Setup function block
enables the sending of IGMP messages or vice versa.

Note: The conflict causes ConfigurationDesk to generate default code during

the build process. For the default code, ConfigurationDesk uses the following
setting:
§ If all referencing function blocks request the same setting, ConfigurationDesk
uses the requested setting.
§ If the referencing function blocks request different settings, ConfigurationDesk
uses the setting of the Ethernet Setup function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, for example, set the IGMP suppression
property to a setting that matches the requested settings.

Function block: Mismatching The specified Internet protocol version does not match to the version that you
internet protocol version specified for the assigned Ethernet Setup or Data Streaming Ethernet Setup
of physical and virtual function block.
controllers

138
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

All members of an Ethernet network must use the same Internet Protocol
version, either IPv4 or IPv6.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, change the specified value for
the Internet protocol property to the commonly used protocol version.

Function block: Mismatching The specified Internet Protocol version does not match to the version that
Internet Protocol version of you specified for the assigned Ethernet setup function block (Ethernet Setup,
referencing function blocks Virtual Ethernet Setup, or Data Streaming Ethernet Setup function block).

All members of an Ethernet network must use the same Internet Protocol
version, either IPv4 or IPv6.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, change the specified value for
the Internet protocol property to the commonly used protocol version.

Function block: Mismatching The communication controller of the bus simulation container (BSC) does not
IP address match the IP address setting of the Ethernet Setup function block. A matching
IP address setting is necessary for BSC communication controller requesting an
exclusiv access.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, choose one of the following
alternatives:
§ Set the IP address property of the Ethernet Setup function block to the IP
address of the BSC communication controller.
§ Set the IP address property of the Ethernet Setup function block to 0.0.0.0
(IPv4) or 0:0:0:0:0:0:0:0 (IPv6).

139
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Mismatching At least one of the following cases occurs:

link speed § The communication controllers of the bus simulation container (BSC) request
a link speed that does not match the setting of the Ethernet Setup function
block.
§ Different link speed configurations are set for the BSC communication
controllers that are mapped to the Configuration port of the Ethernet Setup
function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Link Speed property of the
Ethernet Setup function block to a matching value.
§ Map the Configuration port of the Ethernet Setup function block to
Configuration ports of one or more BSC communication controllers that
request the same link speed.

Function block: Mismatching There is a mismatch between the (string-based) load description of a signal port
load descriptions and the (string-based) load description of the assigned hardware channel.

The load description is used for load compare checks, if the Compare mode
property is set to Load description is compared by system. For details, refer
to Specifying Load Settings (ConfigurationDesk I/O Function Implementation
Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Choose one of the following alternatives to make the properties

match:
§ Change the Compare mode property to Load description is compared by
user. In this case the load compare check by the system is disabled.
§ In the Conflicts Viewer, enter string-based descriptions for the Load
description property (at the corresponding signal port) and for the Load
description property for the assigned hardware channel that are identical.

Function block: Mismatching The specified settings for the Load rejection properties do not match for the
load rejection settings corresponding signal. You can, for example, enforce load rejection at different
positions in the signal path. For basics, refer to Basics on Load Rejection
(ConfigurationDesk Real-Time Implementation Guide ).

140
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

The conflict occurs in the following cases:

§ Load rejection is not enforced by a signal port (of a function block), but by the
assigned hardware.
§ Load rejection is not enforced by a signal port (of a function block), but by
the external load's device port mapped to the load signal port (of a function
block).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy In the Conflicts Viewer, for example, change the settings for the
Load rejection properties for one signal so that they are identically at all
positions in the signal path.

Function block: Mismatching This conflict applies to the Injection/Ignition Current In function block if you
maximum current use extended signal analysis.

The number of channel requests for the Digital Interface does not equal
the number of channel requests for the Analog interface, because you
have specified mismatching values at the Required current property for both
interfaces.

A single hardware channel is able to provide a certain voltage and current

range depending on the channel type. ConfigurationDesk uses the specified
Required current value to determine the number of hardware channels
needed. For further details on channel multiplication refer to Specifying Current
and Voltage Values for Channel Multiplication (ConfigurationDesk I/O Function
Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify matching values for
the Required current property of the Digital Interface and the Analog
Interface of the function block.

Function block: Mismatching The setting of the Measurement range property of at least one Sine Encoder
measurement range In function block differs from the setting of the Measurement range property
configuration of another Sine Encoder In function block.

All Sine Encoder In function blocks which use the Flexible In/Out 1
channel type from the same I/O board should have the same setting for
the Measurement range property. The assigned I/O board supports only a

141
May 2024 ConfigurationDesk Conflicts
Conflicts

common setting. In case of different settings, ConfigurationDesk uses the high

measurement range as a common default for all affected Sine Encoder In
function blocks.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, change the setting of the
Measurement range property of the affected function blocks, so that all
function blocks assigned to the same I/O board have the same setting (High or
Low).
§ Assign a different channel type from the related I/O board or a hardware
resources from another I/O board to the function blocks, which then are
configured to a different measurement range.

Function block: Mismatching The specified IP address is not a member of the subnetwork you specified for the
network address used Ethernet controller.

For example: You specified the subnet mask 255.255.255.0 and the local IP
address 192.168.1.10 to define the subnetwork. Then, you specify the default
gateway 192.168.2.2. In this case, the default gateway and the local IP address
are not members of the same subnetwork. Therefore, IP packets cannot be sent
to the default gateway.

The subnet mask of the Ethernet controller indicates how many most significant
bits of the IP address are used to specify the subnetwork address. The rest of
the IP address is the range to indicate members of the same subnetwork. In
the example, valid IP addresses for the default gateway are in the range of
192.168.1.0 ... 192.168.1.255, because the resulting subnetwork address of the
Ethernet controller is 192.168.1.x .

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify IP addresses that use the same
subnetwork address.
§ In the Properties Browser, specify a subnet mask for the used Ethernet
controller that results in a subnetwork address that matches to all IP addresses.
Use the error description above to decide on the appropriate setting.

142
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Function block: Mismatching A function block requests a certain optimization mode of the physical Ethernet
optimization controller, but the referenced Ethernet Setup function block specifies a different
mode.

Note: The conflict causes ConfigurationDesk to generate default code during

the build process. For the default code, ConfigurationDesk uses the following
setting:
§ If all referencing function blocks request the same optimization mode,
ConfigurationDesk uses the requested optimization mode.
§ If the referencing function blocks request different optimization modes,
ConfigurationDesk uses the setting of the Ethernet Setup function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, for example, set the Optimization

property to a setting that matches the requested optimization type.

Function block: Mismatching Partial networking is enabled but it is not supported by the selected transceiver
partial networking mode and type and/or the assigned hardware resource.
transceiver type
Partial networking is supported only for the ISO 11898-2 High‑Speed CAN
transceiver type. For information on the hardware resources that support partial
networking, refer to Hardware Dependencies (CAN) (ConfigurationDesk I/O
Function Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, change the Partial networking mode
property.
§ In the Conflicts Viewer, for example, change the Transceiver type property.
§ Assign a hardware resource that supports partial networking. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

Function block: Mismatching A CAN function block is referenced in one or more ECU Interface
property values regarding Configuration function blocks. At least one of the following settings differs for
CAN bus access request

143
May 2024 ConfigurationDesk Conflicts
Conflicts

the CAN function block and the EIC files that are imported to the ECU Interface
Configuration function blocks:
§ Baud rate
§ Sample point
§ CAN FD support
§ Data phase baud rate
§ Data phase sample point

If you do not resolve the conflict, default code is generated, i.e., the settings
that are specified for the CAN function block are used at run time. Nevertheless,
it might be useful to adapt the settings of the CAN function block to the
settings that are specified in the EIC files. Whether adapting the settings is useful
depends on your use scenario.

If the Baud rate and sample point source property of the CAN function block
is set to Model, you can change the baud rates and sample points at run time
using the Baud Rate, Sample Point, Data Phase Baud Rate, and/or Data
Phase Sample Point function ports.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy Choose one of the following alternatives:

§ If the CAN function block is affected by one or more EIC files that specify
identical settings, adapt the function block settings. Specify valid values for the
following properties, for example, in the Conflicts Viewer:
§ Baud rate, Sample point, Data phase baud rate, and/or Data phase
sample point properties of the CAN function block
§ Initial value and/or Initial substitute value properties of the Baud Rate,
Sample Point, Data Phase Baud Rate, and/or Data Phase Sample Point
function ports
§ CAN FD mode property of the CAN function block:
Select Enabled (Non-ISO) if you work with the non-ISO CAN FD protocol,
which is the original CAN FD protocol developed by Bosch. Select Enabled
(ISO) if you work with the ISO CAN FD protocol as specified in ISO 11898‑1.
§ If the CAN function block is affected by multiple EIC files that specify
different settings, change the Referencing Configuration in the related ECU
Interface Configuration function blocks:
Reference this CAN function block in ECU Interface Configuration function
blocks whose imported EIC files specify identical settings. Reference other
CAN function blocks in the ECU Interface Configuration function blocks
whose imported EIC files specify different settings.

144
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Function block: Mismatching A CAN function block is assigned to one or more bus access requests of one or
property values regarding more bus configurations. The assignment contains at least one of the following
CAN bus access request settings:
§ Case 1: The baud rate and/or data phase baud rate of the CAN function block
and an assigned bus access request differ.
To ensure correct run‑time behavior, the baud rates that are specified for the
CAN function block and that are required by the bus access requests must
match.
§ Case 2: A bus access request requires CAN FD support but the CAN FD
support is disabled for the CAN function block.
If a bus access request requires CAN FD support, the CAN FD support must be
enabled for the CAN function block.

If you do not resolve the conflict, default code is generated, i.e., the baud rate,
data phase baud rate, and CAN FD mode settings of the CAN function block
are used at run time. This might result in an unintended behavior of the CAN
communication.

However, if the Baud rate and sample point source property of the CAN
function block is set to Model, you can change the baud rates at run time using
the Baud Rate and/or Data Phase Baud Rate function ports.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy Choose one of the following alternatives, depending on the case

that causes the conflict:
§ Case 1: Depending on the CAN function block assignments, resolve the
mismatching baud rates as follows:
§ The CAN function block is assigned to bus access requests with identical
baud rates:
In the Conflicts Viewer, for example, specify valid values for the Baud rate
and/or Data phase baud rate properties of the CAN function block or for
the Initial value and/or Initial substitute value properties of the Baud
Rate and/or Data Phase Baud Rate function ports.
§ The CAN function block is assigned to bus access requests with different
baud rates: Change the conflicting baud rates of the bus access requests or
change the bus access assignment.
To change the conflicting baud rate property of a bus access request, select
the related communication cluster, for example, in the Bus Access Requests
table. Then, specify a valid value for the Baud rate and/or Data phase
baud rate properties in the Properties Browser.
To change the bus access assignment, select the related bus access requests
in the Bus Access Requests table and change the assigned bus access via
the Bus Access Assignment command, for example. Assign this function
block to bus access requests with identical baud rates. Use other CAN

145
May 2024 ConfigurationDesk Conflicts
Conflicts

function blocks to specify the bus access of the bus access requests with the
different baud rates.
§ Case 2: In the Conflicts Viewer, for example, enable the CAN FD mode:
§ Select Enabled (Non-ISO) if you work with the non-ISO CAN FD protocol.
This is the original CAN FD protocol developed by Bosch.
§ Select Enabled (ISO) if you work with the ISO CAN FD protocol as specified
in ISO 11898‑1.

Function block: Mismatching The Configuration port of a CAN function block is mapped to one or more
property values regarding Configuration Port blocks of one or more bus simulation containers (BSC files).
CAN Configuration Port At least one of the following settings differs for the CAN function block and a
mapped Configuration Port block:
§ Baud rate
§ CAN FD mode
§ Data phase baud rate

To ensure correct run‑time behavior, the baud rates that are specified for the
CAN function block and that are required by the Configuration Port blocks must
match. Moreover, if CAN FD support is required by a Configuration Port block,
the CAN FD support must be enabled in the CAN function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy Choose one of the following alternatives:

§ If one or more Configuration Port blocks with identical settings are mapped to
the CAN function block, adapt the function block settings. Specify valid values
for the following properties, for example, in the Conflicts Viewer:
§ Baud rate and/or Data phase baud rate properties of the CAN function
block
§ Initial value and/or Initial substitute value properties of the Baud Rate
and/or Data Phase Baud Rate function ports
§ CAN FD mode property of the CAN function block:
Select Enabled (Non-ISO) if you work with the non-ISO CAN FD protocol,
which is the original CAN FD protocol developed by Bosch. Select Enabled
(ISO) if you work with the ISO CAN FD protocol as specified in ISO 11898‑1.

146
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

§ If multiple Configuration Port blocks with different settings are mapped to the
CAN function block, change the mapping:
Map the Configuration Port blocks with identical settings to this CAN function
block. Map the Configuration Port blocks with different settings to other CAN
function blocks.

Function block: Mismatching A LIN function block is assigned to one or more bus access requests of one or
property values regarding LIN more bus configurations. The assignment contains at least one of the following
bus access request settings:
§ Case 1: The baud rates of the LIN function block and an assigned bus access
request differ.
The baud rate of a LIN function block and all its assigned bus access requests
must match.
§ Case 2: The sum of the LIN slaves and LIN masters that are assigned to the LIN
function block exceeds 64.
The maximum number of LIN slaves of one physical LIN bus is limited.
Therefore, one LIN function block can specify the bus access for up to 64
LIN slaves. Because each LIN master provides one LIN slave task, the number of
assigned LIN masters affects the number of assigned LIN slaves as well.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives, depending on the case

that causes the conflict:
§ Case 1: Depending on the LIN function block assignments, resolve the
mismatching baud rates as follows:
§ The LIN function block is assigned to bus access requests with identical
baud rates: In the Conflicts Viewer, for example, adapt the Baud rate of
the LIN function block to the baud rate of the bus access requests.
§ The LIN function block is assigned to bus access requests with different
baud rates: Change the conflicting baud rates of the bus access requests or
change the bus access assignment.
To change the baud rate of a bus access request, select the related
communication cluster, for example, in the Bus Access Requests table.
Then, specify a valid value for the Baud rate property in the Properties
Browser.
To change the bus access assignment, select the related bus access requests
in the Bus Access Requests table and change the assigned bus access via
the Bus Access Assignment command, for example. Assign this function
block to bus access requests with identical baud rates. Use other LIN
function blocks to specify the bus access of the bus access requests with
the different baud rates.

147
May 2024 ConfigurationDesk Conflicts
Conflicts

§ Case 2: Depending on the LIN function block assignments, reduce the number
of LIN slaves and/or LIN masters as follows:
§ The LIN function block is assigned to one bus access request: In the Bus
Configurations table, remove as many LIN slaves and/or LIN masters as
necessary from the related bus configuration. Assign the removed LIN slaves
and LIN masters to other bus configurations and use other LIN function
blocks to specify their bus access.
§ The LIN function block is assigned to multiple bus access requests: In the
Bus Access Requests table, select the related bus access requests and
change the bus access assignment of as many bus access requests as
necessary, for example, via the Bus Access Assignment command.

Function block: Mismatching One or more Configuration ports of bus simulation containers are mapped to
property values regarding LIN a LIN function block. The baud rates of the Configuration ports and the LIN
Configuration Port function block differ.

The baud rates of all the Configuration ports that are mapped to one LIN
function block and the baud rates of the LIN function block itself must match.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ If either one Configuration port or multiple Configuration ports with
identical baud rates are mapped to the LIN function block, adapt the function
block's baud rate:
In the Conflicts Viewer, for example, specify a valid value for the Baud rate
property.
§ If multiple Configuration ports with different baud rates are mapped to the
LIN function block, change the mapping of the Configuration ports:
Map the Configuration ports with identical baud rates to this LIN function
block. Map the Configuration ports with different baud rates to other LIN
function blocks.

Function block: Mismatching The signals specified for at least one signal pair (for example, A+ and A-) are
sector signal pair problematic. The output levels of the related signal pairs are active at the same
time. This might cause a short circuit in unprotected half bridges.

Signal settings for a signal pair that do not lead to a conflict are:
§ Inactive and all other signals
§ PWM and Inverted PWM
§ Complement PWM and Complement inverted PWM

148
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Signal pair check property to
Disabled. Ensure, that disabling the signal pair check will not result in damage
to the connected half bridges..
§ Specify only the signals for a signal pair that leads not to a problematic
combination. Refer to Configuring Sector and Stationary Signals (Block-
Commutated PWM Out) (ConfigurationDesk I/O Function Implementation
Guide ).

Function block: Mismatching The communication controller of the bus simulation container (BSC) does not
subnet mask match the subnet mask setting of the Ethernet Setup function block. A
matching subnet mask setting is necessary for BSC communication controller
requesting an exclusiv access.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, set the Subnet mask
property of the Ethernet Setup function block to the subnet mask of the BSC
communication controller.

Function block: Mismatching The communication controller of the bus simulation container (BSC) does not
subnet prefix length match the subnet prefix length setting of the Ethernet Setup function block.
A matching subnet prefix length setting is necessary for BSC communication
controller requesting an exclusiv access.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, set the Subnet prefix length
property of the Ethernet Setup function block to the subnet prefix length of the
BSC communication controller.

149
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Mismatching An Ethernet switch port for MACsec functionality and an Ethernet controller
switch port assigned (not on are assigned to the same function block, but the Ethernet switch port and the
same board) Ethernet controller are not on the same board.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, for example, assign an Ethernet switch port
and an Ethernet controller of the same Ethernet board.

Function block: Mismatching The descriptions of the Pump cell resistor property and the Load description
values (pump cell resistance vs property (at the corresponding signal port), and/or description of the assigned
load description) hardware channel do not match.

The load description is used for load compare checks, if the property Compare
mode is set to Load description is compared by system. For details, refer
to Specifying Load Settings (ConfigurationDesk I/O Function Implementation
Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy In the Conflicts Viewer, for example, enter descriptions for the
Load description property (at the corresponding signal port and for the
assigned hardware channel, the latter via Platform Manager) that are identical
to the Pump cell resistor value property value.

Function block: Mismatching This conflict is generated in the following cases:

wavetable sizes § The angle range of the imported wavetables does not match the angle range
of the referenced master APU provider.
The function block supports two wavetable sizes:
§ Wavetables with 65536 entries that support master APUs with an angle
range of 720° for one engine cycle.
If the referenced master APU has an angle range of 360°, only the first
32768 entries are output.
§ Wavetables with 32768 entries that support master APUs with an angle
range of 360° for one engine cycle.
If the referenced master APU has an angle range of 720°, the wavetable is
output twice.
For more information, refer to Execution of angular-coded wavetables
(ConfigurationDesk I/O Function Implementation Guide ).

150
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

§ Not all wavetables that are referenced by the same function block have the
same wavetable size.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy Choose one of the following alternatives:

§ Via the Imported wavetable files property, import wavetable files that
support the angle range of the referenced master APU provider.
§ Via the Assigned master APU provider property, assign a master APU
provider that supports the wavetable size of the imported wavetable files.
§ Change the wavetables so that they all have the same number of wavetable
values.

Function block: Missing For an electrical interface unit with an assigned angle unit channel set or an
channel assignment assigned Ethernet adapter channel set, at least one channel request is not
assigned.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, assign an angle unit or an

Ethernet adapter (depending on the function block) to each channel request
of the function block. For instructions on assigning them via the Properties
Browser, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Missing For an electrical interface unit with an assigned channel set, at least one channel
channel assignment request is not assigned.

ConfigurationDesk determines the types and number of channels required for

a function block according to the assigned channel set, the function block
features, the block configuration and the required physical ranges. The required
channels are called channel requests.

Hardware resource (channels of channel sets) are required for most function
blocks to perform the I/O functionality. For more basics, refer to Basics on
Hardware Resource Assignment (ConfigurationDesk Real-Time Implementation
Guide ).

151
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, for example, assign a channel to each

channel request of the function block. For instructions on assigning them via the
Properties Browser, refer to How To Assign Hardware Resources via Function
Block Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Missing At least one electrical interface unit of the function block is not assigned to a
channel set assignment channel set.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, assign a channel set to the
function block. For instructions on assigning them via the Properties Browser,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

Function block: Missing or At least one of the following conditions is met:

invalid digital filter § No digital filter file is imported via the Import digital filters property.
§ No digital filter file is assigned at one or more of the Assigned digital filter
A, B, C properties.
§ A digital filter file that is assigned to a digital filter is missing in the list of
imported digital filter files, for example, because it was removed after the
assignment.

The following conditions must be met:

§ At least one digital filter file must be imported.
§ A digital filter file must be assigned to each of the three digital filters. All
assigned digital filter files must be in the list of the imported digital filter files.

152
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, import at least one digital
filter file via the Import digital filters property and assign a digital filter file to
each digital filter at the Assigned digital filter A, B, C properties.

Function block: Missing or A function block enables MACsec functionality but no Ethernet switch port is
invalid switch port (not assigned or the assigned Ethernet switch port does not support MACsec.
supporting MACsec)
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, for example, assign an Ethernet switch port
that supports MACsec.

Function block: Missing The number of connections to or from a custom function block to other function
or supernumerous block blocks (for example, the number of connections from APU provider to slave
connections (by constraint) APUs) does not match a MultiplicityConstraint that was defined for the custom
function block type.

For more information on custom function blocks, refer to ConfigurationDesk

Custom I/O Function Implementation Guide .

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Connect the correct number of function blocks to satisfy the

MultiplicityConstraint.

Function block: Missing user The source code file (<Custom_Function_Block_Name>.cpp) and/or header
file(s) file (<Custom_Function_Block_Name>.h) of a custom function block used in
your ConfigurationDesk application are/is missing.

Custom functions (such as the UART function) consist of an XML file, a

source code file, a header file, and a type definition header file. The source
code and header files of a custom function must be located in the same
custom functions folder as the XML file. A missing type definition header file

153
May 2024 ConfigurationDesk Conflicts
Conflicts

(<Custom_Function_Block_Name>_TypeDef.h) does not cause the conflict

since it would be automatically generated during the build process if it was
missing.

Custom function folders are defined via global or application-specific

search paths. Refer to Basics on Search Paths and User Location Files
(ConfigurationDesk Custom I/O Function Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, the names of the missing files are displayed
in the Value column. Add the missing custom function files to the folder
where the XML file is located. Afterwards, use the Reload Custom Functions
command in the Function Browser.

Function block: Missing VLAN The protocol-based VLAN configuration is enabled, but no VLAN is specified for
membership type the membership tagged or untagged of the Ethernet switch port.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a VLAN for the
membership tagged or untagged.

Function block: Multiple The assignment of a function block to an application process is determined by
assignments to different the following factors:
application processes § The mapping to model port blocks of model implementations that are
assigned to application processes.
§ The assignment of I/O events to tasks that are assigned to application
processes.
§ The manual assignment of function blocks to application processes via
function block properties. Manual assignment is only supported by certain
function blocks, such as the Data Streaming Ethernet Setup function block.
§ The referencing of function blocks that must reside in the same application
process, such as the referencing of Injection Out function blocks to Engine
Control Setup function blocks. The referenced and the referencing function
block determines the application process assignment.

154
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

This conflict is generated only if these factors produce an assignment of a

function block to more than one application process.

Note

If you use Bus Configuration function blocks in the ConfigurationDesk

application, there are additional factors that determine the assignment to
an application process. However, if a Bus Configuration function block
is assigned to more than one application process, the 'Bus Configuration:
No valid application process assigned' conflict is also generated. Resolve
this conflict to assign the Bus Configuration function block to only one
application process. Refer to Resolving the Bus Configuration Conflict:
No Valid Application Process Assigned (ConfigurationDesk Bus Manager
Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Ensure that a function block is assigned to only one application

process according to the factors described above.

Function block: Multiple data An application process processes data of different high-speed data streams.
streaming blocks participate
Multiple application processes can process data of a high-speed data stream, but
in an application process
each application process can process only data of one high-speed data stream.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy
§ In the Conflicts Viewer, for example, ensure that all Data Streaming
Ethernet Setup function blocks are assigned to different application
processes.
§ Ensure that the Ethernet Setup and CAN function blocks of the same
application process are assigned to the same Data Streaming Ethernet
Setup function block for data replay.

Function block: Multiple This conflict is generated in the following cases:

processing units connected § Case 1: The function block provides two or more electrical interface units.
These units are assigned to hardware resources (e.g., channels on different I/O
boards) which are directly or indirectly connected to different processing units
(for example, SCALEXIO Processing Units or DS6001 Processor Boards).

155
May 2024 ConfigurationDesk Conflicts
Conflicts

§ Case 2: The function block is mapped to a behavior model that is executed in

a processing unit application that is assigned to processing unit A. However,
the electrical interface unit of the function block is assigned to hardware
resources that are directly or indirectly connected to processing unit B.
§ Case 3: This function block A is referenced by function block B. Function block
B also references function block C. The hardware resources that are assigned
to function block A and C are directly or indirectly connected to different
processing units.
§ Case 4: This function block A is referenced by function block B. Function
block B is mapped to a behavior model. The behavior model is executed in a
processing unit application that is assigned to a processing unit. The hardware
resources that are assigned to function block A are directly or indirectly
connected to a different processing unit.

A function block must have a direct or indirect hardware connection to only one
processing unit (for example, SCALEXIO Processing Unit or DS6001 Processor
Board).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Choose one of the following alternatives depending on your

hardware constellation:
§ Assign a hardware resource with the following characteristics to the function
block: The hardware resource must be directly or indirectly connected to
the same processing unit to which the function block is connected, e.g.,
by means of a processing unit application. For instructions, refer to How To
Assign Hardware Resources via Function Block Properties (ConfigurationDesk
Real-Time Implementation Guide ).
§ Specify a connection to a processing unit via the Uplink or Downlink
properties to get a connection to the same processing unit to which
the function block is connected, e.g., by means of a hardware resource
assignment. These hardware properties are available for IOCNET Routers and
IOCNET Link Boards. For information on accessing the properties, refer to How
to Access Hardware Properties (ConfigurationDesk Real-Time Implementation
Guide ). For basics on the IOCNET connections in a SCALEXIO system, refer
to Network Concept (SCALEXIO Hardware Installation and Configuration ).
§ Only for case 2 and 4: Assign the same processing unit to the processing
unit application that is also connected to the function block by means of
a hardware resource assignment. For instructions, refer to How to Assign
Processing Units to Processing Unit Applications (ConfigurationDesk Real-Time
Implementation Guide ).
§ Only for case 3 and 4: Delete the reference to this function block in the
referencing function block.

Function block: Multiple The function block is triggered by more than one function module but is
triggering not multitriggerable. For more information on multiple function triggers, refer

156
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

to Basics on Function Triggers (ConfigurationDesk Real-Time Implementation

Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy Make sure that the function is triggered by only one function
module. For details, refer to How to Avoid Multiple Function Triggers
(ConfigurationDesk Real-Time Implementation Guide ).
Note: The assignment of a data port to its associated function module can be
determined only during the model code generation and not during the model
analysis. If you move data port blocks in the behavior model from one subsystem
to another, this action might trigger this conflict even if the reason for this
conflict was eliminated and the model was re-analyzed in ConfigurationDesk.
Generating the model code (either by starting the build process or by generating
it explicitly) updates this information and resets the conflict.

Function block: No The use of an application-specific protocol file is enabled, but no protocol file is
application-specific protocol assigned.
file assigned
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy Choose one of the following alternatives:

§ Import an application-specific protocol with the Protocol file property.
To import a protocol file, you can enter its file path or
you can open the standard Open dialog to browse for and
select a protocol file. Predefined protocol files are located in the
<InstallationFolder>\ConfigurationDesk\Implementation\
UserFiles> folder.
§ Disable the use of an application-specific protocol and evaluate a custom
protocol by providing the values of each nibble pulse to the behavior model
separately.

Function block: No A function block is implicitly assigned to an application process via:

assignment to application § Its mapping lines to model port blocks of model implementations that are
process assigned to application processes.
§ The assignment of its I/O events to tasks that are assigned to application
processes.
§ The hardware assignment: A function block must have a direct or indirect
hardware connection to processing hardware.

157
May 2024 ConfigurationDesk Conflicts
Conflicts

To generate code, each function block must be assigned to an application

process.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Assign the function block to an application process. Consider the

factors described above.

Function block: No central The hardware topology in your active ConfigurationDesk application does not
FIU hardware available in contain central FIU hardware which supports the failure simulation feature.
hardware topology
To use failure simulation with a SCALEXIO system, it has to be equipped, for
example, with a DS2680 I/O Unit or a DS2642 FIU & Power Switch Board. These
boards provide a central failure insertion unit (FIU). The central FIU switches the
signal from the ECU pin to simulate the failure.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Failure simulation property to
Not required.
§ Extend the hardware topology by adding the required central FIU hardware
(a DS2680 I/O Unit or a DS2642 FIU & Power Switch Board). For instructions,
refer to How to Extend Existing Hardware Topologies (ConfigurationDesk Real-
Time Implementation Guide ).
§ Replace the hardware topology by scanning a registered SCALEXIO hardware
system, which contains the required central FIU hardware (a DS2680 I/O Unit
or a DS2642 FIU & Power Switch Board). For instructions, refer to How to
Import a Hardware Topology (ConfigurationDesk Real-Time Implementation
Guide ).

Function block: No data High-speed data streaming is enabled for the function block, but no Data
streaming provider assigned Streaming Ethernet Setup function block is assigned to the function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

158
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, assign a Data Streaming Ethernet
Setup function block.
§ In the Properties Browser, set the High-speed data streaming property to
Disable.

Function block: No EIC file An ECU Interface Configuration function block is available in the active
imported ConfigurationDesk application and no ECU interface container (EIC) file is
imported to the function block.

Each ECU Interface Configuration function block that is available in a

ConfigurationDesk application requires one ECU interface container (EIC) file.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Import an EIC file to the ECU Interface Configuration function block.
For instructions, refer to How to Import ECU Interface Container (EIC) Files
(ConfigurationDesk Real-Time Implementation Guide ).
§ Delete the ECU Interface Configuration function block from the
ConfigurationDesk application.

Function block: No engine The function block does not reference an Engine Simulation Setup function
simulation setup assigned block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, for example, select an instantiated Engine

Simulation Setup function block via the Assigned simulation setup property.

Function block: No feature The function block does not reference the required feature provider, for example:
provider assigned § A Current In or a Voltage In function block does not reference a master APU
provider (such as an Angular Clock Setup function block).
§ An ECU Interface Configuration function block does not reference an
Ethernet Setup or CAN function block.
§ A function block that use a trigger function as trigger source does not does
not reference a trigger function provider.

159
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, assign the required feature
provider. Choose one of the following alternatives depending on the conflicting
function block type:
§ Assign a master APU provider (such as an Angular Clock Setup function
block) to the conflicting Current In or Voltage In function block.
§ Assign an Ethernet Setup or CAN function block to the conflicting ECU
Interface Configuration function block.
§ Assign a trigger function provider (such as a Trigger In function block) to the
conflicting function block.

Function block: No or invalid Using a function block requiring a master APU provider, the conflict occurs in
master APU provider assigned one of the following cases:
§ Case 1: An Engine Simulation Setup function block does not reference a
master APU provider (such as an Angular Clock Setup function block).
§ Case 2: There is a mismatch between the processing unit assigned to the
master APU provider and the processing unit, that is indirectly connected to
the Engine Simulation Setup function block, for example, via its model port
mapping. For details, refer to Creating Multi-Processing-Unit Applications With
ConfigurationDesk (ConfigurationDesk Real-Time Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives depending on the case

that causes the conflict:
§ Case 1: In the Conflicts Viewer, for example, assign a master APU provider
to the conflicting Engine Simulation Setup via the Assigned master APU
provider property.
§ Case 2: Resolve the mismatch by one of the following alternatives:
§ Assign a master APU providing function block that is assigned to the same
processing unit as the Engine Simulation Setup function block itself.
§ Change the indirect connection between the Engine Simulation Setup
function block and the processing unit, for example, via model port
mapping.
§ Change the hardware resource assignment and (if existing) the model port
mapping of the master APU provider.
§ Assign the behavior model to an application process whose processing unit
application is assigned to a matching processing unit.

160
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

§ Assign the application process (containing a behavior model) to another

processing unit application to match the processing unit assignment.

Function block: No timestamp The assigned hardware resource does not support timestamp capturing.
provided
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Capture timestamp property to
Disabled.
§ Assign a hardware resource to the function block that supports timestamp
capturing. For instructions, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).

Function block: No wavetable No wavetable file specifying the crankshaft wheel is imported.
imported
The crankshaft wheel in use must be specified via an imported wavetable file.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, import a wavetable file with
crankshaft specifications via the Imported wavetable file property.

Function block: No wavetable The function block must reference one or more wavetable files.
imported
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy Specify the Imported wavetable files property value by importing

one or more wavetable files, which is possible via the Import Wavetables
dialog. You can open the dialog from the Conflicts Viewer, for example.

161
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Too many bits The required buffer size for the related SPI Cycle function exceeds the buffer size
per SPI cycle of the assigned hardware resource.

The required buffer size is specified by the Number of words and Number of
bits per word property values and the hardware-specific word width. The buffer
size can be calculated as follows:

BufferSize = floor((NumberOfBitsPerWord+WordWidth-1)/ WordWidth)·WordWidth· NumberOfWords

Hardware-specific word width:
§ DS1203 (MicroLabBox II): 32 bit
§ DS1511, DS1513, DS1552 (all MicroAutoBox III): 16 bit

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, decrease the values of the
Number of words and/or the Number of bits per word properties so that the
required buffer size does not exceed the buffer size of the assigned hardware
resource.

Function block: Too many More function blocks of a certain function block type are assigned to the
function blocks of the same application process than allowed. For example, only one Data Streaming
function block type assigned Ethernet Setup function block can be assigned to an application process.
to an application process
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Assign the function blocks to different application processes via

model port mapping or via the Manually assigned application process
property, for example. Note that referencing function blocks must be assigned to
the same application process.

Function block: Too many More instantiated function blocks of the related function block type are used in
instances of the same your ConfigurationDesk application than possible.
function block type
For example, only one Crank In function block can be used in a
ConfigurationDesk application.

162
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – ✓

Remedy Reduce the number of instantiated function blocks of the related

function block type in your active ConfigurationDesk application to the
maximum possible number.
The maximum possible number is shown in the Conflicts Viewer and in the
Instance limit property at the related function block type properties.

Function block: Too many More than one FuSa Memory Monitoring function block is assigned indirectly
instances of function to the same processor board via an application process.
block type 'FuSa Memory
Only one FuSa Memory Monitoring function block is supported for each
Monitoring'
processor board

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – ✓

Remedy In the Conflicts Viewer, for example, delete all but one FuSa
Memory Monitoring function block that are indirectly assigned to the same
processor board (for example, MicroAutoBox III) from the ConfigurationDesk
application.

Function block: Too many More than one FuSa System Monitoring function block is assigned indirectly to
instances of function block the same processor board via an application process.
type 'FuSa System Monitoring'
Only one FuSa System Monitoring function block is supported for each
processor board

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – ✓

Remedy In the Conflicts Viewer, for example, delete all but one FuSa
System Monitoring function block that are indirectly assigned to the same
processor board (for example, MicroAutoBox III) from the ConfigurationDesk
application.

163
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Too many LIN A LIN function block is assigned to multiple LIN bus access requests. Two or more
masters assigned of these LIN bus access requests contain a LIN master.

Each physical LIN bus must have exactly one LIN master. If one LIN function block
is assigned to multiple bus access requests with two or more LIN masters, exactly
one of the LIN masters must be active at run time.

Note

If you do not resolve this conflict before you build a real-time application,
you must manually ensure that exactly one LIN master is active at run time.

Tip

If the bus access requests that contain the LIN masters result from different
bus configurations, you can add the Bus Configuration Enable feature
to the affected bus configurations. If you do this, you can deactivate all
the bus configurations except for one at run time to have exactly one LIN
master active at a time. In this case, you do not have to resolve this conflict.
For more information, refer to Enabling and Disabling Bus Configurations
(ConfigurationDesk Bus Manager Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy Perform the following steps:

1. In the Conflicts Viewer, determine the bus access requests whose LIN
master property is set to True.
2. Select these bus access requests in the Bus Access Requests table and
change the bus access assignment except for one, for example, via the Bus
Access Assignment command.

Function block: Too many Function blocks that use different time domains are assigned to the same
time synchronization domains physical Ethernet controller.
assigned
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the affected function blocks to the
same time domain.

164
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

§ In the Properties Browser, for example, assign different physical Ethernet

controllers to the affected function blocks.

Function block: Too many The specified number of assigned wavetables exceeds the maximum value that is
wavetables assigned supported by the assigned hardware resource.

The maximum number of wavetables per function block is limited by the board's
wavetable memory as follows:
§ DS2680 I/O Unit: Max. 24 wavetable references
§ DS2621 Signal Generation Board: Max. 12 wavetable references
§ DS6101 Multi-I/O Board: Max. 12 wavetable references
§ DS6202 Digital I/O Board: Max. 4 wavetable references
§ DS6241 D/A Board: Max. 12 wavetable references
§ :DS6242 D/A Board: Max. 12 wavetable references

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Decrease the total number of assigned wavetables with respect to the limit of
the assigned hardware resource via the Imported wavetable files property.
§ Assign a hardware resource that supports the specified number of assigned
wavetables. For instructions, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).

Function block: Unfavorable Depending on the rotating speed of the simulated or measured device (e.g.,
angle sample distance crankshaft), samples may not be captured, because the following two cases
occur in combination:
§ The sample trigger source is set to Angle.
§ The distance between two angle samples is lower than a critical distance (see
formula below).

To ensure that samples are captured at all APU speeds, the distance between two
angle samples must not fall below the following value:

Critical distance = Minimum sample period * Maximum APU speed.

The minimum sample period depends on the hardware resource assigned to the
function block. The maximum APU speed depends on the assigned APU provider.
For hardware-specific values, refer to dSPACE Help.

165
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify an angle sample distance (via
the Angle sample distance property) that is higher than the critical distance
(see formula above).
§ Reduce the maximum APU speed of the master APU provider via the
Maximum speed property.
§ Specify a setting other than Angle for the sample trigger source.

Function block: Unfavorable Depending on the rotating speed of the simulated or measured device (e.g.,
angle sequence triggers crankshaft), sequences may not be captured, because the following two cases
occur in combination:
§ The sequence trigger source to Angle.
§ The distance between two angle sequence trigger positions is lower than a
critical distance (see formula below).

To ensure that sequences are captured at all APU speeds, the distance between
two angle sequence trigger positions must not fall below the following value:

Critical distance = Minimum sample period * Maximum APU speed.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy Choose one of the following alternatives:

§ Specify a distance between two angle sequence trigger positions (via the
Angle sequence trigger property) that is higher than the critical distance (see
formula above).
§ Reduce the maximum APU speed of the master APU provider via the
Maximum speed property.
§ Specify a setting other than Angle for the sequence trigger source.

Function block: Unfavorable The maximum pulse length of a nibble pulse might be longer than or equal to
pulse configuration the minimum pulse length of the synchronization pulse.

166
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

In the Conflicts Viewer, the Maximal nibble length property and the Minimal
sync pulse length property show the calculated pulse lengths.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy In the Conflicts Viewer, for example, check the properties for the
SENT timing and set values that ensure a sufficiently long sync pulse length.
For basics on the timing of SENT pulses, refer to Basics on the SENT Protocol
(ConfigurationDesk I/O Function Implementation Guide ).

Function block: Unresolved A hardware resource has been assigned, but is no longer required by the
channel request function block (= obsolete).

Example: A function block first requires five channels, but needs only two
channels after reconfiguration. Three channels are obsolete but still assigned to
the function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, delete the assignment to resolve the

conflict. You can use obsolete channels without explicitly deleting the
assignment. In this case, obsolete channel requests and their assignments are
removed automatically after reassigning the channel.

Function block: Unresolved A port of the function block is obsolete. The port is mapped but due to
elements configuration changes to the function block the port is no longer required.

The mapping is not deleted immediately, because this simplifies the remapping
of the corresponding model port block or device block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Remove the mapping line from the obsolete port. This port then is
deleted.

167
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Unresolved You imported a ConfigurationDesk application which contains custom function
function block type blocks whose accompanying plug-in is not installed on your host PC.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Provide the missing plug-in. After this, the function block is resolved
and you can use the block without restrictions.
Custom functions must be available in a search path for user location files or
installed via dSPACE add-on. Refer to Basics on Search Paths and User Location
Files (ConfigurationDesk Custom I/O Function Implementation Guide ).

Function block: Unresolved At least one function block that is related to Functional Safety (FuSa) has a
FuSa configuration conflicts conflicting configuration.

The build process is aborted if only one FuSa function block contains a conflicting
configuration.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Resolve all configuration conflicts of the affected FuSa function

blocks.

Function block: Unsupported The Activation by FRU relay property is set to Allowed for a signal port even
activation by FRU relay though you have configured current enhancement for that signal.

Activation by FRU relay is not supported in case of current enhancement. You

can allow Activation by FRU relay, for example, to support the simulation of
multiple failures in the experiment software.
§ For more information on Activation by FRU relay and simulation of multiple
failures, refer to Specifying Failure Simulation Settings (ConfigurationDesk
Real-Time Implementation Guide ).
§ For more information on current enhancement, refer to see Specifying Current
and Voltage Values for Channel Multiplication (ConfigurationDesk I/O Function
Implementation Guide ).

168
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, for example, set the Activation by FRU
relay property to Not allowed.

Function block: Unsupported No sequence is captured, because the following two cases occur in combination:
angle sequence triggers § The sequence trigger source is set to Angle.
§ The distance between two angle sequence trigger positions is lower than the
minimum angle sample distance.

To capture sequences, the distance between two angle sequence trigger

positions must not fall below the following value:

Minimum angle sample distance = 2 * 720° / 216

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a setting other than Angle for
the sequence trigger source.
§ Specify a distance between two angle sequence trigger positions (via the
Angle sequence trigger property) that is higher than the minimum angle
sample distance (see formula above).

Function block: Unsupported The selected baud rate is not supported by the assigned hardware.
baud rate
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, select a baud rate that is supported by
the assigned hardware resource.
§ In the Properties Browser, assign a hardware resource that supports
the required baud rate. Refer to Hardware Dependencies (UART)
(ConfigurationDesk I/O Function Implementation Guide ).

169
May 2024 ConfigurationDesk Conflicts
Conflicts

Function block: Unsupported The Configuration port of a CAN function block is mapped to a Configuration
baud rate and sample point Port block that is generated for an RTICANMM ControllerSetup block of the
source RTI CAN MultiMessage Blockset. The Baud rate and sample point source
property of the CAN function block is set to Model.

When the Configuration port of a CAN function block is mapped to a

Configuration Port block that is generated for an RTICANMM ControllerSetup
block, the Baud rate and sample point source property of the CAN function
block must be set to Function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set Baud rate and sample point
source to Function block.
§ Map the Configuration Port block to another CAN function block.

Function block: Unsupported For the ECU Interface Configuration function block, the following applies:
ECU interface container for § An ECU interface container (EIC file) of version 3.0.0 or earlier is imported.
MicroAutoBox III § An Ethernet Setup function block is referenced to which a hardware resource
provided by the MicroAutoBox III is assigned.

Hardware provided by the MicroAutoBox III supports ECU interface containers

as of version 4.0.0. For more information, refer to Compatibility of
ConfigurationDesk 2024-A (24.1) (ConfigurationDesk New Features And
Migration ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Import an ECU interface container that is supported by the MicroAutoBox III
to the ECU Interface Configuration function block. For instructions, refer
to How to Import ECU Interface Container (EIC) Files (ConfigurationDesk Real-
Time Implementation Guide ).
§ Assign a hardware resource that supports the imported ECU interface
container to the referenced Ethernet Setup function block. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

170
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

§ Select an Ethernet Setup function block to which a suitable hardware

resource is assigned as the Referencing Configuration in the ECU Interface
Configuration function block.

Function block: Unsupported An ECU interface container (EIC) file that is imported to an ECU Interface
ECU interface container for Configuration function block does not support the target architecture that is
target architecture required by the related real‑time hardware.

An ECU interface container (EIC) file that is imported to an ECU Interface

Configuration function block must support the target architecture that is
required by the related real‑time hardware, i.e., 32‑bit or 64‑bit. EIC files up to
and including file version 4.0.0 only support a 32‑bit target architecture. EIC files
as of version 5.0.0 support 32‑bit and 64‑bit target architectures.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Import an ECU interface container (EIC) file to the ECU Interface
Configuration function block that supports the target architecture that is
required by the real‑time hardware. For instructions, refer to How to Import
ECU Interface Container (EIC) Files (ConfigurationDesk Real-Time Implementation
Guide ).

Function block: Unsupported The settings for the Event generation property and the Sequence trigger
event generation for capture source property are not compatible.
trigger source = 'Model-
Event generation is not supported for a Model task trigger source.
based'
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy In the Conflicts Viewer, for example, choose one of the following
alternatives to make the properties match:
§ Set the Event generation property to Disabled.
§ Change the Sequence trigger source property to Sequence end,
Threshold, Angle, Digital threshold or Trigger function.

Function block: Unsupported The Trigger source property of the function block is set to I/O function, but the
function trigger assigned hardware resource does not support any function block that can work
as a trigger function provider.

171
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Set the Trigger source property to another trigger source, for example, to
Edge.
§ Assign a hardware resource that supports an I/O function as trigger source.
For instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Unsupported The Internet Protocol version that is specified for an ECU Interface
Internet Protocol version for Configuration function block does match the Internet Protocol version that is
the imported ECU interface required according to the imported ECU interface container (EIC) file.
container
If the ECU interface container (EIC) file that is imported to an ECU Interface
Configuration function block specifies only an IPv4 or IPv6 address, the
respective Internet Protocol version, i.e., IPv4 or IPv6, must be selected in the
function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, set the Internet protocol
property of the ECU Interface Configuration function block to the required
value.

Function block: Unsupported The specified value for the Maximum message count property exceeds the
maximum message count possible value range of the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Maximum
message count property that matches the maximum value supported by the
assigned hardware resource.

172
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

§ Assign a hardware resource that supports the required number of nibbles. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Unsupported The specified setting for the Measured phases property is not supported by the
measured phases assigned hardware resource.

If all three phases should be measured (ABC setting), the assigned channel set
has to provide at least three channels.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, change the Measured phases property
to a setting that is supported by the assigned hardware resource.
§ Assign a hardware resource that provides the required number of channels in
one channel set. For instructions, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).

Function block: Unsupported This conflict is generated in the following cases:

measurement point § The specified settings for the Measurement point property and the Signal
type property do not match.

Note

Current signals can only be measured on the load side and not on the
ECU side.

§ The specified setting for the Measurement point property is not supported
by the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, change the setting for the
Measurement point property or the Signal type property to match the
setting of the other.
§ In the Conflicts Viewer, for example, select a setting for the Measurement
point property that is supported by the assigned hardware resource.

173
May 2024 ConfigurationDesk Conflicts
Conflicts

§ Assign a hardware resource that supports the specified setting. For

instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: A UDP Data Replay function block references an Ethernet Setup function
Unsupported multi- block that resides in a different application process. The referencing can be
application configuration for directly or via other function blocks.
UDP Data Replay block
The assignment of Ethernet function blocks to an application process is
determined by the following factors:
§ The mapping to model port blocks of model implementations that are
assigned to application processes.
§ The manual assignment of function blocks to application processes via
function block properties. Manual assignment is only supported by certain
function blocks, such as the Ethernet Setup function block.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Ensure that the function blocks used to output the UDP datagrams
of the replayed data stream reside in the same application process according to
the factors described above.

Function block: Unsupported The specified value for the Number of angle sequence triggers property
number of angle sequence exceeds the valid range.
triggers
The number of angle sequence triggers must be within the range 1 … 72.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify a value for the
Number of angle sequence triggers property in the valid range.

Function block: Unsupported The specified value for the Number of signals property exceeds the possible
number of signals value range of the assigned hardware resource.

The function block synchronously generates up to 32 PWM signals. You specify

the number of non-inverted signals with the Number of signals property. If you
use inverted signals, the inverted PWM signals are automatically added.

174
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, choose one of the following
alternatives:
§ Specify a value for the Number of signals property that matches the max.
number of signals: 32 signals if no inverted signals are generated, otherwise
16 signals.
§ Set the Inverted phase generation property to Disabled.

Function block: Unsupported The setting of at least one property of the CRC, CRC Modify or CRC Value
port settings (CRC, CRC function ports (for example, Initial value) is not supported or outside the
Modify, CRC Value) possible value range.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reduce the specified value for
the related properties with respect to the possible value range.

Function block: Unsupported The setting of at least one property of the Serial_Message - ID or Serial
port settings (id, data) Message - Data function port (for example, Initial value) is outside the possible
value range.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reduce the specified value for
the related properties with respect to the possible value range.

Function block: Unsupported The specified value of at least one property of the related function port exceeds
port settings (noise the possible value range of the assigned hardware resource.
amplitude)

175
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the related properties
that match the value range of the assigned hardware resource.
§ Assign a hardware resource that provides the required value ranges. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Unsupported The reverse crank mode is enabled at the Reverse Crank property but the
reverse crankshaft signal assigned hardware resource does not support the reverse crank mode.

The assigned hardware resource must support evaluating reverse crankshaft

rotation. This is required for using active crankshaft sensors.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Reverse Crank property to
Disabled.
§ Assign a hardware resource that supports the reverse crank mode. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Unsupported The specified buffer size for receiving UART messages is not supported by the
RX buffer size assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, select a buffer size that is
supported by the assigned hardware resource.

Function block: Unsupported The value specified for the Sample period property is outside the valid range
sample period with respect to the specified sequence length.

176
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

If you specify a value of 1 for the Sequence length property, the value for the
Sample period property must be at least 2 µs.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, for example, choose one of the following
alternatives:
§ Specify a value for the Sequence length property that is at least 2.
§ Specify a value for the Sample period property that is at least 2 µs.

Function block: Unsupported One of the three values specified at the Signal gains property is too high with
signal gains respect to the two others.

Each maximum possible signal gain value depends on the other two gain values.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, decrease the highest signal
gain value so that the related normalized signal gain value becomes equal
to or lower than the suggested upper limit for the normalized gains. The
following equation lets you calculate an approximate possible maximum value,
for example, for an excessive signal gaina value:
Max. signal gaina ≤ (Signal gainb + Signal gainc) · 2 — ε (with ε ≈ 0.01)

Function block: Unsupported The assigned hardware resource does not support the specified signal offset
signal offset (current) value for the provided signal.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, set the Signal offset property
to a value within the allowed range.

Function block: Unsupported The assigned hardware resource does not support the specified signal offset
signal offset (voltage) value for the provided signal.

177
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, set the Signal offset property
to a value within the allowed range.

Function block: Unsupported One or more of the values specified at the Signal offsets property are outside
signal offsets the value range specified by the setting of the Measurement range property.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, perform one of the following
actions:
§ Specify signal offset values that match the range specified by the setting of the
Measurement range property.
§ Change the setting of the Measurement range property so that the resulting
range covers the specified offset values.

Function block: Unsupported The setting for the Signal type property is not supported by the assigned
signal type hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a setting for the Signal type
property that is supported by the assigned hardware resource.
§ Assign a hardware resource that provides the specified setting. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Unsupported The product of Sequence length and Sample period property settings exceeds
sequence duration the maximum sequence duration. The maximum sequence duration must be
equal to or less than 1 s.

178
ConfigurationDesk Conflicts May 2024
Function Block Conflicts

This conflict can only occur if Sequence trigger source property is set to
Model task and the Sample trigger source property is set to Time (sequence-
aligned).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, choose one of the following
alternatives:
§ Reduce the values for the Sequence length property and/or the Sample
period property.
§ Change the trigger source settings (Sequence trigger source and Sample
trigger source), to another supported combination. Refer to Specifying
Trigger Sources (Voltage Signal Capture - ADC Type 4) (ConfigurationDesk I/O
Function Implementation Guide ).

Function block: Unsupported The selected transceiver type is not supported by the assigned hardware
transceiver type resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, select a transceiver type that is
supported by the assigned hardware resource.
§ In the Properties Browser, assign a hardware resource that supports
the required transceiver type. Refer to Hardware Dependencies (UART)
(ConfigurationDesk I/O Function Implementation Guide ).

Function block: Unsupported The settings specified for the Sequence trigger source property and/or for the
trigger configuration Sample trigger source property are not supported by the assigned hardware
resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

179
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, change the trigger source to a setting
that is supported by the assigned hardware resource.
§ Assign a hardware resource that supports the specified settings. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Function block: Unsupported The configuration of the trigger sources is not supported by the function block.
trigger configuration The conflict occurs in the following cases:
§ Case 1: The function block uses the Model task trigger source for both trigger
sources (Sequence trigger source and Sample trigger source).
§ Case 2: The Model task trigger source is used as Sequence trigger source in
combination with enabled event generation.
§ Case 3: A trigger function is used for both trigger sources (Sequence trigger
source and Sample trigger source) and both trigger sources are assigned to
the same trigger function provider.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, choose one of the following
alternatives depending on the case that causes the conflict:
§ Case 1: Specify a different trigger source than Model task for one of
the trigger source properties (Sequence trigger source or Sample trigger
source).
§ Case 2: Change the Sequence trigger source property to Sequence end or
Trigger function or set the Event generation property to Disabled.
§ Case 3: Assign a different trigger source provider to one of the two trigger
sources (Sequence trigger source or Sample trigger source).

Function block: Unsupported The specified value for the Trigger shift property exceeds the possible value
trigger shift value range of the assigned hardware resource.

The trigger shift value specifies the number of samples to shift a trigger forward
or backward.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

180
ConfigurationDesk Conflicts May 2024
Global Time Domain Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Trigger shift
property that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that supports the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

Function block: Unsupported The specified buffer size for transmitting UART messages is not supported by the
TX buffer size assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, select a buffer size that is
supported by the assigned hardware resource.

Global Time Domain Conflicts

Global time domain: Conflicting communication matrix elements are assigned to a bus configuration.
Duplicate domain ID on For two or more assigned global time domains of one channel, the
channel (bus configuration) communication matrix specifies identical domain IDs.

The communication matrix must specify a unique domain ID for each global time
domain of one channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

181
May 2024 ConfigurationDesk Conflicts
Conflicts

Global time domain: A communication matrix specifies identical domain IDs for two or more global
Duplicate domain ID on time domains of one channel.
channel (communication
The communication matrix must specify a unique domain ID for each global time
matrix)
domain of one channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Global time domain: Invalid A conflicting communication matrix element is assigned to a bus configuration.
combination of checksum For an assigned global time domain, the communication matrix specifies the
validation setting and data ID following settings:
lists resulting in default code § The CRC validation property of a time slave is set to CRC optional, i.e., if
(bus configuration) time synchronization is CRC-secured, time synchronization will be validated.
§ The Synchronization message data IDs and/or Follow-up message data
IDs properties are not specified, or a specified value is invalid.

If time synchronization is CRC-secured and validated, the communication matrix

must specify a 16-bit vector for the Synchronization message data IDs and
Follow-up message data IDs properties. Each vector element must be in the
range 0 … 255.

If you do not resolve this conflict, default code is generated, i.e., the run-time
behavior depends on whether time synchronization is CRC-secured:
§ Time synchronization is not CRC-secured: No data IDs are required. Therefore,
the conflicting communication matrix settings do not affect the processing of
the received time synchronization information and the time base of the time
slave can be synchronized.
§ Time synchronization is CRC-secured: The run-time behavior depends on
whether partial validation is enabled for the time slave:
§ Partial validation disabled: The received time synchronization information is
not processed and the time base of the time slave is not synchronized.

182
ConfigurationDesk Conflicts May 2024
Global Time Domain Conflicts

If the GTS Validation feature is added to the affected RX global time

domain, the related bits of the Result function port are set to 1.
§ Partial validation enabled: The conflicting communication matrix settings are
ignored. The received time synchronization information is processed and the
time base of the time slave can be synchronized.
For more information on partial validation and the GTS Validation feature,
refer to:
§ Bus Manager in ConfigurationDesk: Accessing Validity Checks for Time
Synchronization Messages (ConfigurationDesk Bus Manager Implementation
Guide ).
§ Bus Manager (stand-alone): Accessing Validity Checks for Time
Synchronization Messages (Bus Manager (Stand-Alone) Implementation
Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

Global time domain: Invalid A communication matrix specifies the following settings for a global time
combination of checksum domain:
validation setting and data ID § The CRC validation property of a time slave is set to CRC optional, i.e., if
lists resulting in default code time synchronization is CRC-secured, time synchronization will be validated.
(communication matrix) § The Synchronization message data IDs and/or Follow-up message data
IDs properties are not specified, or a specified value is invalid.

If time synchronization is CRC-secured and validated, the communication matrix

must specify a 16-bit vector for the Synchronization message data IDs and
Follow-up message data IDs properties. Each vector element must be in the
range 0 … 255.

183
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Global time domain: Invalid A conflicting communication matrix element is assigned to a bus configuration.
combination of checksum For an assigned global time domain, the communication matrix specifies the
validation setting and data ID following settings:
lists resulting in no code (bus § Time synchronization is CRC-secured and validated, i.e:
configuration) § The CRC-secured property of a time master is set to CRC supported.
§ The CRC validation property of a time slave is set to CRC validated.
§ The Synchronization message data IDs and/or Follow-up message data
IDs properties are not specified, or a specified value is invalid.

If time synchronization is CRC-secured and validated, the communication matrix

must specify a 16-bit vector for the Synchronization message data IDs and
Follow-up message data IDs properties. Each vector element must be in the
range 0 … 255.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

184
ConfigurationDesk Conflicts May 2024
Global Time Domain Conflicts

Global time domain: Invalid A communication matrix specifies the following settings for a global time
combination of checksum domain:
validation setting and data § Time synchronization is CRC-secured and validated, i.e:
ID lists resulting in no code § The CRC-secured property of a time master is set to CRC supported.
(communication matrix)
§ The CRC validation property of a time slave is set to CRC validated.
§ The Synchronization message data IDs and/or Follow-up message data
IDs properties are not specified, or a specified value is invalid.

If time synchronization is CRC-secured and validated, the communication matrix

must specify a 16-bit vector for the Synchronization message data IDs and
Follow-up message data IDs properties. Each vector element must be in the
range 0 … 255.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Global time domain: A conflicting communication matrix element is assigned to a bus configuration.
Invalid property values (bus For an assigned global time domain, the communication matrix specifies at least
configuration) one of the following settings:
§ The domain ID is not specified or a specified domain ID is invalid.
§ The length of the related frame and/or general-purpose PDU is not specified or
a specified length is invalid.

For each global time domain, the communication matrix must specify a domain
ID, and a length for the related frame and general-purpose PDU. The specified
values must be in the following range:
§ Domain ID: 0 … 15
§ Frame/PDU length: 8 bytes or 16 bytes

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

185
May 2024 ConfigurationDesk Conflicts
Conflicts

element. Alternatively, set the bus configuration's Is assigned property to

False to remove all conflicting elements in one step.
Depending on the type of the conflicting element, related elements are
removed as well, e.g., all ISignals of a conflicting ISignal IPDU.
§ If you need the conflicting element in the executable application, choose one
of the following alternatives:
§ Resolve the conflict only for the active ConfigurationDesk application:
Specify a valid value for the Length property of the frame and/or PDU,
for example, in the Conflicts Viewer. This changes the communication
matrix in the active ConfigurationDesk application and all element instances
in all bus configurations of the application. The originally imported
communication matrix remains unchanged.

Note

This resolves the conflict only if the communication matrix specifies a

valid domain ID.

§ Resolve the conflict by correcting the original communication matrix. Refer

Global time domain: A communication matrix specifies at least one of the following settings for a
Invalid property values global time domain:
(communication matrix) § The domain ID is not specified or a specified domain ID is invalid.
§ The length of the related frame and/or general-purpose PDU is not specified or
a specified length is invalid.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify a valid value for the Length property of the frame and/or PDU, for
example, in the Conflicts Viewer. This changes the communication matrix
in the active ConfigurationDesk application and all element instances in all

186
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

bus configurations of the application. The originally imported communication

matrix remains unchanged.

Note

This resolves the conflict only if the communication matrix specifies a valid
domain ID.

Hardware Resource Assignment Conflicts

HW resource assignment: The assigned channel is not valid due to channel dependencies.
Invalid channel assignment
For example, the channel's location must be related to the location of another
channel (for example, channel x must be located next to channel y).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reassign the related channels
to match the required dependency, such as the channel locations.

HW resource assignment: The assigned channel is not valid due to channel dependencies.
Invalid channel assignment
For example, the channel's location must be related to the location of another
(by constraint(s))
channel (for example, channel x must be located next to channel y).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reassign the related channels
to match the required dependency, such as the channel locations.

187
May 2024 ConfigurationDesk Conflicts
Conflicts

HW resource assignment: The required hardware settings (port and/or channel specification) for a Gigalink
Invalid HW assigned to function block are not done completely.
Gigalink function
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, specify the Gigalink number
(Gigalink port) and the Channel number to be used for signal transmission.
Note that, internally, SCALEXIO provides up to four Gigalink ports, but only one
of them (default: port number four) is available on the SCALEXIO backplane.
For further information, refer to Configuring the Basic Functionality (Gigalink)
(ConfigurationDesk I/O Function Implementation Guide ).

HW resource assignment: A Gigalink function block is assigned to a processing unit application to which a
Invalid platform assigned for MicroAutoBox III processor board is assigned.
Gigalink function
MicroAutoBox III processor boards do not support Gigalink communication.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Assign a hardware resource that is not associated with a MicroAutoBox III to
the relevant processing unit application.
§ Delete the Gigalink function block from the ConfigurationDesk application.

HW resource assignment: The specified value for the resolution is outside the possible value range of the
Invalid resolution value assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, change the values to match the value
range of the assigned hardware resource.

188
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The settings of the Maximum message count and Nibbles per message
Invalid settings for Maximum properties result in a number of nibble pulses that exceeds the maximum number
message count and Nibbles of pulses that is supported by the assigned hardware resource.
per message
The expected number of pulses must not exceed the maximum supported
number of pulses and is calculated as follows:
§ If the Pause pulse mode property is set to Enabled: Maximum expected
number of nibble pulses = (2 + Nibbles per message) x Maximum message
count.
§ If the Pause pulse mode property is set to Disabled: Maximum expected
number of nibble pulses = (1 + Nibbles per message) x Maximum message
count.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reduce the settings of the
Maximum message count property and/or the Nibbles per message property
to drop below the maximum number of nibble pulses supported by the assigned
hardware resource.

HW resource assignment: The setting of the Signal reference property is not supported by the assigned
Invalid signal reference hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a setting for the Signal
reference property that is supported by the assigned hardware resource.
§ Assign a hardware resource that supports the required signal reference. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The Ethernet modules that are installed to the assigned Ethernet board have
Mismatching Ethernet Switch been changed. Therefore, the configured Ethernet ports are not compatible with
ports the PHYs of the assigned hardware resource.

189
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Properties Browser, assign an Ethernet switch that provide

the PHYs for the configured Ethernet switch ports.

HW resource assignment: This conflict is generated for custom function blocks in the following cases:
Missing channel set or § At least one electrical interface unit of the function block is not assigned to a
channel assignment channel set.
§ For an electrical interface unit with an assigned channel set, at least one
channel request is not assigned.

ConfigurationDesk determines the types and number of channels required for

a function block according to the assigned channel set, the function block
features, the block configuration and the required physical ranges. The required
channels are called channel requests. For more basics, refer to Basics on
Hardware Resource Assignment (ConfigurationDesk Real-Time Implementation
Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, for example, assign a channel set to

the function block and/or assign a channel to each channel request of the
function block. For instructions on assigning them via the Properties Browser ,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The function block is assigned to a hardware resource which is not connected
Missing connection to a (directly or indirectly) to a processing unit (for example, SCALEXIO Processing
processing unit Unit or DS6001 Processor Board).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

190
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

Remedy Choose one of the following alternatives depending on your

hardware constellation:
§ If your hardware topology contains not a processing unit: Extend the hardware
topology by adding a processing unit to the system. For instructions, refer
to How to Extend Existing Hardware Topologies (ConfigurationDesk Real-Time
Implementation Guide ).
§ Specify a connection to a processing unit via the Uplink or Downlink
properties. These hardware properties are available for IOCNET Routers and
IOCNET Link Boards. For information on accessing them, refer to How to
Access Hardware Properties (ConfigurationDesk Real-Time Implementation
Guide ). For basics on the IOCNET connections in a SCALEXIO system, refer
to Network Concept (SCALEXIO Hardware Installation and Configuration ).
§ Replace the hardware topology by scanning a registered hardware system,
which provides the required connections to a processing unit. For instructions,
refer to How to Import a Hardware Topology (ConfigurationDesk Real-Time
Implementation Guide ).
§ Assign a hardware resource that is connected directly or indirectly to a
processing unit. For instructions, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).

HW resource assignment: The function block references a feature provider, for example, an Angular Clock
Missing or invalid resource Setup function block, which has no or an invalid hardware resource assigned to
assignment for referenced its channel request.
feature provider
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, select a suitable feature provider that
already has assigned hardware resources to its channel request.
§ In the Conflicts Viewer, for example, assign a hardware resource to the
referenced feature provider, for example a suitable angle unit to the Angular
Clock Setup function block.

HW resource assignment: Two or more function blocks access channels of the same I/O module and are
Multiple application processes assigned to different application processes.
connected
Some I/O modules of the MicroAutoBox III require all function blocks accessing
their channels to be assigned to the same application process.

191
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Assign the relevant function blocks to the same application process.
A function block is implicitly assigned to an application process via:
§ Its mapping lines to model port blocks of model implementations that are
assigned to application processes.
§ The assignment of its I/O events to tasks that are assigned to application
processes.
§ The hardware assignment: A function block must have a direct or indirect
hardware connection to the processing hardware.

HW resource assignment: A channel is assigned to more than one channel request in your
Multiple assignments to ConfigurationDesk application.
channel requests
If the channel is already assigned to the request of another function block, it's
name is displayed in parentheses.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, assign a channel to the

channel request that is not yet used. Unused channels are displayed in black
letters.
If the assigned channel set does not provide unused channels, you can assign
another channel set to the function block. For instructions, refer to How To
Assign Hardware Resources via Function Block Properties (ConfigurationDesk
Real-Time Implementation Guide ).

HW resource assignment: The channel sets assigned to a function block which contains several electrical
Multiple boards assigned interface units are located on different I/O boards.

For this specific function block, all hardware resources assigned must be located
on the same I/O board.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

192
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

Remedy Assign hardware resources from the same I/O board to all the
electrical interface units of the function block. For instructions, refer to How
To Assign Hardware Resources via Function Block Properties (ConfigurationDesk
Real-Time Implementation Guide ).

Hardware resource The same Ethernet switch port is assigned by multiple function blocks to provide
assignment: Multiple function MACsec functionality. For a valid MACsec configuration, only one function block
blocks assigned to the same must configure the Ethernet switch port.
switch port
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy In the Conflicts Viewer, for example, reassign the function blocks
to different Ethernet switch ports.

HW resource assignment: A channel of the same Gigalink port (Gigalink number) is used for signal
Multiple functions assigned to transmission by more than one Gigalink function block in your application.
the same Gigalink channel
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, change the Channel number
and/or Gigalink number properties to a combination that is not yet used.
Note that, internally, SCALEXIO provides up to four Gigalink ports, but only one
of them (default: port number four) is available on the SCALEXIO backplane.
For further information, refer to Configuring the Basic Functionality (Gigalink)
(ConfigurationDesk I/O Function Implementation Guide ).

HW resource assignment: No The assigned hardware resource does not support capturing of angle positions.
angle position provided
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

193
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, perform one of the following steps
depending on the related function block:
§ Set the Capture angle position property to Disabled.
§ At the Feature activator property, disable Capture angle positions.
§ Assign a hardware resource to the function block that supports capturing of
angle positions. For instructions, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).

HW resource assignment: Too In a ConfigurationDesk application including angle-based signal processing, too
many connected master APUs many slave APU to master APU connections exist for a hardware resource.

Hardware resources with slave APUs (for example, the DS2621 Signal Generation
Board with 1 slave APU or the DS2680 I/O Unit with 6 slave APUs) must not be
connected to more master APUs than slave APUs are available.

The following example shows how connections between a single slave APU and
two master APUs are established, causing the conflict:
§ A channel of a DS2621 Signal Generation Board is assigned to a Crank/Cam
Current Sink function block.
§ A different channel from the same board is assigned to a different Crank/Cam
Current Sink function block.
§ Each Crank/Cam Current Sink function block is assigned to a different
Engine Simulation Setup block via Assigned simulation setup property.
§ Each Engine Simulation Setup function block is assigned to a different
Angular Clock Setup function block via Assigned master APU provider
property.
§ Two angle units are assigned to the Angular Clock Setup function blocks via
hardware resource assignment.
Now connections from one slave APU (on the DS2621) to two master APUs
(angle units) have been established and the conflict is generated.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, assign different hardware

resources to the involved function blocks.

HW resource assignment: Too In a ConfigurationDesk application, too many function blocks of the same type
many functions requesting are assigned to the same I/O board.
same type of resource
Some I/O boards support several function block types only with a limited
number of function blocks. This number is lower than the number of provided

194
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

I/O channels. For example, the DS6202 Digital I/O Board allows the following
maximum number of function blocks to be assigned to the I/O board:
§ 6 Digital Incremental Encoder In function blocks
§ 6 Digital Incremental Encoder Out function blocks
§ 16 Digital Pulse Capture function blocks
§ 16 Wavetable Digital Out function blocks
§ 16 Angular Wavetable Digital Out function blocks
§ 16 Waveform Digital Out function blocks
§ 4 Digital Pulse Out function blocks
§ 8 SENT In function blocks
§ 8 SENT Out function blocks

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Assign hardware resources from a different I/O board to the involved
function blocks.

HW resource assignment: Too One of the following cases apply:

many instances of function § Too many function blocks of the same type are assigned to the same
type processing unit application.
For example, a maximum of 64 Non-Volatile Memory Access function blocks
is supported for one processing unit application.
§ The function block is implicitly assigned to a processing unit (via processing
unit application) that is not supported by the related function block type.
For example, the Temperature System Monitoring function block type does
not support the DS6001 Processor Board, or the SCALEXIO Processing Unit.
This type only supports the DS1403 Processor Board, i.e., the processing unit
of the MicroAutoBox III.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives depending on the case

that causes the conflict:
§ Reduce the number of function blocks that are assigned to the related
processing unit application.
§ Use the function block only in combination with a processing unit that is
supported by the function block type.

195
May 2024 ConfigurationDesk Conflicts
Conflicts

HW resource assignment: Too The specified number of imported and default wavetables exceeds the maximum
many wavetables value supported by the assigned hardware resource.

The I/O board memory to store wavetables limits the total number of wavetables
that can be referenced by the Crank/Cam and Angular Wavetable function
blocks.

The total number of wavetables per I/O board is limited as follows:

§ DS2680 I/O Unit: Max. 24 wavetables.
§ DS2621 Signal Generation Board: Max. 12 wavetables.
§ DS6101 Multi-I/O Board: Max. 12 wavetables.
§ DS6202 Digital I/O Board: Max. 16 function blocks with up to 4 wavetables
per function block.
§ DS6241 D/A Board: Max. 12 wavetables.

A wavetable that is referenced N times by different Crank/Cam or Angular

Wavetable function blocks is stored N times in the wavetable memory. Default
wavetables for function blocks without imported wavetable files are stored N
times in the wavetable memory.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Decrease the total number of wavetables with respect to the limit of the
assigned hardware resource via the Imported wavetable files property.
§ If you use several function blocks that reference wavetables in your
application, assign channel sets from different I/O boards to some function
blocks.
§ Assign a hardware resource that supports the specified number of wavetables.
For instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: A function block is assigned to a hardware resource which is no longer available
Unresolved HW resource in the hardware topology.
assigned
The hardware resource was assigned while it was available in the hardware
topology. However, the hardware topology of the application was changed
and the current hardware topology does not contain the hardware resource (=
missing or unresolved resource).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

196
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

Remedy Choose one of the following alternatives:

§ Add the missing hardware to the hardware topology.
§ In the Conflicts Viewer, for example, assign a different available hardware
resource. Note that assigning a different hardware resource may introduce
wiring conflicts, so the external cable harness must be recalculated.

HW resource assignment: The assigned hardware resource does not provide an analog low-pass filter.
Unsupported analog lowpass
You can use the analog anti-aliasing (low-pass) filter, for example, to reduce
filter feature
signal noise.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Analog low-pass filter
property to Disabled.
§ Assign a hardware resource that provides an analog low-pass filter for
input signals. For instructions, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).

HW resource assignment: The selected transceiver type and/or assigned hardware resource do not support
Unsupported CAN FD mode the CAN FD mode.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the CAN FD mode property to
Disabled.
§ In the Conflicts Viewer, for example, select a Transceiver type that supports
the CAN FD mode.
§ Assign a hardware resource that supports the CAN FD mode. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: Current measurement is not supported by the assigned hardware resource.
Unsupported current
With the current measurement feature, you can measure currents via an
measurement feature
additional function port during run time.

197
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Current measurement
property to Disabled.
§ Assign a hardware resource that provides current measurement. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified values for one or more of the current values at the electrical
Unsupported current value(s) interface (for example, Data pulse current) are outside the possible value range
of the assigned hardware resource.

The value range for specific properties changes depending on the assigned
hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy The Conflicts Viewer shows the range of possible values in the
Possible Values column.
Choose one of the following alternatives:
§ In the Conflicts Viewer, for example, change the values to match the value
range of the assigned hardware resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Current tooth or the Current gap property exceeds
Unsupported current values the valid value range of the assigned hardware resource.
(current tooth and current
The properties let you specify the current that is generated when a crankshaft
gap)
tooth or a camshaft marker is detected (wavetable value > 0.0).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

198
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Current tooth or
Current gap property that matches the value range of the assigned hardware
resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The setting of the Data width property exceeds the maximum available data
Unsupported data width width for the non-volatile memory of the related processing hardware.

The maximum value for the data width of non-volatile memory of

MicroAutoBox III, MircroLabBox II, SCALEXIO LabBox, SCALEXIO AutoBox, and
SCALEXIO Processing Units is 4,096.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reduce the setting of the
Data width property to a value that is supported by the related processing
hardware.

HW resource assignment: The specified value for the Deadband property exceeds the possible value range
Unsupported deadband value of the assigned hardware resource.

A deadband between the rising and falling edges of the generated PWM signal
and its inverted PWM signal avoids shoot through currents on a connected half
bridge.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Deadband
property that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

199
May 2024 ConfigurationDesk Conflicts
Conflicts

HW resource assignment: The assigned hardware resource does not provide the use of digital filters.
Unsupported digital filter
You can use digital filters, for example, to reduce signal noise. smooth the input
feature
signal or to reduce signal noise, or to adapt the signal bandwidth to a specific
model sample frequency in order to avoid aliasing problems.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Digital filter property to
Disabled.
§ Assign a hardware resource that provides the use of digital filters for
input signals. For instructions, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).

HW resource assignment:
The specified value for the Edge count property exceeds the possible value
Unsupported edge count
range of the assigned hardware resource. The property lets you specify the
number of detected edges after which an event is generated.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Edge count
property that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that supports the required edge count value. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The assigned hardware resource supports only falling edge detection.
Unsupported edge type
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

200
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Edge type property to Falling.
§ Assign a hardware resource that supports rising edge detection. Refer
to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: A value specified at the Data Vector function port is not supported by the
Unsupported entry in Data assigned hardware resource.
Vector
The value range for specific properties at the Data Vector function port,
for example, the Initial value property, changes depending on the assigned
hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

HW resource assignment: The specified value for the Event delay property exceeds the possible value
Unsupported event delay range of the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Event delay
property that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Event downsampling property exceeds the possible
Unsupported event value range of the assigned hardware resource.
downsampling

201
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Event
downsampling property that matches the value range of the assigned
hardware resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: Event generation is not supported by the assigned hardware resource.
Unsupported event
With event generation you can generate I/O events that you can use in an
generation feature
executable application to trigger a task.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Event generation property to
Disabled.
§ Assign a hardware resource that provides event generation. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The failure simulation feature is not supported by the assigned hardware
Unsupported failure resource.
simulation feature
If you use failure simulation for the signals in your function block, you can
control the failure simulation with the experiment software.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Failure simulation property to
Not required.

202
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

§ Assign a hardware resource that provides failure simulation for its hardware
channels. For instructions, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).

HW resource assignment: The assigned Ethernet controller does not support at least one of the following
Unsupported feature features requested by the communication controllers of a bus simulation
container (BSC):
§ Restbus simulation implemented with the Ethernet Configuration Package
§ SOME/IP
§ Double VLAN tagging

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – ✓

Remedy In the Conflicts Viewer, for example, assign an Ethernet controller

to the Ethernet Setup function block that supports the requested features.
For an overview of the Ethernet controllers and the supported features, refer
to Hardware Dependencies (Ethernet Setup) (ConfigurationDesk I/O Function
Implementation Guide ).

HW resource assignment: The feedthrough mode is not supported by the assigned hardware resource.
Unsupported feedthrough
For information on the hardware resources that support the feedthrough mode,
refer to Hardware Dependencies (FlexRay) (ConfigurationDesk I/O Function
Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, disable the feedthrough mode by
setting the Feedthrough mode property to False.
§ Assign a hardware resource that provides the feedthrough mode. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: Monitoring electronic fuses is not supported by the assigned hardware resource.
Unsupported fuse feature

203
May 2024 ConfigurationDesk Conflicts
Conflicts

The Configurable fuse property lets you enable the control of the electronic
fuses. Then, you can monitor the state of the electronic fuses and reset them
(after removing the failure) in your experiment software.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Configurable fuse property to
Not required.
§ Assign a hardware resource that provides electronic fuses to be monitored. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: Galvanic isolation is not supported by the assigned hardware resource.
Unsupported galvanic
You can identify a DS2680 I/O Unit which supports galvanic isolation by the
isolation feature
Galvanic isolation property.

You can access it as follows: In the Hardware Resource Browser navigate the
hardware tree of the SCALEXIO system to the Analog Out 2 item (via DS2680
I/O Unit - DS2680 I/O Module). If the Galvanic isolation property has the
Galvanic isolated or the Switchable setting, the DS2680 supports this feature.

Note that if you create a hardware topology from scratch, ConfigurationDesk

adds a new DS2680 I/O Unit to the topology that supports switchable galvanic
isolation. Make sure that the galvanic isolation support of the DS2680 in your
ConfigurationDesk application corresponds to the DS2680 in your SCALEXIO
system, which is displayed in the Platform Manager. In the Platform Manager,
you can also use the relevant property of the Analog Out 2 channel type to
check the board's support of galvanic isolation.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Electrical interface selection
property to Internal load (non-isolated reference).
§ Assign a hardware resource that provides galvanic isolation. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

204
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

HW resource assignment: The specified setting for the Generation mode property is not supported by the
Unsupported generation assigned hardware resource.
mode
Enabling Generation mode allows the simulation of a reverse crank sensor
signal. For general information on the direction sensitive (reverse) crank
sensor signal, refer to Basics on Reverse Crankshaft Signal Generation
(ConfigurationDesk I/O Function Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Generation mode property to
Disabled.
§ Assign a hardware resource that supports the generation mode. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Idle value property exceeds the possible value range
Unsupported idle value of the assigned hardware resource.

The Idle value specifies the signal level when no waveform is generated.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Idle value
property that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified setting for the Interface type property is not supported by the
Unsupported interface type assigned hardware resource.

You have to specify the required input circuit or output circuit (= interface
type) for the signal that is connected to the function block. This helps you to
assign a suitable channel set of the dSPACE real-time hardware, because the
associated channel types support different potentials. For example, the Flexible
In 1 channel type is galvanically isolated to the ground potential of the dSPACE
real-time hardware, so you can connect an individual arbitrary potential. For

205
May 2024 ConfigurationDesk Conflicts
Conflicts

the Flexible In 2 or Digital In 1 channel types, the interface type setting

has to be Ground-based, because the Reference signal port is hard-wired
to the internal ground of the dSPACE real-time hardware. For basics, refer to
Specifying the Circuit Type for Voltage Input Signals (ConfigurationDesk I/O
Function Implementation Guide ) or Specifying the Circuit Type for Analog
Output Signals (ConfigurationDesk I/O Function Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

HW resource assignment: This conflict occurs in one of the following cases:

Unsupported interface type or § Case 1: The setting of the Interface type property is not supported by the
high reference potential assigned hardware resource.
The interface type defines how the digital outputs are driven to get the
required output signal (binary 0 or binary 1). This helps you assign a suitable
channel set of the dSPACE real-time hardware, because the associated channel
types support different interface types.
For example, the Flexible Out 1 channel type provides channels that are
galvanically isolated from the ground potential of the dSPACE real-time
hardware. Each channel has its own electrical connection and is independent
of the other channels. This allows the connection of a potential shifted signal.
If the channel type is Digital Out 2, the reference signal is hard-wired to the
internal ground of the dSPACE real-time hardware.
§ Case 2: The setting of the High reference potential property is not
supported by the assigned hardware resource.
A high reference potential only is required, if you want to operate the
digital outputs as high-side switch or in push-pull configuration. Specifying
this property helps you assign a suitable channel set of the dSPACE real-
time hardware, because the associated channel types support different high
reference potentials.
For example, if the channel type is Digital Out 1, the internal VBat of the
dSPACE real-time hardware can be used as high-reference potential. The High
Reference signal port then is not available,

For basics, refer to Configuring Standard Features of the Electrical Interface

(ConfigurationDesk I/O Function Implementation Guide ).

206
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives depending on the case

that causes the conflict:
§ Case 1: In the Conflicts Viewer, for example, specify an interface type for the
Interface type property that is supported by the assigned hardware resource.
§ Case 2: In the Conflicts Viewer, for example, specify a reference potential
for the High reference potential property that is supported by the assigned
hardware resource.
§ Both cases: Assign a hardware resource that supports the required interface
type or the required high reference potential. For instructions, refer to How To
Assign Hardware Resources via Function Block Properties (ConfigurationDesk
Real-Time Implementation Guide ).

HW resource assignment: The assigned Ethernet controller does not support the specified link speed.
Unsupported linkspeed
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy In the Conflicts Viewer, for example, specify a link speed that is
supported by the assigned Ethernet controller.

HW resource assignment: The specified value for the Required current property exceeds the possible
Unsupported maximum value range of the assigned hardware resource.
current
The property lets you specify the required maximum current of the connected
signal of the external device (e.g., ECU). ConfigurationDesk uses the specified
value to calculate the number of hardware channels needed. With this channel
multiplication feature, the max. current of a single hardware channel can be
enhanced. For more details, refer to Specifying Current and Voltage Values
for Channel Multiplication (ConfigurationDesk I/O Function Implementation
Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

207
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Required
current property that matches the value range of the assigned hardware
resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The hardware topology in your active ConfigurationDesk application contains a
Unsupported maximum central FIU hardware which supports failure simulation but this hardware does
current for central FIU not support the specified required current range.
hardware
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Failure simulation property to
Not required.
§ In the Conflicts Viewer, for example, reduce the specified value for the
Required current property with respect to the possible value range of the
central FIU hardware. For example, the DS2680 I/O Unit provides only a
maximum current of 48 A.
§ Extend the hardware topology by adding a central FIU hardware which
provides the required maximum current range. For example, the DS2642 FIU
& Power Switch Board provides a maximum current of 80 A. For instructions,
refer to How to Extend Existing Hardware Topologies (ConfigurationDesk Real-
Time Implementation Guide ).
§ Replace the hardware topology by scanning a registered hardware system,
which contains a central FIU hardware which provides the required maximum
current range. For example, the DS2642 FIU & Power Switch Board provides a
maximum current of 80 A. For instructions, refer to How to Import a Hardware
Topology (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: This conflict is caused if all the following conditions occur:
Unsupported maximum § The Failure simulation property of the electrical interface of the affected
current for central FIU function block is set to Required.
hardware if Short to VBAT § The Short to VBAT property is set to Allowed for at least one signal port of
the function block.
§ No Power Switch function block is instantiated in your active
ConfigurationDesk application or you are using at least one Power Switch
function block whose maximum ampacity is lower than the specified
Required current value for the affected function block.

208
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

The maximum ampacity for "Short to VBAT" failures at function blocks with
channel multiplication depends on the channel type as follows:
§ Power Switch 1 (on DS2642): Number of channels used * 8 A
§ Power Switch 2 (on DS2680): 19.2 A

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Choose one of the following alternatives:

§ Add a Power Switch function block to the signal chain and assign a suitable
hardware resource to the function block.
§ In the Conflicts Viewer, for example, set the Short to VBAT property to Not
allowed for all signal ports of the affected function block.
§ In the Conflicts Viewer, for example, set the Failure simulation property to
Not required for the affected function block.
§ In the Conflicts Viewer, for example, reduce the specified value for the
Required current property with respect to your minimum required value
range.
§ Extend the hardware topology by adding a central FIU hardware which
provides the required maximum current range. For example, the DS2642 FIU
& Power Switch Board provides a maximum current of 80 A. For instructions,
refer to How to Extend Existing Hardware Topologies (ConfigurationDesk Real-
Time Implementation Guide ).
§ Replace the hardware topology by scanning a registered hardware system,
which contains a central FIU hardware which provides the required maximum
current range. For example, the DS2642 FIU & Power Switch Board provides a
maximum current of 80 A. For instructions, refer to How to Import a Hardware
Topology (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Required voltage property exceeds the possible
Unsupported maximum value range of the assigned hardware resource.
voltage
The property lets you specify the required maximum voltage of the connected
signal of the external device (e.g., ECU). ConfigurationDesk uses the specified
value to calculate the number of hardware channels needed. With this channel
multiplication feature, the max. voltage of a single hardware channel can be
enhanced. For more details, refer to Specifying Current and Voltage Values
for Channel Multiplication (ConfigurationDesk I/O Function Implementation
Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

209
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Required
voltage property that matches the value range of the assigned hardware
resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value(s) for the Measure delay time property/ies exceed(s) the
Unsupported measurement possible value range of the assigned hardware resource.
delay time(s)
The measurement delay time lets you define the delay time for starting
measurement after a trigger occurs.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify value(s) for the Measure delay
time property/ies that match(es) the value range of the assigned hardware
resource.
§ Assign a hardware resource that provides the specified value(s). For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Minimum frequency property exceeds the possible
Unsupported minimum value range of the assigned hardware resource.
frequency
For a PWM/PFM In function block, for example, the minimum frequency defines
the minimum measurable frequency for zero frequency detection of the input
signal.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Minimum
frequency property that matches the value range of the assigned hardware
resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

210
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

HW resource assignment: The specified value for the Minimum pulse duration property exceeds the
Unsupported minimum pulse possible value range of the assigned hardware resource.
duration
This property lets you specify a filter that evaluates the pulse duration. Pulses that
have a duration less than the specified value are ignored.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Minimum pulse
duration property that matches the value range of the assigned hardware
resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Minimum PWM frequency property exceeds the
Unsupported minimum PWM possible value range of the assigned hardware resource.
frequency
The minimum PWM frequency is used to detect the absence of the input signal
and initiate further current measurements independently from a PWM voltage
signal. Frequencies lower than specified are detected as 0 Hz.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Minimum PWM
frequency property that matches the value range of the assigned hardware
resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The noise generation feature is enabled for the function block but not supported
Unsupported noise by the assigned hardware resource.
generation feature
With the noise generation feature, you can disturb the output signal with
additional noise.

211
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Noise Generation property to
Disabled.
§ Assign a hardware resource that supports the noise generation feature. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Number of bits property exceeds the possible value
Unsupported number of bits range of the assigned hardware resource.

The number of bits equals the digital input lines representing the input signal.
If the specified Number of bits property exceeds the number of hardware
channels you can allocate, ConfigurationDesk creates the channels but does not
connect them to the hardware.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Number of
bits property that matches the max. number of channels (= digital input lines)
provided by the assigned hardware resource.
§ Assign a hardware resource that provides the required number of channels
(= digital input lines). For instructions, refer to How To Assign Hardware
Resources via Function Block Properties (ConfigurationDesk Real-Time
Implementation Guide ).

HW resource assignment: The settings of the Nibbles per message and Maximum message count
Unsupported number of properties result in a number of nibbles that is not supported by the message
nibbles buffer of the assigned hardware resource.

The maximum number of nibbles that are supported by the message buffer is 84
nibbles. The number is calculated as follows:
§ If the Pause pulse mode property is set to Disabled:
Maximum number of nibbles = (Nibbles per message + 1) · Maximum
message count

212
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

§ If the Pause pulse mode property is set to Enabled:

Maximum number of nibbles = (Nibbles per message + 2) · Maximum
message count

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In the Conflicts Viewer, for example, reduce the setting of the
Nibbles per message property or the Maximum message count property. Use
the error description above to decide on the appropriate settings.

HW resource assignment: The specified value for the Nibbles per message property exceeds the possible
Unsupported number of value range of the assigned hardware resource.
nibbles
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Nibbles
per message property that matches the maximum value supported by the
assigned hardware resource.
§ Assign a hardware resource that supports the required number of nibbles. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value of at least one property of the related function port exceeds
Unsupported port settings the possible value range of the assigned hardware resource.
(amplitude)
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

213
May 2024 ConfigurationDesk Conflicts
Conflicts

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the related properties
that match the value range of the assigned hardware resource.

214
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

§ Assign a hardware resource that provides the required value ranges. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value of at least one property of the related function port exceeds
Unsupported port settings the possible value range.
(gap width)
The possible value range is 0 pitches ... 255 pitches and can be reduced by the
Pitch count property.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – ✓ – – – –

Remedy In the Conflicts Viewer, for example, choose one of the following
alternatives:
§ Specify a value for the related property/ies that matches the valid value range.
§ Increase the value for the Pitch count property to extend the valid value
range.

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

215
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the related
property/ies that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that provides the required value ranges. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

HW resource assignment: The specified value of at least one property of the related function port exceeds
Unsupported port settings the possible value range of the assigned hardware resource.
(speed)

216
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

217
May 2024 ConfigurationDesk Conflicts
Conflicts

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the related properties
that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that provides the required value ranges. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

HW resource assignment: The assigned hardware resource does not support power wake‑up.
Unsupported power wake‑up
Effects
feature
Abort Warning Generate Generate Abort BSC Warning Abort
Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Power wake‑up property to
Disabled.
§ Assign a hardware resource that supports power wake‑up. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

218
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

HW resource assignment: A value specified for at least one property of the Pulse Delay function port
Unsupported pulse delay (for example, Initial value) exceeds the value range of the assigned hardware
resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Initial value or
Stop value property that matches the value range of the assigned hardware
resource.
§ Assign a hardware resource that supports the required pulse delay value. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Speed pulse width and/or Data pulse width
Unsupported pulse width property exceeds the possible value range of the assigned hardware resource.

Values for the speed pulse width and the data pulse width are given by the
sensor specification of the simulated wheel speed sensor type.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Speed pulse
width and/or Data pulse width property that matches the value range of the
assigned hardware resource.
§ Assign a hardware resource that supports the required pulse width value. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Resistance property exceeds the possible value range
Unsupported resistance of the assigned hardware resource.

This adjustable property lets you enter the end-to-end terminal resistance value
of a potentiometer. It specifies the resistance between the Terminal 1 and the
Terminal 2 signal port.

219
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Resistance
property that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that supports the required resistance value. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The value specified for the Sample period property exceeds the possible value
Unsupported sample period range of the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Sample period
property that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that provides the required value ranges. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Standstill detection speed property exceeds the
Unsupported standstill possible value range of the assigned hardware resource.
detection speed
The adjustable speed value lets you configure a value to detect a minimum
wheel speed. If the input value of the Speed function port falls below the
configured Standstill detection speed value, the function block changes to the
standstill mode with a special output signal.

The Standstill detection speed value is given by the sensor specification of the
simulated wheel speed sensor type.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

220
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Standstill
detection speed property that matches the value range of the assigned
hardware resource.
§ Assign a hardware resource that supports the required speed value. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Threshold property exceeds the possible value range
Unsupported threshold of the assigned hardware resource.

The adjustable threshold lets you configure a level for the input signal to
transform the input signal into binary values.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Threshold
property that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that supports the required threshold value. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Threshold or the Digital threshold property exceeds
Unsupported threshold range the possible value range of the assigned hardware resource.
value
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Threshold or
the Digital threshold property that matches the value range of the assigned
hardware resource.
§ Assign a hardware resource that provides the required value ranges. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

221
May 2024 ConfigurationDesk Conflicts
Conflicts

HW resource assignment: The onboard Ethernet controllers of the following processing hardware do not
Unsupported time support the precision time protocol (PTP):
synchronization feature § SCALEXIO Processing Unit with the Real-Time PC version 1.1
§ DS6001 Processor Board

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Assign an Ethernet controller of an Ethernet board to the function

block, such as a controller of the DS6331-PE or DS6335-CS.

HW resource assignment: The selected transceiver type is not supported by the assigned hardware
Unsupported transceiver resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, set the Transceiver type property to a
transceiver type the assigned hardware resource supports.
§ Assign a hardware resource that supports the selected transceiver type. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Timeout property exceeds the value range of the
Unsupported timeout value assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Timeout
property that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that provides the required timeout value. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

222
ConfigurationDesk Conflicts May 2024
Hardware Resource Assignment Conflicts

HW resource assignment: The specified value for the Trigger delay property exceeds the possible value
Unsupported trigger delay range of the assigned hardware resource.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Trigger delay
property that matches the value range of the assigned hardware resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Trigger downsampling property exceeds the
Unsupported trigger possible value range of the assigned hardware resource.
downsampling
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Trigger
downsampling property that matches the value range of the assigned
hardware resource.
§ Assign a hardware resource that provides the specified value. For instructions,
refer to How To Assign Hardware Resources via Function Block Properties
(ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The specified value for the Trigger Threshold property exceeds the possible
Unsupported trigger value range of the assigned hardware resource.
threshold
The adjustable trigger threshold lets you configure the level of the triggering
voltage input signal, to avoid, for example, the measurement being triggered by
noise.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

223
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, specify a value for the Trigger
Threshold property that matches the value range of the assigned hardware
resource.
§ Assign a hardware resource that supports the required threshold value. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

HW resource assignment: The Tristate property is set to Enabled and one of the following conditions
Unsupported tristate feature holds true:
§ The digital outputs of the function block do not operate in Push-pull
configuration.
§ The assigned hardware resource does not provide the tristate feature.

The tristate feature lets you allow the digital outputs (operated in push-pull
configuration) of a function block to be set into high impedance state.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ If you do not want to support the tristate feature at all:
§ In the Conflicts Viewer, for example, set the Tristate property to Disabled.
§ If you want to support the tristate feature:
§ In the Conflicts Viewer, for example, set the Interface type property to
Push-pull.
§ Assign a hardware resource that supports the tristate feature, for example,
the DS2621, DS2680, or DS2690. For instructions, refer to How To Assign
Hardware Resources via Function Block Properties (ConfigurationDesk Real-
Time Implementation Guide ).

HW resource assignment: The specified number of wavetable values exceeds the possible value range of
Unsupported wavetable size the assigned hardware resource.

A Wavetable function block can reference multiple wavetables. However, the

total number of wavetable values (wavetable size * number of wavetables)
is restricted to a hardware-specific limit. For basics, refer to Basics on Signal
Generation Using Time-Coded Wavetables (ConfigurationDesk I/O Function
Implementation Guide )

224
ConfigurationDesk Conflicts May 2024
Hardware Resource Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ Decrease the total number of wavetable values with respect to the limit of the
assigned hardware resource via the Imported wavetable files property.
For example, the DS2621 Signal Generation Board, provides a limit of up to
1024 wavetable values.
§ Assign a hardware resource that supports the required wavetable value. For
instructions, refer to How To Assign Hardware Resources via Function Block
Properties (ConfigurationDesk Real-Time Implementation Guide ).

Hardware Resource Conflicts

HW resource: Duplicate name The hardware topology of the active ConfigurationDesk application contains
two or more components (for example, SCALEXIO racks, MicroAutoBoxes III,
MicroLabBoxes II, units, I/O boards, processing units, or processor boards) with
the same name.

The names of the hardware systems in the hardware topology must be unique
and the names of the components within a hardware system must also be
unique.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – ✓

Remedy In the Conflicts Viewer, for example, enter unique names for the
hardware systems and/or for the components within a hardware system.

HW resource: Duplicate name Two or more Ethernet controllers or switches with the same name are part of the
same dSPACE hardware in the hardware topology.

The names of Ethernet controllers and switches must be unique. However,

Ethernet controllers or switches of different SCALEXIO Processing Units can use
the same name.

225
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, enter unique names for the
Ethernet controllers and switches.

HW resource: Exceeding The slave APU of an assigned hardware resource does not support the specified
angular speed of assigned I/O maximum speed of the master APU provider. The functionality of function
boards blocks that require angular functionalities is not guaranteed and might lead to
unpredictable results if the supported speed of the virtual engine exceeds the
speed of the slave APU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy Choose one of the following alternatives:

§ Reduce the Maximum speed property setting of the master APU provider to
a value that is supported by all hardware resources and will not be exceeded
by your real-time application. 168000 °/s is supported by all relevant hardware
resources. Keep in mind that the Maximum speed property does not saturate
the speed of the virtual engine.
§ Assign a hardware resource to the function block that fulfill the angular speed
requirement. For instructions, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).

HW resource: No mounted I/O An I/O module is required to provide the I/O interface for the FPGA base board.
module for I/O base board
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose at least one of the following alternatives:

§ In the Hardware Resource Browser, add the missing I/O module to the FPGA
base board.
§ Install an I/O module on the FPGA base board and replace the hardware
topology.

226
ConfigurationDesk Conflicts May 2024
Hardware Unit Slot Conflicts

HW resource: Too many In a ConfigurationDesk application the event generation feature is enabled for
events assigned too many function blocks which all are assigned to the same I/O board. The
number of events exceeds the allowed maximum for the assigned hardware
resource. For example, the DS6101 Multi I/O Board allows only max. 8 events per
board.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, disable Event generation for that
function blocks which do not require the event generation feature.
§ Assign a hardware resource that supports the required number of events or
reassign some function blocks to other I/O boards so you no longer exceed
the maximum number of supported events. For instructions, refer to How To
Assign Hardware Resources via Function Block Properties (ConfigurationDesk
Real-Time Implementation Guide ).

Hardware Unit Slot Conflicts

HW unit slot: Multiple boards One slot of a slot I/O unit is assigned multiple times by different I/O boards.
assigned
A slot of a slot I/O unit can only be used once.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy In the Properties Browser, for example, reassign the boards, so

that every slot is used only once in a slot I/O unit.

HW unit slot: PCIe board in A board with a PCIe connector is assigned to an I/O slot that does not support
non PCIe slot the PCIe standard.

For example, in a SCALEXIO LabBox or in a SCALEXIO AutoBox (if they are

equipped with a DS6001 Processor Board) only the slots 3 ... 7 support the PCIe
standard.

227
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy In the Properties Browser, for example, assign the board with the
PCIe connector to a PCIe I/O slot.

IPDU Conflicts

IPDU: Duplicate J1939 A conflicting communication matrix element is assigned to a bus configuration.
identifier on CAN channel For two or more assigned J1939-compliant IPDUs, the communication matrix
(bus configuration) specifies the following settings:
§ The IPDUs are mapped to the same CAN channel.
§ For at least two of these IPDUs, identical settings are specified for the
following properties:
§ PGN (parameter group number)
§ Source address
§ Destination address

The tuple [PGN; source address; destination address] must be unique for each
J1939-compliant IPDU of one CAN channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

228
ConfigurationDesk Conflicts May 2024
IPDU Conflicts

IPDU: Duplicate J1939 A communication matrix specifies the following settings for two or more J1939-
identifier on CAN channel compliant IPDUs:
(communication matrix) § The IPDUs are mapped to the same CAN channel.
§ For at least two of these IPDUs, identical settings are specified for the
following properties:
§ PGN (parameter group number)
§ Source address
§ Destination address

The tuple [PGN, source address, destination address] must be unique for each
J1939-compliant IPDU of one CAN channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

IPDU: Invalid end-to- A conflicting communication matrix element is assigned to a bus configuration.
end protection profile For an ISignal group of an assigned IPDU, the communication matrix specifies an
or description (bus unsupported or invalid end-to-end protection profile.
configuration)
For the end-to-end protection of ISignal groups contained in IPDUs, the
communication matrix must specify a profile that the Bus Manager supports.
The specified profile must be compliant to the AUTOSAR specifications.

For an overview of the end-to-end protection profiles the Bus Manager supports,
refer to:
§ Bus Manager in ConfigurationDesk: Aspects of End‑to‑End (E2E) Protection for
ISignal Groups (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Aspects of End‑to‑End (E2E) Protection for ISignal
Groups (Bus Manager (Stand-Alone) Implementation Guide ).

If you do not resolve this conflict, default code is generated, i.e., no end-to-end
protection is used for the affected ISignal group. Nevertheless, the ISignal group
and its related IPDU can be transmitted and received at run time.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

229
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

IPDU: Invalid end-to-end A communication matrix specifies an unsupported or invalid end-to-end

protection profile or protection profile for an ISignal group of an IPDU.
description (communication
For the end-to-end protection of ISignal groups contained in IPDUs, the
matrix)
communication matrix must specify a profile that the Bus Manager supports.
The specified profile must be compliant to the AUTOSAR specifications.

For an overview of the end-to-end protection profiles the Bus Manager support,
refer to:
§ Bus Manager in ConfigurationDesk: Aspects of End‑to‑End (E2E) Protection for
ISignal Groups (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Aspects of End‑to‑End (E2E) Protection for ISignal
Groups (Bus Manager (Stand-Alone) Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

IPDU: Invalid event-controlled A conflicting communication matrix element is assigned to a bus configuration.
timing (bus configuration) For an assigned TX IPDU, its ISignals and/or ISignal groups, and the bus
configuration, all of the following applies:
§ For the TX IPDU, the communication matrix does not specify an
event‑controlled timing or at least one setting of a specified event‑controlled
timing is invalid.
§ For an ISignal or ISignal group that is available for the TX IPDU and assigned to
the bus configuration, Transfer property is set to Triggered with repetition
or Triggered on change with repetition.

230
ConfigurationDesk Conflicts May 2024
IPDU Conflicts

§ For the bus configuration, Use transfer property is set to True.

If the use of the transfer property is enabled for a bus configuration and
Transfer property of an ISignal or ISignal group is set to Triggered with
repetition or Triggered on change with repetition, the communication
matrix must specify an event‑controlled timing for the related IPDU. For the
event‑controlled timing, the following settings must be specified:
§ Number of repetitions: 0 … 255
§ Repetition period:
§ Valid value range: 0 … 3,600 seconds
§ If the number of repetitions is 0, the repetition period can be unspecified.

If you do not resolve this conflict, default code is generated, i.e., no

event‑controlled timing is used for the affected TX IPDU. Nevertheless, an ISignal
or ISignal group can trigger a single transmission of the IPDU. Additionally, the
IPDU can be transmitted according to a cyclic timing and by bus configuration
features, such as the PDU Trigger feature.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application. Choose
one of the following alternatives:
§ Remove the conflicting element from the bus configuration: In the Conflicts
Viewer, set the element's Is assigned property to False to remove only this
conflicting element. Alternatively, set the bus configuration's Is assigned
property to False to remove all conflicting elements in one step.
Depending on the type of the conflicting element, related elements are
removed as well, e.g., all ISignals of a conflicting ISignal IPDU.
§ Disable the use of event‑controlled timings for the bus configuration: Select
the bus configuration, for example, in the Bus Configurations table. In the
Properties Browser, set Use transfer property of the bus configuration to
False.
§ If the communication matrix does not specify an event‑controlled timing for
the IPDU, add event‑controlled timing elements to the IPDU. This changes
the communication matrix in the active ConfigurationDesk application and
all element instances in all bus configurations of the application. The
originally imported communication matrix remains unchanged. Refer to:
Bus Manager in ConfigurationDesk: Adding Event‑Controlled Timing
Elements to IPDUs (ConfigurationDesk Bus Manager Implementation
Guide ).
Bus Manager (stand‑alone): Adding Event‑Controlled Timing Elements to
IPDUs (Bus Manager (Stand-Alone) Implementation Guide ).
§ If the communication matrix specifies invalid settings for an event‑controlled
timing of the IPDU, specify valid values for the Number of repetitions
and/or Repetition period properties, for example, in the Conflicts Viewer.

231
May 2024 ConfigurationDesk Conflicts
Conflicts

This changes the communication matrix in the active ConfigurationDesk

application and all element instances in all bus configurations of
the application. The originally imported communication matrix remains
unchanged.
§ Specify a valid value for Transfer property of the affected ISignal or
ISignal group, for example, in the Conflicts Viewer. This changes the
communication matrix in the active ConfigurationDesk application and all
element instances in all bus configurations of the application. The originally
imported communication matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

IPDU: Invalid event-controlled A communication matrix specifies all of the following invalid settings for an IPDU
timing (communication and at least one of its ISignals or ISignal groups:
matrix) § For the IPDU, the communication matrix does not specify an event‑controlled
timing or at least one setting of a specified event‑controlled timing is invalid.
§ For an ISignal or ISignal group that is available for the IPDU, Transfer
property is set to Triggered with repetition or Triggered on change with
repetition.

If Transfer property of an ISignal or ISignal group is set to Triggered with

repetition or Triggered on change with repetition, the communication
matrix must specify an event‑controlled timing for the related IPDU. For the
event‑controlled timing, the following settings must be specified:
§ Number of repetitions: 0 … 255
§ Repetition period:
§ Valid value range: 0 … 3,600 seconds
§ If the number of repetitions is 0, the repetition period can be unspecified.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
§ If the communication matrix does not specify an event‑controlled timing for
the IPDU, add event‑controlled timing elements to the IPDU. This changes
the communication matrix in the active ConfigurationDesk application and
all element instances in all bus configurations of the application. The
originally imported communication matrix remains unchanged. Refer to:
Bus Manager in ConfigurationDesk: Adding Event‑Controlled Timing
Elements to IPDUs (ConfigurationDesk Bus Manager Implementation
Guide ).

232
ConfigurationDesk Conflicts May 2024
IPDU Conflicts

Bus Manager (stand‑alone): Adding Event‑Controlled Timing Elements to

IPDUs (Bus Manager (Stand-Alone) Implementation Guide ).
§ If the communication matrix specifies invalid settings for an event‑controlled
timing of the IPDU, specify valid values for the Number of repetitions
and/or Repetition period properties, for example, in the Conflicts Viewer.
This changes the communication matrix in the active ConfigurationDesk
application and all element instances in all bus configurations of
the application. The originally imported communication matrix remains
unchanged.
§ Specify a valid value for Transfer property of the affected ISignal or
ISignal group, for example, in the Conflicts Viewer. This changes the
communication matrix in the active ConfigurationDesk application and all
element instances in all bus configurations of the application. The originally
imported communication matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

IPDU: Invalid J1939 payload A conflicting communication matrix element is assigned to a bus configuration.
length (bus configuration) For an assigned J1939-compliant IPDU, the communication matrix specifies an
invalid length.

For each J1939-compliant IPDU, the communication matrix must specify a

payload length in the following ranges:
§ J1939‑21: 0 … 1,785 bytes
§ J1939‑22, peer‑to‑peer communication: 0 … 60 bytes
§ J1939‑22, broadcast communication: 0 … 15,352 bytes

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

233
May 2024 ConfigurationDesk Conflicts
Conflicts

Specify a valid value for the Length property, for example, in the
Conflicts Viewer. This changes the communication matrix in the active
ConfigurationDesk application and all element instances in all bus
configurations of the application. The originally imported communication
matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer
to:
Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

IPDU: Invalid J1939 payload A communication matrix specifies an invalid length for a J1939-compliant IPDU.
length (communication
For each J1939-compliant IPDU, the communication matrix must specify a
matrix)
payload length in the following ranges:
§ J1939‑21: 0 … 1,785 bytes
§ J1939‑22, peer‑to‑peer communication: 0 … 60 bytes
§ J1939‑22, broadcast communication: 0 … 15,352 bytes

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

IPDU: Invalid J1939-22 A conflicting communication matrix element is assigned to a bus configuration.
assurance data (bus For an assigned J1939‑22‑compliant IPDU that is transmitted using the Broadcast
configuration) Announce Message (BAM) protocol, the communication matrix specifies one of
the following invalid combinations for the assurance data and the IPDU length:
§ Assurance data type is set to No assurance data and the length of the IPDU
exceeds 15,300 bytes.
§ Assurance data type is set to Cybersecurity (manufacturer‑specific),
Functional safety (manufacturer‑specific), or Cybersecurity and

234
ConfigurationDesk Conflicts May 2024
IPDU Conflicts

functional safety (manufacturer‑specific) and at least one of the following

applies:
§ The length of the IPDU exceeds 15,352 bytes.
§ The assurance data size exceeds 52 bytes.

If a J1939‑22‑compliant IPDU that is transmitted using the BAM protocol

provides no assurance data, the length of the IPDU must be in the range
0 … 15,300 bytes. If such an IPDU provides assurance data, the assurance data
size must be in the range 0 … 52 bytes and the IPDU length must be in the
range 0 … 15,352 bytes.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application. Choose
one of the following alternatives:
§ Remove the conflicting element from the bus configuration: In the Conflicts
Viewer, set the element's Is assigned property to False to remove only this
conflicting element. Alternatively, set the bus configuration's Is assigned
property to False to remove all conflicting elements in one step.
Depending on the type of the conflicting element, related elements are
removed as well, e.g., all ISignals of a conflicting ISignal IPDU.
§ Specify a valid value for the Length, Assurance data type, and/or
Assurance data size properties, for example, in the Conflicts Viewer.
This changes the communication matrix in the active ConfigurationDesk
application and all element instances in all bus configurations of
the application. The originally imported communication matrix remains
unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

IPDU: Invalid J1939-22 A communication matrix specifies one of the following invalid combinations
assurance data for the assurance data and the length of a J1939‑22‑compliant IPDU that is
(communication matrix) transmitted using the Broadcast Announce Message (BAM) protocol:
§ Assurance data type is set to No assurance data and the length of the IPDU
exceeds 15,300 bytes.
§ Assurance data type is set to Cybersecurity (manufacturer‑specific),
Functional safety (manufacturer‑specific), or Cybersecurity and

235
May 2024 ConfigurationDesk Conflicts
Conflicts

functional safety (manufacturer‑specific) and at least one of the following

applies:
§ The length of the IPDU exceeds 15,352 bytes.
§ The assurance data size exceeds 52 bytes.

If a J1939‑22‑compliant IPDU that is transmitted using the BAM protocol

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify a valid value for the Length, Assurance data type, and/or Assurance
data size properties, for example, in the Conflicts Viewer. This changes
the communication matrix in the active ConfigurationDesk application and all
element instances in all bus configurations of the application. The originally
imported communication matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

IPDU: Invalid length A conflicting communication matrix element is assigned to a bus configuration.
of secured IPDU (bus For an assigned secured IPDU, the communication matrix specifies an invalid
configuration) length.

For each secured IPDU, the communication matrix must specify a valid length.
The valid length depends on whether the communication matrix configures the
secured PDU as cryptographic PDU:
§ Secured IPDU configured as cryptographic IPDU:
valid length ≥ (secured PDU header length +
freshness value TX length + authenticator TX length +
message link length)
§ Secured IPDU not configured as cryptographic IPDU:
valid length ≥ (secured PDU header length +
freshness value TX length + authenticator TX length +
authentic IPDU payload length)

236
ConfigurationDesk Conflicts May 2024
IPDU Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

IPDU: Invalid length of A communication matrix specifies an invalid length for a secured IPDU.
secured IPDU (communication
For each secured IPDU, the communication matrix must specify a valid length.
matrix)
The valid length depends on whether the communication matrix configures the
secured IPDU as cryptographic IPDU:
§ Secured IPDU configured as cryptographic IPDU:
valid length ≥ (secured PDU header length +
freshness value TX length + authenticator TX length +
message link length)
§ Secured IPDU not configured as cryptographic IPDU:
valid length ≥ (secured PDU header length +
freshness value TX length + authenticator TX length +
authentic IPDU payload length)

237
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

IPDU: Invalid number of A conflicting communication matrix element is assigned to a bus configuration.
ISignal groups for end-to- For an assigned IPDU, the communication matrix specifies the following settings:
end protected IPDU (bus § An end-to-end protection definition contains one or more references to the
configuration) IPDU.
§ To at least one of these references, the end-to-end protection definition maps
no or more than one ISignal group.

Within an end-to-end protection definition, exactly one ISignal group must be

mapped to one IPDU reference. If the end-to-end protection definition references
an IPDU more than once, one ISignal group must be mapped to each of these
references.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

238
ConfigurationDesk Conflicts May 2024
IPDU Conflicts

§ Correct the setting in the original communication matrix. Refer to:

§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

IPDU: Invalid number of A communication matrix specifies the following settings for an IPDU:
ISignal groups for end- § An end-to-end protection definition contains one or more references to the
to-end protected IPDU IPDU.
(communication matrix) § To at least one of these references, the end-to-end protection definition maps
no or more than one ISignal group.

Within an end-to-end protection definition, exactly one ISignal group must be

mapped to one IPDU reference. If the end-to-end protection definition references
an IPDU more than once, one ISignal group must be mapped to each of these
references.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

IPDU: Invalid J1939 PGN (bus A conflicting communication matrix element is assigned to a bus configuration.
configuration) For an assigned J1939‑compliant IPDU, the communication matrix specifies an
invalid parameter group number (PGN).

For each J1939‑compliant IPDU, the communication matrix must specify a

parameter group number (PGN) in the range 0 … 262,143 (0x00 … 0x3 FF FF).
Moreover, the following conditions must be met:
§ If Broadcast is False, PDU format must be PDU 1.
§ If PDU format is PDU 1, the lowest byte of the PGN must be 0.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

§ If you do not need the conflicting element in the executable application,
remove it from the bus configuration: In the Conflicts Viewer, set the

239
May 2024 ConfigurationDesk Conflicts
Conflicts

element's Is assigned property to False to remove only this conflicting

element. Alternatively, set the bus configuration's Is assigned property to
False to remove all conflicting elements in one step.
Depending on the type of the conflicting element, related elements are
removed as well, e.g., all ISignals of a conflicting ISignal IPDU.
§ If you need the conflicting element in the executable application, correct the
setting in the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

IPDU: Invalid J1939 PGN A communication matrix specifies an invalid parameter group number (PGN) for
(communication matrix) a J1939‑compliant IPDU.

For each J1939‑compliant IPDU, the communication matrix must specify a

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

IPDU: Invalid period A bus configuration is configured as follows:

for J1939‑21 transport § At least one J1939‑21‑compliant IPDU with more than 8 data bytes is assigned
protocol communication (bus to the bus configuration, i.e., a transport protocol is used for the J1939
configuration) communication.
§ For the Timer Event of the task to which the related
BusCfg_MainFunctionFetch [<bus configuration name>] and
BusCfg_MainFunctionDeliver [<bus configuration name>] runnable
functions are assigned, a period of longer than 0.05 s is specified.

If transport protocols are used for J1939‑21 communication, the Timer

Event of the task to which the related BusCfg_MainFunctionFetch
[<bus configuration name>] and BusCfg_MainFunctionDeliver [<bus
configuration name>] runnable functions are assigned should have a period
in the range 0 … 0.05 s.

240
ConfigurationDesk Conflicts May 2024
IPDU Conflicts

If you do not resolve this conflict, default code is generated, i.e., because
the period exceeds 0.05 s, not all of the timing requirements of the
transport-protocol-based J1939‑21 communication might be fulfilled at run time.
Therefore, timeouts might occur.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

§ Remove the conflicting PDUs from the bus configuration: In the Conflicts
Viewer, set the Is assigned property of the bus configuration to False.
§ Specify a valid value for the Period property of the Timer Event of the related
task, for example, in the Conflicts Viewer.

IPDU: Invalid period A bus configuration is configured as follows:

for J1939‑22 transport § At least one J1939‑22‑compliant IPDU with more than 60 data bytes is
protocol communication (bus assigned to the bus configuration, i.e., the Broadcast Announce Message
configuration) (BAM) transport protocol is used for the J1939 communication.
§ For the Timer Event of the task to which the related
BusCfg_MainFunctionFetch [<bus configuration name>] and
BusCfg_MainFunctionDeliver [<bus configuration name>] runnable
functions are assigned, a period of longer than 0.01 s is specified.

If the Broadcast Announce Message (BAM) transport protocol is used

for J1939‑22 communication, the Timer Event of the task to which
the related BusCfg_MainFunctionFetch [<bus configuration name>]
and BusCfg_MainFunctionDeliver [<bus configuration name>] runnable
functions are assigned should have a period in the range 0 … 0.01 s.

If you do not resolve this conflict, default code is generated, i.e., because the
period exceeds 0.01 s, not all of the timing requirements of the BAM protocol
for J1939‑22 communication might be fulfilled at run time. Therefore, timeouts
might occur.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

241
May 2024 ConfigurationDesk Conflicts
Conflicts

IPDU: Missing authentic A conflicting communication matrix element is assigned to a bus configuration.
IPDU for secured IPDU (bus For an assigned secured IPDU, the communication matrix specifies the following
configuration) settings:
§ The secured IPDU is configured as a cryptographic IPDU.
§ No authentic IPDU is mapped to the secured IPDU.

To each cryptographic IPDU, the communication matrix must map one authentic
IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

IPDU: Missing authentic A communication matrix configures a secured IPDU as a cryptographic IPDU but
IPDU for secured IPDU does not map an authentic IPDU to the cryptographic IPDU.
(communication matrix)
To each cryptographic IPDU, the communication matrix must map one authentic
IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

242
ConfigurationDesk Conflicts May 2024
IPDU Conflicts

IPDU: Multiple secured IPDUs Two or more secured IPDUs that are assigned to the Simulated ECUs or
for one authentic IPDU (bus Manipulation part of a bus configuration are configured as follows: The
configuration) secured IPDUs are configured for the same ECU and communication cluster, and
secure the same authentic IPDU.

For the Simulated ECUs and Manipulation part of a bus configuration, the Bus
Manager supports only one secured IPDU per ECU and communication cluster
for one authentic IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

§ If you do not need any of the conflicting elements in the executable
application, remove all of them from the bus configuration: In the Conflicts
Viewer, set the bus configuration's Is assigned property to False.
§ If you need only one of the conflicting elements in the executable application,
remove all but one element from the bus configuration: In the Conflicts
Viewer, set the Is assigned property of the elements you do not need to
False.
§ If you need two or more of the conflicting elements in the executable
application, change the assignment to the bus configurations: Keep one
secured IPDU and the authentic IPDU for this bus configuration. Remove all
the other secured IPDUs from this bus configuration. Assign all the removed
secured IPDUs, including the authentic IPDU, to separate bus configurations.

IPDU: Too many J1939 PGNs A conflicting communication matrix element is assigned to a bus configuration.
per IPDU on CAN channel (bus For an assigned J1939‑compliant IPDU, the communication matrix specifies all of
configuration) the following settings:
§ For the J1939‑compliant IPDU, more than one parameter group number (PGN)
is specified.
§ At least two of the related sending network nodes (source addresses) are
members of the same communication cluster.

For each communication cluster, the communication matrix must specify only
one PGN for a J1939‑compliant IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

§ If you do not need the conflicting element in the executable application,
remove it from the bus configuration: In the Conflicts Viewer, set the

243
May 2024 ConfigurationDesk Conflicts
Conflicts

element's Is assigned property to False to remove only this conflicting

IPDU: Too many J1939 PGNs A communication matrix specifies all of the following settings for a
per IPDU on CAN channel J1939‑compliant IPDU:
(communication matrix) § For the J1939‑compliant IPDU, more than one parameter group number (PGN)
is specified.
§ At least two of the related sending network nodes (source addresses) are
members of the same communication cluster.

For each communication cluster, the communication matrix must specify only
one PGN for a J1939‑compliant IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

IPDU: Too many receiving A conflicting communication matrix element is assigned to a bus configuration.
J1939 transport protocol For an assigned J1939‑compliant IPDU, the communication matrix specifies the
nodes connected (bus following settings:
configuration) § The communication mode is peer‑to‑peer, i.e., Broadcast is False.
§ More than one receiving J1939 transport protocol node is specified.

For each J1939‑compliant peer‑to‑peer IPDU, the communication matrix must

specify exactly one receiving J1939 transport protocol node.

244
ConfigurationDesk Conflicts May 2024
IPDU Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

IPDU: Too many A communication matrix specifies the following settings for a J1939‑compliant
receiving J1939 transport IPDU:
protocol nodes connected § The communication mode is peer‑to‑peer, i.e., Broadcast is False.
(communication matrix) § More than one receiving J1939 transport protocol node is specified.

For each J1939‑compliant peer‑to‑peer IPDU, the communication matrix must

specify exactly one receiving J1939 transport protocol node.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

IPDU: Unsupported IPDU A conflicting communication matrix element is assigned to a bus configuration.
type for J1939-22 (bus An assigned secured IPDU or container IPDU is specified as a J1939‑22‑compliant
configuration) IPDU by the communication matrix.

245
May 2024 ConfigurationDesk Conflicts
Conflicts

Secured IPDUs and container IPDUs are not supported as J1939‑22‑compliant

IPDUs. Instead, J1939‑22‑compliant IPDUs can be ISignal IPDUs or multiplexed
IPDUs, for example.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

IPDU: Unsupported IPDU type A communication matrix element specifies a secured IPDU or container IPDU as a
for J1939-22 (communication J1939‑22‑compliant IPDU.
matrix)
Secured IPDUs and container IPDUs are not supported as J1939‑22‑compliant
IPDUs. Instead, J1939‑22‑compliant IPDUs can be ISignal IPDUs or multiplexed
IPDUs, for example.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

246
ConfigurationDesk Conflicts May 2024
ISignal Conflicts

ISignal Conflicts

ISignal: Duplicate ISignal or A conflicting communication matrix element is assigned to a bus configuration.
ISignal group name (bus For an assigned PDU, the communication matrix defines two or more ISignals or
configuration) ISignal groups with identical names.

For ISignals and ISignal groups of the same PDU, the communication matrix must
define unique names.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

ISignal: Duplicate ISignal A communication matrix defines two or more ISignals or ISignal groups with
or ISignal group name identical names for one PDU.
(communication matrix)
For ISignals and ISignal groups of the same PDU, the communication matrix must
define unique names.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

247
May 2024 ConfigurationDesk Conflicts
Conflicts

ISignal: Invalid byte alignment A conflicting communication matrix element is assigned to a bus configuration.
(bus configuration) For an assigned ISignal, the communication matrix specifies the following
settings:
§ The ISignal is an array signal.
§ The length and/or start bit position of the ISignal is not byte-aligned.

According to AUTOSAR, array signals must be byte-aligned, i.e.:

§ The signal length (in bits) must be 8 or a multiple of 8.
§ The signal's start bit position (in bits) must be 0 or a multiple of 8.

If you do not resolve this conflict, default code is generated, i.e., even though
the array signal is not byte-aligned, it can be transmitted and received at run
time.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application. Choose
one of the following alternatives:
§ Remove the conflicting element from the bus configuration: In the Conflicts
Viewer, set the element's Is assigned property to False to remove only this
conflicting element. Alternatively, set the bus configuration's Is assigned
property to False to remove all conflicting elements in one step.
Depending on the type of the conflicting element, related elements are
removed as well, e.g., all ISignals of a conflicting ISignal IPDU.
§ Specify valid values for the Length and/or Start bit position properties,
or change the signal type via the Category property, for example, in
the Conflicts Viewer. This changes the communication matrix in the
active ConfigurationDesk application and all element instances in all bus
configurations of the application. The originally imported communication
matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

ISignal: Invalid byte alignment A communication matrix specifies the following settings for an ISignal:
(communication matrix) § The ISignal is an array signal.
§ The length and/or start bit position of the ISignal are not byte-aligned.

Array signals must be byte-aligned, i.e.:

§ The signal length (in bit) must be 8 or multiples of 8.
§ The signal's start bit position (in bit) must be 0 or multiples of 8.

248
ConfigurationDesk Conflicts May 2024
ISignal Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify valid values for the Length, Start bit position, and/or Category
properties, or change the signal type via the Category property, for example,
in the Conflicts Viewer. This changes the communication matrix in the
active ConfigurationDesk application and all element instances in all bus
configurations of the application. The originally imported communication
matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

ISignal: Invalid coding defined A conflicting communication matrix element is assigned to a bus configuration.
(bus configuration) For an assigned ISignal, the communication matrix defines no or more than one
coding.

For each ISignal, the communication matrix must define exactly one coding.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

249
May 2024 ConfigurationDesk Conflicts
Conflicts

ISignal: Invalid coding defined A communication matrix defines no or more than one coding for an ISignal.
(communication matrix)
For each ISignal, the communication matrix must define exactly one coding.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

ISignal: Invalid length (bus A conflicting communication matrix element is assigned to a bus configuration.
configuration) For an assigned ISignal, the communication matrix does not define a length in
bit, or a defined length exceeds the valid range.

For each ISignal, the communication matrix must define a length ≥ 1 bit. The
maximum valid ISignal length depends on the coded base data type of the
ISignal.

For more information, refer to:

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

250
ConfigurationDesk Conflicts May 2024
ISignal Conflicts

Tip

You can change the maximum valid ISignal length by specifying another
coded base data type for the ISignal. To access the related ISignal
property in the Properties Browser, right-click the conflicting ISignal-
to-IPDU mapping in the Conflicts Viewer and select Select Related
Elements in Bus Configurations Table from the context menu.

§ Resolve the conflict by correcting the original communication matrix. Refer

ISignal: Invalid length A communication matrix does not define a length for an ISignal, or a defined
(communication matrix) length exceeds the valid range.

For each ISignal, the communication matrix must define a length ≥ 1 bit. The
maximum valid ISignal length depends on the coded base data type of the
ISignal.

For more information, refer to:

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

251
May 2024 ConfigurationDesk Conflicts
Conflicts

Tip

You can change the maximum valid ISignal length by specifying another
coded base data type for the ISignal. To do so, select the ISignal in
the Buses Browser, for example. Then, select another data type for the
coded Base data type property in the Properties Browser.

ISignal: No name defined (bus A conflicting communication matrix element is assigned to a bus configuration.
configuration) For an assigned ISignal, the communication matrix does not define a name.

For each ISignal, the communication matrix must define a name. The name must
be unique for all the ISignals and ISignal groups of one IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

ISignal: No name defined A communication matrix does not define a name for an ISignal.
(communication matrix)
For each ISignal, the communication matrix must define a name. The name must
be unique for all the ISignals and ISignal groups of one IPDU.

252
ConfigurationDesk Conflicts May 2024
ISignal Group Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

ISignal Group Conflicts

ISignal group: Invalid A conflicting communication matrix element is assigned to a bus configuration.
end-to-end transformation For an assigned ISignal group or ISignal, the communication matrix specifies the
profile or description (bus following settings:
configuration) § The ISignal group or ISignal is protected by an end-to-end transformer.
§ For the end-to-end transformer, one of the following settings is specified:
§ The specified Profile name references an end-to-end protection profile the
Bus Manager does not support.
§ One or more transformer attributes are invalid for the specified end-to-end
protection profile.

End-to-end transformers must use an end-to-end protection profile the Bus

Manager supports. All the transformer attributes that are required by the used
end-to-end protection profile must be specified within the valid range according
to the AUTOSAR specifications.

If you do not resolve this conflict, default code is generated, i.e., no end-to-end
protection is used for the affected ISignal group or ISignal. Nevertheless, the
ISignal group or ISignal and its related IPDU can be transmitted and received at
run time.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

253
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

ISignal group: Invalid end-to- A communication matrix specifies the following settings for an ISignal group or
end transformation profile or ISignal:
description (communication § The ISignal group or ISignal is protected by an end-to-end transformer.
matrix) § For the end-to-end transformer, one of the following settings is specified:
§ The specified Profile name references an end-to-end protection profile the
Bus Manager does not support.
§ One or more transformer attributes are invalid for the specified end-to-end
protection profile.

End-to-end transformers must use an end-to-end protection profile the Bus

Manager supports. All the transformer attributes that are required by the used
end-to-end protection profile must be specified within the valid range according
to the AUTOSAR specifications.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

254
ConfigurationDesk Conflicts May 2024
ISignal Group Conflicts

ISignal group: Invalid number A conflicting communication matrix element is assigned to a bus configuration.
of ISignal IPDUs for end-to- For an assigned ISignal group, the communication matrix specifies the following
end protected ISignal group settings:
(bus configuration) § An end-to-end protection definition contains a reference to the ISignal group.
§ The end-to-end protection definition maps no or more than one ISignal IPDU
to the ISignal group reference.

Within an end-to-end protection definition, exactly one ISignal IPDU must be

mapped to one ISignal group reference.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

ISignal group: Invalid number A communication matrix specifies the following settings for an ISignal group:
of ISignal IPDUs for end-to- § An end-to-end protection definition contains a reference to the ISignal group.
end protected ISignal group § The end-to-end protection definition maps no or more than one ISignal IPDU
(communication matrix) to the ISignal group reference.

Within an end-to-end protection definition, exactly one ISignal IPDU must be

mapped to one ISignal group reference

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

255
May 2024 ConfigurationDesk Conflicts
Conflicts

ISignal group: Invalid A communication matrix specifies the following settings for an ISignal group or
transformation configuration ISignal:
(communication matrix) § The ISignal group or ISignal is protected by an end-to-end transformer.
§ For the ISignal group or ISignal, at least one of the following references is
missing:
§ Reference to a data transformation
§ Reference to a transformation description

ISignal groups and ISignals that are protected by an end-to-end transformer must
reference a data transformation and a transformation description.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

ISignal group: Multiple end- A conflicting communication matrix element is assigned to a bus configuration.
to-end configurations related For an assigned ISignal group, the communication matrix specifies the following
(bus configuration) setting: The ISignal group is end-to-end protected but it is related to more than
one end-to-end configuration.

An end-to-end-protected ISignal group must be related to exactly one end-to-

end configuration., i.e.:
§ The ISignal group must be referenced only once within an END-TO-END-
PROTECTION-SET.
- OR -
§ Only one set of END-TO-END-TRANSFORMATION-I-SIGNAL-PROPS must be
specified for the ISignal group.

256
ConfigurationDesk Conflicts May 2024
ISignal Group Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

ISignal group: Multiple end- A communication matrix specifies the following setting for an ISignal group:
to-end configurations related The ISignal group is end-to-end protected but it is related to more than one
(communication matrix) end-to-end configuration.

An end-to-end-protected ISignal group must be related to exactly one end-to-

end configuration, i.e.:
§ The ISignal group must be referenced only once within an END-TO-END-
PROTECTION-SET.
- OR -
§ Only one set of END-TO-END-TRANSFORMATION-I-SIGNAL-PROPS must be
specified for the ISignal group.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

257
May 2024 ConfigurationDesk Conflicts
Conflicts

ISignal-to-IPDU Mapping Conflicts

ISignal-to-IPDU mapping: A conflicting communication matrix element is assigned to a bus configuration.

Invalid endianness (bus For an assigned ISignal-to-IPDU mapping, the communication matrix specifies at
configuration) least one of the following settings:
§ For the ISignal-to-IPDU mapping, no or more than one byte layout is defined.
§ The position of the start bit is unspecified.
§ The endianness is unspecified or invalid.

For each ISignal-to-IPDU mapping, the communication matrix must define exactly
one byte layout. The start bit position and endianness must be specified. The
start bit position must be ≥ 0. Depending on the ISignal type, the endianness
must be either big endian, little endian, or opaque.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

ISignal-to-IPDU mapping: A communication matrix contains at least one of the following settings:
Invalid endianness § For an ISignal-to-IPDU mapping, no or more than one byte layout is defined.
(communication matrix)

258
ConfigurationDesk Conflicts May 2024
J1939 Network Management Node Conflicts

§ The position of the start bit is unspecified.

§ The endianness is unspecified or invalid.

For each ISignal-to-IPDU mapping, the communication matrix must define exactly
one byte layout. The start bit position and endianness must be specified. The
start bit position must be ≥ 0. Depending on the ISignal type, the specified
endianness must be either big endian, little endian, or opaque.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify valid values for the Start bit position and/or Endianness properties
of the ISignal-to-IPDU mapping, for example, in the Conflicts Viewer. This
changes the communication matrix in the active ConfigurationDesk application
and all element instances in all bus configurations of the application. The
originally imported communication matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

J1939 Network Management Node Conflicts

J1939 network management One or more J1939 network management nodes are assigned to a bus
node: Invalid J1939 name configuration. For the assigned J1939 network management nodes, the
on CAN channel (bus following applies:
configuration) § For one or more assigned J1939 network management nodes, the
communication matrix specifies at least one of the following settings:
§ For an assigned J1939 network management node, the communication
matrix specifies an invalid value for the Arbitrary address capable,
Industry group, Vehicle system instance, Vehicle system, Function,
Function instance, ECU instance, Manufacturer code, and/or Identity
number property.
§ The communication matrix maps two or more of the assigned J1939
network management nodes to the same CAN channel and specifies
identical settings for all of the properties above.
§ The J1939 Network Management Enable feature is added to the affected
communication controllers and the feature's Enable property is set to 1:
Static address handling or 2: Dynamic address handling.

259
May 2024 ConfigurationDesk Conflicts
Conflicts

The tuple of the following properties must be unique for each J1939 network
management node of one CAN channel and within the following ranges:
§ Arbitrary address capable: True or False
§ Industry group: 0 … 7
§ Vehicle system instance: 0 … 15
§ Vehicle system: 0 … 127
§ Function: 0 … 255
§ Function instance: 0 … 31
§ ECU instance: 0 … 7
§ Manufacturer code: 0 … 2047
§ Identity number: 0 … 2097151

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

260
ConfigurationDesk Conflicts May 2024
J1939 Transport Protocol Node Conflicts

J1939 network management A communication matrix specifies the following settings for a J1939 network
node: Invalid J1939 name on management node: The tuple of the following properties is not unique on a CAN
CAN channel (communication channel or at least one of the property values exceeds the valid range:
matrix) § Arbitrary address capable
§ Industry group
§ Vehicle system instance
§ Vehicle system
§ Function
§ Function instance
§ ECU instance
§ Manufacturer code
§ Identity number

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

J1939 Transport Protocol Node Conflicts

J1939 transport protocol A conflicting communication matrix element is assigned to a bus configuration.
node: Invalid transport For an assigned J1939 transport protocol node, the communication matrix
protocol address (bus specifies an invalid transport protocol address.
configuration)

261
May 2024 ConfigurationDesk Conflicts
Conflicts

For each J1939 transport protocol node, the communication matrix must specify
a transport protocol address in the range 0 … 253.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Note

This resolves the conflict only if the transport protocol address of the
J1939 transport protocol node is 254.

Tip

The Conflicts Viewer displays the J1939 transport protocol node and
not the communication controller. To access the controller, right-click
the transport protocol node and select Select Related Elements in
Bus Configurations Table from the context menu.

Refer to:
Bus Manager in ConfigurationDesk: Enabling and Disabling J1939 Network
Management (ConfigurationDesk Bus Manager Implementation Guide ).
Bus Manager (stand-alone): Enabling and Disabling J1939 Network
Management (Bus Manager (Stand-Alone) Implementation Guide ).
§ Resolve the conflict by correcting the original communication matrix. Refer
to:
Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

262
ConfigurationDesk Conflicts May 2024
LIN Cluster Conflicts

J1939 transport protocol A communication matrix specifies an invalid transport protocol address for a
node: Invalid transport J1939 transport protocol node.
protocol address
For each J1939 transport protocol node, the communication matrix must specify
(communication matrix)
a transport protocol address in the range 0 … 253.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

LIN Cluster Conflicts

LIN cluster: Invalid speed A communication matrix contains at least one of the following settings:
(baud rate) defined § For a LIN cluster, no baud rate is defined.
(communication matrix) § A defined baud rate exceeds the valid range.

For each LIN cluster, the communication matrix must define a baud rate in the
range 1 … 20 kbit/s.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

263
May 2024 ConfigurationDesk Conflicts
Conflicts

LIN cluster: Too many A conflicting communication matrix element is assigned to a bus configuration.
channels connected (bus For an assigned LIN cluster, the communication matrix specifies more than one
configuration) channel.

For each LIN cluster, the communication matrix must not specify more than one
channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

LIN cluster: Too A communication matrix specifies more than one channel for a LIN cluster.
many channels connected
For each LIN cluster, the communication matrix must not specify more than one
(communication matrix)
channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

264
ConfigurationDesk Conflicts May 2024
LIN Communication Controller Conflicts

LIN Communication Controller Conflicts

LIN communication controller: For a LIN master, a bus configuration references an initial schedule table, but this
Invalid initial schedule table schedule table does not exist in the assigned communication matrix.

A communication matrix can define multiple schedule tables for a LIN master.
The Initial value of a Schedule Index function port references the position of a
schedule table in the communication matrix. This schedule table is used as the
initial schedule table. The specified Initial value must be equal to or smaller
than the number of schedule tables defined in the communication matrix.
Alternatively, you can specify 0 as the Initial value to use no initial schedule
table at all.

For details on schedule tables, refer to:

§ Bus Manager in ConfigurationDesk: Working with LIN Schedule Tables
(ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Working with LIN Schedule Tables (Bus Manager
(Stand-Alone) Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy In the Conflicts Viewer, for example, specify a valid Initial value
for the Schedule Index function port.

LIN communication controller: A conflicting communication matrix element is assigned to a bus configuration.
Too many channels connected For an assigned LIN communication controller, the communication matrix
(bus configuration) specifies more than one channel.

For each LIN communication controller, the communication matrix must not
specify more than one channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

§ If you do not need the conflicting element in the executable application,
remove it from the bus configuration. In the Conflicts Viewer, set the Is
assigned property to False

265
May 2024 ConfigurationDesk Conflicts
Conflicts

LIN communication controller: A communication matrix specifies more than one channel for a LIN
Too many channels connected communication controller.
(communication matrix)
For each LIN communication controller, the communication matrix must not
specify more than one channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

LIN Frame Conflicts

LIN frame: Invalid payload A conflicting communication matrix element is assigned to a bus configuration.
length defined (bus For an assigned LIN frame, the communication matrix defines a payload length
configuration) that exceeds the valid range.

For a LIN frame, the communication matrix must define a payload length within
the range 1 … 8 bytes.

Tip

The payload length of sporadic and event-triggered frames can exceed this
range.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

266
ConfigurationDesk Conflicts May 2024
LIN Frame Conflicts

Remedy Choose one of the following alternatives:

LIN frame: Invalid A communication matrix defines a payload length for a LIN frame that exceeds
payload length defined the valid range.
(communication matrix)
For a LIN frame, the communication matrix must define a payload length within
the range 1 … 8 bytes.

Tip

The payload length of sporadic and event-triggered frames can exceed this
range.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

267
May 2024 ConfigurationDesk Conflicts
Conflicts

LIN frame: Invalid sender A conflicting communication matrix element is assigned to a bus configuration.
defined (bus configuration) For an assigned sporadic LIN frame or a related unconditional frame, the
communication matrix specifies a LIN slave as the transmitting LIN bus node.

Sporadic LIN frames and their related unconditional frames can only be
transmitted by the LIN master.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

LIN frame: Invalid sender A communication matrix specifies a LIN slave as the transmitting LIN bus node
defined (communication for a sporadic LIN frame or a related unconditional frame.
matrix)
Sporadic LIN frames and their related unconditional frames can only be
transmitted by the LIN master.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

268
ConfigurationDesk Conflicts May 2024
LIN Frame Conflicts

LIN frame: No collision A communication matrix does not define a collision resolver schedule table for a
resolver defined for LIN frame.
event-triggered frame
For each LIN frame, the communication matrix must define a collision resolver
(communication matrix)
schedule table.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

LIN frame: Too many LIN A conflicting communication matrix element is assigned to a bus configuration.
frame triggerings connected An assigned LIN frame is used as a substitute frame for a sporadic or event-
(bus configuration) triggered frame. For this assigned LIN frame, the communication matrix specifies
more than one frame triggering for the channel that is also used by the sporadic
or event-triggered frame.

For a LIN frame that is used as a substitute frame for a sporadic or event-
triggered frame, the communication matrix must specify exactly one frame
triggering for the channel that is also used by the sporadic or event-triggered
frame.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

269
May 2024 ConfigurationDesk Conflicts
Conflicts

Depending on the type of the conflicting element, related elements are

LIN frame: Too many LIN A communication matrix specifies a LIN frame that is used as a substitute frame
frame triggerings connected for a sporadic or event-triggered frame and has more than one frame triggering
(communication matrix) for the channel that is also used by the sporadic or event-triggered frame.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

LIN frame: Too many PDU-to- A conflicting communication matrix element is assigned to a bus configuration.
frame mappings connected For an assigned unconditional LIN frame, the communication matrix specifies
(bus configuration) more than one PDU-to-frame mapping.

An unconditional LIN frame must not contain more than one PDU-to-frame
mapping.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

270
ConfigurationDesk Conflicts May 2024
LIN Frame Triggering Conflicts

element. Alternatively, set the bus configuration's Is assigned property to

LIN frame: Too many PDU-to- A communication matrix specifies more than one PDU-to-frame mapping for an
frame mappings connected unconditional LIN frame.
(communication matrix)
An unconditional LIN frame must not contain more than one PDU-to-frame
mapping.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

LIN Frame Triggering Conflicts

LIN frame triggering: Conflicting communication matrix elements are assigned to a bus configuration.
Duplicate LIN identifier on LIN For two or more assigned LIN frame triggerings of one channel, the
channel (bus configuration) communication matrix specifies identical identifier values.

If the communication matrix specifies an identifier value for a LIN frame

triggering, the value must be unique for all the frame triggerings of one channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

271
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

LIN frame triggering: A communication matrix specifies identical identifier values for two or more LIN
Duplicate LIN identifier on frame triggerings of one channel.
LIN channel (communication
If the communication matrix specifies an identifier value for a LIN frame
matrix)
triggering, the value must be unique for all the frame triggerings of one channel.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify unique and valid values for the Identifier properties, for example,
in the Conflicts Viewer. This changes the communication matrix in the
active ConfigurationDesk application and all element instances in all bus
configurations of the application. The originally imported communication
matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

272
ConfigurationDesk Conflicts May 2024
LIN Frame Triggering Conflicts

LIN frame triggering: A conflicting communication matrix element is assigned to a bus configuration.
Invalid frame type (bus For an assigned LIN frame triggering, the communication matrix references a
configuration) CAN frame.

Each LIN frame triggering must reference a LIN frame.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

LIN frame triggering: Invalid A communication matrix references a CAN frame for a LIN frame triggering.
frame type (communication
Each LIN frame triggering must reference a LIN frame.
matrix)
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

LIN frame triggering: A conflicting communication matrix element is assigned to a bus configuration.
Invalid property values (bus For an assigned LIN frame triggering of one channel, the communication matrix
configuration) specifies an invalid frame identifier.

273
May 2024 ConfigurationDesk Conflicts
Conflicts

For a LIN frame triggering of an unconditional or event-triggered frame, the

communication matrix must specify a frame identifier within the range 0 … 63.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

LIN frame triggering: A communication matrix specifies an invalid frame identifier for a LIN frame
Invalid property values triggering.
(communication matrix)
For a LIN frame triggering of an unconditional or event-triggered frame, the
communication matrix must specify a frame identifier within the range 0 … 63.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify a valid value for the Identifier property, for example, in
the Conflicts Viewer. This changes the communication matrix in the

274
ConfigurationDesk Conflicts May 2024
LIN Schedule Table Conflicts

active ConfigurationDesk application and all element instances in all bus

configurations of the application. The originally imported communication
matrix remains unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

LIN frame triggering: No A communication matrix specifies the following settings for a LIN frame and its
frame triggering of related frame triggerings:
unconditional frame on the § An unconditional LIN frame is referenced by an event-triggered or sporadic
same channel (communication frame.
matrix) § None of the frame triggerings of the unconditional frame and the event-
triggered or sporadic frame use the same channel.

An unconditional frame that is referenced by an event-triggered or sporadic

frame must have at least one frame triggering on the same channel as the
referencing frame.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

LIN Schedule Table Conflicts

LIN schedule table: Invalid LIN A conflicting communication matrix element is assigned to a bus configuration.
schedule table entries (bus For entries of an assigned LIN schedule table, the communication matrix specifies
configuration) invalid settings for the delay, position in table, and/or the used channel.

For each entry, a LIN schedule table must at least specify the following settings:
§ Delay
§ Position in table
The values of this setting must be unique for each entry of a schedule table.
§ The channel used by the frame triggerings
The frame triggerings of each entry must use the same channel as the
schedule table itself.

275
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

LIN schedule table: Invalid For entries of a LIN schedule table, a communication matrix specifies invalid
LIN schedule table entries settings for the delay, position in table, and/or the used channel.
(communication matrix)
For each entry, a LIN schedule table must at least specify the following settings:
§ Delay
§ Position in table
The values of this setting must be unique for each entry of a schedule table.
§ The channel used by the frame triggerings
The frame triggerings of each entry must use the same channel as the
schedule table itself.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Model Conflicts

Model: Multiple assignments A model implementation is assigned to two or more application processes in the
to different application executable application.
processes
The assignment of a model implementation to an application process must be
unique.

276
ConfigurationDesk Conflicts May 2024
Model Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, select only one application
process to assign the model implementation to.

Model: No source code and The executable application contains an application process to which a Functional
no supported library available Mock-up Unit (FMU), a Simulink implementation container file (SIC file), or a
bus simulation container file (BSC file) is assigned, that does not contain source
code or a precompiled library in a supported version. You can work with such
FMUs, SIC files, and BSC files as usual. This means that you can map model port
blocks, configure tasks, etc. However, you cannot perform a build process for
your executable application.

To perform a successful build process, FMUs, SIC files, or BSC files that are
assigned to an application process must contain source code or precompiled
libraries in a supported version.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Remove the FMU,SIC file, or BSC file that does not have source code
or a precompiled library from the application process, and assign an FMU, SIC
file, or BSC file with source code or a precompiled library to it.

Model: Unsupported At least one of the following cases occurs:

combination of assigned § Case 1: Binary libraries contained in a model container or referenced by a
processing unit and model(s) Simulink model are incompatible with the operating system of the processing
unit assigned to the relevant processing unit application.
§ Case 2: A Simulink model contains blocks of the RTI CAN MultiMessage
Blockset and/or RTI LIN MultiMessage Blockset and a MicroAutoBox III or
MicroLabBox II hardware topology is added to the Hardware Resource
Browser.
The RTI CAN MultiMessage Blockset and RTI LIN MultiMessage Blockset are
not supported by the MicroAutoBox III or MicroLabBox II.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

277
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

§ Case 1: The Simulink model or model container must be replaced with
a Simulink model or model container that uses binary libraries that are
compatible with the registered platform.
§ Case 2: In the Simulink model, delete the blocks of the RTI CAN MultiMessage
Blockset and/or RTI LIN MultiMessage Blockset. Then, analyze the model
including task information in ConfigurationDesk.

Model: Unsupported version The executable application contains an SIC file that is not supported by
of SIC file in project ConfigurationDesk.

ConfigurationDesk supports SIC files that are generated with the same Release
or one of the 7 previous general Releases of the Model Interface Package for
Simulink. For SIC files generated with TargetLink, the same time window applies.
However, note that a new TargetLink version is only released for dSPACE Releases
xxxx-B.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Replace the related SIC file with an SIC file that has been generated
with the current Release or one of the 7 previous Releases of the Model Interface
Package for Simulink, or with a suitable TargetLink version.

Model Port Block Conflicts

Model port block: Duplicate The model topology contains two or more model implementations with the
ID same interface, which means, that two or more model port blocks have the
same ID. At least two of these model implementations with the same interface
are assigned to an application process. These model port blocks are marked with
a specific icon in the Model Browser.

Only one of the model implementations that have the same interface must be
assigned to an application process.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

278
ConfigurationDesk Conflicts May 2024
Model Port Block Conflicts

Remedy In the Processing Resource Assignment table, remove all but one
assignment from model implementations with the same interface to application
processes.

Model port block: No This conflict is caused by all of the following conditions:
assignment to application § The model port block is resolved.
process § The model port block is a part of the signal chain.
§ The model implementation providing the model port block is not assigned to
an application process.

The model port block is highlighted in the working view. During code
generation, the model port block is treated like an unresolved model port
block (refer to Characteristics of Model Port Blocks (ConfigurationDesk Real-Time
Implementation Guide )).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Choose one of the following alternatives:

§ Assign the model implementation to an application process.
§ Create a preconfigured application for the model implementation.
§ Delete the related model port block from the configuration.

Model port block: Unresolved A model port is obsolete.

port
An obsolete model port can occur, for example, if a model port is connected to
an I/O function port and the model port is deleted from the model port block in
the Simulink model. If you then perform a model analysis, the port is unresolved,
but it is still displayed in ConfigurationDesk as long as it is connected to any
other port. The obsolete model port is highlighted in the working view.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Delete the connection between the obsolete model port and the
port it is connected to.

279
May 2024 ConfigurationDesk Conflicts
Conflicts

Model Port Mapping Conflicts

Model port mapping: Invalid Two model port blocks of the same model are mapped in the currently active
connection between data ConfigurationDesk application.
port blocks of same model
Mappings between model port blocks must only be used for model
communication between different models.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In a working view, modify the model port mapping.

Model port mapping: Invalid A CAN or LIN function block is used as follows:
Configuration port mapping § The Configuration port of the CAN or LIN function block is mapped
to a Configuration Port block that is generated for an RTICANMM
ControllerSetup or RTILINMM ControllerSetup block.
§ Additionally, the CAN or LIN function block specifies the hardware access for a
bus configuration or an ECU Interface Configuration function block.

RTICANMM ControllerSetup blocks and RTILINMM ControllerSetup blocks

require exclusive access to CAN and LIN function blocks, i.e., the function
blocks must not specify the hardware access for any other blocks or model
implementations.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Choose one of the following alternatives:

§ In a working view, delete the mapping line.
§ In the Conflicts Viewer, select another suitable CAN or LIN function block
from the list of the Assigned feature provider property. If no suitable
function block is available, instantiate a new CAN or LIN function block.
For basic information on specifying the hardware access for bus
configurations, refer to Specifying the Hardware Access (ConfigurationDesk
Bus Manager Implementation Guide ).

Model port mapping: The model port mapping contains two ports with mismatching values for the
Mismatching data width Data width property.

280
ConfigurationDesk Conflicts May 2024
Model Port Mapping Conflicts

Model port mappings can either be between a function port and a model port or
between two model ports. The width of two mapped ports does not necessarily
need to be identical. If the port widths differ, the intersecting vector elements
are used. The other elements are neglected, and ConfigurationDesk issues a
warning for the signal chain. Note that only scalars and vectors are supported.
Multidimensional signals are not supported.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Choose one of the following alternatives:

§ Adjust the function block settings to make the data width of the function port
match the data width of the model port (not possible if two mapped model
ports are affected).
§ Adjust the behavior model in Simulink and reanalyze it.
§ In a working view, modify the model port mapping.

Model port mapping: The mapped ports do not comply with the rules for model port mapping.:
Mismatching port type § Function ports must not be mapped to other function ports.
§ Configuration ports of function blocks must be mapped to Configuration
Port blocks.
§ The port type (for example, the data direction) must match.

For a complete overview of mapping rules, refer to Rules for Model Port
Mapping (ConfigurationDesk Real-Time Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In a working view, modify the model port mapping.

Model port mapping: The Configuration port of a CAN, FlexRay, or LIN function block is mapped
Mismatching protocol type to a Configuration Port block that was created for a different bus protocol.
For example, the Configuration port of a CAN function block is mapped to
a Configuration Port block that was created for a FLEXRAYCONFIG UPDATE
block.

281
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Modify the model port mapping.

Model port mapping: The inport of a model port block is mapped to two or more function ports or
Multiple data sources outports of a model port block.
connected
The inport of a model port block must be mapped to exactly one function port
or outport of a model port block.

Note

Multiple data sources are allowed for other sources.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Modify the model port mapping.

Model port mapping: The Configuration port of a FlexRay, CAN, or LIN function block is mapped to
Multiple links Configuration Port blocks in a way that is not supported.

For FlexRay function blocks: The Configuration port must be mapped to

exactly one Configuration Port block of a Simulink model.

For CAN and LIN function blocks: The Configuration port must be mapped in
one of the following ways:
§ To exactly one Configuration Port block of one Simulink model.
§ To one or more Configuration Port blocks of one or more bus simulation
containers.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Modify the mapping to Configuration Port blocks to match the valid
mappings as described above.

282
ConfigurationDesk Conflicts May 2024
Model Port Mapping Conflicts

Model port mapping: No The Configuration port of an instantiated FlexRay function block is not
suitable configuration port mapped to a suitable Configuration Port block.
connected
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy In a working view, map the Configuration port to a suitable

Configuration Port block, which is a specific model port block.

Model port mapping: The ConfigurationDesk application contains a precompiled Simulink

Unsupported combination of implementation container (SIC file) created with the Model Interface Package
used models for model for Simulink, or an SIC file created with TargetLink 4.4 that provides structured
communication data ports. The structured data ports participate in model communication with
a bus simulation container (BSC file) created with the Bus Manager of dSPACE
Release 2019-A or earlier.

For model communication, this combination of model implementations is not

supported.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Make sure that you only use supported model implementation
combinations for model communication.

Model port mapping: The port with a variable-size signal has an invalid mapping line.
Unsupported connection of
The mapping of variable-size ports must comply with the following rules:
variable-size data port
§ Variable-size inports of model port blocks or function blocks are mapped to
variable-size outports or fixed-size outports of a model port block.
§ Variable size outports are mapped to variable-size inports.
§ The data width of the variable-size inports must be ≥ the data width of the
variable-size outports.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

283
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

§ Delete the unsupported mapping line from the variable-size port and create a
mapping line that complies with the above rules.
§ Change the setting of the mapped function block to provide a function port
that complies with the above rules. For example: Change the value of the
Variable vector size property.

Model port mapping: The ConfigurationDesk application contains a Configuration Port block that was
Unsupported mapping of created for an RTICANMM ControllerSetup or RTILINMM ControllerSetup
RTIxxxMM configuration to block. The configuration port of the Configuration Port block is mapped to a
MicroAutoBox bus I/O CAN or LIN function block to which a hardware resource is assigned that is
function provided by the MicroAutoBox III.

The MicroAutoBox III does not support bus communication that was configured
using the RTI CAN MultiMessage Blockset or RTI LIN MultiMessage Blockset,
respectively.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Choose one of the following alternatives:

§ Assign a suitable SCALEXIO-based hardware resource to the CAN or LIN
function block. For instructions, refer to How To Assign Hardware Resources
via Function Block Properties (ConfigurationDesk Real-Time Implementation
Guide ).
§ Map the configuration port of the Configuration Port block to a CAN or LIN
function block to which a SCALEXIO-based hardware resource is assigned.

Multiplexed IPDU Conflicts

Multiplexed IPDU: Duplicate A conflicting communication matrix element is assigned to a bus configuration.
selector field code (bus For an assigned multiplexed IPDU, the communication matrix specifies two or
configuration) more dynamic‑part alternatives with identical selector field codes.

For each dynamic‑part alternative of a multiplexed IPDU, the communication

matrix must specify a unique selector field code.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

284
ConfigurationDesk Conflicts May 2024
Multiplexed IPDU Conflicts

Remedy Choose one of the following alternatives:

Multiplexed IPDU: Duplicate A communication matrix specifies identical selector field codes for two or more
selector field code dynamic‑part alternatives of a multiplexed IPDU.
(communication matrix)
For each dynamic‑part alternative of a multiplexed IPDU, the communication
matrix must specify a unique selector field code.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Multiplexed IPDU: Exceeding A conflicting communication matrix element is assigned to a bus configuration.
selector field and/or data For an assigned multiplexed IPDU, the communication matrix specifies the
segment positions (bus positions of the selector field or the data segments in such a way that at least
configuration) one of them exceeds the boundaries of the multiplexed IPDU.

The communication matrix must specify the positions of the selector field and
the data segments within the boundaries of a multiplexed IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

285
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy Choose one of the following alternatives:

Note

Depending on the specified selector field and/or data segment

positions, this remedy might not resolve the conflict.

§ Resolve the conflict by correcting the original communication matrix. Refer

Multiplexed IPDU: Exceeding A communication matrix specifies the positions of the selector field or the data
selector field and/or segments of a multiplexed IPDU in such a way that at least one of them exceeds
data segment positions the boundaries of the multiplexed IPDU.
(communication matrix)
The communication matrix must specify the positions of the selector field and
the data segments within the boundaries of a multiplexed IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Extend the length of the multiplexed IPDU: Specify a suitable value for the
Length property, for example, in the Conflicts Viewer. This changes the
communication matrix in the active ConfigurationDesk application and all
element instances in all bus configurations of the application. The originally
imported communication matrix remains unchanged.

286
ConfigurationDesk Conflicts May 2024
Multiplexed IPDU Conflicts

Note

Depending on the specified selector field and/or data segment positions,

this remedy might not resolve the conflict.

Multiplexed IPDU: Invalid A conflicting communication matrix element is assigned to a bus configuration.
selector field length (bus For an assigned multiplexed IPDU, the communication matrix specifies at least
configuration) one of the following settings:
§ For the multiplexed IPDU, no selector field is specified.
§ A specified selector field has an invalid bit length.

For each multiplexed IPDU, the communication matrix must specify a selector
field with a bit length in the range 1 … 8 bits.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Multiplexed IPDU: Invalid A communication matrix contains at least one of the following settings:
selector field length § For a multiplexed IPDU, no selector field is specified.
(communication matrix) § A specified selector field has an invalid bit length.

For each multiplexed IPDU, the communication matrix must specify a selector
field with a bit length in the range 1 … 8 bits.

287
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Multiplexed IPDU: Invalid A conflicting communication matrix element is assigned to a bus configuration.
selector field code (bus For an assigned multiplexed IPDU, the communication matrix specifies at least
configuration) one of the following settings:
§ For a dynamic‑part alternative of the multiplexed IPDU, no selector field code is
specified.
§ A specified selector field code exceeds the bit length of the related selector
field.

For each dynamic‑part alternative of a multiplexed IPDU, the communication

matrix must specify a selector field code. The selector field code
must be smaller than the bit length of the related selector field:
selector_field_codemax ≤ 2bit_length_selector_field -1

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

288
ConfigurationDesk Conflicts May 2024
Multiplexed IPDU Conflicts

Multiplexed IPDU: Invalid A communication matrix contains at least one of the following settings:
selector field code § For a dynamic‑part alternative of a multiplexed IPDU, no selector field code is
(communication matrix) specified.
§ A specified selector field code exceeds the bit length of the related selector
field.

For each dynamic‑part alternative of a multiplexed IPDU, the communication

matrix must specify a selector field code. The selector field code
must be smaller than the bit length of the related selector field:
selector_field_codemax ≤ 2bit_length_selector_field -1

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Multiplexed IPDU: Invalid A conflicting communication matrix element is assigned to a bus configuration.
endianness of aggregated For the selector field and/or the data segment positions of the static or dynamic
elements (bus configuration) part of an assigned multiplexed IPDU, the communication matrix specifies at
least one of the following settings:
§ At least one start bit position is unspecified.
§ At least one endianness (byte order) is unspecified or invalid, or the specified
byte orders differ.

For the selector field and the data segment positions of the static and dynamic
part of a multiplexed IPDU, the start bit positions and endiannesses must be
specified. The endianness must be the same for all the elements. It must be
either big endian or little endian.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

289
May 2024 ConfigurationDesk Conflicts
Conflicts

Depending on the type of the conflicting element, related elements are

Multiplexed IPDU: Invalid A communication matrix specifies at least one of the following settings for the
endianness of aggregated selector field and/or the data segment positions of the static or dynamic part of a
elements (communication multiplexed IPDU:
matrix) § At least one start bit position is unspecified.
§ At least one endianness (byte order) is unspecified or invalid, or the specified
byte orders differ.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Multiplexed IPDU: Invalid A conflicting communication matrix element is assigned to a bus configuration.
PDU-to-frame mapping For an assigned multiplexed IPDU, the communication matrix specifies at least
references (bus configuration) one of the following settings:
§ For the dynamic part of the multiplexed IPDU, no PDU-to-frame mapping is
specified.
§ A PDU-to-frame mapping that is specified as the dynamic part of the
multiplexed IPDU is not related to an IPDU in the communication matrix.

At least one PDU-to-frame mapping must be specified as the dynamic part of a

multiplexed IPDU and the PDU-to-frame mapping must be related to an IPDU in
the communication matrix.

290
ConfigurationDesk Conflicts May 2024
Multiplexed IPDU Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Multiplexed IPDU: Invalid A communication matrix specifies at least one of the following settings for a
PDU-to-frame mapping multiplexed IPDU:
references (communication § For the dynamic part of the multiplexed IPDU, no PDU-to-frame mapping is
matrix) specified.
§ A PDU-to-frame mapping that is specified as the dynamic part of the
multiplexed IPDU is not related to an IPDU in the communication matrix.

At least one PDU-to-frame mapping must be specified as the dynamic part of a

multiplexed IPDU and the PDU-to-frame mapping must be related to an IPDU in
the communication matrix.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Multiplexed IPDU: Conflicting communication matrix elements are assigned to a bus configuration.
Mismatching IPDU length (bus A multiplexed IPDU and its dynamic‑part IPDUs and/or static‑part IPDU are
configuration)

291
May 2024 ConfigurationDesk Conflicts
Conflicts

assigned to a bus configuration. For the assigned IPDUs, the communication

matrix specifies mismatching payload lengths.

The payload length of each dynamic‑part IPDU and the static‑part IPDU must be
equal to or shorter than the payload length of the multiplexed IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Multiplexed IPDU: A communication matrix specifies mismatching payload lengths for a multiplexed
Mismatching IPDU length IPDU and its dynamic part IPDUs and/or static part IPDU.
(communication matrix)
The payload length of each dynamic‑part IPDU and the static‑part IPDU must be
equal to or shorter than the payload length of the multiplexed IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

292
ConfigurationDesk Conflicts May 2024
Multiplexed IPDU Conflicts

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
In the Conflicts Viewer, for example, adjust the conflicting lengths via the
related Length property: Extend the length of the multiplexed IPDU and/or
reduce the lengths of its dynamic‑part IPDUs and/or the static‑part IPDU.
This changes the communication matrix in the active ConfigurationDesk
application and all element instances in all bus configurations of
the application. The originally imported communication matrix remains
unchanged.
§ Resolve the conflict by correcting the original communication matrix. Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related
Conflicts (ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

Multiplexed IPDU: A conflicting communication matrix element is assigned to a bus configuration.

Overlapping selector field For an assigned multiplexed IPDU, the communication matrix specifies at least
and/or data segment positions one of the following settings:
(bus configuration) § The data segment positions in the multiplexed IPDU overlap.
§ The selector field and the data segment positions of the static part overlap.

The communication matrix must specify the selector field and the data segment
positions in such a way that they do not overlap each other within the
multiplexed IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

293
May 2024 ConfigurationDesk Conflicts
Conflicts

Multiplexed IPDU: A communication matrix specifies at least one of the following settings for a
Overlapping selector field multiplexed IPDU:
and/or data segment positions § The data segment positions in the multiplexed IPDU overlap.
(communication matrix) § The selector field and the data segment positions of the static part overlap.

The communication matrix must specify the selector field and the data segment
positions in such a way that they do not overlap each other within the
multiplexed IPDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Partial Networking Conflicts

Partial networking: Duplicate Two or more partial network clusters of the same communication matrix have
name of partial network identical names in a bus configuration.
cluster
The names of partial network clusters of the same communication matrix should
be unique within a bus configuration. The names are generated when importing
the communication matrix to the ConfigurationDesk application. Refer to:
§ Bus Manager in ConfigurationDesk: Implementing Partial Networking in
Executable Applications (ConfigurationDesk Bus Manager Implementation
Guide )
§ Bus Manager (stand-alone): Implementing Partial Networking in Executable
Applications (Bus Manager (Stand-Alone) Implementation Guide )

If you do not resolve this conflict, default code is generated, i.e., even though
the names are not unique, the related partial network clusters can be included in
executable applications. However, it is not possible to unambiguously identify the
partial network clusters in the ConfigurationDesk application.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

294
ConfigurationDesk Conflicts May 2024
PDU Conflicts

Remedy Resolve the conflict by correcting the original communication matrix.

Refer to:
§ Bus Manager in ConfigurationDesk: Resolving Bus Manager-Related Conflicts
(ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Resolving Bus Manager-Related Conflicts (Bus
Manager (Stand-Alone) Implementation Guide ).

PDU Conflicts

PDU: Duplicate name (bus Conflicting communication matrix elements are assigned to a bus configuration.
configuration) For two or more assigned PDUs of the same ECU and direction (TX or RX), the
communication matrix specifies identical names.

For PDUs of the same ECU and direction, the communication matrix must specify
unique names.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

PDU: Duplicate name A communication matrix specifies identical names for two or more PDUs of the
(communication matrix) same ECU and direction (TX or RX).

For PDUs of the same ECU and direction, the communication matrix must specify
unique names.

295
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

PDU: Exceeding ISignals A conflicting communication matrix element is assigned to a bus configuration.
and/or update bits (bus For an assigned PDU, the communication matrix specifies ISignal-to-IPDU
configuration) mappings and due to these mappings, ISignals and/or update bits exceed the
PDU boundaries.

The communication matrix must specify ISignal-to-IPDU mappings in such a way

that ISignals and update bits are within the boundaries of the PDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

296
ConfigurationDesk Conflicts May 2024
PDU Conflicts

Note

If you change the length of an ISignal, you might have to adapt the
ISignal's coded Base data type. For more information, refer to:
§ Bus Manager in ConfigurationDesk: Configurable Settings of ISignals
(ConfigurationDesk Bus Manager Implementation Guide ).
§ Bus Manager (stand-alone): Configurable Settings of ISignals (Bus
Manager (Stand-Alone) Implementation Guide ).

Tip

To access the coded Base data type property of an ISignal in the

Properties Browser, right-click the ISignal in the Conflicts Viewer
and select Select Related Elements in Bus Configurations Table
from the context menu.

§ Resolve the conflict by correcting the original communication matrix. Refer

PDU: Exceeding ISignals A communication matrix specifies ISignal-to-IPDU mappings for a PDU and due
and/or update bits to these mappings, ISignals and/or update bits exceed the IPDU boundaries.
(communication matrix)
The communication matrix must specify ISignal-to-IPDU mappings in such a way
that ISignals and update bits are within the boundaries of the PDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Extend the length of the PDU and/or adjust the conflicting settings of its
included ISignals: Specify suitable values for the Length property of the PDU
and/or the Length, Start bit position, and/or Endianness properties of the
conflicting ISignals, for example, in the Conflicts Viewer.
This changes the communication matrix in the active ConfigurationDesk
application and all element instances in all bus configurations of
the application. The originally imported communication matrix remains
unchanged.

297
May 2024 ConfigurationDesk Conflicts
Conflicts

Note

PDU: Invalid payload length A conflicting communication matrix element is assigned to a bus configuration.
defined (bus configuration) For an assigned PDU, the communication matrix specifies an invalid payload
length.

The communication matrix must specify a valid payload length for each PDU. The
valid value range depends on the bus system and bus protocol as follows:
§ Classic CAN and LIN: 0 … 8 bytes
§ CAN FD: 0 … 64 bytes
§ J1939‑21: 0 … 1,785 bytes
§ J1939‑22: 0 … 15,352 bytes

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

298
ConfigurationDesk Conflicts May 2024
PDU Conflicts

§ Resolve the conflict by correcting the original communication matrix. Refer

PDU: Invalid payload length A communication matrix specifies an invalid payload length for a PDU.
defined (communication
The communication matrix must specify a valid payload length for each PDU. The
matrix)
valid value range depends on the bus system and bus protocol as follows:
§ Classic CAN and LIN: 0 … 8 bytes
§ CAN FD: 0 … 64 bytes
§ J1939‑21: 0 … 1,785 bytes
§ J1939‑22: 0 … 15,352 bytes

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

PDU: Overlapping ISignals A conflicting communication matrix element is assigned to a bus configuration.
and/or update bits (bus For an assigned PDU, the communication matrix specifies ISignal-to-IPDU
configuration) mappings and due to these mappings, ISignals and/or update bits overlap each
other within the PDU.

The communication matrix must specify ISignal-to-IPDU mappings in such a way

that ISignals and update bits do not overlap each other within the PDU.

If you do not resolve this conflict, default code is generated, i.e., the run-time
behavior depends on the PDU direction:
§ TX PDU: It is undefined which signal value is written last to the PDU bits that
are affected by the overlapping ISignals and/or update bits. Therefore, the

299
May 2024 ConfigurationDesk Conflicts
Conflicts

run-time behavior is undefined when the affected PDU is transmitted on the

bus.
§ RX PDU: All the signals that are available in a PDU are extracted separately.
Therefore, the values of the PDU bits that are affected by the overlapping
ISignals and/or update bits apply to each of the affected ISignals and update
bits.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

Note

Tip

To access the coded Base data type property of an ISignal in the

Properties Browser, right-click the ISignal in the Conflicts Viewer
and select Select Related Elements in Bus Configurations Table
from the context menu.

300
ConfigurationDesk Conflicts May 2024
PDU Triggering Conflicts

PDU: Overlapping ISignals A communication matrix specifies ISignal-to-IPDU mappings for a PDU and due
and/or update bits to these mappings, ISignals and/or update bits overlap each other within the
(communication matrix) PDU.

The communication matrix must specify ISignal-to-IPDU mappings in such a way

that ISignals and update bits do not overlap each other within the PDU.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify suitable values for the Length, Start bit position, and/or Endianness
properties of the conflicting ISignals, for example, in the Conflicts Viewer.
This changes the communication matrix in the active ConfigurationDesk
application and all element instances in all bus configurations of
the application. The originally imported communication matrix remains
unchanged.

Note

PDU Triggering Conflicts

PDU triggering: Invalid cyclic A conflicting communication matrix element is assigned to a bus configuration.
timing (bus configuration) For the cyclic timing of an assigned PDU, the communication matrix specifies at
least one of the following settings:
§ No time period (cycle time) is specified or a specified time period is invalid.
§ A specified time offset (delay time) is invalid.

301
May 2024 ConfigurationDesk Conflicts
Conflicts

For each cyclic timing of a PDU, the communication matrix must specify a time
period in in the range 0 … 3600 seconds. If a time period of 0 is specified,
the cyclic timing of the PDU is disabled and the PDU cannot be transmitted
according to this cyclic timing. If the communication matrix specifies a time
offset, it must also be in the range 0 … 3600 seconds.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

§ If you do not need the conflicting element in the executable application,
remove it from the bus configuration: In the Conflicts Viewer, set the
element's Is assigned property to False to remove only this conflicting
element. Alternatively, set the bus configuration's Is assigned property to
False to remove all conflicting elements in one step.
Depending on the type of the conflicting element, related elements are
removed as well, e.g., all ISignals of a conflicting ISignal IPDU.
§ If you need the conflicting element in the executable application, choose one
of the following alternatives:
§ Resolve the conflict only for the active ConfigurationDesk application:
Specify valid values for the Time Period and/or Time Offset elements of
the PDU, for example, in the Conflicts Viewer. If the Conflicts Viewer
does not display configurable properties, no time period is specified. In this
case, add a Time Period element to the PDU via the Properties Browser.
Alternatively, add the PDU Cyclic Timing Control, PDU Trigger, or Frame
Access feature to the PDU. If the communication matrix specifies a global
time domain for the PDU, you can also assign the global time domain
element to the bus configuration. For more information, refer to:
Bus Manager in ConfigurationDesk: Configurable Settings of PDUs
(ConfigurationDesk Bus Manager Implementation Guide ), Controlling
the Cyclic Timing of CAN PDUs (ConfigurationDesk Bus Manager
Implementation Guide ), Specifying User-Defined Triggers for Transmitting
PDUs (ConfigurationDesk Bus Manager Implementation Guide ),
Accessing CAN Frame Settings (ConfigurationDesk Bus Manager
Implementation Guide ), or Simulating Time Masters and Time Slaves
of Global Time Domains (ConfigurationDesk Bus Manager Implementation
Guide ) respectively.
Bus Manager (stand-alone): Configurable Settings of PDUs (Bus Manager
(Stand-Alone) Implementation Guide ), Controlling the Cyclic Timing
of CAN PDUs (Bus Manager (Stand-Alone) Implementation Guide ),
Specifying User-Defined Triggers for Transmitting PDUs (Bus Manager (Stand-
Alone) Implementation Guide ), Accessing CAN Frame Settings (Bus
Manager (Stand-Alone) Implementation Guide ), or Simulating Time
Masters and Time Slaves of Global Time Domains (Bus Manager (Stand-
Alone) Implementation Guide ), respectively.
Specifying valid values for the Time Period or Time Offset elements or
adding a Time Period element to the PDU changes the communication

302
ConfigurationDesk Conflicts May 2024
PDU Triggering Conflicts

matrix in the active ConfigurationDesk application and all PDU instances

in all bus configurations of the application. The originally imported
communication matrix remains unchanged. Adding a feature to the PDU
or assigning a global time domain element changes only the related bus
configuration. Other bus configurations and the communication matrix are
not affected.

Tip

The Conflicts Viewer displays the PDU triggering and not the PDU
itself. To access the related PDU, right-click the PDU triggering and
select Select Related Elements in Bus Configurations Table from
the context menu.

§ Resolve the conflict by correcting the original communication matrix. Refer

PDU triggering: Invalid A communication matrix specifies a cyclic timing for a PDU with at least one of
cyclic timing (communication the following settings:
matrix) § No time period (cycle time) is specified or a specified time period is invalid.
§ A specified time offset (delay time) is invalid.

For each cyclic timing of a PDU, the communication matrix must specify a time
period in the range 0 … 3600 seconds. If a time period of 0 is specified,
the cyclic timing of the PDU is disabled and the PDU cannot be transmitted
according to this cyclic timing. If the communication matrix specifies a time
offset, it must also be in the range 0 … 3600 seconds.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Remedy Choose one of the following alternatives:

§ Resolve the conflict only for the active ConfigurationDesk application:
Specify valid values for the Time Period and/or Time Offset elements of the
PDU, for example, in the Conflicts Viewer. If the Conflicts Viewer does not
display configurable properties, no time period is specified. In this case, add a
Time Period element to the PDU via the Properties Browser. This changes
the communication matrix in the active ConfigurationDesk application and all
element instances in all bus configurations of the application. The originally
imported communication matrix remains unchanged.
For more information, refer to:
§ Bus Manager in ConfigurationDesk: Configurable Settings of PDUs
(ConfigurationDesk Bus Manager Implementation Guide ).

303
May 2024 ConfigurationDesk Conflicts
Conflicts

§ Bus Manager (stand-alone): Configurable Settings of PDUs (Bus Manager

(Stand-Alone) Implementation Guide ).

Tip

The Conflicts Viewer displays the PDU triggering and not the PDU itself.
If the names of the PDU and the PDU triggering match, you can use
the displayed PDU triggering name to search for the PDU via the Find
command, for example.

Processing Unit Application Conflicts

Processing unit application: The executable application contains two or more processing unit applications
Duplicate name with the same name.

The names of processing unit applications must be unique.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, enter unique names in the
Name edit field for the processing unit applications.

Processing unit application: There is no application process defined in the processing unit application.
No application process
A processing unit application must have at least one application process.
defined
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Depending on your use scenario, create a new application process

by using one of the following commands:
§ If the model topology already contains a model to be used in the application:

304
ConfigurationDesk Conflicts May 2024
Processing Unit Application Conflicts

Right-click the model in the Model Browser and select Create

Preconfigured Application Process - In Existing Processing Unit
Application - <Processing unit application> from the context menu.
§ If the model topology does not contain a model:
Right-click the empty space in the Task Configuration table and add
one or more models using the Add Model command. Select Create
one preconfigured application process for each model or Create one
application process for all models and Optimize configuration in the Add
Model dialog.
§ If you want to model the executable application from scratch:
Right-click the processing unit application in the Processing Resource
Assignment table, and select New - Application Process or New -
Application Process (Providing default task).

Processing unit application: The processing unit application has no processing unit assigned.
No processing unit assigned
Each processing unit application must have a processing unit assigned on which
it is executed.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – – – –

Remedy Add a processing unit in the Hardware Resources Browser. In the

Conflicts Viewer, for example, assign a processing unit to the processing unit
application via the Assigned processing unit list.

Processing Unit Application: The number of application processes in the processing unit application exceeds
There are more application the number of processor cores available in the assigned processing unit.
processes than available
Effects
processor cores
Abort Warning Generate Generate Abort BSC Warning Abort
Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – – –

Remedy Choose one of the following alternatives:

§ Assign a processing unit that has a sufficient number of processor cores to the
processing unit application.
§ Reduce the number of application processes in the processing unit application.

305
May 2024 ConfigurationDesk Conflicts
Conflicts

Processing Unit Conflicts

Processing unit: Multiple Several processing unit applications are assigned to the same processing unit.
assignments to different
Only one processing unit application is allowed per processing unit.
processing unit applications
Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Processing Resource Assignment table, for example, assign

excess processing unit applications to unassigned processing units.

Runnable Function Conflicts

Runnable function: The BusCfg_MainFunctionFetch [<bus configuration name>] and

Mismatching assignments to BusCfg_MainFunctionDeliver [<bus configuration name>] runnable
tasks functions of the same bus configuration are assigned to different tasks. For the
timer events of the tasks, different periods are specified.

To ensure predictable run‑time behavior, the BusCfg_MainFunctionFetch

[<bus configuration name>] and BusCfg_MainFunctionDeliver [<bus
configuration name>] runnable functions should be assigned to the same
task. This is the recommended configuration. If the runnable functions are
assigned to different tasks, the periods of the related time events should be
identical.

For more information on the runnable functions, refer to:

§ Bus Manager in ConfigurationDesk: Fetch and Deliver Runnable Functions
for Receiving and Transmitting PDUs (ConfigurationDesk Bus Manager
Implementation Guide ).
§ Bus Manager (stand‑alone): Fetch and Deliver Runnable Functions for
Receiving and Transmitting PDUs (Bus Manager (Stand-Alone) Implementation
Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Choose one of the following alternatives:

§ Assign the runnable functions to the same task, for example, in the Conflicts
Viewer.

306
ConfigurationDesk Conflicts May 2024
Signal Chain Conflicts

§ Specify identical periods: Select the tasks, for example, in the Task
Configuration table. In the Properties Browser, specify identical values for
the Period property of the related timer events.

Runnable function: Multiple A runnable function is assigned to two or more tasks in an application process.
assignments to different tasks
A runnable function must not be assigned to several tasks.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, select only one task in the Value column
(next to the Assigned to field) to assign the runnable function to.

Runnable function: No task A component that is assigned to an application process provides a runnable
assignment function that is not assigned to a task. That means, that the runnable function is
never called during simulation.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, select a task in the Value column (next to the
Assigned to field) to assign the runnable function to.
§ In the Task Configuration table, select the Optimize Configuration
command from the context menu of the application process that contains
the runnable function. ConfigurationDesk then assigns unassigned runnable
functions to suitable tasks. If no suitable tasks exist, ConfigurationDesk creates
new tasks for unassigned runnable functions.

Signal Chain Conflicts

Signal chain: Duplicate In the signal chain, two ports are connected by a mapping line twice.
mapping line
ConfigurationDesk does not support duplicate mappings.

307
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, select one of the mapping lines and press
Del to remove it.

Signal chain: Mismatching The failure simulation settings of a signal port and mapped device port(s) do not
failure simulation settings match for one of the following reasons:
§ One or more failure class(es) that are set to Allowed at a signal port are
not set to Allowed at a device port that is directly or indirectly mapped
to it. This means that the failure class(es) are not available for the affected
signal during failure simulation in your experiment software. For details,
refer to Specifying Failure Simulation Settings (ConfigurationDesk Real-Time
Implementation Guide ).
§ A load signal port is mapped to a device port of a Load device type and
Load rejection is set to Not enforced at the signal port of the same function
block, while Load rejection is set to Enforced at the mapped device port.
For details, refer to Basics on Load Rejection (ConfigurationDesk Real-Time
Implementation Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, for example, change the failure simulation settings of
the device and/or signal port(s) so that none of the conditions described above
is met.
§ If the conflict results from an erroneous device port mapping: In a working
view, remove the mapping causing the conflict by using the context menu
command Delete from Application.

Signal chain: Unresolved There are unresolved model port blocks in the currently active ConfigurationDesk
model port block application.

Unresolved model port blocks can result from the following actions:
§ They were added to the signal chain via function blocks.
§ They were removed from the behavior model linked to your active application
and afterwards the interface of the behavior model was reanalyzed by
ConfigurationDesk.
§ The model port block is used in a multimodel application and resides with
the same identity in two or more behavior models linked to your active

308
ConfigurationDesk Conflicts May 2024
Task Conflicts

ConfigurationDesk application. Additionally, two or more of these behavior

models are assigned to an application process.
In addition this unresolved model port block is marked with an icon.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – – –

Remedy Choose one of the following alternatives:

§ To resolve unresolved model port blocks, you must generate and analyze the
model interface. For details, refer to Transferring the ConfigurationDesk Model
Interface to a New Simulink Interface Model (ConfigurationDesk Real-Time
Implementation Guide ).
§ If you no longer need the unresolved model port blocks, you can remove them
from the application. To do so, right-click the blocks in the Model Browser
or in a working view and select Delete from Application from the context
menu.

Task Conflicts

Task: Unfavorable bus Bus monitoring is activated for an asynchronous task.

monitoring configuration for
Bus monitoring must not be activated for asynchronous tasks, but only for
an aperiodic task
periodic tasks.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Deactivate bus monitoring for the asynchronous task. If required,

activate it for a periodic task in the relevant application process.

Task: Invalid number of An Any Error Hook event of the FlexRay function block is assigned to a task
accepted overruns whose Number of accepted overruns property is set to a value other than -1.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

309
May 2024 ConfigurationDesk Conflicts
Conflicts

Remedy In the Conflicts Viewer, for example, enter -1 for the Number of
accepted overruns property of the related task.

Task: Mismatching event A runnable function has a cycle time restriction (refer to Basics on Modeling
period and runnable function Tasks in ConfigurationDesk (ConfigurationDesk Real-Time Implementation
cycle time restriction Guide )), and the event type triggering the corresponding task is one of the
following:
§ Case 1: A timer event with a mismatching Period value specified
§ Case 2: An event other than a timer event, or a software event. In this case,
ConfigurationDesk cannot detect if the event has the required properties.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy
§ Case 1: In the Properties Browser, enter the value indicated for the cycle
time restriction provided by the runnable function in the Period edit field of
the timer event.
§ Case 2: Assign a timer event or software event to the task.

Note

If you are sure that the task is triggered correctly by the assigned I/O
event, you can ignore this conflict.

Task: Mismatching task The executable application contains tasks assigned to an application process
priority and runnable that do not correspond to the task priority restrictions provided by the runnable
function priority restriction functions that are called by the tasks. For details, refer to Basics on Modeling
Tasks in ConfigurationDesk (ConfigurationDesk Real-Time Implementation
Guide ).

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy In the Conflicts Viewer, for example, specify the task priorities in
the Priority edit field according to the task priority restrictions provided by the
runnable functions called by the tasks.

Task: Multiple events assigned Two or more resolved events are assigned to the task. At least one event
assigned to the task is not an I/O event.

310
ConfigurationDesk Conflicts May 2024
Task Conflicts

If a task has multiple events assigned, all of the assigned events must be I/O
events.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Choose one of the following alternatives:

§ If the task must be triggered by exactly one event, select the event that must
trigger the task from the Assigned events list in the Conflicts Viewer.
§ If the task must be triggered by multiple events, select suitable I/O events from
the Assigned events list in the Conflicts Viewer.

Task: Multiple simulation time There is a Gigalink event (I/O event from a Gigalink function block) assigned
providers (Gigalink and Timer to a task and a timer event assigned to another task belonging to the same
events) in an application application process.
process
Each application process can have only one time provider (Gigalink event or timer
event) in the tasks belonging to it.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, delete the event assigned to one of the conflicting
tasks.
§ Assign an event of the same type or an available asynchronous event to one of
the conflicting tasks.

Task: Multiple Tasks triggered Two or more tasks in an application process have a Gigalink event (I/O event
by Gigalink events in an from a Gigalink function block) assigned to them.
application process
An application process can have only one task with assigned Gigalink events.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
✓ – – – ✓ – –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, delete the Gigalink event assigned to one of the
conflicting tasks.

311
May 2024 ConfigurationDesk Conflicts
Conflicts

§ Assign another of the available events to one of the conflicting tasks.

Task: No event assigned There is a task in an application process that has no event assigned. The task is
not triggered during real-time simulation.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Choose one of the following alternatives:

§ In the Conflicts Viewer, assign an existing event to the task.
§ In the Task Configuration table, create a new timer event for the task via the
New - Timer Event context menu command of the task.

Task: No runnable function There is a task in an application process that does not have any assigned
assigned runnable function. If the task is triggered during simulation, it does not call any
runnable functions.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy In the Conflicts Viewer, assign a runnable function to the task.

Task: Unfavorable runnable The execution order of the runnable functions in a task in a multimodel
function execution order application process might be unfavorable with regard to the interconnection of
the models that provide the relevant runnable functions.

For example, if model A sends data to model B, the runnable functions provided
by model A should be executed before the runnable functions provided by model
B.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy To resolve this conflict, choose one of the following options:

§ In the Task Configuration table, select the Optimize Configuration
command from the context menu of the relevant application process.

312
ConfigurationDesk Conflicts May 2024
Task Group Conflicts

§ In the Conflicts Viewer, specify a suitable runnable function execution order

via the Execution Order property of the related runnable functions.

Task: Unresolved event There is a task within the application process triggered by an event that is not
provided by a component of the application process. This means that the event
is unresolved. The event is ignored during code generation. The task is not
triggered during real-time simulation.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Make sure that the component providing the event is assigned to
the application process. For example, in the Task Configuration table, assign
the model providing the event to the application process.

Task: Unresolved runnable In the application process, a task has a runnable function assigned that is
function not provided by a component of the application process. This means that the
runnable function is unresolved.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy Make sure that the component providing the runnable function is
assigned to the application process. For example, in the Task Configuration
table, assign the model providing the runnable function to the application
process.

Task Group Conflicts

Task group: Invalid priority The synchronization task priority of a FlexRay function block has a value > 0.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – – – ✓ –

Remedy In the Conflicts Viewer, for example, change the priority value.

313
May 2024 ConfigurationDesk Conflicts
Conflicts

Time Master Conflicts

Time master: Invalid property A conflicting communication matrix element is assigned to a bus configuration.
values resulting in default For an assigned time master and its related global time domain, the
code (bus configuration) communication matrix specifies at least one of the following settings:
§ For the Sync period property, no value is specified.
§ For the Debounce time property, no value is specified.
§ The Sync period and the Debounce time properties are specified, but
the specified Sync period value is smaller than <value of Debounce
time · 2>

For each time master and its related global time domain, the communication
matrix must specify values for the Sync period and Debounce time properties
as follows:
<value of Sync period> ≥ <value of Debounce time · 2>

If you do not resolve this conflict, default code is generated, i.e., the run-time
behavior depends on the following:
§ No Sync period value specified: No time synchronization messages are
transmitted, i.e, no synchronization (SYNC) messages and no follow‑up (FUP)
messages.
§ No Debounce time value specified: The next pending PDU providing global
time information is transmitted as soon as possible.
§ Sync period value smaller than <value of Debounce time · 2>: PDUs
providing global time information are transmitted with the smallest possible
synchronization period, which is <value of Debounce time · 2> if there
are no other factors that additionally delay the transmission.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

314
ConfigurationDesk Conflicts May 2024
Time Master Conflicts

Note

This remedy does not resolve the conflict if the conflict cause is an
unspecified Debounce time value.

Refer to:
Bus Manager in ConfigurationDesk: Controlling the Timing of
Time Synchronization (ConfigurationDesk Bus Manager Implementation
Guide ).
Bus Manager (stand-alone): Controlling the Timing of Time Synchronization
(Bus Manager (Stand-Alone) Implementation Guide ).

Tip

The Conflicts Viewer displays the time master and not the global
time domain itself. To access the related global time domain, right-
click the time master and select Select Related Elements in Bus
Configurations Table from the context menu.

Time master: Invalid property A communication matrix specifies at least one of the following settings for a
values resulting in default time master and its related global time domain:
code (communication matrix) § For the Sync period property, no value is specified.
§ For the Debounce time property, no value is specified.
§ The Sync period and the Debounce time properties are specified, but
the specified Sync period value is smaller than <value of Debounce
time · 2>.

For each time master, the communication matrix must specify values for the Sync
period and Debounce time properties as follows:
<value of Sync period> ≥ <value of Debounce time · 2>

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

315
May 2024 ConfigurationDesk Conflicts
Conflicts

Time master: Invalid property A conflicting communication matrix element is assigned to a bus configuration.
values resulting in no code For an assigned time master, the communication matrix specifies invalid values
(bus configuration) for at least one of the following properties:
§ Sync period
§ Debounce time

For each time master, the communication matrix must specify the values of the
Sync period and Debounce time properties in the following range:
§ Sync period: 0 … 4200 seconds
§ Debounce time: 0 … < 4.0 seconds

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Note

This remedy does not resolve the conflict if the conflict cause is an
invalid Debounce time value.

Tip

316
ConfigurationDesk Conflicts May 2024
Time Slave Conflicts

§ Resolve the conflict by correcting the original communication matrix. Refer

Time master: Invalid property A communication matrix specifies invalid values for at least one of the following
values resulting in no code time master properties:
(communication matrix) § Sync period
§ Debounce time

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Time Slave Conflicts

Time slave: Invalid property A conflicting communication matrix element is assigned to a bus configuration.
values (bus configuration) For an assigned time slave, the communication matrix specifies invalid values for
at least one of the following properties:
§ Follow-up timeout value
§ Maximum counter jump width

For each time slave, the communication matrix must specify values for the
Follow-up timeout value and Maximum counter jump width properties in
the following range:
§ Follow-up timeout value: 0 … 4.32 seconds
§ Maximum counter jump width: 1 … 15

317
May 2024 ConfigurationDesk Conflicts
Conflicts

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ ✓ – – ✓ –

Remedy Choose one of the following alternatives:

Time slave: Invalid property A communication matrix specifies invalid values for at least one of the following
values (communication time slave properties:
matrix) § Follow-up timeout value
§ Maximum counter jump width

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

Time slave: Missing property A conflicting communication matrix element is assigned to a bus configuration.
values (bus configuration) For an assigned time slave, the communication matrix does not specify values

318
ConfigurationDesk Conflicts May 2024
Time Slave Conflicts

for the Follow-up timeout value and/or Maximum counter jump width
properties.

For each time slave, the communication matrix must specify values for the
Follow-up timeout value and Maximum counter jump width properties.

If you do not resolve this conflict, default code is generated, i.e., the Bus
Manager uses the following values:
§ Follow-up timeout value: 4 seconds
§ Maximum counter jump width: 15

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– ✓ – ✓ – ✓ –

Remedy Choose one of the following alternatives:

Time slave: Missing property A communication matrix does not specify values for the Follow-up timeout
values (communication value and/or Maximum counter jump width properties.
matrix)
For each time slave, the communication matrix must specify values for the
Follow-up timeout value and Maximum counter jump width properties.

Effects

Abort Warning Generate Generate Abort BSC Warning Abort

Build During No Code Default File During XLSX
Build Code Generation BSC File Export
Gen.
– – – – – – –

319
May 2024 ConfigurationDesk Conflicts
Conflicts

320
ConfigurationDesk Conflicts May 2024

Control Desk Next Generation Platform Management
No ratings yet
Control Desk Next Generation Platform Management
614 pages
System Verilog Interview Questions With Answers
100% (2)
System Verilog Interview Questions With Answers
10 pages
ControlDeskIntroductionAndOverview 5c9cfe49 A7c6 4205 8df0 C317b9a28dea
No ratings yet
ControlDeskIntroductionAndOverview 5c9cfe49 A7c6 4205 8df0 C317b9a28dea
206 pages
Automation Desk Accessing Control Desk
No ratings yet
Automation Desk Accessing Control Desk
108 pages
Configuration Desk Automating Tool Handling
No ratings yet
Configuration Desk Automating Tool Handling
324 pages
Configuration Desk Bus Manager Implementation Guide
No ratings yet
Configuration Desk Bus Manager Implementation Guide
574 pages
Automation Desk Accessing RD Com
No ratings yet
Automation Desk Accessing RD Com
82 pages
D SPACECANAPI20 CReference
No ratings yet
D SPACECANAPI20 CReference
120 pages
Configuration Desk Using Demo Projects
No ratings yet
Configuration Desk Using Demo Projects
82 pages
Control Desk Lay Outing
No ratings yet
Control Desk Lay Outing
162 pages
Automation Desk New Features and Migration
No ratings yet
Automation Desk New Features and Migration
66 pages
Bus Manager Implementation Guide
No ratings yet
Bus Manager Implementation Guide
566 pages
Control Desk Introduction and Overview
No ratings yet
Control Desk Introduction and Overview
160 pages
Micro Auto Box I Irt Lib Reference
No ratings yet
Micro Auto Box I Irt Lib Reference
1,240 pages
Control Desk Bus Navigator
No ratings yet
Control Desk Bus Navigator
374 pages
D SPACEBus APIManual
No ratings yet
D SPACEBus APIManual
234 pages
Automation Desk Accessing Model Desk
No ratings yet
Automation Desk Accessing Model Desk
68 pages
Control Desk Customization
No ratings yet
Control Desk Customization
110 pages
Ds 1104 Hardware Installation Configuration
No ratings yet
Ds 1104 Hardware Installation Configuration
112 pages
Micro Auto Box IISoftware Getting Started
No ratings yet
Micro Auto Box IISoftware Getting Started
72 pages
Installingd SPACESoftware
No ratings yet
Installingd SPACESoftware
96 pages
FPGAProgramming Software Message Reference
No ratings yet
FPGAProgramming Software Message Reference
148 pages
Configuration Desk Syntax TRCfile
No ratings yet
Configuration Desk Syntax TRCfile
44 pages
Bus Custom Code Interface Handling
No ratings yet
Bus Custom Code Interface Handling
180 pages
Flex Ray Configuration Features
No ratings yet
Flex Ray Configuration Features
100 pages
DS1104 Software Getting Started
No ratings yet
DS1104 Software Getting Started
64 pages
Using COMIn Automation Desk Application Note
No ratings yet
Using COMIn Automation Desk Application Note
30 pages
Mab Xin ST Config
0% (1)
Mab Xin ST Config
268 pages
D Space Install
No ratings yet
D Space Install
52 pages
Micro Auto Box IIRTIReference
No ratings yet
Micro Auto Box IIRTIReference
448 pages
Micro Lab Box Features
No ratings yet
Micro Lab Box Features
166 pages
Micro Auto Box Features
No ratings yet
Micro Auto Box Features
532 pages
Automation Desk Accessing RC Com
No ratings yet
Automation Desk Accessing RC Com
86 pages
Installing D Space Software
No ratings yet
Installing D Space Software
108 pages
Using Virtual COMIn Automation Desk Application Note
No ratings yet
Using Virtual COMIn Automation Desk Application Note
28 pages
DSETHRTLib Reference
No ratings yet
DSETHRTLib Reference
50 pages
Bus Manager Tutorial
No ratings yet
Bus Manager Tutorial
230 pages
Control Desk Calibration and Data Set Management
No ratings yet
Control Desk Calibration and Data Set Management
168 pages
D SPACESimulator Mid Size Features
No ratings yet
D SPACESimulator Mid Size Features
216 pages
204.4295.65 - DmOS - Release Notes - 8.6.4 - English
No ratings yet
204.4295.65 - DmOS - Release Notes - 8.6.4 - English
35 pages
Getting Started With XILMapping
No ratings yet
Getting Started With XILMapping
48 pages
Ds 1104 in ST Config
100% (1)
Ds 1104 in ST Config
120 pages
Genconfig 3 1 0 Global Guide
No ratings yet
Genconfig 3 1 0 Global Guide
148 pages
204.4295.36 - DmOS - Release Notes - 5.0.0 - English
No ratings yet
204.4295.36 - DmOS - Release Notes - 5.0.0 - English
27 pages
553 3001 156 - 14.00
No ratings yet
553 3001 156 - 14.00
134 pages
204.4295.51 - DmOS - Release Notes - 5.0.4 - English
No ratings yet
204.4295.51 - DmOS - Release Notes - 5.0.4 - English
24 pages
204.4295.52 - DmOS - Release Notes - 7.2.0 - English
No ratings yet
204.4295.52 - DmOS - Release Notes - 7.2.0 - English
27 pages
Automation Desk Accessing Motion Desk
No ratings yet
Automation Desk Accessing Motion Desk
30 pages
Control Desk MCD 3 Automation
No ratings yet
Control Desk MCD 3 Automation
132 pages
Device-Gui-2.11 Relnote Rev A
No ratings yet
Device-Gui-2.11 Relnote Rev A
16 pages
IDX 4.1.2 - Release Notes
No ratings yet
IDX 4.1.2 - Release Notes
94 pages
204.4295.82 - DmOS - Release Notes - 10.4.4 - English
No ratings yet
204.4295.82 - DmOS - Release Notes - 10.4.4 - English
40 pages
204.4295.670 - DmOS - Release Notes - 9.0.0 - English
No ratings yet
204.4295.670 - DmOS - Release Notes - 9.0.0 - English
40 pages
Release Notes: For iDX Release 4.1.2.x
No ratings yet
Release Notes: For iDX Release 4.1.2.x
90 pages
D SPACEInternal Bypassing Service Implementation
No ratings yet
D SPACEInternal Bypassing Service Implementation
34 pages
204.4295.40 - DmOS - Release Notes - 5.6.0 - English
No ratings yet
204.4295.40 - DmOS - Release Notes - 5.6.0 - English
24 pages
Control Desk Instrument Handling
No ratings yet
Control Desk Instrument Handling
802 pages
RN iDX 4.1.2.x. T0001050 RevE 03 20 20
No ratings yet
RN iDX 4.1.2.x. T0001050 RevE 03 20 20
94 pages
Installing and Maintaining Operator Workplace Electronics
No ratings yet
Installing and Maintaining Operator Workplace Electronics
280 pages
Matlab M Files Tutorial
No ratings yet
Matlab M Files Tutorial
16 pages
2024-09-24 - Model-Based Design in The Context of ISO 26262
No ratings yet
2024-09-24 - Model-Based Design in The Context of ISO 26262
33 pages
Modelportblockfrom A Functionblock
No ratings yet
Modelportblockfrom A Functionblock
6 pages
MBD HIL Interview Questions Mohamed Azarudeen
No ratings yet
MBD HIL Interview Questions Mohamed Azarudeen
2 pages
FPGAProgramming Blockset FPGAInterface Reference
No ratings yet
FPGAProgramming Blockset FPGAInterface Reference
714 pages
F Pga Programming Block Set Getting Started
No ratings yet
F Pga Programming Block Set Getting Started
52 pages
FPGAProgramming Handcode Framework FPGAInterface Reference
No ratings yet
FPGAProgramming Handcode Framework FPGAInterface Reference
496 pages
F Pga Programming Block Set Guide
No ratings yet
F Pga Programming Block Set Guide
270 pages
Demo VCFP
No ratings yet
Demo VCFP
26 pages
Control Desk Electrical Error Simulation
No ratings yet
Control Desk Electrical Error Simulation
206 pages
Automation Desk Accessing Mat Lab
No ratings yet
Automation Desk Accessing Mat Lab
58 pages
D SPACECalibration and Bypassing Service Implementation
No ratings yet
D SPACECalibration and Bypassing Service Implementation
142 pages
Ethernet
No ratings yet
Ethernet
11 pages
An Open Framework For Highly Concurrent Hardware-In-The-Loop Simu
No ratings yet
An Open Framework For Highly Concurrent Hardware-In-The-Loop Simu
52 pages
(BOSCH2002) BOSCH Automotive Handbook
No ratings yet
(BOSCH2002) BOSCH Automotive Handbook
1,391 pages
Victory School Club Business Plan 20pages
No ratings yet
Victory School Club Business Plan 20pages
20 pages
Side Dump Book 2014
No ratings yet
Side Dump Book 2014
36 pages
Topic 1 - Problem Domain of Artificial Intelligence
100% (1)
Topic 1 - Problem Domain of Artificial Intelligence
21 pages
Nokia 6100 LCD Display Driver
No ratings yet
Nokia 6100 LCD Display Driver
55 pages
Abc Company
No ratings yet
Abc Company
4 pages
1 Introduction To Servlets
No ratings yet
1 Introduction To Servlets
32 pages
Commonmeccheme
No ratings yet
Commonmeccheme
3 pages
Jeremy Quigg 062812
No ratings yet
Jeremy Quigg 062812
2 pages
RE L02 System Context Boundaries and Types of Requirements
No ratings yet
RE L02 System Context Boundaries and Types of Requirements
51 pages
Ford 1977
No ratings yet
Ford 1977
16 pages
Bionic Build - Prop
100% (1)
Bionic Build - Prop
6 pages
Assignment 4: Self-Excited Compound-Wound DC Generator
No ratings yet
Assignment 4: Self-Excited Compound-Wound DC Generator
11 pages
Elation 48ch
No ratings yet
Elation 48ch
36 pages
DS 3WR15X - 1500Mbps Wi Fi 6 Router - 20230310
No ratings yet
DS 3WR15X - 1500Mbps Wi Fi 6 Router - 20230310
4 pages
47-Control Instrumentation Brochure
No ratings yet
47-Control Instrumentation Brochure
12 pages
100 Cyber Threats
No ratings yet
100 Cyber Threats
103 pages
Vacuum Pump: Oil-Free Pump With Constant Suction Rate, Robust, Requires Little Maintenance
No ratings yet
Vacuum Pump: Oil-Free Pump With Constant Suction Rate, Robust, Requires Little Maintenance
3 pages
Energie: Industrial Energy Management System DIA
No ratings yet
Energie: Industrial Energy Management System DIA
16 pages
MigrationManagerAD Guide
No ratings yet
MigrationManagerAD Guide
67 pages
Design and Calculation of Planetary Transmission W
No ratings yet
Design and Calculation of Planetary Transmission W
8 pages
Q1 W6 MIL Types of Media
No ratings yet
Q1 W6 MIL Types of Media
5 pages
Research Methodology
No ratings yet
Research Methodology
21 pages
Monolithic IC-Component Fabrication
100% (2)
Monolithic IC-Component Fabrication
6 pages
Syllabus of Digital Electronics 1 - Logic Circuits and Switching Theory
No ratings yet
Syllabus of Digital Electronics 1 - Logic Circuits and Switching Theory
4 pages
Z 1 DC Inverter VRF System Technical Manual 3 Units Selection V2.0 140703
No ratings yet
Z 1 DC Inverter VRF System Technical Manual 3 Units Selection V2.0 140703
7 pages
rfc430 Interbus
No ratings yet
rfc430 Interbus
128 pages
Structural and Vibrational Analysis of Six Axis ARISTO Robot Using ANSYS
No ratings yet
Structural and Vibrational Analysis of Six Axis ARISTO Robot Using ANSYS
6 pages
GR 07
No ratings yet
GR 07
6 pages
NRT Z43 Firmware Upgrade
No ratings yet
NRT Z43 Firmware Upgrade
2 pages