JP1 Remotes

[mdavej]

I put together a little GUI for John Fine's MakeHex to make it a little easier to deal with IRP files.

Please post any comments or suggestions.

LINK

EDIT: This tool leaves all your original IRP files intact. All changes are made to temporary copies.

[The Robman]

Seems pretty cool, appears to work as advertised.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

[vickyg2003]

Hi Dave, I need to download MakeHex to work with the IRScope, so thought I'd try your program too. Since I don't understand MakeHex, I'm having trobule understanding what MakeProntoHex is going to do, or how to enter data.
Is there a ReadMe?
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

[johnsfine]

[mdavej]

My GUI assumes you already understand makehex, so I rely on John's readme for that. There is a Help menu option that has a brief how-to and a link to his readme. The static text is just a format reminder. If you have any ideas, I'd be glad to add more to my help screen.

I wanted to keep it a 2 step process so you can preview your IRP changes to make sure they're correct, especially since the function fields are a little complicated. Direct editing is a 1 step process since you can see your changes as you make them.

I guess I could update the IRP automatically with each change the user types in, but you could get some weird intermediate results. For example, if you enter the end ranges first and leave the beginning blank, my code ignores them.

I'd be interested to see some other opinions.

To be perfectly honest, I still don't understand the "a.b through c.d" option myself, so I made no attempt to explain it in my help window

[johnsfine]

[mdavej]

I'll give it a shot. I also have a few other tweaks to do.

I agree that the user doesn't/shouldn't care about what gets written to what file or when. In spite of what I implied, I don't really change the IRP file itself, even when you press accept. Everything you see on the screen, edits included, is just in memory. I only write to my !output.irp when you press makehex. So I'm already doing it like you said, aside from the accept (preview) step.

[vickyg2003]

[3FG]

I like it! It definitely makes generating Pronto hex much easier.

My preference would be to eliminate the Accept button. Also, I would make the default choice for the format of the device/function number in the output file to be "Both". I can't see any downside to including both decimal and hex numbers.

ETA: How about including the protocol name as the first line in the output file?

This may be a limitation of the irp file format, but it would be good if there were a warning when the user specifies an illegal device or function number. For example, using Sony12 as the protocol, device 129 with function numbers up to 255 is accepted. The generated Pronto Hex is device 1, and the function numbers roll over at 128, so the final ouput is legal, but it doesn't match the description.

[mdavej]

New version posted. Removed "Accept" button and default to "Both".

Nothing I can do about the protocol name. I thought about putting it in the file name, but then you'd have to manage lots of output files versus one, so I decided against that.

I could add some limit checks too, but I don't know the rules for each protocol.

[garyb.ncc]

[garyb.ncc]

[johnsfine]

[3FG]

Yamaha receivers use the NEC1 protocol, and recently some functions have 16 bits of data. Normally the second byte of data in NEC1 is the complement of the the first byte, but Yamaha now sometimes violates that "rule".

I don't know whether MakeHex would generate such a code or not.

[garyb.ncc]