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

scs and keypad comms failures
 Moderated by: slychiu Page:    1  2  3  4  5  Next Page Last Page  
 New Topic   Reply   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Monday Dec 1st, 2014 11:25 pm
   PM  Quote  Reply 
1st Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi,
The last few days I have had a few instances of coms failure alarms on my comfort system.  I have 2 keypads, 4 scs's a ucm etch and a ucm velbus. I have completed no work or upgrades on comfort over the last few months, so nothing has been done to introduce this as far as I can tell.
It started as a keypad failure, and another time as an scs failure, and this evening everything started failing. I also dont seem to be able to log in via ethernet either, although my velbus is working fine via comfort.
Any help in a bit of troubleshooting would be much appreciated.

Regards,Eamon



 Posted: Tuesday Dec 2nd, 2014 12:32 am
   PM  Quote  Reply 
2nd Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

ok, looking a bit bizzare now. I started to disconnect all my scs switches to see if one was causing he problem, and started to notice a pattern. It seems I get comms failure when a specific velbus relay is activated!!

I have one channel on a vmb4ry for turinin on the central heating, an without fail, whenever I turn it on, the comms failures come on, and clear when i turn it off again...

Doesnt happen with any other velbu channel, just this one.



 Posted: Tuesday Dec 2nd, 2014 01:57 am
   PM  Quote  Reply 
3rd Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Have just upgraded comfort firmware to latest. UCM velbus is at 5.2.3 thouh as I hadnt upgraded this due to not being able to do it via comfigurator.

Will look at upgrading it towards end of week, but I cant see how that would be the problem, considering that it had been working fine for years and I have not touched it for months, and the last firmware upgrade I did on comfort was early this year.

Its very odd that the activation of the velbus channel causes the problem (when activated either via comfort, or via velbus pb input)



 Posted: Tuesday Dec 2nd, 2014 04:44 am
   PM  Quote  Reply 
4th Post
CytechMartin
Cytech


Joined: Monday Oct 13th, 2014
Location:  
Posts: 47
Status: 
Offline

  back to top

When you activate a velbus relay, you get communication failure. I think you can check the wiring of that part. It does not look like programming problem, just in case, you may send your cclx file to support@cytech.biz . I will help you check the programming.



 Posted: Tuesday Dec 2nd, 2014 12:19 pm
   PM  Quote  Reply 
5th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi Martin,
Thanks for update, I will forward on my logfile shortly. While not ruling out a wiring problem, there are a few things that make me think it is not.
I will refer to the velbus relay which triggers the comms failure as the water heating relay
1) I have a number of vmb4ry modules, each of them has one connection to the comfort ucm, but controls 4 relays. The water heating relay in question is one of 4 relays on this module, all communicating to comfort via the exact same bus, and the same physical wiring, yet it is only this relay which causes the problem.2) Everything is working fine now this morning, even when the water heating relay is activated.

So, the topology, and the wiring of the suspect relay, just doesnt make sense to be due to a wiring problem, as you would expect the same thing to happen on all relays on that module which communicate out the same physical wiring to comfort.

Regards,Eamon



 Posted: Tuesday Dec 2nd, 2014 12:27 pm
   PM  Quote  Reply 
6th Post
slychiu
Administrator


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

  back to top

I think it is not so much a wiring error in Comfort , but what the velbus relay is connected to
For example the relay may be disconnecting the comfort bus or it may be switching some load that causes comfort to be switched off. Communications failure is due to loss of connection on the bus or loss of voltage to the module

Test by switching on the relay, then investigate what causes the communications failures.



 Posted: Tuesday Dec 2nd, 2014 12:55 pm
   PM  Quote  Reply 
7th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi slychiu,[size=
]Last night when the problem was occurring, I disconnected the wiring on the velbus relay side so the relay was not switching any power, just in case it was leaking something in to the bus. It made no difference.[size=
]I'm confused even with that at how even a problem on the velbus out affect the comma bus in comfort, as they are effectively isolated are they not ?



 Posted: Tuesday Dec 2nd, 2014 01:09 pm
   PM  Quote  Reply 
8th Post
slychiu
Administrator


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

  back to top

There certainly appears to be some interference. It depends on how the wirings between the 2 systems are connected.
when the communications trouble happens, check the voltages on the UCM modules



 Posted: Friday Dec 5th, 2014 10:02 pm
   PM  Quote  Reply 
