I have a TSU9600 and a Tvix HD M-4000P. I have successfully learned all the codes from the Tvix remote. The on/off Button is a toggle. I have found what appear to be discrete on and off codes at this location on the Tvix website: [Link: dvico.com] .
However I haven't a clue how to implement them into the database, or more precisely how to get them into Pronto hex format. I have read articles here on how hex codes are deciphered but have no idea how to get the Tvix info into a readable format. Any help would be appreciated either on how to accomplish this or where I might find info on doing this.
Thanks

Try fixing the bad URL you posted for that pdf file.

I probably can help you if I can get the file.

Thanks for the reply. Hopefully this will work:

[Link: dvico.com]

Thanks again'

Steve

That's now a well formed url, but it still doesn't work for me.

My email is listed in my profile. You could email the pdf to me. Generally it is better to make such info available to any expert who may want to help. But given that seems to be difficult, I'm the resident expert who most often looks at manufacturer documentation of IR protocols to try to translate that into a form that is useful for Prontos etc.

If it would be any help below is the learned Pronto code for the on/off button which is labeled as K1 in the chart.

0000 006E 0044 0000 0156 00AA 0016 0015 0016 003F 0016 003F 0016 0015 0016 003F 0016 0015 0016 0015 0016 003F 0016 0015 0016 003F 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 05F6 0156 00AA 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 003F 0016 0015 0016 0015 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 003F 0016 0015 0016 003F 0016 003F 0016 003F 0016 0015 0016 0015 0016 003F 0016 0015 0016 003F 0016 0015 0016 0015 0016 0015 0016 003F 0016 003F 0016 0015 0016 003F 0016 C590


Also if it helps below is the code for one other button, K7 which is the digit 1.

0000 006E 0022 0002 0156 00AA 0016 0015 0016 003F 0016 003F 0016 0015 0016 003F 0016 0015 0016 0015 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 003F 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0741 0156 0055 0016 0E56

Thanks again,
Steve

I got the pdf by email.

I wouldn't have figured out what that pdf meant without that learn from the K7 key. The On/Off key is quite strange. Seeing its Pronto hex AND the Pronto Hex for K7 and the pdf description of On/Off was enough to understand On/Off. Seeing two learned signals, even though one was the tricky one, was enough to figure out what the PDF means.

The PDF says the discrete power commands only work on the HD M-4100SH and HD M-5100SH. Is your model one of those two?

Also that note covered up the "Custom Code" value for the discrete codes, so I can only guess it is 0x96 like the rest.

Most models of Pronto understand the 900A condensed form of Pronto Hex, which is easier for these codes. So we'll try that first. If it's wrong we can do this the harder way.

First try K7 in 900A form. It is

900A 006D 0000 0001 961B 0000

If that works then your TSU9600 is processing 900A condensed Pronto Hex correctly and the signals really are what they look like from that learned sample. Then you can try the two discrete codes:

900A 006D 0000 0001 9644 0000

900A 006D 0000 0001 9637 0000

But if the 900A form of K7 doesn't work, we'll need to get the discrete codes a different way.

BTW, the On/Off button is a macro, first sending the signal

900A 006D 0000 0001 9656 0000

then sending the signal

900A 006D 0000 0001 20DF 4EB1

It would be interesting to know what the device does in response to those individually.

John,all I can say is that you're a genius. At first I couldn't figure out where you saw that the discrete codes only applied to the 4100SH. I hadn't added the Korean Language pak to Adobe reader, but when I did the little note showed up. I have a 4000P which was replaced by the 4100SH, but thought I'd check out your tips regardless. First I did the digit 1 which worked fine with the 900A code. Then I tried the two discrete codes neither of which did anything. However when I tried the two codes included in the macro the following happened. The first code (900A 006D 0000 0001 9656 0000) will turn the unit on or off i.e. press it turns it on, press it again it turns it off, press it again it turns it back on. The second code (900A 006D 0000 0001 20DF 4EB1) will only turn the unit off. If the unit is off it has no effect no matter how many times you press it.
So the simple solution until I upgrade to a 4100SH to use the discrete codes appears to be a macro that first sends the second command to make sure it's off, a short delay, then the command that turns it on. When I want to turn it off I'll just use the off only command.
Do you see any reason this wouldn't work?
I can't thank you enough for helping me with this. If you're ever heading down toward the Florida Keys (where I live) and enjoy fishing and/or boating send me an email (my address from my profile) - I'd be more than happy to take you out.
Thanks again,
Steve

Thanks very much steveswan and johnsfine for raising the point and coming up with a solution for the TVIX 4000. I have one of these wonderfull units and I am located in Melbourne Australia. Using a Pronto 3000 and a URC MX-850 and MX-900 I am certainly eager to try your solution, I will do this over the weekend and will let you know how I went with this. Cheers!

