PDA

View Full Version : MKII touch screen - C-bus communication failure


stevenfrost
03 Oct 08, 12:18 AM
HI
I have jsut added a MKII to a existing network, plug it in and it boots up. Screen then alternates between Unit not been programmed and Warning - C-bus comms failure. I also notice when its plugged in the c-bus light flashes on the PCI (mostly on littel flash off then on for a about 3 seconds then flashes off again)

I have loaded the USB driver on toolkit

I also cannot connect to the touch screen in PICED, nor see it when scanning the network. I am using latest version of both.

Thanks

Newman
03 Oct 08, 09:07 AM
It sounds like your network voltage is too low. C-Bus Devices flash their C-Bus LED at about 4Hz when the network voltage drops below 20V and the C-Bus LED turns off when the network voltage is below 15V or there is no C-Bus clock signal.

The MKII B&W Touchscreens draw 65mA, which is 25mA more than the old one and approximately a third of the power provided by one DIN dimmer/relay with built-in power supply.

stevenfrost
09 Oct 08, 12:26 AM
Network voltage is 30v+ on all units with the screen plugged in. Network has:
1 x12ch ralay with power supply 200ma
1 x 12ch relay no power,
1 x 350ma power supply,
1 PC interface
6x 4 button swithces
3x PIR.

So by my calculations should be enough?

______.
09 Oct 08, 04:12 AM
Does your switches etc still work while the screen is connected to the network?
Have you checked the basics eg: the connections on the back of the screen are right (no legs crossed etc) one clock/burden turned on etc

If you can't scan the C-bus network with toolkit and find the screen and you can't connect to the screen via USB with PICED then it sounds like you might have a faulty screen.

stevenfrost
09 Oct 08, 07:43 PM
I have checked all the basics, everything stops working when the screen is plugged in and can connect to the screen via PICED. Cant scan so I cant tell if the burden is enabled on the screen.
Do the screens come factory default burden enabled?

Newman
13 Oct 08, 09:09 AM
Sounds more & more like a faulty screen. Might be worth giving Tech Support a call.