Converting JP1 Learned commands to Pronto Hex?

[Banta156]

Hello,

I can't seem to find the answer to my problem. I love my JP1 Remote, but have a Home Automation device that will only accept Pronto formated codes.

So, the question is, how? What software do I use to convert a learned code on my JP1 remote into a Pronto hex code? I can't seem to find one that will work. My learned commands show up in IR as something like....

+7988 -4030 +500 -1506 +500 -506 +500 -1506 +500 -506 +500 -1506 +500 -506 +500 -506 +500 -506 +500 -4002 +500 -1506 +500 -506 +500 -1506 +500 -506 +500 -1506 +500 -506 +500 -506 +500 -506 +500 -21064

... I have tried to use IRTool but, that doesn't like the code.

I have also looked into the .txt file saved by IR but, can't figure out how to isolate the individual leaned commands, such as....

0220: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0230: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0240: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

......

Anyone can point me into the right direction? I just need to convert the learned codes to Pronto hex and do not need the entire remote to be converted.

THere must be a utility to do this? I can't seem to find the answer.

Thanks in advance
Banta

[The Robman]

I have a Home Automation device that will only accept Pronto formated codes.

What is the device? If you give us the brand and model number, it's possible that someone here is familiar with it and can give you more specific help with it.

So, the question is, how? What software do I use to convert a learned code on my JP1 remote into a Pronto hex code?

When you look at the learned signals in IR.exe, does it display a protocol, device code and OBC/EFC codes? If so, that's the info that we need.

My learned commands show up in IR as something like....

+7988 -4030 +500 -1506 +500 -506 +500 -1506 +500 -506 +500 -1506 +500 -506 +500 -506 +500 -506 +500 -4002 +500 -1506 +500 -506 +500 -1506 +500 -506 +500 -1506 +500 -506 +500 -506 +500 -506 +500 -21064

Raw timing data like that is rarely of any use to us, it doesn't even give us the frequency. If IR.exe doesn't display the protocol info, post your entire IR file in the Diagnosis Area then post a link to the file here.

I have tried to use IRTool but, that doesn't like the code.

IRTool is used to convert Pronto hex into JP1 codes, not the other way around. The reverse program is MakeHex, but you need the protocol info to use that tool.

I have also looked into the .txt file saved by IR but, can't figure out how to isolate the individual leaned commands, such as....

0220: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0230: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0240: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

