Texecom Chime Time

[MeRon]

Yes another Chime question

It has been working great for years and I recently replaced my Elite 48 panel and added a Smartcom as my comip wasn't playing anymore.
After getting it back together I found that I couldn't just press the chime button on the keypad to silence it temporarily as before.

I use Areas for arming rather than omits. I find it more convenient.
I have the chime on my front door, a pir that looks at the front of the house for visitors, a pir that covers anyone around the front door and a pair of beams on the driveway for vehicles. The two front pirs are Area D. The two beams are zone 14 in Area A and programmed as a timed foyer. Area B is the perimeter and area C is internal.

I have Auto Chime C2A set on areas A,B & D as those areas contain Zones with chimes. This is recent as previous to the new panel I only had Area D on C2A and by Pressing Chime on the keypad it enabled or disabled all chime Zones in all areas. I changed it in desperation as I can no longer switch off the chimes with the keypad.

My previous panel was on firmware 2.11 and the new panel is on the latest 6.x
My Configuration is not set to Grade 3 but I suspect something in the later firmware changes something that I need to know about and take account of
I am also wondering about the serviceability of my keypad but think that is probably ok as the chime button does give the different beep sounds from the keypad when switching 0n/off. It just does not disable the chimes!

Any pointers gratefully accepted.

 

[secureiam]

I would compare the programming in both panels in the first instance for differences.

Silence what exactly?

I think your sying the chime isnt toggling on nd off with the chime button??

 

[sparkymarka]

Don’t you have to do something different to turn off chime when you have multiple areas on one keypad ?

 

[sparkymarka]

As below

 

[MeRon]

Thanks for taking the time to reply.

Sorry for not being more explicit but you got it anyway. Yes, toggle on/off.

I did setup two instances of wintex side by side using an old backup and the current one.
The old one was on firmware 2.11 the other on 6.# but I haven't manage to spot any differences yet!
I will have another go though.

I did make some small changes on the new one but I don't think it should have effected the chime toggling,
When my Area A was time arming it would beep for 5 minutes which would drive me mad. It took me a long time to stop that but was actually just simply turning off exit tones from the key pad.

Looking at the screenshot below I just remembered that the info LED also is not working as it used to.
When the Chimes were on the info LED would be on and toggling the chime off would turn off the LED.
As the chime is not turning off the info LED is staying on as it should so it would seem that the output is not changing when the toggle is used although the toggle does make a different sound for on and off which leads me to believe that the keypad button is working ok
As the outputs are not physical I suspect it is a software switch. Looking at the Wintex/Diagnostics/Sytem, C2A seems to be permanently active even though I have disabled it in area options

Just to be certain I have just put the exit tones back on and checked the info LED. As expected it made no difference so the keypad was set as it always has been in 2.11

What could keep C2A lit even though it is disabled in software?

Regards

 

[MeRon]

Guys, thank you for your inputs. All fixed.

sparkymarka​

I puzzled a lot over your comments about multiple areas especially as it all worked on my older panel and 2.11 firmware. Ultimately you were correct in that I did not need to have multiple areas or C2A for the chime although the chime zones were in multiple areas.
The problem turned out to be in the pic above. Use Keypad Areas should have been enabled.

secureiam​

As you suggested I eventually discovered the difference from an older backup. It took me a while as I kept bypassing the keypad even when researching the info LED.

Several months ago I had a stoke which wiped out a lot of my technical knowledge. Not quite as bad as it sounds because it seemed to leave a shadow of that knowledge which just needed relearning. Easier said than done. I am still relearning so will probably be back soon