Xbox noname remote.

jon_armstrong · Post by **jon_armstrong** » Thu May 06, 2004 6:09 pm

The Robman wrote:In case I missed it, did you confirm whether that one button does indeed have the parity bit set incorrectly? If is does, then we'll need to go the mini-combo route, if it works with the bit set according to Jon's formula, I'll write the assembler logic for it.

The very bottom bit of the data-bits IS the complement of the parity of the 8-bit function code in ALL cases. I had somehow gotten a bad learn mixed up and thought it was an exception. The last file has the KM Master file, for both device upgrades and all the valid OBC's. The first of my links has the PB file in it.

Here is a summary of the commands:

1010 00010001 1 Dev=10 OBC=017 display
1010 00010010 1 Dev=10 OBC=018 up
1010 00010011 0 Dev=10 OBC=019 left
1010 00010100 1 Dev=10 OBC=020 select
1010 00010101 0 Dev=10 OBC=021 right
1010 00010110 0 Dev=10 OBC=022 down
1010 00100001 1 Dev=10 OBC=033 rewind
1010 00100010 1 Dev=10 OBC=034 play
1010 00100011 0 Dev=10 OBC=035 FF
1010 00100100 1 Dev=10 OBC=036 ch- (skip back)
1010 00100101 0 Dev=10 OBC=037 stop
1010 00100110 0 Dev=10 OBC=038 pause
1010 00100111 1 Dev=10 OBC=039 ch+
1010 01000001 1 Dev=10 OBC=065 macro
1010 01000010 1 Dev=10 OBC=066 macro2
1010 01000011 0 Dev=10 OBC=067 menu
1010 01000100 1 Dev=10 OBC=068 exit
1010 10000001 1 Dev=10 OBC=129 1
1010 10000010 1 Dev=10 OBC=130 2
1010 10000011 0 Dev=10 OBC=131 3
1010 10000100 1 Dev=10 OBC=132 4
1010 10000101 0 Dev=10 OBC=133 5
1010 10000110 0 Dev=10 OBC=134 6
1010 10000111 1 Dev=10 OBC=135 7
1010 10001000 1 Dev=10 OBC=136 8
1010 10001001 0 Dev=10 OBC=137 9
1010 10001010 0 Dev=10 OBC=138 0

freebase · Post by **freebase** » Thu May 06, 2004 6:45 pm

I'm guessing that the last message wasn't for me and that I am still waiting for someone to combine the two upgrades?

jon_armstrong · Post by **jon_armstrong** » Thu May 06, 2004 7:10 pm

freebase wrote:I'm guessing that the last message wasn't for me and that I am still waiting for someone to combine the two upgrades?

It was for Rob. What would be useful would be for you to find out/write up all the information about how you found out about that upgrade, so we can describe it other than NoName xBox remote upgrade in case some one else gets the gear.

If you really want to advance science, when Rob finishes the protocol mod, then you could test all of the remaining 256 possible commands and see if you find anything new. Of course, this has the slight risk that you trigger some sort of reset. But the reason we have a big set of discrete commands is that intrepid IR geeks had to find out what was out there ... Your aluminum foil helmet will probably protect you

freebase · Post by **freebase** » Thu May 06, 2004 8:15 pm

I kind of like "NoName Xbox remote". The name is growing on me. Besides I still have no way of identifying it as anything else

At least there shouldn't be more than two or three remotes for the Xbox.

I'm happy to try and find more codes. I tried to do that for one of the other upgrades I posted to yahoo's files section. It would be nice to find a power on/off for instance.

I had a rather stupid remote for my Panasonic portable stereo. It has a discrete Aux selector on the main unit, but no button for it on the remote. The remote just had the tuner, tape and CD buttons - which I found kind of stupid since you are probably only going to use an Aux connection when you have it mounted in a corner at home...These companies aren't always the smartest - or maybe it was a crappy marketing ploy to get me to buy a real receiver which I didn't find out about until I owned the unit for a while...

Post by **The Robman** » Thu May 06, 2004 9:43 pm

OK, I've written a new version of the protocol which calculates the checksum parity bit, you can find it here: xbox-rob.zip

There's a KM file and an IR file. The upgrade is on the DVD button and only includes those buttons identified in Jon's last post, it's up to you to re-label them to match what they really are and to learn whatever other buttons are on the remote. Jon will probably give you the OBCs once he sees the rest of the learns.

Once you're done re-labelling the functions and adding the remaining functions, could you load your KM file into the file section please. I guess it belongs in the DVD folder.

freebase · Post by **freebase** » Thu May 06, 2004 11:27 pm

Thanks Robman, I'll do all that you ask.

Another small glitch though... The KM file says it was developed with v8.20. I have v8.19 which also appears to be the latest available from yahoo.

For now I'll play with IR to test the new protocol until the new KM becomes available... (I always want to keep those keymoves to a minimum

Mark Pierson · Post by **Mark Pierson** » Fri May 07, 2004 4:37 am

freebase wrote:The KM file says it was developed with v8.20. I have v8.19 which also appears to be the latest available from yahoo.

KM v8.20 is the current release. I must not have updated the description in the Files area.

Post by **The Robman** » Fri May 07, 2004 6:26 am

freebase wrote:Thanks Robman, I'll do all that you ask.

Another small glitch though... The KM file says it was developed with v8.20. I have v8.19 which also appears to be the latest available from yahoo.

Like Mark said, 8.20 is the current release, but even so, my upgrade doesn't utilize any new feature that isn't also in 8.19, so you can just click past the warning and use 8.19 to manipulate the file I created.

But before you mess with the KM file, test the IR file to see if it works.

I've thought of a way to streamline my code even more, so I'll be coming out with a slightly smaller version either this evening or tomorrow.

johnsfine · Post by **johnsfine** » Fri May 07, 2004 7:32 am

I don't have time now to add this protocol to DecodeIR. But I want to get back to that soon, at which point I hope this thread contains a suggestion for the NAME of the protocol (preferably some name that won't generate confusion relative to the RCA protocol normally used by xbox).

A name is also all that's likely to be needed for the easier job of adding this to protocols.ini for RM.

Post by **The Robman** » Fri May 07, 2004 8:17 am

Freebase,
I have just updated my zip file to include a second IR file which contains the streamlined version of the protocol. This new version has not been tested, so if it doesn't work (and the original one does) just let me know and I'll look at it. Also, could you tell us where you bought this Xbox, and better yet, if it was online, could you provide a link? This might help us determine who really made it.

Jon,
My executor is written based on the assumption that only the variable data bits contribute to the parity bit, but I don't know if this is true or not. I suspect that the fixed data bits may also contribute, but as the current fixed data (binary 1010) XORs to zero, I can't tell.

In case you're interested in what I did to create this exec, I opened your PB file in PB, then I switched the 1 and 0 times (to save me having to complement the results of the checksum) and I reduced the number of device code bits to 4. Then, once I had copied the code over to IR, I added logic to calculate the checksum. I altered the R28 bits so that the command code has one byte of R13 bits and one more of R24 bits.

Also, just FYI, when you use the Manual Settings option in KM for a protocol like this, in order to be able to enter the device codes correctly all you need to do is select the correct device code length in the KM drop down.

John,
I notice that when you enter an alternative lead-out time in PB, it extendes the controls bytes (ie, R28, etc) out to R2B. I don't have complete documentation on what all the bits in R2A thru R2C do, do you have such a list that you could share please?

freebase · Post by **freebase** » Fri May 07, 2004 8:22 am

The IR file you provided is not compatible with my remote (it gives me a warning when I try to upload). So I figured I needed to use KM to change the remote to the 6800 and then use the new upgrade codes in IR to upload to my remote. Then there's the small matter of trying to find new codes which would probably change your protocol still firther.

I look forward to the smaller code, but I figured it would still be useful to verify the current one.

I guess I'll spend some time on ebay and see if I can find some unique way of identifying this remote versus all of the others.

TTFN,

Gordon

Post by **The Robman** » Fri May 07, 2004 8:44 am

freebase wrote:The IR file you provided is not compatible with my remote (it gives me a warning when I try to upload).

What warning does it give? Those files were based on the 6800 file that Jon created. Regardless, I just recreated the files using the original file of learned signals you posted, so these ones should definitely be compatible.

I've included them in the zip, there's called...
6800-Xbox-version1.IR
6800-Xbox-version2.IR

As for the brand thing, I've just done a bit of Google searching myself and I think the brand is simply "Xbox".

John,
I would recommend that we call this new protocol "Xbox". I think the situation is somewhat similar to the one with Replay where you have one set of remotes where the brand name is "Replay" that use the Replay (aka RC6a) protocol, and you have another set of remotes where the brand name is "Panasonic" that use the Panasonic protocol. Another similar example might be Tivo where most remotes use the Tivo protocol but the Sony branded remotes use the Sony protocol.

freebase · Post by **freebase** » Fri May 07, 2004 9:02 am

The warning I get is:

The signature in the remote is different from the signature you are attempting to write. This indicates that the data you are trying to write may have come from an incompatible remote. Copying the entire contents of one remote to another can only be done safely if both remotes are identical. Are you sure you want to do this?

The remote type listed in the IR file is a URC-881z/801x/601x.

I've used the new version of KM to change some of the function names to match the original remote more closely and have created the upgrades for my particular remote. I'll test once my daughter stops whatching her movie

I don't think we can use the name "Xbox". There is already an upgrade in the DVD section of yahoo with that name and it is NOT compatible with the version of the remote I have. The one already posted is probably the official one sold by Microsoft. Mine is definately not a Microsoft one.

freebase · Post by **freebase** » Fri May 07, 2004 9:29 am

Hi Robman,

The test of your new protocol did not go well. The only buttons which worked are right, select, ch-, stop, macro, macro2, 1, 4, 5. (I don't think I caused the problem with the work in KM since it was the macro and macro2 buttons I changed in KM and they still work.)

If it helps, I had a perfect test with the files Jon posted at the top of the third page of this topic.

It's odd that you got some buttons from one device and some buttons from the other device to work. I would have thought that all of the working buttons would have come from the same device

What next?

freebase · Post by **freebase** » Fri May 07, 2004 9:45 am

More testing...

I finally found:

I've included them in the zip, there's called...
6800-Xbox-version1.IR
6800-Xbox-version2.IR

I had to redownload the xbox-rob.zip file - they weren't part of my original download.

The 6800-Xbox-version1.IR file behaves exactly like the xbox-rob-KM.txt file that I had modified and moved into IR.

The 6800-Xbox-version2.IR file is working well at all. i.e. When I hit play the light on my 6800 stays on permanently. None of the buttons that I tried worked.