As reported in pronto forums, there is the phenomenon, that IR-Codes are repeated twice (or more?) if used in a macro.
I have analized this for the RC5-Code (from internal data base) with a self made IR-Receiver (SAA3049).
So it is possible to measure when and how long a valid signal is received.

If the code is not used in a macro, the code is received once (of course). The pulse duration is 16 ms
If the code is used in a macro, it is repeated 3 times. The duration of each pulse is 16 ms. The time between the starting edges of two pulses is 112 ms.

It doesn't matter if the macro includes a sequence of RC5 codes, or only one RC5 code and one delay.

Is there any solution to avoid this effect?

In my application it is possible to avoid side effects with a monoflop (130 ms). So a new code is only detected if the time between pulses exceeds 130 ms.
So the triple pulse within a macro is detected as only one pulse. In order to make it possible to detect a new code in a sequence, after each single code a delay (0.1s) is necessary.

So the minimum time between 2 detectable codes is 340 ms (112+112+16+100; 2 gaps, 1 pulse duration, 1 delay(0.1s))
It's a pity, because it is as ten times longer as necessary.

Jochen

Any ideas?

Jochen

Strange, my receiver uses RC5 codes and I've never had that happen in a macro -- yet. :-P

I think, that the code repetition is not a problem for 'normal' hardware, because it accepts a new code only after some 100 ms.
In my hardware I step through a menu structure by number direct access. So it is useful to select it as fast as possible, to have an immediate reaction and not only after 5x 340 ms.

Code sequence to change one value of my hardware:
-reset (ready for new navigation sequence)
-line number (navigation to parameter number)
-page number (navigation to parameter number)
-parameter number (navigation to parameter number)
-parameter value

Jochen