Ethercat XI342204 Analog Inpu Module Error

[tomtw1]

Hello,

I've got an issue with the XI342204 Analog Input module. After configuring and restarting the Ctrl X PLC gives the error notifications below (see images) and seems to be starting in 'safe mode'. When I remove the module and only use or 'normal' digital i/o modules everything seems ok.

All apps are running on version 1.20. The Ctrl X is giving a red led after restarting. When i go to 'install an app' on the internet page and set the system in 'Service mode' to set it in 'Operation mode' again after that, everything works perfectly fine.

Anyone got any ideas what this issue could be? 

[Pinball_NL]

I have the same problem here (ctrlX 1.20).

When the module XI432204 is in the project. Everything works fine until reboot !!

After reboot the ctrlX I get the messages under and the system doesn't start.

(only way to get it up and runng is to go into service mode and back to operation)

When I remove the XI432204, everything works fine with/after reboot.

(the module is not connected to wiring yet)

[cc2go]

Hello,
can both of you please share each a system report, which includes an exception log and more details. Is with the analog IO any special function executed which may force the issue? (How to generate a system report and switch on additional traces [DOCU])

And a list/overview of the used EtherCAT devices.

[tomtw1]

Below a system report. Also a list of ethercat devices below: (note: this error was also present before adding the CTEU or YASKAWA Ethercat connection)

[Pinball_NL]

 Systemreport added. Even I had this error after creating the error/systemreport.

But please focus on the initial (First) problem entree of tomtw1 tomtw1

[georkueh · Accepted solution]

Hi

in any case you should update your software and apps to the current release 1.20 (RM 23.03.5), that is available by our collaboration room.

kind regards

[Pinball_NL]

Thank you, this solved the problem at my side, now we will do the same on the problemcase of Tomtw1 and see if it can be solved there too. Just hang on for a moment....

Thanks for hanging on.  Today we solved the issue at the other project too. Updated the apps in the project and no problem anymore.