Galaxy 'guru' Required Please.

[Thunderass]

Evening all.

Been a while since I was last on here, but still prooves to be the best place for advice and help.

So here goes-

Galaxy Dimmension 520.

Large site with loads of 'security'programmed zones - PA's, firedoors etc and several groups in use (A1 to B8).

On Tuesday we had the system inspected-everything is tested, more in depth than any NACOS or NSI inspection.

Everything worked sweet, apart from a slight mix up in labelling of a few sensors.

On these particular systems there are Intelligent Sounders fitted which use a neg trig off an output.

So, any security zone opened triggers the output and thus the sounder.

No problem there.

However- the next day as requested an additional keypad was fitted into the data bus on line 4.

Since then if any output is prog'ed as 'security' the sounders keep activating.

But, this only happens on groups A1 to B2.

If i re-programme anything on the system to groups B3 to D8 there is no prob. and the output works fine!

For example:

On group A2 there are 3 PA's operating as security so only to activate a local IS.

If i have my IS prog'ed to security - it triggers straight awy.

If i relocate A2 to say C1, this does not happen and the o/p works ok.

I have checked connections and earths and data and neg's, but all ok.

So why? is this only happening on Groups A1 to B2 and not on the rest????

I also tried having group A2 empty with no zones - still happened.

I also tried a restart - still happened.

I tried Honey. Tec to be put on hold for 20 mins then gave up.

I am pulling my hair out!

I understand that the Galaxy data AB is very sensitive, but I am not new to this.(buggered one before - expensive way to learn)

Is there a Galaxy Guru out there sitting on the top of a mountain - Help please.

Many thanks.

Thunderass

[whistle]

I have had software problems with the dimension 96 and groups.

Still not got to the bottom of it yet.

[Thunderass]

If it was a software 'glitch', surely it would affect all the groups, not just A1 to B2????

This is the first time of may 520's that i have fitted.

[james.wilson]

New one on me.

The only thing id try after what you have done is a copy, cold start and an overwrite.

James

[Alex]

I don't think it has anything to do with a data cable fault. I had similiar glitches before, where the outputs stopped working properly. I would try what James suggested first. Worst case you might have to default and reprogram the galaxy manually if the data is somehow corrupted (if you just copy the data back over the fault might come back but if you program the galaxy manually it should be OK). Also, you could try to reprogram an output as spare, then restart the panel and then reprogram the output back to what it what it was before. that worked for me before but not always.

[Thunderass]

Problem solved.

A dodgy RIO that was working ok in conjunction with a faulty DT.

Replaced both and the system is or was sitting sweet.

The was being that when I was lidding up the main control panel - without warning the whole thing crashed - complete data F.U.B.A.R

No data, no bleeps , no peeps - nada.

spent the next two hours jaw open just gawlping and jibbering "how"?

outcome - time now 19:30 where do i get a panel from at this time of night?

drove 64 miles home, to get a spare, then the 64 miles back to the job.

spent the rest of the night and morning replacing the panel, reprogramming and testing the whole system.

at the time of typing this all's well, no callouts yet.(not seen my bed since 05:30 Monday)

the morale's to this story are thus:

1. invest in a Spi key.

2. invest in a Spi key.

3. invest in a Spi key.

4. learn how to setup galaxy software on my laptop.

5. and the biggest morale of all - when fitting a new system where the customer wants to retain the existing panel - make sure that those who installed it originaly and hole cut the housing to fit the cables, have cleaned out all the burrs and shrapnel sitting behind the pcb.

Thus when you place the lid on, you dont have the fear of pressing the cables against the pcb and onto the metal c##p behind!!!!!!!!!!!!!!!!!!!!!!

This as most common sensed persons will know, is a good cause of shorts!!! and bloody long nights!

Thank you to you guys with your suggestions, always good to know that there is help out there.

Ps If the nice man who aided me on the blower last night is part of this community - thank you again.

Kindest regards

Thunderass