dspace Release New Features and Migration

Transcription

1 dspace Release New Features ad Migratio Release 7.4 November 2012

2 How to Cotact dspace Mail: dspace GmbH Ratheaustraße Paderbor Germay Tel.: Fax: Web: How to Cotact dspace Support There are differet ways to cotact dspace Support: Visit our website at Sed a or phoe: Geeral Techical Support: [email protected] TargetLik Support: [email protected] Use the dspace Istallatio Maager: O your dspace DVD at \Tools\IstallatioMaager Via Start Programs dspace Istallatio Maager (after istallatio of the dspace software) At You ca always fid the latest versio of the dspace Istallatio Maager here. dspace recommeds that you use the dspace Istallatio Maager to cotact dspace Support. Software Updates ad Patches dspace strogly recommeds that you dowload ad istall the most recet patches for your curret dspace istallatio. Visit for software updates ad patches. Importat Notice This documet cotais proprietary iformatio that is protected by copyright. All rights are reserved. The documet may be prited for persoal or iteral use provided all the proprietary markigs are retaied o all prited copies. I all other cases, the documet must ot be copied, photocopied, reproduced, traslated, or reduced to ay electroic medium or machie-readable form, i whole or i part, without the prior writte coset of dspace GmbH. Copyright by: dspace GmbH Ratheaustraße Paderbor Germay This publicatio ad the cotets hereof are subject to chage without otice. AutomatioDesk, CalDesk, CofiguratioDesk, CotrolDesk, SCALEXIO, SYNECT, SystemDesk, TargetLik ad VEOS are registered trademarks of dspace GmbH i the Uited States or other coutries, or both. Other brad ames or product ames are trademarks or registered trademarks of their respective compaies or orgaizatios.

3 Cotets About This Documet 9 Documet Symbols ad Covetios...10 Accessig Olie Help ad PDF Files...11 Overview of dspace Release Geeral Ehacemets ad Chages...14 Product Versio Overview...16 New Product Key Features...19 Migratig to dspace Release AutomatioDesk 27 New Features of AutomatioDesk Migratig to AutomatioDesk Automotive Simulatio Models (ASM) 31 All ASM Blocksets...32 New Features of All ASM Blocksets...32 ASM Diesel Egie Blockset...33 New Features of ASM Diesel Egie Blockset Chages i the ASM Diesel Egie Demo Model...33 Migratig to ASM Diesel Egie Blockset ASM Diesel Exhaust Blockset...35 Migratig to ASM Diesel Exhaust Blockset ASM Drivetrai Basic Blockset...35 Migratig to ASM Drivetrai Basic Blockset ASM Electric Compoets Blockset...36 Migratig to ASM Electric Compoets Blockset ASM Eviromet Blockset...37 New Features of ASM Eviromet Blockset Migratig to ASM Eviromet Blockset ASM Egie Gasolie Basic Blockset...38 New Features of ASM Egie Gasolie Basic Blockset Chages i the ASM Egie Gasolie Basic Demo Model...38 Migratig to ASM Egie Gasolie Basic Blockset New Features ad Migratio November

4 Cotets ASM Egie Gasolie Blockset New Features of ASM Egie Gasolie Blockset Chages i the ASM Egie Gasolie Demo Model Migratig to ASM Egie Gasolie Blockset ASM Optimizer Migratig to ASM Optimizer Blockset ASM Traffic Blockset Migratig to ASM Traffic Blockset ASM Trailer Blockset New Features of ASM Trailer Blockset Migratig to ASM Trailer Blockset ASM Truck Blockset Chages i the ASM Truck Demo Model Migratig to ASM Truck Blockset ASM Turbocharger Blockset Migratig to ASM Turbocharger Blockset ASM Vehicle Dyamics Blockset New Features of ASM Vehicle Dyamics Blockset Migratig to ASM Vehicle Dyamics Blockset CofiguratioDesk 49 CofiguratioDesk Implemetatio New Features of CofiguratioDesk Migratig Projects from CofiguratioDesk 4.2 (o dspace Release 7.3) or Earlier Cotaier Maager 55 New Features of the Cotaier Maager CotrolDesk 3.x 57 New Features of CotrolDesk Migratig to CotrolDesk CotrolDesk Next Geeratio 59 New Features of CotrolDesk Next Geeratio (CotrolDesk 4.3) New Geeral Features (CotrolDesk 4.3) New Features of Platform Maagemet ad Platforms/Devices (CotrolDesk 4.3) New Variable Maagemet Features (CotrolDesk 4.3) New Istrumet Features (CotrolDesk 4.3) New Measuremet ad Recordig Features (CotrolDesk 4.3) 70 4 New Features ad Migratio November 2012

5 Cotets New Bus Navigator Features (CotrolDesk 4.3)...70 New Data Set Maagemet Features (CotrolDesk 4.3)...70 New ECU Diagostics Features (CotrolDesk 4.3)...72 New Automatio Features (CotrolDesk 4.3)...73 Migratig to CotrolDesk Next Geeratio (CotrolDesk 4.3)...75 Migratig to CotrolDesk Next Geeratio (CotrolDesk 4.3).75 dspace HIL API.NET 77 New Features of dspace HIL API.NET dspace FlexRay Cofiguratio Package 79 New Features of dspace FlexRay Cofiguratio Package Migratig to dspace FlexRay Cofiguratio Package dspace Pytho Extesios 83 New Features of dspace Pytho Extesios Migratig to dspace Pytho Extesios ECU Iterface Maager 85 New Features of ECU Iterface Maager Migratig to ECU Iterface Maager Model Compare 89 New Features of Model Compare Migratio to Model Compare ModelDesk 91 New Features of ModelDesk MotioDesk 93 New Features of MotioDesk Migratig to MotioDesk RapidPro Cotrol Uit RTI Blockset 97 New Features of the RapidPro Cotrol Uit RTI Blockset...97 Real-Time Testig 99 New Features of Real-Time Testig Migratig to Real-Time Testig New Features ad Migratio November

6 Cotets RTI/RTI-MP ad RTLib 101 New Features of RTI/RTI-MP ad RTLib Migratio Aspects of RTI/RTI-MP ad RTLib RTI Bypass Blockset 105 New Features of the RTI Bypass Blockset Migratig to RTI Bypass Blockset RTI CAN MultiMessage Blockset 109 New Features of the RTI CAN MultiMessage Blockset Migratig to RTI CAN MultiMessage Blockset RTI LIN MultiMessage Blockset 111 New Features of the RTI LIN MultiMessage Blockset Migratig to RTI LIN MultiMessage Blockset RTI FPGA Programmig Blockset 113 New Features of the RTI FPGA Programmig Blockset Migratig to RTI FPGA Programmig Blockset SystemDesk 3.x 117 New Features of SystemDesk New Geeral Features Cofigurig ad Geeratig V-ECUs Simulatig Systems Migratig to SystemDesk Migratig to SystemDesk SystemDesk 4.x 129 New Features of SystemDesk Migratig to SystemDesk TargetLik 131 New Features of TargetLik 3.4 ad TargetLik Data Dictioary New Productio Code Geeratio Features Compoet-Based Developmet Usig Abstract Iterfaces Improvemet for Custom Code Optioal Deactivatio of Compute-Through-Overflow Geeratig Virtual ECUs for Virtual ECU Testig Specificatios of the Target Simulatio Modules Code Geerator Optios New Features ad Migratio November 2012

7 Cotets New API Commads New Hook Fuctios Access Fuctio Chages Improvemet of Code Efficiecy Geeral Ehacemets ad Chages New AUTOSAR-Related Features Features of the TargetLik AUTOSAR Module New TargetLik Data Dictioary Features Compare ad Merge Features Improvemets for Data Dictioary File Hadlig Further Improvemets of the Data Dictioary Maager New DD MATLAB API Commads Migratig to TargetLik 3.4 ad TargetLik Data Dictioary Discotiued Data Dictioary Features Migratig to TargetLik Data Dictioary How to Upgrade a Data Dictioary Without Iclude Files How to Upgrade a Data Dictioary With Iclude Files How to Upgrade Libraries ad Models from TargetLik 2.x to 3.x Code Chages Migratio Aspects Regardig Code Geerator Optios Chages i TargetLik ad TargetLik Data Dictioary API Fuctios Various Migratio Aspects AUTOSAR-Related Migratio Aspects Obsolete Limitatios VEOS 179 New Features of VEOS Compatibility Iformatio 183 Supported MATLAB Releases Operatig System Ru-Time-Compatibility of dspace Software Limitatios for Widows Vista/Widows Limitatios for 64-Bit Widows Operatig Systems i Combiatio with dspace 32-Bit Software Idex 191 New Features ad Migratio November

8 Cotets 8 New Features ad Migratio November 2012

9 About This Documet Cotets This documet iforms you about the ew features of all the dspace software products i Release 7.4. It also gives you a overview of software products with o or mior chages. There are istructios o migratig from earlier dspace releases, especially from earlier product versios, if required. Where to go from here Iformatio i this sectio Documet Symbols ad Covetios 10 Accessig Olie Help ad PDF Files 11 New Features ad Migratio November

10 About This Documet Documet Symbols ad Covetios Symbols The followig symbols may be used i this documet. Idicates a geeral hazard that may cause persoal ijury of ay kid if you do ot avoid it by followig the istructios give. Idicates the dager of electric shock which may cause death or serious ijury if you do ot avoid it by followig the istructios give. Idicates a hazard that may cause material damage if you do ot avoid it by followig the istructios give. Idicates importat iformatio that should be kept i mid, for example, to avoid malfuctios. Idicates tips cotaiig useful iformatio to make your work easier. Namig covetios The followig abbreviatios ad formats are used i this documet: %ame% Names eclosed i percet sigs refer to eviromet variables for file ad path ames, for example, %DSPACE_PYTHON25% is the folder cotaiig the Pytho istallatio. < > Agle brackets cotai wildcard characters or placeholders for variable file ad path ames, etc. Precedes the documet title i a lik that refers to aother documet. Idicates that a lik refers to aother documet, which is available i dspace HelpDesk. 10 New Features ad Migratio November 2012

11 About This Documet Accessig Olie Help ad PDF Files Objective After you istall your dspace software, the documetatio for the istalled products is available as olie help ad Adobe PDF files. Olie help You ca access the olie help, dspace HelpDesk, as follows: Widows Start meu Click Start Programs <ProductName> dspace HelpDesk (<ProductName>) to ope dspace HelpDesk with the start page of the selected product displayed. You ca also avigate ad search i the user documetatio of ay other istalled software product ad its supported hardware. Cotext-sesitive Press the F1 key or click the Help butto i the dspace software to get help o the curretly active cotext. Cotext-sesitive help is ot available i all software products. Help meu i the dspace software From the meu bar, choose Help Cotets or Help Search (ot available i all software products) to ope dspace HelpDesk. It opes at the start page of the curretly active product. You ca also avigate ad search i the user documetatio of ay other istalled software product ad its supported hardware. PDF files You ca access the PDF files as follows: dspace HelpDesk Click the PDF lik at the begiig of a documet: New Features ad Migratio November

12 About This Documet 12 New Features ad Migratio November 2012

13 Overview of dspace Release 7.4 Objective Gives you a overview of the ew key features i Release 7.4, ad also iformatio about uchaged products ad geeral istructios o migratig. Where to go from here Iformatio i this sectio Geeral Ehacemets ad Chages 14 Product Versio Overview 16 New Product Key Features 19 Migratig to dspace Release New Features ad Migratio November

14 Overview of dspace Release 7.4 Geeral Ehacemets ad Chages Objective The followig ew features ad chages cocer several dspace products. Improvig dspace software istallatio As of dspace Release 7.0, improvemets are beig made to the istallatio programs for dspace software. The software architecture has bee redesiged to reduce depedecies betwee products. The aim is to esure that software istallatios have maximal flexibility i istallatio ad maximal ru-time compatibility. This meas that dspace products ca be used i parallel after software istallatio, eve if they are istalled i differet folders. dspace Release 7.4 is a itermediate step towards this aim. Some products do ot yet support all the ew features. For details, refer to Importat Chages ad Improvemets to dspace Setup ( Software Istallatio ad Maagemet Guide). Restrictios whe workig with dspace HelpDesk dspace HelpDesk is istalled i release-specific folders i C:\Program Files\Commo Files\dSPACE. For example, if you have istalled products from dspace Release 7.4 ad products from dspace Release 7.3, there are two dspace HelpDesks available. (RCP ad HIL software still accesses dspace HelpDesk i %DSPACE_ROOT%\Doc.) Note the followig restrictios: If liks to documets do ot work, but retur the error message Selectio is ot associated with ay topics., the possible reasos are: The documets for the product are ot istalled aywhere because the product is ot icluded i your licese key. The documets for the product are istalled i aother dspace HelpDesk. For example, if a product o the curret dspace Release is uchaged, its user documetatio is istalled i the dspace HelpDesk versio that the product setup was created for. Each setup o dspace Release 7.4 istalls its user documetatio i dspace HelpDesk 7.4. If you are ot sure where to fid the user documetatio for your product, use the dspace HelpDesk shortcut i the Widows Start meu to ope the olie help. 14 New Features ad Migratio November 2012

15 Overview of dspace Release 7.4 Release update The prited user documetatio is ot delivered with Release 7.4 if you receive the release as a update for your existig dspace release. Use the curret olie help or PDF files to obtai iformatio about ew features, ehacemets, ad the curret safety precautios regardig your products. Restrictio for usig Microsoft.NET Framework 4.5 Redistributables The software products o dspace Release 7.4 do ot support the Microsoft.NET Framework 4.5 Redistributables. To avoid problems whe usig dspace software: If.NET Framework 4.5 Redistributables is istalled o your host PC, you must uistall it before you istall the dspace software. Do ot istall the framework after istallig dspace software. New Features ad Migratio November

16 Overview of dspace Release 7.4 Product Versio Overview Objective The followig table is a extract from product versio histories showig the product versios of the curret release ad of the three precedig releases. If a product has ew features, there is a lik to the brief descriptio i this documet. Product dspace Release AutomatioDesk See AutomatioDesk o page 27. Automotive Simulatio Models See Automotive Simulatio Models (ASM) o page 31. CofiguratioDesk See CofiguratioDesk o page 49. Cotaier Maager See Cotaier Maager o page 55. CotrolDesk 3.x 1) See CotrolDesk 3.x o page 57. CotrolDesk Next Geeratio 2) See CotrolDesk Next Geeratio o page 59. DCI Cofiguratio Tool ) dspace CAN API dspace ECU Flash Programmig Tool dspace FlexRay Cofiguratio Package See dspace FlexRay Cofiguratio Package o page 79. dspace HIL API.NET See dspace HIL API.NET o page New Features ad Migratio November 2012

17 Overview of dspace Release 7.4 Product dspace Release dspace Pytho Extesios See dspace Pytho Extesios o page 83. ECU Iterface Maager ) 1.2 See ECU Iterface Maager o page 85. Model Compare See Model Compare o page 89. ModelDesk See ModelDesk o page 91. MotioDesk See MotioDesk o page 93. MotioDesk Blockset Real-Time Testig See Real-Time Testig o page 99. RTI See RTI/RTI-MP ad RTLib o page 101. RTI-MP See RTI/RTI-MP ad RTLib o page 101. RTI AUTOSAR Package RTI Bypass Blockset See RTI Bypass Blockset o page 105. RTI CAN Blockset RTI CAN MultiMessage Blockset See RTI CAN MultiMessage Blockset o page 109. RTI LIN MultiMessage Blockset See RTI LIN MultiMessage Blockset o page 111. New Features ad Migratio November

18 Overview of dspace Release 7.4 Product dspace Release RTI RapidPro Cotrol Uit Blockset See RapidPro Cotrol Uit RTI Blockset o page 97. RTI FPGA Programmig Blockset See RTI FPGA Programmig Blockset o page 113. RTI Etheret (UDP) Blockset SystemDesk 3.x p3 3.2 (supportig AUTOSAR 3.x) See SystemDesk 3.x o page 117. SystemDesk 4.x 4.0 (supportig AUTOSAR 4.x) See SystemDesk 4.x o page 129. TargetLik See TargetLik o page 131. TargetLik Data Dictioary See TargetLik o page 131. Variable Editor VEOS 5) p2 3.0 See VEOS o page ) CotrolDesk 3.x will be delivered for the last time with dspace Release 2013-A. This meas you must migrate to CotrolDesk Next Geeratio, the successor to CotrolDesk. For migratio iformatio, refer to Migratig from CotrolDesk 3.x to CotrolDesk Next Geeratio ( CotrolDesk Next Geeratio Migratio Guide). 2) CotrolDesk Next Geeratio is the successor to CotrolDesk 3.x ad CalDesk. 3) As of dspace Release 7.4, the DCI Cofiguratio Tool comes with the DCI-GSI Cofiguratio Package setup. 4) Also available as patch 1 for ECU Iterface Maager 1.0 sice April ) VEOS is the successor to the dspace Offlie Simulator If you have ot updated regularly, refer to the New Features ad Migratio documets for the dspace releases listed above for iformatio about the ew features ad ecessary migratio steps. 18 New Features ad Migratio November 2012

19 Overview of dspace Release 7.4 New Product Key Features Objective This is a overview of each product's ew key features. For detailed iformatio, refer to the product-specific sectios. Iformatio i this topic AutomatioDesk o page 19 Automotive Simulatio Models (ASMs) o page 19 CofiguratioDesk o page 20 Cotaier maagemet o page 20 CotrolDesk Next Geeratio o page 20 dspace FlexRay Cofiguratio Package o page 20 ECU Iterface Maager o page 21 Model Compare o page 21 ModelDesk o page 21 MotioDesk o page 21 Pytho Extesios o page 22 Real-Time Testig o page 22 RTI, RTI-MP ad RTLib o page 22 RTI Bypass Blockset o page 22 RTI CAN MultiMessage Blockset o page 22 RTI LIN MultiMessage Blockset o page 22 RapidPro Cotrol Uit RTI Blockset o page 23 RTI FPGA Programmig Blockset o page 23 SystemDesk o page 23 TargetLik o page 23 VEOS o page 25 AutomatioDesk The ew key features of AutomatioDesk are: The ew Test Builder library providig blocks for creatig tests with implicit basic features such as exceptio hadlig, loggig ad result evaluatio. Ehacemets to the Framework Builder library, the CotrolDesk NG Access library ad the HIL API library. Ehacemets to data object hadlig i the Pytho Editor, ad additioal sort methods i the Chage Order dialog. Ehacemets to the report hadlig ad report layout. For details o the ew features, refer to New Features of AutomatioDesk 3.6 o page 27. Automotive Simulatio Models (ASMs) For details o the ew features, refer to Automotive Simulatio Models (ASM) o page 31. New Features ad Migratio November

20 Overview of dspace Release 7.4 CofiguratioDesk For details o the ew features, refer to CofiguratioDesk Implemetatio o page 49. Cotaier maagemet The ew key features of cotaier maagemet are: Exportig V-ECU implemetatios i SystemDesk 3.2 ad TargetLik Exchagig SWCs betwee SystemDesk 4.0 ad TargetLik For details o the ew features, refer to New Features of the Cotaier Maager 3.2 o page 55. CotrolDesk Next Geeratio The ew key features of CotrolDesk Next Geeratio (CotrolDesk 4.3) are: Camera iterface ad Video Moitorig istrumet Avioics istrumets Improved scale-usig istrumets VEOS support: triggered measuremets o VEOS platform Automatio: readig ad writig variables directly without havig to use istrumets Support of ASAM MDF 4.0 for measuremets ECU Diagostics: Workig with multiple ODX databases Bus Navigator: o Ehacemets whe usig PC-based iterfaces o Automatio support Combied variable filter offerig more flexibility For details o the ew features, refer to New Features of CotrolDesk Next Geeratio (CotrolDesk 4.3) o page 60. dspace FlexRay Cofiguratio Package The ew key features of the dspace FlexRay Cofiguratio Package are: Support of PDU trasmissio modes Update bit behavior accordig to AUTOSAR Support of static evet PDUs The ew key features of the dspace FlexRay Cofiguratio Tool are: Support of AUTOSAR System Template Alias ame for physical bus access 20 New Features ad Migratio November 2012

21 Overview of dspace Release 7.4 The ew key feature of the FlexRay Cofiguratio Blockset is: Assigig tasks to timetables via Ruable Fuctio blocks of the Model Port Block Library For details o the ew features, refer to New Features of dspace FlexRay Cofiguratio Package 3.0 o page 79. ECU Iterface Maager The ew key features of the ECU Iterface Maager are: Automatio iterface Password protectio for ECU applicatios Deactivatig fuctio calls ad write accesses For details o the ECU Iterface Maager, refer to New Features of ECU Iterface Maager 1.2 o page 85. Model Compare The ew key features of Model Compare are: Ehaced tree view display optios Tree view display cosiderig commets Highlightig with smarter widow opeig Savable highlightig Support of Simulik SLX model format For details o the ew features, refer to New Features of Model Compare 2.3 o page 89. ModelDesk The ew key features of ModelDesk are: Support of VEOS Support of Simulik SLX model format Exteded tool automatio for automized hadlig of parameter files ad variats For details o the ew features, refer to New Features of ModelDesk 2.6 o page 91. MotioDesk The ew key features of MotioDesk are: Automatio iterface Visualizatio of rai ad sow For details o the ew features, refer to New Features of MotioDesk 3.1 o page 94. New Features ad Migratio November

22 Overview of dspace Release 7.4 Pytho Extesios The ew key feature of Pytho Extesios is: New API for platform maagemet For details o the ew features, refer to dspace Pytho Extesios o page 83. Real-Time Testig The ew key feature of Real-Time Testig is: Support of VEOS For details o the ew features, refer to New Features of Real-Time Testig 2.0 o page 99. RTI, RTI-MP ad RTLib The ew key features of RTI, RTI-MP ad RTLib are: Support of Simulik SLX model format Ehacemets to the implemetatio software for MicroAutoBox II New procedure for loadig slave applicatios to a DS2302 board For details o the ew features, refer to New Features of RTI/RTI-MP ad RTLib o page 101. RTI Bypass Blockset The ew key features of the RTI Bypass Blockset are: Ehacemets to the RTIBYPASS_FUNCTION_BLx block Reusig existig ECU variables with the iteral bypass model Support of ASAM MCD-2 MC Ver. 1.6 The ew key feature of the RTI Bypass Blockset MATLAB API is: Support of ehacemets to the RTIBYPASS_FUNCTION_BLx block For details o the ew features, refer to New Features of the RTI Bypass Blockset o page 105. RTI CAN MultiMessage Blockset The ew key feature of the RTI CAN MultiMessage Blockset is: Support of AUTOSAR System Template For details o the ew features, refer to New Features of the RTI CAN MultiMessage Blockset 2.7 o page 109. RTI LIN MultiMessage Blockset The ew key features of the RTI LIN MultiMessage Blockset are: Support of AUTOSAR System Template Support of LDF files accordig to the SAE J2602 stadard For details o the ew features, refer to New Features of the RTI LIN MultiMessage Blockset 2.0 o page New Features ad Migratio November 2012

23 Overview of dspace Release 7.4 RapidPro Cotrol Uit RTI Blockset The ew key features of the RapidPro Cotrol Uit RTI Blockset are: Arbitrary crakshaft wheel desig Detectio of reverse crakshaft rotatio Smoothed speed measuremet For details o the ew features, refer to New Features of the RapidPro Cotrol Uit RTI Blockset o page 97. RTI FPGA Programmig Blockset The ew key features of the RTI FPGA Programmig Blockset are: Exteded Xilix software support Verilog support for hadcoded FPGA applicatios Ehaced support of framework migratio For details o the ew features, refer to New Features of the RTI FPGA Programmig Blockset 2.4 o page 113. SystemDesk As of dspace Release 7.4, there are two differet SystemDesk versios due to the coceptual differeces betwee the AUTOSAR Releases 3.x ad 4.x supported by SystemDesk: SystemDesk 3.x supports AUTOSAR 3.x. SystemDesk 4.0 supports AUTOSAR ad SystemDesk 3.x The ew key features of SystemDesk 3.x are: Ehaced optios for cofigurig ad geeratig V-ECUs for test scearios New simulatio scearios for V-ECU systems For details o the ew features, refer to New Geeral Features o page 118. SystemDesk 4.x The key features of SystemDesk 4.0 are: Complete support of AUTOSAR ad Iteroperability with other AUTOSAR-compliat tools For details o the features, refer to New Features of SystemDesk 4.0 o page 129. TargetLik The ew key features of TargetLik are: Compoet-based developmet usig abstract iterfaces Custom code: o o Ehacig usupported Simulik blocks to TargetLik Width-ivariat custom code template New Features ad Migratio November

24 Overview of dspace Release 7.4 Optioal deactivatio of compute-through-overflow Geeratig virtual ECUs for virtual ECU testig Target simulatio modules: o o New evaluatio board: Reesas AB_050_Fx4 New compiler versios New code geerator optios New API commads New hook fuctios Access fuctio chages o o o Specifyig structure access fuctios Propagatio ito structures Cotrollig use of auxiliary variables Improved code efficiecy Support of ew Simulik SLX model format For details o the ew features, refer to New Productio Code Geeratio Features o page 132. The ew key features of the TargetLik AUTOSAR module are: Support of AUTOSAR 4.03 ad Usig compoet-based developmet Improved frame model geeratio icludig update fuctioality Delivery of software compoets as object code For details o the ew features, refer to New AUTOSAR-Related Features o page 146. The ew key features of the TargetLik Data Dictioary are: Improved visualizatio ad hadlig for comparig/mergig full DDs or subtrees Simplified loadig ad iclusio of partial Data Dictioary files Simplified partitio of a DD project file Improved way to add properties to the Object Explorer New DD MATLAB API commads For details o the ew features, refer to New TargetLik Data Dictioary Features o page 150. For details o the TargetLik migratio aspects (TargetLik, TargetLik AUTOSAR module, TargetLik Data Dictioary), refer to Migratig to TargetLik 3.4 ad TargetLik Data Dictioary 3.4 o page New Features ad Migratio November 2012

25 Overview of dspace Release 7.4 VEOS VEOS is the successor to the dspace Offlie Simulator. The ew features described below are ehacemets ad chages compared with dspace Offlie Simulator 2.2p2. The ew key features of VEOS are: New dspace Target for Offlie Simulatio features icludig Real- Time Testig support Improved support for stimulatio scearios New VEOS Player For details o the ew features, refer to VEOS o page 179. Migratig to dspace Release 7.4 Objective After you istall Release 7.4, some additioal steps may be ecessary. Migratig from dspace Release 7.3 There are o geeral migratio steps to be doe. Product-specific migratio steps are usually doe automatically by the products. For exceptios, refer to the product-specific migratio descriptios. Migratig from dspace Release 7.2 or earlier To migrate from dspace Release 7.2 or earlier to Release 7.4, you also have to perform the migratio steps of the iterveig dspace Releases. All of the required migratio steps ca be doe with Release 7.4 istalled. For iformatio o the required migratio steps, refer to the New Features ad Migratio documets of the iterveig dspace Releases. Previous release documets The New Features ad Migratio documets for previous releases are available via Iteret ad o the dspace DVD: Dowload them from Read them from the dspace DVD (see the \Doc\Prit\PreviousReleases folder). The PDF files are called NewFeaturesAdMigratioxx.pdf, where xx stads for the release umber. New Features ad Migratio November

