id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5103	CompositeModel::solveAlgLoop: max. number of iterations	Boldizsár Németh <nboldi@…>	Lennart Ochel	"While trying to simulate two connected FMUs, I got the following error.

{{{
nboldi@nboldi-VirtualBox:~/OMSimulator$ build/linux/src/OMSimulator/OMSimulator ../moonlander.lua
info:	New temp directory: ""/home/nboldi/OMSimulator/temp""
# FMI composite model ""model""
## FMI sub model ""Lander""
type: FMU
## FMI sub model ""World""
type: FMU
## Connections
model: World:h -> Lander:h
model: World:v -> Lander:v
model: Lander:u -> World:u
warning: Alg. loop (size 3)
error:   CompositeModel::solveAlgLoop: max. number of iterations (10) exceeded at time = 0.000000
info:	Result file: results.mat (bufferSize=1)
error:   failed to fetch variable Lander:u
error:   Failed to log simulation results
MoonLander::InitToFF
MoonLander::FFtoControlled
Segmentation fault (core dumped)
}}}

The FMUs World and Lander are connected. There is one variable from Lander to World (u) and two variables from World to Lander (h and v).

After initialization, Lander outputs 0 for u, and World returns 1000 and 0 for h and v. They should return the same value for repeated calls regardless of the inputs they are given. I checked this behavior by simulating individual FMUs.

Since the FMUs were generated from different sources, it is possible that they are unconventional in some way. Could you suggest what can be the problem behind the errors?"	defect	closed	high	1.13.0	OMSimulator	v1.13.0-dev-nightly	worksforme