------------------
Sorry for the repost, I figured my post was really for the Pronto Classic than the PDAs.The original post was at [Link: remotecentral.com] delete if necessary.
-------------------

Alright, I have this Neuston Virtuso MC-500, but its remote died one day. Its not a well known brand, so I couldn't find a universal remote that has its remote codes built in. The manufacturer does have a list of remote codes in NEC format shown here:
[Link: neuston.com]

I've read how the Pronto Hex codes for NEC codes can be generated from MakeHex, so I tried it and generated the required hex, and consequently the ccf file from hex2ccf. However, none of the nec protocol versions I tried worked. I probably blame it on my lack of understanding of what should be entered in the Device field, is it the decimal equivalent of 01FE (510) or 01 (1) or FE (254)? Or did I get everything wrong here?

So what I am now looking for is the proper way of generating the ccf file, or, since I am using a PDA to emulate a Pronto, any software that I can use?

It should also be noted that there is already a pcf file for the neuston found in the database but I do not have any software that can read or convert it (I still do not understand why it cannot be converted):
[Link: remotecentral.com]

Please reply asap, I've been trying to get this working for almost 3 months now; alternatively, if anyone has a Neuston MC-500, please help create a ccf file and share it!

Thanks!

Most likely 1. But maybe 128. Manufacturers aren't always consistent about how they represent this info in hex.


I'll see if I can find the file you mean and get some Pronto Hex strings out of it with some version of ProntoEditNG. Those can be decoded with IrTool to tell us whether we're reading that documentation correctly.

That was easier than I expected. I got the file from
[Link: remotecentral.com]
I opened it and grabbed the Pronto Hex for Play/Pause, which was
0000 006D 0026 0000 0155 00AC 0016 0040 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0040 0016 0040 0016 0040 0016 0040 0016 0040 0016 0040 0016 0040 0016 0016 0016 0040 0016 0040 0016 0016 0016 0016 0016 0016 0016 0040 0016 0016 0016 0040 0016 0016 0016 0016 0016 0040 0016 0040 0016 0040 0016 0016 0016 0040 0016 05EB 0155 0056 0016 0E55 0155 0056 0016 00AC

I decoded that with IRtool and it is NEC1 device 1, function 70. Looking in the Neuston documentation you linked, Play/Pause is function 0x46. 46 hex is 70 decimal, so everything is as expected.

None of that explains what went wrong when you tried MakeHex, but if you give more details, we probably can figure it out.

Thanks for the quick reply!

I tried it with the settings you found, still no go.

Here are the relevant files:
NECx1.irp
[Link: pastebin.ca]
Neuston.hex
[Link: pastebin.ca]
Neuston.ccf
[Link: sharebigfile.com]

The commands I used to generate the above files are:
MakeHex.exe NECx1.irp Neuston.hex
hex2ccf Neuston.hex Neuston.ccf

This brings me to think that maybe the IR receiver is damaged, but I'm quite sure the remote's dead; IR images of the remote's LED show that its always on even when no button is pressed.

Then it could also be the crappy software I'm using on my PDA to emulate the Pronto. It does however work when I make it learn my TV's remote.

The information provided by the manufacturer could be wrong too, though the fact that someone managed to create a pcf file with the right code and uploaded it may prove it otherwise (why upload a file that doesn't work?)

So now I have multiple possible points of failure.

Don't use NECx1.irp, use NEC1.irp

Nope, it didn't work.

nec1.irp
[Link: pastebin.ca]

Neuston.hex
[Link: pastebin.ca]

Neuston.ccf
[Link: sharebigfile.com]

I'll need someone to confirm if the ccf i generated works. If it does, then I know my software is crap and I should get a real Pronto.

Your .hex file looks OK. I couldn't figure out how to get your ccf file to check that. You can email it to me if you want me to check it (see email address in profile).

If the CCF file is OK, I have no idea how to check whether your PDA software is bad, or you're using it wrong, or your Neuston doesn't really use the same IR signals from that pcf file and the Neuston web site.