On February 18, 2009 at 00:13, SOUND.SD said...
Jim-
I dont think your solution makes sense. The processor does not send a command back to the remote to stop issuing the command. The processor simply stops receiving the command thus stops issuing the command. This would happen as soon as interference occurs or you stop pressing the button. Unless you have enabled "button pause" for this step in a macro.
That's the biggest thing that caught me off guard. Didn't seem to make sense, but I don't know how a processor handles its "internal" RF triggers (not system macros). The way I explained was how it was acting and I can't think of another reason why it would happen that way. I'd love to hear from RTI how the "repeat while button is pressed" is handled in System Mode. It seems more "efficient" to have the processor wait for a Stop command to stop repeating a macro - but yeah, I could be wrong.
Like I said above, I just had the same situation with NO RF whatsoever, so figure that one out. :)
