JP1 Remotes

vickyg2003 · Posted: Tue Mar 09, 2010 11:58 am Post subject:

Thanks Rob, I'll look at that after I beat up on the JP1.2 version for a while. This is a great learning exercise for me.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

The Robman · Posted: Tue Mar 09, 2010 12:49 pm Post subject:

Just so we can tell if we're on the same page or not, i've compiled a spreadsheet that lists all the keys, along with their pronto hex, the base4 code, the real binary, the OBC, the binary using Vicky's method and the hex required for Vicky's method.

http://www.hifi-remote.com/forums/dload.php?action=file&file_id=8131
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

vickyg2003 · Posted: Tue Mar 09, 2010 5:48 pm Post subject:

As always Rob knows best. The results I've been getting from my trial are bizzare and if there is a pattern, to what is being emitted, I can't find it. I'm abandoning my attempt at buffer manipulation, (for now) and I am moving to an approach similar to Rob's suggestion.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

The Robman · Posted: Tue Mar 09, 2010 7:48 pm Post subject:

You're idea was a good one, so I don't know that you should give up on it. It boils down to a trade off between using memory for the protocol or for the device upgrade.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

vickyg2003 · Posted: Tue Mar 09, 2010 9:49 pm Post subject:

Maybe my idea was a good one, but the IR engine doesn't like it. There is something extremely odd going on with the JP1.2 signals when the "on time" of zero is set to zero. I'm not seeing what I expect at all.

I've now got the signal appearing once, before it resets the remote, but I can't figure out how or why its working at all. Crying or Very sad

I've got to figure out why the remote is resetting, but I'm really pretty close and have absolutely no idea how I got there. Rolling Eyes

_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

vickyg2003 · Posted: Tue Mar 09, 2010 11:18 pm Post subject:

bengt, Here is an upgrade to try. I've viewed a few of the numbers and it looks good.

nokiaKeyboard

What brand of IR keyboard is this for?

Rob, I've moved on to the sc38+. That's going to take a bit of work as first try locked up the remote with no signal emitted. Apparently the IREngine on the JP1.2 remote handles these things natively, which is why my first approach didn't work.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

The Robman · Posted: Wed Mar 10, 2010 8:19 am Post subject:

It has built in support for 4-burst signals? I'll have to look at your code to see how you did 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!

vickyg2003 · Posted: Wed Mar 10, 2010 8:56 am Post subject:

Barf · Posted: Wed Mar 10, 2010 4:21 pm Post subject:

Rob, Vicky, I am impressed by your recent progress. I loaded Vicky's protocol implementation in an urc-7781 (jp1.2, hcs08) and -- everything seemed to work except for the repetition rate, which was much too high. Looking at the signal with the IRWidget showed approximately 90ms of "silence" between the signals, my Pronto codes said 0fd2, corresponding to approximately 112 ms (as Rob wrote in his PB file). I just analysed the original HW, and it turned out that 162ms turns out to be the delay it uses.

vickyg2003 · Posted: Wed Mar 10, 2010 4:48 pm Post subject:

You've got a Widget! Cool! Could you capture the "Number 1" to the IRScope, and post the resulting ICT file? Then I can fine tune the timings against the original device, instead of against learns of learns.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

vickyg2003 · Posted: Thu Mar 11, 2010 1:10 pm Post subject:

I've increased the time between repeats and have zipped it with the PB file. Support for the s3c8+ and the JP1.2 is included.

Nokia Keyboard
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

Barf · Posted: Thu Mar 11, 2010 5:13 pm Post subject:

Vicky, the file you posted consists of two PB-files, so it should probably not reside in the device upgrade section... I tried the protocol string, and it fixes the delay that I talked about in my last post. So at least in some sense, this settles the original question; thank you very much!

However, there is another issue: also with the 160ms delay, it is very hard to just enter one keypress (instead of several), thus getting, e.g., 222 instead of 2. There is some "key-released-event" detection using the original keyboard, that fails with our signals. I may have a closer look into this, and chances are that I will even post some ict-files Wink

In the meantime, I think it would be a good idea to get rid of the repetition altogether. Thinking about it, repetition makes sense only with the cursor keys up and down.

vickyg2003 · Posted: Thu Mar 11, 2010 6:17 pm Post subject:

Barf · Posted: Sat Mar 13, 2010 10:57 am Post subject:

I looked into the signals a bit further, and it turns out that an up-signal is generated when releasing a button on the original keyboard. When this happens, the standard distance beween signals, 161ms, may not be observed. The signal is the same as the original one, but with 128 added to the OBC. (Note that all the OBCs in my file was <= 127). There is some debouncing logic in the receiver, so that two normal signals followed by one up-signal is translated to one normal and one up-signal, making it easier to enter e.g. a one-digit number.

Here is one sample ict-file, recorded from the original component:

vickyg2003 · Posted: Sat Mar 13, 2010 11:17 am Post subject:

I will take a look at this, but the ICT file would have saved me the steps of having to decode this. (A picture is worth a thousand words!)