Code for Osmart brand XBox DVD Remote

[Flavor]

This is my first post here, so I'll try to follow the form.

Link To Picture Of Osmart XBox Remote
Device: XBox DVD Remote by Osmart (ITEM# CY-860)
Type of device: DVD
JP1 Remote model: Radio Shack 15-2104 6-IN-1 AV
JP1 user: Yes (Borrow cable from friend)
Still have original remote: Yes
Checked the file section: Yes
Learning remote: Yes

Here's the problem. I learned all the buttons from my XBox remote to my 15-2104. Though, not a single one of them will do any repeating if the button is held. When I look in IR.EXE, it shows that the all have a "Sent Once" entry for each button, but none of them have a "Sent Repeatedly" or "Upon Completion" entry.

I use XBMC (XBox Media Center) and MythTV among other things, and sometimes it's really annoying to have to press the arrow buttons MANY times to traverse a menu. I should be able to just hold the arrow button down. I assume you get my point.

I'll include a block from the down arrow so you can see what my learned signal looks like.

DVD: Down
-------------
Frequency: 37914
Sent Once When Key Is Pressed: +500 -526 +1422 -528 +500 -1538 +1422 -528 +500 -1538 +500 -1538 +500 -1538 +500 -1538 +1422 -528 +500 -1538 +1422 -528 +1422 -528 +500 -1538 +500 -1538 +500 -10904 +500 -526 +1422 -528 +500 -1538 +1422 -528 +500 -1538 +500 -1538 +500 -1538 +500 -1538 +1422 -528 +500 -1538 +1422 -528 +1422 -528 +500 -1538 +500 -1538 +500 -10904
Sent Repeatedly While Key Held:
Sent Once Upon Completion:

Is there anything I can do to get this working better? Oh, and I should mention that I learned with fairly quick keypresses because when I would hold it down, my 15-2104 would not learn them.

Thanks!

[Capn Trips]

Was there any decode information (Protocol, Device, Subdevice, OBC/EFC/Hex)? If so, build your upgrade and then if it's one of the standard known protocols, there is likely a way to tweak the protocol (or, simply switch from NEC1 to NEC2, for example). If there is no decode info, post your learned IR file and link to it here, and one of the experts will examine it.

[Flavor]

Here's a link to my .ir file.

RadioShack_11-02-05.ir.zip

I don't see any decode info. I'm really no expert on this stuff, but here's a screenshot. Maybe that's better than me trying to explain.

Screenshot

Thanks!

[Capn Trips]

It looks like a new protocol, which will require someone smarter than I to help. Wait a few hours, they will come.

[Flavor]

Thanks for the help, Capn Trips.

I've been dealing with this issue for probablly over a year, now. I just finally needed to do some other stuff with the JP1 cable, so I re-visited this problem. Though, this is the first time I've ever asked for help about it. I think I can afford to wait a few more hours. 8)

[johnsfine]

I see you used version 2.14 of DecodeIr.

I'm using version 2.28 (which is a little strange since the change log says 2.30 is current). Version 2.28 decodes your signals as GXB protocol.

The change log says GXB protocol has been decoded this way since version 2.23

I don't recall whether anyone has yet added KM or RM support for GXB protocol.

Edit: So I checked RM. It has a choice for GXB. Note that, unlike most protocols, this one takes the device number as a column on the functions sheet, not as a field on the General tab. Then it needs 2 bytes of hex cmd for each function. Again I don't recall detials, but I assume GXB has check bits that were too complicated for whoever wrote the executor, so it was simpler to use two byte hex commands.

[johnsfine]

I think I can afford to wait a few more hours. 8)

What makes you think it takes hours to get a good answer here.

BTW, the current version of DecodeIr is normally available at
http://john.fine.home.comcast.net/ir/Decode_IR_DLL.zip

BTW2, something is wrong with your learned signal for the digit 9. There is a lot more there than for the others and DecodeIr is decoding the extra stuff as GXB device 0, OBC 0, which is obviously wrong.

I'm not sure how much of that is due to a learning glitch (at least some of it) and how much if any is a flaw in DecodeIr that I ought to fix. It will be quite a while (if ever) before I have time to investigate that.

But in general you should look for the single most plausible decode in any multiple decode situation and ignore the extra. There are exception situations (such as Pioneer protocol) in which you want info from more than one decode line. But beginners should start with the rule of using only the most plausible. That rule is correct in this case, and even a beginner (after looking at the decodes for 7 and 8) should see the plausible decode for 9 is device 10, OBC 137.

[Flavor]

Thanks for point that out, johnsfine. I just got DecodeIR 2.29 which it said was submitted by you.

