
Originally Posted by
NetMedic
PS do you want to continue this by email instead of forum postings?
Leaving it forum based allows it to serve as a reference for others trying to achieve the same purpose.

Originally Posted by
NetMedic
I thought the pronto neo picked up the frequency as well as the codes... am I wrong???
...
Do I have to obtain a more recent pronto, and capture the codes that way??
Is there a util to directly convert neo codes to pronto?
The neo remote does learn the frequency. At present, the only way to convert neo codes to pronto format is via the Marantz RC3200.
It's very likely that the problems you are having lie with the conversion methods and not with the actual learnt codes or the TiVo. When writing my own Neo2Pronto & Pronto2Neo conversions there seemed to be little consistency between what has been written about the conversion and what the Marantz software outputs as far as the Lead In & Lead Out codes are concerned. Given the fact that the Lead In codes are what your decoder is waiting for before it will respond to the inputted command this may very well be the cause of the problem.
What I can tell you is that I have reliably captured 4 remotes (44 buttons) using the Neo -> Marantz -> IR Conversion method so there is hope 

Originally Posted by
NetMedic
So I did a bit of detective work. Unplugged the ir blaster. No, the stb is not seeing the codes from the tivo peanut remote, but it IS seeing codes sent from the ir blaster. Hmm. This could mean that the that the the stb I chose during guided setup has codes with at least approximately the right frequency....
So I'm going to play with the code frequency and see what happens.
Strange...
To test the complete range of frequencies, download the testcodes.tgz again (I've updated it) and install it as above. This time call 'testfreq.tcl' instead of 'testcode.tcl', what this will do is try each frequency from 1 to 100 for the specified button. So for button 1, type:
Code:
./irlock testfreq.tcl ir.codes Dig1
Bookmarks