scs and keypad comms failures

[wexfordman]

Everything now working normally again as expected, from 08:50 ish

[wexfordman]

[user=318]wexfordman[/user] wrote:

Everything now working normally again as expected, from 08:50 ish

Just to put some definate times on this, the event log over the last few days shows
29th: comms failures start at 16:57 with keypad 2, and continue on for all modules until the comms failure stops recurring at 08:37 the following morning (30th)
30th:- Comms failures start, again at 16:57 with scs 01, and continue for all modules until comms failure stops the followign morning (31st) at 08:35
I will now disconnect the ucm velbus from comfort, and remove the ucm from comfigurator. Will leave it in this state until tomorrow am, and report back with any changes etc.


Event log is attatched (ignore the mid -day comms failures for the 30th, this was me trying to replace the ucm velbus with a ucm usb main board) and a keypad

Regards,Eamon

[wexfordman]

Okay, update again.
With ucm velbus disconnected from comfort AND velbus bus no alarms came in a expected time (around 1:57). The heating relay was off at this stage
I then turned on the heating relay manualy (bearing in mind, that comfort now has absolutely no connectivity to the velbus system), and I lost comms!
I am absolutely stuck on this, I simply cannot explain it.
Bus monitor file enclosed, you can see the issue come in at about 17:07
Regards,Eamon

[slychiu]

The NAKs appear around 17:07 and stop at 17:08:21
After that the commuications seem to be fine. The keypad and RIO/SCS are being polled and reply is received. So you should be able to use the system after that time

[wexfordman]

I could not connect to eth, I had to restart the system by disconnecting power and battery before I could connect again.
I have two more tests to do, I am going to have the vmb4ry on its own 12v power supply independent of the other modules and see what happens. 
After this, I can only think that perhaps the load side of the heating is introducing interference in the comfort bus somewhere, so I will try and trace the Gnostic to see if I can find a cross over.

[wexfordman]

Okay,
Latest update, this issue is still happening. Today as expected, the comms failures started once again like clockwork at 5pm.
Tonight, I rewired the heating ac supply via a different route, bypassing the mcb that was feeding it and still no change.
Whenever the oil burner kicks in, I get comms failure in comfort (between 5pm and 9am).
It looks like I am going to have to get an electrician in to see if I can completely rewire the heating, and possibly remove it from comfort altogether...I\'ve run out of ideas...it\'s been like this and working fine for nearly fifteen years, and the last month has me dumbfounded.

[slychiu]

It does look like the oil burner is causing interference to the RS485 bus. The bus is normally very robust as it is differential and very noise resistant so it takes a lot of interference to affect it

I think it should be looked into as there may be other effects

[Ingo]

One leg of the RS485 touching ground somewhere? Check all the places where the RS485(KA/KB) cables route through between ALL the different modules. Check connectors also, one might be loose etc.

[wexfordman]

Thanks all, will do a bit more digging. I would be in agreement to the ibterfer nxe issue, but the regularity of it has mendkubting. 5pm start, 9am finish, pretty much gauranteed.

[slychiu]

[user=318]wexfordman[/user] wrote:

Thanks all, will do a bit more digging. I would be in agreement to the ibterfer nxe issue, but the regularity of it has mendkubting. 5pm start, 9am finish, pretty much gauranteed.

you seem a bit stressed