The segment of the dump that you posted contains absolutely nothing (you'll notice that every single byte is null (ie, FF). The learned signals start at either $3FF or $400 depending on which remote you are using, but even if you were able to isolate the code, it would be of no use to you.

Anyone can point me into the right direction?

Hopefully I have.

[Banta156]

Excellent Info Robman. I do appreciate the help.

The device I am using is a combination of Homeseer and MainLobby. These programs utilize a device by Global Cache called the GC-100. With the GC-100, IR signals are translated over TCP/IP and sent to my IR devices. Both Homeseer and Mainlobby use Pronto hex codes, although the Mainlobby info says "supports Pronto Learned, RC5, RC5X, RC6 and RC6X formats". I am not familiar enough to know if this is of any help. I did manage to get some codes from

http://ir.premisesystems.com/

these codes work.


Yes, the learned signal displays the information you described, as follows. This is a learned command the remote Toshiba SE-R0089, which is used with the Toshiba SD-H400. The learned command is for the Select/Enter button.
The JP1 remote is the RS 15-2117.

Here is the info...

Frequency = 38277

# = 1
Protocol = NEC1
Device = 69
OBC = 39
Hex Cmd = 7B
EFC = 217

So, having the protocol info available, will MakeHex work? If so, could you point me to the right direction to use the program? I have downloaded it but, when I run MakeHex.exe, A dos window zips by and closes so, I do not know what I am suppose to do to convert, and subsequently find the data.

Thanks again for any help you can provide and yes, you are difinately getting me going in the right direction.

Thank You!
Banta

[johnsfine]

The timing you posted first doesn't look to me like that NEC1 signal.

The timing looks like a Proton command. That command happens to be in this CCF file renaud-wangler_ccf.zip
I'm confused over which device is which in that CCF. I think the device with that command is the Daewoo VCR DVK965S.

The NEC1 signals are easy to generate with MakeHex. See the ReadMe file included with MakeHex.

But you don't need MakeHex. All Toshiba DVDs use the same (NEC1, device 69) signals. You can find lots of CCF files for Toshiba DVDs at:
http://www.remotecentral.com/cgi-bin/fi ... player&fc=

And if you prefer data from Premise, the NEC1:69:39 command you mentioned is the Audio command in this code set at Premise (and in several other code sets at Premise)
http://ir.premisesystems.com/search.asp ... A&l=SD2006

[Banta156]

Very Impressive JohnsFine!

You are exactly right. The Original Post did have a comand learned from A Daewoo VCR. But, I subsequesntly blew it away. I wound up using the codes from the site I listed with the premis link. It did appear to be a proton command. WOW!

I used the NEC1 signal in the second post. I was hoping it might be easier and most of the codes I have tried to learn seem to be using this.

I am curious. I did find some CCF files for a divice I would like to use, but, could not find a way to extract the hex code from the file. I downloaded ProntoEdit and tried to find the button code in there, but, all I could seem to find was info about the screen layout. Perhaps I was not looking in the right place??? For sure, I am a novice.

But, I did build a JP1 cable that worked first time out, so, I got that under my belt!

Going to read the Makehex readme now.

Any more help is appreciated, as well as needed.

I am impressed with your knowledge of the code.

[johnsfine]

I think I was editing my previous post while you were replying to it, so you may want to reread it.

I also reread your post (a couple back) and you said the "Select/Enter" key. But I'm sure that is OBC 33 and you said 39.

I'm really not sure what you're trying to do here. But if you read the ReadMe file for MakeHex you probably now know how to do that part.

If you want ProntoEdit instructions, ask again in the right forum:
http://www.remotecentral.com/cgi-bin/mb ... o/list.cgi

[Banta156]

Yeah, it is a goofy remote and device. It is a DVD and TIVO combo. This is one of the reasons I need to learn the IR signals with my JP1 and convert them to Pronto. I could not seem to find any of these remotes that have been decoded.

Right again! I had it wrong and it is obc 33.

How, if you can tell me this, do I look at the protocol code and what not, and know which code that is available will work, or is the same. I guess this is where the mystery comes in for me because I am amazed that you are able to pick up that little imformation and know exactly what I have.

As far as what I am doing, I really just need to convert the learned JP1 commands to Pronto hex codes. As I stated, none of the Tivo functions seem to be readily available for the Toshiba device, so, I figured learning and converting them would be my best bet.

Any more thoughts?

Sorry to bother you, but, I am trying to understand how I can go out and grab the MANY readily available codes. Or how to just convert into Pronto codes using the information provided above such as Frequency, protocol etc..

Thanks again!

Oh, and how do I get MakeHex into GUI mode???

Thanks

[johnsfine]

How, if you can tell me this, do I look at the protocol code and what not, and know which code that is available will work, or is the same. I guess this is where the mystery comes in for me because I am amazed that you are able to pick up that little imformation and know exactly what I have.

Now if only I could read questions like that as well as I can read IR signals 8)

Answering what I think you're asking:

I have gradually downloaded a LOT of CCF files from RemoteCentral and run them through my DecodeCCF program to get .txt files full of protocol/device/subdevice/OBC data matched with whatever identifying info was in the CCF file. When I download those I create a .text file for each containing the original URL at RC and the list of Brand/Type/Model info from that URL. Then manually, I put the protocol/device/subdevice values found in the .txt file next to the models in the .text file wherever I can tell which device is which.

I use a text search program to search the .txt files or .text files for various things. For example, in answering this thread, I did a search of .txt files for Pronto:21:21, which is what I manually guessed that timing was, found it exactly once and opened the corresponding .text file to see what URL it came from and what device within that URL I had guessed owned that signal when I first downloaded it.

For NEC1:69, that is so common JP1 experts would just know that is a Toshiba DVD. I did a .txt search for NEC1:69:39 to see it was the "Audio" command in all the files I have for Toshiba DVD's.