Anyway, here's my new screenshot. Though, I must say that it doesn't reall mean anything new to me. Obviously, I'm a noob at this.

Screenshot

I really appreciate the help, though. At least I feel like I'm getting somewhere. Last night I was downloading XBox remote upgrade files and none of them worked for me. I felt like I was getting nowhere. I suppose they were all "Microsoft" official brand codes or something. Mine is a junky knockoff.

[Flavor]

I think I can afford to wait a few more hours. 8)

What makes you think it takes hours to get a good answer here.

Here's why I said that.

It looks like a new protocol, which will require someone smarter than I to help. Wait a few hours, they will come.

[johnsfine]

Thanks for point that out, johnsfine. I just got DecodeIR 2.29 which it said was submitted by you.

That's why I thought is was strange that I'm using 2.28 and my change log says 2.30. I need to be a bit more careful about copying the latest version to all the places it belongs.

Anyway, here's my new screenshot.

Please cut back on the use of screen shots. They're not really appreciated here (though in that first case it did tell me which DecodeIr you were using). All we really needed was the URL of the .ir file. From that I could have deduced you weren't using the current DecodeIr.

Though, I must say that it doesn't reall mean anything new to me. Obviously, I'm a noob at this.

That's getting into the basics of using JP1. There's some often quoted URL for that, but I don't have it handy. In summary you should:

Use RemoteMaster to create a new setup code containing all those signals (which requires copying the information one function at a time from IR's learned signals list so RM's functions tab).

Load the device upgrade and protocol upgrade from RM into IR.EXE

Delete all the learned signals.

Save the result to a .ir file and upload it to your remote to test.

[Flavor]

BTW2, something is wrong with your learned signal for the digit 9. There is a lot more there than for the others and DecodeIr is decoding the extra stuff as GXB device 0, OBC 0, which is obviously wrong.

I'm not sure how much of that is due to a learning glitch

Yeah, I actually noticed that, myself after I got DecodeIR 2.29. I assume it's a problem from when I learned it.

From looking at your site, it seems that you must have seen this "nonstandard Xbox remote" before. Do you have any more info from that one? Do you have an .IR file from that one?

And sorry about the screenshots. I assumed that it would be the easiest way for others to see my problem. I can remove them.

I'm still concerned about my initial key repeating problem. Do you expect that using RemoteMaster to create a new setup code will fix that issue?

[johnsfine]

it seems that you must have seen this "nonstandard Xbox remote" before. Do you have any more info from that one? Do you have an .IR file from that one?

My memory is really rotten and this forum has a search function. I just now used search to find the thread:
http://www.hifi-remote.com/forums/viewt ... 9399#29399
I just glanced there, didn't reread the whole thing, so I still don't recall most of what I said there.

I'm still concerned about my initial key repeating problem. Do you expect that using RemoteMaster to create a new setup code will fix that issue?

I don't know why long presses wouldn't learn right for you. The key repeating problem is because of the short presses you used to learn.

I am pretty confident the upgrade will do repeats correctly. I understood this protocol's repeat pattern when I built the upgrade and if there had been a problem duplicating that in a JP1 executor, I would have put in a lot of comments about that problem.

Since you can discard your learned signals after using the decodes to build the upgrade, you don't really need to worry about any of the learning problems. Those learned signals are all good enough to decode. They don't need to be good enough to use.

[Flavor]

Okay, I think I got it figured out.

I created the new setup code using a combination of my learned signals and the ones in that other thread you mentioned.

I think it's all good, but I'll have to wait until tonight before I can test it.

Assuming it works, should I post any of my .IR or .RMDU files anywhere?

Thanks again!

[johnsfine]

Assuming it works, you should upload the rmdu file somewhere in the device upgrade area:
http://www.hifi-remote.com/forums/dload ... y&cat_id=4

I think (but I'm not sure) that the convention is to put XBOX upgrades in the DVD area:
http://www.hifi-remote.com/forums/dload ... y&cat_id=5

You probably should cram the names Osmart, XBOX and GBX all into the file title, so people can easily distinguish it from a standard XBOX upgrade and might find it for GBX decodes from a brand other than Osmart.

We don't need to see the working .ir file and once the .rmdu file is uploaded it is best to delete the learned signal file from the diagnosis area.

But if it doesn't work, put both the rmdu file and the .ir file you used to test it into the diagnosis area (preferably combined in one .zip file) and post the URL back here.

[Flavor]

It seems to have worked just fine. I really do appreciate all the help. The arrows repeat just like I hoped that they should. Thanks a lot.

Here's the link to the rmdu file.

http://www.hifi-remote.com/forums/dload ... le_id=2395

Thanks.