No bus comms

[sinky100]

Hi all,

Just upgrading my comfort system from Comfort 1 to Comfort 2.

I have installed all of the following in my previous panel:
CP9000-ULT PCB, control panel x 1.
LEM03-M2, local expansion board 16 inputs x 1 (max 24 inputs/zones)
UCM-ETH V3, Ethernet interface x 1
APB01, ADSL passthrough x 1
KP06BL-NF, Keypad x 2
RGR05, ringer module x 1
Use existing DP03
Use existing sensors/siren, etc.

On start up, the red LED comes on, then off; the green LED comes on and stays on for a few seconds then starts to blink. All the KPs and the DP beep continuously and the KPs report \"Bus Communications Failure\". The installation manual indicates possible problem with the main PCB and to check U5 IC (can\'t see any issues there). I have checked the incoming power to the board (14 VAC), and the outgoing on COM and 12V terminals (13VDC).I disconnected the UCM-ETH03, but no difference.

Please note that this is a clean install, so I have not configured the system with comfigurator.

Any help would be greatly appreciated.

Many thanks,
Iain

[slychiu]

This indicates that the Comfort Bus (KA/KB) is shorted

Remove all devices fron the bus except Comfort and 1 Keypad and try to log in with default code 1234

Then add devices 1 by 1

[sinky100]

Hi Slychiu,

Have disconnected as following:
UCMETH03 - RS485
LEM - ribbon cable disconnected.
DP03 disconnected KA/KB and 12V/COM.
1 x KP06 disconnected KA/KB and 12V/COM

This leaves the comfort with 1 x KP06 connected. On start-up same problem and fault reported on front door KP06. Disconnected this and tried the rear door KP06, this initially indicates that the KP is not polled, then the fault returns \"Bus Communications failure\".
I have also checked the KA/KB terminals on the main PCB, but there is no short present here.

Any other ideas?

Thanks,
Iain

[sinky100]

Slychui,

Forgot to mention that the KP is unresponsive so I could not sign in.

Thanks,
Iain

[sinky100]

Slychiu,

Continued reading various posts and I think I have solved the issue! Seems that I should be using CAT5 for the KPs and DP.

I used the previous cabling from before which was normal alarm cabling for the KPs and DP. I have tried a KP06 using a short CAT5 cable, and the system boots to \"Security off\" as normal.

I will go ahead and replace all the cabling for the KPs and DP using CAT5. Hopefully then, I can get my system up and running.

Thanks for your help.
Iain

[slychiu]

The type of cable should not be causing the problem
Cat5 reduces interference and noise compared to alarm cable
But alarm cable should not stop communications
I think you disconnected the devices without disconnecting the bus from comfort
You connected 1 Kp to comfort after disconnecting the bus and this worked
So the problem should be the bus but not the cable type
What is the resistance between ka and kb?
Also ka or kb may be shorted to ground or other signals not just to each other

[sinky100]

Hi Slychiu,

Just an update:

KA/KB is measuring at 125kOhms.
I have connected both the KPs and the DP and the system boots up normally, all tested with short CAT5 cable locally. Have a fault for ID conflict (KP?), but guess that will resolve itself once I have configured the system for 2 KPs.

I will attempted to reconnect the UCM and LEM, and all the 12V/COM consumers, and report if this fault returns.

Many thanks for your continued assistance.

Thanks,
Iain

[sinky100]

Hi Slychiu,

Well, the system has been installed and I think I have managed to configure all the system correctly. All zone types allocated and tested, UCM configured, and system tested and working ok. Successful upload of configuration file through Comfigurator also completed.

I have not had a repeat of the initial bus communication failure as first boot up, but I\'m guessing that the replacement of the KPs and DP cabling might have corrected a wiring mistake(?)

If you think further testing is necessary, please revert and I will carry this out.
System is on test, in night mode tonight, so hopefully will gain some confidence with this.

Thanks again for all your assistance.
Iain

[slychiu]

Yes I think it was some problem with the connection which has been fixed when you disconnected and  reconnected