(TE1410) TwinCAT 3 – Matlab App communication issue

Dear Matlab or Beckhoff community,

I’m facing some difficulties with the features provided by the license TE1410 of TwinCAT. This problem is illustrated step by step in the pdf attached to this question.

In a nutshell, my issue is that the simple functionalities of TE1410 work when I’m on the development area of Matlab (e.g. the app designer), but when I build an app nothing work anymore.

Source of the PB: I know it is related to the fact that built apps use the matlab runtime compiler (MRC), which is not the compiler used in the development space of Matlab. Let’s call the later compiler “development compiler” (DC). To create the link between TwinCAT and DC I had to run a setup file “SetupTE14xx.p”, which (I guess) parametrize DC so that it knows what functions like “TwinCAT.ADS.Port()” are. I have tried several things to do something similar on the MRC, but nothing worked. So if you know what I should do, I would be very grateful if you would share it with me.

Toy program: Finally, attached to this message there is a very simple toy problem (one button calling one TE1410 function: “TwinCAT.ADS.Port()”). If you find a way to deploy this app and make it work outside of the development environment of Matlab (DC), then please tell me how you did it => that would really help me. (To make this code run on your computer you would need to have TwinCAT with an activated TE1410 license -- Also, it has been coded on Matlab 2022a)

Kind regards,

Aris

[chrisw23]

The TWIN Cat Doc says that for runtime execution TwinCAT 3 XAR needs to be installed. Is this requirement fullfilled ?

BTW There's no MRC , but MCR which is the Matlab Compiler Runtime environment.

[Aris]

Hi Chrisw23,

Thank you for your help! TwinCAT 3 XAR is installed on my computer. There is the twincat icone on the bottom right of my screen which color changes depending on the mode of my system, i.e. blue/green.

You are right, it 's MCR, not MRC. Thanks for correcting this mistake of mine.

[chrisw23]

try to check the runtime license state

(read the Notes) local working copy of the license file