Question 1: I'm not familiar with the details of these OES versions, but what probably happened is that the station was done with an older version of OES. In that version the extension didn't recveive the model tree struct references, but in OES4.8.5 they do. If you want to change this then you need to override the default export template. I haven't tested but this feature should be available in OES4.8.5 (I think it was already in OES3). To do that, first select a template folder. This has to be done here: I have only seen the STD used for this but you could also use a folder inside the station. Inside this folder you need to put the new template with the same folder structure and name like in your OES installation. The file you want to change is in <Default OES installation path>\OpCon\Templates\_Common\UnitOnApplyParameters.otd. For me the correct path with the standard installation is C:\Program Files (x86)\OpCon\OES V4.8\OpCon\Templates\_Common\UnitOnApplyParameters.otd. Copy this file and put it into your template folder, for example when using the path in the screenshot, it needs to go into Std\Templates\_Common\UnitOnApplyParameters.otd. Now OES will use this file for export instead of the one in your OES installation folder. So you can modify it and make it skip the extension export. I looked at the file and it's the lines 219 and 226 you want to delete I think (I haven't tested this!) Question 2: I think this is not possible. Model tree struct variables are only distributed to child units (and their extensions, unless you do Q1 solution) and to chains, but not to add-ons. Just manually add the references in TwinCAT, that's what I would do. Although you don't get much benefit from this over using the global variable directly, judging by the screenshots.
... View more