26 Overview of dspace Release New Features ad Migratio November 2012

27 AutomatioDesk Where to go from here Iformatio i this sectio New Features of AutomatioDesk Migratig to AutomatioDesk New Features of AutomatioDesk 3.6 New automatio library Test Builder library AutomatioDesk ow has a Test Builder library, which offers automatio blocks comparable to the Test Framework library. I cotrast to the Test Framework library, the Test Builder library is based o the Framework Builder library ad therefore uses its slot cocept. This gives you greater flexibility i implemetig the iteral features such as exceptio hadlig, loggig ad result evaluatio. The Test Builder library will replace the Test Framework library i the future. For further iformatio, refer to Test Builder ( Library Referece). AutomatioDesk Ehacemets to the libraries The followig libraries have bee ehaced: CotrolDesk NG Access The CotrolDesk NG Access library ow provides two ew automatio blocks: ReadVariableValue This block is used to read the value of a specified variable. WriteVariableValue This block is used to write a value to a specified variable. New Features ad Migratio November

28 AutomatioDesk For further iformatio, refer to CotrolDesk NG Access ( AutomatioDesk Library Referece). HIL API library The HIL API library provides some ew data objects: The ew Symbol commo data object for usig symbols. The ew Vedor data object for switchig betwee vedor-specific HIL API implemetatios. The default is dspace. The Vedor data object is provided by the followig automatio blocks: o IitBaseValue o IitCoditioWatcher o IitDuratioWatcher o IitMAPort There are some ew data objects for capture hadlig: o CaptureResultReader (replaces CaptureResultIDFReader) o CaptureResultWriter (replaces CaptureResultIDFWriter) o The Start automatio block ow cotais the CaptureResultWriter data object. There are some ew data objects for stimulus hadlig: o SigalSegmet o SigalDescriptio o SigalDescriptiosReader o SigalDescriptiosWriter For further iformatio, refer to HIL API ( AutomatioDesk Library Referece). Framework Builder library The library ow provides the SequeceFrame block for creatig custom templates o sequece level. For further iformatio, refer to Framework Builder ( AutomatioDesk Library Referece). Ehacemets to project hadlig The Chage Childre Order dialog has a ew optio to sort data objects alphaumerically or by type. For example, this helps you orgaize variables ad parameters more clearly. For further iformatio, refer to Chage Childre Order ( AutomatioDesk Referece). If you drag a data object from the Project Maager to the Pytho Editor of a opeed Exec block, the data object ame is ow automatically added to the script with its _AD_ alias. 28 New Features ad Migratio November 2012

29 AutomatioDesk Ehacemets to report hadlig If you execute the Export Report commad, the Save As dialog the file ame ow suggests a file ame cosistig of the paret's elemet ame ad the result ame. For example, if you wat to export the result amed Result5 from the sequece amed MySequece, the file ame suggested for the exported report is MySequece_Result5. For easier avigatio i reports, more bookmarks (PDF) or tree odes (HTML) are automatically added to each report. For example, each test step is ow be represeted by a bookmark or tree ode. Ehacemets to platform maagemet Ehaced platform support VEOS, the ew offlie simulatio platform, is supported by AutomatioDesk usig the HIL API library or the Platform Access library. dspace Release 7.4 provides VEOS as a ew software product to perform offlie simulatio o your host PC, but you must istall a add-o to dspace Release 7.4 to work with VEOS i coectio with AutomatioDesk 3.6. The add-o is available at Ehaced platform maagemet fuctios AutomatioDesk provides further commads for platform maagemet: Clear Flash Clear System Create Support Ifo Display Platform Message Dialogs Update Firmware For further iformatio, refer to Platform Maager ( AutomatioDesk Referece). New Features ad Migratio November

30 AutomatioDesk Migratig to AutomatioDesk 3.6 Geeral migratio aspects If you ope a AutomatioDesk project with a later AutomatioDesk versio, the software automatically detects whether migratio is ecessary. Click OK i the message dialog to start migratio. If you also wat to cotiue workig with the old project, you should ot overwrite it with the migrated project, because the versios are ot dowward compatible. Save the migrated project to aother path or ame. Before you ope a older project with the ew AutomatioDesk versio, esure the followig precoditios are fulfilled: You must create backups of the project ad of the liked custom libraries. AutomatioDesk must be ruig properly. There must ot be ay error messages displayed i the Log Viewer. The built-i libraries, required custom libraries ad other packages must be correctly loaded. For further iformatio, refer to Migratig AutomatioDesk ( AutomatioDesk Guide). Migratio aspect whe usig HIL API library With AutomatioDesk 3.6, the data type of the TaskNames data object i the GetTaskNames automatio block has chaged from Dictioary to List. The data objects are automatically migrated if you load a AutomatioDesk project created with a earlier versio, but the refereces which you specified for parameterizig this data object remai uchaged. Use the Fid Icosistecies dialog to search for ivalid refereces. The search result will cotai the refereces to the TaskNames data objects to be migrated maually. You must also do this for the OfflieTaskNames data object i the GetTaskNames automatio block. 30 New Features ad Migratio November 2012

31 Automotive Simulatio Models (ASM) Where to go from here Iformatio i this sectio All ASM Blocksets 32 ASM Diesel Egie Blockset 33 ASM Diesel Exhaust Blockset 35 ASM Drivetrai Basic Blockset 35 ASM Electric Compoets Blockset 36 ASM Eviromet Blockset 37 ASM Egie Gasolie Basic Blockset 38 ASM Egie Gasolie Blockset 40 ASM Optimizer 42 ASM Traffic Blockset 42 ASM Trailer Blockset 43 ASM Truck Blockset 45 ASM Turbocharger Blockset 46 ASM Vehicle Dyamics Blockset 47 Iformatio i other sectios Migratig ASM Models ( ASM User Guide) Provides geeral iformatio o the migratio process of ASM models. New Features ad Migratio November

32 Automotive Simulatio Models (ASM) All ASM Blocksets New Features of All ASM Blocksets Support of ew Simulik SLX model format ASM ad ModelDesk ow support the ew Simulik SLX model format. With MATLAB R2012b, models cotaiig ASM blocks ca be opeed or saved i MDL or SLX format. Both formats ca be used i ModelDesk projects ad for custom compoets libraries. Problems usig ASM with MATLAB R2012a ad R2012b Due to performace problems with i MATLAB R2012a ad R2012b, it is recommeded to istall the followig bugfix from the Mathworks website before usig ASM with MATLAB R2012a or 2012b: 32 New Features ad Migratio November 2012

33 Automotive Simulatio Models (ASM) ASM Diesel Egie Blockset Where to go from here Iformatio i this sectio New Features of ASM Diesel Egie Blockset Chages i the ASM Diesel Egie Demo Model 33 Migratig to ASM Diesel Egie Blockset New Features of ASM Diesel Egie Blockset MEASUREMENT_ INTERFACE block The ASM Diesel Egie models ca ow replicate testbech measuremet data durig real-time simulatio to validate the actual simulatio results i a specific operatig poit. This feature has bee icluded i the ASM Parameterizatio demo projects ad i the Simulik demo model. CotrolDesk layouts are provided for validatio. Chages i the ASM Diesel Egie Demo Model MDLUserIterface/Egie Diesel/MDL_MEAS The structure of the measuremet iterface feature has bee chaged: New subsystem MDL_MEAS. MDLUserIterface/ Eviromet/MDL_PAR The structure of the support of the measuremet iterface feature has bee chaged. The defiitio of uit for the ambiet temperature has bee chaged from [mbar] to [Pa] for cosistecy. MDL/Eviromet/ Maeuver The structure of the support of the measuremet iterface feature has bee chaged. MDL/Egie/Coolig System The structure of the support of the measuremet iterface feature has bee chaged: Adaptatio of Goto/From block tags respectively. MDL/Eviromet/Road The defiitio of uit for the ambiet temperature has bee chaged from [mbar] to [Pa]. MDL/Egie/AirPath/Turbo The iport at the MAPS_TC block has bee chaged. New Features ad Migratio November

34 Automotive Simulatio Models (ASM) Migratig to ASM Diesel Egie Blockset EXHAUST_MANIFOLD block A reset coditio has bee iserted to switch betwee map-based ad physical turbocharger approach durig simulatio. SOFT_ECU_DIESEL block The extrapolatio method for ijectio timig ad smoke limitatio map has bee chaged to iterpolatio-extrapolatio (for homogeous ad stratified mode) due to ModelDesk coformity. The crak agle bus sigal has bee reamed to correct the agle uit. SWITCHES_TURBO block The lik to former versio has bee moved due to ModelDesk coformity by usig the MAPS_TC parameter page. 34 New Features ad Migratio November 2012

35 Automotive Simulatio Models (ASM) ASM Diesel Exhaust Blockset Migratig to ASM Diesel Exhaust Blockset SCR_CATALYST block The lie i subsystem ame "SCR Catalyst \ for each cell" has bee removed to comply with amig covetios. ASM Drivetrai Basic Blockset Migratig to ASM Drivetrai Basic Blockset GEARBOX_MT block To simplify the mode, the PT1 elemet with time costat was deleted from the Trq_Trm_I[Nm] outport because it had egligible effect. A uit delay is added durig migratio. GEARBOX_AT block To simplify the mode, the PT1 elemet with time costat was deleted from the Trq_Trm_I[Nm] outport because it had egligible effect. A uit delay is added durig migratio. New Features ad Migratio November

36 Automotive Simulatio Models (ASM) ASM Electric Compoets Blockset Migratig to ASM Electric Compoets Blockset 2.3 PMSM_CONTROLLER block The decouplig equatio of the curret cotroller has bee corrected. PMSM_CONTROLLER_ THREE_LEVEL block The decouplig equatio of the curret cotroller has bee corrected. BATTERY block The Goto-From blocks have bee replaced with sigal lies i the ASMSigalBus. This solves a problem with multiple istaces of the battery block. BATTERY_MULTICELL block The Goto/From blocks have bee replaced with sigal lies i the ASMSigalBus. This solves a problem with multiple istaces of the battery block 36 New Features ad Migratio November 2012

37 Automotive Simulatio Models (ASM) ASM Eviromet Blockset Where to go from here Iformatio i this sectio New Features of ASM Eviromet Blockset Migratig to ASM Eviromet Blockset New Features of ASM Eviromet Blockset Lae sesor The lae sesor ca ow be parameterized usig ModelDesk. Migratig to ASM Eviromet Blockset CONTROLLER block Brakig durig slow acceleratio after startup is ow avoided. MANEUVER_SCHEDULER block Durig iitializatio of the maual drivig state, a fixed value was used to iitialize the vehicle height. This has bee replaced by a small offset to the tire radius. ROAD block The calculatio of the legth iside splie segmets has bee modified. v_road_ref block Brakig at maeuver segmet trasitio betwee two cosecutive 'FialVelocity' segmets is ow avoided. New Features ad Migratio November

38 Automotive Simulatio Models (ASM) ASM Egie Gasolie Basic Blockset Where to go from here Iformatio i this sectio New Features of ASM Egie Gasolie Basic Blockset Chages i the ASM Egie Gasolie Basic Demo Model Migratig to ASM Egie Gasolie Basic Blockset New Features of ASM Egie Gasolie Basic Blockset MEASUREMENT_ INTERFACE block The ASM Gasolie Egie Basic models ca ow replicate testbech measuremet data durig real-time simulatio to validate simulatio results at a specific operatig poit. This feature has bee icluded i the ASM Parameterizatio demo projects ad the Simulik demo model. CotrolDesk layouts are provided for validatio. Chages i the ASM Egie Gasolie Basic Demo Model MDLUserIterface/Egie GasBas/MDL_MEAS The structure of the measuremet iterface feature has bee chaged: New subsystem MDL_MEAS. MDLUserIterface/ Eviromet/MDL_PAR The structure of the support of the measuremet iterface feature has bee chaged. The defiitio of uit for the ambiet temperature has bee chaged from [mbar] to [Pa] for cosistecy. MDL/Eviromet/ Maeuver The structure of the support of the measuremet iterface feature has bee chaged. MDL/Egie/Coolig System The structure of the support of the measuremet iterface feature has bee chaged: Adaptatio of Goto/From block tags respectively. MDL/Eviromet/Road The uit defied for the ambiet temperature has chaged from [mbar] to [Pa]. 38 New Features ad Migratio November 2012

39 Automotive Simulatio Models (ASM) MDL/Egie/AirPath/Turbo The iport at the MAPS_TC block has bee chaged. Migratig to ASM Egie Gasolie Basic Blockset WALL_FILM block The extrapolatio method for the time delay map has bee chaged to iterpolatio-extrapolatio due to ModelDesk coformity. New Features ad Migratio November

40 Automotive Simulatio Models (ASM) ASM Egie Gasolie Blockset Where to go from here Iformatio i this sectio New Features of ASM Egie Gasolie Blockset Chages i the ASM Egie Gasolie Demo Model 40 Migratig to ASM Egie Gasolie Blockset New Features of ASM Egie Gasolie Blockset MEASUREMENT_ INTERFACE block The ASM Gasolie Egie Basic models ca ow replicate testbech measuremet data durig real-time simulatio to validate simulatio results at a specific operatig poit. This feature has bee icluded i the ASM Parameterizatio demo projects ad the Simulik demo model. CotrolDesk layouts are provided for validatio. Chages i the ASM Egie Gasolie Demo Model MDLUserIterface/Egie Gasolie/MDL_MEAS The structure of the measuremet iterface feature has bee chaged: New subsystem MDL_MEAS. MDLUserIterface /Eviromet/MDL_PAR The structure of the support of the measuremet iterface feature has bee chaged. The defiitio of uit for the ambiet temperature has bee chaged from [mbar] to [Pa] for cosistecy. MDL/Eviromet/ Maeuver The structure of the support of the measuremet iterface feature has bee chaged. MDL/Egie/Coolig System The structure of the support of the measuremet iterface feature has bee chaged: Adaptatio of Goto/From block tags. MDL/Eviromet/Road The defiitio of uit for the ambiet temperature has bee chaged from [mbar] to [Pa]. MDL/Egie/AirPath/Turbo The iport at the MAPS_TC block has bee chaged. 40 New Features ad Migratio November 2012

41 Automotive Simulatio Models (ASM) Migratig to ASM Egie Gasolie Blockset EXHAUST_MANIFOLD block A reset coditio has bee iserted to switch betwee the map-based ad physical turbocharger approach durig simulatio. SOFT_ECU_DIESEL block The extrapolatio method for ijectio timig ad smoke limitatio map has bee chaged to iterpolatio-extrapolatio (for homogeous ad stratified mode) due to ModelDesk coformity. WALL_FILM block The extrapolatio method for the time delay map has bee chaged to iterpolatio-extrapolatio due to ModelDesk coformity. SWITCHES_TURBO block The lik to the former versio has bee moved due to ModelDesk coformity by usig the MAPS_TC parameter page. Related topics Basics Migratig ASM Models ( ASM User Guide) New Features ad Migratio November

42 Automotive Simulatio Models (ASM) ASM Optimizer Migratig to ASM Optimizer Blockset Loadig results of previous optimizatio tasks Whe loadig the results of a previous optimizatio task, it was oly assiged to the last parameter i the parameter list. Further, the assiged value was rouded by mistake. These issues were solved. ASM Traffic Blockset Migratig to ASM Traffic Blockset FELLOW_PARAMETERS block Zero legths of fellow vehicles are ow avoided to prevet a divisio by zero. FELLOW_POSITION block The step size of a discrete itegrator is ow a block parameter. TRAFFIC_SCHEDULER block Traffic scearios with cotiue segmets after iitial segmets resulted i icosistet simulatio results. This has bee corrected. 42 New Features ad Migratio November 2012

43 Automotive Simulatio Models (ASM) ASM Trailer Blockset Where to go from here Iformatio i this sectio New Features of ASM Trailer Blockset Migratig to ASM Trailer Blockset New Features of ASM Trailer Blockset 2.0 Dolly extesio The ASM Trailer blockset ow supports simulatig a dolly extesio, see the followig illustratio. A ew demo model of ASM Truck shows the simulatio with a semitrailer or dolly extesio. Migratig to ASM Trailer Blockset 2.0 TIRE_MODEL_MAGIC_ FORMULA_<xyz> block Two ew iports have bee added to the blocks for the tire radius to be chaged by a exteral sigal. TIRE_MODEL_TMEASY_ <xyz> block Two ew iports have bee added to the blocks for the tire radius to be chaged by a exteral sigal. The scalig parameters are coected to the slip camber ad overturig torque calculatio. RELATIVE_VELOCITIES_ TRAILER_<xyz> block The Steerig rod velocity iport is ow a 2-dimesioal sigal to eable the left ad right wheels to be steered idepedetly. New Features ad Migratio November

44 Automotive Simulatio Models (ASM) SUSKIN_TRAILER_<xyz>_ 3DOF block The Steerig rod displacemet ad Steerig rod velocity iports are ow 2-dimesioal sigals to eable the left ad right wheels to be steered idepedetly. BALL_JOINT_ ACCELERATION_TRAILER block This subsystem ca ow be switched to simulate a mechaism with 1 degree of freedom. BALL_JOINT_ARTICULATED _BODY_TRAILER block This subsystem ca be ow switched to simulate a mechaism with 1 degree of freedom. HITCH_POS_TRAILER block The block ame has bee chaged from HITCH_POS_VEHICLE to HITCH_POS_TRAILER. HITCH_VELOCITY_TRAILER block The block ame has bee chaged from HITCH_VELOCITY_VEHICLE to HITCH_VELOCITY_TRAILER. CONTACT_POINT_ CALCULATION_<xyz> block You ca reset the tire radius calculatio. 44 New Features ad Migratio November 2012

