JP1 Remotes

[leres]

If the shift key is mapped (e.g. right arrow) it blinks and sends an IR code. I believe if it's a key that's not mapped (e.g. TV/video), it still blinks every with every key press.

I haven't built the extender but I downloaded the assembler yesterday and it doesn't look difficult. Since the shift key works the first time, could it be a timeout isn't getting reset? Maybe because the key is unmapped? Anyway, if you give me a modified extender, I'll figure out how to assemble and load it (especially later this week after I receive more parts and finish converting a 2nd RM-Y809 so I can do testing and still have a remote that "works").

[vasqued2]

Oh, I get it now. There isn't a native shift key on the remote, right?

Anyway, the first thing to try is to take out the code which resets the shift after a timeout and try that.

Go into the Raw Data tab in IR and go to the row 07A0. Go to columns 0E and 0F. They should have the values B0 and 4C in them. Overwrite them both w/ 00.

Retry everything.

If the problem was a problem w/ the shift timing out, this will resolve it. Keep in mind that this 'solution' will always keep the shift from timing out. So if you press the shift, walk away for three days, and then come back. It will still be in shift mode, and will stay that way until you press a second button.

Try this and see what happens. If it doesn't work, we'll try something else.

David

[The Robman]

Thanks for helping out David. I don't have the remote either anymore as I sent it back to the person I was programming it for, and it's great that we have leres around now who can do some testing. If we get something that looks like a fix I'll send it onto my guy to load and test.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

[leres]

Here's what the remote looks like:

[mtakahar]

[leres]

The following is silkscreened onto the pcb:

[mtakahar]

[leres]

Ok, I just tried this:

• Upload an extender config with shift set to TV/video
  
• Set the TV/SAT slide switch to TV
  
• Boot the extender
  

I can't find a difference between that and booting the extender with the slide switch set to SAT.

Here's another test:

• Boot the extender
  
• Use a non-shifted macro key to execute O_TiVo
  
• Hit TV/video
  
• Wait 35 seconds
  
• Hit a shift-ed macro key
  
• The unshifted key is used (the shift timeout works)
  
• Hit TV/video
  
• Wait 5 seconds
  
• Hit a shift-ed macro key
  
• The shifted key is used
  

And of course from that point on, shift times out very quickly.

When TV/video is the shift key, it always works the first time after booting the extender even if native keys or macro keys are used first.

And as I said earlier, when right arrow is the shift key, shift always works.

How do the buttonmaps defined in the rdf relate to the capabilities of the remote? Is the fact that the rdf for the extender doesn't include $26 (TV/video) in the map for device type 1 (SAT) mean that the remote cannot deal with a mapping for that key when using that device type?

Looking at the rdf, I would think that the two device type 0 devices (TV and RCVR) would have the same keys available. But when I look at the keymap on the devices page of ir.exe, I see different key names listed in the keymaps for SAT and RCVR.

One last thing; back when I first started playing around with JP1 remotes I was working with a URC-6131. I never understood why keymap-master had remote definitions for URC 6131 PVR and URC 6131 PVR extender. When I first started programming the RM-Y809, I was expecting keymap-master to have an extender version of RM-Y809 but it didn't. What's the difference?

[vasqued2]

[The Robman]

[mtakahar]

WaitNoKeys would cancel the shift state if timeout happens, so there's still a possibility that the timeout value getting set incorrectly. Another possibility is the timeout event getting caught in a different place, but I don't see why SA TiVo remote and 6131 are not showing the same problem...

David,

Please feel free to ask leres do experiments whatever you think useful.

Hal

[mtakahar]

[vasqued2]

leres,

Let's try another experiment where we hard it so every key gets treated as a shift key.

In line 00E0 you should find the hex string
44 4c a3 (OR R_MacLast, R_SFlags ;Shift the key if flag is set)
Change it to
46 A3 80 (OR R_MacLast, 80 ;always shift the key!)

This change essentially puts in the code to treat all of your buttons as being shifted all of the time. Run some experiments to see if they are all treated as shifted buttons. Remember, if a button has a function mapped to the shifted value, it will execute the shifted function. If it doesn't, it will execute the regular unshifted value.

If this code treats everything as shifted, then we know the problem is with the SFlag getting reset somewhere. If it doesn't, then we know the problem is associated somehow with what buttons are getting recognized when.

I expect they will all behave as if they are shifted, but we should conclusively rule out the other option first.

David

[leres]

I can't do any testing until tonight. But yesterday I did successfully build and install a version of the extender built from source. Does it make more sense to test from source instead of patching byte codes? If so, please email me your test version of the .asm file.

I'm expecting a order from mouser.com so by Friday I should have a 2K RM-Y809 available for testing.

[vasqued2]

Going forward it will make things easier.

These are just some quick easy things to test. The next step it will be very helpful to have the source, and we'll start back w/ the original version again.

Right now, I'm trying to keep all of the code the same length so the offsets in the rdf file don't change.