I have an OEM customer who has recently upgraded an End-user machine from Sercans1 to Sercans2 (3SCS04-A04 with FWA-SERC*2-SCM-01V14-D0) . They use this card to talk with Generation 1 Indradrive which are running FWA-INDRV*-MPH-07S27.02-D5-1-SRV-NN.

The OEM customer is unable to read Parameter P-0-3213 Safety Technology Operating Status from the connected slave devices since the upgrade. this functioned perfectly OK in the Sercans1 hardware and firmware.

The ctrlX PLC Engineering provides a powerful Python programming interface (Script Engine). This allows you to automate menu commands, as well as create and edit source code.

While the official CODESYS help page (CODESYS Scripting - Starting Scripts from Toolbars) explains how to integrate these scripts into the standard CODESYS environment, users of ctrlX WORKS face a challenge: The directory structure and paths of ctrlX PLC- Engineering are different.

ctrlX PLC Engineering searches for the script configuration in two locations:

• ctrlX PLC Engineering AppData directory (version-independent)

• ctrlX PLC Engineering installation directory (version-specific)

Prerequisites & Locating the Path

ctrlX PLC Engineering AppData directory

If multiple versions of ctrlX PLC Engineering are installed, they all load the script configuration. Replace <user> by your username.

C:\Users\<user>\AppData\Local\ctrlX PLC Engineering\Script Commands

ctrlX PLC Engineering installation directory

Only the ctrlX PLC Engineering version into whose directory structure the script configuration has been copied reads it in.

The default installation directory is usually: C:\Program Files\ctrlX WORKS\ctrlX PLC Engineering\<Version-Number>

Tip for easily finding the path:

1. Right-click the desktop shortcut for ctrlX PLC Engineering and open its Properties.

2. Look at the path in the "Start in" field (e.g., "C:\Program Files\ctrlX WORKS\ctrlX PLC Engineering\3.6.3\Studio\Common").

3. Ignore the last two directories (\Studio\Common). The relevant base path for the next steps in this example is:
   "C:\Program Files\ctrlX WORKS\ctrlX PLC Engineering\3.6.3"

Install example files

Step-by-Step Guide

Step 1: Create one of the directories mentioned above.

Note: Creating this folder and copying files into it later might require administrator privileges.

Step 2: Extract and Copy the Sample Files

Extract the ZIP archive (Commands.zip) and copy all the included files directly into the newly created "Scripts Commands" directory.

The ZIP archive contain the following files:

• icon-a.ico (Icon for toolbar button of Script A)

• icon-b.ico (Icon for toolbar button of Script B)

• script-a.py (Your Python script A)

• script-b.py (Your Python script B)

• config.json (The configuration file for the menu integration)

Configuration File Structure (config.json)

This file controls how ctrlX PLC Engineering reads the scripts and displays them in the user interface. The table below shows the structure of the file and explains each parameter:

Copy

[
 {
  "Name": "hello world A",
  "Desc": "description python test",
  "Icon": "icon-a.ico",
  "Path": "script-a.py"
 },
 {
  "Name": "hello world B",
  "Desc": "description python test",
  "Icon": "icon-b.ico",
  "Path": "script-b.py"
 }
]

1. "Name" is display as tooltip

2. "Desc" description of the script not yet displayed

3. "Icon" name of the icon file

4. "Path" name of the script file

   Verifying the Integration

Once the files are placed in the folder, they will be loaded automatically the next time you start ctrlX PLC Engineering. Follow these steps to verify that everything was imported correctly:

1. Start ctrlX PLC Engineering.

2. In the menu, navigate to Tools > Customize > Command Icons.

3. Select the category ScriptEngine Commands from the list.

Your configured scripts (e.g., hello world A and hello world B) should now be listed here with their assigned icons.

Now you can add the scripts to a new or an existing toolbar.

Related links

• ctrlX PLC Engineering

• (external) CODESYS Scripting

It's impossible to configure the I/O settings and the system says also that I have to check parameter S-0-1032.0.144

But If I check that parameter I get : IDN Not available.

Drive is brand new and delivered with Firmware AXS 06V10

We have a customer that does not use the P1 and P2 signals, therefore the Q0.6 and Q0.7 outputs are free,

We saw in the ctrlX Safety Engineering that we can configure an output in these pins

However in the wiring is not wired and therefore we have an error when we compile

So, can we use these outputs? If so, how can we do it?

Many thanks,

Following the obsolescence of the MLC L75 and HCS0.2, we now have an XM42 and ctrlX Drive architecture using Sercos III.

With our previous architecture, we used the TouchProbe function, which was directly connected to the onboard inputs of the MLC. Since the XM42 does not have any physical inputs, we decided to connect the TouchProbe function to the drive instead.

I have already configured the TouchProbe function on the drive using the tutorial available on the forum.

However, I am now wondering how to retrieve the TouchProbe position and counter information.

In the example available on the ctrlX forum, the application is based on ctrlX PLC Engineering with EtherCAT. In my case, I am using IndraWorks Engineering 15V22 with Sercos III.

The function blocks used in the example do not seem to be available in IW Engineering 15V22.

Could anyone help me understand how I can retrieve the TouchProbe position and counter information in an XM42 + ctrlX Drive + Sercos III architecture using IndraWorks Engineering?

Thank you in advance for your help.
Hasan

Indraworks ML 15V22P1.

generate certificate, all works fine from Winstudio. Simulation works well. When send the files the VR2109 it does not communicate with CtrlX.

I tested same procedure with VEP15 and that works well.

VR2109 for some reason does not seem to connect. I dont see any reject certificate from CtrlX.

Tried also to change Machine Name to VR2109 and Compact, none of them work either.

I used this as reference:  

https://community.boschrexroth.com/communication-5ojipb0n/post/ctrlx-core---opc-ua-server-app-potentially-not-compatible-with-winstudio-9oEKXChBNfYpa7a

 Any suggestions will be appreciated.

A customer is using IWS 14V22 P12, the project itself is correct for running project for a longtime, but recently they are not able to open the OPC-UA sheets by IWS14V22P12 after installed IWS15V24P1.

Is there any solution to fix it?

Regards

Marco

Could anyone help me guide how to get these files.