Where can I see the ir hex code assigned to a button?

In Pronto Edit, I could just double click the action and see the IR hex. It doesn't seem to work this way in Neo Edit. I do remember that to get this functionality in Pronto Edit I had to change a setting in an .ini file or something. Is there something similar in Neo Edit.

TIA...Josh

I dont believe they exist in Neo-Edit. You can however in the maranze RC3200 Setup version.

If it is in NeoEdit, its Neo propretary codes that are not readily available. RC3200 setup uses standard ccf Hex Codes.

In the download area you will find some tools:

NeoHacker (to enter Neo-Codes)
pronto2neo.xls (to convert ProntoIRcode to neo code)

and even some documents that helps to understand the way that the neo use to store IR-Codes...

h.a.n.d. Sven

So If I want to enter a discrete code I found on this web site, I have to convert it to Neo code with pronto2neo.xls then insert it with NeoHacker?

Josh

This is right! The Neo-Code is a 'compressed' format and is not as easy to understand than the Pronto-Code. But If you understand the format you are able to do almost the same with neo-code...

Pronto code:
groups of 4 hexnumbers...
1. 0000 or 0100 (modulated or unmodulated ir-signal)
2. xxxx (divisor for the modulation frequenzy)
3. yyyy (length of the one-time code)
4. zzzz (length of the repeated code)
5. cccc cccc cccc .... (Bursts, first one-time (if exists) then repeated (if exists))

Neo-code:
groups of 2 hexnumbers...
1. 0 (Every learned code starts that way)
2. f "
3. 6c (There are some codes with other numbers but mostly 6c)
4. x Size of the Burst-times table (can be 2-6(7?))
5. yy Divisor for modulation-frequenzy
6. Lead-Out burst time for the "OFF" part of the Leadout of the repeated part of the code.
7. Table with burst times. The Neo can NOT have every burst separately spezified. Neo can only use one of the predefined times of the Table. So here the length of the burst can set in this table. almost all the codes I've ever seen is easy to build with only 2-4 different timings for the burst. The table is 2-6, sometimes 7 bytes long

8. IR-Code... Instead of exact timings for every burst now only the number of the code of the table (see 8.) will be written... This makes it possible to put 2-4 complete Burstpairs into only one byte of IR-code. The Pronto will use 4 bytes for only one Burstpair.
The one-time-code and the repeated-code has it's spezial "start" and "end" mark because there is no length-byte like the pronto-code have.

This is the information I've extracted from the documents here in the Files-section of remotecentral.


h.a.n.d. Sven

Thanks...Josh

I used NeoHacker and Pronto2Neo... on a whim, I just hit Ctrl-V in NeoHacker and the exact same code was displayed as if I went the two step route through Pronto2Neo.

Am I correct??