Unfortunately the new cleaned code is also not working (Error 0030 in PENG 1.2.4.0), so that the only way is to split the code (or to change the Tuner...)

I have the same version of PENG (even though I have no remote to go with it) and it doesn't give an error when I posted the corrected version of the cleaned code.

I have also no problem when a post the cleaned code. I got it when I connect the RU950 to the PC (USB) and I press "Test IR" in PENG.
From my point of view, it shows that the RU950 is not capable to handle the long code properly.

I'm curious if you made any progress with that.

I'm sure other people will be trying to use the Sony DSP signals with the TSU3000 and some of them will run into the same problem with the whole signal that you had. Is the cut apart signal a practical method?

I'm also curious about the timing of the cut apart signal. There are a few PENG problems that seem to prevent getting good control over that timing. So this method doesn't control the size of the gap between parts and it doesn't control the number of copies of the first part. I'm curious why that worked. Most likely the Sony device doesn't care much about the timing. But maybe the remote accidentally hit near the right timing. If you learn the five part sequence (as one signal) from the 950 into the 890, the hex stored by the 890 would tell us some or all of those answers.

I'm also curious about the problem with the cleaned up code. If the cut apart code works, then it doesn't really matter. But how did you get the SAME error message for the version with the typo vs. the version I think is correct? The first I can't even paste into PENG because the data isn't consistent with the header. The second I can paste.

At the moment, it seems to be the only method which works


I really have no idea why this solution works, but I'll try to send the RU950 signal to the RU890 and to save it as one code. I'll let you know asap.


I also thought about the problem with the cleaned up code. The only thing I can say is that PENG has probably some bugs too and it's not able to handle "long codes" properly (connection problems with RU950, etc.). Philips should work a little more on it...

Anyway, thanks again for your help -> the situation is slowly improving!!

Hello,
You guys are way ahead of me! I am trying to do a similar thing with a bang and olufsen remote but I have no idea how to break the string up. any suggestions?

I think it's a different set of problems.

There are problems with signals that include durations longer than 255 cycles (as the Sony DSP signals do). There may be problems with very long signals (such as the Sony DSP signals). I don't understand the results reported here well enough to be sure whether the total length was really an issue.

Breaking the string up would fix both the long durations and the long total, but it can only be done at points within the signal where the receiver doesn't care about accurate timing (which in Sony DSP are exactly the points at which the durations are over 255 cycles).

There are also problems with high frequency (I'm pretty sure B&O is high frequency). There are also problems with very short durations (most high frequency signals also have short durations, but I don't know about B&O).

Breaking up the signal is useless for either of those problems and can't be done for B&O anyway because there are no points in a B&O signal at which the receiver doesn't care about accurate timing.