The alarm types are fixed by the ETH03 firmware
Alarm Type 23 has been changed to Unused in the latest ETH03 firmware where it was previously \"Force arm\" If you upgrade your eth03 firmeware it will then show Unused
I sugest that you upgrade the firmware not because of the Unused alarm name but bvecause of other features
Your email will still work but the alarm name will show as \"Unused\" but you will still know what is the meaning
We do not have a way yet of changing the alarm name in the email
I had already upgraded the ETH03 firmware to 7.061 which Comfigurator says is the latest and I still get the \'Force Arm\' reported in the email.
Ah, I quoted the wrong firmware number. I updated the ETH03 firmware a few days ago to 2.14
Sorry my mistakeUpgrading the ETH03 firmware does not change Force arm to UnusedIt remains as Force arm
Maybe it\'s just me but does anybody else think this is absolutely ridiculous?
600 possible entries in the event log.
- 10 real entries
- 590 Datetime changes
What is going on Cytech? I\'ll attach my event log for your viewing pleasure! :?
Julian
That should not be the caseSe my event log - there are very few date/time changes events
The time change is recorded in the event log only if the difference is 4 seconds or more
Try disabling the time update and check what the time accuracy is over 1 day
So it seems to have stopped now I\'ve unchecked the box.
When that box is checked I assume the Eth3 talks directly to the UCM and then Comfort right. Nothing broadcast to Comforts or something like that over Ethernet/UDP is there?
Reason asking is I have 2 Comforts (one is test rig). Both Eth3\'s were ticked to report back time to Comfort. My test rig one showed +1 instead or +0 as the offset as I only just switched it on again in the last few days. There\'s no chance they are both trying to update the same Comfort is there and fighting each other; surely they\'d update their own Comforts via RS434 comms only! Just trying to make sense of it all.
Anyway unchecked both of them now, cleared the log, synced time from Comfigurator and haven\'t seen any more so far!
Screenshot of my original settings attached.
Ju
Each UCM/ETH03 updates its own comfort time via RS485, it will not affect another system
make sure both systems have the latest firmware for Comfort, UCM and eth03 as there were changes to updating time for daylight saving and update of event log when the time differentce is at least 4 seconds
Both UCM\'s (in LIVE and TEST rigs) are on 7.061.
Eth3\'s as below.
Don\'t think I can go any later than these.
Ju