| ECS-L Home Automation and Security Archives |
| Subject: From: Date: | Re: [ECS] RE: ECS Primer Bill Walters Fri, 02 Oct 1998 10:03:37 -0500 |
All, E-mailed Jeff Anderson last night with information about ECS Primer project and requested to "reprint" the articles. He heartily agreed it was a good idea and said to go ahead and include David's articles in the Primer project. What a great deal! I'd also like to suggest that we break down advanced uses in the following areas (are these the most likely to need detailed information? What about the proposed order? Other suggestions? ) Telephone Messaging 1. Simple answering/playback system DOS Windows (& why the differences) 2. Use of individual Mailboxes (can build on #1 above) Dos Windows (if any different, and why) 3. Page on Call Notification a. Numeric Only Dos Windows b. Alphanumeric Dos Windows 4. Caller-ID with Announcements a. Simple Announce only b. testing/reject/etc (based on David Kindred's model) (this is same -I think- for both DOS & windows) 5. Outgoing Call Logging a. DOS Only based on BIGMOUTH --->unless someone has used Weeder stuff & willing to share/help 6. Local Telephone Control DOS Only a. Simple "stand-alone" operation --->again, unless someone has used Weeder stuff & willing to share/help 7. Remote Telephone Control a. Simple "stand-alone" operation b. Macro capabilities w/voice confirmation dialogues c. System "monitoring" & "status" 8. Integration of PBX System for Caller-ID/Messaging/Control ??? ??? 9. Serial-Byte implementation ---David's article covers subject WELL! ---with example of IR control 10. HVAC Contol ---Mark's code in full CFG file is excellent ---but could use extra commenting perhaps? Bill Walters David A. Kindred wrote: > > Bill, > > Your proposed outline is excellent. > > --David K. > > -----Original Message----- > From: Bill Walters [mailto:wtwalters@home.net] > Sent: Thursday, October 01, 1998 11: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 > > > > > >