Comfort Home Automation/ Security System Forums Home
Home Search search Menu menu Not logged in - Login | Register

Keypad scan adds invalid keypads
 Moderated by: admin Page:    1  2  Next Page Last Page  
 New Topic   Reply   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Monday Apr 29th, 2013 09:05 am
   PM  Quote  Reply 
1st Post
Howser
Member
 

Joined: Monday May 22nd, 2006
Location: Pretoria, South Africa
Posts: 196
Status: 
Offline

  back to top

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.



 Posted: Monday Apr 29th, 2013 09:13 am
   PM  Quote  Reply 
2nd Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 519
Status: 
Offline

  back to top

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!



 Posted: Monday Apr 29th, 2013 09:29 am
   PM  Quote  Reply 
3rd Post
juwi_uk
Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1246
Status: 
Offline

  back to top

Happening to me regularly.

Update: I should add it's only on my KP04.

Last edited on Monday Apr 29th, 2013 09:54 am by juwi_uk



 Posted: Monday Apr 29th, 2013 11:32 am
   PM  Quote  Reply 
4th Post
wiredhome
Comfort Distributors


Joined: Thursday Apr 12th, 2007
Location: Dublin, Ireland
Posts: 81
Status: 
Offline

  back to top

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?



 Posted: Monday Apr 29th, 2013 12:09 pm
   PM  Quote  Reply 
5th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 546
Status: 
Offline

  back to top

Me as well.

Last edited on Monday Apr 29th, 2013 12:09 pm by Ingo



 Posted: Monday Apr 29th, 2013 02:41 pm
   PM  Quote  Reply 
6th Post
juwi_uk
Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1246
Status: 
Offline

  back to top

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

Attachment: Scan.png (Downloaded 92 times)

Last edited on Monday Apr 29th, 2013 02:50 pm by juwi_uk



 Posted: Monday Apr 29th, 2013 02:47 pm
   PM  Quote  Reply 
7th Post
juwi_uk
Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1246
Status: 
Offline

  back to top

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



 Posted: Monday Apr 29th, 2013 02:56 pm
   PM  Quote  Reply 
8th Post
juwi_uk
Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1246
Status: 
Offline

  back to top

Also why it seems do I get a

< KL00010000

every time a UCM ID u? command is sent; is this right?

J



 Posted: Monday Apr 29th, 2013 03:31 pm
   PM  Quote  Reply 
9th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 546
Status: 
Offline

  back to top

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



 Posted: Monday Apr 29th, 2013 03:38 pm
   PM  Quote  Reply 
10th Post
juwi_uk
Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1246
Status: 
Offline

  back to top

yes but sending for every command seems a bit overkill.



 Posted: Thursday May 2nd, 2013 12:56 pm
   PM  Quote  Reply 
11th Post
mikegriff
Member
 

Joined: Saturday Aug 19th, 2006
Location: United Kingdom
Posts: 94
Status: 
Offline

  back to top

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

Last edited on Thursday May 2nd, 2013 01:00 pm by mikegriff



 Posted: Thursday May 2nd, 2013 01:37 pm
   PM  Quote  Reply 
12th Post
juwi_uk
Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1246
Status: 
Offline

  back to top

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



 Posted: Thursday May 2nd, 2013 05:21 pm
   PM  Quote  Reply 
13th Post
mikegriff
Member
 

Joined: Saturday Aug 19th, 2006
Location: United Kingdom
Posts: 94
Status: 
Offline

  back to top

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

 
 



 Posted: Thursday May 2nd, 2013 07:19 pm
   PM  Quote  Reply 
14th Post
juwi_uk
Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1246
Status: 
Offline

  back to top

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



 Posted: Friday May 3rd, 2013 04:13 am
   PM  Quote  Reply 
15th Post
hendy
Cytech


Joined: Wednesday Sep 19th, 2007
Location: Singapore
Posts: 221
Status: 
Offline

  back to top

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).

Last edited on Friday May 3rd, 2013 04:15 am by hendy



 Posted: Friday May 3rd, 2013 05:28 am
   PM  Quote  Reply 
16th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 546
Status: 
Offline

  back to top

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



 Posted: Friday May 3rd, 2013 06:53 am
   PM  Quote  Reply 
17th Post
hendy
Cytech


Joined: Wednesday Sep 19th, 2007
Location: Singapore
Posts: 221
Status: 
Offline

  back to top

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?



 Posted: Friday May 3rd, 2013 07:45 am
   PM  Quote  Reply 
18th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 546
Status: 
Offline

  back to top

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



 Posted: Friday May 3rd, 2013 08:02 am
   PM  Quote  Reply 
19th Post
juwi_uk
Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1246
Status: 
Offline

  back to top

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



 Posted: Friday May 3rd, 2013 08:58 am
   PM  Quote  Reply 
20th Post
hendy
Cytech


Joined: Wednesday Sep 19th, 2007
Location: Singapore
Posts: 221
Status: 
Offline

  back to top

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.



 Current time is 09:33 pmPage:    1  2  Next Page Last Page  
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems