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). It does report the current state.
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?

Assuming it was only a Wintex programming update and not a firmware update then defaulting and reprogramming would fix this corruption.

I'd have probably been considering defaulting and recommissioning the Ricochet stuff if you had weird issues anyway.

 

By 'defaulting' you mean rest to factory setup? That is a possibility if I can then completely reload from Wintex after I've reconfigured the interface.

Yes. I personally wouldn't use any profiles and start fresh.

Those saved ones maybe corrupt but you could TIAS if you know what your doing.

Thanks. Sort of confirmed my thoughts.

 

I guess it's a trade-off of my time versus paying someone with a cloud account.

 

Nothing wrong with the Ricochet information - although I do wish it would give better info about battery power.  I think it was just a glitch where something went awry.  It's been ok for several years, barring battery changes. Had to dig out the original info from around a decade ago.

The Texecom Cloud has to cover it's costs somehow.

Glitches are not normal they are usually a hint to something failing or not setup correctly when it comes to Ricochet.

Messing with Wintex is obviously an engineers facility. Messing with firmware or site profiles comes with a risk of a non working system if you mess up.

Firmware flash goes wrong you usually end up with a brick.

Indeed. I took that risk some years ago and it was worthwhile.

Yes, I agree about the Texecom Cloud, just sad that DIYers are pushed out.

 

Updating firmware, and more complex applications than Wintex, cloud computing, operating systems, laptops, virtual machines, etc., etc. used to be my job.  Wintex is nothing unusual.

4 hours ago, Ingeneer said:

Just sad that DIYers are pushed out.

 

I doubt there enough profit I a single panel to pay for  15 minutes of support ?

13 hours ago, sixwheeledbeast said:

The Texecom Cloud has to cover it's costs somehow.

Glitches are not normal they are usually a hint to something failing or not setup correctly when it comes to Ricochet.

Messing with Wintex is obviously an engineers facility. Messing with firmware or site profiles comes with a risk of a non working system if you mess up.

Firmware flash goes wrong you usually end up with a brick.

Out of curiosity, does the panel do the firmware update ? So it loads the firmware and then updates itself , similar to most devices , if the laptop was to disconnect why would the panel brick? Wouldn't it simply fail the update at download stage ?

I don't believe so no. There are two options either PC via flasher interface board or via cloud and Smartcom.

To move the site profile you connect to the panel COM port reading/writing the NVM, for firmware there is a interface board that sits between the PC and flash on a programming port.

If the firmware on the flash is corrupt to the point that you can't put the panel into flashing mode or you can't push any firmware because the panel doesn't respond, then you have a bricked panel.