Comfort Automation/ Security System Forums

[user=876]juwi_uk[/user] wrote:

Quote: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)

Julian can you clarify yiour steps
\"Open comfigurator and sign in, and see new keypad in Red\"

Do you mean just start comfigurattor without any file? or do you open the lastfile
What do you mean \"sign in\' do you mean press the login button?

Just Log in will not make any changes to the modules.
Do you mean do a scan for keypads?

Do you save the file with the invallid keypads and open the file again?

This topic has been moved to Comfigurataor as it seems to be a comfiguraor handling issue and not related to firmware

Hi
I have Comfigurator set to load the last opened cclx file.
By sign in I mean I usually select System Info menu action and it pops up a signon dialog box, I enter my code and once the info dialog is returned I close it and then go to the modules tab and I see a duplicate.
J

what you describe is the result  of a Scan for modules and not log in. Transfer System information also does a scan for modules
This is why we were unable to duplicate your problem. We just logged in and did not see the problem with the extra module

Do you know what is the firmware of the KP04?

I\'m working away from home this week but think its 1.08e

Julian

It\'s not Keypad firmware related. I simulated this using my Simulator (firmwares 0000, 1.010 and even fictituous 7.001) and it seems that it\'s something in Comfigurator itself. Strangely, in my case, it\'s always a KP04 that is the phantom keypad.

Ingo

We have found the cause of the problem

If an old  KP04 before 1.010 that does not report its firmware version during the scan is in the system (ie it reports version Unknown like in Julian\'s screenshot) , when you save the file and open it again, a new scan will result in another KP04 with status \"not found\"

This wil be fixed in the next comfgurator but as workaround, please delete any unknown KP04s before saving the file. Right click on the keypad on the left pane and select Delete

The phantom keypads problem has been fixed in Comfigurator 3.7 beta
Old keypads may not be able to be scanned but they will not cause communications failures by adding extra keypads in Comfigurator

The phantom keypad issue also occurs with UCMs

I was updating the firmware of products in our stores, i managed to create phantom UCM\'s when scanning older versions of firmware.

Do you have a release date for next comfigurator

Comfigurator 3.7 is in beta now, it will include support for new versions of Zwave, Heatmiser and GSM and also has many improvememts
see http://www.comfortforums.com/forum20/3453.html

It will be a few weeks before this is ready for release

The problem with the phantom keypads being added each time a scan is done has been fixed in Comfigurator 3.7.6, seehttp://www.comfortforums.com/forum20/3543.html

If a phantom keypad firmware < 1.010 appears after a scan and is shown in RED and with Status NOT Found, writing to Comfort will NOT add this keypad to the Number of Keypads and so will not cause a Communications Failure Trouble alarm.

Modules which are NOT found will not be added to Number of modules