Minder 5207A Keypad Comms Error Message

[tavsec]

After wiring up my 2 keypads, I'm getting the following error message - " Keypad COMMS Failed, Call Installer for Service" I've checked the keypads are daisy chained together correctly, the TERM jumper is removed from the intermediate keypad, and the P2 RS485 terminal are used on the minder unit with the shield from the cable connected to the ground terminal at the P2 RS485 terminals

Any ideas??

[Forumadmin]

The keypads for the minder have been an issue for many users for some time. My experience is that if they work first time all should be well. Questions first.

1. Is the minder a v2 and when did you purchase it?
2. Did you set unit id's for the keypads, eg; 01 and 02?
3. Have the keypads ever worked together or singularly?
4. What version of firmware are you using. 3.02 or 4.04?
5. Can you communicate with the minder via the pc you are using?
6. What is your shoe size (just kidding)

Answers these and I'll be able to give you a fix I'm pretty sure.

Cheers

[tavsec]

Answers to the questions as follows:
1. No mention of a version no, unless the model No - 5200CU/2 means version 2? The serial no is 001000372457. I purchased it direct from Clipsal in Northgate Brisbane (I work for Bovis Lend Lease & our electrical engineer arranged a VERY good discount to trade pricing)
2. Yes I did manage to figure out how to get the keypad no's to 01 and 02
3. No, they have never worked yet
4. Firmware version 3.0.2
5. Yes my PC can communicate through the minder to C-Bus, but not the minder itself (very wierd)
6. 15 - just kidding

[Forumadmin]

You need to establish PC comms with the minder to tell it what to do and what equipment is attached to it, ie the keypads. Unless you can get this far not much else will happen, however if you have PC comms and have added the keypads then....

We can assume the software version you are using is 3.02?

1. Power off the 5200 and count to 10 power on the 5200.
the LEDS should cycle through and then leave just 1 LED lit. The RHS LED looking at the panel should be the only LED lit excepting the C-Bus card. Is this the case?
2. If you get this far, power down again and then remove one of the keypads, reset the jumpers accordingly to have a single comms keypad. Power up and see if you can get one kepad talking. While you have the keypad open look for a socketed chip on the PC board. It should have something like MCM LCD V1.6 and a date. Can you tell me what it has stamped on the keypad?
3. Have you tried to do a firmware download to the 5200? or a controller reload?

Bell me on 0414 434040 during business hours and we can discuss the problem and find a solution alot quicker.
Its late and my brain hurts.

[coppo1]

coming from experience and how many times i have been assured by people of what their current firmware version is.....

the first instruction with LCD keypads and the "contact your installer" error messages is....

ALT - J , this will give you a pop up "engineering" window. It lists the current software version you are using and the firmware version loaded into the controller.

note: due to complaints from integrators still happily using 302 software and having issues with CIS supplying the controllers pre-loaded to 404 firmware, and integrators not being able to go back to 302 easily.... CIS then decided to sell all controllers with 302 loaded. This way new users could still update the firmware to 404 easily.

A reminder window was built- in to the software to check your firmware version, but it also had an option to disable the auto firmware checker. As with most users they disabled it and then they would forget to manually check the firmware.

effectively what happens is 404 software + 302firmware + LCD keypad = contact your installer error message, ALWAYS. updating of the firmware fixes this 99% of the time.

All of this is common knowledge ( ie , not confidential ).

[Forumadmin]

Not touching this one.

[tavsec]

I've disconnected the 2nd keypad, as advised, and re-inserted the jumper, but still get the error message

The firmware is 4.04, and the software is 4.04, and the keypad is V1.9

Any further ideas?

[tavsec]

I had the wrong address in the keypad - I had 00, when minder was looking for 01. I suspect minder does not like 00 as an address.

Holding down the menu button, then pressing 1, got me into the setup screen for the keypad, which then allowed me to edit the address - don't forget to press 0 to save and exit properly

Many thanks to Forum Admin for spending the time on the phone with me - I finally get to play around with writing scenarios

[coppo1]

I had the wrong address in the keypad - I had 00, when minder was looking for 01. I suspect minder does not like 00 as an address.



It is more so that the software does not support "00" as an address. When you add a LCD keypad in the software gui , you will see that the first supported address is "1" whcih the keypad takes as "01".

details of how to access the menu are in on your computer in "online documentation" if using v404 software. look at the LCD installation instructions.

additional info to you guys.....

The whole thing of the LCD keypad resetting to "00" typically tends to happen when you have a 12volt battery connected to the controller and the 12 volt battery is run right down to approx 10.5 volt. At this point the controller "puts up its hands" and says enough, falls over, shuts down. When power is re-applied the controller correctly starts up on the correct scenario, but the keypad beeps coz it has reset to address "00".

Another suggestion to the keypad "comms failed", is that the IC for the P2-RS458 connection on the controller can "die", it is very rare , but it has happened, due to surge, oeverload, etc.

Seeing that Homeminder only uses P2-RS485 and not the P3-RS485 connection it is possible to power down the panel and "swap" the IC's between P2 and P3 ( if P3 IC is still good).

This has been done by installers in the past for a quick fix...

[Forumadmin]

Good Reply coppo.

you should run a forum :D