Please can anyone help me...

I have just chipped my Xbox with one of these new chips that need the power button to be pressed for at least 2 secs. This is the code I use for the vellman remote receiver, but I need to send the button held for 2 secs.

7000 006D 0000 0008 0011 000D 0010 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 00BB

Thanks in advance

Craig

That is a database command for RECS80:1:34. John Fine may know how to force a minimum number of repeats in that database format, but if not I can probably use MakeHex and create a "learned" format command to do what you need, but it may be a day or so before I can get to it.

Well I certainly would appreciate the help. I spent a couple of hours today reading docs on the type of code that 7000 was and tried to make it longer but failed miserably.

I may have to steal my kids Xbox with the older type chip in that boots normally. :-(

That will make me way unpopular with them.

Craig

We'll try to keep you out of trouble with your kids.

I went back to Eigeny Oulianov's document that describes the database commands [Link: remotecentral.com]

I think this will work, but I will post a description of the process so that any of the real experts can detect any flaws in my logic.

Here is a breakdown of what that command means:

7000 006D 0000 0008 Normal preamble 7000 means variable length database command, 006D is a parameter that indicates wavelength, and where 8 is the number of burst pairs that follow.

0011 ID parameter and indicates the table of values for the words that follow listed below.

000D Number of two-byte hex words that are relevant

0010 Indicates what follows is a repeat segment

0002
0017 Toggle Bit
0003
0003
0002
0002
0003
0003
0003
0002
0003
0000

00BB Filler

Table of values (+ is carrier On, - is carrier Off)
-------------------------
0000 =+158,-55,563
0001 =+158,-42,783 not used
0002 =+158,-7,415 Logical 1
0003 =+158,-4,917 Logical Zero

I calculate the length of the IR command to be 123 mS and to get two seconds that will be a total of 16 commands (or 15 more). You must adjust two hex words. The fourth word 0008 becomes 8+15 x 6 burst PAIRS (98 decimal => 0062) and the sixth word 000D becomes 13+15 x 12 words (decimal 193 => 00C1)

7000 006D 0000 0062 0011 00C1 0010 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 0002 0017 0003 0003 0002 0002 0003 0003 0003 0002 0003 0000 00BB


Let me know if this works, obviously this is a "use at your own risk", hopefully everthing doesn't turn purple :-) Also, I think some versions of the Pronto will repeat the repeat segment some defined number of times (my guess is three) so This command could be way too long, but see what happens. It is also possible that it won't accept a database command this long.

What model Pronto is this for? We've had varied results from hand edited "7000" format codes, probably depending on the model of Pronto involved. Some codes crashed PENG. Some got translated by ProntoEdit or PENG back into the simpler code we were trying to escape. Some failed for reasons unknown. Some worked.


...


Too much modesty there Jon. On this narrow subtopic of IR encoding maybe Eigeny is the only "real expert". But if there is more than one real expert, Jon is one of them. (On IR encoding in general, Jon is of course one of the real experts).

On first reading of your post, I did think I spotted a flaw. I thought you were saying 11 was one of the strange IDs with more than two values in a BurstSeq:


Then I realized I was just misinterpreting the second comma there. If anyone else was confused (sometimes it's just me) pretend the second comma isn't there.


In case someone who didn't understand Eigeny's document is trying to follow this, the main step is inserting 15 extra copies of the main body of the command (as broken out above in Jon's description of the original hex sequence). But the overall command includes two different counts of parts of it's own length. The sixth word counts the body length. The fourth word is half of a count of a larger part. Rather than go through all the boundary conditions of what's in and out and compute the counts from scratch, Jon noted that the item being inserted 15 times was 12 words long, thus adding 15*12 to the previous value of word six and adding 15*6 to the previous value of word four.

All looks right to me, but I haven't checked too carefully, nor tried to paste into ProntoEdit to see if it's rejected or scrambled.

I will test it shortly, I have a 7000 and an RC9200. Thanks for all your help so far.

Craig

OK tested it out, works ok on RC9200, boots xbox fine, tested on 7000, code dissapears, unable to learn it or cut and psste it /import ccf from rc9200.

Any ideas?

Craig

Try this in the learned format:

Device Code: 1 Function: 34
0000 006D 00C0 0000 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843

I created this by using MakeHex written by John Fine. This would be the normal protocol file for the Variant of RECS80 that the basic 7000 command produces:

'*********************RECS80.irp********************
Device=1
Function=34..34

Protocol=RECS80
Frequency=38000
Time Base=158
Zero=1,-31
One=1,-47
Suffix=1,-352
First Bit=MSB
Form=;1:1,T:1,D:3,F:6,_
'***************************End of File**********

This is protocol to create the two second held command:
'*************************RECS80-2SEC.irp****************
Device=1
Function=34..34

Protocol=RECS80-2sec
Frequency=38000
Time Base=158
Zero=1,-31
One=1,-47
Suffix=1,-352
First Bit=MSB
Form=1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_,1:1,T:1,D:3,F:6,_


'***************************End of File**********

Finally, John thanks for the kind words. For those that don't know, John in addition to writing MakeHex has written a decoder that can decode and identify ~50 IR protocols and uses it to decode Pronto ccf files (including the 500X, 600X, 90XX and 7000)database commands, RTI TT files, and raw learned commands in OFA remotes.

OK, tried that code, the TSU 7000 turned it into this code when saved.

0100 000D 0000 0008 0003 444D 0003 444D 0003 444D 0003 444D 0003 444D 0003 444D 0003 444D 0003 444D

I just cut and pasted the codes you sent into the action.

My IR receiver didn't even recognise it. Thanks for trying...

Craig

You only pasted in the hex, right? Not the header
"Device Code: 1 Function: 34".

The only other thing I can think of is either holding down the "button" for 2 seconds with this command:

0000 006D 0000 000C 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 0843

It should keep repeating unless you release the button.
Or you could create a macro with this command repeated 16 times.

0000 006D 000C 0000 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 011A 0006 00BA 0006 00BA 0006 00BA 0006 011A 0006 00BA 0006 03CE

I assumed that a macro will take ~30mS to execute and reduced the final off time. If it doesn't work, then learn with the RC9200 the macro command transmitted from the 7000 and post the learned hex, and I can adjust the final off time.

As I'd expect, the ProntoEdit software detected the obvious repeat pattern and compressed it. To create a long signal you need to get around that. That means introducing some changes into the signal in a way that won't matter to the actual device but will hide the repeat structure from ProntoEdit.

I think that is most easily done by tweaking the gaps between frames. But I don't know how much they should be tweaked.

Second and more disturbing, it seems to have gotten confused by the short pulses and switched to unmodulated form, but then it has lots of bugs in handling unmodulated, so it garbled the signal into total trash. I can't be sure of all that without some experiments with the same version of ProntoEdit you're using (which is that?) but if I'm guessing right that the short pulses start the chain of events leading to trash, we can just use longer pulses.

The actual device almost certainly won't care if the pulses are significantly longer (as long as the total of pulse plus following gap doesn't significantly change), but longer pulses may sidestep the ProntoEdit bugs.

Again I'm not sure how much. If Jon doesn't have time to help you experiment soon, I'll get back to this thread later.

The NG models discard the final off time entirely when they load a signal without a repeat part.
I think their automatic delay between steps in a macro is so slow that with zero final off time it still will be too big a gap for a RECS80 device.

It still may be worth trying, but I'd bet against it working.

All very confusing I must say, but if it helps, I'm using PENG for the TSU7000, Pronto Edit for my Pro, Tonto for the RC9200 and Pro.

I would really like to sort this out, but the kids xbox is looking more and more tempting.

Craig

I gave John's suggestion a try. I just increased the On times to 1 mS and shortend the off times by the same. So the bits are still the same total length as before.

0000 006D 00C0 0000 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 00F7 0026 0098 0026 0098 0026 0098 0026 00F7 0026 0098 0013 00E4

Jon, what happened to the lead out?