TVISTO remote codes

MajorWoody · Post by **MajorWoody** » Thu Oct 19, 2006 12:48 pm

Rob, I am looking at Force learned timings: "Sent Ones When Key is Pressed" +9002 -4536 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -1662.

How do you isolate this sequence: dddddddd DDDDDDDD cccccccc CCCCCCCC.

I am sorry for being to inquisitive.

Post by **The Robman** » Thu Oct 19, 2006 1:35 pm

MajorWoody wrote:Rob, I am looking at Force learned timings: "Sent Ones When Key is Pressed" +9002 -4536 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -1662.

How do you isolate this sequence: dddddddd DDDDDDDD cccccccc CCCCCCCC.

leadin burst pair: +9002 -4536
ZERO pair: +576 -546
ONE pair: +576 -1662
binary: 000000001

johnsfine · Post by **johnsfine** » Thu Oct 19, 2006 1:38 pm

Capn Trips wrote: If you look at the functions that work (once you combine them all in a single upgrade, look at the "Code List" worksheet and select "Sort by OBC" in the upper left-hand Corner), they are all in the range of OBCs 000-031 and 064-078. That pattern suggests that test file number three, which likely had some more of the 079-095 OBCs assigned, might hide some of the functions you still lack.

I finally looked at that second file. I strongly agree with Capn Trips.

It is very common for a device designer to use OBCs entirely from the two ranges 0 to 31 and 64 to 95.

Looking at your list of OBCs and functions, I cannot believe that OBCs 79 through 95 contain zero working functions.

So I have to conclude either that third upgrade was wrong in the .ir file (Unlikely. I didn't double check Rob's files but I don't think he made a mistake) or the .ir file never really loaded into your remote well enough for a correct test.

If you understand even just the basics of editing an upgrade and loading it into your remote, you should be able to build and test an upgrade to retest just OBCs 79 through 95 without all the other stuff present. If you have no learned signals, no keymoves and no other upgrades for this test, that both reduces the chances of confusing yourself about what is really tested and hopefully reduces the chances of whatever upload malfunction you ran into before.

Capn Trips · Post by **Capn Trips** » Thu Oct 19, 2006 2:04 pm

The Robman wrote:
MajorWoody wrote:Rob, I am looking at Force learned timings: "Sent Ones When Key is Pressed" +9002 -4536 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -1662.

How do you isolate this sequence: dddddddd DDDDDDDD cccccccc CCCCCCCC.
leadin burst pair: +9002 -4536
ZERO pair: +576 -546
ONE pair: +576 -1662
binary: 000000001

Feel free to study all of the read-me's in THIS Protocol-Builder zip file for detailed discussions of protocols, or THIS help doc which has a good explanation of how to recognize the basics of a signal (Lead-in, Lead-out, Zero, One, Repeat).

Capn Trips · Post by **Capn Trips** » Thu Oct 19, 2006 3:09 pm

Try this upgrade to see if it consolidates all of the functions that worked properly.

MajorWoody · Post by **MajorWoody** » Fri Oct 20, 2006 7:56 am

John, after looking at Digitrace.zip file, I realized that I will not be ready to use CaptureIR because off more hardware requirement.
With arival of TSOP1738 I can only build detector for GetIR. I need to order other parts from Mouser to build Digitrace hardware.

MajorWoody · Post by **MajorWoody** » Fri Oct 20, 2006 8:02 am

Thank you Capn, I will try your upgrade tonigh.

johnsfine · Post by **johnsfine** » Fri Oct 20, 2006 8:25 am

MajorWoody wrote:John, after looking at Digitrace.zip file, I realized that I will not be ready to use CaptureIR because off more hardware requirement.
With arival of TSOP1738 I can only build detector for GetIR. I need to order other parts from Mouser to build Digitrace hardware.

I'm pretty sure whatever hardware works for GetIR will also work for CaptureIR. CaptureIR does not need the hardware to match the original hardware design described in Digitrace.zip

MajorWoody · Post by **MajorWoody** » Fri Oct 20, 2006 8:57 am

I just uploaded TVISTO KM for ReplayTV 5000 http://www.hifi-remote.com/forums/dload ... le_id=3735 with NEC 2DEV Combo. I used NEC2 device only for arrow keys for repeated key sequences. TVISTO payback and search functions work great from ReplayTV 5000 remote, but I am still in testing phase.

Rob, thank you for protocol details. I will study "THIS Protocol-Builder zip file" before asking any questions.

johnsfine · Post by **johnsfine** » Fri Oct 20, 2006 10:40 am

MajorWoody wrote: I used NEC2 device only for arrow keys for repeated key sequences.

Why?

Why didn't you simply make an NEC2 upgrade for the whole thing? (Select NEC2 as the protocol name on the setup sheet).

It would be smaller and simpler.

I haven't seen anything in this thread that suggests your original remote uses NEC1 for some functions. Mostly we can't tell whether it uses NEC1 or NEC2, but where we can tell it is NEC2.

I understand that you used NEC2 for those keys where the difference between NEC1 and NEC2 would visibly affect the repeat behavior. But why use NEC1 for the others?

MajorWoody · Post by **MajorWoody** » Fri Oct 20, 2006 11:10 am

Nec2 are enabling repeated sequences. They are welcome on VOL, Arrow, Channel keys but not for play, skip forward, etc. For instance if I do long press in skip F.Forward, it may shutdown TVISTO.

Post by **The Robman** » Fri Oct 20, 2006 11:47 am

If you want to use NEC1 for most buttons and NEC2 for the VOL/CH/FFWD/RWD buttons, just change the first byte of the fixed data from "00" to "08" (or from "20" to "28" for upgrades with sub-device codes).

MajorWoody · Post by **MajorWoody** » Fri Oct 20, 2006 12:15 pm

I wrote simple program to convert timings to bytes. http://www.hifi-remote.com/forums/dload ... le_id=3738.

This program must be run with SQR interpreter. I do not have it with me right now.

For pairs: !+9002 -4536 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -546 +576 -1662

Output is:

9002 -4536 Initial Pair
576 -546 0h
576 -546 0h
576 -546 0h
576 -546 0h
576 -546 0h
576 -546 0h
576 -546 0h
576 -546 0h
576 -1662 1h Last Pair

------- Timing converted to HEX data ----------

Byte1 00000000
Byte2 1

MajorWoody · Post by **MajorWoody** » Fri Oct 20, 2006 12:26 pm

Rob, If I use NEC1 protocol for full layout and change fixed data from "00" to "08", then protocol will become NEC2? That is awesome!
00 to 08 change must be done in KM layout or in IR.

Post by **The Robman** » Fri Oct 20, 2006 1:01 pm

In KM you would use the "Parm (hex)" box (below the "Sub Device" box) on the Setup sheet. KM has built in support for parms 00 01 20 and 21 (which are controlled by you selecting NEC1 or NEC2 and entering 1 or 2 device codes) but there are many other variants that are not directly supported, which is why we give you the parm box so you can enter them yourself.

When you enter "08" in the parm box, the resulting upgrade will use NEC1 for most of the buttons, and it will use NEC2 for VOL +/-, CH +/-, FFWD and RWD. It won't do the arrow buttons.