Using Behavior Modeling

You can use the behavior modeler BME based on the Modelica language to logically define various resources such as NC machines, robots, humans, or stations.

When you open data created in previous versions, a message is displayed indicating that data must be migrated using the DELMIABehaviorModelerMigration batch.

To customize compilation for simulation, use the options available in Me > Preferences > App Preferences > Simulation > Digital Manufacturing Apps Common Services > Live Simulation Common Services > Compiler. For more information, see Compiler.

This task shows you how to:

Install the C++ Compiler
Install the C++ Compiler from Visual Studio 2010
Migrate Data Using a Batch

Install the C++ Compiler

Modelica requires a C++ compiler, such as Visual Studio or MinGW64 (GCC).

Note that:

Running performances are similar between Express and Professional editions of Visual Studio
The initialization step ratio between Visual Studio and GCC is 2.5

It is recommended to use the following compilers:


C Compiler	Init	Play Forward 80s
Visual Studio 2015 Express Edition for Windows Desktop (14.0) - FREE	20s	1m 16s
MinGW64 4.9.2 GCC - FREE	59s	1m 43s
Visual Studio 2015 Professional Edition (14.0)	20s	1m 16s

Before you begin: To install Visual Express, create an account on Microsoft website.

To install Visual Express, select one of the following links:
1. If Visual Studio Compiler is not automatically recognized, select Customized Visual Studio Path in Me > Preferences > Infrastructure > DELMIA Infrastructure > Compiler, and enter the destination folder path to Vc: C:\ProgramFiles(x86)\Microsoft Visual Studio 14.0\Vc
2. Click Test Compiler to check that the compiler is correctly configured.
To install MinGW64 GCC:
1. Download the compiler from sourceforge
2. Start the generic MinGW installer, then specify the following parameters:
  - Version: 4.9.2
  - Architecture: x86_64
  - Threads: posix
  - Exception: she
3. Install MinGW64 GCC on C:\mingw-w64\
4. In Me > Preferences > Infrastructure > DELMIA Infrastructure > Compiler, select the 64-bit option under MinGw GCC Full Path, and enter the destination folder path to gcc.exe: C:\mingw-w64\mingw64\bin\gcc.exe
5. Click Test Compiler to check that the compiler is correctly configured.

Install the C++ Compiler from Visual Studio 2010

Modelica requires a C++ compiler, such as GCC, MinGW, or Visual Express. The following scenario illustrates how to install a C++ compiler from Visual Studio 2010 Express onto a 64bit system. Visual Studio 2010 Professional editions include native 64bit C compiler, so the following procedure is not required.

Install Visual C++ 2010 Express from www.microsoft.com.
Install Windows SDK 7.1 from www.microsoft.com.
Install the following VC-Compiler update: KB2519277 from www.microsoft.com.
Create vcvars64.bat at C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64 with the following content: CALL "C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd" /x64
The C++ compiler is installed.
Test the compiler using the Test Compiler option under Verify Compiler Setup in Me > Preferences > App Preferences > Simulation > Digital Manufacturing Apps Common Services > Live Simulation Common Services > Compiler..

The C++ compiler is installed and can be selected as the default compiler in Me > Preferences > App Preferences > Simulation > Digital Manufacturing Apps Common Services > Live Simulation Common Services > Compiler..

Note: An unavailable compiler indicates that the compiler has not been installed on to the system. Availability is based on a default access path check. If the default compiler has been changed during installation, select the Customized Visual Studios Path option and select the appropriate access path.

