JP1 Remotes Forum Index JP1 Remotes


FAQFAQ SearchSearch 7 days of topics7 Days MemberlistMemberlist UsergroupsUsergroups RegisterRegister
ProfileProfile Log in to check your private messagesLog in to check your private messages Log inLog in

NEC Yamaha protocols and RMIR

 
Post new topic   Reply to topic    JP1 Remotes Forum Index -> JP1 - Software
View previous topic :: View next topic  
Author Message
mathdon
Expert


Joined: 22 Jul 2008
Posts: 4515
Location: Cambridge, UK

                    
PostPosted: Thu Mar 19, 2020 12:57 pm    Post subject: NEC Yamaha protocols and RMIR Reply with quote

Until now, IrpTransmogrifier has decoded NEC Yamaha protocols as NEC1-f16 or NEC2-f16 without any indication of whether they meet the Yamaha restrictions, and if they have the NECx1 or NECx2 form they have not been recognised at all. In contrast, DecodeIR identifies all NEC Yamaha variants by suffixing NEC1, NEC2, NECx1 or NECx2 with -y1, -y2 or -y3 as appropriate.

I now have posted development build 2 of RMIR v2.10 in the RMIR Development folder on SourceForge. This includes enhancements to the IrpTransmogrifier support in RMIR that enable the Learned Signals tab to identify NEC Yamaha variants in a similar way to DecodeIR. For such signals, NEC1, NEC2, NECx1 or NECx2 are suffixed with -Yamaha and the Misc column displays YStyle=Y1, Y2 or Y3 as appropriate. This follows the notation used by the NEC 4DEV Yamaha Combo executor, and the Convert to Device Upgrade button on the Learned Signals tab can convert any selection of Yamaha or standard NEC signals to an upgrade with this executor.

NEC1 or NEC2 signals where the two function bytes do not meet either the NEC or Yamaha criteria still display as NEC1-f16 or NEC2-f16, with the second function byte showing as OBC2 in the Misc column. The enhancements make use of the linkage between the IrpProtocols.xml file of IrpTransmogrifier and the protocols.ini file of RMIR. As I am not aware of any executors in protocols.ini that can generate NECx1-f16 or NECx2-f16 signals that do not meet the Yamaha criteria, RMIR cannot rename the second function byte of these from E to OBC2 so they show this byte as E in the Misc column.

There are two .rmir files that can be used to demonstrate these new features. One is this file from rsbrux that started the whole investigation of NEC-f16 support in RMIR in this thread last November. The other is this file created by me as a demo file, with a greater selection of Yamaha signals as well as some other demo learns.

The Yamaha enhancements are the largest addition to IrpTransmogrifier support but this build also adds the ability to convert NEC signals to upgrades with other executors that were not previously supported.

I would welcome comments on these enhancements, and the Yamaha support in particular. The version of IrpTransmogrifier included in this development build of RMIR is also a development build by Barf so new official versions of both programs hang on your views.
_________________
Graham
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic       JP1 Remotes Forum Index -> JP1 - Software All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
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
Top 7 Advantages of Playing Online Slots The Evolution of Remote Control