New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Communications to use Modelica_DeviceDrivers #277
Comments
Is there anything still to do fir this issue or can it be closed, @AnaConstantin? |
@AnaConstantin, could you give an update if this issue is still relevant or has been solved? |
@mlauster the work still has to be done, but it is not a priority for the next release. I would leave it open. |
@AnaConstantin, just a quick update, is this still an open issue? |
It is still open. I looked over it again. It might take some time to implement, but it is very interesting, since the TCP/IP interface in ModelicaDeviceDrivers seems to be more robustely constructed. |
I gave three reasons in #149 (comment) why current design has some drawbacks.
Since it is not complex to do it, I believe it is some resource=time constraint, which is the bottleneck to keep this issue open for more than 13 months. |
@AnaConstantin, I don't think there is much to happen here, can we close this? |
I really wonder why there is no progress, but see my comment above from 20 Nov 2017. |
@tbeu, @AnaConstantin is in parental leave and so far nobody else took over this work. I will see with @AnaConstantin how to proceed here. Thanks for your input and interest! |
Just to wrap up what still needs to be done here: Scan our Communications Package and make use of https://github.com/modelica/Modelica_DeviceDrivers. All parts that cannot be used to extend the functionalities of Modelica Device Drivers should be deleted. |
Tested the new implementation by @tbeu. The example provides the same results. |
Resolved through #722 |
As mentioned in #149, the communication package should use https://github.com/modelica/Modelica_DeviceDrivers.
The text was updated successfully, but these errors were encountered: