01-11-2017, 10:02 PM
Before I could perform your test I had to temporarily downgrade to V2.20 so that the date would be wrong again. Having achieved that, I immediately reupgraded to V2.22.
I then did as you advised. As before, the date on the keypads changed but not on the eDLTs.
I noticed that I didn\'t have the latest firmware for the controller so I upgraded from V7.099 to V7.116. Unfortunately, that made no difference either.
To summarise where we are:
V2.20 I can manually change the date on both Comfort and the eDLTs to be correct but with SNTP enabled this will jump a day ahead on the next auto date/time update.
V2.22 I can manually change the date on Comfort only. Having SNTP enabled or disabled makes no difference.
I agree with you that it seems odd that a firmware update on the UCM/ETH03 should have this effect but I can only report what I am observing. Under V2.22, there is some interaction between the UCM and the controller which is preventing time updates on the eDLTs which wasn\'t the case with V2.20 or earlier.
I then did as you advised. As before, the date on the keypads changed but not on the eDLTs.
I noticed that I didn\'t have the latest firmware for the controller so I upgraded from V7.099 to V7.116. Unfortunately, that made no difference either.
To summarise where we are:
V2.20 I can manually change the date on both Comfort and the eDLTs to be correct but with SNTP enabled this will jump a day ahead on the next auto date/time update.
V2.22 I can manually change the date on Comfort only. Having SNTP enabled or disabled makes no difference.
I agree with you that it seems odd that a firmware update on the UCM/ETH03 should have this effect but I can only report what I am observing. Under V2.22, there is some interaction between the UCM and the controller which is preventing time updates on the eDLTs which wasn\'t the case with V2.20 or earlier.

