v0.2.0

Changelog:

New connection handling:

• Simulink won’t freeze anymore if is not receiving from BeamNG:
  • At the start of the simulation will run without any block until the connection is established and will inform in the Diagnostic Viewer when the connection is opened.
  • If there was a connection between Simulink and BeamNG running and Simulink stops receiving messages from BeamNG, it will stop the simulation after 3 seconds.
  • Reloading the scenario/vehicle, will correctly close the UDP socket on the BeamNG side, allowing to reload the controller vehicleSystemsCoupling without any error

New examples:

• demo_0.m run a simulation where the car is automatically driven by the BeamNG AI and Simulink is used only to display some data. The simulation can run infinitely and can be stopped pressing any key in the Matlab Command Window.
• demo_1.m run a simulation where Simulink control the car using the driver inputs (throttle, brake and steering) to perform a double lane change. The simulation stops automatically after performing the maneuver.
• demo_2.m run a simulation where Simulink control the car using the driver inputs (throttle, brake and steering) to perform a braking test. The simulation stops automatically after performing the maneuver.
• demo_3.m run a simulation where the car can be controlled manually from BeamNG and Simulink decides the amount of torques to apply on each wheel. The simulation can run infinitely and can be stopped pressing any key in the Matlab Command Window.

v0.1.0

Initial BeeamNG Simulink Generic Interface release