Hi, someone found a solution to this problem? Because I have the same one.
Actually, the main issue is to get the correct path to the FMU. This is still an issue, and I am really greatful if someone has some tips on this! The path to the matlab-fmu is included in the matlab path..
Actually, the main issue is to get the correct path to the FMU. This is still an issue, and I am really greatful if someone has some tips on this! The path to the matlab-fmu is included in the matlab path..
Hi, Thanks for providing this FMI toolbox for MATLAB. I have searched for some time, for an alternative to using Simulink and more conveniently use the script and command interface. I have downloaded the files, unzipped and made the environment variables in windows. Python 2.72 and Visual Studio Community 2019 is installed. MATLAB Version: 9.2.0.538062 (R2017a) However, the 'fmu.instantiate' will not execute and produces an error. Is there a way to debug this? I have tried to export the ControlledRadiator.mo,...
Hi, Thanks for providing this FMI toolbox for MATLAB. I have searched for some time, for an alternative to using Simulink and more conveniently use the script and command interface. I have downloaded the files, unzipped and made the environment variables in windows. Python 2.72 and Visual Studio Community 2019 is installed. MATLAB Version: 9.6.0.1072779 (R2019a) However, when running the script 'Import/SimpleController', i cannot seem to get the fmu = FMUModelExchangeV2(...) to work with the path...
Hi, Thanks for providing this FMI toolbox for MATLAB. I have searched for some time, for an alternative to using Simulink and more conveniently use the script and command interface. I have downloaded the files, unzipped and made the environment variables in windows. Python 2.72 and Visual Studio Community 2019 is installed. MATLAB Version: 9.6.0.1072779 (R2019a) However, when running the script 'Import/SimpleController', i cannot seem to get the fmu = FMUModelExchangeV2(...) to work with the path...
updated documentation (version history)
updated tutorial for exporting FMUs (new version of function createFMU)
added tutorial folder to release (amd removed the test folder from the release)
added support for FMU v2.0 export
package +fmipputils is copied from FMI++
FMU export uses now an OO-based approach
added example for import
added example for FMUCoSimulation
updated version from FMI++
added content
adapted to new back-end definition (partial update to FMI 2.0)
added log messages to export example script
added some documentation
added tutorial
updated examples
release version v0.2
adopted script according to latest changes in fmipputils scripts
runs now with Python 2 and Python 3
fixed calculation of syncTime in export example
small changes to make code more object-oriented
updated examples
first release versio: added minimal documentation, fixed license, added SUNDIALS stuff
adapted test to name change of class FMUBase to FMIAdapter
switched to 64-bit toolchain (MATLAB R2017a); moved package fmipputil to this repository; updated FMI++ sources; other cosmetic changes;
removed contructor
first commit
improved handling of JVM and ficed step size options
use graphical model for testing
use Visual Studio Express 2013, add support for Python 3
added script to ease setup
Hi, Firstly thank you for the toolbox; it is very powerful. I was wondering if anyone has had any success with utlising this toolbox with a 64 bit of Matlab?. I have been testing with 2016b and 2018b without any success. Is there any plans to update the combatability with newer versions of Matlab? Does anyone know of any alternatives for importing and simulating FMUs in theMatlab interface (64 bit)? I would rather not go with Simulink.
I have found two issues and solved them. Two library dependencies were missing. Added them in MATLAB bin>win32 directory. boost_filesystem-vc120-mt-1_58.dll boost_system-vc120-mt-1_58.dll The addpath command adds the packages to search path. But the application only runs and creates FMU when MATLAB's current directory is in packages>lib. This is really weird and I don't know why this happened.
I have found two issues and solved them. Two library dependencies were missing. Added them in MATLAB bin>win32 directory. boost_filesystem-vc120-mt-1_58.dll boost_system-vc120-mt-1_58.dll The addpath command adds the packages to search path. But the application only runs and creates FMU when MATLAB's current directory is in packages>lib. This is really weird and I don't know why this happened.
I have found two issues and solved them. Two library dependencies were missing. Added them in MATLAB bin>win32 directory. boost_filesystem-vc120-mt-1_58.dll boost_system-vc120-mt-1_58.dll The addpath command adds the packages to search path. But the application only runs and creates FMU when MATLAB's current directory is in packages>lib. This is really weird and I don't know why this happened.
I'm trying to run the create_fmu.m inside test > export. I'm having invalid MEX file error for the file fmippexMEX.mexw32. I have used windows 7 32 bit OS and MATLAB 2013a as mentioned in the documentation. I also have Visual Studio 2013 Express and Python 2.7 installed. Can you suggest me how to resolve this issue? I have attached the screenshot of MATLAB command window here
I'm trying to run the create_fmu.m inside test > export. I'm having invalid MEX file error for the file fmippexMEX.mexw32. I have used windows 7 32 bit OS and MATLAB 2013a as mentioned in the documentation. I also have Visual Studio 2013 Express and Python 2.7 installed. Can you suggest me how to resolve this issue? I have attached the screenshot of MATLAB command window here: ![(https://drive.google.com/file/d/0B6AtN2LWjMX3akNjLVNFaFdZLTA/view?usp=sharing)]
I'm trying to run the create_fmu.m inside test > export. I'm having invalid MEX file error for the file fmippexMEX.mexw32. I have used windows 7 32 bit OS and MATLAB 2013a as mentioned in the documentation. I also have Visual Studio 2013 Express and Python 2.7 installed. Can you suggest me how to resolve this issue? I have attached the screenshot of MATLAB command window here: