Galaxy Flex V3 50n - Recognition of TCC8M Keyfob

[Angiolino]

Hi,
I had to replace the motherboard of a Galaxy V3 50 about 10 years old. I kept the original comm and wireless modules. All was fine, but the old keyfobs would not be recognized any nore, and I purchased two new TCC8M. Got problem, though, when I tried to get them recognized using the 42.1.User,10 function. I found it was almost impossible to do it. I got one of them recognized, by pure chance, after trying every possible combination of buttons... The second one is still unrecognized. What could be the reason?

 

[GalaxyGuy]

When you first sync the fobs with the portal, a rolling code enrollment mechanism is initiated. This stops someone scanning the RF and replaying the transmission. To start the process off again, remove the battery from the fobs and short the pins in the fob. Once you power them up again by adding the battery, they will be recognised. Also, ensure the latest panel firmware, as I think the RF registration timeouts were increased. Watch out for changing fob modes from Alpha to V2 and vice versa, as this is done by pressing keys on the fob whilst inserting the battery.

See the image below for information on the power up sequence to set the mode. Alpha is supposed to be more reliable.

 

[GalaxyGuy]

 

[GalaxyGuy]

 

[Angiolino]

GalaxyGuy, thank you. I saw that I had not paid attention enough to the specs, because at the beginning I just thought of colors (the old ones from TCB800) and not in terms of actual arrows indicating the buttons, from the specs. This error had caused me other problems when I tried out the TLC the first time - after the chance recognition of one TLC.
I was trying to set the system instead of unsetting it. Thought the TLC programming might have been faulty, or that something was wrong with using the TLC with the Manager identity, or that the protocol was the wrong one.... So I cancelled the Manager assignment, but without any improvement.
Recognition now OK, operation OK.

 

[Angiolino]

Dear GalaxyGuy,
I have serious problems with the usage of TCC8M.
If I, i.e., ask system status after partial set, by pressing button 4 on the TCC8M and do it 2 or 3 times at short intervals, I do not get consistent answers. At the first attempt i get the three leds blinking together several times, at the second attempt they blink serveral times one after the other going round. But I had other strange and unconsistent answers too.
Also:
If I do partial setting of the system on the keypad, and then go out, the system sets correctly. When I come back, open the entrance door, take the TCC8M and press the black button to reset, it happens (but not always) that the first time I try it, the led blinks several times then remains off, but nothing happens as if it would not be "heard". I press again the black button: the led has one blink and goes off. The third time the system answers correctly. But: If I set partial again, go out of the door with the TCC8M in my hands, then shortly after do unset by pressing the black button, without before coming in, the system answers correctly at the first attempt.
I had never such unconsistencies when I used the old TCC800.
What is going on? What can I do to find and correct the problem?

 

[GalaxyGuy]

I wouldn't use the fob LEDs as an indication of correct setting and unsetting - they seem to be sequence dependent, and an inadvertent keypress when out of range will knock the sequence out. It's better to use remote monitoring push notifications to give the set / unset notifications.

 

[Angiolino]

Dear GalaxyGuy,
I have solved my problem by resetting fully the keyfob, after having removed the battery. It now reacts consistently and correctly. I have however doubts about the protocol before removing the battery. Could the unconsistency have been causewd by the V2 protocol?
Thank you,