ECS-L Home Automation and Security Archives
  learn more | view messages for this month | NetBloc® | terms of use | search

Google
 


  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects

Subject:
From:
Date:
ECS Primer
gbailey
Sat, 3 Oct 1998 21:00:28 -0600

Interesting how this topic has come round again. About 2 years ago I set out
on the noble mission of doing exactly this - I got a bit of it done, but ran
out of time to devote to it. I can give you what I have so far to get
started with if you wish. Also, copies of articles I have done in the past
may be of some use.



-----Original Message-----
From: Bill Walters [mailto:wtwalters@home.net]
Sent: Thursday, October 01, 1998 9:51 PM
To: ecs-list@vancouver.ml.org
Subject: [ECS] RE: ECS Primer


Note to all interested parties -

Thread renamed to reflect subject change
========================================

Everyone has made excellent suggestions and I am willing to help
coordinate, I guess, since I suggested it.

I will e-mail Jeff Anderson and request permission to reproduce the
appropriate articles in the "Primer" for ECS.

How should the "Primer" be distributed once completed?  I'd really like
to see it up on Mark's web page for download as well as him providing a
disk of it for new ECS purchasers, but guess my enthusiasm is getting
the "..cart before the horse"

OK folks, those interested, how about some suggestions for an outline:

	1.  Introduction
	2.  Basic Operation of ECS

		- Installing DOS version
		- Installing Windows version

			(& why the differences)


		A.  Configuration
			1.  Items
			2.  Events
			3.  Groups
		B.  Simplest CFG file
			1.  Light Item
			2.  On/Off at certain time
				a.  Logic operators, GT, LT, IS NOW,
					(etc.)
			3.  PLC Item
				a.  Kinds of PLC devices
					1. 6 button console
					2. 22 button console
					3. RF devices
						-keybob
						-universal rf remote
			4.  On/Off with PLC item
			5.  Macro control of On/Off
				considering "time of day"
		C.  What is "ECS Lite Configuration"
			1.  Overview of implementation
			2.  Reorganize Items & Comment
				a.  Lights
				b.  System items
					1. What's "needed" and not
			3.  What Groups show and why they're useful

			etc., etc., etc., etc.,......

...... and this is just for starters.....  Any other
suggestions/additions/ideas?  Perhaps we can tack on "modular code"
examples once we get through the basics?

Just my thoughts -

Bill Walters



David Rabin wrote:
>
> The manual should start with ECS LITE. If ECS LITE is not easy to
implement
> and get working well right away then you wont get new consumer level
> purchasers. ECS (in my very humble opinion as a non ecs user ) needs to
get
> basic functionality at the consumer level. I listen to this list but still
> dont convert from homevision because it sounds too complex for a non
> technical person.
> I really wish mark well because it sounds great and he sounds very nice
but
> keep in mind that most new potential buyers are not technical people and
> they want plug and play.
>
> david
>
> At 11:07 AM 10/1/98 PDT, you wrote:
> >A good manual with examples really is needed, in any format.
> >I'm a bit weary of doing everything by trial and error.Mostly error.
> >I would be happy to contribute.
> >
> >Carl K
> >
> >
> >
> >>
> >>Bill, I agree that a primer and updated manual for ECS would be very
> >>valuable, not just for current users, but even more so for new users.
> >>
> >>Command structures syntax and options are a necessary part of an ECS
> >>manual, but just as important would be sections on the logic of
> >>programming a given interface; for example "How to Implement CID" or
> >>"How to Implement a Serial-Byte Interface". The manual should probably
> >
> >
> >______________________________________________________
> >Get Your Private, Free Email at http://www.hotmail.com
> >
> >


  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects




Services provided by [NetBloc]®! NetBloc Solutions Inc.
Terms of use. Indexing software (c) 1999 Lin-De, Inc
.