9th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

OKay, been away for a few days so not had a chance to do much on this, but been at home all day and everything has been working perfectly. Since 505pm every time i turn on the velbus relay related o the water heating, I get a comms failure, and then when I turn it off, it clears.

This has been happening consistently over the last few days, in that during the day time, everyhitng is fine, even when using the velbus relay, but in the evening, problems start.



 Posted: Saturday Dec 6th, 2014 05:17 am
   PM  Quote  Reply 
10th Post
slychiu
Administrator


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

  back to top

If it happens consistently at a certain time hen it should not be too difficult to fnd the cause
It is not possible for the cause to be anything related to programming or the behaviour of comfort because this cannot cause  loss of communications. It has to be a physical cause, either loss of voltage on the modules or disconnection



 Posted: Saturday Dec 6th, 2014 01:07 pm
   PM  Quote  Reply 
11th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Ok Thanks

I will measure voltage on the ucm modules today and check again when the problem occurs this evening.

Regards
Eamon



 Posted: Saturday Dec 6th, 2014 10:57 pm
   PM  Quote  Reply 
12th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Right,
Did a bit of work on it today, upgraded my velbus ucm to latest firmware. Everything was working fine again until again, about 5 o'clock things started to go awry.
Communications failure again. When it started again, It was again only when the velbus heating relay was activated, and I could clear it by un activating it. Measured the voltage for comfort 12v, and was getting about 13.8v, with about 0.1v drop when i truned on the velbus relay, and about the same with any other relay too, so nothing jumping out at that.
Things started to get very weird after a bit more testing and measuring, in that the comms filure was permanent, and the keypads un responsive, so i did the follwing
1) Disconnected all scs switches, (by disconnecting the common 12v feed to them) No change.2) Disconnected both keypads (and tried to log in via app), unable to log in via app.3) Disconnected velbus ucm, no change, reconnected and disconnected just the velbus bus, no change, still unable to log in via app.
Reconneced everything, restarted comfort, kepyapds bleep, announce tamper alarm, as expected, start screaming and then lock out, no access to anything.
Stumped now. I am exepcting it to clear again in a few hours.
Regards,Eamon



 Posted: Sunday Dec 7th, 2014 06:03 am
   PM  Quote  Reply 
13th Post
slychiu
Administrator


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

  back to top

Can you measure if there is a short circuit on the KA/KB wires?

try removing the KA/KB and connect just the  ucm  by the  short 4 way cable to Comfort PCB and log in by UCM?

Its better to solve this while the fault is manifested and before it recovers

Last edited on Sunday Dec 7th, 2014 06:28 am by slychiu



 Posted: Sunday Dec 7th, 2014 12:34 pm
   PM  Quote  Reply 
14th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi slychui

Will try that, all is working again now, since 8am everything started working again.

I did notice a tamper alarm slave 12 in the keypad, I have no slave units



 Posted: Sunday Dec 7th, 2014 11:17 pm
   PM  Quote  Reply 
15th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi Slychiu,
OKay, as expected, around about 6 this evening things started going awry again, so here is what I did
1) Removed KA and KB wiring from the main board so that only ucms were connected to ka kb via the ribbon cables2) Tested to make sure no short on the ka/kb inputs that I had just removed, all okay.

So, at this point, all keypads and scs's had no ka/kb connectin to comfort. I then logged in to comfort successfully via the app and did the following tests.
1) Turned on the velbus heating channel....the app failed to report the status, and also failed to respond to any other velbus commands to any other channels.2) Turned off the velbus heating channel....the app immediately began to successfully report back velbus commands from any other channel.

I could repeat the above over and over again with 100% the same results each time.
So, it appears that when this velbus channel is activated, it pulls down the ka/kb bus ?
Just to clarify also, this particular velbus channel is 1 of 4 on that vmb4ry module, and all communicate on the same velbus bus, but only this one causes the problem.
The removal of the ka/kb for all the scs/keypads etc would confirm that the wiring of these are not the problem ?


Regards,
Eamon
Comfort firmare is 100% up to date, including ucms. My setup includes 4 scs switches 1 kp01, 1 kp04, 1 ucm eth01, 1 ucm velbus 7 vmb4ry and 1 vmbdmi

