I was under the impression that the 7800 & 6800 were alike except for the fact that the 6800 has one less physical device button.
When I tried loading a 7800 extender (my first attempt at extenders) I got a warning message about an incorrect signature.
Do I ignore this
I have my 6800's setup as far as I can go with macros & keymoves I am wanting to move on to extenders.
I have read lots of the guides and I am still waiting for it all to click, so when I get warning messages I get worried I am doing things wrong.
I also read in another post that the 7800 extenders were more limited than newer remotes. In what way? I am looking to do TOADtoggle, pause, skp/lkp and maybe dsm.
Yes, ignore the message about signature error.
Yes, 7800ext2 is an early one, and there's no nested macros or ToadTog (yet, there's some hope that'll change) but it's great to use even with those missing.
I do not know how 6800 will behave. It might work.
Pause you can always add from KM or RM.
L/DKP can be added as well. I converted it from 8910, and as it stands now it's klugdy because you have to work on the keymoves sheet, not special protocols, because it's built differently than all the others due to some 3-byte restriction I was apparently working under. DSM is included, works great. Or you can use one of the standalone DSMs from the 7800ext file section.
Liz Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
A 6800 is just like a 7800 but with one button missing. The internal electronics and firmware are identical. The extender and all other JP1 support works the same in 6800 and 7800. The only consequence of the missing button is that you can't physically press that button. With JP1 you can include the missing button in a macro.
ElizabethD wrote:Yes, ignore the message about signature error.
Yes, 7800ext2 is an early one, and there's no nested macros or ToadTog (yet, there's some hope that'll change) but it's great to use even with those missing.
I do not know how 6800 will behave. It might work.
Pause you can always add from KM or RM.
L/DKP can be added as well. I converted it from 8910, and as it stands now it's klugdy because you have to work on the keymoves sheet, not special protocols, because it's built differently than all the others due to some 3-byte restriction I was apparently working under. DSM is included, works great. Or you can use one of the standalone DSMs from the 7800ext file section.
Thanks very much for your help. I'll start with the pause bit first. You lost me however after the L/DKP bit.
I just noticed there are three RDFs for the cinema6(6800) and the most comprehensive one has the following:
I believe that the [SpecialProtocols] section in RDF means these are the things IR can recognize and therefore those entries can be visible in the Special Protocol type dropdown, so long as you add the protocols and devices such as you do for Pause. None of those protocols and devices are built into this extender.
The DSM that IR will recognize is one of the standalone ones (use whichever one works). That can be used from the Special Protocols tab. And even if you don't use this DSM, it's handy for gathering button numbers if you don't want to use the button numbers listed in the RDF.
L/DKP and DSM included within are excluded because it is non-standard. So instead of coding on the Special Protocol keymoves tab, it has to be coded on the Keymoves tab using button numbers instead of button names.
Read the tail end of the readme file in the L/DKP+DSM package for details.
Liz Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
ElizabethD wrote:I believe that the [SpecialProtocols] section in RDF means these are the things IR can recognize and therefore those entries can be visible in the Special Protocol type dropdown, so long as you add the protocols and devices such as you do for Pause. None of those protocols and devices are built into this extender.
The DSM that IR will recognize is one of the standalone ones (use whichever one works). That can be used from the Special Protocols tab. And even if you don't use this DSM, it's handy for gathering button numbers if you don't want to use the button numbers listed in the RDF.
L/DKP and DSM included within are excluded because it is non-standard. So instead of coding on the Special Protocol keymoves tab, it has to be coded on the Keymoves tab using button numbers instead of button names.
Read the tail end of the readme file in the L/DKP+DSM package for details.
Thanks again
It's time to study a little harder. I had read the document in question but that was before I found what it was all about and before I read the extender doc.
