Thank you in advance.

I’m trying to access the Datalayer on my Core X3 from Node-RED and pass arguments with the request. I’d like to recreate the setup shown in the picture in Node-RED.

In Node-RED, I’ve connected a Timestamp node, a Function node, and a READ_WITH_ARG node in sequence. However, I haven’t been able to determine the correct format for the arguments, and my request keeps failing.

Could someone please explain how the arguments need to be formatted to recreate the setup in the first picture?

For now, I’m not concerned that the returned data is undefined; receiving a response would be enough to get started.

Thanks in advance!

What is the recommended method to back up the editable PLC source code for a ctrlX CORE?

I would like to ensure that if the engineering PC/project is lost, another engineer can recover the PLC project and open/edit it again using ctrlX PLC Engineering.

Does the ctrlX CORE system backup contain the PLC source project, or do we need to create and maintain a separate PLC project archive? using memory card ?

Also, is there a way to upload the complete PLC source/project directly from the ctrlX CORE?

Thanks for your advice.

I am currently working on implementing the Recipe Manager on the ctrlX CORE. I followed the tutorial provided by Jordi Laboria: : ctrlX Core – How to use the Recipes system. Most of the functions work as expected, but I am experiencing an issue with recipe deletion.

To illustrate the problem, I would like to present the following example:

1. I have two recipes in my PLC:

2. I use the IL_FileDeleteAsync function to delete the recipe file I want to remove. This function is recommended in the tutorial instead of DeleteRecipe, but I also tried using DeleteRecipe and obtained the same result.

   The function completes successfully with the Done status, and the recipe file BaseRecipe1.Recipes.txtrecipes is indeed deleted. It no longer appears in the controller's file system.

3. My goal is to retrieve the recipes stored on the PLC so that I can use them on an HMI. I want to retrieve all the recipe names into a string array and allow the operator to select and load the desired recipe. To retrieve the names of the stored recipes, I use the GetRecipeNames function.

Before writing to my array, I make sure to clear its contents using a FOR loop.

After resetting the array:

I execute the GetRecipeNames function, but the deleted recipe still appears in my array, even though the corresponding file no longer exists in the controller's file system.

How is it possible that the GetRecipeNames function returns a recipe name that no longer exists on the controller?

PLC Enginnering version : 4.6.3

PLC App version : 4.6.4

Please find my code attached as a .txt file.

Thank for your support !

Hasan.

I have 2 separate drive applications at an OEM customer in the UK that have seen diagnostic F8304 be generated by the SMO safety system.

The first occurrence was at a HMS01.1N-W0210-A-07-NNNN running a MBS202D motor and using Heidenhain Incremental encoder. Firmware would be MPB20V32 with SRV extension.

This issue occurred in standard production with the drive at Ab status

The second occurrence was at a HMD01.1N-W0036-A-07-NNNN running 2 off MS2N06 motors with CM encoders. Firmware would be MPM20V32 with SRV extension.

This issue occurred in standard production with the drive at PA status

In both cases rebooting the drive cleared the issue.

Which steps can be checked around both systems to determine the cause of the issues?

If I'm using a ctrlX Core PLC (M5) and I need two HMI's running on the line with the same application (1 in front and 1 in back of the machine) I need 2 of WebIq (SWL-W-XC*-WIQ**RUD*001K**-NNNN)? or is enough only one and I can run from 2 hmi devices?

Could you please let me know if there is an explosion-proof gearbox available for the MS2E motor?
We need a gearbox suitable for Zone 2 / Zone 22 hazardous areas.

If available, could you please recommend a suitable model?

Kirikiman

see system report.

1. Intro

2. Prerequisite

3. Sign parameter file with ctrlX DRIVE Engineering (Offline signing)

4. Download of a signed parameter file

5. Good to know

Intro

With AXS-V-0702 and "Drive level" as mitigation strategy, it is only possible to load signed parameter files as end user (user role 4) per default. The file must be signed using the same "Admin" password as present in the drive it is intended to be load to.

Using this functionality ensures that only unmanipulated parameter files signed with the administrator password can be loaded to a drive. Unsigned parameter files will be ignored by the drive.

To sign a parameter file, you can:

• use the signing tool within ctrlX DRIVE Engineering to sign an unsigned parameter file (offline signing)

Prerequisite

• ctrlX DRIVE Engineering 01V44 (recommended)

• Runtime >= AXS-V-0702

Configure the drive correctly to enable security control "signed parameter files":

Select mitigation strategy „Drive level“!

Activate password protection and change "Admin" password

Allow „Load and activate parameter file via TFTP” for end user (user role 4). This enables the end user to load signed parameter files via TFTP (file based). Also other user level can have this permission.

Sign parameter file with ctrlX DRIVE Engineering (Offline signing)

To download a parameter file via TFTP to a drive with active security (with selected "Drive level" mitigation), one needs to sign the file in advance.

Open "Sign file..." dialog

Select the parameter file you want to sign!

Enter "Admin" password to sign the file!

Signed file (with name extension *_signed.par) will be stored in the same directory as the original file.

Download of a signed parameter file

When downloading a signed file via TFTP, the drive will check the signature before activating the file.

ctrlX DRIVE Engineering 01V44 and later will use the file based parameter download per default

If the file is not signed or signed with wrong signature, the drive will ignore the file with an error message.

Good to know

If you are unable to use TFTP in your environment or there are other reasons why you can not use file based parameter download, you can deactivate the file based parameter download.

The parameter file will then be downloaded using individual parameter write access, as in previous versions of ctrlX DRIVE Engineering.

Setting can be changed in menu Tools>Options: