Is it possible to go from JP1 to Pronto Neo?

[SCCA Racer X]

I have read the thread about going from Neo Hex to EFC. Is it possible to go the other way?

I like to hack around for discretes using the JP1 HTPro, but when it comes to everyday use I prefer the MX-500. No problem, it learns incredibly well. Today I should be getting my first Neo in the mail and I'll be seeing if I like that even better. I've read the Neo may not be as forgiving a learner, so I'd like to have plan a B.

Thanks,
Jeff

[johnsfine]

Can the software for the Neo import Pronto Hex?

I have a partial understanding of the Neo Hex format, but I don't know of any tools for converting in either direction between Neo Hex and the generic Protocol, Device, Subdevice and OBC form we use in most of our programs.

You can convert from Protocol, Device, etc. to Pronto Hex using my MakeHex program. I expect you can find a way to import Pronto Hex or convert it to Neo Hex.

MakeHex works with OBC numbers, not EFC numbers. My decode software (used in various tools that go from Pronto Hex to Protocol, etc.) normally generates both OBC and EFC so you can choose whichever is more convenient for the intended use. But MakeHex has no EFC option, so if you're starting from EFC numbers you must first use some JP1 program to convert the EFC numbers to OBC. KM or RM are the programs with the most complete protocol specific rules for that conversion. The functions page of either can be used as that conversion tool once the setup page has been filled in.

[johnsfine]

using the JP1 HTPro, but when it comes to everyday use I prefer the MX-500.

In another thread I determined a particular MX-500 was consistently transmitting signals at 4Khz lower frequency than it had learned them and I think consistently transmitting them with 2.5% shorter duration.

Either one of those symptoms could be an out of spec component within a correct design. But the two symptoms together don't make sense as an out of spec component (a component causing lower frequency would cause longer durations). Only a firmware bug makes sense. But if one MX-500 has that firmware bug wouldn't they all? Very few protocols are picky enough to notice that disortion at all. So I'm wondering if all MX-500's have this flaw and no one noticed before.

Can you do a test for me to see if your MX-500 distorts signals that way:

1) Select some built-in setup code in the HTPro. As long as you tell me which it is, I'll know what the timing should be.

2) Learn a few signals from the HTPro to the MX-500.

3) Learn them back from the MX-500 to the HTPro.

4) Download the HTPro's eeprom to a .ir file using IR.EXE

5) Put that file in the diagnosis area and post its URL back here.

[SCCA Racer X]

It is my understanding that to get from Pronto Hex to Neo Hex, you use the Marantz version of NeoEdit, which displays codes in the original Pronto Hex. So you can pase Pronto Hex codes in the editor, save, and read the corresponding Neo Hex in NeoHack. So it sounds like there is a (moderately convoluted) path. I look forward to giving it a try!

Thanks,
Jeff