fmi-standard | Specification of the Functional Mock-Up Interface (FMI) | Mock library

by modelica C Version: v3.0.1-rc.1 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | fmi-standard Summary

fmi-standard is a C library typically used in Testing, Mock applications. fmi-standard has no bugs, it has no vulnerabilities and it has low support. However fmi-standard has a Non-SPDX License. You can download it from GitHub.

Specification of the Functional Mock-Up Interface (FMI)

Support

Quality

Security

License

Reuse

Support

fmi-standard has a low active ecosystem.

It has 219 star(s) with 78 fork(s). There are 51 watchers for this library.

It had no major release in the last 12 months.

There are 23 open issues and 1024 have been closed. On average issues are closed in 75 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of fmi-standard is v3.0.1-rc.1

Quality

fmi-standard has 0 bugs and 0 code smells.

Security

fmi-standard has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

fmi-standard code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

fmi-standard has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

fmi-standard releases are available to install and integrate.

It has 2375 lines of code, 0 functions and 33 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of fmi-standard

Get all kandi verified functions for this library.

fmi-standard Key Features

No Key Features are available at this moment for fmi-standard.

fmi-standard Examples and Code Snippets

No Code Snippets are available at this moment for fmi-standard.

Community Discussions

Trending Discussions on fmi-standard

How to export c file/function to FMU using fmusdk

FMI - C standard library version differences cause linking errors

QUESTION

How to export c file/function to FMU using fmusdk

Asked 2017-Jul-07 at 11:32

This is my function. I am trying to export this code to fmu. I am using fmusdk.

For each cycle(time step),

my input should be changed to the value given during simulation.
myexecute() should be called.
the values of input and pout should be stored during simulation, so that we can plot the values after the simulation.

I tried the examples(BouncingBall and values) given in fmusdk. I have created corresponding fmus and imported them in Amesim. They are working fine. But i am unable to figure out how to do the same for my C file/function

...

ANSWER

Answered 2017-Jul-07 at 11:32

Consider the C file given below similar to the files you mentioned bouncingBall.c or valus.c . Since you have referred the function myexecute from another c file, replace yourCFile.c and/or yourHFile.h with the correct files. Also your modelDescription.xml should be in sync with this C file. For ex) guid value should be the same in both files. Also the value reference for the scalar variables should be the same. Analyse and #define pin_ 0 . Similarly for pout. Create a folder structure similar to bouncingBall. Create a separate batch file, since we have to include additional files(yourCFile.c and/or yourHFile.h)

Source https://stackoverflow.com/questions/44964787

QUESTION

FMI - C standard library version differences cause linking errors

Asked 2017-Apr-11 at 05:37

I have a publicly-available FMU for which I am trying to link the embedded .so file with the rest of my program. (This is contained within the .fmu file if you view as an archive.) During the linking phase I am getting the following undefined reference errors:

RoomHeating_OM_RH.so: undefined reference to '__longjmp_chk@GLIBC_2.11'

RoomHeating_OM_RH.so: undefined reference to '__fread_chk@GLIBC_2.7'

If I look at the content of RoomHeating_OM_RH.so with a tool like nm -a, I see lots of undefined references of this form that aren't causing errors at link time. Here are a couple such lines from the nm -a output:

U __vsnprintf_chk@@GLIBC_2.3.4

U _setjmp@@GLIBC_2.0

However, the ones that are causing errors are differentiated from the rest of them by the fact that they have newer versions of GLIBC in the name. Here's what I have in my /lib dir for the libc library (yes I realize these are old versions, but it's what I am stuck with for now):

/lib/libc-2.5.so

/lib/libc.so.6

So my guess is that I don't have a new enough version of libc to link against. Is it a requirement that the version of libc be exactly what the .so file calls out? Or does it only need to be equal to or newer than the version called out? Furthermore, does the FMI specification even cover this aspect of compatibility? Or does it assume that IF .so files are provided in the FMU that they MUST be compiled using the same or older versions of libraries as will be installed on the target machine?

...

ANSWER

Answered 2017-Apr-11 at 05:37

So my guess is that I don't have a new enough version of libc to link against.

Correct.

Is it a requirement that the version of libc be exactly what the .so file calls out?

No. You need GLIBC-2.11 or newer. See this answer for explanation.

Source https://stackoverflow.com/questions/43334208

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install fmi-standard

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: