KT03 not working

[davestevens_uk]

Hi,
I\'m not quite sure why, but I decided to try the \'setup\' button on my KT03 for the first time ever....mistake. I remember getting to \'ID\', and I think I must have changed it by mistake. The outcome is that the KT03 won\'t now do anything. I\'ve ploughed through the tutorials, but I\'m now not sure whether the fix is via Comfigurator, or the keypad itself. The problem on the KT03 is that if I now press setup, it\'s presenting me with a keypad screen, and not the setup one. All buttons are unresponsive - ie they bleep, but do nothing.
I\'ve tried doing a direct USB connect to it and uploading a new config file, but I just get an error when trying to connect. I can connect to the main UCM fine and pull back system config.
Comfort is working fine, though the other keypads are showing communications failure, and flashing a green light.
Any help gladly received!Thanks,Dave.

[slychiu]

you may have changed the ID to another which is not polled by Comfort or clashes with another Keypad id, eg 1

Do a scan for modules and check if the KT03 is scanned at a higher ID.


When you press setup, the keypad screen appears for you to enter your user code. But if  the ID has been changed then the code cannot be validated with Comfort.


When the KT03 is unable to communicate with Comfort, it should show the screen below





Press the CHECK ID button.
This should directly go to the ID setting page. Change the ID to the correct one and exit. This should restore the ID and allow the KT03 to communicate

However if your KT03 firmwware is too old, it may not have this communixations failure detection feature. Do a firmware upgrade of the KT03 by direct connection to the KT03 USB port.  Right click on the KT03 and select Check for Updates (you must have an internet connection)


another solution if the KT03 ID clashes with another Keypad, is to remove the other keypad and let the KT03 communicate with the changed ID
Then you can change the KT03 id to the correct value and then reconnectthe other keypad

[davestevens_uk]

Hi Chiu,
Thanks for the rapid response. My KT03 is one of the very originals, and its firmware hasn\'t been updated since. I\'ve downloaded the latest via Comfigurator, but I get the \"comfort and ucm version must be at least 6\" error message. I\'ve found your post on that here:

http://www.comfortforums.com/view_topic.php?id=1782&forum_id=4&jump_to=7109

I don\'t have a spare UCM or cable though, so does that mean I\'m now stuck? I can USB direct connect to the KT03, but it sounds like that\'s not going to help.

Is there any other way of updating the ID on the KT03 without the firmware update?

Thanks,
Dave.

[slychiu]

I believe you tried to upgrade the KT03 firmware through another UCM

That requires a higher version firmware for the KT03

You should try to connect via the KT03 USB and do the upgrade that way. That was what I recommended

If you have problems you can also use the UCM firmware upgradng cable to upgrade the KT03 firmware, see instructions at http://www.comfortforums.com/forum4/1782.html

[davestevens_uk]

Sorry, that\'s what I did try. I have the KT03 connected to a PC via USB. In Comfigurator, right click the KT03, then \"upgrade firmware from local file\".

I get the message: \"Comfort and ucm version must be at least 6 to upgrade firmware by direct connection or bus. Please upgrade using the UCM programming cable\"

[slychiu]

That could be due to the KT03 having the wrong ID so comfigurator thinks it is upgradinbg by bus

Please use the ucm firmware upgrade cable

[davestevens_uk]

OK, thanks.

[davestevens_uk]

All,

I thought it may be useful to share that I managed to resolve it.

I took the KT03 out of the wall, and disconnected it from the Comfort bus (ie just power). It then reboots in a default config, and you can login with 1234# and get to the setup screen. I\'d managed to set the ID as 2, so it was an easy change to 1.

Put it all back, and after a quick date change, all working fine again.

I\'d like to say that I worked that out myself, but kudos to Jamie from soundandsafe.com who suggested it!

Cheers,
Dave.

[slychiu]

Thanks, I should have mentioned that as well

I hope you managed to upgrade your firmware