Following Cadence Design Systems’ acquisition of the Design & Engineering (D&E) business, the D&E Community Forum on the Nexus Community Center has been migrated in the Cadence Physical System Simulation Community. For more details and if you have any questions, please refer to the FAQ.

Stats

  • State Not Answered
  • Replies 2
  • Subscribers 1
  • Views 3
  • Members are here 0
More Content

Using subrutine request from Acar in Aview and in FMU

jozef.bucha
Hello everyone,
 
I have model of vehicle in Aview created according templates from Acar. Model is working without problem. The model in Aview contains also requests from Acar (i.e. from rigid chassis.tpl based on subrutine abgVDM::req907). During normal simulations in View, those requests work without problem.
 
But after fmu export of model from Aview the model is not working in simulink (Error in supplied FMU: An error occurred in function 'fmi2ExitInitializationMode' for block...), without request fmu from same model works without problem.
 
Is it possible somehow to export fmu with those subrutine request or not?
 
Thanks
 
Jozef
 
Parents
  • 0
    Thanks Kent, i have tried that, but during my test using Adams 2021_1 i have noticed, that i am getting this error in Matlab 2018b also in Matlab 2021a. It should me normal co-simulation between Matlab and Adams 2021_1. It is first example form ADM711:
     
    Warning: Location D:\adams_working_dir\cosim\The syntax of the command is incorrect.
    C:\PROGRA~1\MSC~1.SOF\Adams\2021_1~1\controls\win64 specified for a File or Folder is invalid.
    > In path (line 109)
     In addpath (line 86)
     In cosim (line 18)
    Warning: Location D:\adams_working_dir\cosim\The syntax of the command is incorrect.
    C:\PROGRA~1\MSC~1.SOF\Adams\2021_1~1\controls\matlab specified for a File or Folder is invalid.
    > In path (line 109)
     In addpath (line 86)
     In cosim (line 20)
    Warning: Location D:\adams_working_dir\cosim\The syntax of the command is incorrect.
    C:\PROGRA~1\MSC~1.SOF\Adams\2021_1~1\controls\utils specified for a File or Folder is invalid.
    > In path (line 109)
     In addpath (line 86)
     In cosim (line 22)
     
    Repeating same procedure using Adams 2021_2_beta works without problem on same computer with same Matlab. Is some issue with this in Adams 2021_1 in general or just with my Adams 2021_1
     
    Thanks
     
    Jozef
     
     
    Attached Files (1)
Reply
  • 0
    Thanks Kent, i have tried that, but during my test using Adams 2021_1 i have noticed, that i am getting this error in Matlab 2018b also in Matlab 2021a. It should me normal co-simulation between Matlab and Adams 2021_1. It is first example form ADM711:
     
    Warning: Location D:\adams_working_dir\cosim\The syntax of the command is incorrect.
    C:\PROGRA~1\MSC~1.SOF\Adams\2021_1~1\controls\win64 specified for a File or Folder is invalid.
    > In path (line 109)
     In addpath (line 86)
     In cosim (line 18)
    Warning: Location D:\adams_working_dir\cosim\The syntax of the command is incorrect.
    C:\PROGRA~1\MSC~1.SOF\Adams\2021_1~1\controls\matlab specified for a File or Folder is invalid.
    > In path (line 109)
     In addpath (line 86)
     In cosim (line 20)
    Warning: Location D:\adams_working_dir\cosim\The syntax of the command is incorrect.
    C:\PROGRA~1\MSC~1.SOF\Adams\2021_1~1\controls\utils specified for a File or Folder is invalid.
    > In path (line 109)
     In addpath (line 86)
     In cosim (line 22)
     
    Repeating same procedure using Adams 2021_2_beta works without problem on same computer with same Matlab. Is some issue with this in Adams 2021_1 in general or just with my Adams 2021_1
     
    Thanks
     
    Jozef
     
     
    Attached Files (1)
Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.