JP1 Remotes

Thanks ElizabethD!

It's a great reference and good read about what I was trying to accomplish.

And just to ensure I understand correctly, you have set it up such that for a single button, you have THREE different behaviours:
(1) Single Short press = sequence/macro1
(2) Single long press = sequence/macro2
(3) Double press = sequence/macro3

Is that correct? Cool!


Well, for the most part ...

Since I just experienced this, I'm passing some info along. The parallel cable may fail to communicate (every time in my case) if the remote gets a set of fresh batteries. There is an issue related to parallel voltage vs remote battery voltage that prevents or makes unreliable the communication ...

Here is the file.
https://www.hifi-remote.com/forums/dload.php?action=file&file_id=2925

Sorry, I have not cleaned up the device code operlap yet. :( But that's one of my next projects now that I overlayed their text output on the LCD :)

Also, Phantom2 is still the extra key sequence to prevent ...

It appears to work the way I intended, but I just wanted to confirm that the fall through condition is not just hapinstance and prone to change in future extender revisions.

I have a macro #4 for the CBL button calling into the DKP special protocol funtion #8, which, in the case of single key ...

Thanks for the indepth reply!

You are right on all calls in your interpretation of my setup. The power button for the device works flawlessly by itself when called upon by the power button in the correct device mode for both the Xbox and Pinnacle unit. The power only seems to fail in subsequent ...

Ok. I played with duration, and from what I saw, I got it setup and installed correctly. Although it did help with the power on/off slightly (more reliable operation) it really ate into device/protocol memory. So much so that I had to remove some currently unused devices and protocols from the ...

Great info. Thanks for the quick reply. I'll try working the device combiner a.s.a.p. for my troubling macro keys!

Did you just replace the batteries? Fresh batteries can cause communication problems, as I recently learned from the boards.

The extender docs do not really describe how to adjust duration, only how to detect if you have a duration vs. delay problem.

However, I stumbled across a few posts talking about the DeviceCombiner. I finally read/found how to access the protocol in RM. It appears fairly straightforward; I'm hoping ...

Yes, I did stumble upon it, of course this was after I posted it and got a most excellent reply explaining the situation about voltage supply through the parallel port. The sticky was under the subject of parallel cable problems, and I was having a communication problem based on batteries. So I ...

Thanks, I'll review that part of the document again. I may have missed some tweak in there.

I wish I could just erase this entire post. I'm still having other problems. It appears just a macro problem in general, and not an embedded problem necessarily.

Calling a discrete value more than once in a row, like input selection, fixes one of my main problems. However, now I'm having ...

Multiple input selection keys back to back in the macro appear to fix the problem with minimal impact on macro space, but I'm still curious why the L2 macro works outside of being embedded in the other macro. Odd.

Turns out embedding the 2nd macro's keys into the first does not guarantee success. It fails like the embedded macro. Trying to repeat the bad step a few times to see if that helps.