Here are some of the codes provided by xtend technolgies in cleveland, ohio who said they "captured" these codes.. they are an RTI authorized dealer.. RTI also did the firmware for sonance and also made their capture device while it was on the market.. the "1" prior to the hex string was for number of repeats
I am going to try your recommendation using sony20 with device code 26.19. I will retest my IR eye to make sure it is functioning, but I did this last year and it was... Other pertinents.. the remote clearly functions and changes tuner settings... the eye is properly positioned on the left side of the unit when looking at it near the power button.. I am going to try and decipher the above codes to see what device code shakes out after converting to binary.. given the number of data strings, makehex sony20 would produce this number (46 groups of 4).
as I stated in my intitial email, I can contol a cd player denon and direct tv satellite with the 4630 from all keypads no problem.... the sony has been a pain in my u know what!! I was surprised that they were not very helpful when called... same for sonance...
the info provided by ted timmons using lirc suggest 12 bits, standard header of 2400/600, one = 1200/600 and zero = 600/600 with 8 post data bits and post data hex of 0xC8, min repeat of 2, gap of 45000.. I tried building a modified makehex code last night starting with sony 15, device 200, command 61 and was unsuccessful.. tried it with "preset +" of 0xBCB....
The control manager software for the sonance does show drawing of the ir signal if a hex code is inputted with some data... for sony15, device 200, code 61, It stated SIRC15, raw: 0x643D, cmd 0111101 (0x3D) addr:11001000 (0xC8)
the same code (makehex sony 15 code in my initial email0 also had correct time intervals of 1.2 ms and 602 micros with the 0018 and 0030 data strings... header was also correct at 2.41 ms with data string of 0060.... the end of the code-presumed post data- matched lirc data by timmons as 0xC8 with bin of 110010000... I could not get the front end of the code to correspond to 0xCBC provided by lirc info... I was not sure how to work in the gap of 45000 into the code... the very end of the code also had a 19.8 ms flat line trailer.. not sure the significance of this....