RMIModelServer issueshttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/RMIModelServer/-/issues2019-11-07T21:31:09+01:00https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/RMIModelServer/-/issues/7Runtime model exchange2019-11-07T21:31:09+01:00Evgeny KusmenkoRuntime model exchangeCurrent situation: dll/so is fixed; if a new autopilot model is provided RmiModelServer needs to be recompiled.
Goal: Make the RMIModelServer parameterizable, e.g. via its command line interface with a new model, so that we don't need t...Current situation: dll/so is fixed; if a new autopilot model is provided RmiModelServer needs to be recompiled.
Goal: Make the RMIModelServer parameterizable, e.g. via its command line interface with a new model, so that we don't need to rebuild the RMIModelServer, whenever we want to test a new autopilot.
@jean.meurice for infoWei LuWei Lu2019-11-08https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/RMIModelServer/-/issues/6Exchangeability of HW-Emulator2019-11-14T18:29:19+01:00Evgeny KusmenkoExchangeability of HW-Emulatorden RMI Server so umbauen, dass man per Flag einen Emulator auswählen kann:
- Unicorn
- None
- Predefined (Latenz=const)
Alle Emulatoren müssen von einer gemeinsamen Klasse erben oder ein Emulator-Interface implementieren, um Austauschba...den RMI Server so umbauen, dass man per Flag einen Emulator auswählen kann:
- Unicorn
- None
- Predefined (Latenz=const)
Alle Emulatoren müssen von einer gemeinsamen Klasse erben oder ein Emulator-Interface implementieren, um Austauschbarkeit zu erlauben.
Auch müssen die Parameter auf Sinnhaftigkeit geprüft werden (jeder Emulator braucht ein bestimmtes Set, manche Params schließen andere aus, z.B. macht no_time keinen Sinn in Verbindung mit CPU_freq-Angabe).Jean MeuriceJean Meurice2019-06-12https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/RMIModelServer/-/issues/5[ERR] Could not open DLL/ Could not open SO2019-11-11T16:40:48+01:00Sabrina Wolff[ERR] Could not open DLL/ Could not open SOWhen starting a simulation, an error in the RMIServer occured: "[ERR] Could not open DLL: path\to\RMIModelServer\install\autopilot\AutoPilotAdapter\AutopilotAdapter.dll" or "[ERR] Could not open SO: path\to\RMIModelServer\install\autopil...When starting a simulation, an error in the RMIServer occured: "[ERR] Could not open DLL: path\to\RMIModelServer\install\autopilot\AutoPilotAdapter\AutopilotAdapter.dll" or "[ERR] Could not open SO: path\to\RMIModelServer\install\autopilot\AutoPilotAdapter\AutopilotAdapter.so". The Server wants to open the AutopilotAdapter.so and AutopilotAdapter.dll files located in the "AutopilotAdapter" folder but this folder does not exist. The files are placed in the "autopilot" folder. So to fix it, you just need to create a folder named "AutopilotAdapter" in "autopilot" and place both files into it.
![Unbenajjnnt](/uploads/c3b7888a4fa598a20bd20824b8e26d1e/Unbenajjnnt.jpg)
![Unbenkkklannjjjt](/uploads/c101a42422363c24c6303c224cabdac3/Unbenkkklannjjjt.jpg)Evgeny KusmenkoEvgeny Kusmenkohttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/RMIModelServer/-/issues/4How to handle structs in the automated adapter generation?2019-10-09T18:00:07+02:00Evgeny KusmenkoHow to handle structs in the automated adapter generation?Now, only primitive types are adapted, please think about structs.
Possible solutions: introduce classes for structs or flatten structsNow, only primitive types are adapted, please think about structs.
Possible solutions: introduce classes for structs or flatten structsJean MeuriceJean Meuricehttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/RMIModelServer/-/issues/3Readme.md2020-07-08T16:35:25+02:00Evgeny KusmenkoReadme.mdOnce you get the MPC controller generated and intgrated , please create a readme / tutorial , how to get an executable autopilot into the rmimodelserver starting from an embeddedmontiarc modelOnce you get the MPC controller generated and intgrated , please create a readme / tutorial , how to get an executable autopilot into the rmimodelserver starting from an embeddedmontiarc modelJean MeuriceMarkus Philipp BauerJean Meuricehttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/RMIModelServer/-/issues/2Investigate generation of autopilot adapter2019-10-09T17:58:44+02:00Evgeny KusmenkoInvestigate generation of autopilot adaptercurrently the autopilot adapter is quite simple and most of the code is hard written
please check how the generator can be extended so that a suitable adapter (+ jni calls + (rmi interfaces)) are generated automatically and do not need ...currently the autopilot adapter is quite simple and most of the code is hard written
please check how the generator can be extended so that a suitable adapter (+ jni calls + (rmi interfaces)) are generated automatically and do not need to be adapted manually whenever the interface of the autopilot component is changed
@markus.bauer can show you how the ros generation process works. maybe it makes sense to omit the tagging stepJean MeuriceJean Meuricehttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/RMIModelServer/-/issues/1Investigate RMI mapping problem2019-11-12T20:44:58+01:00Evgeny KusmenkoInvestigate RMI mapping problemapparently the rmi server can't cope with multiple controllers. Please investigate why/where the bug occursapparently the rmi server can't cope with multiple controllers. Please investigate why/where the bug occursHengwen Zhanghengwen.zhang@rwth-aachen.deHengwen Zhanghengwen.zhang@rwth-aachen.de