SysIntegration,
I am happy that you have discovered IrScrutinizer (I am the author), but I am also a bit sad to see how little of its capacities you have discovered. IrScrutinizer replaces, among others, makehex and IrPanels.
You describe a very tedious and error prone procedure consisting of many steps and many tools, which are not very good at communicating with each other. Fortunately, it can be done much easier, using only IrScrutinizer (and some supplementing hardware, or the Pronto).
So here is, leaving out details, how to do it, the IrScrutinizer version.
0. Get some supported capturing hardware, e.g. GlobalCache, IrWidget, IrToy, or Arduino, and make sure it works, and open the device.
1. Select the "Scrutinize remote" pane, "Parametric Remote" subpane. Press capture. Assuming that the hardware works, you can now just "shoot" the buttons of the OEM remote at the sensor. As opposed to other capturing programs, you just fire them one after another (remembering the ordering!) without having to "multiplex" you hands between the remote, the mouse, and the keyboard. If desired, fill in the names of the commands just captured.
If you have some working sending hardware, you can try the signals just captured by selecting the signal, pressing the right mouse button, and selecting "Transmit selected".
8. If you like to search for functionality on the other possible signals, that where not on thte keys on your OEM remote, this is how to do it: Select one signal having the "interesting" D and S parameter. Press the right mouse button, in the popup menu select Advanced -> Add missing F's. This will generate all the "missing" signals. Assuming the access of suitable hardware, these can be tried one after another by pressing the right mouse button and selecting "Transmit selected". The column "Comment", "Name" and "Ver." can be used to electronically take notes of the outcome.
9. Add comments, fix up than names etc in the table. Then the table can be exported to a number of different formats. If intending to post to RC, the export format "text" is probably suitable, ticking the CCF and the Parameters checkboxes in the "Export" pane.
If no suitable capturing hardware is available, but a Pronto (Classic) instead, the signals of the OEM remote (or a subset of them) can be captured by the Pronto, and saved to a CCF file. This CCF file can be imported directly by IrScrutinizer (Import -> Pronto Classic) into the "Scrutinize remote" table.
If no suitable sending hardware, but a Pronto (Classic) is available, the table (for example augmented by the "missing" signals) can be exported to another CCF file (Pane Export), and the testing of the missing signals carried out by using the Pronto.
If you want to generate a table, like in the steps 4 and 5, IrScrutinizer does with with the "Generate" pane, in conjunction with the Export.
Note that I just (day before yesterday) released a new version, 1.1.0, see
[Link: harctoolbox.org] .
Now, if you are lucky, the manufacturer has provided an .pdf or excel file for you listing all
of their codes like Integra does. If you are REALLY lucky, the manufacturer has made a
file for you that you can directly import into IR Library Manager. Yamaha does this. IF you
are somewhere in between, the manufacture may provide a PDF document with a list of
object numbers, device, and protocol set that you have to generate the codes yourself.
If you are ridiculously lucky, someone has done all the hard work for you, and you copy
and paste the codes from this site or JP1 or avsforums.
Note that IrScrutinizer has advanced features for importing Ir signals, also from rather unstructured texts, like an RC posting. Often, you can just copy a whole thread to the clipboard, select Import -> Text -> Raw, line based (e.g.) and press "Load from Clipboard"
Happy hunting. Go make a friend with someone who has a pronto.
Or go make friends with a pronto.
Or make friends with IrScrutinizer :-)
Bug reports and suggestions for improvements are welcome.