45 Automotive Simulatio Models (ASM) ASM Truck Blockset Where to go from here Iformatio i this sectio Chages i the ASM Truck Demo Model 45 Migratig to ASM Truck Blockset Chages i the ASM Truck Demo Model ASM_TruckTrailer The demo model ca ow be simulated with a dolly extesio (see New Features of ASM Trailer Blockset 2.0 o page 43. Migratig to ASM Truck Blockset 1.4 TIRE_MODEL_MAGIC_ FORMULA_<xyz> block Two ew iports have bee added to the blocks for the tire radius to be chaged by a exteral sigal. TIRE_MODEL_TMEASY_ <xyz> block Two ew iports have bee added to the blocks for the tire radius to be chaged by a exteral sigal. The scalig parameters are coected to the slip camber ad overturig torque calculatio. RELATIVE_VELOCITIES_ REAR_<xyz> block The Steerig rod velocity iport is ow a 2-dimesioal sigal to eable the left ad right wheels to be steered idepedetly. SUSKIN_REAR_<xyz>_ 3DOF block The Steerig rod displacemet ad Steerig rod velocity iports are ow 2-dimesioal sigals to eable the left ad right wheels to be steered idepedetly. CONTACT_POINT_ CALCULATION_<xyz> block You ca reset the tire radius calculatio. New Features ad Migratio November

46 Automotive Simulatio Models (ASM) ASM Turbocharger Blockset Migratig to ASM Turbocharger Blockset 2.1 COMPRESSOR block The COMPRESSOR block has bee modified to reflect a certai behavior durig istable surge operatig coditio. This operatig coditio is detected durig simulatio by comparig the curret pressure ratio with the maximum stable pressure ratio. This mechaism requires iformatio about the margi of the stable operatig regio, which is ow cotaied i the surge lie ad the iverse surge lie. The parameterizatio files for this block have a ew extrapolatio optio to simulate a appropriate pressure ratio durig surge ad backflow coditios. COMPRESSOR_HP block Refer to Compressor HP ( ASM Turbocharger Referece). MAPS_TC block A lik to the MAPS_TC block is chaged to the former versio MAPS_TC_6_0 block durig migratio to guaratee the same block behavior after migratio. The ew MAPS_TC block cotais several chages: The turbo cotrol ifluece o efficiecy has bee modified from additive to multiplicative. The temperatures are evaluated relatively istead of absolutely to accout for chages i the ambiet coditios. The variable amig for compressor output pressure limits has bee corrected. 46 New Features ad Migratio November 2012

47 Automotive Simulatio Models (ASM) ASM Vehicle Dyamics Blockset Where to go from here Iformatio i this sectio New Features of ASM Vehicle Dyamics Blockset Migratig to ASM Vehicle Dyamics Blockset New Features of ASM Vehicle Dyamics Blockset 2.3 Subframe The elastokiematics of a subframe are ow used i additio to the suspesio compliaces. The SUBFRAME block ca be used i the model as a optio ad i parallel to the suspesio compliace block. Migratig to ASM Vehicle Dyamics Blockset 2.3 TIRE_MODEL_MAGIC_ FORMULA_<xyz> block Two ew iports have bee added to the blocks for the tire radius to be chaged by a exteral sigal. TIRE_MODEL_TMEASY_ <xyz> block Two ew iports have bee added to the blocks for the tire radius to be chaged by a exteral sigal. The scalig parameters are coected to the slip camber ad overturig torque calculatio. RELATIVE_VELOCITIES_ <xyz> block The Steerig rod velocity iport is ow a 2-dimesioal sigal to eable the left ad right wheels to be steered idepedetly. CONTACT_POINT_ CALCULATION_<xyz> block You ca reset the tire radius calculatio. Steerig left ad right wheel The Steerig rod displacemet ad Steerig rod velocity iports are ow 2-dimesioal sigals to eable the left ad right wheels to be steered idepedetly. This applies to the followig blocks: RIGID_AXLE SEMI_TRAILING_ARM MC_PHERSON_STRUT SUSKIN_REAR_SYM_3DOF New Features ad Migratio November

48 Automotive Simulatio Models (ASM) SUSKIN_REAR_ASYM_3DOF SUSPENSION_KINEMATICS_REAR_SYMMETRIC SUSPENSION_KINEMATICS_REAR_ASYMMETRIC SUSKIN_FRONT_SYM_3DOF SUSKIN_FRONT_ASYM_3DOF SUSPENSION_KINEMATICS_FRONT_SYMMETRIC SUSPENSION_KINEMATICS_FRONT_ASYMMETRIC 48 New Features ad Migratio November 2012

49 CofiguratioDesk CofiguratioDesk Implemetatio Where to go from here Iformatio i this sectio New Features of CofiguratioDesk Migratig Projects from CofiguratioDesk 4.2 (o dspace Release 7.3) or Earlier 52 New Features of CofiguratioDesk 4.3 Geeral CofiguratioDesk 4.3 has a ew software architecture with improved software hadlig ad also some ew features. Assessig properties of elemets A cetral Properties Browser is ow always available o the scree to display ad cofigure properties, for example, of the sigal chai elemets. The Properties Browser replaces the properties dialogs of earlier software versios, where you had to ope ad close the dialogs for each elemet separately. New Features ad Migratio November

50 CofiguratioDesk Hadlig coflicts The ew cocept of CofiguratioDesk allows very flexible cofiguratio settigs, with the effect that oe settig might ot match a settig at aother place i the sigal chai. These cofiguratio coflicts are iitially allowed, but before you build a realtime applicatio, you have to resolve the coflicts to get proper build results. The ew Coflicts Viewer shows all the coflicts ad helps you to resolve them. Implemetig tasks Up to CofiguratioDesk 4.2, the implemetatio of tasks ad compoets that ifluece the timig behavior of the executable applicatio (= real-time applicatio) is adopted from the behavior model (Simulik). CofiguratioDesk 4.3 ow allows you to model executable applicatios ad the tasks used withi them very flexibly. For further iformatio, refer to Modelig Executable Applicatios ad Tasks ( CofiguratioDesk Real-Time Implemetatio Guide). Udo/Redo As of CofiguratioDesk 4.3, the software has udo/redo fuctioality. You ca udo/redo actios or chages that you carried out beforehad. Rebuild detectio for CotrolDesk Next Geeratio CofiguratioDesk provides specific build iformatio so that CotrolDesk Next Geeratio ca detect whether ew build results are available. Support of Simulik SLX model format CofiguratioDesk 4.3 supports the Simulik SLX model format. Limitatios cocerig MATLAB compatibility The followig limitatios apply whe you work with MATLAB R2012a ad R2012b: No icremetal code geeratio for top-level models CofiguratioDesk does ot support the Icremetal Code Geeratio for Top-Level Models feature. Simulik Iport ad Outport blocks used as I/O data iterfaces If your model cotais more tha oe periodic task, you must ot use Simulik Iport ad Outport blocks as I/O data iterfaces. Otherwise, the build process is aborted with the followig error message: Compilig "E:\Prj1\Appl1\Build\myModel\MdlCode\myModel_dsrt\myModel.c" mymodel.c: 50 New Features ad Migratio November 2012

51 CofiguratioDesk I fuctio 'mymodel_output0': mymodel.c:185: error: 'tid' udeclared (first use i this fuctio) Oly valid for MATLAB R2012a: No spaces i applicatio path ames The applicatio path ame must ot cotai ay spaces. Otherwise, the build process is aborted with a error message similar to the followig oe: Compilig "D:\dSPACE RCPHIL 7.4\MATLAB\DSRT\C\dsrt_mdlfc.cpp" dsrt_mdlfc.cpp:19:21: error: rtmodel.h: No such file or directory <...> I file icluded from dsrt_mdlfc.cpp:21: dsrt_mdlfc.h:34: error: variable or field 'APLastApplStateStopped' declared void <...> tox86-g++.exe: RCPHIL: No such file or directory tox86-g++.exe: 7.4\Work\Project_Test\Applicatio\Build\dsmpblib_test\MdlCode" : No such file or directory Usupported ew features of MATLAB R2012b CofiguratioDesk does ot support the followig ew features i MATLAB R2012b: Commetig out blocks Code geeratio for protected models New Features ad Migratio November

52 CofiguratioDesk Migratig Projects from CofiguratioDesk 4.2 (o dspace Release 7.3) or Earlier Reasos for migratio CofiguratioDesk 4.3 has a ew software architecture with improved software hadlig ad also some ew features. To use projects ad applicatios from earlier versios with CofiguratioDesk 4.3, you have to migrate them beforehad. Ruig the migratio You ca migrate a project created with CofiguratioDesk 4.2 or earlier automatically by opeig it with CofiguratioDesk 4.3 as usual. CofiguratioDesk detects projects which eed to be migrated ad opes the migratio dialog. Whe you click OK, migratio starts ad coverts all the data ad applicatios belogig to the project. At the ed of the migratio process, the project opes automatically ad you ca work with it i CofiguratioDesk 4.3. You caot ope ad use a migrated project with CofiguratioDesk 4.2 or earlier. Durig the migratio process, a backup ZIP file is created for each applicatio i the project. The ZIP files cotai the old data ad ca be used for later restoratio. Each <Applicatio ame>.migratiobackup.zip file is saved to the applicatio root level. Migratio of Simulik models Simulik models which are added to the CofiguratioDesk applicatio are migrated the first time you ope the model from CofiguratioDesk 4.3, for example, if you perform a model aalysis. Migratio of custom fuctio blocks If you wat to migrate a project which cotais custom fuctio blocks from demo models provided by dspace, a additioal workaroud is ecessary. For details, refer to Migratig Custom Fuctio Blocks Used i CofiguratioDesk 4.2 Projects or Earlier ( CofiguratioDesk Real- Time Implemetatio Guide). 52 New Features ad Migratio November 2012

53 CofiguratioDesk Chages after migratio Due to the chages i the software architecture, there are major ad mior chages i the user iterface ad i hadlig. The mior chages do ot really affect your work ad its results. The major chages are described below. Chages related to the Project Maager The followig chages affect projects ad CofiguratioDesk applicatios: A CofiguratioDesk applicatio o loger cotais the Cofiguratio applicatio compoet. The CDS file which holds the data of the Cofiguratio applicatio compoet is o loger provided or supported. As of CofiguratioDesk 4.3, all applicatio data (topology data ad sigal chai data) is stored i oe iteral zip file. You ca import ad export the data to reuse it i other projects. The topology files ow are used oly to exchage sigle topology data betwee differet applicatios. The file ame extesios of topology files have chaged, for example, the file ame extesio of the hardware topology file has chaged from HTF to HTFX. Chages related to the model iterface The chages after migratio are as follows: I the Model Port Block Library, the Trigger Evet Port block has bee replaced with the Ruable Fuctio block, which exports a fuctio-call subsystem as a ruable fuctio. A ruable fuctio groups together all the behavior model compoets that must be called for computig results i a specific task. I CofiguratioDesk: o You ca access ruable fuctios (provided by the Ruable Fuctio block i the behavior model) after model aalysis. With the executable applicatio ad the task modelig feature, you ca assig the ruable fuctios to a tasks (periodic or asychroous tasks) for executio. Ruable fuctios are ot part of the model topology ad therefore you caot access them via the Model Browser. o Trigger Evet Port blocks that allow the trasfer of asychroous CofiguratioDesk fuctio evets to a Simulik behavior model do ot exist ay more. New Features ad Migratio November

54 CofiguratioDesk o I/O fuctio evet ports (at fuctio blocks) o loger exist. Access to the I/O evets ow is realized via the executable applicatio ad task modelig feature, where you ca assig I/O evets to tasks to trigger them. Limitatios The followig limitatios exist for migratig projects: Migratio of sigle topologies (HTF, DTF, MTF) You caot migrate sigle topologies, for example, a sigle device topology directly. If you wat to migrate oly oe topology, you must add it i a empty applicatio of CofiguratioDesk 4.2 or earlier. After this you ca migrate the project cotaiig the applicatio. Obsolete ad uresolved elemets Obsolete elemets i a sigal chai are ot migrated. Uresolved elemets of the hardware topology ad the model topology are ot migrated. However, uresolved elemets of the device topology are migrated. Workig view layouts User-defied workig view layouts for customized layout settigs are ot migrated ad ot supported with CofiguratioDesk New Features ad Migratio November 2012

55 Cotaier Maager New Features of the Cotaier Maager 3.2 Exportig V-ECU implemetatios i SystemDesk 3.2 ad TargetLik I SystemDesk ad TargetLik, you ca geerate V-ECUs for use with VEOS. You ca export V-ECU implemetatios as cotaiers. Whe you export a V-ECU implemetatio, a collectio of files that belogs to the V-ECU implemetatio is gathered i a CTLGZ file archive. Files i a V-ECU implemetatio Three kids of files ca be part of a V-ECU implemetatio: Cofiguratio files (ARXML) Code files (H, C) A variable descriptio file (A2L) For details, refer to Export V-ECU Implemetatio ( Maagemet Documet). Cotaier Exchagig SWCs betwee SystemDesk 4.0 ad TargetLik You ca exchage software compoets betwee SystemDesk 4.0 ad TargetLik usig cotaiers. You ca use a cotaier to trasfer AUTOSAR files from SystemDesk 4.0 to TargetLik, either to start implemetig a software compoet with TargetLik or to update a existig software compoet. After implemetig or updatig, you ca export a cotaier from TargetLik ad import the relevat part of its cotets i SystemDesk 4.0. For details, refer to Exchagig Compoet Cotaiers Betwee SystemDesk ad TargetLik ( Cotaier Maagemet Documet). New Features ad Migratio November

56 Cotaier Maager 56 New Features ad Migratio November 2012

57 CotrolDesk 3.x Discotiuatio of CotrolDesk 3.x CotrolDesk 3.x will be delivered for the last time with dspace Release 2013-A. This meas you must migrate to CotrolDesk Next Geeratio, the successor to CotrolDesk. For migratio iformatio, refer to Migratig from CotrolDesk 3.x to CotrolDesk Next Geeratio ( CotrolDesk Next Geeratio Migratio Guide). Where to go from here Iformatio i this sectio New Features of CotrolDesk Migratig to CotrolDesk New Features ad Migratio November

58 CotrolDesk 3.x New Features of CotrolDesk MicroAutoBox support The Platform Maager ow displays FPGA piggyback ad IP modules coected to MicroAutoBox. Migratig to CotrolDesk Reusig CAN/LIN bus cofiguratios last saved i CotrolDesk or earlier Suppose you worked i CotrolDesk 3.x with a bus cofiguratio (XML file) based o a real-time applicatio built with RTI CAN MultiMessage Blockset or RTI LIN MultiMessage Blockset from dspace Release 7.2 or earlier. Whe you reuse this bus cofiguratio i CotrolDesk after rebuildig the applicatio with the RTI MultiMessage Blockset from dspace Release 7.3, some fuctios such as replay ad variat hadlig do ot work (due to a chaged build process). To reuse your old bus cofiguratio, you must migrate it to CotrolDesk CotrolDesk provides the DSMigrateBusCfg.exe commad lie tool for this. You ca fid the tool at %dspace_root%\cotroldesk\bi after istallatio of CotrolDesk. To migrate a bus cofiguratio, perform the followig steps: 1. Ope a Commad Prompt widow. For example, o the Start meu i Widows XP, select Ru, eter cmd ad click OK. 2. Eter DSMigrateBusCfg IputFile [OutputFile]. IputFile is the old bus cofiguratio file, whose file ame extesio must be XML. This parameter is madatory. OutputFile is the ew bus cofiguratio ad is a optioal parameter. If you specify the OutputFile parameter, it must have the XML file ame extesio. If you do ot specify the OutputFile parameter, the ew bus cofiguratio has the ame of the old bus cofiguratio with the suffix _ew. 58 New Features ad Migratio November 2012

59 CotrolDesk Next Geeratio Where to go from here Iformatio i this sectio New Features of CotrolDesk Next Geeratio (CotrolDesk 4.3) Migratig to CotrolDesk Next Geeratio (CotrolDesk 4.3) Iformatio i other sectios CotrolDesk Next Geeratio Migratio Guide Explais migratio from CalDesk/CotrolDesk 3.x to CotrolDesk Next Geeratio (CotrolDesk 4.3). New Features ad Migratio November

60 CotrolDesk Next Geeratio New Features of CotrolDesk Next Geeratio (CotrolDesk 4.3) Where to go from here Iformatio i this sectio New Geeral Features (CotrolDesk 4.3) 60 New Features of Platform Maagemet ad 62 Platforms/Devices (CotrolDesk 4.3) New Variable Maagemet Features 64 (CotrolDesk 4.3) New Istrumet Features (CotrolDesk 4.3) 65 New Measuremet ad Recordig Features 70 (CotrolDesk 4.3) New Bus Navigator Features (CotrolDesk 4.3) 70 New Data Set Maagemet Features 70 (CotrolDesk 4.3) New ECU Diagostics Features (CotrolDesk 4.3) 72 New Automatio Features (CotrolDesk 4.3) 73 New Geeral Features (CotrolDesk 4.3) VEOS support CotrolDesk supports VEOS, the successor to the dspace Offlie Simulator. The ew VEOS support feature is: Performig triggered measuremets o eviromet VPUs based o SDF files. Refer to Cofigurig Triggered Measuremet o dspace Platforms ( CotrolDesk Next Geeratio Basic Practices Guide). dspace Release 7.4 provides VEOS as a ew software product to perform offlie simulatio o your host PC. However, you must istall a add-o to dspace Release 7.4 to work with VEOS i coectio with CotrolDesk Next Geeratio (CotrolDesk 4.3). The addo is available at AddO. 60 New Features ad Migratio November 2012

61 CotrolDesk Next Geeratio Camera iterface CotrolDesk 4.3 provides a ew iterface to access video cameras coected to the CotrolDesk PC. The iterface lets you display, record ad replay video data sychroously with data from vehicle buses, ECUs, dspace RCP systems, etc. Camera view Widscree LIN, CAN, FlexRay Sesor ad cotrol uit CotrolDesk Next Geeratio Etheret, USB Camera CotrolDesk's camera iterface supports all cameras that use DirectShow. The supported cameras are usually Plug ad Play cameras coected via USB or Etheret. You ca save recorded video data as a IDF or AVI file. The camera iterface cosists of: A Video Capturig device. Refer to Cofigurig a Video Capturig Device ( CotrolDesk Next Geeratio Basic Practices Guide). A Video Moitorig istrumet. Refer to Video Moitorig Hadlig ( CotrolDesk Next Geeratio Basic Practices Guide). Supported CAN iterfaces CotrolDesk ow also supports the followig CAN iterfaces from Vector Iformatik: VN16xx CANcardXLe Refer to Supported CAN Iterfaces ( Basic Practices Guide). CotrolDesk Next Geeratio New Features ad Migratio November

62 CotrolDesk Next Geeratio These iterfaces are ot supported by CotrolDesk's ECU Diagostics devices. New Features of Platform Maagemet ad Platforms/Devices (CotrolDesk 4.3) Iformatio i this topic New platforms/devices o page 62 VEOS platform o page 62 Video Capturig device o page 62 Automatic reload of variable descriptio after rebuild o page 62 Detectig termiated real-time applicatios o page 63 Clearig the system o page 63 SCALEXIO Processig Uit platform: Switchig betwee assembly view ad etwork view o page 63 Multiprocessor System platform: Chaged cofiguratio process o page 63 MicroAutoBox platform: Display of coected piggyback modules o page 63 DS230x: Registratio via processor board o page 64 New platforms/devices CotrolDesk Next Geeratio ow also supports the followig platforms/devices: VEOS platform CotrolDesk s ew VEOS platform lets you cofigure ad cotrol a offlie simulatio applicatio ruig i VEOS ad access the applicatio's eviromet VPU. The VEOS platform replaces the Offlie Simulator platform from CotrolDesk Video Capturig device CotrolDesk s ew Video Capturig device lets you capture video sigals sychroously to sigals from other platforms/devices. Refer to Cofigurig a Video Capturig Device ( Geeratio Basic Practices Guide). CotrolDesk Next Automatic reload of variable descriptio after rebuild CotrolDesk ca ow detect the rebuild of a real-time applicatio if it was built usig a implemetatio software (RTI or CofiguratioDesk) versio dspace Release 7.4 or later. You ca specify to reload the variable descriptio file automatically i such cases. Refer to Variables Page ( CotrolDesk Next Geeratio Referece). 62 New Features ad Migratio November 2012

63 CotrolDesk Next Geeratio Detectig termiated realtime applicatios Whe you start olie calibratio, CotrolDesk automatically detects whether a real-time applicatio has bee termiated. You caot ru a measuremet for a termiated applicatio. You ca specify whether to reload the applicatio. Refer to Basics o Real-Time Applicatios ( Geeratio Basic Practices Guide). CotrolDesk Next Clearig the system CotrolDesk lets you clear the system by erasig the recet hardware cofiguratio. The it refreshes the iterface coectios betwee the host PC ad the hardware to reiitialize the Platform/Device Maager. Whe the system is cleared, CotrolDesk creates a copy of the recet hardware cofiguratio. To recover the system, you ca import the copy agai via the Maage Recet Hardware Cofiguratio dialog. Refer to Clear System ( CotrolDesk Next Geeratio Referece). SCALEXIO Processig Uit platform: Switchig betwee assembly view ad etwork view You ca ow switch betwee a assembly view ad a etwork view for the SCALEXIO Processig Uit platform: Assembly view: To display a compoet-based view of the registered hardware i the Platform/Device Maager. Refer to Assembly View ( CotrolDesk Next Geeratio Referece). Network view: To display a etwork-based view of the registered hardware i the Platform/Device Maager. Refer to Network View ( CotrolDesk Next Geeratio Referece). Multiprocessor System platform: Chaged cofiguratio process The way you cofigure a Multiprocessor System platform has chaged i CotrolDesk 4.3. For istructios, refer to How to Register a Platform ( Next Geeratio Basic Practices Guide). CotrolDesk For iformatio o the Multiprocessor System platform ad o assigig registered hardware to a Multiprocessor System platform, refer to Basics o Multiprocessor System Platforms ( CotrolDesk Next Geeratio Basic Practices Guide). MicroAutoBox platform: Display of coected piggyback modules The Platform/Device Maager ow displays piggyback modules coected to MicroAutoBox. New Features ad Migratio November

64 CotrolDesk Next Geeratio DS230x: Registratio via processor board As of CotrolDesk 4.3, a DS230x board ca be registered oly by registerig the processor board to which the DS230x board is coected. Whe you register the processor board, a coected DS230x board is detected automatically. Refer to Register Platform ( Referece). CotrolDesk Next Geeratio New Variable Maagemet Features (CotrolDesk 4.3) Automatic reload of variable descriptio after rebuild CotrolDesk ca ow detect the rebuild of a real-time applicatio if it was built usig a implemetatio software (RTI or CofiguratioDesk) versio dspace Release 7.4 or later. You ca specify to reload the variable descriptio file automatically i such cases. Refer to Variables Page ( CotrolDesk Next Geeratio Referece). Combied variable filter To filter the variable list i CotrolDesk's Variable Browser, you ca ow defie a filter that combies several filter coditios. You ca defie a combiatio of the followig filter coditios: Wildcard filter Variable state Variable type 64 New Features ad Migratio November 2012

65 CotrolDesk Next Geeratio You ca also specify filter groups to defie cascaded filters. For istructios, refer to How to Filter the Variable List ( CotrolDesk Next Geeratio Basic Practices Guide) New Istrumet Features (CotrolDesk 4.3) Iformatio i this topic Avioics istrumets o page 66 Airspeed Idicator o page 66 Altimeter o page 66 Artificial Horizo o page 67 Headig Idicator o page 67 New Video Moitorig istrumet o page 68 Importig layouts as refereces o page 68 Assigig istrumet properties o page 68 Lockig layout editig for each layout idividually o page 69 Discotiuatio of the Cofigure Variables dialog o page 69 Further istrumetatio features o page 69 New Features ad Migratio November

66 CotrolDesk Next Geeratio Avioics istrumets CotrolDesk ow provides the followig Avioics istrumets to visualize variables of a simulated aircraft. Airspeed Idicator To idicate the airspeed of a simulated aircraft. Captio with BLOCK ad VARIABLE macro Visible eighbor Magifier Airspeed Visible eighbor Airspeed idicator scale with colored bads Refer to Airspeed Idicator ( Referece). CotrolDesk Next Geeratio Altimeter To idicate the altitude of a simulated aircraft. Captio with BLOCK ad VARIABLE macro Visible eighbor Magifier Visible eighbor Altimeter scale Refer to Altimeter ( CotrolDesk Next Geeratio Referece). 66 New Features ad Migratio November 2012

67 CotrolDesk Next Geeratio Artificial Horizo Roll poiter To idicate a simulated aircraft's pitch ad roll. Zero poiter Upper sky Roll scale Lower sky Aircraft symbol Horizo Upper lad Pitch scale Lower lad Refer to Artificial Horizo ( Referece). CotrolDesk Next Geeratio Headig Idicator To idicate the directio a simulated aircraft is headed i. Numeric display Lubber lie Headig idicator scale Refer to Headig Idicator ( Referece). CotrolDesk Next Geeratio New Features ad Migratio November

68 CotrolDesk Next Geeratio New Video Moitorig istrumet CotrolDesk Next Geeratio ow provides the Video Moitorig istrumet for displayig video data. The illustratio below shows the Video Moitorig istrumet displayig recorded video data: Refer to Video Moitorig Hadlig ( Geeratio Basic Practices Guide). CotrolDesk Next Importig layouts as refereces You ca import a layout as a local workig copy with a referece to a exteral layout file (LAX file) by importig the exteral layout as a lik. You ca the sychroize the layout settigs via the cotext meu of the ew experimet layout. Refer to: Import Layout(s) ( CotrolDesk Next Geeratio Referece) Sychroize (Layout) ( CotrolDesk Next Geeratio Referece) Assigig istrumet properties You ca ow easily assig properties of oe istrumet to aother (if the properties are commo to both istrumets). Refer to Assig Properties ( Referece). CotrolDesk Next Geeratio 68 New Features ad Migratio November 2012

69 CotrolDesk Next Geeratio Lockig layout editig for each layout idividually You ca ow lock layout editig for each layout idividually. Up to ow, this was possible for the etire experimet oly. Refer to Locked Mode ( CotrolDesk Next Geeratio Referece). Discotiuatio of the Cofigure Variables dialog The Cofigure Variables dialog has bee discotiued i CotrolDesk 4.3. The dialog was used to select istrumets ad layouts for visualizig variables. To visualize variables i CotrolDesk 4.3, select them i the Variable Browser ad press Eter. The variables are placed o the curretly active layout ad coected to their default istrumet. Further istrumetatio features Further istrumetatio features: Improvemets for istrumets that use a scale (Kob, Gauge,...) Table Editor: Support for the exteded ad fixed scalig modes for data axes o Exteded mode: The data axis ca oly grow. o Fixed mode: The rage of the data axis is set to the values of the Mi ad Max properties. Refer to Axes Properties (Table Editor) ( CotrolDesk Next Geeratio Referece). Multiselectig layouts for export Refer to Export ( CotrolDesk Next Geeratio Referece). Cofigurig the istrumet selectio border style Refer to Istrumets Page ( Referece). CotrolDesk Next Geeratio New Features ad Migratio November

70 CotrolDesk Next Geeratio New Measuremet ad Recordig Features (CotrolDesk 4.3) Support of ASAM MDF 4.0 CotrolDesk ow supports the ASAM MDF 4.0 format (MF4 file ame extesio) for importig ad exportig measuremet data. New Bus Navigator Features (CotrolDesk 4.3) CotrolDesk's Bus Navigator ow provides the followig ew features: Features for CAN Geeratio of Bus Istrumets (TX Type) i coectio with PCbased CAN iterfaces such as DCI-CAN1 Features for FlexRay Geeratio of Bus Istrumets (RX Type) i coectio with PCbased FlexRay iterfaces Filtered moitorig ad loggig i coectio with PC-based FlexRay iterfaces Features for LIN Geeratio of Bus Istrumets (RX Type) i coectio with PCbased LIN iterfaces Filtered/ufiltered moitorig ad loggig i coectio with PCbased LIN iterfaces Demo CotrolDesk ow provides a Bus Navigator demo. Refer to Bus Navigator Demo ( CotrolDesk Next Geeratio Basic Practices Guide). New Data Set Maagemet Features (CotrolDesk 4.3) Restoratio of data sets after reload If you reload the variable descriptio (SDF file) of a dspace platform, CotrolDesk maitais the data set assigmet ad tries to reestablish all parameter coectios. Refer to Reload Variable Descriptio ( Geeratio Referece). CotrolDesk Next 70 New Features ad Migratio November 2012

71 CotrolDesk Next Geeratio Specifyig data sets to be dowloaded o olie calibratio start CotrolDesk ow lets you select oe or more data sets / sub data sets to be dowloaded to a platform o olie calibratio start. If you select more tha oe data set / sub data set to dowload o olie calibratio start, the data sets / sub data sets are dowloaded oe after the other accordig to their order i the Project Maager. Refer to How to Select Additioal Data Sets for Dowloadig o Olie Calibratio Start ( CotrolDesk Next Geeratio Basic Practices Guide). Creatig data sets for devices that have o memory segmet defiitio CotrolDesk ow lets you create data sets for devices that have o memory segmet defiitio. Refer to Create Data Set ( Referece). CotrolDesk Next Geeratio Creatig a applicatio image If a platform supports creatig a ew applicatio image, you ca ow upload the real-time image to the hardware i oe step. Refer to How to Create a Applicatio Image ( CotrolDesk Next Geeratio Basic Practices Guide). Automatic EPK check o import data set from HEX file Whe you import a HEX file (HEX, S19, MOT), CotrolDesk checks the cosistecy of the A2L file ad the imported data set (EPK check), if possible. Refer to Cosistecy Checks (EPK Checks) ( CotrolDesk Next Geeratio Basic Practices Guide). EPK check for MMF-based data sets For HEX files (HEX, S19, MOT, CotrolDesk iteral file format: MMF), you ca iitiate a cosistecy check (EPK check) maually. Refer to Check EPK ( CotrolDesk Next Geeratio Referece). Filterig data set parameters by memory segmets I CotrolDesk's Data Set Maager, you ca ow reduce the umbers of displayed parameters by choosig the Memory Segmets Filter prefilter. Refer to How to Filter a Data Set ( CotrolDesk Next Geeratio Basic Practices Guide). New Features ad Migratio November

72 CotrolDesk Next Geeratio New ECU Diagostics Features (CotrolDesk 4.3) Workig with several ODX databases (oly for ECU Diagostics v2.0.2 devices) If you work with a ECU Diagostics v2.0.2 device, you ca specify several ODX diagostics databases for it ad switch betwee them. Workig with several ODX databases eables you to check a further ODX diagostics database withi a existig experimet without havig to modify or copy the experimet. After a successful test, you ca easily make the ew diagostics database the oly diagostics database for the device by removig the other databases. Refer to Basics of the ECU Diagostics Device ( Geeratio Basic Practices Guide). CotrolDesk Next Optimizig the database If you work with a ECU Diagostics v2.0.2 device, you ca use a proprietary biary format istead of ODX data for the diagostics database. Usig biary files speeds up experimet loadig ad lets you work with large ODX databases, sice memory usage is reduced. However, trasformig the ODX data ito the biary format takes some time, so you should thik carefully whether to use ODX data or the biary format with your experimet. Usig the biary format is useful for experimets That are frequetly loaded, ad whose diagostics database is modified oly rarely. That require large ODX databases. For details, refer to How to Cofigure a ECU Diagostics Device ( CotrolDesk Next Geeratio Basic Practices Guide). Ehacemets to ECU flash memory programmig via ECU diagostics The dialog for programmig the flash memory of a ECU via a diagostic protocol is ehaced. Refer to How to Program the ECU Flash Memory via a Diagostic Protocol ( CotrolDesk Next Geeratio Basic Practices Guide). Measuremet ad calibratio of diagostic variables: Support for TEXTTABLES For TEXTTABLEs i a ODX database, CotrolDesk ow geerates variables with a COMPU_VTAB coversio table whe you geerate a variable descriptio from the ODX database. Whe you visualize such a variable, for example, i a Variable Array, you ca select the coverted value i the istrumet. 72 New Features ad Migratio November 2012

73 CotrolDesk Next Geeratio Ehaced demo The ECU Diagostics demo is ehaced. Refer to ECU Diagostics Demo ( Basic Practices Guide). CotrolDesk Next Geeratio New Automatio Features (CotrolDesk 4.3) Automatig direct variable access CotrolDesk's automatio iterface ow lets you read ad write variables directly without havig to use istrumets. For example, you ca read ad write the values of scalar variables (e.g., scalar parameters ad measuremet variables) ad multidimesioal variables (e.g., value blocks, maps, curves ad measuremet arrays). Refer to Automatig Direct Variable Access ( Geeratio Advaced Practices Guide). CotrolDesk Next Automatig the Bus Navigator CotrolDesk's automatio iterface ow lets you automate bus commuicatio moitorig, loggig, ad replayig. Refer to Automatig the Bus Navigator ( CotrolDesk Next Geeratio Advaced Practices Guide). Your CotrolDesk istallatio also provides a demo for automatig the Bus Navigator i the.\demos\toolautomatio\<programmiglaguage>\ folder. Ehacemets to automatig ECU diagostics Readig DTCs from the ECU fault memory ad eviromet data for a specific DTC via automatio has bee simplified. Refer to Automatig ECU Diagostics Tasks ( Geeratio Advaced Practices Guide). CotrolDesk Next Automatig the CotrolDesk NG Properties dialog You ca ow specify most of the settigs of the CotrolDesk NG Properties dialog via automatio. Refer to the CotrolDesk Next Geeratio API Referece. Assigig exteral scripts to evets You ca ow assig exteral scripts to CotrolDesk evets. For details, refer to Importig Pytho Scripts from the Active Project or Experimet to the Evet Hadler ( CotrolDesk Next Geeratio Advaced Practices Guide). New Features ad Migratio November

74 CotrolDesk Next Geeratio Automatig groups i a experimet You ca ow add groups to a experimet via automatio. Groups are structurig elemets that are oly displayed i the project tree but ot stored i the file system. For details, refer to Add Group ( Referece). CotrolDesk Next Geeratio 74 New Features ad Migratio November 2012

75 CotrolDesk Next Geeratio Migratig to CotrolDesk Next Geeratio (CotrolDesk 4.3) Migratig to CotrolDesk Next Geeratio (CotrolDesk 4.3) Discotiuatio of the ECU Diagostics v2.0.1 Device The ECU Diagostics v2.0.1 device (supportig ASAM MCD-3 D V2.0.1) will be discotiued i This meas you must migrate to the ECU Diagostics v2.0.2 device (supportig ASAM MCD-3 D V2.0.2), the successor to the ECU Diagostics v2.0.1 device. Migratig from CotrolDesk To migrate from CotrolDesk to CotrolDesk 4.3 ad reuse existig experimets, you do ot have to carry out ay migratio steps. Migratig from CalDesk, CotrolDesk 3.x, or CotrolDesk Next Geeratio 4.0/4.1 To migrate from CalDesk, CotrolDesk 3.x, or CotrolDesk Next Geeratio 4.0/4.1 ad reuse existig experimets, you may have to carry out additioal migratio steps. For iformatio o the migratio steps, refer to Migratig to CotrolDesk Next Geeratio ( CotrolDesk Next Geeratio Migratio Guide). New Features ad Migratio November

76 CotrolDesk Next Geeratio 76 New Features ad Migratio November 2012

77 dspace HIL API.NET New Features of dspace HIL API.NET 1.3 Ehaced platform support VEOS as the ew offlie simulatio platform is supported by dspace HIL API.NET usig the MAPort implemetatio. dspace Release 7.4 provides VEOS as a ew software product to perform offlie simulatio o your host PC, but does ot iclude VEOS support by HIL API.NET 1.3. However, you must istall a add-o to dspace Release 7.4 to work with VEOS i coectio with HIL API.NET 1.3. The add-o is available at For further iformatio o the dspace HIL API.NET implemetatio, refer to dspace HIL API.NET Implemetatio - Notes. New Features ad Migratio November

78 dspace HIL API.NET 78 New Features ad Migratio November 2012

79 dspace FlexRay Cofiguratio Package Where to go from here Iformatio i this sectio New Features of dspace FlexRay Cofiguratio Package 3.0 Migratig to dspace FlexRay Cofiguratio Package New Features of dspace FlexRay Cofiguratio Package 3.0 FlexRay Cofiguratio Package Support of PDU trasmissio modes dspace FlexRay Cofiguratio Package 3.0 ow supports trasmissio modes (as defied i AUTOSAR ad later). It has two trasmissio modes called True ad False, which are assiged to the PDUs. A specific timig is defied i the commuicatio cluster file ad assiged to each trasmissio mode. The FlexRay Cofiguratio Package also provides the User-Defied trasmissio mode for creatig a additioal timig based o the LPDU timig. You ca switch betwee the PDU trasmissio modes durig ru time. You ca work with differet PDU trasmissio modes i coectio with cofiguratios based o the followig commuicatio cluster files: FIBEX 3.0 files FIBEX 3.1 files New Features ad Migratio November

80 dspace FlexRay Cofiguratio Package FIBEX files AUTOSAR system descriptio files based o AUTOSAR 3.1.4, 3.2.1, or For further iformatio, refer to How to Cofigure PDU Trasmissio Modes ( FlexRay Cofiguratio Tool Guide). Update bit behavior accordig to AUTOSAR The update bit behavior has chaged i dspace FlexRay Cofiguratio Package 3.0. The update bit behavior is ow defied o the basis of AUTOSAR specificatios. Up to dspace FlexRay Cofiguratio Package 2.7, the update bit of a TX PDU was set to 1 each time that the payload of the PDU had chaged. As of dspace FlexRay Cofiguratio Package 3.0, the update bit is set to 1 each time that the IPDU data is packed, eve if o ew data is available. IPDU data is packed accordig to IPDU timig, that is, the update bit value is set to 1 each time that the IPDU is set. Update bit maipulatio has also chaged: It ca ow be performed for a cyclic IPDU oly whe the IPDU is set, ot each time that the LPDU is set, because this would be a idirect maipulatio of the PDU timig. Support of static evet PDUs With dspace FlexRay Cofiguratio Package 3.0, static evet PDUs are o loger treated like cyclic PDUs. A trigger for sedig static evet PDUs is available. The trigger is part of the PDU bus of the RTIFLEXRAYCONFIG PDU TX or FLEXRAYCONFIG PDU TX block. Ehacemets to static TX PDUs With older versios of the dspace FlexRay Cofiguratio Package, static TX PDUs were packed accordig to the LPDU timig, ad ay cycle time defiitio was ot evaluated. dspace FlexRay Cofiguratio Package 3.0 takes ito accout the cycle time of static TX PDUs, which are ow packed accordig to their cycle times. Thus, the update bit of a static TX PDU is set to 1 oly i the cycles i which the PDU is ewly packed. FlexRay Cofiguratio Tool Support of AUTOSAR System Template The FlexRay Cofiguratio Tool ow also supports the AUTOSAR System Template based o AUTOSAR Release for describig FlexRay etworks. 80 New Features ad Migratio November 2012

81 dspace FlexRay Cofiguratio Package Alias ame for physical bus access The FlexRay Cofiguratio Tool lets you specify a alias for the physical FlexRay bus. The specified alias ame is used i CotrolDesk Next Geeratio's Bus Navigator. It is displayed i the Bus Navigator tree ext to the respective cotroller ico. For further iformatio, refer to Geeral Page ( Cofiguratio Tool Referece). FlexRay FlexRay Cofiguratio Blockset Assigig tasks to timetables The FLEXRAYCONFIG TIMETABLE TASK blocks that were used to assig tasks to timetables i previous versios of the FlexRay Cofiguratio Blockset are obsolete. The block is still visible i the FlexRay Cofiguratio Blockset for migratio purposes, but it o loger provides fuctioality. FlexRay Cofiguratio Blockset 2.0 ow uses Ruable Fuctio blocks of the Model Port Block Library to assig tasks to timetables. Ruable Fuctio blocks are added to the automatically geerated FlexRay model durig the geeratio process. A Ruable Fuctio block is amed after its task. The block lets you view the port cofiguratio settigs ad displays the block parameters specified durig the geeratio process. Whe you update the FlexRay blocks i your Simulik model, the Ruable Fuctio blocks are icluded i the automatic update process. For further iformatio, refer to the Simulik Model Block Referece. New Features ad Migratio November

82 dspace FlexRay Cofiguratio Package Migratig to dspace FlexRay Cofiguratio Package 3.0 Migratig models based o dual-chael cofiguratios with differet timigs for the chaels After a FlexRay model based o a dual-chael cofiguratio is migrated, the default trasmissio mode is assiged to all PDUs by the FlexRay Cofiguratio Tool regardless of chael. If your model is based o a dual-chael cofiguratio with differet timigs for the two chaels, you must set the trasmissio mode for the PDUs separately for each chael durig ru time. Switch the trasmissio mode where ecessary. Chaged update bit behavior The update bit behavior has chaged i dspace FlexRay Cofiguratio Package 3.0, which causes differeces i the ru-time behavior whe you reuse existig FlexRay models. To make the ew update bit behavior available to a existig FlexRay model, you must geerate ew cofiguratio data ad code for the FlexRay cofiguratio with the FlexRay Cofiguratio Tool ad the update your Simulik model ad start the build process. Migratig models with static evet PDUs The hadlig of static evet PDUs has chaged. Now a trigger is used to sed static evet PDUs. The trigger is part of the PDU bus of the RTIFLEXRAYCONFIG PDU TX or FLEXRAYCONFIG PDU TX block. If you use PDU-based modelig, you must add the TxTrigger iport of the TX PDU block maually. There is o automatic model update. You ca copy the trigger part from the ewly geerated PDU mappig subsystem. With sigal-based modelig, static evet PDUs are ot supported. Static evet PDUs caot be used, that is, they are ot set ad their update bits remai 0. Chaged trasmissio times for static TX PDUs The trasmissio times of static TX PDUs have chaged. Static TX PDUs are ow set accordig to their cycle times, if available. The chaged trasmissio times ca cause differeces i the ru-time behavior whe you reuse existig FlexRay models cotaiig static TX PDUs with cycle times. To apply the ew trasmissio times to your model, you must first geerate ew code with the FlexRay Cofiguratio Tool, ad the update your Simulik model ad start the build process. 82 New Features ad Migratio November 2012

83 dspace Pytho Extesios Where to go from here Iformatio i this sectio New Features of dspace Pytho Extesios Migratig to dspace Pytho Extesios New Features of dspace Pytho Extesios 1.3 dspace Platform Maagemet API With the dspace Platform Maagemet API, you ca access your platform via script. For example, you ca register a platform ad load a real-time applicatio. It is ot ecessary to use a program such as AutomatioDesk or CotrolDesk Next Geeratio for platform maagemet. For further iformatio, refer to dspace Platform Maagemet API Referece. New Features ad Migratio November

84 dspace Pytho Extesios Ehaced platform support VEOS as the ew offlie simulatio platform is supported by dspace Pytho Extesios usig the HIL API Pytho implemetatio for the MAPort. dspace Release 7.4 provides VEOS as a ew software product to perform offlie simulatio o your host PC, but does ot iclude VEOS support by Pytho Extesios 1.3. To work with VEOS i coectio with Pytho Extesios, you must istall a add-o to dspace Release 7.4. The add-o is available at AddO. For further iformatio o the dspace HIL API Pytho Implemetatio, refer to dspace HIL API Pytho Implemetatio - Notes. Migratig to dspace Pytho Extesios 1.3 Registerig the platform To use a platform with rtplib2 or the dspace HIL API Pytho Implemetatio of the MAPort, it has to be registered via the dspace Platform Maagemet API or CotrolDesk Next Geeratio or AutomatioDesk. Platforms registered via CotrolDesk 3.x are igored. 84 New Features ad Migratio November 2012

85 ECU Iterface Maager Where to go from here Iformatio i this sectio New Features of ECU Iterface Maager Migratig to ECU Iterface Maager New Features of ECU Iterface Maager 1.2 Automatig the ECU Iterface Maager You ca automate the applicatio cofiguratio ad code geeratio via the ew ECU Iterface Maager automatio iterface. The mai fuctios of the automatio iterface are Maagig, i.e., opeig, savig, ad closig a project Importig software modules (ECU applicatios ad dspace bypassig services) Addig bypassig service calls to the applicatio Exportig the applicatio You ca automate the ECU Iterface Maager i two ways: Via a iterface that allows you to automate the ECU Iterface Maager via XML files or XML fragmets. The iterface ca be used via commad lie. Via a M API that allows you to automate the ECU Iterface Maager from MATLAB. For details, refer to Automatig the ECU Iterface Maager ( Iterface Maager Guide). ECU New Features ad Migratio November

86 ECU Iterface Maager Password protectio for ECU applicatios The ecryptio tool of the ECU Iterface Maager ow has a password protectio optio so that suppliers ca give software modules better protectio whe shippig them to their customers. Software module descriptio files ca be ecrypted ad passwordprotected. For details, refer to Ecryptig a Software Module Descriptio File ( ECU Iterface Maager Guide). Disablig fuctio calls ad write accesses To improve performace, you ca disable fuctio calls ad write accesses to variables. The disabled parts of the code are refereced i the exported A2L file. You ca disable fuctios i the ECU code to improve the ECU's rutime behavior. You ca use the saved processig time for the itegratio of ew iteral bypass fuctios. You ca disable write accesses to ECU variables. This allows you to specify the values of these variables by usig a measuremet ad calibratio tool such as CotrolDesk Next Geeratio or by usig a bypass fuctio. For details, refer to How to Disable Code Items i the ECU Applicatio ( ECU Iterface Maager Guide). Backup curret project You ca ow back up your curret project from the ECU Iterface Maager. The project files are archived with relative paths, so they ca be extracted aywhere. If a ZIP archive cotais a file from a differet file system, the absolute path is stored. For details, refer to Backup Project ( ECU Iterface Maager Referece) ad Ope Project from Backup ( ECU Iterface Maager Referece). LOG file You ca ope the ECU Iterface Maager's LOG file directly from the user iterface of the ECU Iterface Maager. For details, refer to Log File ( ECU Iterface Maager Referece). 86 New Features ad Migratio November 2012

87 ECU Iterface Maager Migratig to ECU Iterface Maager 1.2 Migratig projects last saved with a former versio of ECU Iterface Maager. I ECU Iterface Maager 1.2, you ca reuse projects that were last saved with a former versio of the ECU Iterface Maager. However, if you save them i ECU Iterface Maager 1.2, you ca o loger use them with a former versio of the ECU Iterface Maager. Savig a project uder a ew ame Whe you ope a project that was last saved with a former versio of the ECU Iterface Maager i ECU Iterface Maager 1.2 ad save it, the ECU Iterface Maager prompts you to save it uder a ew ame. This lets you keep a versio of the project with which you ca work i the former versio of ECU Iterface Maager. New Features ad Migratio November

88 ECU Iterface Maager 88 New Features ad Migratio November 2012

89 Model Compare Product use prohibited i Uited States You are ot licesed to use Model Compare i the Uited States. You are ot allowed to use or permit others to use this product i the Uited States or i ay way that violates the laws of the Uited States. Where to go from here Iformatio i this sectio New Features of Model Compare Migratio to Model Compare New Features of Model Compare 2.3 Ehaced tree view display optios Model Compare ow offers eve more optios for showig/hidig blocks, lies, ad aotatios i the tree view of the Model Navigator. The improvemet also icludes shortcut access to the most importat optios. For details, refer to the descriptio of the Block Display ( Model Compare Referece), Lie Display ( Model Compare Referece), ad Aotatio Display ( Model Compare Referece) toolbar buttos. Tree view display cosiderig commets Model Compare ow ca show/hide odes i the tree view depedig o whether the odes are commeted (icludig shortcut access), refer to the Node Display Cocerig Commets ( Model Compare Referece) toolbar butto. New Features ad Migratio November

90 Model Compare Highlightig with smarter widow opeig Durig recursive highlightig, Model Compare o loger opes each of the subsystems where blocks or lies are highlighted, but oly the earest commo subsystem is displayed i Simulik. Refer to How to Visualize Model Differeces i MATLAB ( Model Compare Guide). Savable highlightig As a alterative to highlightig, you ca ow colorize block differeces for oe or more selected subsystems or blocks as a kid of permaet or savable highlightig. If subsystems are selected, all the child subsystems ca also be colorized recursively. Colorizatio ca be saved with the Simulik model but it caot be removed (udoe) from withi Model Compare. Refer to Colorize Differeces ( Model Compare Referece) ad Colorize Differeces Recursively ( Model Compare Referece). Support of SLX file format Model Compare ow supports the SLX Simulik model file format. You ca dump, compare, ad merge SLX files i the same way as with MDL model files. Compatibility with TargetLik Model Compare 2.3 is fully compatible with TargetLik 3.4. Migratio to Model Compare 2.3 User prefereces ad compariso settigs User prefereces ad compariso settigs are stored separately from the tool. Thus, Model Compare 2.3 does ot make use of the user prefereces ad compariso settigs previously specified with Model Compare 2.0/2.1/2.2, but uses the defaults. However, user prefereces ad compariso settigs that have bee exported with Model Compare 2.0/2.1/2.2 ca be imported by Model Compare 2.3. Model Compare 2.3 lets you specify more user prefereces ad compariso settigs tha is possible with Model Compare 2.0 or older. For details refer to User Prefereces Dialog ( Model Compare Referece). 90 New Features ad Migratio November 2012

91 ModelDesk New Features of ModelDesk 2.6 New supported platform dspace Release 7.4 provides VEOS as a ew software product to perform offlie simulatio o your host PC. However, you must istall a add-o to dspace Release 7.4 to work with VEOS i coectio with ModelDesk 2.6. The add-o is available at Support of Simulik SLX model format ModelDesk ow supports the ew Simulik SLX model format. With MATLAB R2012b, models cotaiig ASM blocks ca be opeed or saved i MDL or SLX format. Both formats ca be used i ModelDesk projects ad for custom libraries. Exteded tool automatio The tool automatio iterface of ModelDesk is exteded. You ca ow save, delete, lik or dowload parameter files via the automatio iterface. You ca recofigure parameter sets via the automatio iterface, for example, chagig the trasmissio from maual to automatic. New Features ad Migratio November

92 ModelDesk 92 New Features ad Migratio November 2012

93 MotioDesk Where to go from here Iformatio i this sectio New Features of MotioDesk Migratig to MotioDesk New Features ad Migratio November

94 MotioDesk New Features of MotioDesk 3.1 Scee Editor The Scee Editor has a uiform scale mode. Visual ehacemets The visualizatio is ehaced. MotioDesk has ew settigs for atmospherics: rai ad sow fall. A ew fullscree mode shows the scee without ay frames. Frictio maps modeled with ModelDesk's Road Geerator ca be visualized. New supported platforms or coectio The followig features are ew for the data source: MicroAutoBox II is supported as a simulatio platform. Platforms with a slot CPU that are coected to the host PC via Etheret are supported. The frame rate may be slow for both features. Automatio iterface MotioDesk has a automatio iterface which lets you use scripts to cotrol MotioDesk. It provides the followig features: Projects ad experimets o Opeig ad savig project ad experimet 94 New Features ad Migratio November 2012

95 MotioDesk Library o Scee o o o o o Importig 3-D objects ito the customer object library Addig ad removig movable objects Readig ad settig properties of movable objects Addig ad removig static objects Readig ad settig properties of static objects Reloadig the scee Visualizatio o o Startig ad stoppig the aimatio Settig the widow mode (ormal or full scree) Related topics Basics Automatig MotioDesk ( HowTos MotioDesk Guide) How to Visualize Rai ad/or Sow Fall ( MotioDesk Guide) Migratig to MotioDesk 3.1 Migratig from MotioDesk ad earlier From MotioDesk 2.2, there is a differet project/experimet structure for maagig experimet data. Earlier MotioDesk projects must therefore be migrated. For details, refer to Migratig from MotioDesk ad Lower ( MotioDesk Guide). Migratig from MotioDesk ad earlier As MotioDesk uses aother format for the 3-D objects, the scees ad custom 3-D objects must be migrated. For details, refer to Migratig from MotioDesk ad Lower ( MotioDesk Guide). New Features ad Migratio November

96 MotioDesk 96 New Features ad Migratio November 2012

97 RapidPro Cotrol Uit RTI Blockset New Features of the RapidPro Cotrol Uit RTI Blockset Arbitrary crakshaft wheel desig You ca specify a crakshaft wheel via a wavetable comprisig 7200 data poits (correspodig to a agular resolutio of 0.05 ). Specifyig a crak wheel via wavetable is advatageous because: The gaps ad teeth of a crakshaft wheel ca have arbitrary legths. Asymmetric crakshaft wheels ca be used. There is o eed to specify a camshaft evaluatio segmet. Sychroizatio ca be achieved faster. For details o this ew feature, refer to Basics o Crakshaft Wheel Specificatio ( RapidPro System I/O Subsystem MPC565 Implemetatio Features). Support of reverse crakshaft rotatio A reverse crakshaft rotatio does ot ecessarily lead to the loss of sychroizatio. This is possible, if the crakshaft wheel is specified via wavetable ad you have eabled the reverse crakshaft operatio mode. Sophisticated iformatio o the egie status is retured. For details o this ew feature, refer to Basics o the Egie Status (Crak Wavetable) ( RapidPro System I/O Subsystem MPC565 Implemetatio Features). New Features ad Migratio November

98 RapidPro Cotrol Uit RTI Blockset Smoothed speed measuremet If the crakshaft wheel is specified via wavetable, you ca smooth speed measuremet by applyig a recursio. The measured speed value ad the last speed result are used to calculate the egie speed. The ifluece of the last speed result, i.e., the degree of smoothess, is defied by a weightig factor. I additio, speed measuremet is more precise if the crakshaft wheel is specified via wavetable ad the speed chages abruptly, for example, at a gap. For details o this ew feature, refer to Basics o Speed Measuremet (Crak Wavetable) ( RapidPro System I/O Subsystem MPC565 Implemetatio Features). 98 New Features ad Migratio November 2012

99 Real-Time Testig Where to go from here Iformatio i this sectio New Features of Real-Time Testig Migratig to Real-Time Testig New Features of Real-Time Testig 2.0 New supported platform dspace Release 7.4 provides VEOS as a ew software product to perform offlie simulatio o your host PC. However, you must istall a add-o to dspace Release 7.4 to work with VEOS i coectio with Real-Time Testig (RTT) 2.0. The add-o is available at Migratig to Real-Time Testig 2.0 Limitatio of Real-Time Testig caused by the istallatio Real-Time Testig 1.6 is part of Release 6.5. If you activate Release 6.5, all tools which use Real-Time Testig from the Pytho iterpreter use Real-Time Testig 1.6 regardless of the settigs i the dspace Istallatio Maager. This also applies to dspace tools istalled with Release 7.4. Sice Release 6.6 (Real-Time Testig 1.7), this limitatio does ot exist. New Features ad Migratio November

100 Real-Time Testig 100 New Features ad Migratio November 2012

101 RTI/RTI-MP ad RTLib Where to go from here Iformatio i this sectio New Features of RTI/RTI-MP ad RTLib 101 Migratio Aspects of RTI/RTI-MP ad RTLib 103 New Features of RTI/RTI-MP ad RTLib Supported ew features itroduced with MATLAB R2012a RTI ad RTI-MP support the followig ew features itroduced with MATLAB R2012a: Icremetal code geeratio for top-level models Simulik SLX model format Possible problems with icremetal code geeratio With dspace Release 7.4, RTI supports the Icremetal Code Geeratio for Top-Level Models feature itroduced with MATLAB R2012a. If o chages i the model are detected, the build process skips code geeratio for the model ad recompiles the code which was geerated i the last build process. This ca cause problems if the RCP & HIL eviromet has chaged sice the last code geeratio. For example, the RCP & HIL eviromet is chaged if you switch to aother RCP & HIL istallatio. For further iformatio, refer to Troubleshootig ( RTI ad RTI-MP Implemetatio Guide). New Features ad Migratio November

102 RTI/RTI-MP ad RTLib Usupported ew features of MATLAB R2012b RTI ad RTI-MP do ot support the followig ew features i MATLAB R2012b: Commetig out blocks Code geeratio for protected models rti_mdlversioget commad discotiued The rti_mdlversioget commad is obsolete ad has bee removed. It is ot compatible to the ew SLX model format. Rebuild detectio for CotrolDesk Next Geeratio RTI ad RTI-MP provide specific build iformatio so that CotrolDesk Next Geeratio ca detect whether a ew applicatio file is available. MicroAutoBox MicroAutoBox has some hardware ad software ehacemets. Acceleratio sesor The base board of MicroAutoBox II (DS ad later) provides a acceleratio sesor. The measuremet is supported by RTLib ad RTI. For further iformatio, refer to Oboard Sesors ( MicroAutoBox Features). Pressure sesor Pressure measuremet is ow also supported by RTI. For further iformatio, refer to Oboard Sesors ( MicroAutoBox Features). Watchdog hadlig There is ew flexible watchdog hadlig for MicroAutoBox II (DS ad later) supported by RTLib. With a watchdog, you ca moitor a task i your real-time applicatio. For further iformatio, refer to Watchdog Hadlig ( MicroAutoBox Features). MicroAutoBox cofiguratio tool The ds1401cofig commad lie utility is ow a dialog-based cofiguratio tool, which you ca ope by callig DS1401_Cofig. For easy access, you ca itegrate the tool as a user fuctio, for example, i CotrolDesk Next Geeratio. For further iformatio, refer to Itegratig ito a Network ( MicroAutoBox II Hardware Istallatio ad Cofiguratio). Ejectig the USB Flight Recorder device For a safe removal of the USB mass storage device used for flight recordig, there are ow RTLib fuctios ad a RTI block for ejectig the device. For further iformatio, refer to USB Flight Recorder ( MicroAutoBox Features). 102 New Features ad Migratio November 2012

103 RTI/RTI-MP ad RTLib Loadig slave applicatios to DS2302 boards To load slave applicatios to a DS2302 board, RTI provides the ew DS2302_DSP_SETUP_Bx block. Slave applicatios are writte i the C programmig laguage. To load them to the DS2302, they must be coverted to a itermediate format (SLC format). The the block icludes them i the real-time applicatio for the processor board ad loads them to the DS2302 DSPs durig applicatio start. For further iformatio, refer to DS2302_DSP_SETUP_Bx ( RTI Referece). DS2302 Migratio Aspects of RTI/RTI-MP ad RTLib Loadig slave applicatio to DS2302 boards As the cocept for loadig a slave applicatio to DS2302 boards has chaged (see New Features of RTI/RTI-MP ad RTLib o page 101), you must modify your real-time model to use the ew loadig cocept. If the real-time model is implemeted i Simulik, you must geerate the SLC files for the slave applicatios, add the DS2302_DSP_SETUP_Bx block to your Simulik model ad rebuild the real-time applicatio. For details, refer to How to Load Slave Applicatios via RTI ( DS2302 DSP Programmig). If the real-time model is had-coded i C, you must geerate the SLC files for the slave applicatios, add a loadig fuctio to your C program ad rebuild the real-time applicatio. For details, refer to How to Load a Slave Applicatio via a RTLib Fuctio ( DS2302 DSP Programmig). New Features ad Migratio November

104 RTI/RTI-MP ad RTLib 104 New Features ad Migratio November 2012

105 RTI Bypass Blockset Where to go from here Iformatio i this sectio New Features of the RTI Bypass Blockset Migratig to RTI Bypass Blockset New Features of the RTI Bypass Blockset RTI Bypass Blockset Ehacemets to the RTIBYPASS_FUNCTION_BLx block The RTIBYPASS_FUNCTION_BLx block provides the followig ehacemets: The Variables page ow makes it easier to itegrate custom C code ito the bypass applicatio. Whe you add a source file, all its fuctios are parsed ad displayed hierarchically with their parameters for you to select from. The RTIBYPASS_FUNCTION_BLx block ow supports global variables related to the source code files. Whe you add a source file cotaiig iformatio o global variables, the global variables are displayed o the Variables page. You ca select these variables to be used as iput ad/or output values for a fuctio call. The iput ad output ports of a Fuctio block are therefore ow assiged by evaluatig the parameters of the C fuctio selected for the block, the fuctio's retur values, ad the selected global variables. New Features ad Migratio November

106 RTI Bypass Blockset The RTIBYPASS_FUNCTION_BLx block ow supports value coversio. You ca add a A2L file associated to a imported C module to the Fuctio block. The coversio iformatio for the fuctio's iput ad output variables is imported to the model from the added A2L file. If value coversio is activated for a variable, the coverted (physical) value is used for the variable i model cotext. Refer to RTIBYPASS_FUNCTION_BLx ( RTI Bypass Blockset Referece). Reusig existig ECU variables with the iteral bypass model The RTI Bypass Blockset ow allows you to reuse ECU variables that were already defied i the origial ECU code ad its associated A2L file with the iteral bypass model. If eabled, the ECU applicatio ad the iteral bypass applicatio use the same sigal ad parameter istaces, that is, they share the same memory locatios. Otherwise, the iteral bypass code declares its ow represetatios. Reusig ECU variables saves ECU flash memory, sice o extra memory has to be allocated. Refer to Build Page (RTIBYPASS_SETUP_BLx for INTERNAL) ( RTI Bypass Blockset Referece). Support of ASAM MCD-2 MC Ver. 1.6 The RTI Bypass Blockset supports A2L ad AML files that are compatible with versio 1.6 of the ASAM MCD-2 MC stadard. RTI Bypass Blockset MATLAB API Support of ehacemets to RTIBYPASS_FUNCTION_BLx block The RTI Bypass Blockset MATLAB API supports the ehacemets to the RTIBYPASS_FUNCTION_BLx block. It comes with ew ad modified methods for fuctio hadlig. For details, refer to the RTI Bypass Blockset MATLAB API Referece. Method discotiuatio The followig methods are obsolete due to chages i the RTIBYPASS_FUNCTION_BLx block: SET_HEADER GET_HEADER UNSET_HEADER 106 New Features ad Migratio November 2012

107 RTI Bypass Blockset Migratig to RTI Bypass Blockset Workig with models from earlier RTI Bypass Blockset versios 2.x The curret release comes with RTI Bypass Blockset 2.9.1, which is compatible with earlier blockset versios 2.x. However, data maagemet has chaged compared to RTI Bypass Blockset Versio 2.5 or earlier. If you have a Simulik model built with blockset versio 2.5 or earlier ad ope it with RTI Bypass Blockset 2.9.1, the old Data Dictioary file (file ame extesio DD) is replaced by a ew Data Dictioary file (file ame extesio VDB) usig the iformatio stored i the Setup block as soo as you ope ad close the Setup block dialog by clickig OK, or ope the Read, Write, Upload or Dowload block dialog ad click the Fill Variable Selector butto o the Variables page. If you have a model that was saved with RTI Bypass Blockset ad wat to use it with RTI Bypass Blockset 2.5 or earlier, the model's Data Dictioary file for the earlier blockset versio (file ame extesio DD) is recreated as soo as you update the A2L files i the Setup block or ope the Read, Write, Upload or Dowload block ad click the Fill Variable Selector butto o the Variables page. The Data Dictioary file created uder RTI Bypass Blockset (file ame extesio VDB) remais o disk. To eable the RTI Bypass Blockset to recreate the data dictioary, the ASAM-MCD 2MC (A2L) files specified i the Setup block must be accessible at the specified locatio ad must be uchaged. Reusig a model with Fuctio block i earlier RTI Bypass Blockset versios The Fuctio block i RTI Bypass Blockset is ot dowward compatible with the Fuctio blocks i earlier RTI Bypass Blockset versios. If you have a model with a Fuctio block that was saved with RTI Bypass Blockset ad you wat to use it with a earlier RTI Bypass Blockset versio, you must delete the Fuctio block ad replace it by a ew oe from the earlier blockset versio. Migratio aspects of RTI Bypass Blockset MATLAB API Due to chages i the RTIBYPASS_FUNCTION_BLx block, the RTI Bypass Blockset MATLAB API for RTI Bypass Blockset is icompatible with earlier versios. You possibly caot reuse existig batch scripts to automate the creatio ad cofiguratio of RTI MATLAB models if they cotai methods for fuctio hadlig. New Features ad Migratio November

108 RTI Bypass Blockset 108 New Features ad Migratio November 2012

109 RTI CAN MultiMessage Blockset Where to go from here Iformatio i this sectio New Features of the RTI CAN MultiMessage 109 Blockset 2.7 Migratig to RTI CAN MultiMessage Blockset New Features of the RTI CAN MultiMessage Blockset 2.7 Support of AUTOSAR System Template The RTI CAN MultiMessage Blockset ow also supports the AUTOSAR System Template based o AUTOSAR Release for describig CAN etworks. Refer to Geeral Settigs Page (RTICANMM MaiBlock) ( MultiMessage Referece). RTI CAN New Features ad Migratio November

110 RTI CAN MultiMessage Blockset Migratig to RTI CAN MultiMessage Blockset 2.7 Workig with models from earlier RTI CAN MultiMessage Blockset versios To reuse a model created with a earlier RTI CAN MultiMessage Blockset versio, you must update the S-fuctios for all the RTICANMM blocks ad save the model before modifyig the CAN cofiguratio. To create ew S-fuctios for all the RTICANMM blocks i your model i oe step, you ca perform oe of the followig actios after opeig the model: I the MATLAB Commad Widow, eter rtimmsu_update('system', gcs) For further iformatio o the commad ad its optios, eter help rtimmsu_update i the MATLAB Commad Widow. Select the Create S-Fuctio for all CAN Blocks commad from the Optios meu of the RTICANMM GeeralSetup block. For further iformatio, refer to Limitatios with RTICANMM ( CAN MultiMessage Referece). RTI Reusig CAN bus cofiguratios last saved i CotrolDesk or earlier Suppose you worked i CotrolDesk or earlier with a CAN bus cofiguratio based o a real-time applicatio built with RTI CAN MultiMessage Blockset or earlier. Whe you reuse this CAN bus cofiguratio i CotrolDesk after rebuildig the applicatio with RTI CAN MultiMessage Blockset 2.7, you caot perform moitorig, loggig ad replay (due to a chaged build process). There are two ways to perform moitorig, loggig ad replay: Use the DSMigrateBusCfg.exe commad lie tool i CotrolDesk to migrate your existig CAN bus cofiguratio to CotrolDesk Refer to Migratig to CotrolDesk o page 58. Create a ew bus cofiguratio i CotrolDesk 3.7.4, ad the add the required moitor, logger ad replay odes to the Bus Navigator tree agai. 110 New Features ad Migratio November 2012

111 RTI LIN MultiMessage Blockset Where to go from here Iformatio i this sectio New Features of the RTI LIN MultiMessage 111 Blockset 2.0 Migratig to RTI LIN MultiMessage Blockset New Features of the RTI LIN MultiMessage Blockset 2.0 Support of AUTOSAR System Template The RTI LIN MultiMessage Blockset ow also supports the AUTOSAR System Template based o AUTOSAR Release for describig LIN etworks. Refer to Geeral Settigs Page (RTILINMM MaiSetup) ( MultiMessage Referece). RTI LIN Support of LDF files accordig to the SAE J2602 stadard The RTI LIN MultiMessage Blockset ow also supports LDF files accordig to the SAE J2602 stadard for describig LIN etworks. You ca base your cofiguratio o a imported J2602-compliat LDF file. New Features ad Migratio November

112 RTI LIN MultiMessage Blockset Migratig to RTI LIN MultiMessage Blockset 2.0 Workig with models from earlier RTI LIN MultiMessage Blockset versios To reuse a model created with a earlier RTI LIN MultiMessage Blockset versio, you must update the S-fuctios for all the RTILINMM blocks ad save the model before modifyig the LIN cofiguratio. To create ew S-fuctios for all the RTILINMM blocks i your model i oe step, you ca perform oe of the followig actios after opeig the model: I the MATLAB Commad Widow, eter rtimmsu_update('system', gcs) For further iformatio o the commad ad its optios, eter help rtimmsu_update i the MATLAB Commad Widow. Select the Create S-Fuctio for all LIN Blocks commad from the Optios meu of the RTILINMM GeeralSetup block. For further iformatio, refer to Limitatios of RTI LIN MultiMessage Blockset ( RTI LIN MultiMessage Referece). Reusig LIN bus cofiguratios last saved i CotrolDesk or earlier Suppose you worked i CotrolDesk or earlier with a LIN bus cofiguratio based o a real-time applicatio built with RTI LIN MultiMessage Blockset or earlier. Whe you reuse this LIN bus cofiguratio i CotrolDesk after rebuildig the applicatio with RTI LIN MultiMessage Blockset 2.0, you caot perform moitorig, loggig ad replay (due to a chaged build process). There are two ways to perform moitorig, loggig ad replay: Use the DSMigrateBusCfg.exe commad lie tool i CotrolDesk to migrate your existig LIN bus cofiguratio to CotrolDesk Refer to Migratig to CotrolDesk o page 58. Create a ew bus cofiguratio i CotrolDesk 3.7.4, ad the add the required moitor, logger ad replay odes to the Bus Navigator tree agai. 112 New Features ad Migratio November 2012

113 RTI FPGA Programmig Blockset Limited availability outside Europe ad Asia, please iquire. Where to go from here Iformatio i this sectio New Features of the RTI FPGA Programmig Blockset Migratig to RTI FPGA Programmig Blockset New Features of the RTI FPGA Programmig Blockset 2.4 Ehacemets to the RTI blocks of the Processor Iterface library I the PROC_SETUP_BL block, you ca ow also add FPGA model INI files to the build process i the Processor-Build model mode. FPGA subsystems ca still oly be added i FPGA-Build/Offlie simulatio model mode. For further iformatio, refer to RTI FPGA Programmig Blockset - Processor Iterface Referece. Ehacemets to the RTI blocks of the FPGA Iterface library I the FPGA_SETUP_BL block, the dialog settigs have bee prepared for a future ehacemet. The settigs are curretly deactivated. For further iformatio, refer to RTI FPGA Programmig Blockset - FPGA Iterface Referece. New Features ad Migratio November

114 RTI FPGA Programmig Blockset Exteded Xilix support The RTI FPGA Programmig Blockset ow supports Versios 13.4 ad 14.1 of the Xilix desig tools. Xilix Desig Tools Versio Operatig System MATLAB Versio 1) ) o Widows XP Professioal SP3 (32-bit versio) o Widows 7 Busiess, Ultimate, ad Eterprise SP1 (32-bit versio ad 64-bit versio) ) o Widows XP Professioal SP3 (32-bit versio) o Widows 7 Busiess, Ultimate, ad Eterprise SP1 (32-bit versio ad 64-bit versio) 1) Oly 32-bit versio 2) Tested by dspace but ot officially supported by Xilix. o MATLAB R2010bSP2 2) o MATLAB R2011a o MATLAB R2011b o o MATLAB R2011a MATLAB R2011b The DS5203 FPGA Board (LX50) also supports the WebPACK Editios of the Xilix desig tools. Ehaced performace The startup phase of the build process is ow up to eight times faster. The startup phase is the time betwee startig the build process ad startig the ISE. Chagig a parameter i a block dialog of a RTI FPGA Iterface block is ow up to six times faster. Ehaced hadcode support The hadcode iterface ow supports Verilog i additio to VHDL. Simplified migratio for DS5203 ad DS5203M1 frameworks If you use oe of the DS5203 frameworks ad wat to switch to the DS5203M1 framework, you ow do ot eed to maually replace all the blocks i your model that come from the RTI FPGA Programmig Blockset. The framework migrate mechaism aalyzes the blocks ad automatically reparameterizes all the blocks that are compatible with the previous oes. After migratio you get a list of the icompatible blocks, which you have to migrate maually. This migrate mechaism also works for all the other frameworks, but there are o or oly few compatible compliaces. 114 New Features ad Migratio November 2012

