About CodeWasi

CodeWasi · ‎02-21-2022

Hello ! I assume you did not succeed in meantime. Do you mind to save the data operating via the "save Configuration/Solution" part. If you update via the image1.12.7 you can upload the config and try to activate. Bye Jens

CodeWasi · ‎01-10-2022

Hello, could you please point out in detail what happend? Wonder if I get the message correct. Assuming you made a factory-reset using the uSD with the RM2111 Image to refresh the system. After that, the system was on RM21_11 level and the reboot and state switching worked fine, right? What happend next? Did you only load apps fitting to RM21_11? Just ones labeled with 1_12 instead of the RM2107related 1_10 versions? Which app-handling is related to the trouble? Did you operate with configurations based on old RM2107 ? Please return with further details. Bye!

CodeWasi · ‎12-14-2021

Its quite easy to operate the RESTORE fct provided in the BACKUP API using the Web-UI or the Swagger side. The option like filename, sync/async, password-option etc is easy to choose. Postman for instance operates the API as well successful. I would really appreciate if somebody could leave a hint on how to organise payload, header and especially the file-info to post correctly. Thanks!

CodeWasi · ‎12-06-2021

Fix is not released yet - available soon, but in meantime please consider the following workaround: Fact: ctrlX-IOEngineering (released by RM21_11) does not support the configuration of a few modular slave. Identified devices : ● ctrlX SAFETY ● ifm AL1x3x (e.g. ifm AL1930) but potentially others might be affected. What does the malfunction look like? E.g. running "Scan for device" - will not identify the affected slaves correctly ( Unknown device... ). Workaround : Import into the ctrlX-IOEngineering (RM2111) the projectarchive which was created with former (RM2107) version. Verify that the related device-data is included in the projectarchive file. Save and extract examplarily like below. In case the WorksVersions are not available (anymore) - the collaboration-room still offers RM2107-Works and installing in parallel is recommended (choose 'New Installation' instead of 'Update-I.') The workaround does not require any changes to the ctrlX environment (Apps etc stays the same). Please note that the behaviour is documented in the release-notes of RM2111 already. Further details available in chapter 3.3.2 ctrlX IO Engineering

CodeWasi · ‎10-08-2021

Hello Engi, did you note that the task-schedule sets the PLC-freecycling task with a higher prio and and the same periodtiming than the automation-task which includes the ecat-com etc. ? Please have a look to the attachments? Could you please check. Bye Jens

About CodeWasi

Re: ctrlX CORE backup error

Re: ctrlX Core keeps rebooting after installing an app (v1.12)

Python post prequest can trigger the REST-API Restore function similiar to other clients -...

Interims handling regarding RM2111 ctrlX-IOEngineering effects on modular ECAT slaves

Re: Task Watchdog error