Xbox noname remote.

jon_armstrong · Post by **jon_armstrong** » Thu May 06, 2004 5:35 am

The Robman wrote:That's good work Jon. When I get a chance I will modify your protocol so that it generates the XOR bit.

Let's make sure, I'm right first. One command ("Down") that looked like a good learn didn't fit the parity bit scheme.

jon_armstrong · Post by **jon_armstrong** » Thu May 06, 2004 5:46 am

freebase wrote:Your running now jon_armstrong! But I can't keep up. I have never used PB and really don't understand how protocols work (perhaps now would be a good time for me to explore the forums and learn). I don't know what to do with the protocol (pseudocode?) that you provided on the second line.

You don't have to do anything with PB and I should have been more clear. I was just using the shorthand notation to explain to the other experts what I thought was really going on. For now, I just calculated the last bit for the numerals.

And I figure I need to do something before pasting those OBC codes into KM.....

More clues would be greatly appreciated. What you posted last time worked like a charm and I could actually use my limited experience to get it done.

All you need to do is add a second device upgrade with device=168 (rather than 160) to test the numerals. You will need to pick a different setup code and then use the numbers in the second column starting with 000 and ending in 020 as OBC's for numerals 0 through 10. I am prettty sure 000 will be the Numeral Zero function (but it could also be 020)

Once we test everything, then I can clean up the protocol, and if the Parity bit theory holds up then Rob can add that bit of code and we will be able to get everything into one device upgrade.

Post by **The Robman** » Thu May 06, 2004 6:30 am

If the parity bit theory doesn't hold up, we can go back to what I was thinking originally about this when I first noticed what appeared to be 2 device codes.

As the device code is short, if you expand it to 7 bits, leaving just 6 bits for the command code, you would have 4 different device codes used in this signal. You could then use the two freed up bits in the command code portion to work some mini-combo logic to select those device codes.

freebase · Post by **freebase** » Thu May 06, 2004 9:18 am

I'm still missing something. I tried putting the device codes and associated OBC commands into KM using the NEC1 combo protocol name with no luck. I guess I should be using a different protocol name?

I also noticed that a number of keys were missing from your list: FF, Up, Skip Fwd (CH+)*, Menu, Exit, Display, Info (macro2)*.

I understand about Skip Fwd (CH+) and Info (macro2) since they were not learned properly from the original remote. But I wonder about the others since they were learned to the last memory dump I gave you.

How should I proceed?

freebase · Post by **freebase** » Thu May 06, 2004 9:23 am

One more question. You listed a value for key 10 - where did that come from? I don't have a key 10.

freebase · Post by **freebase** » Thu May 06, 2004 9:42 am

Me again.

I finally managed to learn the last of the missing keys from my Xbox remote. I wonder why waiting a day or so changes my success at these things? - maybe it's the changing light conditions with the sun coming out or something....

Anyway, I've posted NoNameXBOX-3.txt to the usual diagnosis location. I learned the keys to the VCR device button. The keys are CH+ (skip fwd), Macro (Title), Macro2 (Info), 2, 0. The keys are confirmd to work except that just about all of them fire twice per press (it looks like you can deal with that though

Please let me know how to proceed.

Thanks for everything!

Gordon

jon_armstrong · Post by **jon_armstrong** » Thu May 06, 2004 9:43 am

freebase wrote:I'm still missing something. I tried putting the device codes and associated OBC commands into KM using the NEC1 combo protocol name with no luck. I guess I should be using a different protocol name?

Use Manual and enter Protocol 01 69 with the space. Or just load the other device upgrade and change the device to 168 and change the values for the keys in the functions tab. You must also assign the functions to buttons in the buttons tab.

I also noticed that a number of keys were missing from your list: FF, Up, Skip Fwd (CH+)*, Menu, Exit, Display, Info (macro2)*.

I understand about Skip Fwd (CH+) and Info (macro2) since they were not learned properly from the original remote. But I wonder about the others since they were learned to the last memory dump I gave you.

I'll check when I get back home where my decoded learned signals spreadsheet is. I am pretty sure I decoded all the learned commands in the second batch except for a couple that I couldn't figure out like Macro 2.

BTW, the 10 key is just made up. All the numbers are in a progression and Zero can be either OBC'=0 or OBC'=10 in most cases -- it's just a guess. It may do something else, nothing, or be Zero.

