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 5
  • Members are here 0
More Content

Exporting fmu from event (dcf in private database)

jozef.bucha
Hi, is somebody having same issue? Exporting fmu when dcf file is stored in private database (i.e. just coping acceleration_dcf.xml from shared database) for me i am always having this error:
aview_0eOBQeCvXL
Jozef
  • 0
    Hi Josef,
     
    I wonder if the message about "_controls.acf" is the problem here? I think that this dialog box assumes/depends that you have previously ran a simulation with the model in this working directory while the Controls plugin is loaded. When the Controls plugin is loaded and you run a simulation (either run it, or just do "files only") the simulation process produces an extra file named <event>_controls.acf. That file must be put into the proper field when exporting.
     
    So this is one possible problem that you might face here. I would check that you have the file in the working folder AND you have specified the exact name of this file in the dialog box - that might be the problem.
    Good luck,
    Kent
     
  • 0
    Hi Kent,
     
    thanks for reply,
     
    I am using for fmu export Simulate/FMI Interface/General FMU Export so problem with incorrect names should not happen.
     
    Creation of FMU fails somewhere during process. Subfolder with correct name is created. adm file is copied, acf file has correct name but is empty.
     
    XML event (dcf is from shared database) is just copied to private database. Event is created as File Driven Events, Analysis Mode: Event Only
     
    explorer_4eemuDb677
     
    Jozef
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.