It\'s nothing to do with the hostname is it as noticed both LIVE and TEST rig UCMS set same to \"COMFORT\". changed the UCM/GE\'s now to distinguish but the UCM/HM\'s I\'d expect to now also change to ones they are pointing too but after reboot they are same; how do I get these to show COMTEST and COMLIVE respectively?
And here is my twist on all this. I set my PC to NTP time, set Comfort to be +-1 minute out from NTP time and then waited. I started to monitor at 13:19 and the Time Change came through at 14:01. Firstly it didn\'t come within the 10 minutes my Eth03 was configured for and secondly it didn\'t set Comfort time at all.
The time on Comfort is confirmed to be that same +-1 minute out even after the Time Change update. Looking at the event log I should see a time change event at 14:01 right? Nothing, nada, zip. No Date Time change in the event log even though the Bus monitor shows a Set command.
The Bus Monitor at 14:01 shows the time was changed to 14:00. This changes the time on Comfort
As the time change was less than 4 seconds, this is not reported to the UCM nor event log even though Comfort did change the time by 1 second
Hence on the next interval of 10 minutes, Comfort time should not be out by 4 seconds, and the ETH03 may make a small correction to the Comfort time again without reporting
This is why the event log should not be filled up by time change events, unless the crystal oscillator in Comfort is so inacurate that it is out by more than 4 seconds every 10 minutes
See that is the problem, doing a DT after the \'supposed\' change still shows Comfort to be out by +-1 minute. The change was logged but not actually implemented.
Hi,Ingo, when eth03 is used in comfigurator,it disable SNTP, SMTP and second port in case some problem happening when you are in the process of such as downloading firmware, bus monitor etc...if you still want to monitor the normal command, you can input \"LT00\" (can\'t use in bus monitor mode),actually you no need wait 10 minutes to see comfort time change or not, you just reboot the Eth03 in CSManager,then you will see comfort time change(after Eth03 reboot, it will report the NTP time for the first time!)
05-09-2015, 08:08 PM (This post was last modified: 05-09-2015, 08:13 PM by Ingo.)
Ok, that makes sense. How then does the below relate to your previous statement?
[17:58:52] > DT -> I check time here.
[17:58:52] < DT2015050917575000 -> Comfort out by +-1 minute, set manually earlier.
[18:01:01] < DT2015050918000000 -> This comes in probably from Eth03.
[18:04:40] > DT -> Checked time again.
[18:04:40] < DT2015050918033800 -> Boom!! Still not right.
I also used ComfortClient which doesn\'t block any ports/protocols.
And here comes another Set from Comfort. Two Set commands within minutes... weird but true.
[18:05:57] < OK
[18:05:57] < DT2015050918055700
This time it corrected the time. Now I am interested to see if there will be an update later and what the time will be.
After some testing I don\'t get Julian\'s amount of DateTime changes in my eventlog and when factoring out the Comfigurator \'features\' it all seems to work pretty well.
Here is my setup:
Comfort with Eth03 connected to local timesource. ComfortClient connected to same timesource. TimeChange events monitored in PC Eventlog and also Comfort eventlog.
Every 10 minutes I get a Time Update message from the Eth03. I then correlate this back to CC to confirm when it was sent and it\'s always within the same second or next of the correct time. Comfort keeps time fairly accurately and at no time did I notice any kind of drift.
The only thing is the dreaded \'Ok\' message every 10minutes but the Eventlog is clear of any DateTime changes when used as per my testbed setup.
Perhaps more investigation is required to find the source of Julian\'s eventlog entries.
Mine too has only logged 1 DT change since I un-ticked the \"Send to Comfort\" checkbox on the Eth3. Now I guess the challenge is to re-tick and see if they all start flooding in again.
Don\'t get me wrong, my \'Send to Comfort\' is Enabled. I did press Submit again just to be sure since these settings haven\'t changed from the introduction of this feature. I thought it best to start with a clean slate when I did my testing. I have my CC set to 10s before it changes the time so the Eth03 is the Time Master between these two and will set the time when it\'s 4s out.
