 |
JP1 Remotes
|
| View previous topic :: View next topic |
| Author |
Message |
vickyg2003
Site Admin
Joined: 20 Mar 2004
Posts: 7073
Location: Florida
|
 Posted: Wed Sep 01, 2010 7:32 am Post subject: |
 |
|
| 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.
| Quote: |
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.
| Code: | Upgrade protocol 0 = 01 FF (S3C80) Manual Settings (RM v1.98)
44 8C 11 8B 12 E5 4C 08 08 01 21 01 06 01 21 03
31 D4 FD 11 A7 08 B7 8D 01 46
End |
|
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.
| Quote: |
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.
_________________
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.
Last edited by vickyg2003 on Wed Sep 01, 2010 7:41 am; edited 1 time in total |
|
| Back to top |
|
 |
alanrichey
Expert
Joined: 24 Mar 2008
Posts: 3529
Location: UK/USA
|
| Posted: Wed Sep 01, 2010 7:38 am Post subject: |
|
|
Beyond my capability I'm afraid - too technical  |
|
| Back to top |
|
|
The Robman
Site Owner
Joined: 01 Aug 2003
Posts: 21234
Location: Chicago, IL
|
| Posted: Wed Sep 01, 2010 9:25 am Post subject: |
|
|
| alanrichey wrote: | | Beyond my capability I'm afraid - too technical |
Try adding this to protocols.ini and then use the following file:
[NEC1 (No Repeats)]
PID=01 FF
DeviceTranslator=Translator(lsb,comp)
CmdTranslator=Translator(lsb,comp)
CmdParms=OBC=0
DevParms=Device Number
FixedData=ff
Notes=This protocol produces NEC1 signals, that only use 1 device code, with no repeats.
Code.S3C80=44 8C 11 8B 12 E5 4C 08 08 01 21 01 06 01 21 03 31 D4 FD 11 A7 08 B7 8D 01 46
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=8844
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
| Back to top |
|
|
alanrichey
Expert
Joined: 24 Mar 2008
Posts: 3529
Location: UK/USA
|
| Posted: Wed Sep 01, 2010 11:33 am Post subject: |
|
|
| 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 |
|
| Back to top |
|
|
The Robman
Site Owner
Joined: 01 Aug 2003
Posts: 21234
Location: Chicago, IL
|
| Posted: Wed Sep 01, 2010 12:10 pm Post subject: |
|
|
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! |
|
| Back to top |
|
|
eferz
Expert
Joined: 03 Jun 2010
Posts: 1078
Location: Austin, Texas
|
| Posted: Wed Sep 01, 2010 2:47 pm Post subject: |
|
|
| Thanks, everyone for your input! This works for me. |
|
| Back to top |
|
|
alanrichey
Expert
Joined: 24 Mar 2008
Posts: 3529
Location: UK/USA
|
| Posted: Fri Sep 03, 2010 6:47 am Post subject: |
|
|
| 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 ? |
|
| Back to top |
|
|
The Robman
Site Owner
Joined: 01 Aug 2003
Posts: 21234
Location: Chicago, IL
|
| Posted: Fri Sep 03, 2010 7:30 am Post subject: |
|
|
| 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! |
|
| Back to top |
|
|
alanrichey
Expert
Joined: 24 Mar 2008
Posts: 3529
Location: UK/USA
|
| Posted: Fri Sep 03, 2010 7:43 am Post subject: |
|
|
| Yes please |
|
| Back to top |
|
|
The Robman
Site Owner
Joined: 01 Aug 2003
Posts: 21234
Location: Chicago, IL
|
| Posted: Fri Sep 03, 2010 9:26 am Post subject: |
|
|
Try this...
[NEC1 (No Repeats)]
PID=01 FF
DeviceTranslator=Translator(lsb,comp,0,8,0) Translator(lsb,comp,1,8,8)
CmdTranslator=Translator(lsb,comp)
CmdParms=OBC=0
DevParms=Device Number,Sub Device=[-0]
FixedData=ff 00
Notes=This protocol produces NEC1 signals, with no repeats.
Code.S3C80=44 8C 21 8B 12 CF 4C 08 08 01 21 01 06 01 21 03 31 D4 FD 11 A7 08 B7 20 11 E4 05 06 60 06 8D 01 46
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
| Back to top |
|
|
alanrichey
Expert
Joined: 24 Mar 2008
Posts: 3529
Location: UK/USA
|
| Posted: Fri Sep 03, 2010 10:01 am Post subject: |
|
|
Looks great, thanks. Haven't got anyone to test it with yet but will let you know when it gets proven.
Many thanks
Al |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
File Section
Wiki
