Extender needs to press device key twice to select it

adrusa · Post by **adrusa** » Wed Jan 25, 2006 6:38 pm

I installed the 8910 extender and programmed custome mode name, but I noticed that I need to press the device buttons twice to change device mode, did I do anything wrong?
Thank you all.

Capn Trips · Post by **Capn Trips** » Thu Jan 26, 2006 12:51 am

Probably.

Capn Trips · Post by **Capn Trips** » Thu Jan 26, 2006 12:53 am

But seriously, how can anybody try to divine what you might possibly have done wrong with so little information?

See the link below ("Something not working?") and try to comply.

i.e. upload the guilty IR file to the diagnosis area and post a link to it and someone will have a look.

adrusa · Post by **adrusa** » Thu Jan 26, 2006 1:58 am

Thank you, I have uploaded the offending ir. file to the diagnosis area. it is named 222233CM22.ir. dload.php?action=file&file_id=2733

While at it can somebody help me use the toadtoggle to programme discrete power codes for my devices, all of them.

Thanks

Capn Trips · Post by **Capn Trips** » Thu Jan 26, 2006 3:58 am

What extender are you using? Your file description says extender 3, and when I open your file, IR has all sorts of problems figuring out what rdf to use, and then there are no notes, nor any Special Function Keymoves. To my knowledge, the 8910 has only a single extender fully integrated into the JP1 toolkit.

One JP1-er recently created some custom modified extenders for the 8910, but they are not supported with any readme's and were incorrectly designed to use the same rdf ID as extender 1, so IR gets very confused, when your file says rdf ID CPT0CPx1 but it's not the NORMAL CPT0CPx1, but a modified version of it.

If you're using one of these custom rdf's (from the file linked below), you have to also provide the rdf file, and I highly recommend you NOT reuse existing rdf names. If you're calling it "extender 3" then a logical rdf ID would be CPT0CPx3, for example.

For the appropriate extender expert/administrator:
THIS FILE, created by teamvc last month, continues to languish in the 8910 extender section. It's OK, I suppose, to let folks have access to them, but it really needs a disclaimer of some sort, as there is no real support for these and new users stumbling across them can get in trouble pretty quickly. Or perhaps most simply - it should be moved to the rdf section and taken out of the extenders section. Or perhaps they should be properly renamed and added to the rdf list and appropriate mods made to IR to use them.

Capn Trips · Post by **Capn Trips** » Thu Jan 26, 2006 4:28 am

Having scolded you above, I've bludgeoned through your file, and I'm not sure I used the right rdf, but at least I got a look at your macros and keymoves. Your problem is you've defined MACROS to your device buttons (to presumably select the device). Then you have additionally defined KEYMOVES to the SAME BUTTONS to execute your tailored Custom Mode Name (CMN) commands.

Now try to stay with me 8) :

KEYMOVES take priority OVER MACROS - i.e. if you have a KEYMOVE and MACRO assigned to the same button, your remote will preferentially execute the KEYMOVE. However:

MACROS are global - i.e. they execute the assigned sequence of functions regardless what "device mode" your device is in (This terminology is not quite precise, as with the extender you don't really have a current device mode, but you have keysets assigned to particular devices. In your case, using the default device selection macros, that is effectively what you have)

KEYMOVES (such as your CMN assignments) are DEVICE-SPECIFIC, so, for example, your "TV" CMN, although assigned to the "TV" button, will only execute AFTER YOU ARE IN TV MODE.

Hence, if you are in other than TV mode to start, the FIRST PRESS of the "TV" buton will not see the CMN keymove and will execute the MACRO. The MACRO put your remote into TV mode, so the SECOND press of "TV" will now execute the KEYMOVE, i.e. the CMN.

This is precisely the behaviour you are seeing, so the good news is - IT WORKS LIKE DESIGNED!

What you want to do for this specific situation, is assign the CMN keymoves to ANOTHER button, (I'd use something like the x-shifted device buttons), and INCLUDE THAT BUTTON in your device selection macros instead of the "SET_LCD" command.

Having written all of that, I still HIGHLY recommend - while your current IR file is still relatively simple and easy to recreate (i.e. before it gets too complex) - rebuild your IR file using the original extender (1) that's properly supported. You will then get a usable Special Functions Tab in IR and you certainly have enough upgrade memory without the shifted memory allocation boundary that this tailored rdf has.

Then we can talk about ToadTog. 8)

underquark · Post by **underquark** » Thu Jan 26, 2006 10:24 am

I'm no expert but I'm creating an IR file for the 8910 extender using some of the things you are tring to do. Latest version is here. It uses Custom Mode Names etc. on the shift-device key with the device macro on the device key itself (kind of like how it tells you to do it in the ReadMe file, actually). It also has a few LKPs thrown in for good measure and I've started to enter notes as I'm easily confused.

adrusa · Post by **adrusa** » Thu Jan 26, 2006 12:22 pm

Thanks to you both, the problem is I dont seem to be able to import my current programming to extender 1. I had thought I will do that myself. But anytime I tried the keymoves and macros disappeared and I dont seem to be able to recreate them. I'm currently examine the file created by underq.

Capn Trips · Post by **Capn Trips** » Thu Jan 26, 2006 12:38 pm

How are you trying to do this?

It's really pretty simple using the "File/Merge using Extinstall" function in IR. Of course you must have Extinstall.exe, and the hex file for the extender, both in the IR directory, and then select the correct rdf. Have you done this?

If it's still a problem, upload and link your unextended and extended IR files and someone will take a look.

Post by **ElizabethD** » Thu Jan 26, 2006 1:00 pm

Disclaimer - I haven't see the file in trouble.

Process is to first open your IR file already correctly running under IR . Also make sure that the RDF, IR, Extinstall use the same drive letter, HEX file does'nt have to. IR needs correct RDF. Then and only then bring in the HEX file.
I suspect the macros are getting lost due to still existing nonstandard memory pointers with that ext3.

Edited: Extinstall's Merge wipes out all Notes except those on the General tab. At least that's what happened to me.

Post by **ElizabethD** » Thu Jan 26, 2006 1:03 pm

Capn Trips wrote:For the appropriate extender expert/administrator:
THIS FILE, created by teamvc last month, continues to languish in the 8910 extender section. It's OK, I suppose, to let folks have access to them, but it really needs a disclaimer of some sort, as there is no real support for these and new users stumbling across them can get in trouble pretty quickly. Or perhaps most simply - it should be moved to the rdf section and taken out of the extenders section. Or perhaps they should be properly renamed and added to the rdf list and appropriate mods made to IR to use them.

Great idea. Because we're supposed to take the lastest version and #1 is the latest and bestest official. I would suggest to make a subdirectory under the 8910 extenders, call it 'Unofficial or Under development' and move the non=version1 files there. I'd rather not see it under the rdfs.

adrusa · Post by **adrusa** » Thu Jan 26, 2006 2:47 pm

Thanks to you both, the problem is I dont seem to be able to import my current programming to extender 1. I had thought I will do that myself. But anytime I tried the keymoves and macros disappeared and I dont seem to be able to recreate them. the file posted by underq is not related to the one I uploaded.

Capn Trips · Post by **Capn Trips** » Fri Jan 27, 2006 4:01 am

Capn Trips wrote:If it's still a problem, upload and link your unextended and extended IR files and someone will take a look.

underquark · Post by **underquark** » Fri Jan 27, 2006 7:22 am

adrusa wrote:Thanks to you both, the problem is I dont seem to be able to import my current programming to extender 1. I had thought I will do that myself. But anytime I tried the keymoves and macros disappeared and I dont seem to be able to recreate them. the file posted by underq is not related to the one I uploaded.

If you can't get the porting-over of your old setup to work then I'd suggest treating this as an opportunity to so some spring cleaning and start afresh.

Close (or minimize) all open windows, open IR.EXE twice, right-click on the Windows Taskbar and choose to tile windows vertically. Open your existing IR file in one window and start a new, extender-using IR file in the other Window. Read the extender documentation and make sure that you have actually installed the extender and not just opened its RDF and expected it to work straight away.

Set up the devices and their setup codes in the new IR file. Open each device from the old file in turn and choose "Edit" then copy the string of hex code. Open in the new file (Choose "New") and paste in this code. Repeat the procedure for any protocols that are required. Now check which KeyMoves you need to copy and do this manually. Now check your Macros and see if they need any changes. You should already have read the extender documentation and will have seen that the device keys need set up in a particular way which might influence you choice of KeyMoves and Macros in the new file.

Save the new file as it develops (using a differnet name eaxh time) so that you can always go back a step when you make a mess of something.

Post by **The Robman** » Fri Jan 27, 2006 7:31 am

Capn Trips wrote:For the appropriate extender expert/administrator:
THIS FILE, created by teamvc last month, continues to languish in the 8910 extender section. It's OK, I suppose, to let folks have access to them, but it really needs a disclaimer of some sort, as there is no real support for these and new users stumbling across them can get in trouble pretty quickly. Or perhaps most simply - it should be moved to the rdf section and taken out of the extenders section. Or perhaps they should be properly renamed and added to the rdf list and appropriate mods made to IR to use them.

As far as disclaimers go, everyone has the ability to add comments to the files in the file section. If there are known problems with this file it would probably be a good idea to add a comment that describes them. You can also "rate" a file and the rating is visable right there next to the rest of the file info, so if a file has a poor rating it might make new users more cautious about using it.