@cechurat Hi,
it works with the settings see below. I think there will be a problem in the provider and access to the SMTP server. It's still working with "seznam.cz".
Best regards
Michal

@reitinge Hi Jan,
I continuously monitor the system log. None of the errors (49 52, 51 49, 49 50 or 52 51) that I solved last time have come. Errors still occur 52 51. I replaced one of the 1-wire sensors that oscillated the most, so there are fewer errors, about 10 errors a day (see below).
It would not be bad if the system log could list the REXLANG error even with the pin where the errors occur. This would make it easier to find out which sensor has the most errors.
Best regards
Michal

@reitinge Hi,
I have currently 6x 1-wire sensors connected. Each sensor is connected separately to Arduino pins 26 to 31. I increased the task period from 1s to 2s. I did that on September 22nd. Today came a new communication error, see the picture below. The serial line dropped out for a moment. Communication resumed immediately. New fault codes have appeared in the system log.
What could have caused it?
Thanks.
Michal

@reitinge Hi,
error 52 51 occurs continuously, see below. I only record "peak" in the graph occasionally, because I archive the data every minute, see the graph below.
Michal

@mtomek Hi,
after three weeks, without a communication problem, the communication error came again. The communication error came exactly after the "peak" of the 1-wire Tsolar measurement (see graph below). The "comm_status" of FB Arduino_MEGA2560hex changes from 0 to 1 (0: Arduino not responding, waiting for timeout to try again, 1: Serial port open, trying to initialize communication).
I still get 1-wire measurement errors in System Log ...

This communication error has not yet occurred. Could it be related to that "peak" of measurement?

Thanks.
Best regards
Michal

@reitinge Hi,
it isn´t related to the previous problem. This was solved by deploying the latest version of FB Arduino_MEGA2560hex and the latest library.
But, during panel repairs, I accidentally found out that I have a broken USB cable between the RaspberryPI and ArduinoMEGA. This error did not recur after replacing the cable. So I will hope that this was the problem.
Michal

@reitinge Hi,
I will definitely analyze all outgoing and incoming data into the REXYGEN protocol system as you wrote. Then I'll let you know.

However, at the last communication failure, the states of the communication variables of FB Arduino_MEGA2560hex were as follows (comm_status = 3, err_code = 57, err_subcode = 57). These values have not changed.
The system log had the following errors:

Is it possible to find out what the problem is from this system log listing?

Thanks.
Best regards
Michal

Hi,
I have another big problem with communication between Raspberry PI and ArduinoMEGA. I solved the previous communication problem, see HERE.
I still use REXYGEN 2.50.10.12932, Arduino IDE 1.8.12 and REXduino master / slave version 2.2.0.
Sometimes the communication between Raspberry PI and ArduinoMEGA fails. No data comes from or to ArduinoMEGA (measurement doesn´t change, nothing can be controlled), data remains in the last state.
Communication status FB Arduino_MEGA2560hex, comm_status = 3, but the status LEDs Tx and Rx Arduino_MEGA don´t flash.
So REXcore on Raspberry PI is still running, but the data from and to Arduino_MEGA isn´t going.
According to the manual "REXduino_User_Guide.pdf" I tried to send the message c2 in the Arduino IDE, through the serial monitor. The E11 answer came back to me, but correct answer is c2.

So could it be a problem? How to solve it?

Thank you very much.
Best regards.
Michal

@reitinge Hi Jan,
I had downloaded the latest version 2.2.0 of the Rexduino library. The problem was that I only replaced the REXduino_master.c library, but I forgot replace the REXduino_library.mdl library. So I have an old function block left in the project.
Now the error didn´t appear.
Thank you so much for the solution.
Best regards
Michal

@reitinge Hi Jan,
I don't use the userSend input of block Arduino_MEGA2560Hex.
Thanks.
Michal