- Top Results
Clicking through the peripheral sequence can last a few minutes, but it saves you linking hundreds of PLC in-/outputs manually. The diagram shall help you if you don’t know what do. If you know what to do you can skip some steps:
Enhanced description:
- Install device descriptions
Only necessary if you want to add a bus device the first time on your laptop. - Read field bus from PLC IDE (without updating designators)
Only necessary if you have changed the bus configuration in the PLC editor.
If you just have renamed a bus device in the PLC editor use the last step instead of this one. - Write peripheral and IO designators to the PLC IDE
It updates the bus configuration in the PLC editor.
Only necessary if you did an EPLAN import or some renaming in Control plus Studio.
Renaming of peripheral designators is more efficient in the PLC editor, see last step. - Control plus Studio export
It exports the peripheral instances and the BinIo FB.
Only necessary if have changed anything in the bus like a new slave or renaming an IO. - Build PLC project
After a successful build the new PLC in-/outputs are available for linking with the bus.
Only necessary if have changed anything in the bus like a new slave or renaming an IO. - Link IO with variables in PLC IDE
It links the PLC in-/outputs with the bus device.
Only necessary if have changed anything in the bus like a new slave or renaming an IO.
You can shortcut this step in two ways, especially if you have added/changed only one or two devices:- Link the IO manually in the PLC editor.
- Since Control plus Studio 5.3 you can link only single bus devices:
- Read fieldbus config from PLC IDE only to update designators
Only necessary if you did a renaming of bus devices in the PLC editor.
When you double click on Peripherals and select the IO tab you can see all in-/outputs within a peripheral tree. Here you can move in-/outputs via drag and drop without losing object parameters.
Copying or cutting and pasting is also possible for several in-/outputs by multiple selection.
Since TwinCAT 3.1.4022 SFC actions can be "integrated" into a SFC step. That means the action is renamed automatically according to the step name and the whole action content is copied when copying a step.
This is a huge improvement when using numbered step names:
You must set the option "duplicate on copy" for each step. To apply this setting for new steps set the general TwinCAT options like in the screenshot:
Some remarks:
- "Integrated" actions automatically get the prefix "_a", e.g. _aN100_active. This is no problem for Control plus Studio V5, OES V4 or CodeChecker.
- Since Control plus Studio V5.0 the chain templates use the parameter "duplicate on copy".
- In TwinCAT 3.1.4022 renaming does not work automatically. Uncheck and check the checkbox "duplicate on copy". Since TwinCAT 3.1.4024 everything works automatically.
- As this is a CODESYS feature ctrlX also supports this option.
Contacting our helpdesk is most effective when using the email template out of Control plus Studio:
Alternatively use this forum to get in contact with the whole Control plus community.
Hopefully only your cycle time is „falling“, not the Christmas tree.
Always record and save a measurement with the Cycle Time Assist app during/after final acceptance. This will help you and the operator to identify deviations due to faster or slower movements or communication times later. Analysing and comparing can also be done in the office with Cycle Time Diagnosis.