Login

**wexfordman** · (This post was last modified: 12-17-2014, 03:15 AM by wexfordman.)

Thanks Ingo,Slychui
General update, I disconnected the suspect vmb4ry module from the velbus system today, and everything g has worked 100% ok so far.
It does indeed look like the velbus module was causing the problem, a very weird problem.
Anyway, hoping to have a new module by the end of the week to swap out and this should give a final answer, and I will send the faulty one back for repair.
Regards
Eamon

***slychiu*** · 12-17-2014, 01:30 PM

I hope they will feedback what the problem was. We would like to know what caused this

**wexfordman** · 12-18-2014, 01:31 AM

[user=1]slychiu[/user] wrote:

Quote:I hope they will feedback what the problem was. We would like to know what caused this

Will definately ask them to provide details. Day two now of full service with no issues and the vmb4ry disconnected
Regards
Eamon

**wexfordman** · (This post was last modified: 12-30-2014, 09:58 PM by wexfordman.)

ok,

Update as follows. Shortly after the post above, I started to have problems again, and it really confused me, as the vmb4ry was completely disconnected from the system, the only thing common was the 12v power whcih was still powering the vmb4ry so I could retain local control.

I ignore the issue, as I had a new vmb4ry on the way, and this would eliminate the module as faulty or not.

Anyway, christmas eve, the new module arrived, it was in fact a vmb4ryno, which is pretty much the same module, just to local PB inputs. I replaced it for the suspect one, updated comfort and left to see how things panned out.

That evening, the problem came in again, comms failure.

So, fairly confused now, I am just simply working my way through replacing parts to eliminate as much hardware as possible.

Yesterday I swapped the ucm board that my eth was connected to (re-used the daughter board), and the problem still recurred. The event log shows UCM2 (the velbus ucm) as the main/first module to lose comms, so that was next on my list.

I have replaced the ucm velbus, but cant upgrde the firmware to ucm velbus, as it is showing as a ucm general.

Can anyone advise how I do this it was formerly a ucm usb, so I am simply replacing the daughter boards).

Regards,
Eamon

***slychiu*** · 12-31-2014, 08:45 AM

You cannot change a UCM/USB firmware to a UCM/Velbus. You can only upgrade the firmware to the same type

I dont think the fault is with the UCM/Velbus

What triggers the fault now? Is it the switching on of the relays?

Can you switch on the velbus relay manually and not from Comfort? Does that cause the problem?

***HeFeng*** · 12-31-2014, 09:25 AM

hi, waxfordman
I noticed from your post: \"from the system, the only thing common was the 12v power whcih was still powering the vmb4ry\"
so you power the VMB4RY or VMB4RTNO input (12V) by comfort system? if like this, maybe your problem is due to this...
just ignore my post if the relay is powered by velbus system...

**wexfordman** · (This post was last modified: 12-31-2014, 01:04 PM by wexfordman.)

[user=1]slychiu[/user] wrote:

Quote:You cannot change a UCM/USB firmware to a UCM/Velbus. You can only upgrade the firmware to the same type

I dont think the fault is with the UCM/Velbus

What triggers the fault now? Is it the switching on of the relays?

Can you switch on the velbus relay manually and not from Comfort? Does that cause the problem?

Hi slychui,
The fault still seems to be trigggered by the heating going on (whether manually or via comfort) but it does not seem to recover if i turn it off again.
Last night, the problem occurred and no matter what I did to try and restore comms I could not. I disconnected every keypad and scs switch via removing the ka/kb and 12 power out from the main board. I also disconnected the ucm velbus. At that point the only items connected were the main board lem and ucm eth, and I could not connect to the system even after restart. (By this I mean I could not connect comfigurator to log in to the system, nor connect a phone via the app.
All this time, and trhiughout the night however, comfort performed all macros etc so was not frozen. For example there are pir activations which aactivate velbus lights and turnnthen off again after timers expire etc.....all this worked fine, so comfort continued to work this way, which indicates velbus ucm was fine and main board was fine.
The system is still down, but I expect it to recover at about 9am

**wexfordman** · 12-31-2014, 01:07 PM

[user=4020]HeFeng[/user] wrote:

Quote:hi, waxfordman
I noticed from your post: \"from the system, the only thing common was the 12v power whcih was still powering the vmb4ry\"
so you power the VMB4RY or VMB4RTNO input (12V) by comfort system? if like this, maybe your problem is due to this...
just ignore my post if the relay is powered by velbus system...

Hi hefeng,
The velbus modules are powered by a separate 12v/15v power[size= supply which is independent of comfort (it does power the ucm velbus daughter boardbi think though.)][/size]

***slychiu*** · 12-31-2014, 01:14 PM

If you completely disconnect UCM/Velbus from Comfort and turn on the relays with Velbus does it still happen?

**wexfordman** · 12-31-2014, 01:16 PM

[user=1]slychiu[/user] wrote:

Quote:If you completely disconnect UCM/Velbus from Comfort and turn on the relays with Velbus does it still happen?

I can try that this evening, but put it this way. When I completely disconnect the ucm velbus I still cannot get comfort to recover.
Comfort will recover now at about 9am.