Alarm Control Panel
hmlittle59
Posts: 404
Hello All,
Has anyone ever integrated a (Carbon Monoxide/Fire) detector to a "Alarm Control Panel" and know how the work or designed your own Custom Control Panel? I've purchased the CM-E1 CO detector and I'm learning the ins and outs of the units connection. Want to be sure an capture all errors and any other things to look out for when making my own "Custom Controller".
Thanks for any knowledge or insight.
Note: I've got a lot of "google"/Douglas Krantz printouts to get me started.
Howard
Has anyone ever integrated a (Carbon Monoxide/Fire) detector to a "Alarm Control Panel" and know how the work or designed your own Custom Control Panel? I've purchased the CM-E1 CO detector and I'm learning the ins and outs of the units connection. Want to be sure an capture all errors and any other things to look out for when making my own "Custom Controller".
Thanks for any knowledge or insight.
Note: I've got a lot of "google"/Douglas Krantz printouts to get me started.
Howard
Comments
Sorry, could not attach the data sheet, it was too big. You can download it by googling "CM-E1 CO detector".
I have all the printouts and then SOME from the CO gas detector, but I'm trying to make sure I fully understand the errors and how they are distinguished (1,2, and 3 with only 2 lines) on the Control Panel and the Circuitry involved. MY pcb already detects open/closed magnetic switch(s), so that part I understand, its the 3rd error that I'm trying to fully understand and make sure that I can detect it or figure out some other way. I do have an extra I/O pin, (Active Low) that maybe I can incorporate.
I have the Parallax (10k/220 ohm) on my I/O pins...This has worked great in the pass and I even have my own Custom switch board (5 keys...up/down/right/left/select) through a MainMenu on Serial and/or Parallel LCD Screen. Just trying to figure in that 3rd error with only (2) two lines. Just hasn't clicked in my mind yet on how to do it.
The CO is something I want to add on. The new PCB's should arrive here by this Saturday and the current layout will detect at lease 2 states.
Hope this gives a clearer insight on my dilemma.
Note: I saw a cheap Control Panel on Ebay ($24.00) that may have the schematic with it that maybe I can learn from.
I did get some Control Panel printout from good ole "Google", mainly "Fire" connection and errors.
Thanks for any help.
Thanks.
Still looking on Ebay for that cheap Control Panel that I saw two nights ago...
Thanks again.
Hello ALL,
After reading the Manual of the unit I purchased and other web. Printouts and various Control Panel manuals...over and over and over again, along with wiring connection, I think that I understand how it works and can now re-re-reorder my OWN PCB and make it work.
That's without seeing a schematic of an actual Fire/Gas "Alarm Control Panel".
My PCB's coming in this week will work as is, but future boards will need a Supervisor Circuit (Loop). Part of the Loop will consist of the 10 k of the (10 K/ 220 ohm) Pull-up resistor combo moved to be the Supervisor Circuit. Meaning, 5 vdc from my PCB will go out and Loop through the 10 K End Of Line Resistor (EOLR) and come back to my PCB and then through the 220 ohm resistor and to the sensing I/O pin.
Now, Just trying to figure if I need a dedicated 'Common' pin per I/O pin or split one (1) per 2 I/O pins. Four (4) I/O's and two (2) Commons. I don't thinks so off the top of my head for now.
Thanks for any input
EDITED...Sorry for not proof reading, was running out the door to visit someone in the Hospital.
In my hast, I did a simple over site about connecting the returning END(s) of 2 Supervisor Circuits to a Common connection.
WRONG WRONG WRONG.
This would connect one I/O to another I/O and during Alarm or Trouble could cause 2 or more I/O pins to go into Alarm at the same time.
OOPs...
Will Cut and Hack on the new new boards coming in to make this work and then re-spin.
You don't need a dedicated common per I/O pin. All the I/O pins can share a single common, although the typical setup is one common connected between two I/O's.