JP1 Remotes

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

Update on testing xshift-device:
Separating shift buttons made an enormous difference.
> After watching more signals, and in a more typical use than in an earlier experiments, a separate Xshift button does switch correctly most, if not all the time.. I think I only got stuck once in one device.
> Both shifts on one button reliably do not send correct signals to dev5 and dev6 when I press xshift-device.
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride Smile

unclemiltie · Posted: Thu Feb 17, 2011 6:01 pm Post subject:

OK, so I have a theory

If you are using Shift-Shift as the Xshift key, it could be possible that you are getting three shifts with a bounce of some kind.

Think of this:

1: the first shift key has the shiftmask set to $00, the key ($02) is ORed with the shiftmask and then tested to be Shift. The shift mask is set to $80 and then the remote goes to get the next key.

2: the second shift has the shiftmask set to $80 and the key is ORed with the shiftmask, which then tests to be Xshift. The shift mask is set to $C0 and then the remote goes to get the next key

3: now the third shift is pressed. The shiftmask is set to $C0 and the key is ORed with the shiftmask. This turns out to be XShift-Shift ($C2), which likely has no keymove associated with it. Since there is no keymove, the extender then "cloaks" the key back to the original shift key.

You could validate this by putting a keymove on Xshift-Shift that does something that you can detect and then see if it fires during "step 3" above.
_________________
this JP1 stuff is a sickness!

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

Xshift and shift on one button: Your theory of cycling maybe right.
I don't know how to make a macro on xshift-shift, but it works from the keyboard like you say - step 3, because we get back to the base device. Don't know whether this is equivalent to your idea of a macro on Xshift-shift. If not, I need more instructions.

Ever since you suggested trying xshift on a different button from shift I started thinking about the second paragraph of the old shift description (which is why I quoted it). But a nearly 100% time occurence?

So the bottom line might be the keybounce when shifts are on one button. This is a tricky situation - we want to detect two presses of the same shift, yet not see it as a keybounce Evil or Very Mad

Is this something that can/should/should not be changed?
If I'm the only person addressing this, I suspect the answer is no. I think mdavej said he has no issues. Don't know about other people. Hint, hint Smile

All this should be easy to test even without a widget (How can you live without a widget?). If you now have a, say TV device macro, make a Xshift-TV macro containing Dev_DVD,followed by DVD keysets and watch if the signals go to the TV or DVD. When Xshift-TV works, the destination should be DVD. When it fails, signals go to TV.

Request:
Would it be possible to somehow tell me what is the 'current device'?(Atlas needs it too) On 8910 I can press light and it'll show me DVD/setup code. Maybe we could have a button which will flash the device, and maybe double flash for dev4, dev5, dev6. I know an earlier proposal is to flash like this after other keysets run. But I'd like to know where I am before I press Power Smile

or something else destructive.

Are we ready for official v1.0 yet?
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride Smile

R2-M0 · Joined: 14 Aug 2009 Posts: 92

unclemiltie · Posted: Thu Feb 17, 2011 10:13 pm Post subject:

unclemiltie · Posted: Thu Feb 17, 2011 10:17 pm Post subject:

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

unclemiltie · Posted: Thu Feb 17, 2011 10:32 pm Post subject:

Bill isn't bored. He's working on porting this extender to the Insignia 3147 remote. I had thought at the time it came out that it would be an interesting remote, but now that I actually have one I'm not sure.

The Atlas 1056 backlit is still my favorite, if it only had the 8 devices like the RCA has I'd be very happy with it.

Not only that, I need to find a job!
_________________
this JP1 stuff is a sickness!

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

mdavej · Expert Joined: 08 Oct 2003 Posts: 4501

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

Bill,
I thought a bit more about blinking.
(1) CBL,TV,DVD,AUD,DVR - single blink
(2) dev4,dev5,dev6 - double blink or blink Play then the device button.

I wonder if we could define what to blink for virtual devices when Set_Other is done. Just before Set_Other is done we could include device index number to blink (0,1,2,3,7). That would permit to blink, for instance CBL when index is 0 or AUD button when index is 3. A change from what Vicky wrote, but I think it would be useful.
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride Smile

unclemiltie · Posted: Fri Feb 18, 2011 11:17 am Post subject:

A lot more code...... The blink routines are the ones used in the remote and the device list is not contiguous for checking which are real and which are phantoms.

I'll look at it
_________________
this JP1 stuff is a sickness!

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

Lots of fun with this extender. Thank you, Bill.

I have a way to find out which is the active/current device. Quite simple actually.
Using a harmless command such as what I have in the upgrades on the Dash button. Two of my devices had nothing there, so I added something similar to "-" for entering channel numbers. Pressing "-" button in the wrong context blinks, and the gear ignores it.

So really, some refinement of what and how blinks in the existing code is sufficient and will be more than cool to complete the picture.
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride Smile

unclemiltie · Posted: Fri Feb 18, 2011 8:32 pm Post subject:

I think I can figure out how to blink the real devices once and the phantom devices twice using only about 10 extra bytes and it'll fit. I'm having a bit of a fight with the assembler right now since

unclemiltie · Posted: Mon Feb 21, 2011 7:57 pm Post subject:

I'm just about ready to release V1.00 of this extender. The last thing that I wanted to get in was the blinking for Set_Other.

After the suggestion here from Liz, I did implement a single blink on "real" devices and a "double blink" on phantom devices. This can be disabled so that no blinks happen on phantom devices at activation through IR as previous. Liz has this version and is going to test it for me, but I'm pretty sure that it will work for her.

Any other changes before I let this one fly?
_________________
this JP1 stuff is a sickness!