115 RTI FPGA Programmig Blockset For further iformatio, refer to Usig Differet Frameworks ( FPGA Programmig Blockset Guide). RTI Related topics Basics Migratig to RTI FPGA Programmig Blockset 2.4 o page 115 Migratig to RTI FPGA Programmig Blockset 2.4 Objective There are differet methods to migrate a existig model, depedig o the blockset versio used. Migratig from RTI FPGA Programmig Blockset 1.0 to 2.4 Because the RTI FPGA Programmig Blockset 1.0 (released with dspace Release 6.4) was ot fully implemeted, a model that you implemeted with it must be migrated maually. You must replace each block of the RTI FPGA Programmig Blockset by a ew oe to make the model compatible with the curret dspace RTI eviromet for modelig, buildig ad executig. The update fuctio of the script iterface does ot support RTI FPGA Programmig Blockset 1.0. Migratig from RTI FPGA Programmig Blockset 1.1 ad higher to 2.4 If you have implemeted your FPGA applicatio usig RTI FPGA Programmig Blockset Versio 1.1 ad later, ad wat to use it with RTI FPGA Programmig Blockset 2.4, you must update the FPGA framework. You ca use the script iterface for this, refer to Updatig the FPGA framework usig the script iterface o page 115. You also have to update the framework if you have updated from MATLAB R2008b or earlier to MATLAB R2009a or later. Updatig the FPGA framework usig the script iterface Before you start migratio, you should make a backup of your model. The script iterface provides the FPGAFrameworkUpdate method to update a framework. You ca decide whether to set the block parameters to their iitial values or leave them uchaged. New Features ad Migratio November

