would it be possible to write an extender that remembers the IR protocol toggle bit per device instead of globally? specifically, i have an 7960 and on the watch tv activity when i click
- ok (which goes to my sat receiver)
- volume up (amplifier)
- ok (sat receiver) => ignored!
- ok => works
when i do
- ok
- vol up
- vol up
- ok => works!
i assume the 2nd ok in the first example is ignored because the volume up toggled the protocol toggle bit (although it's a different protocol) and as such the my sat receiver obviously can't see it.
That's not really an extender request, but a request for a custom executor for the protocol used by your sat.
As your results have shown, UEI executors use a global button press count to determine the state of the toggle, so even if the executor for your TV doesn't use a toggle, pressing a TV button will cause the sat toggle to flip.
Armed with the knowledge that any button press will cause the toggle to flip, my advice would be to construct your macros carefully so that the toggle is in the right state for when you need it, and if that means adding some meaningless button presses, so be it.
Rob www.hifi-remote.com Please don't PM me with remote questions, post them in the forums so all the experts can help!
The Robman wrote:That's not really an extender request, but a request for a custom executor for the protocol used by your sat.
Actually I believe it is really kind of a hybrid, because a protocol that tracked a bit would have to be written for the specific remote, because there is no common register that would be availble across the remotes, to do the tracking. So you would have to have 'extender writing skills' and "protocol writing skills" to get the protocol to be customized for a given remote.
Give Rob's suggestion some thought.
I have made it a prioritiy not to buy any more equipment that uses toggling protocols because they are so difficult to manage with a universal, often requiring a double tap to get some reaction and being extremely difficult to manage in a macro.
vickyg2003 wrote:I have made it a priority not to buy any more equipment that uses toggling protocols because they are so difficult to manage with a universal, often requiring a double tap to get some reaction and being extremely difficult to manage in a macro.
Just wondering about the general idea behind toggle bits. For the life of me, I cannot think of any other reason why anybody would implement them other than to thwart the compatibility of universal remotes. Are there any other reasons (positive/negative) why else they would be used?
it's a way to distinguish repeated button presses from a long button press that was interrupted by, for example, a hand. it has the advantage that if the first frame is not received for some reason it can still react to a repeated button press, unlike a system that sends a different first frame than repeat frame.
at least that's my guess...
