Head Scratcher

[Elliotrender]

Right I have a job which has been installed and working perfectly or for 2 years, then six weeks ago it started to go wrong.

The job has a Scantronic 65en installed

3x rkps all wired on network 1,

Next to the control panel there is a msnode address 2 wired on network 2,

There is also an mspsu address 1 wired on network 2 fitted about 50m away,

All detection devices are wired 2k/4k

As I said the job was working fine, then I started getting random tamper faults on the devices wired on the mspsu so zones 2011 to 2018, no standard tamper faults on any of these zones, all zones are wired on individual cables, checked for ac induction on the mspsu found 10v induced fitted a act fitler and got it down to 0.2v also fitted one on the control unit aswell as that was at 7v induced. Job was ok for 2 days then again random tampers on a mixture of zones from 2011 to 2018. So I changed the mspsu. Again ok for a weekish, then same again. So fitted a stand alone 12v psu and a msnode (commoned up the negatives) ok again for awhile, then again same faults, control unit got changed and programmed from scratch and not upload to the cu incase there was some bug there.

Been ok for 2 weeks and again same problem.

All cable runs are ran surface and away from all higher voltage cables, I installed the job was know where they have been ran and was able to check them easily

But I'm running out of ideas any help would be much appreciated

[datadiffusion]

As you say the job is a few years old and has been fine so far. You've replaced the CU and MSPSU (twice, effectively)

and you're still getting the faults.

 

Do they happen at the same time of day?

 

Is there any chance it could be a loose connection, even with all the changes? (I had this on a 95, system would work but did exactly the same, took ages to find...)

 

Is there any chance it could be the original MSNODE??

[Elliotrender]

I haven't checked each end of line connection (4x contacts HD 2G, 4x texecom QDs) as the faults are in no pattern or on the same device it's always a mixture of zones, but usually 2 at a time.

The MSNODE was straight out the stores and not pre used

There is no connection with times however I have never been called out after 10pm the business works 7am till 9pm

The CU is powered from the office side of the building, a stardard RCD DB style, on its own breaker, the MSPSU now PSU is spurred from a socket in the workshop which is 3 phase, my next thought is to change the phase,

We have been having a few AC induced power problems on scanny control panels at the moment but mainly on upgrades from aritech panels CD range, so I'm not sure if I'm over thinking the problem, when it's looking at me straight in the face..

[sixwheeledbeast]

Tried ACT Mains Filters on MPSU and CPU?

[timmo66]

Whats the mains reading?

[Elliotrender]

Not sure on the mains reading I'll check next visit.

And ACT filters were the first thing I tried normally work great, but not this time, I also fitted spike suppressors

[Couger]

Can't really add anything apart from never gets these issues on texe gear never had ac related issues rip it out

[datadiffusion]

Just like the 8** / 8136 series before it, the common platform series didn't last 5 minutes before it too was binned for the i-on, with the 9xxx outliving it all...

 

For the OP I suspect it has to be something to do with a LV cable issue or existing node rather than AC power, because I can't believe after all those years

the supply is suddenly duff or overloaded with nastiness to the extent it would effect the CU and the MSPSU in two different locations / phases.

 

Also OP, I wouldn't worry a bit about differing phases being a potential issue, personally.

[ian.cant]

You could put relays on all the zones which would allow you to figure out if the problem is cable or device related as opposed to node related maybe?

[sixwheeledbeast]

Also OP, I wouldn't worry a bit about differing phases being a potential issue, personally.

 

I agree.