Simulink Real-Time R2020b and later - setting up non-Speedgoat machines

Hello,

I'm working on a real-time application that involves code generation and communication of the target machine with the development computer and another computer for simulations.

The target machine works quite fine with R2020a and previous releases with slrt, but apparently support has been dropped after R2020b with slrealtime. I've set up FreeDOS on the target machine and configured it to run Simulink Real-Time just fine for slrt, and it ran quite well without issues. For the current release R2021a, Simulink just rejects to connect to the target machine even though I'm able to properly ping it, and haven't changed anything on the target machine. The code generation also runs fine on its own, when I'm not trying to upload its output to the target, for both versions, however UDP management on the target appears to be severely restricted in slrealtime compared to slrt.

After some digging through the documentation and the new interface, I've noticed that there is no visible kernel generation for standalone runs in the newer version. Since the .tlc file has changed as well, it I think the necessary standalone execution resources have changed, and currently there is no visible method to create those.

Is there a way to generate the relevant rttboot, autoexec and kernel files with the new release, or a way to acquire them for a first-time setup? Am I supposed to buy a Speedgoat target and throw the target machine I currently have (which works perfectly fine) away for futureproofing?

Answer 1

[Diego Kuratli]

R2020b introduced a major update for Simulink Real-Time. The RTOS has been replaced. Here you can find more information:

https://www.mathworks.com/products/simulink-real-time/r2020b-update.html

Simulink Real-Time requires Speedgoat hardware to enable latest features and integration with MATLAB/Simulink for rapid control prototyping and hardware-in-the-loop simulation. Third-party hardware is no longer supported, but you may continue to use your target computer with R2020a and previous releases.

[Atakan Botasun]

Is it possible to work around this by a kernel file, or has MathWorks deliberately locked out other hardware out of this ecosystem? From the word "support" I am inferring the meaning that using other hardware isn't easy and there will be no particular solution for other systems, so I would need to work hard on it to find a solution. From the phrase "require" specific hardware I feel like the latter case is what is going on here. I may try to use a Speedgoat of course, but I don't have one. And the device I currently have would be then useless in the future, as other pre-R2020b applications become deprecated, or essential post-R2020b applications become incompatible with my device.

So the actual question here is this: "Do/can you provide a kernel file for the new Simulink Real-Time add-on, or the means to produce one for non-Speedgoat targets post-R2020b?". If the answer is clearly no, presumably due to some business that MathWorks has with Speedgoat, I will accept the answer and move on with that. If the answer is yes, please provide the solution to this problem.

Thanks, and have a nice day.

[Diego Kuratli]

No, we can't provide a kernel file. The RTOS is natively installed on Speedgoat target computers, and we do not support any other hardware vendor.

I would recommend to reach out to Speedgoat to discuss options:

https://www.speedgoat.com/company/contact-us