I noticed then that the DVD model numbers tend to start with SD, so I checked Premise (where they don't list the device types) for SD models to verify that their data matched.

Even without the giant library of .txt files to search, you can do a lot of the same things by decoding individual CCF files with DecodeCCF.exe and DecodeIR.DLL, decoding Pronto Hex (such as from Premise) with the JP1 version of IrTool and DecodeIR.DLL and decoding JP1 signals using IR.EXE and DecodeIR.DLL. Since they all use the same decoder the results are directly comperable.

As far as what I am doing, I really just need to convert the learned JP1 commands to Pronto hex codes. As I stated, none of the Tivo functions seem to be readily available for the Toshiba device, so, I figured learning and converting them would be my best bet.

If you're using Ir.EXE and DecodeIR.dll correctly, that should give you protocol/device/subdevice/obc for each command.

If you understood the MakeHex instructions you know how to take Protocol/device/subdevice and turn it into a .hex file with Pronto Hex for every OBC (which MakeHex calls "function") then edit that .hex file and copy out the specific OBCs you decoded.

I'm not a Tivo expert. But this is the right forum for Tivo IR knowledge. It may be easier for you to just decode learned signals than find the answer here. But I suspect the answer about Toshiba Tivo is already posted somewhere in the forum or file area.

Oh, and how do I get MakeHex into GUI mode???

By downloading the C++ source code of MakeHex and writing a GUI for it.

I didn't write a GUI for MakeHex. The readme explains it.

You can use it in command prompt mode. You can use it by the drag and drop method explained in the Readme. You can make a Windows explorer association for it for the .ir extension and run it by double clicking the .ir file (that's how I do it). I use file extension associations and context menu items for almost everything, so I do most tasks by double clicking or right clicking a file in the file explorer.

[Banta156]

Thank you SO Much.

This definately spins me in the right direction. It looks like MakeHex was the answer all along, I just didn't know how to use it.

Just to pick your brain one last time and then I will experiment on my own. I am a little confused on what all is necassary to change. Particularly the "Function"

For instance, for the device code above, in the .IRP, I did the following..


Device=69
Function=33

Protocol=NEC
Frequency=38277
Time Base=564
One=1,-3
Zero=1,-1
Prefix=16,-8
Suffix=1,-78
R-Prefix=16,-4
R-Suffix=1,-174
Default S=~D
Form=*,D:8,S:8,F:8,~F:8,_;*,_

and the results were....

0000 006C 0022 0002 015A 00AD 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0041 0016 0698 015A 0057 0016 0EB7

Did I do this right? I guess the thing that is confusing me with function is if a single number or a range of numbers should be spcified? Also, I left "Protocol=NEC", and I am wondering if I should have changed this to
"Protocol=NEC1". As for the rest of the parameters, I am lost. Ok to leave them at the default when IR.exe just specifies the above info, or this this where,,,
Hex Cmd = 7B and EFC = 217 comes into play?

After that, I am on my way and saved a couple of bucks to boot!

Extremely grateful! Should have asked earlier.
Thank you so much
Banta

[johnsfine]

Did I do this right?

IrTool decodes it right, so I think you got it right.

I guess the thing that is confusing me with function is if a single number or a range of numbers should be spcified?

Whichever you prefer. If you specify one, the output will have one. If you specify a range the output will have one for each value in the range.

Also, I left "Protocol=NEC", and I am wondering if I should have changed this to
"Protocol=NEC1".

The Protocol= line in the .irp file is just a comment. It has no effect on the output. It was intended to be used in some GUI that never got written. It is also useful in cases where a .irp file's contents are posted in a forum without the filename. But I guess I haven't kept it in sync in every .irp file.

As for the rest of the parameters, I am lost. Ok to leave them at the default when IR.exe just specifies the above info, or this this where,,,
Hex Cmd = 7B and EFC = 217 comes into play?

The other parameters describe the protocol structure. Usually you would have no reason to mess with them, because those things are very consistent from one device using a protocol to another, and Jon and I have recoded them fairly accurately in those .irp files.

If the frequency were significantly different (2Khz or more) between the learned signals and the .irp, AND the learned frequencies are consistent enough (to each other) that you trust them, you might want to make an edited copy of the .irp with a different frequency. Occasionally a protocol is used with a different frequency than we expect. DecodeIR normally doesn't check. It's rare enough even the experts usually don't check until we see some strange failure and start checking obscure details to find the cause.

Beyond that, there's nothing you can usefully change without a good understanding of IR signals and almost never anything you'd have any need to change.

[The Robman]

Btw, if you have a ready made CCF file and all you want to do is extract the pronto hex code, you don't need to use ProntoEdit, you shoudl use anothe rone of John's programs called CCF2EFC. Be aware, however, that CCF2EFC can't handle the newest formats of CCF files (those labelled M1, I think).

[Banta156]

Good Information.

I thank you both and I will post if I run into any troubles.

This gets me miles ahead of where I was yesterday and, as long as I am moving forward, I am making progress.

Thank You

Banta

[The Robman]

Straight ahead: REMOTE NIRVANA !!!