116 RTI FPGA Programmig Blockset To update the FPGA framework without chagig the values of the block parameters rtifpga_scriptiterface('fpgaframeworkupdate', <SimulikHadle>) The script hadles all the subsystems i the model/subsystem which is specified by the Simulik hadle. The parameters of the blocks are uchaged after updatig to the curret framework versio. Example: The followig script updates the FPGA framework for ay FPGA subsystems i the processor model called MyProcModel. The specified values of the block parameters are ot chaged. ProcModelHadle = get_param('myprocmodel','hadle') rtifpga_scriptiterface('fpgaframeworkupdate', ProcModelHadle) To update the FPGA framework ad reset the values of the block parameters to their iitial values rtifpga_scriptiterface('fpgaframeworkupdate', <SimulikHadle>, 'ReIit') The script hadles all the subsystems i the model/subsystem which is specified by the Simulik hadle. The parameters of the blocks are reset to their iitial values after updatig to the curret framework versio. ProcModelHadle = get_param('myprocmodel','hadle') rtifpga_scriptiterface('fpgaframeworkupdate', ProcModelHadle,'ReIit') 116 New Features ad Migratio November 2012

117 SystemDesk 3.x Where to go from here Iformatio i this sectio New Features of SystemDesk Migratig to SystemDesk New Features ad Migratio November

118 SystemDesk 3.x New Features of SystemDesk 3.2 Where to go from here Iformatio i this sectio New Geeral Features 118 Cofigurig ad Geeratig V-ECUs 119 Simulatig Systems 126 New Geeral Features SystemDesk 3.2 has the followig ew geeral features. AUTOSAR Releases supported by SystemDesk 3.2 SystemDesk supports the followig AUTOSAR Releases ad Revisios: AUTOSAR Release Revisio ) DAI ) New i SystemDesk New Features ad Migratio November 2012

119 SystemDesk 3.x Cofigurig ad Geeratig V-ECUs RTE itervetios for testig software compoets SystemDesk lets you cofigure RTE itervetios to test software compoets durig a simulatio ru. RTE itervetios are additioal isertios to the origial RTE code that let you access the commuicatio of software compoets (SWCs) durig a simulatio ru. You ca use RTE itervetios, for example, for stimulatio or error ijectio to perform software compoet tests. With RTE itervetios (RTE itervetio poits ad services), you ca overwrite the origial commuicatio of software compoets durig ru time. You ca coect iteral or exteral stimuli to the software compoet ports via RTE itervetios. Iteral stimuli, for example, derivig from a extra stimulus SWC itegrated o the V-ECU, are coected to the SWC to be tested via extra RTE service ports. Exteral stimuli, for example, derivig from a eviromet model ruig o a coected eviromet VPU, are trasmitted by data access poits. New Features ad Migratio November

120 SystemDesk 3.x The illustratio below shows you a simplified sigal flow whe usig RTE itervetios. Stimulus SWC Virtual ECU Eviromet VPU SWC to be tested RTE itervetio poit Rte_Write (Data write access) Ruable () RTE service port Eviromet model Rte_Sigal RTE SWC RTE itervetio service Dap module with data access poits VPU ports VPU ports RTE itervetio mechaism To perform software compoet tests, SystemDesk lets you create RTE itervetios for: Read/write access of data elemets of ucoected ports of software compoets Read/write access of data elemets of coected ports of software compoets Read/write access of iterruable variables of software compoets Status retur values of RTE API fuctios 120 New Features ad Migratio November 2012

121 SystemDesk 3.x RTE itervetios are realized by usig RTE itervetio poits ad RTE itervetio services. RTE itervetio poits are additioal access poits i the RTE code. They are geerated oly whe you eable RTE itervetios. RTE itervetio poits are called up durig ru time, for example, whe a data elemet is read. For further processig, the RTE itervetio poit trasmits data elemet read to a RTE itervetio service that is liked to the RTE itervetio poit. RTE itervetio services are C fuctios also geerated i additio to the geuie RTE code. Each RTE itervetio service is triggered by the RTE itervetio poit liked to it. The RTE itervetio service specifies how to hadle the data elemet value, operatio argumet or status retur value that it gets form the RTE itervetio poit. The values/argumets ca be forwarded ad/or chaged. For this purpose, a RTE itervetio service ca have up to two iput sigals (iput ad eable) ad oe output sigal. The illustratio below shows the RTE itervetio mechaism whe workig with seder/receiver iterfaces. SWC a SWC b Rte_Write (Data write access) Data elemet Rte_Read (Data read access) Ruable_a () RTE itervetio poit 1 Rte_Sigal RTE itervetio poit 1 Ruable_c () Rte_Write (Data write access) Rte_Read (Data read access) Ruable_b () Ruable_d () Iput 1 Eable 1 Output 1 Iput 2 Eable 2 Output 2 RTE itervetio service 1 RTE itervetio service 2 I additio to what is said, SystemDesk geerates A2L variables for the iput ad output sigals of RTE itervetio services. So you ca access the RTE itervetios also via these A2L variables with a experimetig software whe executig the simulatio system o VEOS. New Features ad Migratio November

122 SystemDesk 3.x Specifyig RTE itervetios You ca specify RTE itervetios via a editor that provides access to the sigals of a ECU. You ca map oe or more RTE itervetio poits to a RTE itervetio service. So you ca modify multiple RTE sigals i the same way ad at the same time. The illustratio below shows the a example i SystemDesk's RTE itervetios editor. Whe geeratig the RTE code afterwards, SystemDesk istrumets the RTE code, adds data access poits or RTE service ports, ad specifies A2L variables as specified. Code example for a RTE itervetio The followig listig shows a code example for a RTE itervetio: File Rte_<swc>.c Std_ReturType Rte_Read_Plat_RpUpi_Upi(Float * Upi) { Std_ReturType Rte_Status = RTE_E_OK; /* read data elemet */ *Upi = RTE_IP_READ(RTE_IP_0, float32, Rte_Sigal_2); } /* API call retur */ retur RTE_IP_STATUS(RTE_IP_1, Rte_Status); 122 New Features ad Migratio November 2012

123 SystemDesk 3.x Support for the IO hardware abstractio module You ca ow cofigure the IO hardware abstractio module ad geerate a implemetatio for it to be used with VEOS simulatio. This allows you to map ECU sigals to IO hardware abstractio ports. The illustratio above shows how you ca select ECU sigals that are to be accessible via the IO hardware abstractio module. First you select a iterface from SystemDesk's library. I a secod step you select sigals from the ECU that istatiate the preselected library iterface. Whe you geerate a V-ECU implemetatio SystemDesk geerates a IO hardware abstractio module with ports ad a implemetatio. SystemDesk adds VPU ports durig system build for accessig the ECU sigals that you have mapped to IO hardware abstractio ports to be used with VEOS offlie simulatio. New Features ad Migratio November

124 SystemDesk 3.x Auto cofigure ad geerate V-ECU implemetatios With this versio SystemDesk supports the cofiguratio ad implemetatio of additioal basic software modules such as IO hardware abstractio, ECU state maager, or BSW scheduler module. SystemDesk ca ow automatically solve depedecies betwee basic software modules whe you perform tasks such as geeratig RTE, COM stack, or V-ECU implemetatio. A V-ECU implemetatio is the implemetatio of a virtual ECU (model) that ca be ru i a offlie simulatio. 124 New Features ad Migratio November 2012

125 SystemDesk 3.x The illustratio above shows the plugi methods that SystemDesk provides for the RTE module. Whe you geerate a V-ECU implemetatio, you have to execute some of the plugi methods of the RTE module. First you have to update the RTE cofiguratio, the geerate the RTE compoet, ad fially start RTE geeratio. Additioally it might be ecessary to update other module cofiguratios before updatig the RTE cofiguratio. The illustratio above shows how SystemDesk supports you whe you geerate RTE or a whole V-ECU implemetatio. Whe you select the Auto Cofigure ad Geerate - V-ECU Implemetatio commad SystemDesk automatically executes all the required plugi methods of the basic software modules that are cotaied i the selected ECU cofiguratio. Exportig V-ECU implemetatios SystemDesk ow allows you to export V-ECU implemetatios. A V- ECU implemetatio is the implemetatio of the etire virtual ECU for the purpose of simulatio. It is the startig poit for offlie simulatio with VEOS as well as for real-time simulatio o SCALEXIO (comig with a future release). Whe you export a V-ECU implemetatio, SystemDesk gathers a collectio of files that belogs to the V-ECU implemetatio i a CTLGZ file archive. New Features ad Migratio November

126 SystemDesk 3.x Files i a V-ECU implemetatio Three kids of files ca be part of a V-ECU implemetatio: Cofiguratio files (ARXML) Code files (H, C) A variable descriptio file (A2L) For details, refer to Export V-ECU Implemetatio ( Maagemet Documet). Cotaier Simulatig Systems New features of simulatig systems i cojuctio with VEOS Offlie simulatio of ECU startup You ca ow dowload a simulatio system without startig the simulatio. This allows you to modify A2L variables before simulatig systems. This feature lets you simulate startup scearios of V-ECUs. New stimulatio scearios Due to the ew V-ECU geeratio features, SystemDesk 3.2 supports the followig ew stimulatio scearios i cojuctio with VEOS: Modifyig iterruable variables ad status retur values of RTE API fuctios Stimulatig a ECU or a bus breakdow Delayig the trasmissio of bus messages The RTE itervetios mechaism lets you stimulate: Data elemets of software compoets Iterruable variables ad status retur values of RTE API fuctios Operatio argumets of cliet server calls 126 New Features ad Migratio November 2012

127 SystemDesk 3.x Migratig to SystemDesk 3.2 Migratig to SystemDesk 3.2 Usig SystemDesk 3.1 projects with SystemDesk 3.2 SystemDesk 3.2 lets you ope SystemDesk 3.1 projects. Each project is migrated automatically whe opeed the first time ad ca be saved as a SystemDesk 3.2 project. To reuse i SystemDesk 3.2 a project last saved i SystemDesk 3.0 or earlier, you have to migrate it to SystemDesk 3.1 first. For detailed iformatio o migratig projects to SystemDesk 3.1, refer to the related New Features ad Migratio documet at Simulatig systems With this versio SystemDesk supports the cofiguratio ad implemetatio of additioal basic software modules such as I/O hardware abstractio, ECU state maager, or BSW scheduler module. The ECU state maager (EcuM) cofiguratio is madatory for simulatig systems with VEOS 3.0. If you wat to simulate the systems of SystemDesk 3.1 projects that you have migrated to SystemDesk 3.2 you have to perform the followig steps: 1. Add the EcuM module cofiguratio to each ECU cofiguratio of the system you wat to simulate. For istructios o addig module cofiguratios, refer to How to Create Module Cofiguratios ( SystemDesk 3.x Guide). 2. Right-click the ECU cofiguratios ad select Auto Cofigure ad Geerate - V-ECU Implemetatio ( SystemDesk 3.x Referece) to cofigure the ECU cofiguratio ad geerate RTE code. 3. Build the simulatio system. For istructios o buildig systems, refer to How to Build the Simulatio System ( SystemDesk 3.x Guide). New Features ad Migratio November

128 SystemDesk 3.x 128 New Features ad Migratio November 2012

129 SystemDesk 4.x Where to go from here Iformatio i this sectio New Features of SystemDesk Migratig to SystemDesk New Features of SystemDesk 4.0 The ew SystemDesk 4.0 supports the modelig of software ad system architectures accordig to AUTOSAR ad SystemDesk supports all the elemets defied i the AUTOSAR schema. However, SystemDesk's mai focus is modelig the automotive software architecture, that is, the coveiet desig of software compoets with iterfaces ad iteral behaviors. Feature overview Modelig of AUTOSAR elemets. SystemDesk 4.0 supports AUTOSAR ad completely. Refer to Workig with AUTOSAR Elemets ( SystemDesk 4.x Guide). Support of a AUTOSAR package view. Refer to Workig with Packages ( SystemDesk 4.x Guide). Assigmet of AUTOSAR elemets to ARXML files, facilitatig the coectio to versio cotrol systems. Refer to Basics o Assigig AR Elemets to AUTOSAR Master Files ( SystemDesk 4.x Guide). New Features ad Migratio November

130 SystemDesk 4.x Iteroperability with other AUTOSAR-compliat tools: o o You ca export software compoets from SystemDesk 4.0 for behavior modelig i TargetLik via cotaier maagemet. Refer to Itegratio of SystemDesk ito a AUTOSAR Tool Chai ( SystemDesk 4.x Guide). You ca export a system extract from SystemDesk 4.0 for further use i basic software cofiguratio tools. Refer to Create System Extract ( SystemDesk 4.x Guide). Complete tool automatio. Refer to Automatig SystemDesk ( SystemDesk 4.x Guide). Validatio of elemets i a SystemDesk project. Refer to Validatig SystemDesk Elemets ( SystemDesk 4.x Guide). Migratig to SystemDesk 4.0 You caot reuse or import SDP project files created with SystemDesk 3.x i SystemDesk 4.0, but you ca reuse data via AUTOSAR coversio. For details o migratig to SystemDesk 4.0 ad o the differet workig cocepts i SystemDesk 3.x compared with SystemDesk 4.0, refer to Migratig to SystemDesk 4.0 ( SystemDesk 4.x Guide). 130 New Features ad Migratio November 2012

131 TargetLik Where to go from here Iformatio i this sectio New Features of TargetLik 3.4 ad TargetLik Data Dictioary 3.4 Migratig to TargetLik 3.4 ad TargetLik Data Dictioary New Features ad Migratio November

132 TargetLik New Features of TargetLik 3.4 ad TargetLik Data Dictioary 3.4 For last-miute iformatio o TargetLik 3.4 ad o potetial difficulties with model upgrades, it is recommeded to visit the TargetLik 3.4 website at Update. Where to go from here Iformatio i this sectio New Productio Code Geeratio Features 132 New AUTOSAR-Related Features 146 New TargetLik Data Dictioary Features 150 New Productio Code Geeratio Features Where to go from here Iformatio i this sectio Compoet-Based Developmet Usig Abstract Iterfaces 133 Improvemet for Custom Code 134 Optioal Deactivatio of Compute-Through- Overflow 134 Geeratig Virtual ECUs for Virtual ECU Testig 135 Specificatios of the Target Simulatio Modules 136 Code Geerator Optios 138 New API Commads 142 New Hook Fuctios 142 Access Fuctio Chages 143 Improvemet of Code Efficiecy 144 Geeral Ehacemets ad Chages New Features ad Migratio November 2012

133 TargetLik Compoet-Based Developmet Usig Abstract Iterfaces Separatig fuctioality to software modules Support of compoet-based developmet allows you to separate the overall fuctioality ito smaller software modules, called modular uits ( Modular uit ( TargetLik Advaced Practices Guide)), which ca be developed ad tested idepedetly. A separated modular uit ca be tested with full test coverage more easily. Testig with full coverage is ofte ot possible if the fuctioality is itegrated i a larger cotext ad therefore ot all the test vectors ca easily be applied directly at the modular uit. Thus the testability of modular uits is geerally higher. Later you oly have to test the iteractio betwee the modular uits i the itegratio model for coverig the overall fuctioality. Modular uits also help you solve problems with log code geeratio times ad high memory cosumptio durig code geeratio for very large models, ad ca easily be reused without modificatio across differet projects ad i differet cotexts ( Itegratio model ( TargetLik Advaced Practices Guide)). This is a advatage if you wat to chage certai aspects of modular uit implemetatio: e.g., whe you make a parameter of a modular uit a costat variable i oe ECU project ad a calibratable variable i aother project. TargetLik provides abstract iterfaces to support such chages without modifyig the modular uit itself. You ca map abstract iterfaces to cocrete implemetatios idepedetly ad after productio code has bee geerated ad tested for the modular uit (ad should therefore ot be chaged). For further iformatio, refer to Basics o Compoet-Based Developmet Usig Abstract Iterfaces ( TargetLik Advaced Practices Guide) Demo model: REPLACEABLE_DATA_ITEMS ( TargetLik Demo Models) Icremetal code geeratio for AUTOSAR SWCs o page 147 New Features ad Migratio November

