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
OMsimulator reports the folowing error when a integer output on the form "." is connected to an enum:
"Type mismatch in connection:..."
Steps to reproduce the behavior
Checkout "Embrace_trunk\WP3\D3.0\Saab\IntToEnumExample" from the embrace repository.
Run the file "SSP_Export.py" available in the folder mentioned above.
Version and OS
Linux, CentOS 7.4 VS. OMSimulator v2.1.1.post59-g0165678-linux
It seems like the connection works if i change the order of the signals i.e
addConnection("model.root.AdaptionUnit.sWsignals.Aircraft_State","model.root.ECS_SW.Input.Aircraft_State"): this works
addConnection("model.root.ECS_SW.Input.Aircraft_State","model.root.AdaptionUnit.sWsignals.Aircraft_State"): this produces the error above
The order does not matter for reals that are connected in the same way
Description
OMsimulator reports the folowing error when a integer output on the form "." is connected to an enum:
"Type mismatch in connection:..."
Steps to reproduce the behavior
Checkout "Embrace_trunk\WP3\D3.0\Saab\IntToEnumExample" from the embrace repository.
Run the file "SSP_Export.py" available in the folder mentioned above.
Version and OS
Linux, CentOS 7.4 VS. OMSimulator v2.1.1.post59-g0165678-linux
@lochel @arun3688
The text was updated successfully, but these errors were encountered: