OK, so you used the FMU approach. So you will get all the results from the Car model. And you have found the results file from the unpacked FMU for the View model. Correct?
Well, you have to define in the View model what outputs you want. Results, graphics and request files. Adams/View does not automatically create requests for all elements in the way Car does it, so you have to define all requests manually in the View model.
You will never be able to animate both models at the same time, at least not in Adams PPT (well you could load both models, bit results or graphics files and animate in separate views).
Was the simulation successful? No strange discretization problem? Stable results?
One thing I'm currently working on is stability of co-simulations and that includes FMU connections. So we are very interested in what you are doing. Anything you can tell us can help us create a better interface in Adams.
OK, so you used the FMU approach. So you will get all the results from the Car model. And you have found the results file from the unpacked FMU for the View model. Correct?
Well, you have to define in the View model what outputs you want. Results, graphics and request files. Adams/View does not automatically create requests for all elements in the way Car does it, so you have to define all requests manually in the View model.
You will never be able to animate both models at the same time, at least not in Adams PPT (well you could load both models, bit results or graphics files and animate in separate views).
Was the simulation successful? No strange discretization problem? Stable results?
One thing I'm currently working on is stability of co-simulations and that includes FMU connections. So we are very interested in what you are doing. Anything you can tell us can help us create a better interface in Adams.