@sbooke, your motion sense is working.  Your event viewer is showing EXACTLY what I posted above.

Your last program you posted is incorrect.  You are using a time trigger, not a motion trigger.  The THEN statement is also incorrect.

However, your original program should work.  As @Guy Lavoie indicated, this would perform better if you used a "control" vs "status" qualifier.

Not sure how, but we seem to have come full circle.  

 

Event Viewer Showing MS-II Communication

Original Program Motion Program

2 device scenes - 9

3 device scenes - 4

4 ...1

9.....1

11....1

 

thats it

Ok I'll get off my high link high horse! That's all I have to offer, hopefully @IndyMike can help you like he helped me.

i must have been searching for a program that might work.

 

I have put the program back to the above plus changed the line to control, still no joy.

 

@sbooke, your event viewer shows communication from your motion sensor, but it's from group 13.  Motion is from group 1.  I can't see enough from the event viewer to tell if you got a group 1 communication like you had previously.

Regardless, your program should run as you have it written:

1. Make sure you have saved the program.
2. Look at the program summary to see the "last run" for the program.  It should be triggering within the time window.
3. If it has triggered, try performing a "run then" on the program to see if your device responds correctly.
4. If none of the above works, delete the time constraint and check to see if the motion trigger alone works.

 

Thanks for taking the time here. Frankly I have learn a lot more about the interworking's of the console.

I am thinking, we went around our *** to get to our elbow solely due to operator error.

I had been hitting update in programs and not save changes. At least i think that's it.

Program is saved correctly now.  I did not save the correction I just did just update.  And when you suggested saved, I double checked and it reverted back to status and not control.. 

Program summary - ran with ran then.

And now motion has turned the light on and off twice.

.......thanks Issue resolved

 

 

MS devices use many channels and each one establishes a link with your PLM.

It is very common during disturbances and EPROM rewriting to MSes to lose or scramble one link. All the other functions may work, but one doesn't.

Put the MS into linking mode and use IoX to Restore the device, by right clicking on the device in the device tree.

If that doesn't do it, then try factory resetting the MS and then Restore it again.

Sent from my SM-S711W using Tapatalk