Keypad scan adds invalid keypads

[mikegriff]

I have had this!
7.026 and 7.026
or could be the new configurator 3.6.6 to 3.6.8
the only cure I had was to delete all the keypads and re scan
this cured it
Till the next time
Mike

[juwi_uk]

If you exit configurator and go back in again and login and scan does it find the phantom ones again. It does in my setup.

If not you say deleting all and scan fixes. I must admit I only deleted the KP04 one in my config and left in the KP06 definition so didn\'t test this scenario.

If deleting them all works this would suggest some missing keys un the CCLX file for the older records.

Julian

[mikegriff]

Hi Julian
Sorry I might have confused things
I do a scan
I then end up with my 4 Keypad KP04 and 4 Ghost Red Keypads
I cant just delete the extra ones as the id are then screwed so I have to delete them all
I scan again
I  end up with the right number
I\'m then safe to upload a set up to Comfort

If I want to do it again I have to delete everything
scan and upload
Safely

Mike

 
 

[juwi_uk]

Hmm, same as me.

Chaps at Cytech; have you managed to recreate this yet as you seem a bit quiet in responding on this one?

Julian

[hendy]

I\'m running Comfigurator 3.6.8, Comfort ULT 7.027 and UCM 7.016 (all latest release versions for now).

1. Run Comfigurator and sign-in for System Info inquiry.
2. The two keypads (KP06 and KP04) connected on my test bench showed Status: Scanned. No red additional keypad appear.
3. Exit Comfigurator.
4. Run Comfigurator again and sign-in for System Info inquiry.
5. The two keypads (KP06 and KP04) connected on my test bench showed Status: Scanned. No red additional keypad appear.
6. Exit Comfigurator.
7. The cycle repeats itself from #1.

I did however get a red (not found) keypad if I do the following:

1. Run Comfigurator and sign-in for System Info inquiry.
2. The two keypads (KP06 and KP04) connected on my test bench showed Status: Scanned. No red additional keypad appear.
3. Disconnect KP04 and do Scan for Keypad. Found Keypad010 in red.
   
4. Delete the Keypad010.
5. Exit Comfigurator.
6. Run Comfigurator and sign-in for System Info inquiry. Keypad010 (in red) appears.
   
7. Delete the Keypad010.
8. Exit Comfigurator.
9. Run Comfigurator and sign-in for System Info inquiry. Keypad010 (in red) appears.
10. To counter it. Delete the Keypad010.
11. Save and exit Comfigurator.
    
12. Open the saved configuration.
13. Sign-in for System Info Inquiry or Scan for Keypads will give the correct keypad with no additional red keypad(s).

[Ingo]

This is my scenario.

I\'m running Comfigurator 3.6.8, Comfort ULT 7.027 and UCM 7.019(Beta).

1. Run Comfigurator and Edit the default Connection method to use Network (Local) and add IP of UCM.
2. The two keypads (KT03 and KP04) connected on my test bench.
3. Scan for All Modules, enter LoginID and Scan produces phantom Keypad010.
5. Close Comfigurator and go back to #1 produces the same result over and over.

Ingo

[hendy]

Ingo, how about if you delete the phantom keypad, save the config, exit the Comfigurator and then re-open the saved file to do Scan for Keypads; will this still produce a phantom keypad?

[Ingo]

It\'s not about a saved config at all. I start Comfigurator with a default blank config, change the connection setting to use IP and then do a scan and voila, phantom keypads.

By loading an existing config, doing a scan, deleting the phantom keypads is just fixing the symptoms and not the cause.

Ingo

[juwi_uk]

It\'s worry in that you guys cant recreate this. What else could be different in our setups. We are all so able to reproduce that it hurts!! :0)

Hendy are you testing eth or ucm connected ucm. Im on eth2 if this message makes any difference.

J

[hendy]

Julian, I have tried with both the UCM/ETH02 and UCM/USB and able to reproduce the phantom keypad issue to a certain extent as indicated in my previous post.

And I\'m aware that the countermeasure offered is not a fix for the cause but merely a work-around for the time being (as Ingo has suggested); while at the same time I raised this issue to our software guys.