Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Puck]

I just has a problem with an ActiveEye motion sensor that I want to share to see if anyone ever experienced this (and to let you know of a potential failure mode).

The motion sensor stopped triggering its intended macro. When I walk in front of it, the LED would flash so I knew it was still working. I took the batteries out and replaced them with new (good) ones.. the old ones were down to 1.4V.

I reprogrammed the motion sensor for the correct X10 address. This address was confirmed by the flashing of the LED during the programming sequence.

When I walk in front of it, the LED blinks but the macro still did not run. When I looked at the activity monitor I discovered that the address being send out is A1. I verify & reprogram and the LED still flashes out the correct address, but activating it still sends out A1.

I tried different batteries, reprogramming multiple times, and still the program shows it correctly but the RF sent out will not change from A1.

[Brian H]

Thanks for the information.
Did you by chance wait a few minutes after removing the batteries so the filter caps discharged completely?

[Puck]

Did you by chance wait a few minutes after removing the batteries so the filter caps discharged completely?

My last try was the following day (without batteries all night).

If it were not for the Activity Monitor in AHP showing what the MS16A was really sending out, this fault would surely send one on a wild goose chase trying to find out why it is not turning on a light or activating a camera.

[Alan V]

I took the batteries out and replaced them with new (good) ones.. the old ones were down to 1.4V.

I haven't seen this before.  But even at 2.8V (1.4V for each battery), the MS16A should still function.  The PIC12C508 will work reliably down to 2.5V when using its internal 4MHz oscillator.  It could simply be a device failure.

[PAULF]

I am having the same problem, everything works when I trigger the macro on the PC but it won,t trigger with the M16 only (connected to pc or not).  The activity monitor sees the trigger but that is where it stops.

[Puck]

I am having the same problem, everything works when I trigger the macro on the PC but it won,t trigger with the M16 only (connected to pc or not).  The activity monitor sees the trigger but that is where it stops.

Are your macros stored in the interface or run from the pc? I have experienced macros that run from the pc need their house code set to transceive in order for a motion sensor or remote (RF) to trigger them.

[PAULF]

I figured out my problem.  The new upgrade does not work with VISTA.  I completely removed the program, cleared the interface and reloaded the old version and now everything works again.