This is the code for an On-Off button that requires a full 3.250 seconds of activation, before the device will come on.......
can anybody give me a hand with this, as I have tried the double learn but no cigar as yet....


0000 006d 0001 0011 0140 00a0 0014 003c 0014 003c 0014 0014 0014 0014 0014 003c 0014 003c 0014 003c 0014 0014 0014 003c 0014 003c 0014 003c 0014 0014 0014 003c 0014 0014 0014 0014 0014 0014 0014 02e5

Thanks,

Bill
[email protected]

The repeating part of that signal is

0000 006d 0000 0011 0014 003c 0014 003c 0014 0014 0014 0014 0014 003c 0014 003c 0014 003c 0014 0014 0014 003c 0014 003c 0014 003c 0014 0014 0014 003c 0014 0014 0014 0014 0014 0014 0014 02e5

It's about a 20'th of a second long. You may need as many as 64 copies of that sent after the initial part to add up to 3.25 seconds.

You could try aliasing that repeat signal 64 times and see how the device behaves (and how long it seems to take).

The Pronto adds some delay between steps in a sequence, so you might need less than 64 copies, or (if the device counts copies rather than time) you might need the full 64 and it might take over 3.25 seconds, or it might not work at all if the device decides the copies are coming in too slowly.

Also, I've never been sure exactly what a Pronto does when a signal constructed as repeating is used in a sequence. It might send some small fixed number of copies. If it sends 3 copies, you'd only need to alias it 21 times to send 63 copies. That should be an advantage to representing the repeat part as a repeat part (as I did above). But some people have had that fail and found it works when you represent the repeat part as a one_time signal.

0000 006d 0011 0000 0014 003c 0014 003c 0014 0014 0014 0014 0014 003c 0014 003c 0014 003c 0014 0014 0014 003c 0014 003c 0014 003c 0014 0014 0014 003c 0014 0014 0014 0014 0014 0014 0014 02e5

I don't understand why that would work better, but I've gotten that feedback enough that there must be a reason. If you do that, you need one copy of the orriginal (what you posted) followed by the full number of copies required of the repeat (if you want 63 copies you must alias it 63 times).

On some Pronto models, I think you can speed up the repeat rate (compensate for the added delay) by reducing that last number (the 2e5) to something smaller. That sort of edit makes more sense in the last version I showed (giving the repeat in one_time form).

It's also possible to splice together a signal containing multiple copies of the original (which avoids the issues associated with delay between steps in a sequence). I keep forgetting the max size limit on those. I think that limit is too low for 64 copies of this.

John, I think some had mentioned a long tinme ago hat it sends 5 repeats

I'd like to review that thread if you remember any keywords distinct enough to allow a search, but I think I have enough feedback in similar situations to believe it DOESN'T consistently send 5 copies. Maybe it varies by model of Pronto. Maybe it varies by some other aspect of the signal itself (length in bursts or length in milliseconds or ???).

Obviously it would be firmware, so it can be changed at any time, and on any model, and from one firmware to an other.

Of course they could change it from one firmware rev to the next within a model and clearly in the NG (TSU3000 etc.) models they did so. I haven't seen any hint that they ever did that to other models. But I still suspect that they may have changed it between models even before the NG (though I do understand you that they are no more nor less ABLE to change it between models than between any two firmware revs in one model).

Johnsfine:

Thanks for all your help and input...let me see if I have this correct.

1.- Go to button properties of my ON-OFF button.
2.- Enter under "Action" - "Alias"
3.- Enter one entry of the standard code.
4.- Enter 64 entrys of the repeating code.

Is this correct??
Why not just paste up the standard code and 64 entries of the repeating code under one entry?

This is crazy, I have emailed the company and asked them to verify the 3 second hold down..seems a bit much!!

Thanks,

Bill
[email protected]

I'm not really an expert in ProntoEdit. Hopefully someone else will answer the ProntoEdit aspect of the above question.

I think you want two buttons defined on an unused page, one of which holding the orriginal code and one holding the repeat part, then you want the real button to alias the first one once and the second 64 times.

I'm not sure what you mean by "paste up ... under one entry". I do know how to splice together a long signal as one learned signal:

First you need the header:
0000 006d 0??? 0000
where the ??? is replaced by the hex value of 1+17*N where N is the number of repeat parts you want, so if N were 14, 1+17*N is 239 decimal which is 0EF hex.

Next you need the fixed part:
0140 00a0

Next you need N copies of the repeat part:
0014 003c 0014 003c 0014 0014 0014 0014 0014 003c 0014 003c 0014 003c 0014 0014 0014 003c 0014 003c 0014 003c 0014 0014 0014 003c 0014 0014 0014 0014 0014 0014 0014 02e5

If you do all that for N=14, you should get a valid string of Pronto Hex for 14 copies of the repeat part. But if you try that for 64 copies I think you'll exceed some limit on the max size of a Pronto Hex string and it won't work at all.

I agree with John, chances are that 64 would be too long, never tried it. I think the main reason to do the 64 aliases is that

1) you still have the original code if needed. For instance many projectors are setup so that a short burst is OK for on while off needs a long burst, so doing it this way you still have the original code

2) Like John said, is it really 64 or is it less (or more) when you press the button you continue pressing until something happens (is it exactly 3.25 sec that are needed?) this way you can add aliases or remove them until you have something stable

Good Point and you just brought something to light!!

-I pulled the code off the Projector ON/OFF button by doing the typical Pronto IR "Learn".

But when I press the The Pronto button and hold it down all I get is a short burst...( I can see it in the LED's of the IR/RF repeater).......however when I press ON on the orginal remote and hold it down I can see a continous flash on the IR repeater until I release the button...maybe what I need to look at is the "HOW" to make the Pronto button work until I release it...??

Am I on the right track??

-Bill
[email protected]

I would try relearning the code. A well learnt code in the Pronto should work like your code on the original remote. There is the possibility that a long press sends a different code then a short one, but all the Projectors that I know that need a long push just send the same code for a long time.

The code you posted is correct for transmitting as long as you hold the button down. Since you report it doesn't work that way, I assume something else is wrong.

I know that the repeat while held feature of a Pronto only works when there is just a single action on the button. No other IR commands, no jumps to other pages, nothing but sending the one signal. If that doesn't explain the problem you'll need help from someone who knows ProntoEdit better than I do.

Don't bother trying to relearn the code. It is a perfectly good learn of JVC protocol. I'm sure (from looking at a lot of JVC samples) a long press doesn't send a different code.

When it failed to repeat while held in the Pronto, that is due to some aspect of the way the action is assigned to the button and is not due to anything about the learned signal itself (as mentioned above, the easy theory is that there is more than one action on the button, which totally disables the repeat while held behavior).

It Works!!

Set up the primary signal followed by "Johnsfine" repeating part of the signal 9 times...and It worked not in 3.2 seconds when using the standard but 50 seconds seconds using the pronto 60000 in the RF mode......
Why such a difference I don't know unless the stock remote is falsing some unknown garbage but this should have shown up in the "learned" mode...

But Happy Days..it works...

Thanks Guys for all the help and hand holding and direction!!

-Bill
[email protected]