Forum for JP1 remotes
http://www.hifi-remote.com/forums/
Keep in mind that Alan is creating BIN files for people, so he's the only one that would need to update his RDF (and I hope he would remember to change it back afterward).vickyg2003 wrote:I was away on vacation when that method was explained to you. I read it on a public computer and wanted to respond, but forgot about it by the time I got back. That's kind of a poor method, IMHO, because it requires you to change your rdf to get the protocol. So anyone that wanted to use the RDMU would need to make this change. Too complex!
It's not quite like a remote. With a remote you can have several upgrades in use at once, which is not the case with a Slingbox (at least, the original ones), which can only control one device at a time.vickyg2003 wrote:IF A SLINGBOX WORKS LIKE A REMOTE, that protocol upgrade would override the NEC protocol for all equipment.
Well the person that is so organized that he's constantly erasing his untested stuff, is probably organized enough to keep track of that, but I still think its difficult for other people to pitch in with something so complicated.The Robman wrote:Keep in mind that Alan is creating BIN files for people, so he's the only one that would need to update his RDF (and I hope he would remember to change it back afterward).vickyg2003 wrote:I was away on vacation when that method was explained to you. I read it on a public computer and wanted to respond, but forgot about it by the time I got back. That's kind of a poor method, IMHO, because it requires you to change your rdf to get the protocol. So anyone that wanted to use the RDMU would need to make this change. Too complex!
Does that mean that some of the protocols can't be added as manual protocols in rm? I've only had a small amount of exerience with RM. I tweaked a few protocols, added then to RM as 01FF and then looked at what the original PRotocols.ini looked like and then made the items match what protocols.ini said.The Robman wrote:I agree, it's not ideal, but in some cases it's the only way to force RM to do what's needed. Remember, they don't copy stuff over to IR to create the bin files, they come directly from RM.
Here's the post: http://answers.slingbox.com/message/17137#17137alanrichey wrote:OK, we'll see what it does in this case. I can't find the thread now but i am sure eferz used NEC2 instead of NEC1. No doubt he will read this and confirm/deny that
and the response: http://answers.slingbox.com/message/17199#17199eferz wrote:I noticed in Remote Master's protocol notes for NEC1 indicates, "There are primarily 2 versions of the NEC protocol: NEC1 and NEC2. The difference between the two is in how the codes repeat when a button is held down. Even if you use the wrong version, it will probably still work, except that the codes won't repeat (or vice versa)."
So, I recompiled Alan's remote update bin files to NEC2 and attached them to this post. Give that a try, if it doesn't work I'll hit up the folks at JP1 to see if they can help me tweak the protocol to remove the repeats. Also, make sure you delete the previous files that you copied into the SBAV folder as I notice windows is a little quirky about replacing files in "protected" areas.
I can't explain why it worked, as the vicky's and rob's logic makes sense. All I know is that I tried it, the user tested it, and is happy with it. However, we won't know if it will also works Rodge until he provides us with some feedback.pamf wrote:Hello!
Mate i did work, i´ve got no words to thank you guys.......
Amazing......if one day you guys decide to come over to brazil.....the first beer is mine...
Couldn't we save the file as a separate RDF? That way we can refer to that one when we don't want to use repeats?The Robman wrote:Keep in mind that Alan is creating BIN files for people, so he's the only one that would need to update his RDF (and I hope he would remember to change it back afterward).
Actually, the SlingRemote of the Slingbox works like a non-learning universal remote. You have to feed it a setup code then the buttons work as pre-programmed. Each video source (Component, S-Video, ANT, and Composite) can associate itself to a single setup code. However, if you upgrade the setup code with a remote update bin then it also changes for all the video sources that uses the same code.The Robman wrote:It's not quite like a remote. With a remote you can have several upgrades in use at once, which is not the case with a Slingbox (at least, the original ones), which can only control one device at a time.
(I don't know if the multi-device Slingboxes are out yet, but if and when they come, they probably would have act more like a remote).
Out of intellectual curiosity, could you test both files? And please, do make sure to delete the previous files before copying them over. I've seen Windows act peculiar about writing over files in protected areas while UAC is enabled.Rodge wrote:Sorry folks, I had thought I set my forum settings to email me whenever a post reply comes in and I've just been busy lately and hadn't had chance to check back in. Thanks Rob for reminding me about this.
In any case, I'm not at home right now, so I wont be able to try anything until later tonight. I'll let reply back with results of the C2011 code as soon as I can.
Thanks again,
Rodge