by hvxl » Sun Feb 25, 2018 1:33 pm
You really are intent on making it as hard as possible for people to help you, aren't you? Along with the OTGW I made the otmonitor application, primarily to get a well-defined log when people have problems. But you decided to use some other method to create a log, so that it would be unclear to me what is and isn't logged, and it doesn't decode the messages. With your logging method you thought a nice additional complication would be to use an inconsistent number of digits for the parts of your timestamp. Then finally you considered what would be the least convenient format to provide the data in and came up with PDF, which indeed is much more difficult to automatically process than a plain text file.
After conquering all the obstacles you put up, it turns out there really aren't any jumps. The temperature is steadily changing over several minutes. In the log of what you call "jump up" you didn't include much history to really see what's going on, but you can just see that the thermostat has instructed the boiler to produce heating. As a result the temperature is going up. Nothing unusual. You only seem to have quite a bit of overshoot. But the OTGW is basically just passing on the messages between the thermostat and the boiler, without making any modifications. The only exceptions are messages with ID 16 and 18, so the OTGW does provide the current time and an override setpoint to the thermostat. I don't see the SC commands, which clearly must have been issued, so I guess your logging tool fails to record commands.
Your "jump down" log shows absolutely nothing strange. Sure, the temperature is going down over a period of time. But that's exactly what the thermostat reports. Again your log is too short to see what led up to this. But it shows no evidence that the OTGW is interfering with the communication between the thermostat and the boiler in any way.
Schelte