Last edited on Sunday Dec 7th, 2014 11:21 pm by wexfordman



 Posted: Monday Dec 8th, 2014 08:02 am
   PM  Quote  Reply 
16th Post
slychiu
Administrator


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

  back to top

So when the velbus channel 1 of VMB4RY is switched on, it causes rs485 bus to lose communications
But then how are you able to switch off the velbus channel 1?


I suspect there may be a fault with the isolation of  the Comfort RS485 bus  from Velbus RS485 bus

Can you send a photo of thye UCM/Velbus and the connections to it?



 Posted: Monday Dec 8th, 2014 11:32 am
   PM  Quote  Reply 
17th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi slychiu,


I turn off the velbus relay manually from the wall switch wired to the pb input.

Will send photo shortly, thanks



 Posted: Monday Dec 8th, 2014 12:13 pm
   PM  Quote  Reply 
18th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi,[size=
]Just to update, the comms failure seemed to have come on permanently just before we headed to bed last night. Couldn't activate it control anything. Disconnected the ka and kb and could not connect to comfort via the app.[size=
][size=
]Plugged ka and kb back in and went to bed.  At 8am this morning, everything restore and working perfectly.[size=
][size=
]I don't understand the regularity of this, it's so predictable.



 Posted: Tuesday Dec 9th, 2014 12:13 am
   PM  Quote  Reply 
19th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Update today.

Again, all seemed to be okay during the day, I did a few minor things, I downloaded latest firmware to my local drive and updated all my modules locally just to be force a firmware update. All went okay, and everything seemed to be working, but the evening gremlins were not due to call till another few hours.

Bang on que, at about 5pmish problems started again. Here is what I did to troubleshoot

1) I rewired the comfort velbus (l and h) onto a new direct cable from the velbus ucm to the nearest vmb4ry. No change, comms woud fail when heating was turned on, and clear when it was turned off.

2) When comms is down, I can still see commands goin to the ucmvelbus from the vmb4ry modules when i manually activate the relays.
3) I also rewired so that the only velbus mdule connected was the one vmb4ry with the heatng control relay on it. This meant that the only wiring for L and H was a short 2ft cable between the ucm velbus and the vmb4ry.  I was still able to replicate the failure of the comms by turning on an off the heating relay.

4) I started to require the heating relay from chan 1 of the vmb4ry to chan 4, to see if I could move the problem with it.

As I was doing this, I then noticed that i had completely lost comms, and could no longer communicate with comfort via keypads, scs, or app (can ping the ucm eth no problem).

To try and isloate the probelm with the comms failure, I started to disconnect different modules on the ka/kb bus as follows

1) Disconnected ka/kb connection to main board, effectively removing all kepyads and scs units. Unable to log on to ucm eth
2) Disconnected ucmvelbus also, leavin just the mainn bard and ucm eth connected, and still unable to connect via app.
3) Disconnected ucmeth, and reconnectd just main board ka/kb to reconnect all scs and kepyapds, unable to get keypads or scs switches working,

It seems I am now completel locked out of the system, I suspect it will remain so until tomrrow at approx 8am.

Regards,
Eamon
Edit:- When I refer to not being able to connnect via app, the login screen appears in the "connected" staate, but when I enter the code, I get a continious "logging in" message.

Last edited on Tuesday Dec 9th, 2014 01:04 am by wexfordman



 Posted: Tuesday Dec 9th, 2014 11:31 am
   PM  Quote  Reply 
20th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi,
Photo is here 
What you are looking at is the ucm velbus with the new cable I ran yesterday connected. The new cable is about 3ft long and connects direct to the use board housing my velbus modules. 
You can also see the old cable with the connectors haning just besie it, this cable was abbrox 40ft run between comfort to a patch panel and back to the fuse board housing the velbus modules.
Again, at one point, I had the new short cable running to just one vmb4ry module last night, nothing else, and still no change.
As of 7am this morning, the velbus connection to comfort has started working again (comfort is performing velbbus commands based on pir responses), but the scs, keypads and ucm eth are still not contactable. I am expecting these to come back at about 8am.






Last edited on Tuesday Dec 9th, 2014 11:42 am by wexfordman



 Current time is 08:02 amPage:    1  2  3  4  5  Next Page Last Page  
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems