| Posted: Thursday Sep 1st, 2011 03:03 pm |
|
21st Post |
| Posted: Tuesday Sep 13th, 2011 04:08 pm |
|
22nd Post |
Ingo
UCM Pi Users
| Joined: | Sunday Jan 21st, 2007 |
| Location: | South Africa |
| Posts: | 562 |
| Status: |
Offline
|
back to top
|
I just got home to find my Comfort system yet again not 'seeing' any Cbus counter updates. A quick check confirmed commands from Comfort to Cbus goes through but nothing coming back from Cbus to Comfort. I am going to leave it untill tomorrow morning to see if it recovers.
I am already on the latest Cbus firmware, 6.010.
Ingo
PS. Thanks to Julian for ComfortClient which aids in detecting this very quickly.
|
| Posted: Wednesday Sep 14th, 2011 02:57 am |
|
23rd Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
Are there are Busy1, Busy2 or ERROR leds on?
The new firmware basiaclly resets the SIM to a known state every minute so this state should not maiuntain for more than 60 seconds
|
| Posted: Wednesday Sep 14th, 2011 04:35 am |
|
24th Post |
Ingo
UCM Pi Users
| Joined: | Sunday Jan 21st, 2007 |
| Location: | South Africa |
| Posts: | 562 |
| Status: |
Offline
|
back to top
|
Yes, the Busy2 LED is permanently on.
|
| Posted: Wednesday Sep 14th, 2011 04:53 am |
|
25th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
If you wait for 60 seconds can you see the Busy1 and Busy 2 leds flashing like they do after a reset? This shows that the SIM Module is being initialised, and he BUSY1 and BUSY2 leds will switch off leaving the RDY led on
|
| Posted: Wednesday Sep 14th, 2011 05:03 am |
|
26th Post |
Ingo
UCM Pi Users
| Joined: | Sunday Jan 21st, 2007 |
| Location: | South Africa |
| Posts: | 562 |
| Status: |
Offline
|
back to top
|
No, nothing happens at all. I watched it for 2 minutes. The only time the Busy2 LED goes off is when there is movement detected on my Garage PIR. Once movement stopped it goes back on. No other LED's flash except the RS485 BUS Led's and the Rdy LED being On all the time.
I think the reset routine might not be initialising.
Here is an idea: Can you not reassign the PP2 jumper to force a reinitialise when shunted? This way I can run the UCM without PP2 jumper and when I detect the issue I can manually reinitialise it. This is all assuming that your internal reinit routine doesn't fire when it's supposed to... This will at least prove that we are working in the right direction.
Last edited on Wednesday Sep 14th, 2011 05:38 am by Ingo
|
| Posted: Wednesday Sep 14th, 2011 03:48 pm |
|
27th Post |
Ingo
UCM Pi Users
| Joined: | Sunday Jan 21st, 2007 |
| Location: | South Africa |
| Posts: | 562 |
| Status: |
Offline
|
back to top
|
Just an update, getting home today the response restored by itself. When I checked this morning it was still broken but 10H later it fixed itself...
Ingo
|
| Posted: Saturday Sep 17th, 2011 09:58 am |
|
28th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
Which SIM Module are you using?
The PP2 is a hardware jumper so it cannot be reassigned but something like that may be possible
|
| Posted: Saturday Sep 17th, 2011 11:42 am |
|
29th Post |
| Posted: Monday Sep 19th, 2011 11:55 am |
|
30th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
It looks like whatever caused the SIM to go into that mode also prevents the commands from changing the modes to the correct ones
The new firmware 6.011 goes 1 step further - if it fails to set the options, the UCM is reset so this should be foolproof
Also SW8H shunt when inserted will cause the mode stting commands to be immediately sent to the SIM instead of waiting for 60 seconds
Attachment: Cbus6_011.zip (Downloaded 1 time)
|
| Posted: Monday Sep 19th, 2011 01:34 pm |
|
31st Post |
Ingo
UCM Pi Users
| Joined: | Sunday Jan 21st, 2007 |
| Location: | South Africa |
| Posts: | 562 |
| Status: |
Offline
|
back to top
|
I've downloaded the new code so let's see what happens.
Ingo
|
| Posted: Friday Sep 30th, 2011 01:29 am |
|
32nd Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
So there has been no problems since the upgrade to Cbus 6.011 since the upgrade for any of you?
|
| Posted: Friday Sep 30th, 2011 04:28 am |
|
33rd Post |
Ingo
UCM Pi Users
| Joined: | Sunday Jan 21st, 2007 |
| Location: | South Africa |
| Posts: | 562 |
| Status: |
Offline
|
back to top
|
Mine has been running stable since the upgrade but we know it sometimes take more than two weeks to 'break'. I would give it another week or two before I can really say that it's working better than before. It does look promising though...
Ingo
|
| Posted: Wednesday Oct 5th, 2011 05:54 pm |
|
34th Post |
Ingo
UCM Pi Users
| Joined: | Sunday Jan 21st, 2007 |
| Location: | South Africa |
| Posts: | 562 |
| Status: |
Offline
|
back to top
|
I just had another partial failure. I had a power failure for about 20 minutes where the Cbus network went down but obviously Comfort stayed up and running. Checking functionality after the power failure I saw commands go to/from Cbus to/from Comfort and back EXCEPT when I do a Cbus 'Get Status' command below.
2011/10/05 19:47:45 Info : Special Function "Security Status Request" Executed
Usually this command forces the UCM/Cbus to send all the zones status to Cbus but it doesn't do anything. Resetting the UCM/CBus via software restarted the zone updates again.
Ingo
|
| Posted: Thursday Oct 6th, 2011 01:18 am |
|
35th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5500 |
| Status: |
Offline
|
back to top
|
The communications both ways between cbus and comfort were working after the power failure?
Did you know if the zones were already updated to Cbus before you send the Security Status command? Does the security status command work in normal cases?
|
| Posted: Thursday Oct 6th, 2011 03:26 am |
|
36th Post |
Ingo
UCM Pi Users
| Joined: | Sunday Jan 21st, 2007 |
| Location: | South Africa |
| Posts: | 562 |
| Status: |
Offline
|
back to top
|
slychiu wrote: The communications both ways between cbus and comfort were working after the power failure?
Did you know if the zones were already updated to Cbus before you send the Security Status command? Does the security status command work in normal cases?
1. Yes.
2. Good question - I don't know, it's not something I check regularly, perhaps once or twice a week. Under normal conditions it works perfectly.
|
| Posted: Thursday Oct 6th, 2011 03:56 am |
|
37th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5500 |
| Status: |
Offline
|
back to top
|
Perhaps you can switch off the Cbus for a few seconds and try
The UCM/Cbus shoulod resend the zones info once it detets that the Power has retured, so it should not be necessary to query security zones
|
| Posted: Thursday Oct 6th, 2011 07:09 am |
|
38th Post |
Ingo
UCM Pi Users
| Joined: | Sunday Jan 21st, 2007 |
| Location: | South Africa |
| Posts: | 562 |
| Status: |
Offline
|
back to top
|
I simulated the conditions of last night but this morning the Security command worked as expected. It seems that this issue is not related to the thread we are currently busy with. I sent you a PM earlier with some findings.
Ingo
|
| Posted: Monday Nov 28th, 2011 01:31 pm |
|
39th Post |
palmlodge
Member
| Joined: | Thursday Dec 14th, 2006 |
| Location: | United Kingdom |
| Posts: | 507 |
| Status: |
Offline
|
back to top
|
Is this 6.0 stream now stable and Ok to upgrade from 5.x ?
|
| Posted: Tuesday Nov 29th, 2011 12:56 am |
|
40th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
Yes, as far as we know, that is why they have been released.
We have not heard from you if the firmware has fixed the problem you reported. This was one of the problems we intended to fix, so until we have a confirmation from you we dont really know if it does fix it, because the problemnms repirted could not be duplicated
|
| Current time is 05:08 am | Page:   1 2 3   |
|
