Subject: From: Date:

Re: [ECS] RE: ECS Primer David Rabin Fri, 02 Oct 1998 21:13:37 -0500

---

i would also have a section on hardware that is EASY to implement.
a newcomer who is trying out ecslite needs to know what hardware to use.
a hardware list for other features would also be nice (i have no idea what
you need for vr etc).
i know the beauty of ecs is most things can be MADE to work but the
newcomer or consumer wants easy to find and easy to implement things that
dont need to be MADE to work.

i would want a simple list that does not have to all inclusive just nearly
goofproof to start up !

thanks

david


At 10:51 PM 10/1/98 -0500, you 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
>> >
>> >
>
>

---