Comfort Home Automation/ Security System Forums Home
Home Search search Menu menu Not logged in - Login | Register

UCM/ETH03 New Features
 Moderated by: admin Page:  First Page Previous Page  1  2  3  Next Page Last Page  
 New Topic   Reply   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Tuesday May 5th, 2015 06:21 am
   PM  Quote  Reply 
21st Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 4307
Status: 
Offline

  back to top

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



 Posted: Friday May 8th, 2015 12:25 am
   PM  Quote  Reply 
22nd Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 36
Status: 
Offline

  back to top

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.



 Posted: Friday May 8th, 2015 12:31 am
   PM  Quote  Reply 
23rd Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 543
Status: 
Offline

  back to top

Eth03 firmware is not the same as the UCM firmware, it should be 2.14 and needs to be upgraded using the CS Manager software.

http://www.cytech.biz/eth03_firmware.html



 Posted: Friday May 8th, 2015 02:00 am
   PM  Quote  Reply 
24th Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 36
Status: 
Offline

  back to top

Ah, I quoted the wrong firmware number. I updated the ETH03 firmware a few days ago to 2.14

Last edited on Friday May 8th, 2015 02:04 am by Craig Robins



 Posted: Friday May 8th, 2015 01:46 pm
   PM  Quote  Reply 
25th Post
admin
Administrator


Joined: Saturday Mar 3rd, 2007
Location: Singapore
Posts: 1203
Status: 
Offline

  back to top

Sorry my mistakeUpgrading the ETH03 firmware does not change Force arm to UnusedIt remains as Force arm



 Posted: Friday May 8th, 2015 10:19 pm
   PM  Quote  Reply 
26th Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

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

 

 

 

 

Attachment: Eventlog.clg (Downloaded 4 times)



 Posted: Saturday May 9th, 2015 06:18 am
   PM  Quote  Reply 
27th Post
admin
Administrator


Joined: Saturday Mar 3rd, 2007
Location: Singapore
Posts: 1203
Status: 
Offline

  back to top

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

Attachment: eventlog 20150509.clg (Downloaded 1 time)



 Posted: Saturday May 9th, 2015 11:51 am
   PM  Quote  Reply 
28th Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

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

 

 

Attachment: sntp.png (Downloaded 47 times)



 Posted: Saturday May 9th, 2015 11:56 am
   PM  Quote  Reply 
29th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 4307
Status: 
Offline

  back to top

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



 Posted: Saturday May 9th, 2015 12:02 pm
   PM  Quote  Reply 
30th Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

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

 

Attachment: 2015-05-09_09-02-08.png (Downloaded 44 times)



 Posted: Saturday May 9th, 2015 12:11 pm
   PM  Quote  Reply 
31st Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

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?

 

Attachment: 2015-05-09_09-08-41.png (Downloaded 40 times)



 Posted: Saturday May 9th, 2015 04:22 pm
   PM  Quote  Reply 
32nd Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 543
Status: 
Offline

  back to top

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.

09 May 2015


13: 19: 33: 961 ----< 03 00 9A 31 34 30 30 30 31 34 45 02 <--->/š1400014E
               broadcast for flag:14state is:00
14: 01: 26: 359 ----< 03 00 53 32 30 31 35 30 35 30 39 31 34 30 30 30 30 30 30 35 33 02 <--->/S201505091400000053
               Set date and time
 


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.

Ingo

 

 



 Posted: Saturday May 9th, 2015 05:16 pm
   PM  Quote  Reply 
33rd Post
admin
Administrator


Joined: Saturday Mar 3rd, 2007
Location: Singapore
Posts: 1203
Status: 
Offline

  back to top

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



 Posted: Saturday May 9th, 2015 06:33 pm
   PM  Quote  Reply 
34th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 543
Status: 
Offline

  back to top

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.



 Posted: Saturday May 9th, 2015 06:59 pm
   PM  Quote  Reply 
35th Post
HeFeng
Cytech


Joined: Saturday Dec 11th, 2010
Location:  
Posts: 29
Status: 
Offline

  back to top

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!)



 Posted: Saturday May 9th, 2015 08:08 pm
   PM  Quote  Reply 
36th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 543
Status: 
Offline

  back to top

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.

Last edited on Saturday May 9th, 2015 08:13 pm by Ingo



 Posted: Monday May 11th, 2015 04:34 pm
   PM  Quote  Reply 
37th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 543
Status: 
Offline

  back to top

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.

Ingo



 Posted: Monday May 11th, 2015 05:36 pm
   PM  Quote  Reply 
38th Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

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.

J

 



 Posted: Monday May 11th, 2015 05:47 pm
   PM  Quote  Reply 
39th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 4307
Status: 
Offline

  back to top

only reason I can think of is his clock is very inaccurate, out by more than 4 secs every 10 minutes 



 Posted: Monday May 11th, 2015 05:49 pm
   PM  Quote  Reply 
40th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 543
Status: 
Offline

  back to top

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.



 Current time is 08:58 amPage:  First Page Previous Page  1  2  3  Next Page Last Page  
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems