Subject: From: Date:

Re: [ECS] RE: ECS Primer Bill Walters Sun, 04 Oct 1998 22:10:08 -0500

---

OK folks, 

Time to think about really -working- on this project.  I'm off to Lima
Tuesday night (they don't allow crewmembers to bring computers :<{{{{  )
so I'd like to make some suggestions:


1.  Any examples, or "code" which makes up each chapter needs to be
self-contained.  By that I mean if you're going to document & explain
"telephone" event, you need to have the whole enchalada; items and all,
so it can be "pulled-in" by anyone into their .CFG file.

	- obvious exception is the expanded explanation of LITE.CFG
		...there just "Lots" of comments ?????


2.  I'd like to get volunteers for various chapters.

	- I'll pony-up for the introduction and several chapters (at least).

	- I'm -WEAK- on telephone events, so who is willing to tackle that? 
I'll help "clean" up the text but need someone versed on it.

3.  Everyone think the chapters listed so far are pretty good starting
points?  If so, great, if not, then any suggestions?  I suspect that one
thing will lead to another, so the general outline is (to say the least)
VERY flexible.

------ So --------

Who wants to pony-up for what chapter?

Got a favorite interest?  Something really nifty to share?


Bill Walters




Bill Walters wrote:
> 
> 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
> > >
> > >

---