Tnx,
Andrej
So what exactly is a PC-Link connector?
Dan Lanciani
ddl@danlan.*com
| It's a hardware link between the DSC Power832 panel and a PC serial port.
Is this for up/down-loading only or does it support some interactive uses
that might be good for automation? Does the Maxysys have something similar?
(Maybe a v3 feature?)
Dan Lanciani
ddl@danlan.*com
Dan Lanciani wrote in message <312...@news.IPSWITCH.COMM>...
Regards,
Robert L Bass
=====================>
Bass Home Electronics
The Online DIY Alarm Store
http://www.BassHome.com
80 Bentwood Road
West Hartford, CT 06107
860-561-9542 voice
860-521-2143 fax
=====================>
BTW the Link comes in DB-09 and DB-25 variants, which also work well with
the MD-12 modem, contrary to what DSC told me :-)
Now the RJ-45 (?) on the 5400 is for DVACS! Not Automation, the other RJ-12
is for a serial port connector (again that little deal with the link works
here also.). to link to a serial printer or serial port of a PC.
You are thinking of the 5580 with the RJ-12 port for a Powerline interface
module for home automation.
FYI.
Now getting back to the original question, you mean the little PCB board?
Sorry I don't have a schematic.
James Friesen, Lucretia Enterprises.
Bruce Thornhill wrote in message <721g86$gtt$1...@nntp3.uunet.ca>...
>This one is just for up/downloading. There is another serial port on the
>PC5400 which could be used for home automation. The port is out-bound
only,
>but it shouldn't be hard to write drivers for it.
>
James Friesen, Lucretia Enterprises.
Robert L Bass wrote in message ...
>The link is primarily for up/downloading. I haven't checked on
>compatibility with Maxsys. There are others more knowledgeable on that
>here. Perhaps someone will reply.
>
>Regards,
>Robert L Bass
>
>=====================>
>Bass Home Electronics
>The Online DIY Alarm Store
>http://www.BassHome.com
>80 Bentwood Road
>West Hartford, CT 06107
>860-561-9542 voice
>860-521-2143 fax
>=====================>
>
James Friesen, Lucretia Enterprises
Ken Zeller wrote in message <3645E945...@shaw.wave.ca>...
Can you expand on this a little? For my home automation purposes, I want
to get the current status of each zone (one sensor per zone) from the PC4020
to my computer. I first looked at using the printer interface and parsing
the output. Unfortunately, there is no documented way to make the printer
output convey zone status changes when the system is not armed (and DSC will
not offer any program patches to accomplish it). I also looked at the PC4580
but, as far as I could tell, it merely provided X10 output capability for the
PC4020. It did not provide an automation interface unless you consider the
PC4020 to be the automation controller. I eventually settled on using several
PC4216 output modules configured as zone followers.
The 4216 approach certainly works but it is a bit clumsy. The COMBUS connects
to several PC4216s, lots of wires run to i/o boards, and the i/o boards are
interconnected to a bus that is converted to a serial port. It's kind of
funny to see this big kludge with 4 wires in and 3 out, but many wires in
the middle. :) I would like to find a better way to do this. A patch to
make the printer output reflect zone state changes even when disarmed would
seem the best approach, but even a box that pretended to the COMBUS that is
is several PC4216s while outputting the information on a serial port would
significantly reduce the clutter.
Dan Lanciani
ddl@danlan.*com
Regards,
Robert L Bass
=====================>
Bass Home Electronics
The Online DIY Alarm Store
http://www.BassHome.com
80 Bentwood Road
West Hartford, CT 06107
860-561-9542 voice
860-521-2143 fax
=====================>
Dan Lanciani wrote in message <313...@news.IPSWITCH.COMM>...
Andrej Lipovec wrote in message ...
What you want is a graphic annunciator, with real-time updates. I'm not
overly familiar with graphic annumciators but this should do what you want,
if not then I don't know how. But your approach to the 4580 or the 4400 is
frought with headaches.
Dan Lanciani wrote in message <313...@news.IPSWITCH.COMM>...
>In article <3645E945...@shaw.wave.ca>, kze...@shaw.wave.ca (Ken
Zeller) writes:
>| PC4020 version 3.0 and higher, supports downloading via PC LINK and DLS
>| 2 version 1.31 downloading software. Home automation is lots easier if
>| you use the X10 interface, the PSC04, with the PC4580.
>
>Can you expand on this a little? For my home automation purposes, I want
>to get the current status of each zone (one sensor per zone) from the
PC4020
What has automation and zone status got to do with each other? Can you
expand on this a little?
>to my computer. I first looked at using the printer interface and parsing
>the output. Unfortunately, there is no documented way to make the printer
>output convey zone status changes when the system is not armed (and DSC
will
>not offer any program patches to accomplish it). I also looked at the
PC4580
It just reports stuff that would sit in the event buffer. Perhaps a RE of
this might show some assistance, but too much work for such little reward.
I mean the escort does (Just like a keypad kind of) report this information,
but changes seem to make this impractical for logging purposes.
>but, as far as I could tell, it merely provided X10 output capability for
the
>PC4020. It did not provide an automation interface unless you consider the
>PC4020 to be the automation controller. I eventually settled on using
several
>PC4216 output modules configured as zone followers.
>
>The 4216 approach certainly works but it is a bit clumsy. The COMBUS
connects
>to several PC4216s, lots of wires run to i/o boards, and the i/o boards are
>interconnected to a bus that is converted to a serial port. It's kind of
>funny to see this big kludge with 4 wires in and 3 out, but many wires in
>the middle. :) I would like to find a better way to do this. A patch to
>make the printer output reflect zone state changes even when disarmed would
>seem the best approach, but even a box that pretended to the COMBUS that is
>is several PC4216s while outputting the information on a serial port would
>significantly reduce the clutter.
Ok, I'm certainly confused here?
Care to elaborate for me?
Thanks.
>
> Dan Lanciani
> ddl@danlan.*com
In an abstract, virtual, sense--yes. I want my computer to be aware of
the same information that a graphic annunciator would display.
| I'm not
| overly familiar with graphic annumciators but this should do what you want,
| if not then I don't know how.
As far as I know, DSC's graphic annunciators are merely panels of lights.
You still have to drive them with 4216s. They do not provide a COMBUS
interface on their own.
| But your approach to the 4580 or the 4400 is
| frought with headaches.
The 4580 was suggested by another poster. I asked how it would work.
I don't think it would be useful at all in this case. The 4400 on the
other hand would be ideal if only it could be configured to spit out
zone status changes when the system is not armed. This is not really
a lot to ask--certainly some alarm panels are willing to log zone activity
when the system is not armed. In any case, the 4400 can provide all the
other information about system status so it is still a useful interface
to a home automation system. It can make the computer aware of arming
and disarming along with the associated user. This information may have
a bearing on the activities of the HA controller.
| What has automation and zone status got to do with each other? Can you
| expand on this a little?
An automation controller seeks to adjust the environment to suit the
activities of the occupants by, e.g., manipulating the lights, A/V
equipment, HVAC, etc. It is very helpful to the computer to keep track
of where occupants are and aren't. Alarm zone status often represents
the same information that the computer would otherwise have to get from
redundant sensors installed alongside those of the alarm...
| It just reports stuff that would sit in the event buffer.
Yes, and this is almost the right stuff. If the panel could be convinced
to log zone status changes to the event buffer when not armed, it would
be exactly the right stuff. I've thought about various tricks like assigning
each zone to two partitions and arming one (with no bell output associated
with said partition), but the logic works the wrong way. Multiple partitions
all have to be armed.
| Ok, I'm certainly confused here?
|
| Care to elaborate for me?
I'm not sure which part you want me to elaborate on...
Dan Lanciani
ddl@danlan.*com
Zone status on motion detectors is often used for automation systems to
determine occupancy. The status may be used to turn on lights, warm or cool
the air, etc. A zone connected to a moisture sensor might over ride the
lawn sprinklers if the ground is sufficiently damp already. Motion detected
outside would turn on lights at night, shut down lawn sprinklers during the
day, or possibly start the VCR to record cameras around the perimeter.
>
> It just reports stuff that would sit in the event buffer. Perhaps a RE of
> this might show some assistance, but too much work for such little reward.
Half the reward of a home automation system to a DIY wiz like DL is the work
itself. The other half for many HA enthusiasts (I won't speak for Dan) is
about evenly split between the actual benefits and the gee whiz reaction
from friends.
>I mean the escort does (Just like a keypad kind of) report this
information,
>but changes seem to make this impractical for logging purposes.
>
>>but, as far as I could tell, it merely provided X10 output capability for
>the
>>PC4020. It did not provide an automation interface unless you consider
the
>>PC4020 to be the automation controller. I eventually settled on using
>several
>>PC4216 output modules configured as zone followers.
>>
>>The 4216 approach certainly works but it is a bit clumsy. The COMBUS
>connects
>>to several PC4216s, lots of wires run to i/o boards, and the i/o boards
are
>>interconnected to a bus that is converted to a serial port. It's kind of
>>funny to see this big kludge with 4 wires in and 3 out, but many wires in
>>the middle. :) I would like to find a better way to do this. A patch to
>>make the printer output reflect zone state changes even when disarmed
would
>>seem the best approach, but even a box that pretended to the COMBUS that
is
>>is several PC4216s while outputting the information on a serial port would
>>significantly reduce the clutter.
I imagine a few hours of playing with a scope might reveal the protocols,
Dan. If it was Napco....
> Ok, I'm certainly confused here?
>
>Care to elaborate for me?
There are many things you can do in an automated home based on the condition
of the security system. Zone status changes can tell you much about what is
going on and what needs to be done by the HA system at any given time. By
reading the combus data, one could possibly gain intimate knowledge of
almost every change in real time.
Andrej
(Mark Leuck) wrote in message ...
| I imagine a few hours of playing with a scope might reveal the protocols,
| Dan.
Probably more than a few hours. I did the preliminary investigation. The
protocol isn't trivial...
| If it was Napco....
Yes, that's always something to consider for the next pass. At the time I
settled on DSC, neither company had an interface and Maxsys seemed to have
more expandability as an alarm system (which was my primary goal--automation
is secondary). And even when the Napco interface showed up, they implied
that the protocol was not going to be open. (Actually, I still haven't
seen the docs...) In any case, perhaps DSC will come out with an interface
of its own soon.
| By
| reading the combus data, one could possibly gain intimate knowledge of
| almost every change in real time.
Unfortunately, this is not the case. I did enough research to determine
that (for example) status changes for zones on the main board do not in
and of themselves cause anything to go over the COMBUS. Makes sense
given its intended purpose. So to be useful a home-made interface would
have to emulate something (probably 4216s or a keypad) and fully implement
the module enrollment protocol. Again, non-trivial.
Dan Lanciani
ddl@danlan.*com
Regards,
Robert L Bass
=====================>
Bass Home Electronics
The Online DIY Alarm Store
http://www.BassHome.com
80 Bentwood Road
West Hartford, CT 06107
860-561-9542 voice
860-521-2143 fax
=====================>
Dan Lanciani wrote in message <317...@news.IPSWITCH.COMM>...
>You're paying too much, Mark. They sell at retail for $12.
>
It was an impulse buy, I tend to get gouged when that happens :)
So let me get this straight. You are looking for a module to hook up to DSC's
combus (or just to the main panel) that will allow you to write or have
someone write a computer interface? Are you looking to be able to control the
system through the computer? or is it just an ennunciator. Sounds like this
is something for very large installations? Let me know what you are looking
for and perhaps I can help.
GeoffL
In article <317...@news.IPSWITCH.COMM>,
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
I am not the original poster, but I have a couple of plans for zone status
driving automation:
- Open door from house to garage and garage lights turn on
- Walk into garage at night through open garage door from outside and
motion detector triggers garage lights
Allan.
Stupid answer but I should think the printer would run out of paper if the
printer printed when a zone changed during business hours (I assume this is
a business)
Leave garage door open too long without motion being detected inside the
garage and a piezo inside the house alerts you of the error.
Regards,
Robert L Bass
=====================>
Bass Home Electronics
The Online DIY Alarm Store
http://www.BassHome.com
80 Bentwood Road
West Hartford, CT 06107
860-561-9542 voice
860-521-2143 fax
=====================>
Allan Yates wrote in message <72hiq6$6an$1...@bcarh8ab.ca.nortel.com>...
>In article <AmM22.6888$tF2.4...@news.rdc1.ab.wave.home.com>,
>mail <jer...@home.com> wrote:
>>What has automation and zone status got to do with each other? Can you
>>expand on this a little?
>
It really depends on what the zones are. Most card access systems seem happy
to print a log of each door open/close event (with or without card) at all
hours. An alarm whose zones are just outside doors would use paper no faster.
In any case, it wouldn't hurt to have it as an option...
Dan Lanciani
ddl@danlan.*com