freebase · Post by **freebase** » Thu May 06, 2004 11:25 am

Still stuck....

I tried using the 01 69 Manual, Device 160 as you suggested, but I get the error:

Upgrade Protocol 0 = 01 69 (S3C8)
Code not available for this Remote...
End

I also tried pasting your previously provided upgrade code and upgrade protocol into KM but the cells are protected. I pasted them instead into IR and tried to find a way to get the data from there back to KM but no go. I guess I'm just ignorant when it comes to knowing what to do with these various values I'm being given. It is simply amazing what KM is capable of - it's hard to believe that it was possible to reverse engineer these codes in the first place.

More hand-holding would be appreciated

Gordon

jon_armstrong · Post by **jon_armstrong** » Thu May 06, 2004 1:39 pm

Gordon,

Here is an updated zip containing KM Master files for device 160 (most commands) and 168 (numerals).

I went ahead and created an IR file, 6800_IR_file.txt, that you can just load (use IR|File Open and select 6800_IR_file.txt from whatever directory you unzipped xbox_1.zip into) into your 6800 (it's a virgin 6800 with the two devices already installed). TV 0 to 9 will be numerals 0 to 9 and Cable/Sat will have all the commands on the same buttons they were learned to except Macro is on TV/VCR.

Test out the commands and let me know which ones work correctly. BTW, I found the rest of the commands and the Parity bit is now correct the command that I thought was "down" was incorrect.

Please learn whatever commands are missing using the hard tap method I described earlier in the thread.

freebase · Post by **freebase** » Thu May 06, 2004 2:24 pm

Now that's handholding! I guess it was easier to DO than to explain to an idiot eh

Sending me the .IR file forced me to upgrade to the latest version of IR 5.0 (rev 4 is it?) - at least that's out of the way now

You are very close indeed!

Basically everything works. Pressing the 0 button yields a 9 for some reason. The macro (title) and macro2 (info) keys are nowhere to be seen (I learned them in my third file). But everything else is spot-on!

I assume these buttons get combined onto one device at some point?

What's the next step?

Gordon

jon_armstrong · Post by **jon_armstrong** » Thu May 06, 2004 3:16 pm

Here is the latest revision. Same files as befiore only updated. The Macro button should be on the Cable device, TV/VCR button. Macro 2 is on Last/Prev Ch

Also you had learned Ch+ and 2 did those not work?

Once these work, I can probably create a protocol that uses the mini combiner in PB, unless Rob want's to do the Parity bit complement programming. You need to tell me what the commands really are if not the buttons they were learned to.

freebase · Post by **freebase** » Thu May 06, 2004 3:57 pm

Hi Jon,

The file you just posted gives me a file I/O error when I try to load it into IR. I tried both 5.0 and 4.02. Why did you change from .IR to .TXT?

As a result, I couldn't test the two macro buttons or the zero key.

I had learned ch+ and 2 because they were on my list of commands I had not successfully learned. I posted the file before you posted your codes today. You must have figured out the non-working learns because they worked flawlessly using your updates.

I have been using the two macro buttons for "Title" and "Info" respectively since there is no corresponding button on my 6800. Otherwise all of the buttons were learned to the most appropriate labels. I'm quite happy with the layout you have provided so far.

We just need those three missing buttons (part of you last update I couldn't use) and combine them and we;re all set! So... do you have a Paypal account?

Mark Pierson · Post by **Mark Pierson** » Thu May 06, 2004 4:05 pm

freebase wrote:The file you just posted gives me a file I/O error when I try to load it into IR. I tried both 5.0 and 4.02. Why did you change from .IR to .TXT?

The '6800_IR_file.txt' is an IR file and I was able to open it fine in IR 5.0. The two 'XBox*.txt' files are KM upgrade files... you're not trying to open them in IR, are you?

freebase · Post by **freebase** » Thu May 06, 2004 5:41 pm

Thanks Mark,

Isn't that odd....IR 5.0 wouldn't take the .txt file until i renamed it to .ir - then everything worked perfectly.

Okay Jon... All buttons are good. There is not a single problem with any of them - "Print it!"

This has been a great day. I look forward to the combined upgrade. Thanks for al your hard work Jon.

Gordon

Post by **The Robman** » Thu May 06, 2004 5:48 pm

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.