I know absolutely nothing about these boxes so don't pay that close of attention, but it seems to me that you are still using a byName type of search to get an official setup when you should be looking for some kind of CUSTOM option._________________Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

As far as I remember, you put the BIN file in the "C:\Program Files\Monsoon Multimedia\Vulkano\Setup Wizard" or to "C:\Program Files (x86)\Monsoon Multimedia\Vulkano\Setup Wizard" folder. Only then will it appear in the drop down menu. By the sound of it waht you seeing in the dropdown menu matches the BIN files in that folder. It looks as though you have put it somewhere else ?

Yes, the wizard has the select by code drop down, but C2010 doesn't appear in the list. The list goes from C0000 to C0525, then skips to C3509. I've gotten these results on a Vulkano Flow and a Lava.

To skip from 0 to 525 then to 3509 are long jumps, it makes it sound like there aren't too many codes of any sort in your box, which doesn't seem likely. Is it possible that you selected something before you got to the code selection part that is limiting the selection, like selecting a brand or model?

Like Vicky said, you should not be trying to select a brand or model of any sort, you should be selecting something like "Other" or "Custom". The operating system should give you an option for cases where you can't find your brand and want to select codes directly, and in that mode, you should be able to select any code, so there should be hundreds of them, not just 3 codes._________________Rob
www.hifi-remote.comPlease don't PM me with remote questions, post them in the forums so all the experts can help!

The goal is to replace a known BIN file with Alan's so the Setup Wizard sees it and uses it. The Setup Wizard folder has a set of XML files that list what devices it knows about.

Find a file that matches what you see in your list, for example C2004_Axum.bin is in the directory and is actually the only one with 2004 in its name. Rename the original and then rename Alan's BIN file from C2010_Axum.bin to C2004_Axum.bin.

Restart Setup Wizard so it picks up the new version of C2004_Axum.bin.

We can work with LRN files but in this case we already know the IR protocol the device, SFR STBP-SGM-R2, uses.

I've confirmed all the .bin files are in the correct directory. C:Program Files (X86)\Monsoon Multimedia\Vulkano\Setup Wizard\

There are 476 .bin files, of which 48 are PL, 158 Axum, 266 Gondar, 3 PK and 1 RV.

There are 4 drop downs available: Device Category, (ALL, Cable, Satellite/DSS,Digital Video Disk,VCR, and Learned) Manufacturer, Model, and Code. I'm selecting Device Category/ALL, Manufacturer/ALL, selecting 'Code' then selecting the code drop down of which 785 are listed, which is a bit confusing considering the number of .bin files in the directory.

Regarding the list which goes from C0000 to C0525, then skips to C3509, that's not the total number of codes (3), I was making reference to C2010 which should have been in between those, but isn't. Sorry if I wasn't clear.

C2004_Axum.bin is in the Vulkano setup directory, but C2004 is n-o-t in the drop down list of the Vulkano setup application. The list of STB codes which begin with a 'C' in the drop down list goes from C0000 to C0525, skipping numbers in between, then C3509 all the way up to C3739. In other words, the C range is: C0000>C3739..not consecutively numbered.

So mrphil1, if you can confirm you see the same as I do in the IR Blaster info and the Gondar_IR.xml file, we should probably choose S0447_Gondar.bin as the output filename. Remote type should also be Vulkano with Gondar Chip - 47 keys in order to get the _Gondar output.

Thanks for confirming. I'll try to do some more testing with using a non-existing BIN file and seeing if it reads it and uses it in place of the built-in code. And also replacing an existing BIN file and see if that works.

These steps should also allow us to confirm which BIN file format we should be using.