You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default IP address assigned by the FMU exporter shall be localhost, i.e. 127.0.0.1, which fits in many cases.
This should be loosened a bit, since there are use cases where the XCP service of the FMU runs on a specific machine (e.g. in the cases of FMU remoting or other forms of FMU proxying, where the FMU running on the simulator only interfaces to the actual SW/FMU, and hence the XCP slave is also on that machine).
The text was updated successfully, but these errors were encountered:
@andreas-junghanns Not quite sure what your addition refers to. Maybe you can check/fix this by yourself.
At least for the port it is mentioned that it must be consistent throughout FMU/XCP slave configuration and A2L file.
@andreas-junghanns Not quite sure what your addition refers to. Maybe you can check/fix this by yourself. At least for the port it is mentioned that it must be consistent throughout FMU/XCP slave configuration and A2L file.
Inside the a2l file(s), the IP/Port combinations are also specified. What we define in the .xml file must not contradict the a2l definitions. -- just saw, this is taken care off by PR #26.
Currently the spec states:
This should be loosened a bit, since there are use cases where the XCP service of the FMU runs on a specific machine (e.g. in the cases of FMU remoting or other forms of FMU proxying, where the FMU running on the simulator only interfaces to the actual SW/FMU, and hence the XCP slave is also on that machine).
The text was updated successfully, but these errors were encountered: