About Jesse

Jesse · ‎04-04-2023

Thank you, Uwe. I will do that.

YUL725 · ‎03-22-2023

Hello Jesse, Usually the synchronisation error is because the drive is not in the correct state. Here it seems that the prolem is somewhere else. I would try to stick to the latest firmware. If S-0-0425 is the only problem then I would write this parameter and switch the system after successful writting on it with ImcCtrl. This is a workaround. I cannot reproduce the problem since I do not have the same Hardware. I would recommand to report this to your Bosch Rexoth local support. Hope this helps. Regards,

CodeShepherd · ‎03-17-2023

I talked to our R&D and there are two main reasons why you could get stuck in safe-op: IO data settings of the controller side must fit to the slave. When using a XM22 as controller scanning will find the correct IO structure. There are problems in the Scheduler settings. See Release notes for known ones and how to fix this.

CodeShepherd · ‎11-14-2022

@Jesse in your attached file you get the error message "CERT_NOT_YET_VALID". So it seems that time is still not correct.

nickH · ‎11-11-2022

Hi, I was not able to reproduce your error. I connected the ctrlX CORE to a free internet (not company controlled) and connected with my laptop to the ctrlX CORE and was able to download the palette "node-red-contrib-ui-led" you mentioned. I would suggest to look at the time settings of your ctrlX CORE, please check if your time is set correctly. The time has to match with the server time. This is also mentioned in the troubleshooting part of the node-red-contrib-ctrlx-automation. Best regards, Nick

About Jesse

Re: parameters in CtrlX drive are not saved

Re: XM 21 didn't get into BB on sercos with a ctrlX drive

Re: CtrlX core X3 profinet device transition in safe-op

Re: Download new palette in Node Red

Re: downloading a new dashboard node from palette manager of node-red into CtrlX