matlab-cosimulate-sumo-simulink

Add a Server block pointing to your .sumocfg file and a Client block with a matching port (default 8813) from the SumoInterfaceLibrary. Use a fixed-step solver whose step size matches the SUMO step-length, then add Reader and Writer blocks to exchange vehicle data.

Define the ego vehicle in a .rou.xml route file with depart="0" so it exists from simulation start, then use a Writer block with the Vehicle/Speed topic to set its desired speed each step. Avoid <stop> clauses in the ego route since SUMO stop directives override the Speed Writer.

Vehicle-topic Reader and Writer blocks crash if the target vehicle does not exist yet in SUMO. Gate them inside Enabled Subsystems triggered by Clock >= spawnTime, or define the vehicle in the route file with depart="0".

The Server block concatenates SUMO_HOME with the binary path without a separator, so a SUMO_HOME lacking a trailing backslash causes launch failure. Run setenv('SUMO_HOME', [getenv('SUMO_HOME') filesep]) before simulating.

The Actor block's SpawnMethod='Position' is broken in the support package. Use the spawn-then-teleport pattern: spawn with SpawnMethod='Lane', wait one step with a Unit Delay, then move the vehicle with a Writer(Vehicle/Position) block using int32 lane index and uint8 keep-route types.

Avoid it for pure SUMO traffic studies without Simulink control logic, where SUMO's CLI or Python TraCI is simpler. It also does not replace vehicle dynamics modeling, which requires Vehicle Dynamics Blockset, or scenario design in Driving Scenario Designer.