Moderator: Moderators
Great idea, I think, but it's a bigger job than you think. You'd also have to edit all the readme files, since they all mention that the RDF is included.Nils_Ekberg wrote:I have been wanting to go and delete all the RDF's from the extender files but I just never get around to it. My thought was that the most current would always be in the current RDF distribution and eliminate the use of old ones in the extender zip files.
Mike, million thanks. Yes, General tab was exactly what I was asking about. So dev7 and dev8 can actually be used and not devoted to special protocols - that's cool.mr_d_p_gumby wrote:The two extenders are functionally identical. If you were to copy & paste all of the special protocols into the 1K extender, then both would behave in an identical manner. You do not have to assign any of the setup codes for the special protocols on the General tab, if that's what you mean. Once you've added the device & protocol upgrades for the special protocols, then you can start progamming them on the Spcl Prot Fns tab.ElizabethD wrote:Can you confirm that in 1K extender I have to assign setup code to the device on the General tab (and of course bring in the special protocols whatever fits), but I do not have to assign setup code in the 2K extender?
I got an answer before I asked that one. Thanks again. I would have messed up by pasting all three bytes or would have been doing it the old way with key numbers.mr_d_p_gumby wrote:There is one exception to this for both the 1K & 2K 6131 exteneders (and also the Atlas DVR extender). In these extenders, The DSM functionality is built into the extenders, and does not use a device and/or protocol upgrade. IR will not activate the DSM functions if it does not see the device upgrade. I've added the following note to the 6131 1K extender files that I just updated to explain a workaround: ...
This worked great (in 2K so far) inspite of IR making some objections, thanks Mikemr_d_p_gumby wrote:Upgrade Code 0 = 1C 4F (TV/1103)
FC
End
(You will temporarily need 7 bytes of upgrade space for this.)[/code]
It works because IR only needs to see the FC (protocol ID 01FC) to turn on the DSM functions. Since this is only a "dummy" protocol that is never seen by the remote, you can get away with leaving off the other two bytes to save space.ElizabethD wrote:Re: DSMThis worked great (in 2K so far) inspite of IR making some objections, thanks Mikemr_d_p_gumby wrote:Upgrade Code 0 = 1C 4F (TV/1103)
FC
End
(You will temporarily need 7 bytes of upgrade space for this.)[/code]
How come it's only FC and not the usual 3 bytes? It actually works either way I noticed.