That indicates that we need at least two copies of the Russound code. The JVC may just need a longer space before it. The Russound code will tend to set the JVC's AGC too high. A longer space between Russound and JVC may help.

Try this...
0000 006A 0000 0023 0015 003F 0015 0015 0015 003F 0015 0015 0015 003F 0015 003F 0015 003F 0015 003F 0015 0015 0015 0015 0015 0015 0015 0316 0015 003F 0015 003F 0015 0015 0015 0015 0015 0015 0015 003F 0015 0015 0015 003F 0015 0015 0015 003F 0015 003F 0015 003F 0015 003F 0015 0015 0015 0015 0015 0015 0015 0316 00E2 0071 004B 0094 0094 03B5 00E2 0071 004B 0094 0094 063A

It's one that worked for russound earlier with the final space increased to let the AGC fade a bit.

Dave, the code you just posted worked for Russound but not JVC.

BTW here is what PPENG converted it to.

0000 006A 0000 0023 0015 003F 0015 0015 0015 003F 0015 0015 0015 003F 0015 003F 0015 003F 0015 003F 0015 0015 0015 0015 0015 0015 0015 0319 0015 003F 0015 003F 0015 0015 0015 0015 0015 0015 0015 003F 0015 0015 0015 003F 0015 0015 0015 003F 0015 003F 0015 003F 0015 003F 0015 0015 0015 0015 0015 0015 0015 0319 00E2 0071 004B 0094 0094 03B3 00E2 0071 004B 0094 0094 0648

I don't know if this is a big change or not.

Mark

That's a minor change but we don't know what is actually being transmitted. From other threads there's evidence that the firmware sometimes truncates codes when they are sent.

I'm afraid I'm out of suggestions.

Well thanks anyways Dave. I appreciate your help on this problem, and all the other posts you do. Your tips and John's have helped me in the past, even when they were directed at someone else's questions.

CodeGenPro™ will let you experiment with things like this. You can insert an extra sequence of burst pairs with a few mouse clicks and see a graphic of the resulting code so it's easier to grasp what's going on. Changing the carrier frequency, switching from a single to repeating code, or adjusting pulse/space durations also only take a few mouse clicks.

I'm trying to finalize the documentation and then set up a link where people can buy it ($12) and all this experimenting is merely delaying that.

Dave Houston
CodeGenPro™

Dave,

Can I be a beta tester? How long will it be before I can get a copy of CodeGenPro? I want to learn how this stuff works.

Thanks,
Mark

I think I'm starting to understand the behavior, so I have a couple more to try:

0000 006D 0000 0018 0141 00A0 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 003C 0014 0014 0014 003C 0014 0014 0014 003C 0014 003C 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 0994 00D0 0068 0045 0088 0088 0368 00D0 0068 0045 0088 0088 0368

0000 006D 0000 0029 0141 00A0 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 003C 0014 0014 0014 003C 0014 0014 0014 003C 0014 003C 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 0368 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 003C 0014 0014 0014 003C 0014 0014 0014 003C 0014 003C 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 0994 00D0 0068 0045 0088 0088 0368 00D0 0068 0045 0088 0088 0368

John! You are my hero!

The second one works! The JVC is a little slower at reacting to it, and it jumps a couple levels each button push, but it works. Good enough for me. Would you mind doing my vol- and mute?

Thanks so much,
Mark

Nevermind mute, Russound doesn't have one.

Mark

That's weird. The difference is a lead-in before the JVC code (which makes some sense but is certainly counter-intuitive given that JVC doesn't normally use one) and longer space after the JVC code. Why the latter should make any difference is strange.

Another point of interest is that the final code has more than 5 unique time intervals. Supposedly, that's a no-no.

This message was edited by Dave Houston on 10/08/04 13:39 ET.

I don't think you posted vol- signals, but from that CCF file I mentioned, I think the Russound vol- at JVC frequency would look like

0000 006d 0000 0004 00d0 0068 0045 0088 0088 0045 0045 0304

from plent of JVC sources I expect it's vol- is

0000 006D 0001 0011 0141 00A0 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 003C 0014 0014 0014 003C 0014 003C 0014 003C 0014 003C 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 096C

Splicing those together in the form that worked for vol+ is

0000 006D 0000 002B 0141 00A0 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 003C 0014 0014 0014 003C 0014 003C 0014 003C 0014 003C 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 0304 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 003C 0014 0014 0014 003C 0014 003C 0014 003C 0014 003C 0014 003C 0014 003C 0014 0014 0014 0014 0014 0014 0014 096C 00d0 0068 0045 0088 0088 0045 0045 0304 00d0 0068 0045 0088 0088 0045 0045 0304

There are many different ways this might be tweaked to improve the JVC timing, especially by playing with the values of all the 3 digit numbers (each of which represents a long pause, whose correct length I can barely guess).

I don't know Dave, but I won't knock it if it works! This is so cool. Now if I get the vol- my system will be perfect (in my eyes, and hopefully the wife's). Thanks for both your hard work and efforts on my problem.

Thanks again,
Mark

John,

It works just like the Vol+! Thanks so much. Now if someone is in another room, they can still use the volume buttons to control the russound the same as they would control volume in the HT. It should appear to the user that the volume is being controlled by the same device no matter where they are. Thanks so much.

Mark

There are a whole lot of changes. There are now two full JVC frames rather than one. That's probably the change that matters.


JVC normally has a lead-in before the very first frame but not before repeat frames. All I know about that lead-in is based on what JVC remotes send, not based on specific knowledge about what JVC devices require. That lead-in might be worthless or it might be important.

I don't know if you can get a real JVC remote to send a single frame. I don't think I've seen it done. The results here seem to imply the JVC device requires a minimum of two frames in order to believe the signal. But this test isn't enough to be sure of that.


I just matched what I've seen in real JVC remotes. No idea if it helped. Maybe it hurt. Each of these factors could be independently examined by other tests, but my first goal was to get something with a maximum chance of being understood by both devices. That worked and got something that's understood but not smoothly (bad in timing).

BTW, the two JVC frames is NOT the reason the JVC now sees the command as two vol steps. That is because the Pronto repeats the whole thing but slowly enough that the JVC can't see it as a long press but rather as seperate short presses (two frames per press).


I thought I explained and convinced you last time. More than 4 unique time intervals is NOT a no-no. More than 4 unique time intervals automatically switches to a different internal encoding system which has a much smaller capacity for total number of burst pairs. I forget both limits but the results here indicate that 29h burst pairs is still short enough for that shorter limit.

You IR guys are awesome...I bow to you...

Dave D'Arche