Manual for Edwards System3 ??

If it's a FireShield series panel I have not only the manual but the software and the engineering design manuals. The help system for their software has multiple references to someone named Leuck, who insisted I wasn't working on it. :^)

Thanks everyone who replied, and Mr. Rojas for the emailed copy. I appreciate it!

Great. Can you send me the software? Put it up on rapidshare or something if it's too big to email.

Thanks, G

I never said you weren't working on it I found it funny you did the helpfile, apparently your "team" did the real work

Anyone can make a helpfile

Sorry, I can't. I promised in writing not to make copies and such. BTW, my version has the "back door" to bypass program access codes. It displays the code even if it's unknown to me and then gives access as if I'd entered the code.

My team consists of myself, my brother and my sister. I write code for simpler projects. My brother wrote the main app and, with help from my sister, designed the schema and the XML. On this job I did the help system. It was the first I ever wrote and Edwards said it would be the standard by which all future help systems would be judged.

Yes. I saw the one you worked on. It's very simple, uses the most basic features and looks amateurish. No one would have paid you to do that kind of sloppy work. Perhaps that's an indication of the kind of field work you did until they finally pulled you into the office.

Nice, I'm sure that's comforting to Edwards customers

Like I said you wrote the helpfile, and I seriously doubt you've seen my work otherwise you would have stole the information in it already

I doubt the actual customers ever see it.

I saw it and it includes some text I donated.

AAAHAAAAAAHAHAHAHAHAHAHAAAAA!

sure.

those aren't Edwards customers

HAHAHAHAHAHAHAHAH!!!

Do tell what I supposedly stole from you

I believe that is the double super secret access code.

I don't have a hasp for it anyway. This is the first EST3 I ran across.

I put your name in there, too, since you didn't believe I was working on it. :^)

I doubt you've ever installed one of their systems.

Hey, moron. Try reading before answering next time. Somehow you missed the word, "donated."

If you knew anything about the design of FireShield panels you'd would know that lockout codes on Edwards are a function of the software -- not the hardware. In designing the software we started with the program able to access the panel with or without the correct code. Edwards connected a working panel to the power and phones so we could test the communications module.

BTW, the entire program is modular, allowing Edwards to add various panels at will simply by changing the XML schema. It was the first time this technique was used for their systems. Every major I/O function of the software uses the same modules, with the GUI being modified to fit the type of data fields for each screen by the schema. Larger, addressable systems can also be added but a few additional modules would need to be added. Since GE bought them out, they've used the same technique on their own software designs. I guess they like what we did.

BTW, I didn't just write the help system. I designed the user interface, taught my partners how the systems work and sat in on engineering design meetings at Edwards. Though my primary purpose in being there was to make certain the software would accommodate changes in the final product, I also had input on the features of the panels. Since I was the only one at the table who had actually installed fire alarm systems for a living they wanted my input. It was a lot of fun, besides mildly lucrative.

I know you're such an asshole that you'd rather mock than admit that I'm telling the truth, but that's alright. I'm still telling the truth and you're still an asshole. You proved that once again when I tried to be nice to you recently. It's a shame you have nothing of value to add to most of the threads here -- just snide remarks and general meanness.