|
ECS-L Home Automation and Security Archives |
learn more
| view messages for this
month | NetBloc® | terms of use | search
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects
Subject: From: Date: | RE: [ECS] Support, custom interfaces David Rabin Thu, 01 Oct 1998 19:33:50 -0500 |
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