I have a TVIX HD-5100SH, and I have been struggling for some time to duplicate its remote with my Marantz RC-9500. I´d like to thank John for bringing me very close to a final solution to this problem, but I still have a question for him.
I have inserted the 900A codes for all buttons into the Marantz Wizz-it editing software, but something strange happens.
Wizz-it accepts the condensed codes, but as soon as I press OK and close the "add IR codes" box, Wizz-it "translates" the codes to Pronto hex. I cannot make the codes "stick" in 900A format. This would normally not be a problem, but in my case, the Pronto hex codes seem to send out "double" commands. This is particularly apparent when scrolling menus with the up and down arrows. The cursor jumps two positions at the time instead of just one. I have worked around this by limiting the burst to 0,02 seconds, but clearly it must be something wrong with the codes generated by Wizz-it?
For instance, the 900A code for discrete on is: 900A 006D 0000 0001 9644 0000
John translation for this code is:
0000 006D 0022 0002 0157 00AC 0015 0016 0015 0041 0015 0041 0015 0016 0015 0041 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0689 0157 0056 0015 0E94
The Wizz-it translation for the same code is:
0000 006D 0022 0002 0155 00AB 0016 0015 0016 0040 0016 0040 0016 0015 0016 0040 0016 0015 0016 0015 0016 0040 0016 0015 0016 0015 0016 0040 0016 0015 0016 0015 0016 0015 0016 0040 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0795 0155 0055 0016 0E55

Can you tell anything from this example John?
I can give you more codes for more buttons if you need them, but that would have to be by email.

Jan.

I guess the RC-9500 doesn't understand 900A form and Wizz-it compensates by translating the signal to the form all models understand.

The differences between the way it translated and the way I translated shouldn't matter. Doesn't the code I translated have the same problem as the code it translated?

As for the problem itself, I'm not sure what aspect of the signal timing is causing that failure.

What do you mean by limiting the burst? I didn't know there was any feature like that in a Pronto.

The two values in that Pronto Hex string that control the timing are the two large ones near and at the end (0795 and 0E55 in the one Wizz-it translated). I think increasing those, especially the first one, might fix the problem of double signals. But maybe things are behaving strangely and decreasing them would help. Only big changes to those values can have a noticible effect, but I'm not sure of the max that the RC-9500 can understand. Try changing the 0795 to 0F00. Try changing it to 1800.

Thanks again!
The funny thing is that other condensed A900 codes remain untouched by Wizz-it. It seems the four last digits decide whether or not they are translated. For instance, the code: 900A 006D 0000 0001 20DF 4EB1 (powercode for a Tvix 5000) is not translated.
Yes, your translation caused the same problem with double signals as well. There is a function in Wizz-it (as in ProntProEdit) where you can set the timing for the code burst. I have looked at other pcf-files on remotecentral for other models from Dvico, and most of them seem to have set very short times for the arrow commands to work around this problem.
I will try changing the values as you suggested and keep you posted.

Jan.

I partially understand why that would happen. Anyway, it shouldn't matter. The actual signal sent shouldn't be changed as a result of the translation.


I know there is a feature in ProntoProEdit where you can set a value that extends the duration of a signal. I don't think that same feature can limit the duration.

When you use a signal in a macro, the firmware must select the duration. It has some default rules for that if you don't specify an extended duration. Depending on the device, that default may be too short or too long.

If I understand correctly, setting a duration for a signal used in a macro can only extend the default duration. If you set a duration less than the default, I think it uses the default.

Outside a macro, I don't know if the specified duration has any effect at all. The duration of the actual button press ought to control the duration of the signal.

Are you using the problem signals in a macro (anything with more than one action on the button) or is the "learned" signal the only action on the button?


I should also mention that there is a minimum possible duration for the signal. The minimum is less than the default duration. The value you mentioned 0,02 is less than that minimum duration.

Maybe the firmware can reduce the duration below the default when you specify a short time. I doubt it, but I'm not sure. The firmware certainly can't reduce the duration below the minimum. If specifying 0,02 really does help somehow, I guess that means it takes any value below the minimum as a command to send the minimum.

The only two signals I use in a macro are the on/off commands.


I have looked into the settings in Wizz-it a little further, and I think you are right. Setting a very short duration time just makes the remote send the minimum signal. Somehow this prevents it from duplicating the signal, which probably happens if you press the button a little too long.
I haven't had time to check out the new parameters you gave me yet, but i'll be back with the result of that.

Jan.

Hello from France,

I am interested in this discussion: I own a Tvix M4000 and would like to get the Pronto hex dicrete "Off" command (not the 900A form, but the long stream of values).
If I well understand, I can only get the off discrete code for this model. The good thing is that this is the one I need more, to be sure the Tvix is off before I send an X10 main switch off after a tempo...

Sorry to disturb this post and thank you very much.

selac

See post 9, of the non Pronto thread on this subject at
[Link: remotecentral.com]

You might find the rest of that thread informative as well.