Error that causes the Controller to switch to Serv mode

Hello,

We encounter a problem at our lab machine that once a day the Controller switches to service mode.

As advised in this community, I have added the IecCheck library, but the system logger afterwards has no extra information.

Is it definitely a logical error or it can be related to HW issue(I have already switched the Module supervised setting configuration to off)?
Is it possible to read the backtrace info and relate it to the specific program that caused this?
Can anyone advice how I can get to the root cause of this Error ?

With best regards,
Evgeni Kecher

Hi,

have a look into this post, please:

1 Like

Agree with Christoph, focus on task with FileIO libary and check string operation, memory operation or accessing array

++ the time is wrong. The battery may be missing and your machine configuration may also be incorrect.

As advised in this community, I have already added the IecCheck library but the system logger afterwards has no extra information.
No lines in the backtrace with a green arrow next to them(as appears in the screenshot attached).

We have about a hundred cyclic programs → moving some of them out and inspect this error may not produce the Error because the functionality of the machine will not work.

Please advise.

First of all, you should set the time correctly so that the order of the entries is correct.

Then you could use the ArEventLog library to create an entry for each program so that you know in which program the error occurred.

There may also be a profiler recording that tells us this.

You may be feeding function modules from the libraries with faulty pointers, in which case there is no backtrace.

Unfortunately, searching for such errors can be very complex and time consuming, so it may be better to contact a local B&R office.

Hello,

Here is a Thread in the Community how to use the Profiler for such an analysis, if the default Profiler does not contain enought data.
How to use Profiler

Checking the newest Versions of Software-Components in the Project can be also a good idea. In rare cases there are issues which got fixed in newer Versions.

And at the end, just go the hard way of an software review. In cases all other Diagnostics will not help and the error can’t be encircled.

Greetings Michael

1 Like

Hi @evgeni.kecher Evgeni,

It looks like you got some good suggestions from multiple users here, and it has been a couple of weeks since the last activity on this post. If the answers helped you with your question, can you help the next person with the same question by marking the solution on the information which helped you the most. If you still have open questions on this topic, can you provide an update?

Hi,

Thank you very much for the answers.

Regarding the wrong time logs, currently the time zone setting in the PLC configuration is set to GMT but the time is wrong. How can I check and set the correct system time (PLC: 5APC2100_BY01_000)?

Regarding the profiler, “Continuous recording” means that once the PLC is in run mode it is being overridden Continuously but once the PLC will switch to SERV mode(the problem we face occasionally) the last profiler will remain?

regarding “update all hardware module versions”, will it update the FW version that is supported by the currently installed Automation studio(4.9.2.046) of all devices on the machine? this update might require me to update the Automation studio or automation runtime(B4.73) or any other action accordingly?

With best regards,
Evgeni Kecher

Hi,

Regarding the wrong time logs, currently the time zone setting in the PLC configuration is set to GMT but the time is wrong. How can I check and set the correct system time (PLC: 5APC2100_BY01_000)?

There are several options. The simplest thing will be to use AS for this:

image

A battery must be installed to maintain the time even after a power fail.

it just means the profiler will continously run (= ring buffer) until it is stopped. When PLC enters SERV all actions will stop anyway. Unfortunately the memory preserved for profiling set by default configuration is often to small so you should increase that. To save the new configuration it has to be transferred to ‘USRROM’

image