I came here just now to ask if someone could PLEASE do exactly what SysIntegration did. I have gone through discovering that process three or four times over the last ten years but I was so beat by the end that I realized I had just completed the job without taking notes. I said screw it and moved on. THANK YOU SO MUCH.
On June 22, 2014 at 16:56, Barf said...
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.
Agreed.
Fortunately, it can be done much easier, using only IrScrutinizer (and some supplementing hardware, or the Pronto).
Great! I also carry a Pronto TS1000 all the time in case I have to learn commands. I agree that it is the best learner I've seen except for the Crestron.
So here is, leaving out details, how to do it, the IrScrutinizer version.
...and without the details I won't be able to use it.
Regarding Steps 0 through 9, the details you leave out are the details that make it possible to do. I have a Pronto and a laptop. You know the models of various brands of things that will work; I have to do the work you already did, researching, trying, eliminating due to possible failure, the various models of various brands.... sorry, but in a nutshell, screw that.
If no suitable capturing hardware is available, but a Pronto (Classic) instead,
What is it about a Pronto that makes it not suitable capturing hardware?
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.
Sounds like you just said that the Pronto is suitable sending hardware.
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.
What's the form of the table? I ultimately want Pronto Hex so I can paste it into an RTI file or use URC's Universal Browser to import it into URC. Anything short of Pronto hex... what's that good for?
Note that I just (day before yesterday) released a new version, 1.1.0, see
[Link: harctoolbox.org] .
I will. Thank you very much!
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"
Or make friends with IrScrutinizer :-)
Bug reports and suggestions for improvements are welcome.
One bug is that you're not charging $25 and providing actual step by step instructions with full details. I'd pay that in a heartbeat.
Thanks so much for doing all you've done in this direction. I'll use SysIntegration's method until there's another one as well detailed.
