| ECS Home Automation and Security Archives |
| Subject: From: Date: | RE: [ecs] Closed/Open-pending - & Digital I/O Issue Mark Gilmore Wed, 05 Nov 2003 05:31:52 -0800 |
Hi Rob, Set all .Diagnostic Props back to 0 and retest. It's possible (though very improbable) that the diagnostic dumps effected the problem. You might also add some script logic to speak something when motion is detected on that sensor. Then test it repeatedly to see if it's an intermittent problem. What Object Class detects the motion ? At 09:38 PM 11/4/2003 -0700, you wrote: >Mark, > >Do you have special diagnostic detection software built into ECS? I've been >chasing this problem for 2 months. I spent all of last Saturday trying to >get the motion detector working again. I tested it with WinEVM and ECS 4.10 >and ECS 2.3.07; it worked in all but 2.3.07. Even with 2.3.07 in diagnostic >mode with both the TC+ interface and the motion detector objects set to 2, I >couldn't see anything. > >Now, I've spent the last 2 hours trying to repeat the problem. I can't and >don't know why. Magically, the motion detector is working now. I have no >explanation. Over the past three months, I've rebooted, re-wired, >reconfigured, all to no avail. When you ask, all seems repaired and nothing >is repeatable. I'll start asking sooner:-) > >Rob > > >-----Original Message----- >From: Mark Gilmore [mailto:mark@markgilmore.net] >Sent: Tuesday, November 04, 2003 7:43 PM >To: ecs@netbloc.com >Subject: RE: [ecs] Closed/Open-pending - & Digital I/O Issue > >it won't be in the logs until you the .Diagnose >Properties of the 2 Objects. > >At 07:41 PM 11/4/2003 -0700, you wrote: > > >Mark, > > > >Absolutely nothing shows up in the logs with any level of diagnosis. It's >as > >if the motion detector, or at least the IO channel, doesn't exist. ECS just > >doesn't seem to see anything on the channel. > > > >Is there a way that I can sniff the communications link between the >computer > >and the TC+ to see what's happening? > > > >Rob > >-----Original Message----- > >From: Mark Gilmore [mailto:mark@markgilmore.net] > >Sent: Tuesday, November 04, 2003 7:31 PM > >To: ecs@netbloc.com > >Subject: Re: [ecs] Closed/Open-pending - & Digital I/O Issue > > > >Set the Object's .Diagnose Property to 2, > >do same for the TC, > >reproduce failure, > >and send main.log (incl name of said Objects). > > > >At 07:29 PM 11/4/2003 -0700, you wrote: > > > > >Mark, > > > > > >I rebooted my machine and haven't seen Closed/Open-pending problem again. > > >I'll check it periodically to see if it reoccurs. > > > > > >I am having another problem though. I have a motion detector that I can't > > >get ECS to recognize. I initially thought that it was the motion detector > > >and replaced it. Then I thought that it was a bad port on my TC+. To test > > >that theory, I first moved the motion detector circuit to another port. > >Then > > >I used the software that came with my TC+. And finally, I have tested it > > >using an older Windows version of ECS. The port and the motion detector > > >appear to work fine. > > > > > >Do you have any suggestions what I might look at next? > > > > > >Rob > > >-----Original Message----- > > >From: Mark Gilmore [mailto:mark@markgilmore.net] > > >Sent: Saturday, November 01, 2003 4:33 PM > > >To: ecs@netbloc.com > > >Subject: RE: [ecs] Still looking for where to place the cmd > > > > > >And you're absolutely positive that it changes to "Closed" (and not >"Open") > > >?? > > >If so, please set the relay .Diagnose to 2, re-create problem, and email >me > > >main.log. > > > > > >At 03:38 PM 11/1/2003 -0700, you wrote: > > > > > > >All, > > > > > > > >I am experiencing an issue with ECS 2.3.07. > > > > > > > >I'm using a TimeCommanderPlus. I have set the Minimum-Close-Time on > >relays > > > >controlling dampers for my heating system. They are set at 180 seconds. > > > > > > > >I'm trying to use the Closed/Open-pending property of the relays to > > > >gracefully shut down my furnace. However, every time I attempt to open >a > > > >closed relay before 180 seconds have elapsed, the status changes to > > > >Closed/Open-pending for less than a second and them reverts back to > >Closed. > > > >If I change the status after 180 seconds, the status immediately >changes > >to > > > >Open. > > > > > > > >The reverse works fine, i.e., closing the relay before the > > >Minimum-Open-Time > > > >has elapsed. When I do so, the status changes from Open to > > > >Open/Close-pending and then after the Minimum-Open-Time has elapsed, >the > > > >status changes to Closed. > > > > > > > >I originally thought that I had some other script interfering but have > > > >disabled all referenced scripts. > > > > > > > >Any ideas? > > > > > > > >Rob > > > > > > > >-----Original Message----- > > > >From: Mark Gilmore [mailto:mark@markgilmore.net] > > > >Sent: Saturday, November 01, 2003 2:58 PM > > > >To: ecs@netbloc.com > > > >Subject: RE: [ecs] Still looking for where to place the cmd > > > > > > > >Hi Ingo, > > > >Daemon or not, I *really* need to be able to start a terminal session > > > >and run a pgm *after* the "knoppix" user is logged in. > > > >And given what I have gone thru just trying to do *this* simple task > > > >(burning numerous CDROMs with 1-hour turn-around times), > > > >I am not about to go down the daemon road :-). > > > >I have mastered the startup procedure under RH9 (via Gnome session >mgr). > > > >My problem now is trying to figure out how to get Knoppix (which uses > >KDE) > > > >to load my startup link into the /Autostart folder. > > > >This looks like yet another mystery that will eat many hours. > > > > > > > >At 01:47 PM 11/1/2003 -0800, you wrote: > > > > > > > > >Hi Mark, > > > > > > > > > >Can you clarify why the autostart has to happen after login, rather > >than > > > > >making ECS a daemon? IIRC, ECS is waiting for user input at some >point > > > > >(if only typing Q to terminate) - any chance you can get rid of that? > > > > >Once you have that, it is fairly straightforward to make any program >a > > > > >daemon. > > > > > > > > > >I see two options for solving your problem. Not knowing the exact > > > > >requirements, I don't know if they would meet all requirements for >your > > > > >private label use: > > > > > > > > > >- make ECS a daemon, so it starts up when the system boots instead of > >on > > > > >login. To accomplish that, you have to make sure that ECS never tries > >to > > > > >read anything from stdin. It would also be good not to print anything > >to > > > > >stdout, but instead to a log file. > > > > > > > > > >- if you cannot do that, you could edit /etc/inittab and replace one >of > > > > >the six places where mingetty is called with a call to ecs.bin. Do >note > > > > >that if you do that, ecs.bin needs to be very hacker-proof, since it > > > > >would be running as root. > > > > > > > > > >Mingetty is the program that usually asks the user for login: and > > > > >password: if you are not running X. By replacing it, ECS runs > > > > >immediately without a login, and has full control of the system at >the > > > > >same time. Obviously, a very major security issue if your system is > > > > >connected to the Internet in any way, even behind a firewall. Best, >add > > > > >a call in ECS to change users (setuid) after you opened the listening > > > > >port, as I described in another mail. > > > > > > > > > >On Sat, 2003-11-01 at 05:17, Mark Gilmore wrote: > > > > > > Sorry for the confusion, but this auto-startup effort is for a > >Knoppix > > > > > > private-label vsn of ECS. > > > > > > I am just trying to get it to work under RH9 1st, so I won't waste > > >weeks > > > > > > blindly burning > > > > > > Knoppix test CDs (and I need to know how to do this basic task > > >anyway). > > > > > > So I still need to know where to place my command, > > > > > > *or* preferably why my links in /Autostart have no effect. > > > > > > Thanks, > > > > > > > > > > > > At 09:37 PM 10/31/2003 -0800, you wrote: > > > > > > > > > > > > >I agree completely that making ECS a daemon that runs in the > > >background > > > > > > >without a user interface is the proper way to solve all the > >problems > > > > > > >Mark has struggled with, from automatically starting to the bind > > > >problem > > > > > > >(assuming that I identified that correctly). With ECS as a >daemon, > > > >there > > > > > > >is no need for autostarting. Or even for logging in in the first > > >place. > > > > > > > > > > > > > >But do be aware that X will (usually) NOT be up when the scripts >in > > > > > > >/etc/rc.d/rc5.d are executed (/etc/rc5.d is a redhat-specific >link, > > >and > > > > > > >actually not a very good idea to have). > > > > > > > > > > > > > >Everything in /etc/rc.d/rc5.d is executed completely during >bootup. > >X > > > >is > > > > > > >actually NOT launched during the boot phase. Rather, *once the >boot > > > > > > >phase is completed*, Linux sets up seven terminals. You can >switch > > >back > > > > > > >and forth between them with Alt+F1 through Alt+F7. Then, Linux > > >launches > > > > > > >the applications specified in /etc/inittab. In six of the > >terminals, > > >it > > > > > > >runs /sbin/mingetty. In the seventh terminal, it runs > >/etc/X11/prefdm > > > > > > >-nodaemon. This is the X login screen, and it will also start the >X > > > > > > >server at the same time. So X is definitely NOT running when > > > > > > >/etc/rc.d/rc5.d is executed. The only time it would already be > > >running > > > > > > >is if you start or stop certain individual services. > > > > > > > > > > > > > >As an aside, the script actually should be in /etc/rc.d/init.d. > > > > > > >/etc/rc.d/rc5.d should only contain a link. > > > > > > > > > > > > > >On Fri, 2003-10-31 at 17:44, Rob Hicks wrote: > > > > > > > > Mark, > > > > > > > > > > > > > > > > Why not just create a shell script and place it in /etc/rc5.d/ > > >with > > > >an > > > > > > > > execution number high enough that it will execute after > >everything > > > > > else has > > > > > > > > run. rc5.d runs only when the system is set up for run level >5, > >or > > > >X. > > > > > > > Thus X > > > > > > > > should be up. I assume that you want X running in order to > >launch > > >a > > > > > > > browser? > > > > > > > > > > > > > > > > My preference would be to have ECS run as a daemon that can be > > > > > attached to > > > > > > > > with a browser, either on the local machine or on remote > >machines. > > > > > Then > > > > > > > when > > > > > > > > a user logs in, you give simply give them a desktop or panel > >link > > > > > to launch > > > > > > > > the browser and go to the ECS sign on page. > > > > > > > > > > > > > > > > Rob > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: Mark Gilmore [mailto:mark@markgilmore.net] > > > > > > > > Sent: Friday, October 31, 2003 4:51 PM > > > > > > > > To: ecs@netbloc.com > > > > > > > > Subject: [ecs] Still looking for where to place the cmd > > > > > > > > > > > > > > > > OK - Let me try asking it another way (focusing on RH9 for >now): > > > > > > > > When I log in, I want RH9/Linux to start a terminal (i.e. > > >"konsole" > > > >or > > > > > > > > "gnome") > > > > > > > > session and run a command within that session (the cmd being > > > >"konzole > > > > > > > > -e="ecs.bin"). > > > > > > > > In *what* file would I place this command ? > > > > > > > > Thanks, > > > > > > > > > > > > > > > > Mark Gilmore > > > > > > > > http://OmnipotenceSoftware.com > > > > > > > > > > > > > > > > > > > > > > > > > > > >--- > > > > > > >Incoming mail is certified Virus Free. > > > > > > >Checked by AVG anti-virus system (http://www.grisoft.com). > > > > > > >Version: 6.0.528 / Virus Database: 324 - Release Date: 10/16/2003 > > > > > > > > > > > > Mark Gilmore > > > > > > http://OmnipotenceSoftware.com > > > > > > > > > > > > > >______________________________________________________________________ > > > > > > > > > > > > --- > > > > > > Outgoing mail is certified Virus Free. > > > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > > > Version: 6.0.528 / Virus Database: 324 - Release Date: 10/16/2003 > > > > > > > > > > > > > > > > > > > >--- > > > > >Incoming mail is certified Virus Free. > > > > >Checked by AVG anti-virus system (http://www.grisoft.com). > > > > >Version: 6.0.528 / Virus Database: 324 - Release Date: 10/16/2003 > > > > > > > >Mark Gilmore > > > >http://OmnipotenceSoftware.com > > > > > > > > > > > > > > > >--- > > > >Incoming mail is certified Virus Free. > > > >Checked by AVG anti-virus system (http://www.grisoft.com). > > > >Version: 6.0.528 / Virus Database: 324 - Release Date: 10/16/2003 > > > > > >Mark Gilmore > > >http://OmnipotenceSoftware.com > > > > > > > > > > > >--- > > >Incoming mail is certified Virus Free. > > >Checked by AVG anti-virus system (http://www.grisoft.com). > > >Version: 6.0.536 / Virus Database: 331 - Release Date: 11/3/2003 > > > >Mark Gilmore > >http://OmnipotenceSoftware.com > > > > > > > >--- > >Incoming mail is certified Virus Free. > >Checked by AVG anti-virus system (http://www.grisoft.com). > >Version: 6.0.536 / Virus Database: 331 - Release Date: 11/3/2003 > >Mark Gilmore >http://OmnipotenceSoftware.com > > > >--- >Incoming mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.536 / Virus Database: 331 - Release Date: 11/3/2003 Mark Gilmore http://OmnipotenceSoftware.com
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.536 / Virus Database: 331 - Release Date: 11/3/2003