134 TargetLik Improvemet for Custom Code Ehacig usupported Simulik blocks to TargetLik Ay usupported Simulik block type (icludig subsystems) ca be ehaced to a TargetLik Custom Code block (type II). Type II meas that o S-fuctio is geerated from the custom code template, but the origial MIL simulatio behavior of the ehaced Simulik block is kept. For details, refer to Custom Code for Usupported Simulik Blocks ( TargetLik Advaced Practices Guide). Width-ivariat custom code template (type II) A width-ivariat custom code template ca be (re)used i multiple Custom Code block (type II) istaces of varyig width cotexts. The width cotext relates to the block's iput ad output sigals, ad its states. Width ivariace is achieved by usig width macros i the custom code template. The width macros are resolved to the actual istace-specific widths at code geeratio time. For details, refer to Width-Ivariat Custom Code Template ( TargetLik Advaced Practices Guide). Demo model TargetLik provides a demo model, refer to CUSTOM_ENHANCEMENT ( TargetLik Demo Models). Optioal Deactivatio of Compute-Through-Overflow Cotrollig the use of CTO patters By default, TargetLik uses compute-through-overflow (CTO) code patters to improve code efficiecy. Optioally, you ca cofigure TargetLik to Never implemet CTO patters Always apply CTO code patters wheever a overflow ca occur Optimized use CTO patters to improve the code efficiecy This allows you to adapt TargetLik to your compay's codig style. New Fixed-Poit Library header file The ew header file sumprot.h was added to the Fixed-Poit Library, used by TargetLik to avoid certai 64-bit calculatios whe cofigured to ever implemet CTO patters. 134 New Features ad Migratio November 2012

135 TargetLik For further iformatio, refer to Code Geerator Optios o page 138 (The ew Code Geerator optios.) Resultig productio code chages i compariso to the code geerated by previous TargetLik versios (refer to Code Chages o page 168) Compute-Through-Overflows Property of Two's Complemet Arithmetic ( TargetLik Productio Code Geeratio Guide) Macros ad Fuctios Provided by the Fixed-Poit Library ( TargetLik File Referece) Geeratig Virtual ECUs for Virtual ECU Testig V-ECU Geeratio TargetLik lets you geerate a V-ECU for a TargetLik subsystem ad use it i virtual ECU testig (VET). V-ECUs emulate real ECUs i offlie simulatio scearios. You ca dowload the V-ECUs to VEOS, dspace's offlie simulator. This allows seamless itegratio ito the dspace tool chai ad lets you automate tests with AutomatioDesk or ru experimets i CotrolDesk Next Geeratio. This allows early testig ad validatio throughout the ECU developmet process. V-ECU Maager TargetLik's V-ECU Maager assists you i cofigurig ad performig the V-ECU build process. API commads New API commads allow you to itegrate TargetLik's V-ECU geeratio capability i your workflow. For further iformatio, refer to V-ECU Maager ( TargetLik Tool ad Utility Referece) New API Commads o page 142 Geeratig Virtual ECUs for Virtual ECU Testig ( TargetLik Advaced Practices Guide) New Features ad Migratio November

136 TargetLik Specificatios of the Target Simulatio Modules Supported evaluatio boards, microcotrollers, ad compilers The followig table shows the combiatios of evaluatio boards, microcotrollers, ad compilers supported by TargetLik 3.4 (TargetLik abbreviatios). Evaluatio Board Microcotroller Type Compiler 1) Freescale HCS12EVB 2) Freescale MC9S12DP256 Cosmic 4.7 Freescale HCS12EVB 2) Freescale MC9S12DP256 Cosmic 4.8 Freescale HCS12EVB 2) Freescale MC9S12DP256 Metrowerks CodeWarrior 3.1 Freescale HCS12EVB 2) Freescale MC9S12DP256 Metrowerks CodeWarrior 5.1 MCT HCS12 T-Board (DP256) 2) Freescale MC9S12DP256 Cosmic 4.7 MCT HCS12 T-Board (DP256) 2) Freescale MC9S12DP256 Cosmic 4.8 MCT HCS12 T-Board (DP256) 2) Freescale MC9S12DP256 Metrowerks CodeWarrior 3.1 MCT HCS12 T-Board (DP256) 2) Freescale MC9S12DP256 Metrowerks CodeWarrior 5.1 MCT HCS12 T-Board (DP512) Freescale MC9S12DP512 Cosmic 4.7 MCT HCS12 T-Board (DP512) Freescale MC9S12DP512 Cosmic 4.8 MCT HCS12 T-Board (DP512) Freescale MC9S12DP512 Metrowerks CodeWarrior 3.1 MCT HCS12 T-Board (DP512) Freescale MC9S12DP512 Metrowerks CodeWarrior 5.1 Freescale 56F8367 Evaluatio Module Freescale MC56F8367 Metrowerks CodeWarrior 8.3 Axiom CMD-0565 Freescale MPC565 Wid River Diab 5.7 Axiom CME-0555 Freescale MPC555 Gree Hills 5.1 Axiom CME-0555 Freescale MPC555 Wid River Diab 5.7 Axiom MPC5554DEMO Freescale MPC5554 GNU 4.1 Axiom MPC5554DEMO Freescale MPC5554 No loger supported Gree Hills 5.2 Axiom MPC5554DEMO Freescale MPC5554 New Gree Hills Axiom MPC5554DEMO Freescale MPC5554 Metrowerks CodeWarrior 2.8 Axiom MPC5554DEMO Freescale MPC5554 Wid River Diab 5.7 Axiom MPC5554DEMO Freescale MPC5554 Wid River Diab 5.9 Freescale MPC5561EVB Freescale MPC5561 No loger supported Gree Hills 5.2 Freescale MPC5561EVB Freescale MPC5561 New Gree Hills Freescale MPC5561EVB Freescale MPC5561 Metrowerks CodeWarrior 2.8 Freescale MPC5561EVB Freescale MPC5561 Wid River Diab 5.9 Freescale MPC5561EVB USB Freescale MPC5561 Metrowerks CodeWarrior 2.8 Freescale MPC5561EVB USB Freescale MPC5561 Wid River Diab 5.9 Freescale MPC5561EVB USB Freescale MPC5561 No loger supported Gree Hills 5.2 Freescale MPC5561EVB USB Freescale MPC5561 New Gree Hills Freescale MPC5604BEVB Freescale MPC5604B Gree Hills 5.2 Freescale MPC5604BEVB Freescale MPC5604B New Gree Hills Freescale MPC5604BEVB Freescale MPC5604B Wid River Diab 5.9 MCT S12X T-Board 2) Freescale MC9S12XDP512 Cosmic 4.8 MCT S12X T-Board 2) Freescale MC9S12XDP512 Metrowerks CodeWarrior 5.1 MCT S12X T-Board USB 2) Freescale MC9S12XDP512 Cosmic 4.8 MCT S12X T-Board USB 2) Freescale MC9S12XDP512 Metrowerks CodeWarrior 5.1 I+ME Promotio Package 166 Ifieo c167 TASKING C166/ST10 Toolchai 8.6 I+ME Promotio Package 166 Ifieo c167 TASKING C166/ST10 Toolchai 8.7 Ifieo TriBoard TriCore 1766 Ifieo TC1766 TASKING TriCore VX-Toolset New Features ad Migratio November 2012

137 TargetLik Evaluatio Board Microcotroller Type Compiler 1) Ifieo TriBoard TriCore 1766 Ifieo TC1766 No loger supported TASKING TriCore VX- Toolset 3.5 Ifieo TriBoard TriCore 1766 Ifieo TC1766 New TASKING TriCore VX-Toolset 4.0 Ifieo TriBoard TriCore MHz Ifieo TC1766 TASKING TriCore VX-Toolset 3.2 Ifieo TriBoard TriCore MHz Ifieo TC1766 No loger supported TASKING TriCore VX- Toolset 3.5 Ifieo TriBoard TriCore MHz Ifieo TC1766 New TASKING TriCore VX-Toolset 4.0 Ifieo TriBoard TriCore 1767 Ifieo TC1767 TASKING TriCore VX-Toolset 3.2 Ifieo TriBoard TriCore 1767 Ifieo TC1767 No loger supported TASKING TriCore VX- Toolset 3.5 Ifieo TriBoard TriCore 1767 Ifieo TC1767 New TASKING TriCore VX-Toolset 4.0 Ifieo TriBoard TriCore 1796 Ifieo TC1796 HighTec GNU 3.4 Ifieo TriBoard TriCore 1796 Ifieo TC1796 TASKING TriCore VX-Toolset 3.2 Ifieo TriBoard TriCore 1796 Ifieo TC1796 No loger supported TASKING TriCore VX- Toolset 3.5 Ifieo TriBoard TriCore 1796 Ifieo TC1796 New TASKING TriCore VX-Toolset 4.0 Ifieo EasyKit XC2287 Ifieo XC2287 TASKING VX-toolset for C Reesas M3A-2154 Reesas M32192 Gaio 11 Reesas M3A-2154 Reesas M32192 Gaio 9 Reesas M3A-2154 Reesas M32192 Reesas 5.1 Reesas EVB7058 Reesas SH-2E/SH7058 Reesas 9.3 Reesas EVB7058 Reesas SH-2E/SH7058 Reesas 9.4 Reesas SH72513 System Developmet Kit Reesas SH-2A-FPU/SH72513 Reesas 9.4 New Reesas AB_050_Fx4 New Reesas V850E2/FL4-μPD70F4012 New Gree Hills NEC Fx3-CAN it! NEC V850ES/FG3-µPD70F3377 New Gree Hills NEC Fx3-CAN it! NEC V850ES/FG3-µPD70F3377 No loger supported Gree Hills 5.3 NEC Fx3-CAN it! NEC V850ES/FG3-µPD70F3377 NEC ) Compiler Suite Versio Supported 2) The board is o loger distributed by dspace but is still supported for dowward compatibility For detailed iformatio o the evaluatio boards supported by TargetLik, refer to TargetLik Evaluatio Board Hardware Referece. For further PIL support combiatios that are part of a valid Software Maiteace Service (SMS) cotract, refer to dspace's TargetLik PIL Support website. New Features ad Migratio November

138 TargetLik Code Geerator Optios New Code Geerator optios The followig ew Code Geerator optios are available with TargetLik 3.4: Descriptio Explaatio Default AllowStructAssigmets Copy structs or substructs of idetical type via a sigle assigmet istead of assigmets of all struct (substruct) compoets. The C laguage allows direct assigmets of struct variables. This is equivalet to copyig all struct members but ca istead be implemeted by a compiler as copyig the storage area (e.g. via memcpy()). This Code Geerator optio gives TargetLik permissio to replace compoet-wise assigmets of structs or substructs by the assigmet of whole structs (substructs). If the situatio is ot sufficietly clear, e.g., due to code optimizatio, TargetLik will geerate the compoet-wise assigmets istead. Example: Cosider typedef struct S_tag { T3 c; T4 d; } S; typedef struct T_tag { T1 a; T2 b; S c; }; T S1; T S2;... S2.a = S1.a; S2.b = S1.b; S2.c.d = S1.c.d; S2.c.e = S1.c.e; Here, the copy may be writte istead as S2.a = S1.a; S2.b = S1.b; S2.c = S1.c; or S2 = S1; o 138 New Features ad Migratio November 2012

139 TargetLik Descriptio Explaatio Default AssumeOperatioCallsHaveNoUkowDataFlow For optimizatio purposes, treat every AUTOSAR operatio as if the Data Dictioary Operatio object has the NoDataFlowWithOtherOperatio s property set (or if the uderlyig fuctio has a fuctio class with the SIDE_EFFECT_FREE Optimizatio property set). ExploitComputeThroughOverflow Specifies whether ad whe compute-through-overflow code is implemeted. I priciple, the implemetatio of a iteractio betwee AUTOSAR operatio calls is ukow. For other fuctios, TargetLik allows a fuctio's behavior to be specified via the fuctio class Optimizatio property: "There is o ukow data flow via global variables, apart from the iterface defied i the model" (SIDE_EFFECT_FREE): Accesses to global variables ad fuctio calls accessig global variables ca be moved past a call of the respective fuctio. "There are o iteral states, ad the umber of fuctio calls alog a executio path ca be chaged" (MOVABLE): The fuctio call ca be moved ito a coditioally executed cotrol flow brach or to the secod operad of a logical AND or OR operatio. There is usually o way to specify a fuctio class for operatio calls, uless they are also server ruables. Istead, TargetLik offers the NoDataFlowWithOtherOperatios ad NoStatesOrSideEffects properties at the Data Dictioary Operatio object. This optio allows you to esure that all operatio calls ca be treated as if the fuctio class has the SIDE_EFFECT_FREE Optimizatio property set or the operatio has the NoDataFlowWithOtherOperatios property set, i.e., it overrides the NoDataFlowWithOtherOperatios property of all operatios. If the optio is switched off, the the value of the NoDataFlowWithOtherOperatios property of each operatio is evaluated. TargetLik uses compute-through-overflow (CTO) code patters to implemet efficiet additios ad subtractios ad especially to avoid 64-bit operatio. Sice CTO ca itroduce overflows by castig the operads of a additio/subtractio to a usiged data type, code checkig tools might emit warigs or errors for this kid of code. The possible values: 1 = Never: No compute-through-overflow code patter will be implemeted. 2 = Optimized: Apply compute-through-overflow patters to improve the code efficiecy. 3 = Always: Apply compute-through-overflow style code patters wheever a overflow ca occur. o 2 = Optimized New Features ad Migratio November

140 TargetLik Descriptio Explaatio Default UtilizeValueEqualitySigalLieSplit Replace block output variables of blocks precedig sigal lie splits by a variable with idetical value, e.g., the state variable of a subsequet Uit Delay block. If there is a sigal lie split after block B s output ad the block code for oe of the blocks with iputs drive by B s output leads to a plai value copy via a direct assigmet to a variable of the same data type, the this optio allows TargetLik to elimiate B s block output variable ad replace it by the variable o the left-had side of the assigmet. This situatio usually occurs if the output of B drives a TargetLik Outport block ad is also used iside the system or if the output of B drives a Uit Delay block i additio to subsequet calculatios. TargetLik optimizes the code patter per se, as it may be geerated i other costellatios as well. Example: Without this optimizatio, you ca fid Float64 Sa1_Switch; static Float64 X_Sa1_Uit_Delay1 = 0.; if (Sa1_IPort1 >= 0.) { Sa1_Switch = Sa1_IPort; } else { Sa1_Switch = (Sa1_IPort2 + X_Sa1_Uit_Delay1) * 0.5; } Sa1_OutPort1 = (Float64) si(sa1_switch); Sa1_OutPort = Sa1_Switch; X_Sa1_Uit_Delay1 = Sa1_Switch; o The optimizatio ca replace the switch output by the Uit Delay state or the output of Outport, i.e.: static Float64 X_Sa1_Uit_Delay1 = 0.; if (Sa1_IPort1 >= 0.) { X_Sa1_Uit_Delay1 = Sa1_IPort; } else { X_Sa1_Uit_Delay1 = (Sa1_IPort2 + X_Sa1_Uit_Delay1) * 0.5; } Sa1_OutPort1 = (Float64) si(x_sa1_uit_delay1); Sa1_OutPort = X_Sa1_Uit_Delay1; 140 New Features ad Migratio November 2012

141 TargetLik Descriptio Explaatio Default UtilizeValueEqualityStructFuctioArgumets If a fuctio has a parameter of poiter-to-struct type that is either a iput or a output parameter, e.g., specified via TargetLik Bus IPort or OutPort blocks, ad if the argumet that is passed is the address operator applied to a struct variable, the for (if the optio is activated) TargetLik is allowed to elimiate this struct variable if a complete copy from (or to) aother struct takes place before (or after) the fuctio call. Note that this is effectively a elimiatio of all struct compoets that have to be assiged beforehad, so TargetLik cosiders the o-struct-type struct compoets of the struct variable ad all the (recursively) cotaied substruct compoets, the leaf compoets, ad ca oly perform the optimizatio if these compoets are eligible for the elimiatio of itermediate variables. Specifically, this meas that the struct compoets have to have a default variable class or a user variable class with the ERASABLE Optimizatio property set. Examples: Without this optimizatio, you ca fid struct tag_t S1; struct tag_t S2;... S2.a = S1.a; S2.sub.b = S1.sub.b; S2.sub.c = S1.sub.c; S2.d = S1.d; /* Poiter-to-struct parameter oly used for iput */ r = f(&s2); or, if struct assigmets are requested via the AllowStructAssigmets Code Geerator optio, struct tag_t S1; struct tag_t S2;... S2 = S1; /* Poiter-to-struct parameter oly used for iput */ r = f(&s2); The optimizatio ca replace S2, i.e.: struct tag_t S1;... /* Poiter-to-struct parameter oly used for iput */ r = f(&s1); Coversely, the TargetLik optimizatio struct tag_t S3; struct tag_t S4;... /* Poiter-to-struct parameter oly used for output */ g(i1, i2, &S3); S4 = S3; ca replace S3 if it is certai that all leaf compoets are assiged a ew value i g(), i.e.: struct tag_t S4;... /* Poiter-to-struct parameter oly used for output */ g(i1, i2, &S4); TargetLik eeds to gather iformatio about the accesses to the struct compoets iside the respective fuctios. This also couts agaist the memory limit set by the SideEffectFreeAalysisThreshold optio. New Features ad Migratio November

142 TargetLik For referece iformatio o all Code Geerator optios, refer to Code Geerator Optios ( TargetLik Block ad Object Referece). Migratio aspects of Code Geerator optios Migratio aspects iclude Obsolete Code Geerator optios Chaged Code Geerator optios Recommeded compatibility optios for ew Code Geerator optios to esure the best possible dowward compatibility of the geerated productio code Refer to Migratio Aspects Regardig Code Geerator Optios o page 174 for more iformatio. New API Commads V-ECU geeratio New API commads allow you to itegrate TargetLik's virtual ECU (V- ECU) geeratio capability i your workflow: tl_geerate_vecu_implemetatio (To geerate V-ECU implemetatios that comprises all files ecessary for virtual ECU testig.) tl_compile_vecu (To compile V-ECU implemetatios.) tl_build_vecu (To geerate ad compile V-ECU implemetatios i oe step.) For further iformatio, refer to Geeratig Virtual ECUs for Virtual ECU Testig o page 135. API Commads ( TargetLik API Referece). New Hook Fuctios AUTOSAR Frame model geeratio/update TargetLik provides ew hook fuctios for the AUTOSAR use case. You ca use these hook fuctios to customize the frame model geeratio/update process. tl_pre_add_comspecblock_hook.m ( TargetLik File Referece) tl_post_add_comspecblock_hook.m ( TargetLik File Referece) 142 New Features ad Migratio November 2012

143 TargetLik For further iformatio, refer to Improved frame model geeratio o page 148 AUTOSAR-Specific Files ( TargetLik File Referece) Access Fuctio Chages Improvemets TargetLik's access fuctio mechaism was sigificatly improved. The followig improvemets were made: Specifyig access fuctios Optioally, TargetLik allows you to relate access fuctios to differet variable kids (scalar, vector, structure) by specifyig the VariableKidSpec property of DD AccessFuctio objects. This allows you to Specify variable access fuctios for struct variables Specify separate or commo access fuctios for differet variable kids withi oe access fuctio template ad thus also via oe DD VariableClass object Propagatio ito structures You ca ow cofigure TargetLik to propagate access fuctio templates (AFTs) ito structures by specifyig the PropagateStructToCompoets property of DD /Pool/Templates/AccessFuctios/<AccessFuctioName>/Settigs objects. This allows you to Specify a AFT applyig to the leaf struct compoets (scalar or vector compoets) at the root struct variable (PropagateStructToCompoets property set to o). Access the root struct variable itself by access fuctio (AF) (PropagateStructToCompoets property set to off). Cotrollig use of auxiliary variables Whe specifyig access fuctio templates, you ca ow cotrol whether TargetLik uses auxiliary variables to reduce the umber of access fuctio calls. The specificatio is made at the DD AccessFuctio objects's CreateLocalValueCopy property. For further iformatio, refer to Relatig Access Fuctios to Variable Kids ( TargetLik Advaced Practices Guide) New Features ad Migratio November

144 TargetLik Propagatio ito structures ( TargetLik Advaced Practices Guide). Cotrollig the Use of Auxiliary Variables with Access Fuctios ( TargetLik Advaced Practices Guide). Improvemet of Code Efficiecy Stroger code optimizatio by default The TargetLik default settigs of the Code Geerator optios that relate to code optimizatio have chaged slightly. Productio code geeratio leads to code that is eve more optimized ad readable, which is possible without burdeig memory cosumptio ad executio time i most cases. Assigmet of structs TargetLik allows the assigmet of structs as a whole: struct_b = struct_a; For details, refer to Optimizig Struct Variables ( Advaced Practices Guide). TargetLik Elimiatio of struct fuctio argumets If a fuctio has a parameter of poiter-to-struct type ad certai coditios are met, the TargetLik ca elimiate this struct variable if a complete copy from/to aother struct takes place before/after the fuctio call. For details, refer to Optimizig Struct Variables ( TargetLik Advaced Practices Guide). Optimizatio of block outputs followed by sigal lie splits TargetLik ca elimiate superfluous block output variables if a block output is followed by sigal lie splits. For details, refer to Elimiatig of Temporary Variables ( TargetLik Productio Code Geeratio Guide). Scope reductio of structures TargetLik ca ow reduce the scope of structures dow to local. Because this implies settig the lifetime of the structure to auto, this optimizatio greatly reduces RAM cosumptio. For further iformatio, refer to Scope of structured variables, i Obsolete Limitatios o page 177 Optimizig Variables via Property Values ( TargetLik Advaced Practices Guide) Scope Reductio of Variables ( TargetLik Advaced Practices Guide) 144 New Features ad Migratio November 2012

145 TargetLik Geeral Ehacemets ad Chages Reduced memory cosumptio for loggig Basically, the memory cosumptio for logged simulatio data has bee optimized for all simulatio modes (MIL, SIL ad PIL simulatio modes). If ecessary, you ca further reduce the memory cosumptio i MIL simulatio mode. For details, refer to Loggig speed ad memory cosumptio i MIL simulatio mode ( TargetLik Productio Code Geeratio Guide). Variable bit shifts i Stateflow You ca specify variable bit shifts i Stateflow. For example, the operatio x << shifts the value of x left by bits. Refer to Guidelies o Specifyig Stateflow models ( TargetLik Advaced Practices Guide). Sigal specificatio for the Costat block You ca specify scalig parameters (Type, LSB, Offset) eve though the default variable class is specified. Other blocks ca the iherit these specified properties from a precedig Costat block. For details o the relevat block settig, refer to Allow sigal specificatio ( TargetLik Block ad Object Referece). New Fixed-Poit Library header file The sumprot.h header file was added to the Fixed-Poit Library to avoid certai 64-bit calculatios whe suppressig compute-throughoverflow (CTO). For further iformatio, refer to Optioal Deactivatio of Compute-Through-Overflow o page 134 Macros ad Fuctios Provided by the Fixed-Poit Library ( TargetLik File Referece). Support of Simulik SLX model format TargetLik 3.4 supports the Simulik SLX model format. Obsolete limitatios With TargetLik 3.4, several limitatios have bee removed. For details refer to Obsolete Limitatios o page 177. New Features ad Migratio November

146 TargetLik New AUTOSAR-Related Features Features of the TargetLik AUTOSAR Module Supported AUTOSAR Releases AUTOSAR Release Revisio ) ) ) New i TargetLik 3.4 Specifyig AUTOSAR release i the TargetLik Data Dictioary TargetLik allows you to geerate AUTOSAR-compliat code for both AUTOSAR releases 3.x/4.x. You ca specify which AUTOSAR release to use i the DD /Pool/AUTOSAR/Cofig object the TargetLik Data Dictioary. For iformatio o geeratig AUTOSAR-compliat code, refer to Geeratig AUTOSAR-Compliat Code ( TargetLik AUTOSAR Modelig Guide). Workig with ew AUTOSAR 4.x data type cocept AUTOSAR 4.x itroduced the distictio betwee applicatio data types (ADTs) ad implemetatio data types (IDTs). TargetLik provides two wizards to assist you i the creatio of ADTs ad IDTs to provide a smooth trasitio to the AUTOSAR 4.x use case. 146 New Features ad Migratio November 2012

147 TargetLik You ca use the ApplicatioDataType Creatio Wizard to create ADTs for existig typedefs (IDTs) ad the ImplemetatioDataType Creatio Wizard to create IDTs for existig ADTs. For iformatio o workig with ADTs/IDTs, refer to Basics o Workig with Implemetatio ad Applicatio Data Types ( TargetLik AUTOSAR Modelig Guide). Icremetal code geeratio for AUTOSAR SWCs Feature: CGU Cotais Type A: Fuctioal part of ruable Type B: Complete ruable Type C: SWC cotaiig at least oe ruable Type D: Several ruables TargetLik provides several modelig features for compoet-based developmet. You ca ow also use these features for AUTOSAR models. TargetLik allows you to place your AUTOSAR software compoets ad ruables i separate code geeratio uits (CGUs), i.e., refereced models or subsystems cofigured for icremetal code geeratio. Possible use cases: TargetLik 3.4 supports the followig cases: Purpose: To separate a fuctioal part of a ruable i oe CGU. Must ot cotai AUTOSAR blocks. Modelig of calibratable parameters ad per istace memories is possible. To separate a complete ruable i oe CGU. Ca cotai AUTOSAR blocks. To separate a complete SWC i oe CGU. Ruables have to be modeled i Simulik subsystems or TargetLik CGUs. To separate several ruables i oe CGU. The ruables ca belog to differet SWCs. The CGU does ot eed to cotai all the ruables of oe SWC. Ruables have to be modeled i Simulik subsystems or TargetLik CGUs. CGU Nestig: Ca Cotai CGUs of Type A Type A Type A Type A New Features ad Migratio November

148 TargetLik Example The followig screeshot shows a ruable cotaiig a refereced model of type B. Note that the refereced model cotais AUTOSAR blocks. The Ruable block holds the parameters of the refereced model. For further iformatio, refer to Compoet-Based Developmet Usig Abstract Iterfaces o page 133 Usig Compoet-Based Developmet ( TargetLik AUTOSAR Modelig Guide). Mappig Models to Productio Code ( TargetLik Advaced Practices Guide). Improved frame model geeratio TargetLik's frame model geeratio feature allows you to geerate TargetLik models with AUTOSAR blocks for Ruables ad their iterfaces from AUTOSAR files or AUTOSAR data cotaied i the Data Dictioary. This feature has bee further improved: Update capability TargetLik's frame model geeratio ow has a update capability that facilitates your roud trips betwee TargetLik ad software architecture tools such as SystemDesk. You ca ow update existig frame models accordig to AUTOSAR files imported to the Data Dictioary. This eables you to quickly adapt your model to chages i the AUTOSAR files whe implemetig the software compoet i TargetLik. TargetLik allows you to geerate or update frame models for selected software compoets or groups of software compoets. 148 New Features ad Migratio November 2012

