Judging from your question, you are not so familiar with how objects work, yet. The LCT coupler may look almost the same as the Beckhoff EK1100 but it is not, internally. Trying to use the same peripheral is probably going to fail, and even if it works for the EK1100 coupler then you will probably run into problems with the terminals that you are trying to use. But to answer your question about the RefId: Each object (and also peripheral) has its own unique RefId that the creator of the object is setting once when they start creating the object. The BCI objects take the RefIds from a predefined range, or used to do that up until some recent point at least (not sure if they continue this practice or not). So if you create your own peripheral, you need to create your own RefId for it. The RefLink you marked in the second box refers to the RefId of another object, the NxEcSlave in this case. If you open the .ood of that object, you will find its RefId is identical to the one in the RefLink of the EK1100 .ood file. In the case of bus peripherals, the id in the DeviceType element is also important. This tells OES which peripheral to use when you are reading the IOs from TwinCAT. You cannot use the Beckhoff EK1100 peripheral for your LCT coupler, because the Beckhoff EK1100 and the LCT coupler have different DeviceTypes ids. Note: I sometimes use the word object also for peripherals, because much of the logic in the .ood and accompanying files is the same for both.
... View more