Change Request #3853
Revisit method to launch co-simulation server
- Are there more elegant ways to launch the process rather than assuming that Java is in the path and executing
java -jar coe.jar?
- Check if MacOS support can easily be provided
#3 Updated by Tiziano Munaro 5 months ago
- Status changed from New to In Progress
- % Done changed from 0 to 70
#4 Updated by Tiziano Munaro 5 months ago
- File fmi_co-simulation.af3_23 fmi_co-simulation.af3_23 added
- Status changed from In Progress to Resolved
- Assignee changed from Tiziano Munaro to Alexander Diewald
- % Done changed from 70 to 100
The COE service is now
- imported as a library and started using its
mainmethod instead of run via a OS-level command (
java -jar coe.jar),
- executed as a runnable
- within an Eclipse job
- asynchronously (thus not blocking the UI while running - however, an activity indicator in the lower right corner of the window provides the necessary feedback to the user).
Moreover, in case of an error (e.g. due to an FMU not being found), the
ErrorStream of the
HttpURLConnection is read, providing the user with useful feedback instead of just returning the response code.
- The attached AF3 project contains a component architecture called
Original. Feel free to export one or both of the components (
Relay) as FMUs, combining them in other component architectures which can then be co-simulated.
- Keep in mind that the co-simulation of a component architecture is only possible with at least two components, where at least one of them has to have an FMU specification.
- When handling state automata make sure that they are deterministic! Otherwise, semantically correct FMUs are generated which, however, won't perform any action.