|
JP1 Remotes
|
View previous topic :: View next topic |
Author |
Message |
xnappo Expert
Joined: 30 Dec 2003 Posts: 861
|
Posted: Fri Dec 07, 2012 8:57 am Post subject: |
|
|
The Robman wrote: |
Anyway, a parm value of 0x01 will indeed yield an NEC2 signal. So, if you actually selected NEC1 and then entered 1 as the parm, you would actually get NEC2. |
Okay... But that still doesn't explain where the problem lies in the learn->upgrade process.
If I make a new NEC2 upgrade from scratch, Param is blank, and if I saw learns with NEC2 as the protocol I would LEAVE it blank like Rob suggests since the Protocol notes say:
Quote: | Although NEC1 and NEC2 are by far the most popular versions of NEC, there are some other variations, which you may find listed with names like NEC-30, NEC-04, etc. If you need to use one of these protocols, select "NEC1" or "NEC2" and enter the number after the dash as the parm. For example, if you need "NEC-30", the parm value is "30".
|
Does this mean Protocol.ini is in fact wrong?
With it is left blank, the fixed data is 0x21(which works). If you enter Param=1 it changes to 0x01(which doesn't work).
It looks like RM is taking the Param field whole-sale as the first byte of fixed data when in fact it should be ORed with something?
xnappo |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21237 Location: Chicago, IL |
Posted: Fri Dec 07, 2012 12:52 pm Post subject: |
|
|
01 = NEC2 with a single device code (ie, device2 is the comp of device1)
21 = NEC2 with two different device codes
Another good example of why it should be left blank so RM can do the right thing with it. You should only set the parm value if you are looking at the whole set of learns and have determined that you are dealing with one of the special cases not covered by the standard NEC1, NEC2, NECx1, NECx2 versions.
For example, if all the learns are NEC1 except for the volume, channel, ffwd and rew buttons, you might use 08 or 28 as the parm (ie, B3 is set).
If you see the signal repeated twice but then see an NEC1 repeating trail, set B1. _________________ 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 |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21237 Location: Chicago, IL |
|
Back to top |
|
|
Vyrolan
Joined: 24 Aug 2012 Posts: 168 Location: Chicago, IL |
Posted: Fri Dec 07, 2012 2:59 pm Post subject: |
|
|
It seems that I should just never set a parameter value to a default...just leave them blank and let RMIR handle any defaulting. I can make that change. |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21237 Location: Chicago, IL |
Posted: Fri Dec 07, 2012 3:02 pm Post subject: |
|
|
Vyrolan wrote: | It seems that I should just never set a parameter value to a default...just leave them blank and let RMIR handle any defaulting. I can make that change. |
You should probably make that judgement on a case by case basis, but certainly in the case of the NEC parm, you should always leave it blank. That one is primarily there to allow an expert to create a custom NEC signal if needed but 99% of the time, it's not needed as RM will generate the correct value. _________________ 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 |
|
|
Vyrolan
Joined: 24 Aug 2012 Posts: 168 Location: Chicago, IL |
Posted: Fri Dec 07, 2012 3:45 pm Post subject: |
|
|
The Robman wrote: | Vyrolan wrote: | It seems that I should just never set a parameter value to a default...just leave them blank and let RMIR handle any defaulting. I can make that change. |
You should probably make that judgement on a case by case basis, but certainly in the case of the NEC parm, you should always leave it blank. That one is primarily there to allow an expert to create a custom NEC signal if needed but 99% of the time, it's not needed as RM will generate the correct value. |
Yea, if DecodeIR shows the values, I try to use them...but if it doesn't, I had just been setting to the defaults (that the RMIR code parses out of protocols.ini). It seems better though to just not use the defaults and leave them blank and let RMIR handle it. I do think there's room for error in that feature...perfect conversion from learns to an upgrade is probably not going to happen, but it can do most of the work and leave the user with only a few tweaks on a parameter or whatever to finish it up. /shrug |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21237 Location: Chicago, IL |
Posted: Fri Dec 07, 2012 4:33 pm Post subject: |
|
|
Another possibility would be to create a separate "NEC Generic" protocol entry in protocols.ini and then delete the Parm entry completely from the regular NEC1,2,x1,x2 entries. _________________ 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 |
|
|
Vyrolan
Joined: 24 Aug 2012 Posts: 168 Location: Chicago, IL |
Posted: Fri Dec 07, 2012 4:48 pm Post subject: |
|
|
The Robman wrote: | Another possibility would be to create a separate "NEC Generic" protocol entry in protocols.ini and then delete the Parm entry completely from the regular NEC1,2,x1,x2 entries. |
That would fix NEC... Is the "use the value in protocols.ini as default instead of leaving it blank" going to mess up anywhere else though? |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21237 Location: Chicago, IL |
Posted: Fri Dec 07, 2012 5:09 pm Post subject: |
|
|
Someone would have to go through protocols.ini and review each protocol one by one. _________________ 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 |
|
|
|
|
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
|