About AllAutomation

AllAutomation

Hello StefWi, since the SAFEX-C.1x products are not yet in General Sales state the access is controlled via Collaboration Room. To get there ... Click that link ctrlX AUTOMATION - Collaboration Rooms | Bosch Rexroth AG. A login-dialog is displayed. Either you have a Bosch ID already you can access the collaboration room and search for a directory called "ctrlX SAFETY". If you find it, you can enter the "SAFETY_Engineering-Apps" directory and download the provided versions of ctrlX SAFETY Engineering. If you don't find that, you do not have the necessary access rights. Please apply for them with your Bosch Rexroth Sales contact who will link your E-Mail address registered with your Bosch-ID through to the DC-AE/PRM product management. The responsible product manager will add your ctrlX SAFETY role within 24 hours. If you don't have a Bosch ID please use the login dialog and register for the Bosch-ID After that follow the above procedure Finally you arrive in the collaboration room, where you have access to two main sections: SAFETY_Runtime-Apps (say certified firmware releases, including relevant device description files) SAFETY_Engineering-Apps (ctrlX SAFETY Engineering releases) SAFETY_Templates are not filled, yet. HTH StefWi 😊 Best regards Your ctrlX SAFETY Team

AllAutomation

Hello CodeShepherd, you refer to a problem with a mismatch between ESI and data layer. This (Polygon's case) sounds or could be different. I'm not sure that it is related to ctrlX SAFETY but could be ctrlX PLC or CORE subject. Hello Polygon, can you please provide more detailed facts like ... Which versions of ctrlX CORE and SAFEX-C.1x (FW, change index on name plate) do you use? What state do you reach with EtherCAT (OP or less)? Can you provide the ctrlX I/O- and PLC-Engineering project? How did you get to this point? What did you do in which sequence? Did you try to start the whole configuration from scratch and what has been the result? Can we have a look at the situation on your system? Best regards ctrlX SAFETY Team

AllAutomation · ‎06-16-2022

Hello MST, now I understand. You see a mismatch between documentation and ctrlX SAFETY Engineering or the behaviour of the SAFEX-C.1x. You refer to the Program CRC. This is a remainder of earlier versions. It does not exist anymore. It will be removed from future documentations. There is only one CRC, the device config CRC! Your ctrlX SAFETY team

AllAutomation · ‎06-16-2022

Hello MST, besides inside the validation report, you can see the CRC first in the Compilation report directly after compilation (either explicitly or implicitly when connecting and uploading to the SAFEX-C): The Message Window - Compilation is stored in a file <configuration>.log in the directory where the configuration (*.spl2) is placed. It is another place where the offline CRC can be checked. You then want to compare it with the CRC inside the controller SAFEX-C.1x. As soon as you are connected to the SAFEX-C in the "Device" mode, you can switch the connection into state "Diagnosis". You get there another window called "Diagnostics" with various tabs. The tab "System Info" shows the Device Config CRC amongst other central information. Please mark this as "solution" if it helped to fix your problem! HTH Your ctrlX SAFETY team

AllAutomation · ‎06-15-2022

Hello Polygon, of course there is ... Go to the Mediadirectory and filter for "SAFEX" or just take the direct link. Soon there will be more. Lot of success! In case of questions, let us know! The ctrlX SAFETY team

About AllAutomation

Re: ctrlX SAFETY engineering

Re: ctrlX SAFETY C15 cyclic data not addable in ct...

Re: CRC checksum for Program validation

Re: CRC checksum for Program validation

Re: Error adding Safex C15 to ctrlX Core