Need help adding new codes to your Slingbox, this is the place to ask. You're welcome to ask general Slingbox questions here, but be aware that most of us are not Slingbox experts.
eferz wrote:
My only excuse is letting the simplicity of disabling repeats get head of me from the process which was taught in the Repeat function in Protocols thread. The tools which make it possible lead me to believe it would be an simple request for RM to be able to turn off the "RptHeld" bit if its represented within FF06 address. After all, subtracting a single bit from two bytes doesn't seem difficult.
However, that's where my own ignorance got the best of me. Probably why I got the functionality of the protocol.ini and RDFs a bit mixed up in my head. I should have reviewed the NEC protocols before opening my big mouth. Then I would have realized that the Protocol Upgrade Code doesn't even show up in RM for any NEC protocol.
Acutally they do. There just invisible. If you highlight and copy the field to notepad you'll see the hex.
My one question earlier in this thread remains unanswered though. Since Rob created the Protocol Upgrade Code, is there a way to save it into my own protocol.ini file or do I have to always use that RMDU template to avoid NEC1 repeats.
Yes there is probably a way, although you wouldn't want to use 01ff for the protocol upgrade since that's our catch-all number for custom protocols.
On another note, I've been trying to field your questions about Slingbox to help you understand it better. I'm not sure if I've been helpful in clarifying, unhelpful in confusing, or if I'm just outright annoying you. Alan has warned me in multiple occasions that my explanations are way too complicated. So, I'm starting to fear because you haven't respond to any of those posts that its either the middle or latter option. I apologize if that's the case.
I read every word it just takes me a while to digest it. I'm not as attuned to all of this as most of the forum regulars. I'm low-tech. Your explanations have not been too complicated, as I'm looking for technical understanding. However sometimes it takes me quite a while to pick up the basics. I took me years to understand what a protocol and signal looked like.
Last edited by vickyg2003 on Wed Sep 01, 2010 6:41 am, edited 1 time in total.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Thanks, looks perfect. Now I just have to remember not to overwrite PROTOCOLS.INI each time I update RM. Although as I now appear to be stuck with V1.99 preview 2 forever I guess that won't be a problem
You should create a separate file where you can list all the non-standard protocol entries that you've added to protocols.ini, plus the ones where you modified something, so that when a new copy of the file is released, you can just cut&paste the data into it.
Rob www.hifi-remote.com Please don't PM me with remote questions, post them in the forums so all the experts can help!
alanrichey wrote:Sorry, to be a pain, but the new protocol allows only a Device Number, and no Sub-Device number. Is that a factor we can do nothing about ?
That was all that was needed at the time, and it makes for a smaller executor, but I could re-write it to handle sub-device codes too.
Rob www.hifi-remote.com Please don't PM me with remote questions, post them in the forums so all the experts can help!
