Texecom Elite 48 can't disarm

[Ingeneer]

I have a Texecom Premier Elite 48 + Smartcom. Also have Wintex.
It was all working well until this weekend when a PIR sensor had a radio problem when arming. Investigated. Seemed ok. Battery ok, etc, etc. Checked with Ricochet - all ok. And then I made the mistake of getting all the information from the system with Wintex, changing something (banner) and sending it back. Computer crashed mid transfer.

Got the system back after it time locked out. Texecom connect/Smartcom setup was scrambled. So Wintex eventually back on line.

The problem now is that I can enable the system in any and all zones via the panel, but can't disable anything except via the key fob.
When I arm the system the banner disappears and it just shows date/time on the keypad. I think it used to display the banner
I can't enable or disable any alarm via the Connect app (Error: Alarm state cannot be changed, please check at the panel)
At the keypad it just returns having told me that it's armed. User has allow arming/disarming.

Created a new user - that has identical problems.

So, worst case, the system is scrambled and I need an engineer. Best case - someone here has some ideas - UDL codes, Smartcom setup, User configuration?

 

[secureiam]

Sounds like you have made a common mistake sending data across when the wintex file didn’t have all the info in it to send across.

The Texecom cloud account may have a backup but as this seems to get periodically updated after changes made it may no longer have a backup to reset the panel.

I may be able to get the system useable over the phone /video call.

Do you have a pc or laptop and a usb coms cable ?

 

[Ingeneer]

I did have all the information, so not that basic mistake! I requested all the information first, changed a minor part and sent it back. The problem was the computer crashed during the transfer so incomplete info went back.

The cloud account won't have a backup. I only have the cloud account for Connect (Texecom don't really want DIYers!)

Yes I have a laptop and a usb comms cable. Although couldn't get that to work to communicate on a com port. I do have the interface, but no ribbon cable to the board.

I also have a flasher interface. I used that to update to V5.00.02 some time ago. I was wondering about updating to V6 to fix the problem, although it appears to be parameters rather than basic code. An installer with a cloud account could, of course, just update the firmware.

 

[secureiam]

so you should be able to resend the data if you have it all in Wintex and that should straighten it back out.

I don't have an end users account and therefore cant comment on what you have access to or not with any degree of certainty but know others that are end users that have updated their panels from the cloud platform, but maybe they registered as an installer rather than end user.

However, regardless of having the programming feature the cloud takes a back up, this is for when you flash upgrade the panel, however you are saying the user account doesn't have that option?

for example you can change the user code in the panel and it will update the cloud of that change, so the problem is the backup isn't always there and not seen a list of backups available in the cloud for you to select.

The reality is if its crashed because it disconnected in some way during the use of wintex, then you should be able to reconnect and reinject the profile back in to the panel.
If you cant reconnect, need to know the connection method you are using so I can advise on what you need to do.

from example wintex via smart com would be different to usbcom cable.

In general a usb com cable requires a com port that is not programmed in use.
If it is corrupted and this doesn't work its probably quicker to start from scratch clearing wireless devices defaulting the panel, flashing it up and defaulting the panel as normal and then setting up from scratch.

It isn't common for the panels to become corrupted and unrecoverable completely there are stages to go through to avoid extra work potentially but the worst case is if they dont work its a flatten and flash and reprogram from scratch.

 

[secureiam]

And then I made the mistake of getting all the information from the system with Wintex, changing something (banner) and sending it back. Computer crashed mid transfer.

I have to assume that you had the radio/ ricochet config on when you recieved the info and that you saved the file and sent the info back, if you have the fikle saved with all the info in you should be able to send it back to the panel

 

[Ingeneer]

I was connected to panel from Wintex using Smartcom. I've now got it reconnected. The com parameters were initially corrupted and Wintex wanted the appcode in order to reconnect.

Tried sending the received configuration, but no luck in fixing problem. Corrupted configuration seems most likely, but it's not working with any minor changes to fix the problem.

I have a 'cloud' account because Texecom need that for 'Connect' - and they no longer wish to support DIYers! I'd need to have a registered business and VAT account to go to the next stage of being able to manage it from the cloud. They stopped DIYers like myself registering for more access years ago.

Yeah, worst case might be to reset to factory defaults, configure to allow Smartcom and Wintex, and then update the configuration. Just time consuming! So I guess a trade-off of my time versus paying someone.

 

[secureiam]

If you have the full wintex profile you saying it not going across?

 

[Ingeneer]

A full profile is going across, but the original got corrupted in the computer crash.

Communication via Wintex and Smartcom is now ok - it's just that the alarm system isn't functioning re arm/disarm. Arm is ok on the keypad. Disarm doesn't work on the keypad except via the fob. Texecom connect has information, but doesn't allow either arm or disarm.

 

[secureiam]

Sent you a pm, can take a look if you want

 

[secureiam]

It can’t be corrupted sending in that it would have to been corrupted in the import

 

[marcosmurab]

I have a Texecom Premier Elite 48 + Smartcom. Also have Wintex.
It was all working well until this weekend when a PIR sensor had a radio problem when arming. Investigated. Seemed ok. Battery ok, etc, etc. Checked with Ricochet - all ok. And then I made the mistake of getting all the information from the system with Wintex, changing something (banner) and sending it back. Computer crashed mid transfer.

Got the system back after it time locked out. Texecom connect/Smartcom setup was scrambled. So Wintex eventually back on line.

jiofi.local.html tplinklogin​

The problem now is that I can enable the system in any and all zones via the panel, but can't disable anything except via the key fob.
When I arm the system the banner disappears and it just shows date/time on the keypad. I think it used to display the banner
I can't enable or disable any alarm via the Connect app (Error: Alarm state cannot be changed, please check at the panel)
At the keypad it just returns having told me that it's armed. User has allow arming/disarming.

Created a new user - that has identical problems.

So, worst case, the system is scrambled and I need an engineer. Best case - someone here has some ideas - UDL codes, Smartcom setup, User configuration?

The Texecom cloud account may have a backup but as this seems to get periodically updated after changes made it may no longer have a backup to reset the panel.