+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Software Applications (https://www.comfortforums.com/forum-4.html)
+--- Forum: Comfigurator (https://www.comfortforums.com/forum-20.html)
+--- Thread: Keypad scan adds invalid keypads (/thread-3368.html)
- Howser - 04-29-2013
I am using ...
- Ultra version 7.026 (Tried 7.028 as well)
Configurator 3.6.6
2 x Older Non LCD KP04 (10 years old)
1 x LCD KP04 (firmware 1.017)
When I do a scan, two additional keypads are added to my configuration. I have to manually delete the two keypads and rename the 2 oldish keypads every time. The same thing happened with earlier Ultra firmware, and it got resolved.
- wexfordman - 04-29-2013
Actually,
I think this happened to me a while back when making a modifcation to my config. After I downloaded the new file, I got a communication error, and when I checked it was from some additional keypads that went in with the file but did not exist.
Cant remember if I had done a scan previous to the download or not though!
- juwi_uk - 04-29-2013
Happening to me regularly.
Update: I should add it\'s only on my KP04.
- wiredhome - 04-29-2013
Happened to me on Saturday with a customer
i deleted them and added keypad 3 manually but now it showing comms fail
anybody got any ideas on this?
- Ingo - 04-29-2013
Me as well.
- juwi_uk - 04-29-2013
OK so here are the steps to easily recreate.
1) Open Comfigurator 3.6.8 and sign in
2) I immediately see Keypads for Kitchen (KP06), Landing (KP04, now shown in red) and a new \"Keypad02\". So I delete my \"Landing\" one and exit comfigurator.
3) Open Comfigurator again and sign in; look I\'m now joined by \"Keypad020\" (in red). Close.
4) Open Comfigurator again and sign in; look I\'m now joined by \"Keypad021\" (in red). Close.
5-infinity) I could go on all day like this... :0)
See attached.
I\'m maybe untypical as running ULT 7.028 and UCM 7.019 at the moment but had with the last few firmware\'s as well.
Must be a \"KP04 thing\" but I wouldn\'t say no to a free KP06 replacement if that\'s easier to fix ... :0)!!
Julian
- juwi_uk - 04-29-2013
Here\'s the Comfigurator trace that goes with it too:
> LI****
< LU01
< CT111E00
< cm02011E
> u?41
< KL00010000
< u?4106060700
> u?42
< KL00010000
< u?4200000000
> u?43
< KL00010000
< u?43FFFFFFFF
> u?44
< KL00010000
< u?44FFFFFFFF
> u?45
< KL00010000
< u?45FFFFFFFF
> u?46
< KL00010000
< u?46FFFFFFFF
> u?47
< KL00010000
< u?47FFFFFFFF
> u?48
< KL00010000
< u?48FFFFFFFF
< CT111F00
< cm02011F
< CT111E00
< cm02011E
- juwi_uk - 04-29-2013
Also why it seems do I get a
< KL00010000
every time a UCM ID u? command is sent; is this right?
J
- Ingo - 04-29-2013
It\'s for all Keypads in the 41-48 ID range only. My guess it\'s either for Mobile enhancements or to set LED status after a successful scan.
Ingo
- juwi_uk - 04-29-2013
yes but sending for every command seems a bit overkill.