The table below lists compilers that can be used with Modelica.
V6R2016x and following		GCC	Visual Studio / Visual C++
		MinGW GCC	VS 2013 Pro	VS 2013 Express	VS 2012 Pro	VS 2012 Express	VS 2010 Pro	VC 2010 Express	VS 2008 Pro (9.0)	VC 2008 Express
	Windows 7 64bits	MinGW 32bit GCC: Version 4.8.1 MinGW 64bit GCC: Version 4.9.2	Visual C++ 2013, version 12.0.21005.1 REL	Visual C++ 2013, version 12.0.21005.1 REL	Visual Studio 2012 Update 4 including C/C++ compilers, with the following patches: KB2929731, KB2957527, KB2969618	Visual Studio 2012 Update 4 including C/C++ compilers, with the following patches: KB2929731, KB2957527, KB2969618	2010 SP1, with the following patches: KB2566268, KB2670561, KB2740362	2010 SP1, with the following patches: KB2566268, KB2670561, KB2740362, and Windows SDK 7.1 and VC-Compiler-KB2519277 with vcvars64.bat	9.0.30729.4108 QFE with the following patches: KB945140 (that is, SP1), KB967211, KB968338, KB971672, KB957912, KB969394, KB960075-v2, KB975919, KB979335	Not supported.
	Windows 8.1 64bits	MinGW 32bit GCC: Version 4.8.1 MinGW 64bit GCC: Version 4.9.2	Visual C++ 2013, version 12.0.21005.1 REL	Visual C++ 2013, version 12.0.21005.1 REL	Visual Studio 2012 Update 4 including C/C++ compilers, with the following patches: KB2929731, KB2957527, KB2969618	Visual Studio 2012 Update 4 including C/C++ compilers, with the following patches: KB2929731, KB2957527, KB2969618	2010 SP1, with the following patches: KB2566268, KB2670561, KB2740362	2010 SP1, with the following patches: KB2566268, KB2670561, KB2740362, and Windows SDK 7.1 and VC-Compiler-KB2519277 with vcvars64.bat	9.0.30729.4108 QFE with the following patches: KB945140 (that is, SP1), KB967211, KB968338, KB971672, KB957912, KB969394, KB960075-v2, KB975919, KB979335	Not supported.
	Windows 10 64bits	MinGW 32bit GCC: Version 4.8.1 MinGW 64bit GCC: Version 4.9.2	Visual C++ 2013, version 12.0.21005.1 REL	Visual C++ 2013, version 12.0.21005.1 REL	Visual Studio 2012 Update 4 including C/C++ compilers, with the following patches: KB2929731, KB2957527, KB2969618	Visual Studio 2012 Update 4 including C/C++ compilers, with the following patches: KB2929731, KB2957527, KB2969618	2010 SP1, with the following patches: KB2566268, KB2670561, KB2740362	2010 SP1, with the following patches: KB2566268, KB2670561, KB2740362, and Windows SDK 7.1 and VC-Compiler-KB2519277 with vcvars64.bat	9.0.30729.4108 QFE with the following patches: KB945140 (that is, SP1), KB967211, KB968338, KB971672, KB957912, KB969394, KB960075-v2, KB975919, KB979335	Not supported.

Migrate Data Using a Batch

You can analyze, emulate, or migrate a database or specific data sets created in previous versions, using a batch. You can migrate data in any maturity state provided you have the administrator rights. If you do not have the administrator rights, only data with a maturity of in Work is migrated.

For details on how to define batch parameters, see 3DEXPERIENCE Native Apps Native Apps Common Services: Tools: Batches: Defining the Batch Parameters.

Run CATUTIL:
- From the console: mkrun -c CATUTIL
- From the 3DEXPERIENCE platform:On the Tools section of the action bar, click Utility .
In the Batch Monitor, double-click DELMIABehaviorModelerMigration.
In the dialog box that opens, select one of the following the modes:
- ANALYSE: Searches PLM objects to migrate and compute the scope of the migration based on the selection. Only representations matching a subset of disciplines are taken into account.
  - No selection: All representations with compatible disciplines will be treated.
  - Rep selection: Representations with compatible disciplines will be treated.
  - Ref selection: All representations with compatible disciplines and belonging to the same reference will be treated. For example, all the representations belonging to the same PPR node.
  Note: To see if a PLM object contains LCM code, perform an Open operation.
- EMULATE: Searches and loads integrity sets (lists of interconnected workspaces) in the database. This mode allows you to load a minimal set of components instead of the whole product structure. This mode emulates the migration of the entire database without impacting the content.
- MIGRATE: Searches and loads integrity sets (lists of interconnected workspaces) in the database. This mode allows you to load a minimal set of components instead of the whole product structure. This mode migrates the entire database.
To migrate one specific data set, click Open Main HTML Report to identify PLM objects to migrate. In the TST Object Management dialog box:
1. From the Object list, select a PLM object.
2. From the Extension list, select a clause.
3. Select Apply to apply the query.
4. Select OK.
Each selected object is treated one by one.
Note: If no PLM objects are selected, the entire database is migrated.
Select Search Object to open an automatically generated report. According to the mode selected, the report summarizes the number of PLM objects to migrate and to be migrated, or the integrity sets migrated. The report also generates a summary of the results.
Select Save to save your changes without running the migration, or select Run to run the migration batch.

The batch is launched and the database or selected data sets are migrated.