From: Kevin O. <ko...@ho...> - 2001-06-08 03:35:38
|
Don Flanders wrote: > If I open up the battery compartment and press the on button I hear a click > from the transciever and if I press the off button I also hear a click - > each is accompanied by a flash from the motion detector. If I cover the > detector with my hand and then about 10 seconds later remove it, the light > on A2 comes on and I see the red light flash again. But I never see it > flash, or hear a click without some sort of manual method. After the MS13A sends a signal (due to motion or dusk/dawn) there's a few second (maybe 10, can't remember) delay before it will do anything else. So you're saying that you've tried something like: - in a room, not playing with the lights (to trigger dusk/dawn) - sat in front of the thing for at least 10 seconds - then moved And it didn't send the A1-ON commands and/or the red led didn't flash? Maybe the motion sensor's a dud? Is there a green led that flashes? > Another weird thing is that if I turn off the main light (which is A2), it > catches the change it lighting and turns it back on again, which a second > later turns it back off again, and on etc... It gets into some sort of > loop - which I didn't think it would do because its set to 1 minute for an > off signal. The setable delay applies to the motion sensing, IIRC not to the dusk/dawn feature. You can set the time the sensor will wait before sending and 'motion off' signal. This time window starts again everytime the sensor sees motion. > The only thing I can think of with this is that the off signal > only applies to motion, not light changes. Not sure what you mean. You should be geting an off signal for both lack of motion and lack of dark (but only if the 'lacks' were preceeded by motion and light respectively). I think you want to first determine if the motion sensor is functional. Do this without playing with the dusk/dawn feature. You may want to refer to you MH log for a list of the On/Off commands that get generated. Hope that helps, Kevin |