Hi,
you come at almost the right time: in the next few weeks I'll start looking 
into some *general/automatic way to export FMUs out of Chrono* and I plan 
to be able to generate the first *Cosimulation FMUs *within September.
I recently spent some time upgrading and fixing the Chrono serialization 
feature that should come in handy for the FMU exporting process so it's one 
issue less.
However, I won't probably have time to deal with the *ModelExchange* 
version any time soon. Same applies for the most advanced features like 
*fmi2GetDirectionalDerivative* for which I don't have an immediate need.

In any case, please consider that I'm looking for a general/automatic 
process: it should be *WAY easier* if you just want to *manually create an 
FMU for your specific code*.
In this case you should start from downloading the FMI 
headers https://fmi-standard.org/ and create the definition for the 
functions that you find in *FunctionTypes.h*.
This approach is easier, but you still need to have some knowledge about 
the compilation and linking process, especially if you go for the runtime 
dynamic linking.

Hope to have better news soon.
Dario

Il giorno lunedì 10 luglio 2023 alle 15:59:52 UTC+2 [email protected] ha 
scritto:

> Hello everybody, First of all thank you for this great job. Chrono is a 
> very powerful tool. I am currently interested in the FMI standardized 
> format. I read that in 2019 the team was thinking of integrating it in 
> Chrono Project to be able to import or export FMU models in the future. Is 
> there any progress on this subject or work under progress ?
>
> If not, any help or advises on steps to follow if I would like to be able 
> to do it ? 
>
> Thank you so much.
>

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/0005e969-519d-47a0-929b-ad8fcfed3e8an%40googlegroups.com.

Reply via email to