149 TargetLik Update report Whe updatig a existig model, TargetLik geerates a HTML update report that gives you quick access to chaged model parts via hyperliks: TargetLik's SwcModel Update Report iforms you about updated blocks ad whether user actio is required. Further improvemets TargetLik's frame model geerator ow supports Applicatio errors Commuicatio specificatios Mode access poits For further iformatio, refer to New Hook Fuctios o page 142 (Customizig the frame model geeratio/update process via hook fuctios.) Geeratig/Updatig a Frame Model from AUTOSAR Data ( TargetLik AUTOSAR Modelig Guide). Delivery of software compoets as object code TargetLik ow allows you to deliver software compoets as object code. This meas you ca better protect your itellectual property ad to deliver tested compoets. You ca specify the delivery format at the DeliveryFormat property of DD SoftwareCompoet objects. Compatibility mode By default, the software compoets delivered as object code are compliat to AUTOSAR compatibility mode, which results i fuctios with stadardized ames ad data structures. You ca use a RTE geerator from ay vedor (provided that the RTE geerator supports the compatibility mode). This provides better iteroperability with software architecture tools. New Features ad Migratio November

150 TargetLik For further iformatio, refer to Exchagig Software Compoet Code ( TargetLik AUTOSAR Modelig Guide). Basics o Geerated Code ( TargetLik AUTOSAR Modelig Guide). Improved hadlig of SIL/PIL simulatios The hadlig of SIL/PIL simulatios for operatio call subsystems has bee improved. TargetLik ow geerates simulatio code if the Use this subsystem for SIL/PIL simulatio checkbox is deactivated for all operatio call subsystems cotaied i the model. If the same operatio call subsystem is istatiated multiple times, TargetLik chooses oe istace. Improved Cotaier Maager The Cotaier Maager has bee improved. For details, refer to New Features of the Cotaier Maager 3.2 o page 55. New TargetLik Data Dictioary Features Objective The TargetLik Data Dictioary 3.4 (DD) has the followig ew features, ehacemets ad chages: Where to go from here Iformatio i this sectio Compare ad Merge Features 151 Improvemets for Data Dictioary File Hadlig 152 Further Improvemets of the Data Dictioary 155 Maager New DD MATLAB API Commads New Features ad Migratio November 2012

151 TargetLik Compare ad Merge Features Comparig ad mergig DD objects i the DD Compariso pae of the DD Maager If you eed to compare ad merge DD objects, the DD Maager automatically opes a Compariso pae whe you select two DD objects for compariso. It cotais a sychroized tree structure of the compared DD objects icludig their child objects. You ca compare ad merge selected DD objects i oe DD workspace, DD objects i differet DD workspaces, or whole DD workspaces. The differeces i the compared DD objects are idicated by color codes. This makes it easier for you to maage eve the most complex DD object trees. Beefits You ca compare Data Dictioary workspaces ad objects efficietly (iter- ad itra-workspace comparisos). For more iformatio, refer to How to Compare DD Objects i the DD Compariso Pae ( TargetLik Data Dictioary Basic Cocepts Guide). New Features ad Migratio November

152 TargetLik You ca merge Data Dictioary subtrees, objects ad properties efficietly usig the sychroized tree view. For more iformatio, refer to How to Merge DD Objects ad Property Values i the DD Compariso Pae ( TargetLik Data Dictioary Basic Cocepts Guide). You ca customize the compariso, for example, by igorig specific object properties. Refer to How to Customize the Compariso of DD Objects ( TargetLik Data Dictioary Basic Cocepts Guide). You ca geerate a report o the compariso result (XML or HTML). I a compariso pae, right-click aywhere to geerate a report for the curret compariso. As a alterative, you ca start a compariso i a DOS commad prompt: Use the DsddComp.exe commad. For more iformatio, refer to How to Geerate a Compariso Report (HTML/XML) i the DD Compariso Pae ( TargetLik Data Dictioary Basic Cocepts Guide). Improvemets for Data Dictioary File Hadlig Simplified loadig of partial Data Dictioary files by storig their origial locatios The Ope commad ca read metadata that is stored together with a partial DD file so that its cotet ca easily be reloaded to its origial locatio. You ca also multiselect DD files ad ope them with this commad. If you ope a DD file by usig the Ope commad i the File meu of your TargetLik Data Dictioary Maager, the loadig behavior is as follows: If the file is a complete Data Dictioary, the active DD workspace is filled with the cotet of the DD file. If the file is a partial Data Dictioary with metadata about its origial positio, the Data Dictioary Maager automatically reads the origial subtree ad loads the file cotets to that positio. If the file is a partial Data Dictioary without metadata about its origial positio, the Data Dictioary Maager loads the cotet to a valid positio accordig to the data model. If this is ot possible, it is copied to a /tmp subtree. You ca the move the objects to valid positios maually. Partial DD files saved with TargetLik versios earlier tha TL 3.3 cotai o metadata. 152 New Features ad Migratio November 2012

153 TargetLik Simplified iclusio of partial DD files with the Poit of Iclusio dialog The ew Poit of Iclusio dialog makes it easier to hadle partial DD files, which ca be icluded at specific positios i the DD subtree. You ca ow create iclusio poits for partial DD files directly by selectig a object tree ad usig the Poit of Iclusio dialog. Beefits of the ew Poit of Iclusio dialog: Allows you to work with simplified file specificatio by usig relative paths ad paths relative to the mai DD. Provides you iformatio o the file cotet, for example, its positio i the DD subtree. For more iformatio o how to iclude partial DD files, refer to How to Iclude Partial Data Dictioary Files ( TargetLik Data Dictioary Basic Cocepts Guide). New Features ad Migratio November

154 TargetLik Simplified partitio of a DD project file by separatig partial DD files with the Poit of Iclusio dialog If you ope a DD project file i your TargetLik Data Dictioary Maager, you ca separate specific subtrees ad save them as icluded partial DD files. For more iformatio o how to separate subtrees ad save them as icluded partial DD files, refer to How to Separate DD Subtrees ad Save them as Icluded Partial DD Files ( TargetLik Data Dictioary Basic Cocepts Guide). 154 New Features ad Migratio November 2012

155 TargetLik Further Improvemets of the Data Dictioary Maager Object Explorer Addig properties (colums) from the Property Value List to the Object Explorer has bee improved. I additio to the existig methods for addig properties to the Object Explorer, the TargetLik Data Dictioary Maager ow offers a easier way: You ca add them by selectig a DD object i the Object Explorer ad the selectig the ew checkboxes i the Property Value List. For more iformatio o addig properties to the Object Explorer, refer to How to Specify Properties (Colums) Show i the Object Explorer ( TargetLik Data Dictioary Basic Cocepts Guide) Property Value List Properties that caot be set are ow greyed out i the Property Value List. A tooltip iforms you why the property caot be set. Loadig DD files You ca ow load the same DD file ito differet workspaces. DD IcludeFileGroup objects You ca ow group DD DDIcludeFile objects i DD DDIcludeFileGroup objects. Nestig is possible. New DD MATLAB API Commads The followig ew DD MATLAB API commads are available: 'Compare' 'CreateComparisoReport' 'Duplicate' 'FidPrevious' 'GetCodeFiles' New Features ad Migratio November

156 TargetLik 'GetDDFiles' 'GetFileAttributes' 'GetPathToSLObject' 'IsFileRoot' 'Compare' dsdd('compare',<objectidetifier1>,<objectidetifier2>[,attributename1,attribute Value1,...]) To compare two objects ad to build a compariso tree. 'CreateComparisoReport' dsdd('createcomparisoreport',<objectidetifier>[,attributename1,attributevalue1,...]); To create a XML file that cotais the results of a object compariso. The specified object must be a compariso tree root object. If the specified XML file exists, it is overwritte. 'Duplicate' dsdd('duplicate',<objectidetifier>) To duplicate a DD object. The result must comply with the Data Model. 'FidPrevious' dsdd('fidprevious',<objectidetifier>[,attributename1,attributevalue1,...]) Looks for a object which matches specified criteria. This commad is like the 'FidNext' commad except that the DD tree is traversed i reverse order. Use this commad to look for objects iteratively i a loop. 'GetCodeFiles' dsdd('getcodefiles',<objectidetifier>) To retur ames of geerated files that are associated with a object that resides i the /Subsystems area after code geeratio. 'GetDDFiles' dsdd('getddfiles'[,<dd_idetifier>]); To retur iformatio about partial DD files that have bee loaded ito a workspace. These are files that have bee loaded either by file iclusio or explicitly, for example, with the Load or the AutoLoad commad. 'GetFileAttributes' dsdd('getfileattributes',<filename>) To retrieve attributes of a DD file. dsdd('getpathtoslobject' [...]) dsdd('getpathtoslobject',<objectidetifier>[,attributename1,attributevalue1,...] ) 156 New Features ad Migratio November 2012

157 TargetLik To get the path to the Simulik system or SF object associated with a DD object that resides i the /Subsystems area after code geeratio. dsdd('isfileroot' [...]) dsdd('isfileroot',<objectidetifier>) To check if a DD object is a file root object. Note that DD root objects are always file roots. Related topics Basics dsddma ( TargetLik Data Dictioary MATLAB API Referece) New Features ad Migratio November

158 TargetLik Migratig to TargetLik 3.4 ad TargetLik Data Dictioary 3.4 Upgrade process To migrate from TargetLik 3.3 to TargetLik 3.4, oly the TargetLik Data Dictioary eeds to be upgraded. This is doe by the DD update process which automatically starts whe a DD file is opeed. To migrate libraries/models from older TargetLik Releases, you also have to perform the migratio steps of the iterveig TargetLik Releases. Refer to the previous TargetLik Migratio Guides available o your DVD. You ca lauch a upgrade maually by usig the tl_upgrade API commad. 158 New Features ad Migratio November 2012

159 TargetLik For last-miute iformatio o TargetLik 3.4 ad o potetial difficulties, you are recommeded to visit the TargetLik 3.4 website at Update. Whe upgradig models ad libraries, first upgrade models or libraries that themselves do ot referece ay other libraries, i.e., the blocks/subsystems they cotai have o liks to other libraries. Start with the bottom library ad the upgrade the libraries above it i ascedig order. You must ot ope the model or a referecig library util this is doe. For related iformatio o upgradig libraries, refer to: o How to Upgrade Libraries ad Models from TargetLik 2.x to 3.x o page 167 o How to Prepare TargetLik User Libraries for Upgrade ( TargetLik Productio Code Geeratio Guide) o tl_upgrade ( TargetLik API Referece) Projects that were created uder TargetLik 1.3 or eve earlier versios caot be upgraded directly to TargetLik 3.4 ad TargetLik Data Dictioary 3.4. You must first perform a upgrade to a TargetLik 2.x versio before you ca upgrade to TargetLik 3.4 ad TargetLik Data Dictioary 3.4. Previous New Features ad Migratio documets are available via Iteret ad o the dspace DVD. You ca dowload them from or read them from the dspace DVD (see the \Doc\Prit\PreviousReleases folder). The PDF files are called TLNewFeaturesAdMigratioVer.x.y.pdf, where x.y stads for the release umber. For iformatio o upgradig Data Dictioary files cotaiig AUTOSAR objects, refer to AUTOSAR- Related Migratio Aspects o page 176. Where to go from here Iformatio i this sectio Discotiued Data Dictioary Features 160 Migratig to TargetLik Data Dictioary New Features ad Migratio November

160 TargetLik How to Upgrade a Data Dictioary Without Iclude 164 Files How to Upgrade a Data Dictioary With Iclude 165 Files How to Upgrade Libraries ad Models from 167 TargetLik 2.x to 3.x Code Chages 168 Describes alteratios i productio code due chages made. Migratio Aspects Regardig Code Geerator 174 Optios Chages i TargetLik ad TargetLik Data 175 Dictioary API Fuctios Various Migratio Aspects 176 AUTOSAR-Related Migratio Aspects 176 Obsolete Limitatios 177 Discotiued Data Dictioary Features dsdd_upgrade The dsdd_upgrade commad is o loger available. To upgrade a DD project file, use the dsdd('upgrade'[,<dd_idetifier>]) commad (refer to Upgrade ( TargetLik Data Dictioary MATLAB API Referece)), or the DD Maager. Migratig to TargetLik Data Dictioary 3.4 Discotiued documetatio The dspace Data Dictioary Data Model Referece is o loger available. Refer to the TargetLik Data Dictioary MATLAB API Referece istead, or refer to the user assistace i the TargetLik Data Dictioary Maager. Upgradig Data Dictioary files To migrate from TargetLik 3.3 to TargetLik 3.4, oly the TargetLik Data Dictioary files eed to be upgraded. This is doe by the DD update process which automatically starts whe a DD file is opeed. Upgradig TargetLik models ad libraries is ot ecessary. 160 New Features ad Migratio November 2012

161 TargetLik Deletio of Subsystem ad <Applicatio> areas Due to the chages i the data model, the data i the Subsystem ad <Applicatio> areas, which resulted from code geeratio ad build processes performed before the upgrade, is ot cosistet with ew data models. Upgradig a DD project file therefore deletes the Subsystem ad <Applicatio> areas from the Data Dictioary. You are asked to cofirm the deletio. I batch mode, the subsystem ode is deleted without query, i.e., oly a message is issued. To create correct data i the Subsystem ad <Applicatio> areas after the upgrade, for example, data eeded for geeratig ASAP2 files or AUTOSAR XML files, geerate code for all the code geeratio uits agai. Method to upgrade Data Dictioary files TargetLik Data Dictioary 3.4 provides a upgrade process that automatically upgrades DD files (DD0 workspace) to versio 3.4. The upgrade process ca be called i three ways: Automatically opeig a old TargetLik model Whe you ope a TargetLik model with a old (ot upgraded) DD project file, TargetLik first rus the TargetLik Data Dictioary s upgrade process. New Features ad Migratio November

162 TargetLik Via the Tools meu i the Data Dictioary Maager Maually via Tools - Upgrade curret DD i the DD Maager. The meu commad is available oly if the DD project file eeds upgradig. Otherwise it is disabled (grayed out). Data Dictioary API commad To call the upgrade process via the Data Dictioary s API, type dsdd('upgrade') i the MATLAB Commad Widow. If the upgrade was successful, this is idicated i the MATLAB Commad Widow as show below: >> dsdd('upgrade') as = 0 The asterisk i the title bar of the Data Dictioary Maager idicates that the cotet of the Data Dictioary has chaged. Precoditios for upgradig Data Dictioary files To esure the DD file is upgraded correctly, the followig precoditios must be met: There must be write permissio for the DD file ad the file must ot be write-protected. If Data Dictioary Iclude files are used, there must be write access to all of them. 162 New Features ad Migratio November 2012

163 TargetLik If Data Dictioary Iclude files are used, they must be saved after updatig as well as the mai DD file. This esures that the Data Dictioary partitios ito several files. To save the Iclude files correctly, you must first make the appropriate settigs for them, for example, i the Poit of Iclusio dialog. New Features ad Migratio November

164 TargetLik How to Upgrade a Data Dictioary Without Iclude Files Objective If you ope a TargetLik model with a old, oupgraded DD project file, you have to upgrade the Data Dictioary file. Method To upgrade a Data Dictioary without Iclude files 1 Ope the model ad the refereced TargetLik Data Dictioary, or type dsdd('ope',<ddfile>) i the MATLAB Commad Widow. The Data Dictioary eeds upgradig dialog automatically opes if a older DD versio is ivolved. 2 Click Yes if o Iclude files are used i the Data Dictioary. If Iclude files are used, abort the upgrade process ad refer to How to Upgrade a Data Dictioary With Iclude Files o page 165. The Delete geerated objects dialog automatically opes if the Data Dictioary's Subsystem area cotais objects geerated with a previous TargetLik versio. 3 Click Yes. 4 Save the Data Dictioary. Savig the Data Dictioary (with write permissio to the relevat DD file) completes the upgrade of the DD file. Result The ext time you ope the DD file, the upgrade dialog will ot ope because the DD file is up-to-date. 164 New Features ad Migratio November 2012

165 TargetLik How to Upgrade a Data Dictioary With Iclude Files Objective If you ope a TargetLik model with a old, oupgraded Data Dictioary file, you have to upgrade the Data Dictioary file. Method To upgrade a Data Dictioary with Iclude files 1 Ope the model ad the refereced TargetLik Data Dictioary, or type dsdd('ope',<ddfile>) i the MATLAB Commad Widow. The Data Dictioary eeds upgradig dialog automatically opes if a earlier DD versio is ivolved. 2 Select No i the upgrade dialog. 3 Uder /Cofig/DDIcludeFiles, set the AutoLoad ad AutoSave properties for each Iclude file as show below. New Features ad Migratio November

166 TargetLik This esures that after the Data Dictioary ad the Iclude files have bee upgraded, the upgraded Iclude files are saved whe the Data Dictioary is saved. You ca set these properties for a large umber of Iclude files via the Object Explorer. You ca also use the Poit of Iclusio dialog to set the iclude file properties. 4 Start the DD upgrade (icludig the icluded files) via Tools - Upgrade curret DD i the DD Maager, or eter dsdd('upgrade') i the MATLAB Commad Widow. 5 Save the Data Dictioary (with write permissio to the relevat DD file). This completes the upgrade of the DD file itself as well as the icluded partial DD files. Result The ext time you ope the DD file, the upgrade dialog will ot ope because the DD file is up-to-date ad so are the icluded partial DD files. After the files have bee properly upgraded, you might wat to restore the old settigs for the Data Dictioary Iclude files. 166 New Features ad Migratio November 2012

167 TargetLik How to Upgrade Libraries ad Models from TargetLik 2.x to 3.x Objective Libraries ad models are upgraded i a fixed sequece of steps. Whe upgradig models ad libraries, first upgrade models or libraries that themselves do ot referece ay other libraries, i.e., the blocks/subsystems they cotai have o liks to other libraries. Start with the bottom library ad the upgrade the libraries above it i ascedig order. You must ot ope the model or a referecig library util this is doe. Method To upgrade libraries ad models from TargetLik 2.x to 3.x 1 I the MATLAB Commad Widow, type dsdd_maage_project('ope','<ame>.dd') to load the required ad already upgraded DD project file. (Oe way to upgrade DD project files is to use the dsdd('upgrade'[,<dd_idetifier>]) commad, refer to Upgrade ( TargetLik Data Dictioary MATLAB API Referece)). 2 Type tl_upgrade('model', '<Library>.mdl', 'UpgradeLibs', 'off', 'Force', 'o', <other properties as eeded>) to upgrade sigle libraries. If you set the Force optio to o, the model <ame> is treated as a TargetLik 2.x model. To upgrade a library that was built with TargetLik 2.x, this optio must be set to o. Settig UpgradeLibs to off does ot upgrade other libraries refereced by the updated library. 3 Save the upgraded library file(s), for example, Library.mdl. 4 Repeat steps 2 ad 3 for all other libraries. 5 Ru tl_upgrade() for the model(s) or ope the model(s). If you ope the model(s), the upgrade is started automatically. Result You have upgraded your libraries ad fially your model. Related topics Refereces tl_upgrade ( TargetLik API Referece) New Features ad Migratio November

168 TargetLik Code Chages Compute-throughoverflow The followig tables list code chages that are due to the TargetLik ExploitComputeThroughOverflow Code Geerator optio settig. The productio code patter preseted i the TargetLik 3.4 colum differ with respect to the Code Geerator settig's value. Aotatios are italicized. The represetatio of a costat value i a operatio usig compute-through-overflow ca be differet from its represetatio i a operatio without the istrumetatio of overflows. Sum with operads sharig the output's scalig ad data type The followig table shows the code chages for a Sum block takig as iput two It16s that have the same scalig ad data type as the output. TargetLik 3.4 TargetLik 3.3 ExploitComputeThroughOverflow = Optimized Sa1_SimpleI16Sum = (It16) (Sa1_I16I1 + Sa1_I16I2); No CTO casts are made, because aalysis of cotext shows that o overflow ca occur. ExploitComputeThroughOverflow = Never Sa1_SimpleI16Sum = (It16) (Sa1_I16I1 + Sa1_I16I2); No CTO casts are made, because CTO is forbidde by Code Geerator optio. ExploitComputeThroughOverflow = Always Sa1_SimpleI16Sum = (It16) (((UIt16) Sa1_I16I1) + ((UIt16) Sa1_I16I2)); Same code patter as i TargetLik 3.3. Sa1_SimpleI16Sum = (It16) (((UIt16) Sa1_I16I1) + ((UIt16) Sa1_I16I2)); The CTO casts (UIt16) are made to guaratee defied overflow behavior. 168 New Features ad Migratio November 2012

169 TargetLik Sum with oe operad differetly scaled as output, implyig a right shift The followig table shows the code chages for a Sum block takig two It16s as iput. The scalig of I16I3 differs from the output's scalig, which implies a right shift operatio: TargetLik 3.4 TargetLik 3.3 ExploitComputeThroughOverflow = Optimized Sa1_RShiftI16Sum = (It16) (((It16) (Sa1_I16I3 >> 1)) + Sa1_I16I4); No CTO casts are made, because aalysis of cotext shows that o overflow ca occur. The secod It16 cast is the result cast of the right shift operatio. ExploitComputeThroughOverflow = Never Sa1_RShiftI16Sum = (It16) (((It16) (Sa1_I16I3 >> 1)) + Sa1_I16I4); No CTO casts are made, CTO is forbidde by Code Geerator optio. The secod It16 cast is the result cast of the right shift operatio. ExploitComputeThroughOverflow = Always Sa1_RShiftI16Sum = (It16) (((UIt16) (It16) (Sa1_I16I3 >> 1)) + ((UIt16) Sa1_I16I4)); Same code patter as i TargetLik 3.3. Sa1_RShiftI16Sum = (It16) (((UIt16) (It16) (Sa1_I16I3 >> 1)) + ((UIt16) Sa1_I16I4)); The CTO casts (UIt16) are made to guaratee defied overflow behavior. The secodit16 cast is the result cast of the right shift operatio. Sum with oe operad differetly scaled as output, implyig a left shift New Features ad Migratio November

170 TargetLik The followig table shows the code chages for a Sum block takig two It16s as iput. The scalig of I16I5 differs from the output's scalig, which implies a left shift operatio: TargetLik 3.4 TargetLik 3.3 ExploitComputeThroughOverflow = Optimized Sa1_LShiftI16Sum = (It16) (((UIt16) (Sa1_I16I5 << 1)) + ((UIt16) Sa1_I16I6)); CTO casts are made, because aalysis of cotext shows that the first iput does ot fit i a 16-bit iteger data type. The It16 cast is omitted because suboperatios of additios ad substractios are give a usiged type, if a overflow could occur (refer to Usiged suboperatios for additio/substractio o page 172). ExploitComputeThroughOverflow = Never Sa1_LShiftI16Sum = (It16) (((It32) (((It32) Sa1_I16I5) << 1)) + ((It32) Sa1_I16I6)); Because CTO is forbidde, calculatios are performed i It32 to avoid overflows. ExploitComputeThroughOverflow = Always Sa1_LShiftI16Sum = (It16) (((UIt16) (Sa1_I16I5 << 1)) + ((UIt16) Sa1_I16I6)); Same code patter as i TargetLik 3.3. Sa1_LShiftI16Sum = (It16) (((UIt16) (It16) (Sa1_I16I5 << 1)) + ((UIt16) Sa1_I16I6)); The CTO casts (UIt16) are made to guaratee defied overflow behavior. The secod It16 cast is the result cast of the left shift operatio. Sum with three iputs without assig arithmetic for accumulatios 170 New Features ad Migratio November 2012

171 TargetLik The followig table shows the code chages for a Sum block takig three It16s as iput sharig the same scalig as the output. Note that the DoNotUseAssigArithmeticForAccumulatio Code Geerator optio has bee eabled to suppress assig arithmetic for accumulatios: TargetLik 3.4 TargetLik 3.3 ExploitComputeThroughOverflow = Optimized Sa1_SimpleI16SumTwice = (It16) (((UIt16) (((UIt16) Sa1_I16I7) + ((UIt16) Sa1_I16I8))) + ((UIt16) Sa1_I16I9)); CTO casts are made, because aalysis of cotext shows that the result of the first additio does ot fit i a 16-bit iteger data type. The secodit16 cast is omitted because suboperatios of additios ad substractios are give a usiged type if a overflow could occur (refer to Usiged suboperatios for additio/substractio o page 172). ExploitComputeThroughOverflow = Never Sa1_SimpleI16SumTwice = (It16) (((It32) (((It32) Sa1_I16I7) + ((It32) Sa1_I16I8))) + ((It32) Sa1_I16I9)); Because CTO is forbidde, calculatios are performed i It32 to avoid overflows. ExploitComputeThroughOverflow = Always Sa1_SimpleI16SumTwice = (It16) (((UIt16) (((UIt16) Sa1_I16I7) + ((UIt16) Sa1_I16I8))) + ((UIt16) Sa1_I16I9)); Same code patter as i TargetLik 3.3. Sa1_SimpleI16SumTwice = (It16) (((UIt16) (It16) (((UIt16) Sa1_I16I7) + ((UIt16) Sa1_I16I8))) + ((UIt16) Sa1_I16I9)); The CTO casts (UIt16) are made to guaratee defied overflow behavior. Modified code patter for additio/substractio If a additio or substractio meets the followig coditios, the resultig code guaratees a defied overflow behavior. The result would allow a smaller data type tha the data type specified. A operad does ot fit this smaller data type. Code example Suppose a additio is defied as follows: I32Out = I32I1 + I32I2 The first operad also had the user-defied limits Max = ad Mi = 60000, ad the secod had Max = ad Mi = Thus, the result would always fit It16. However, both operads do ot fit It16 (overflow). I cosequece, the operads are cast to UIt16 so that the overflow is defied. The code would be geerated as follows: TargetLik 3.4 TargetLik 3.3 I32Out = (It32) (It16) (((UIt16) I32I1) + ((UIt16) I32I2)); I32Out = (It32) (It16) (((It16) I32I1) + ((It16) I32I2)); New Features ad Migratio November

