Synchronizing 2 Simulink Models on 2 different machines via UDP
17 vues (au cours des 30 derniers jours)
Afficher commentaires plus anciens
Hi, I'm trying to sinchronize 2 simulink models in 2 different machines to divide the work load of each. So far this is a test and my model is a simple mass, damper, spring moving only on the x-asis connected to a PID controller. I change the reference point with a joystick and visualize via VR Sink. Everything works fine if ran in one machine.
So what I did was divide the model so I put the PID controller in one machine, and the Plant with the physics in another machine and connected the models via UDP. If I start the models at the same time (by clicking the run button on both machines at the same time) the model works excellent with what appears to be zero delay.
The problem arises when I start the model in one machine first, and then, few seconds later I start the other. If I do this, the mass behaves like it's on crack and flyes everywhere. I believe this is because there is old data stored in some type of buffer somewhere and the model that starts late gets old data feed to it and it never schincronizes again; however I am not sure of this because in theory UDP is a best effort protocol and old data should be disregarded, right?
Anyways, some more useful information:
Ran on Matlab 2012a.
The model is compiled as a "Real-time windows target" and I use the Analog Input to get data from the joystick and Package output/Input to send/receive UDP data between machines.
From one machine I send the output from the PID controller and the other sends position data from the Physics Plant, so both computers send data to the other.
I did the experiment using a simple wireless router, and also tried Wireless Ad-Hoc connection to make sure the router wasn't causing the problem.
I appreciate any help given. Thanks!
Réponse acceptée
Plus de réponses (2)
Walter Roberson
le 14 Juil 2012
Data that manages to make its way between systems, and is matched to an open socket, is not discarded in UDP, not unless the receiving system requests discarding.
UDP packets that are received at a system that has no socket for them should be discarded by that system. But since there is no particular length of time defined for delivery, the packets could in theory be "in transit" for an undetermined amount of time. Your application needs to be able to detect and disregard "old" packets... even in cases where "old" turns out just to be "out of order" (a newer packet was received before an older one.)
7 commentaires
Walter Roberson
le 7 Août 2019
https://en.wikipedia.org/wiki/Precision_Time_Protocol PTP is a possible option for synchronizing local computers.
K E
le 16 Juil 2012
A workaround to your original problem might be to run your Simulink model with the Parallel Computing toolbox one just one machine so that Simulink runs faster, but you do not need both machines. Here are some tips on faster Simulink execution. If I have misunderstood your problem, sorry.
3 commentaires
saiful azrie
le 6 Août 2019
i did the same project, but i cannot find the problem like u before. can i know how to perform the problem?
Voir également
Catégories
En savoir plus sur Target Computer Setup dans Help Center et File Exchange
Produits
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!