KP04-SS comms fail

[freak69]

Hi,

I have a KP04-SS (flat stainless steel version of the KP04). All was working fine until I pushed out a new config. Immediately on reset, I get a communication error with the keypad.

I have verified this is keypad 1 (says so on the lcd),  also taken it  and connected it up with short (50cm) patch cables to the main board and I still get the same problem.

Also of note which makes me the unit may have failed is that if I run the bus monitor when the keypad is connected (long or short cables, it makes no difference) I get a heap of traffic, mostly unknown commands.

I have tried diconnecting everything from the main panel but still the same problem.

Any more ideas?
In the previous post, there was some issue with firmware updating? I didnt think the KP04 could be updated? I have never updated any firmware on my system - it just works. (I have updated comfigurator though numerous times)

Thanks
TF

[ident]

Check the ID switches on the keypad. Keypd 1 should have all the shunts A, B, C, D inserted. Perhaps one  has fallen off, but as the system does not detect the ID until a reset is done (after a full write) it  did not have any effect.

Can you copy and send the gibberish on the Bus monitor, as it may give a clue

Is there another keypad in  the system?

[freak69]

I have confirmed that all 4 jumpers are in. This is the only keypad, so it should be number 1.

I have included a capture of the bus monitor from the moment I plug in the unit (which reported communication failure shortly afterwards). Please help!

Thanks
TF

[ident]

Thanks
It looks like the reply is corrupted
Can you send the following screens as well;

In Bus Monitor, before starting, uncheck the box Filer Poll/Null Response, then press Start. Then copy to clipboard and save to file

Then Halt, and press Clear to clear the screen. Now disconnect the KP04 and Start the Bus Monitor again without the keypad

Save to another file and send the 2 files to support@cytech.biz

This will pin down if the problem is due to the KP04 or not

[freak69]

done

[ident]

Thanks for the two bus monitor logs

The log without the KP04-SS  connected shows that when Comfort polls the keypad, there is a reply from a keypad with ID 1

When the KP04-SS is connected, the reply is corrupted, because both keypads are set to the same ID of 1

Comfort is also polling a Door station with ID1 but there is no response. Hence it seems likely that the Door station has its shunt set to keypad which makes it behave like a keypad.
On the Door Station, JP5 should be on the DS position if you have a DP03. Reset the DP03 by removing and connecting power

[freak69]

Thanks for looking, your help is much appreciated.

I\'m actually using the microDP doorstation from here.

http://www.home-control.co.uk/index_products.php?page=product_info.php&cPath=1_6&products_id=332&osCsid=28ada3f66b67bdbbd8b94f106b937518

This uses a DM02 (although their diagram says DM01 for some reason), so I dont have a the jumper you mention on a DP03. Is there something else I need to change for this istallation?

[ident]

No DM02 shpuld not be configurable as a keypad
Does the Door station work?
If you disconnect the DM02, does the KP04 work?

[freak69]

ok, this is downright weird! I disconnected everything before and had no luck however currently....

The KP04 works fine as long as the DM02 isnt plugged in (I dont use the DM02 yet so cant test it). As soon as I plug it in, the system goes crazy. I have checked the bus monitor polls (handy tip) and get garble everytime I poll for keypad01, so its clearly a problem between the DM02.

OK I have just changed the ID on the DM02 so that its now ID 2, changed comfigurator to say 1 have 2 keypads ond 0 doorstations and guess what - no alarms...

So I think the problem is actually with the DM02 now thanks to your help. How can the DM02 think its a keypad?

Thanks for the help so far - real learning experience!

TF

[ident]

What is the firmware version of the DM02? You can see that from the label on the main IC on the DM02.

Is the doorbell button faulty, or permanently pressed? This may be causing the problem.