About SteffenR-

How do you parametrize the IndraDrive regarding Drive Halt?   If you use the red option, ParImm.Dec is used for deceleration (which could be too slow) and the command stays in ExecState RUNNING (with speed 0). If you use the green options, the Drive Halt acceleration (S-0-0372) is used for deceleration and the ExecState will change to ERROR (but I didn't test the combination with ParImm.Activate:=FALSE). For further diagnosis, the version of the base peripheral NexeedEcRxId is needed. There were several changes regarding reset (see VersionHistory.xml). ... View more

Please check the HMI log file on the target system: C:\OpconApp\HMI\Log\ Maybe it is the same problem like in this post? https://community.developer.bosch.com/t5/Control-plus/Problems-starting-the-Event-Recorder/m-p/73314#M732 Try to update everything related to the Event Recorder: Update the service: Update the app: Update the add-on:     ... View more

Thanks for the feedback. But why was the problem not solved by using  this function?   Unfortunately some vendors use a version number or date in the file name although this is not necessary (Rexroth, Balluff, Interroll, etc.). In the Control plus repository usually the original file names are kept. This causes the problem of multiple definitions of the same device: https://community.developer.bosch.com/t5/Knowledge-base/TwinSAFE-4020-error-Multiple-definitions-exist-for-the/ta-p/46781 In case of Rexroth IndraDrive the file name is manipulated in the peripheral NexeedEcRxIndraDrive V2.2: The file name says 01V18, but inside it is a 01V27: Therefore you should not get the error "multiple definitions", but you can get another problem in old projects because TwinSAFE now loads this new file even if the project was done with 01V18. The above mentioned function to install the device descriptions overwrites existing ESI files. After executing the function you should have the suitable ESI file. When working with a server, you will indeed get a problem as soon as two projects are opened at the same time, but they need different FSoE information (nevertheless if the ESI files have different names or the same name but different content). Hopefully Beckhoff introduces soon a TwinSAFE Remote Manager.   ... View more

Do you have any non-Beckhoff FSoE devices in your safety? Like Rexroth IndraDrive with FSoE, robot with FSoE etc. I didn't check it in detail, but last year I had something similar and it looks like TwinSAFE is working with the ESI files (EtherCAT XML files in C:\TwinCAT\3.1\Config\Io\EtherCAT ) on your laptop and does not save the ESI information inside the project. That means if you install new ESI files for new projects on your laptop, it can happen that you cannot edit old safety projects anymore. For normal EtherCAT slaves the ESI file on your laptop is used only once when adding the device to the bus/project. TwinCAT then saves the ESI information inside the project. Therefore everybody can open/edit the project although the ESI files are missing on the laptop.   Conclusion: Install the ESI files from the Std with this function and execute this function everytime you get an old project with TwinSAFE: If you have only Beckhoff devices in TwinSAFE, then it will be more difficult because the (old) Beckhoff ESI files are not included in the Std.   One day TwinSAFE will also get a Remote Manager functionality, then this problem should be solved ... ... View more