UCM/Cbus

[slychiu]

Ingo and Palmlodge have encountered a problem with the UCM/Cbus where after some time, it stops receiving any Cbus messages, ie it does not generate a counter update CT as seen in Monitor IO This could not be duplicated by Cytech so far even when testing with Ingos configuration

However the problems reported by Ingo and palmlodge are not consistent

Correct me if I am wrong, Ingo had no issues with UCM/Cbus 5.208 but started having problems with 5.216 with the new ST7 SIM. After a fea days or week, the UCM/CBus would stop receiving Cbus messages and updating counters but could still send message to Cbus

Ingo upgraded to  UCM 5.235 with the old SIM and had no problems
But when the ST7 SIM was used, the same problems still occured but after a longer interval. So with Ingo it seems the problem only happens with the new ST7 SIM

Palmlodge reported the same issue with receiving cbus messages and counter updates (but not reported whether Comfort can send messages to Cbus) with 5.235 whereas he had noi problems with 5.216 for  several years, see http://www.comfortforums.com/forum73/2397.html
He is using the new  ST7 SIM

CBUS firmware 5.235 generally fixes bugs in 5.216 and also has significant improvements see http://www.comfortforums.com/forum85/2293.html

I hope this is an accurate summary of the problem reported so far

[Ingo]

The description on my issue is correct. I am currently on the new ST7 SIM running 5.216 to see if the specific problem of Counter updates reappear. We just need to wait and see...

I am just curious about your statement regarding palmlodge running 5.216 and ST7 for years. From my checks I saw that 5.216 was released on 20/08/2010 and the ST7 SIM is also fairly new. Perhaps we should just get confirmation on the exact timeframe and H/W that he is running.


Ok, reading his post again I think there was a misunderstanding, the \'for years\' statement means that nothing changed on the CBus button programming side. He did not mention for how long he has been running the new SIM and if the problem was/wasn\'t experienced on an older SIM/Firmware combination.

Ingo

[palmlodge]

Hi Not quite correct. I\'ve used the same \'code\' for years. The CBUS UCM was changed in early 2010 and have been using that unit since. So all has been ok for about 15 months until the last upgrade to 5.235 - that\'s when the issues started.

To summarise :

From 2004 until March 2010, I used the non-programmable CBUS UCM. All OK (except for a few resets over the years).

From March 2010 to date, I have the programmable CBUS UCM. (no reset issues)

Problems started in June 2011 with the 5.235 code drop.

[palmlodge]

Had this a couple more times now - but have not been able to get Comfigurator loaded up quick enough to send a response to CBUS so far. It normally comes back to life after a few minutes of downtime.

[Ingo]

Try ComfortClient and setup an object to send a Cbus command.

www.futurehomesoftware.co.uk

 

[slychiu]

For the older SIMs  the firmware used to re-initialise regularly because they seemed to revert to basic mode. For firmware we support new and older sims (many varieties) so our initialisation is based on which is detected It was assumed that the newer SIMs would be more stable, andf in our own testing we have found no problem as we have 5.235 and new SIM installed for many months in our office.
It looks like we will have to reintroduce the reinitialisation of SIM every minute or so
This will not re-update counters etc because the UCM updates counters only when there is a change

[palmlodge]

No thanks. I will only use the official tools.

[user=436]In[/user][user=436]go[/user] wrote:

Try ComfortClient and setup an object to send a Cbus command.

http://www.futurehomesoftware.co.uk

[palmlodge]

The question you should perhaps ask is - what changed between 5.218 and 5.235 as 5.218 appeared to be OK.

[slychiu]

Everyone has different usage configurations. Other problems that were encountered in older versions were fixed and improved in the later firmware which must deal with different sim versions
The problem experienced by Ingo is also different from yours

[slychiu]

Everyone has different usage configurations. Other problems that were encountered in older versions were fixed and improved in the later firmware which must deal with different sim versions
The problem experienced by Ingo is also different from yours