Jump to content
Security Installer Community

james.wilson

Admin
  • Posts

    30,578
  • Joined

  • Last visited

  • Days Won

    281

Everything posted by james.wilson

  1. as that option no longer complies it probably also needs turning on in the programming menu.
  2. Glad you sorted it Thanks for the follow up
  3. ok id leave the rio where it is and disconnect all the circuits at the rio end and link all circuits with a 1k resistor. Then assuming all show 1k closed change each circuit to 2k one at a time. What do you get then? Is all detection cabling new?
  4. are you sure the resistor values are default on the affected circuits. if the panel is showin a 2k resistance but showing closed looks like programming to me
  5. https://www.securitywarehouse.co.uk/catalog/intruder-alarm-c-36/sounders-c-36_45/external-sounders-c-36_45_140/scantronic-replacement-battery-for-760es-sdrrext-p-3836.html These ones?
  6. If its got a chassis number yes. Put the rotten panels in a barn then your golden Not really
  7. i doubt it, is this another one of your bin things you keep on the wall?
  8. this will work for a few months but the battery isnt dead just the timer has shut it off. What it will do when it does start to go flat is anyone guess
  9. wow that bad. I dont think any pro installer will use it yet, but was surprised how ajax did with a self cert. I think any equipment sold to not meet the requirement it claims should be removed and all certificates and insurance revoked
  10. does it comply to en as ajax doesnt
  11. No the hardware may belong to client. The programming does not. I can only speak for myself but unlocking is free at the office or done on site for a visit cost. Noone Imo should lock the programming without a free unlock option. Ewaste is an issue I'd agree
  12. Ive been looking at crm systems I wondered if there would be any interest for a TSI crm system using suite crm?
  13. agreed but as norman check with your insurer the outgoing co still carries liability. some panel log what programming is changed also.
  14. IMO anyone you doesnt program lock (engineer lock isnt the right word)their config will have an issue and so will their insurer. However the programming is the IP of the programmer. The equipment etc belongs to whoever purchased it
  15. re manufacture yes that is why they have defaults. Its the same on intruder and fire, set defaults. If you 6wb program something unfortunately you are liable for it. You may have done it right at the time, maybe 12 years ago, but if anyone inherits your programming thats what they did. Your programming, your issue. Its the way it is today.
  16. Keep a look on what you actually insured for or Do it properly, default the system fully and take it on.
  17. If you did the last programming then the person yes person not co that did that is the one. One would assume no support contract or expired you cant be liable You need to 'prove' it. If you last 'programmed' it your liable. If new co didnt change the 'programming' then whoever last did carries the liability. Bear in mind its not the client you will have an issue with its the insurer. The client wont care because everyone is insured to include this. Unless you reset just the codes and left the old maintainer with all the liability
  18. Its a shame but the original programmer/co keeps the liability. Its something I want to change because it should be the incoming co/person. Unfortunately it isnt. Panels that allow code defaults are a liability. However i know how it looks but check your policy because you arnt fully insured they chase the one that is. If thats you oops
  19. no but it all helps
  20. When doing a take over the panel should always be fully defaulted.
×
×
  • Create New...

Important Information

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