Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Comfigurator not updating time with UCM-ETH v.6.012
#1
Comfigurator not updating date and time with UCM-ETH v.6.012

Here is a curious finding.
In the course of upgrading firmware today on the comfort ultra II and associated slaves, I went to reset the date/time (which had reverted to December 2011)

Using Comfigurator 3.4.4, I tried to update the time and date: nothing happened (commands and responses did exchange in the UCM I/O monitor), the date/time did not change. The connection was through UCM-ETH v. 6.012

I have two UCM-ETH connected. One for iPhone, the other for a constant link with a PC.

So I tried using the second (older) UCM-ETH connection. Its an earlier OTP version v 5.092. Using comfigurator, it updated date and time without problems.

I have verified this finding by changing the date through keypad and trying various combinations of things using both UCMs.

Is this by design or a bug?
Reply
#2
We have not encountered this. It is noto by design
Can you turn on Monitor I/O before doing the date time update, then save and let us know what it contains?
Reply
#3
As requested -

Using UCM-ETH v6.012
> LI****
< LU01
> SR01
> DT20120519140450
< OK
> LI
< LU00

System date and time are NOT set

Using UCM-ETH v5.092


> LI****
< LU01
> SR01
> DT20120519140545
< OK
> LI
< OK
< LU00

System date and time ARE set.
Reply
#4
How did you know that date and time were not set in the 1st case? By seeing the keypad LCD? It looks like the command was accepted

After setting the date and time with ETH02, can you enter DT<ENTER> in the Monitor I/O  That command requests  the date and time from Comfort
Reply
#5
Q: \"How did you know that date and time were not set in the 1st case? By seeing the keypad LCD? \"

Yes. I changed the year first to 2011 at a keypad, then tried to update with comfig. Agreed it looks like the command was accepted, but no change at keypad.

I will try the test you suggest and revert.
Reply
#6
I changed the year to 2011 at the keypad.
I checked that it was returned by DT (line 2)
It was.
I ran comfig date & time update.
Command accepted.
BUT DT returns an unchanged date

The results of the DT test:
> DT
< DT2011051914530701
>
> SR01
> DT20120519145323
< OK
> LI
< LU00
> LI****
< LU01
> DT
< DT2011051914534101
Reply
#7
Thats very strange. We have not encountered this
What is the Comfort firmware version?
Can you disconnect the UCM 5.92 and see if the DT command works?
Reply
#8
Comfort firmware version 6.020.

When you say \"disconnect\" the UCM 5.92, apart from disconnecting it in the panel would I also have to upload a temporary cclx file without the UCM 5.92 module mentioned?
Reply
#9
The missing UCM will cause a Communications failure but this should not cause a problem if temporary
Reply
#10
Okay & thanks.
I will try, but probably not till mid week.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)