172 TargetLik Usiged suboperatios for additio/substractio Operatios that are operads themselves i additio/substractio are assiged a usiged data type, if they could overflow ad if they apply Compute-Through-Overflow (refer to Sum with oe operad differetly scaled as output, implyig a left shift o page 169). Code example Suppose a additio is defied as follows: I16Out = I16I1 + I16I2 with LSB of I16Out, I16I2 = 2^-1, ad LSB of I16I1 = 2^0 The code would be geerated as follows: TargetLik 3.4 TargetLik 3.3 I16Out = (It16)((UIt16)(I16I1 << 1) + (UIt16) I16I2) I16Out = (It16)((UIt16)((It16)(I16I1 << 1)) + (UIt16) I16I2) Deletio of uused fuctio parameters The followig applies to fuctio parameters that are specified for chart fuctios ad graphical fuctios ad are propagated to all the subfuctios (Stateflow state ad auxiliary fuctios): Fuctio parameters of these subfuctios that are ot used are deleted although the Optimizatio property of their variable class i the TargetLik Data Dictioary is ot set to ERASABLE. Casts i Stateflow shift operatios Shift operatios i Stateflow make use of additioal casts, if the operad meets the followig coditios: Operad uses a TargetLik data type differet from the Stateflow data type. Operad is ot scaled. Casts of poiters (fuctio calls) With this versio of TargetLik the cast behavior of poiters has chaged as follows: If a fuctio parameter has a type prefix that is iterpreted as a address qualifier (e.g., _far), the type prefix is evaluated to check whether casts are ecessary. I older TargetLik versios, a cast was applied for ay type prefix. If a fuctio parameter is a vector ad the required ad the actual type qualifiers differ, the actual type qualifier is cast to the required type qualifier. I older TargetLik versios, o such cast was applied. 172 New Features ad Migratio November 2012

173 TargetLik Type guard idetifiers (MISRA) Type guard idetifiers are ow output without leadig or trailig uderscores, which is i accordace with MISRA. For example: TargetLik 3.4 TargetLik 3.3 #ifdef MyType_TYPE #defie MyType_TYPE typedef MyType; #edif /* MyType_TYPE */ #ifdef _MyType_TYPE_ #defie _MyType_TYPE_ typedef MyType; #edif /* _MyType_TYPE_ */ Macro iitializatio (MISRA) If a macro has a egative iitializatio value, the value is wrapped i paretheses. This is i accordace with MISRA. For example: TargetLik 3.4 TargetLik 3.3 #defie MACRO ((It8) -1) #defie SECOND_MACRO (-10) #defie MACRO (It8) -1 #defie SECOND_MACRO -10 && ad operatios (MISRA) For fuctio calls, access to vector compoets via [ ] operator, ad access to the elemets of structs, the followig ew rule applies, which is i accordace with MISRA: The argumets of && ad operatios are wrapped i paretheses, for example: TargetLik 3.4 TargetLik 3.3 (A()) && b c (D[1]) (Struct.e) f A() && b c D[1] Struct.e f Relay block For the TargetLik Relay block, the Switch O coditio is ow checked first to mimic the Simulik behavior i case the SwitchO ad SwitchOff values are equal. Uit Delay block If the block output has saturatio eabled, a block output variable is always geerated. Additioally, the assigmet output = state is saturated. I additio, the block output variable is always read by the succeedig block, if it meets oe of the followig coditios: Block output variable is logged. Block output variable is refereced from the TargetLik Data Dictioary. Block output variable has a user-defied variable class. Block output variable has saturatio eabled. New Features ad Migratio November

174 TargetLik Migratio Aspects Regardig Code Geerator Optios Basics o default chages The settigs of the Code Geerator optios are stored with the model (model-based optio storage). I additio, you ca store user-defied sets of Code Geerator optios i OptioSets i the TargetLik Data Dictioary sice TargetLik versio 3.1 (DD-based optio storage). You ca use DD-based optio settigs as a cetral source for overwritig model-based optio settigs. If a model-based optio value equals the default value of a older TargetLik versio, it is chaged to the ew default value durig upgrade. If a DD-based optio value equaled the old default value, it is ot chaged to the ew default value durig upgrade but keeps the old value. For details o both storage kids, refer to Basics of Cofigurig the Code Geerator for Productio Code Geeratio ( TargetLik Advaced Practices Guide). Chaged default values of Code Geerator optios The default values of the Code Geerator optios listed below were chaged: Code Geerator Optio Default Value TargetLik 3.4 AllowIterleavigCodeForAllSubsystems o off ExploitRagesIdepetOfErasable off o GlobalOptimizatioIteratioThreshold OptimizatioIteratioThreshold SideEffectFreeAalysisThreshold TargetLik New Features ad Migratio November 2012

175 TargetLik Recommeded compatibility settigs for ew Code Geerator optios For the best dowward compatibility to earlier TargetLik versios ( TargetLik 3.3), it is recommeded to use the Compatibility Settig values for the ew Code Geerator optios listed i the followig table: Code Geerator Optio Compatibility Settig Default Value AllowStructAssigmets off o AssumeOperatioCallsHaveNoUkowDataFlow off o UtilizeValueEqualitySigalLieSplit off o UtilizeValueEqualityStructFuctioArgumets off o ExploitComputeThroughOverflow 3 = Always 2 = Optimized New Code Geerator optios For more iformatio o ew Code Geerator optios, refer to Code Geerator Optios o page 138. Related topics Refereces Code Geerator Optios ( TargetLik Block ad Object Referece) Chages i TargetLik ad TargetLik Data Dictioary API Fuctios Obsolete DD MATLAB API commads The followig DD MATLAB API commad is o loger supported: dsdd_upgrade To upgrade a DD project file, use the dsdd('upgrade'[,<dd_idetifier>]) commad (refer to Upgrade ( TargetLik Data Dictioary MATLAB API Referece)), or the DD Maager. New Features ad Migratio November

176 TargetLik Various Migratio Aspects Style defiitio file ccofig.xml For the %DSPACE_ROOT%\Matlab\Tl\cofig\codege\ccofig.xml style defiitio file, the <TL:geeratio-date...> elemet was reamed. The elemet ow reads as follows: <TL:geeratio-date-commet...>. If you use your ow style defiitio file, you must adapt it. The style defiitio file is refereced i the TargetLik Mai Dialog block o the Advaced page. AUTOSAR-Related Migratio Aspects Validatio of AUTOSAR data The validatio of AUTOSAR data was sigificatly improved. I particular, badly/isufficietly specified ComSpecs are ow detected. This improves data exchage with system architecture tools such as SystemDesk ad third- party RTE geerators. AUTOSAR File Import/Export The followig two properties are obsolete: Merge EablePackageSupport The value of both properties is ow always set to o. Adapt existig scripts accordigly. RTE frame module The default ame of RTE frame modules has chaged from Rte_$N to Rte. It is o loger possible to geerate additioal variables or fuctios ito the RTE frame module. Cotact dspace Support cocerig the migratio of TargetLik models cotaiig workarouds for RTE API fuctios usupported i earlier TargetLik versios. 176 New Features ad Migratio November 2012

177 TargetLik Obsolete Limitatios With TargetLik 3.4, a couple of limitatios existig i previous TargetLik versios have bee removed. They are listed below. Compoet-Based Developmet Limitatios AUTOSAR AUTOSAR blocks are ot supported i refereced models or subsystems cofigured for icremetal code geeratio. 1) 1) AUTOSAR blocks still are ot allowed i model-based code geeratio uits cotaiig fuctioal sub-parts of ruables. Code geeratio limitatio Struct data types caot be accessed by access fuctios Access fuctios are ot supported for structures as such. Oly access to the compoets of a structure which are ot themselves of struct type is supported. Scope of structured variables TargetLik reduces the scope of structures oly to static local at most but ot to local, eve if this is techically possible. If the structure has the local scope to start with, it keeps the local scope. Access fuctio kid ADDRESS Implemetig the ADDRESS access fuctio kid i the form of macros would require differet implemetatios for scalar ad vector variables. Curretly, oly oe implemetatio ca be specified, ad it is therefore ecessary to use separate variable classes for scalar ad vector variables that referece differet AccessFuctio templates. Stateflow limitatios Shift by variable TargetLik does ot support shift operatios with a shift value that is a variable. For example: o a >> 5; // ok o a >> ShiftValue; // ot supported New Features ad Migratio November

178 TargetLik AUTOSAR limitatios RTE API calls i refereced models TargetLik does ot support the use of AUTOSAR commuicatio i refereced models. If AUTOSAR data or parameters shall be used i refereced models, the data ad parameters have to be 178 New Features ad Migratio November 2012

179 VEOS New Features of VEOS 3.0 VEOS is the successor to the dspace Offlie Simulator. The ew features described below are ehacemets ad chages compared with dspace Offlie Simulator 2.2p2. dspace Release 7.4 provides VEOS as a ew software product to perform offlie simulatio o your host PC. However, you must istall a add-o to dspace Release 7.4 to work with VEOS i coectio with oe or more of the followig dspace products: AutomatioDesk CotrolDesk Next Geeratio dspace HIL API (MAPort) ModelDesk Real-Time Testig (RTT) The add-o is available at New Features ad Migratio November

180 VEOS New dspace Target for Offlie Simulatio features Iclusio of a dspace-specific measuremet service Whe you geerate a eviromet VPU usig the dspace Target for Offlie Simulatio, a dspace-specific measuremet service is icluded i the geerated VPU. This allows you to perform triggered measuremets i CotrolDesk Next Geeratio, for example. For details o triggered measuremets, refer to Cofigurig Triggered Measuremet o dspace Platforms ( CotrolDesk Next Geeratio Basic Practices Guide). Real-Time Testig support Whe you geerate a eviromet VPU usig the dspace Target for Offlie Simulatio, you ca ow eable Real-Time Testig support. This allows you to use Real-Time Testig features, for example, to stimulate VPU variables with CotrolDesk Next Geeratio's Sigal Editor i a offlie simulatio. For details o usig the Sigal Editor, refer to Usig the Sigal Editor ( CotrolDesk Next Geeratio Advaced Practices Guide). Improved support for stimulatio scearios SystemDesk 3.2 provides ew methods for accessig ad modifyig variables i a offlie simulatio. I a offlie simulatio with VEOS, you ca access ad modify these variables for stimulatio purposes. I a offlie simulatio with VEOS, you ca access these variables with CotrolDesk Next Geeratio via etries i the A2L file. Stimulatio scearios ivolvig ECU-iteral variables VEOS supports the access to ad modificatio of variables for the followig stimulatio scearios ivolvig ECU-iteral variables: Data elemets ad operatio argumets Iterruable variables RTE status variables Stimulatio scearios ivolvig a etire V-ECU VEOS supports the access to ad modificatio of variables for the followig stimulatio scearios ivolvig a etire V-ECU: Stimulatio of the KL 15 ad KL 30 sigals (ECU start-up sceario) Stimulatio of the break dow of bus commuicatio (possible for each commuicatio cotroller idividually) Iterruptio of I/O sigals Stimulatio of VPU ports with a eviromet VPU 180 New Features ad Migratio November 2012

181 VEOS New VEOS Player VEOS provides the VEOS Player. It lets you coect VPU ports i a simulatio system, ad cofigure ad ru a offlie simulatio. The VEOS Player combies the fuctioality of the followig software products which were part of the dspace Offlie Simulator. The products are discotiued with VEOS 3.0. Offlie Simulatio Player Simulatio System Editor Refer to the VEOS Player Documet. New Features ad Migratio November

182 VEOS 182 New Features ad Migratio November 2012

183 Compatibility Iformatio Where to go from here Iformatio i this sectio Supported MATLAB Releases 183 Operatig System 184 Ru-Time-Compatibility of dspace Software 187 Limitatios for Widows Vista/Widows Limitatios for 64-Bit Widows Operatig Systems i Combiatio with dspace 32-Bit Software 189 Supported MATLAB Releases Supported MATLAB releases The followig MATLAB releases are supported by the dspace products o Release 7.4: R2012a, R2012b: o Both ot supported by the RTI FPGA Programmig Blockset - FPGA Iterface o Problems usig dspace Automotive Simulatio Models (ASM): Due to performace problems i MATLAB R2012a ad 2012b, it is recommeded to istall the followig bugfix before you use ASMs with MATLAB R2012a or 2012b. Refer to R2011a, R2011b R2010b SP2 (tested with RTI FPGA Programmig Blockset but ot officially supported by Xilix) New Features ad Migratio November

184 Compatibility Iformatio For up-to-date iformatio o additioal MATLAB releases which ca be used i combiatio with dspace software, refer to Operatig System Operatig system o host PC The followig operatig systems are supported by the dspace products o Release 7.4: Widows XP Professioal with Service Pack 3 (32-bit versio) Widows XP Professioal x64 Editio is ot supported i geeral. Widows Vista Busiess, Ultimate, ad Eterprise with Service Pack 2 (32-bit versio) Oly the listed editios are supported. The Widows Vista Home ad Starter editios are ot supported. Widows 7 Professioal, Ultimate, ad Eterprise with Service Pack 1 (32-bit or 64-bit versio) Oly the listed editios are supported. The Widows 7 Home ad Starter editios are ot supported. 184 New Features ad Migratio November 2012

185 Compatibility Iformatio 64-bit operatig systems The 64-bit Widows operatig systems are supported by 32-bit dspace software ruig i WoW64 (Widows-O-Widows64). dspace software supports oly the 64-bit versio of Widows 7. Other 64-bit operatig systems (Widows XP ad Widows Vista) are ot supported. Some additioal limitatios apply whe you use a 64- bit Widows operatig system with dspace 32-bit software. Refer to Limitatios for 64-Bit Widows Operatig Systems i Combiatio with dspace 32-Bit Software o page 189. Widows Vista, Widows 7: Some geeral limitatios apply whe you use Widows Vista or Widows 7 i combiatio with dspace software. Refer to Limitatios for Widows Vista/Widows 7 o page bit versios of TargetLik ad Model Compare The 64-bit versios of TargetLik ad Model Compare require Widows 7 Professioal, Ultimate, or Eterprise (64-bit versio) with Service Pack 1. Other 64-bit operatig systems (Widows XP ad Widows Vista) are ot supported. Some additioal limitatios apply whe you use the 64-bit versio of TargetLik. Refer to Limitatios for TargetLik 64-Bit Versio ( Quick Software Istallatio Guide). CotrolDesk Next Geeratio o o CotrolDesk Next Geeratio's ECU Diagostics v2.0.1 device (supportig ASAM MCD-3 D V2.0.1) does ot support Widows 7. As a alterative, you ca use the ECU Diagostics v2.0.2 device (supportig ASAM MCD-3 D V2.0.2), which supports Widows 7. CotrolDesk Next Geeratio ca also be istalled o the MicroAutoBox Embedded PC, ruig uder Microsoft Widows 7 Ultimate (32-bit versio). New Features ad Migratio November

186 Compatibility Iformatio 32-bit dspace software ruig o 64-bit Widows operatig systems dspace software rus as a 32-bit applicatio uder 64-bit Widows operatig systems i a WoW64 (Widows-o-Widows 64- bit) subsystem. WoW64 is the x86 emulator that allows 32-bit Widows-based applicatios to ru seamlessly o 64-bit versios of Widows. This allows you to use up to 4 GB virtual memory for each 32-bit process. 32-bit versios of Widows ca address oly up to 3.2 GB of memory i total for all ruig processes icludig the operatig system itself. Allowig commuicatio via additioal firewall rules Additioal Widows firewall rules are istalled durig the istallatio of various dspace software products. For example, oe rule allows commuicatio with a dspace expasio box such as AutoBox, ad aother rule allows MotioDesk to receive motio data from a etwork chael. These example rules are created by the followig commads: The rules are created by the followig commads: etsh advfirewall firewall add rule ame="dspace Net Service" service=ay dir=i actio=allow profile=ay protocol=icmpv4:0, ay descriptio="allow the dspace Net Service to coect to a dspace expasio box via etwork." etsh advfirewall firewall add rule ame="dspace MotioDesk" program="%dspace_root%\motiodesk\bi\motiodesk.exe" dir=i actio=allow profile=ay descriptio="allow dspace MotioDesk to receive motio data via etwork." If you are ruig third-party firewall software o your host PC, esure that the TCP/IP commuicatio of dspace software is ot blocked. Operatig system o dspace Licese Server If you purchased floatig etwork liceses, you have to istall ad cofigure oe of the etworked PCs as the dspace Licese Server. The operatig system of the dspace Licese Server must be oe of the followig: Widows XP Professioal (32-bit versio) with Service Pack 3 Widows Vista Busiess, Ultimate, or Eterprise (32-bit or 64-bit versio) with the latest Service Pack Widows 7 Professioal, Ultimate, or Eterprise (32-bit or 64-bit versio) Widows Server 2003 (32-bit or 64-bit versio) 186 New Features ad Migratio November 2012

187 Compatibility Iformatio Widows Server 2008 (32-bit or 64-bit versio) Widows Server 2008 RC (32-bit or 64-bit versio) The dspace Licese Server does ot support o-widows operatig systems. Ru-Time-Compatibility of dspace Software Defiitio Ru-time compatibility meas: dspace products ca be used i parallel after software istallatio, eve if they are istalled i differet folders. dspace products without iteractio ca ru idepedetly of each other. Geeral otes o limitatios If dspace products iteract directly (for example, through automatio iterfaces) or idirectly (for example, through commo file types like.a2l limitatios may apply. For major limitatios, see below. For mior limitatios, refer to the appropriate product documetatio. I rare cases, a additioal patch must be istalled for a product to achieve ru-time compatibility. For iformatio o, whether a patch is ecessary ad for the patch itself, refer to Compatibility of products i dspace Release 7.4 Each software product i dspace Release 7.4 is ru-time-compatible with the other software products i dspace Release 7.0 up to dspace Release 7.4. Note that RCP ad HIL software products (o Release 7.4) caot be used i combiatio with RCP ad HIL software products from earlier dspace Releases. Limitatios for TargetLik ad Model Compare With Model Compare 2.1 (o dspace Release 7.1) ad earlier, you caot dump TargetLik 3.4 models. If you eed to dump TargetLik 3.4 models with Model Compare 2.1, cotact dspace support for a compatibility patch. The 64-bit versio of TargetLik caot be used i combiatio with the 32-bit versio of Model Compare ad vice versa because you ca work oly with a bit-compatible MATLAB versio (32-bit or 64-bit). New Features ad Migratio November

188 Compatibility Iformatio Limitatio for CotrolDesk Next Geeratio (= CotrolDesk as of CotrolDesk 4.0) Whe CotrolDesk 4.3 is used with dspace Release 7.0 or earlier, limitatios regardig Real-Time Testig (RTT) apply. Simulik models compiled with these releases are ot supported by the Sigal Editor (for sigal geeratio) ad for CAN Data Replay of the Bus Navigator. For details, refer to Problem with Icompatibility Betwee RTT 2.0 ad 1.6 ( Software Istallatio ad Maagemet Guide). Combiig dspace products from earlier releases For detailed iformatio ad otes o the combied use of differet products from ad with earlier releases, refer to Limitatios for Widows Vista/Widows 7 Objective Some limitatios apply whe you use Widows Vista/Widows 7 i combiatio with dspace software. MATLAB support For system requiremets of MathWorks software, refer to Fast user switchig ot supported The dspace software does ot support the fast user switchig feature of Widows. Closig dspace software before PC shutdow The shutdow procedure of Widows operatig systems might cause some required processes to be aborted although they are still beig used by dspace software. To avoid data loss, it is recommeded to termiate the dspace software maually before a PC shutdow is performed. User Accout Cotrol It is recommeded to disable Widows User Accout Cotrol (UAC) durig the istallatio of dspace software. If you caot disable it, you should ote the followig Widows behavior: If UAC is eabled, the setup programs ru with the admiistrator accout istead of the user accout. Therefore it is importat that the admiistrator accout has access to the required drives, particularly to the required etwork drives. 188 New Features ad Migratio November 2012

189 Compatibility Iformatio USB devices uder Widows 7 The first time dspace USB devices usig cables with opto-isolatio are coected to the PC, there might be a message that the device driver software was ot successfully istalled. The dspace device will evertheless work properly later o. Usig boards with ISA iterface istalled i the host PC Whe istalled directly i the host PC, ISA boards such as the DS1103 or DS813 caot be used with Widows Vista/Widows 7 with the stadard istallatio routies. If ecessary, cotact dspace Support. Limitatios for 64-Bit Widows Operatig Systems i Combiatio with dspace 32-Bit Software Objective Some additioal limitatios apply whe you use 64-bit versios of Widows 7 i combiatio with dspace 32-bit software. Limitatios of device drivers Third-party bus iterfaces (CAN, LIN, or FlexRay) are supported oly if they have 64-bit drivers from the maufacturers. Limitatios of target compilers For iformatio o support for a specific target compiler, cotact the respective compiler maufacturer. MATLAB If you istall a 32-bit versio of MATLAB uder Widows 7 (64-bit versios), the MATLAB istallatio program geerates a message that a 64-bit versio of MATLAB is available. Click OK ad cotiue istallig the 32-bit versio of MATLAB. New Features ad Migratio November

190 Compatibility Iformatio 190 New Features ad Migratio November 2012

191 Idex Idex A ASM blocksets ew features 32 ASM Diesel Egie Blockset migratig 34 ew features 33 ASM Diesel Exhaust Blockset migratig 35 ASM Drivetrai Basic Blockset migratig 35 ASM Electric Compoets Blockset migratig 36 ASM Egie Gasolie Basic Blockset migratig 39 ew features 38 ASM Egie Gasolie Blockset migratig 41 ew features 40 ASM Eviromet Blockset migratig 37 ew features 37 ASM Optimizer Blockset migratig 42 ASM Traffic Blockset migratig 42 ASM Trailer Blockset migratig 43 ew features 43 ASM Truck Blockset migratig 45 ASM Turbocharger Blockset migratig 46 ASM Vehicle Dyamics Blockset migratig 47 ew features 47 AutomatioDesk migratio 30 ew features 27 AUTOSAR TargetLik related migratio 176 ew features 146 C CotrolDesk ew features 58 CotrolDesk 3.x migratig 58 CotrolDesk Next Geeratio migratio 75 ew features 60 D dspace FlexRay Cofiguratio Package migratio 82 dspace FlexRay Cofiguratio Package ew features 79 dspace HIL API.NET ew features 77 dspace Offlie Simulator ew features 179 dspace Pytho Extesios migratio 84 ew features 83 E ECU Iterface Maager migratio 87 ew features 85 G geeral ehacemets ad chages 14 H host PC software operatig system 184 K key features 19 L Limitatios TargetLik obsolete limitatios 177 limitatios for Widows 64-Bit ad dspace 64-Bit software 189 limitatios for Widows limitatios for Widows Vista 188 M MATLAB supported releases 183 MicroAutoBox ew features 102 migratig ASM Diesel Egie Blockset 34 ASM Diesel Exhaust Blockset 35 ASM Drivetrai Basic Blockset 35 ASM Electric Compoets Blockset 36 ASM Egie Gasolie Basic Blockset 39 ASM Egie Gasolie Blockset 41 ASM Eviromet Blockset 37 ASM Optimizer Blockset 42 ASM Traffic Blockset 42 ASM Trailer Blockset 43 ASM Truck Blockset 45 ASM Turbocharger Blockset 46 migratig ASM Vehicle Dyamics Blockset 47 CotrolDesk 3.x 58 SystemDesk 127 migratio AutomatioDesk 30 CotrolDesk Next Geeratio 75 dspace FlexRay Cofiguratio Package 82 dspace Pytho Extesios 84 ECU Iterface Maager 87 Model Compare 90 MotioDesk 95 Real-Time Testig 99 RTI 103 RTI Bypass Blockset 107 RTI CAN MultiMessage Blockset 110 RTI FPGA Programmig Blockset 115 RTI LIN MultiMessage Blockset 112 Model Compare migratio 90 ew features 89 ModelDesk ew features 91 MotioDesk migratio 95 ew features 94 N ew features ASM blocksets 32 ASM Diesel Egie Blockset 33 ASM Egie Gasolie Basic Blockset 38 ASM Egie Gasolie Blockset 40 ASM Eviromet Blockset 37 ASM Trailer Blockset 43 ASM Vehicle Dyamics Blockset 47 AutomatioDesk 27 CotrolDesk 58 CotrolDesk Next Geeratio 60 dspace FlexRay Cofiguratio Package 79 dspace HIL API.NET 77 dspace Offlie Simulator 179 dspace Pytho Extesios 83 ECU Iterface Maager 85 MicroAutoBox 102 Model Compare 89 ModelDesk 91 MotioDesk 94 Real-Time Testig 99 RTI Bypass Blockset 105 RTI CAN MultiMessage Blockset 109 RTI FPGA Programmig Blockset 113 New Features ad Migratio November

192 Idex ew features RTI LIN MultiMessage Blockset 111 RTI/RTI-MP 101 RTLib 101 SystemDesk 118 ot supported MATLAB features 102 P product overview 16 R Real-Time Testig migratio 99 ew features 99 requiremets host PC software operatig system 184 RTI Bypass Blockset migratio 107 ew features 105 RTI CAN MultiMessage Blockset migratio 110 ew features 109 RTI FPGA Programmig Blockset migratio 115 ew features 113 RTI LIN MultiMessage Blockset migratio 112 ew features 111 RTI/RTI-MP ew features 101 RTLib ew features 101 S supported MATLAB releases 183 system requiremets operatig system 184 SystemDesk migratig 127 ew features 118 T TargetLik API commads chages 175 AUTOSAR features, ew compatibility mode 146 compoet-based developmet 146 exchagig SWCs as object code 146 frame model geeratio, improvemets 146 frame models, updatig 146 TargetLik AUTOSAR features, ew hook fuctios, ew 142 supported releases 146 code chages migratio 168 code efficiecy, improvemet of 144 code geerator optios backward compatibility 174 chaged default value 174 hook fuctios AUTOSAR 142 ew 142 migratig to ew versio 158 migratio AUTOSAR related 176 code chages 168 obsolete limitatios 177 various aspects 176 ew API commads V-ECU geeratio 142 virtual ECU geeratio 142 ew code geerator optios 138 ew features 132 AUTOSAR 146 code geeratio 132 compoet-based developmet 133 compute-through-overflow, optioal deactivatio 134 custom code, improvemets to 134 geeral chages 145 geeral ehacemets 145 modular developmet 133 virtual ECU (V-ECU) geeratio 135 ew versio migratig to 158 target support discotiued compiler versios 136 discotiued evaluatio boards 136 ew compiler versios 136 ew evaluatio boards 136 supported targets 136 TargetLik Data Dictioary API commads chages 175 ew commads 155 discotiued features 160 migratig to ew versio 158 migratio 160 discotiued documetatio 160 upgradig existig data dictioaries 164, 165 upgradig from versio 2.x 167 V ew features 132, 150 compare ad merge 151 data maagemet 152 DD IcludeFileGroup objects 155 diff ad merge 151 Loadig oe DD to differet workspaces 155 Object Explorer improvemets 155 poits of iclusio 152 Property Value List improvemets 155 ew versio migratig to 158 versio history 16 W Widows 64-Bit limitatios 189 Widows 7 limitatios 188 Widows Vista limitatios New Features ad Migratio November 2012