Jump to content
Security Installer Community

sixwheeledbeast

Global Moderator
  • Posts

    8,677
  • Joined

  • Last visited

  • Days Won

    136

Everything posted by sixwheeledbeast

  1. You get what you pay for... As tech moves on it's increasingly common to have local radio attacks on equipment. Wifi jammers are often used to defeat doorbell cams at the moment.
  2. It's down to the ethics of the company. I'm sure some would lock just to make it awkward to move maintainer. There are genuine reasons to lock panels from the installers POV tho:- You are protecting the company from a malicious claim, say if the system failed to operate because it had been modified by an end user or another maintainer. Making sure the system is maintained as per any out of hours agreement and that expiry of this is displayed on the system. Maybe the system hardware isn't fully owned by the customer, it could be leased or yet to be paid off in full. There is also a possible argument that the programming of the system is the intellectual property of the maintainer, even if you own the hardware.
  3. I would assume some local co?
  4. Did you read the thread? They are obsolete, upgrade the system or take a risk on finding an equally or less faulty used one.
  5. I'd say someone tried the code defaulting procedure and got it wrong or the panel is knackered.
  6. I still think it's the G3 part that has the fault from what you have explained so far, so wiring bell as G2 like I already said would stop the fault. The other option is getting someone in that knows what they're doing.
  7. Don't really use the wireless keypads. I know you have to wake them up before starting exit procedure if using a prox tag. Otherwise they should work the same. You say your entering the code and nothing is happening so maybe it's not enrolled correctly. Delete and enroll again?
  8. So you've proven the wiring and that it's likely the programming... Yes, you should always default them from new.
  9. What are the comfort LED's doing? Have you triggered it with a bell test or giving the trigger a negative.
  10. If it's "Aux fault" and not "bell tamper" then I don't think it would be the bell tamper? I recall EN was minimum 2" fixings for warning devices but I don't remember if it was overall screw length or penetration. It is daft to have 2" screw and more than half of it not in the wall. I don't like these for this either but it apparently makes them easier to be lazy measuring up for drilling.
  11. The wiring is poorly terminated but it doesn't look loose... There are no resistors required for compatible panels/inputs. You shouldn't mix G3 Aux Fault and Aux Tampers together, but it doesn't seem to have been wired it like that anyway. You haven't terminated the test terminal at the panel from what I see, so it's not doing the G3 periodic testing which I expected to be part of the issue. I'd say it's DIY so just follow the instructions for Grade 2 installation using 5 wires. Make sure the bell hold off and battery works see if the fault clears.
  12. So you have it wired as a Grade 3 bellbox and it's maybe failed one of the G3 self tests I'd guess? Assuming you have everything wired and programmed correctly on a Premier panel that is.
  13. There's gunk on the pyro I'd say it needs replacing anyway. As above for what the colours are, weird as those may be...
  14. Don't come back here after you have cocked up looking for free help and tell those people that do it everyday for a living they're wrong! You did actually say "Theres no need for a service, or calling an engineer" but you don't seem to understand why it needs servicing. If you want poor advice or copies of random copyrighted manuals from people that aren't trade verified, go and find some other forum...
  15. Don't use Scantronic regular but to reset a tamper I'd expect you need the Master user code if not set to Engineer Reset. Sounds like you maybe best to have it serviced and re-programmed so you have the Master code.
  16. So it doesn't reset with your Master user code? You definitely have the lid on and closed the lid switch correctly?
  17. It's not a customer facing interface so I don't see it as an issue. If done via Smartcom and engineers Cloud account, you avoid this issue as well.
  18. Possibly but it's hard to say if it was fully decommissioned correctly when they came out to silence it all those years ago. The alarm wires should be low voltage so your not likely to get a shock from a PIR, if that's what you mean by safe. I have been to a job were someone had suppose to "decommission" a system, all they did was remove the power to the internal siren, bell trig and keypad... PIR's and bell were still powered.
  19. 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.
  20. 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.
  21. 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.
  22. 1) In most cases yes but updating them should be considered. I would usually say on a takeover upgrade ideal is to replace the electronics and test the wiring is sound for re-use. 2) Forget the Gardtec if you need to update. It EOL, better to replace at your convenience before your forced to by a failure.
  23. 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.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.