JP1 Remotes

split from:
https://www.hifi-remote.com/forums/viewt ... p?t=100377

chuliu
I'm trying this whole procedure again with a different remote programmed onto my NEVO C2


I download the remote and go in the LEARNED SIGNALS tab and highlight everything and click CONVERT TO DEVICE UPGRADE but nothing happens

Just a wild guess.
Did you highlight only those signals that belong to the remote you were trying to create bin for? Because you said you highlighted everything, could you highlight also those learned signals that were part of a previous learned remote?

What is the protocol of the new remote?
You can always create a rmdu from scratch.
Just go to device tab, new a device, give it a name, then select the correct protocol. fill in device and subdevice etc. Then go to functions, add functions so that they are have the correct obc and sub device or oem2 (if applicable). Then map the functions to the buttons. Save the device as a rmdu file.

Then click ok to save the device. Upload to nevo c2. Test it on your device to see if the remote is working. Then launch remotemaster, open the rmdu file, change device to slingbox pl chip, export binary upgrade. That is all.

Thanks..... I was thinking about doing that .... but that would take me an age.

Any idea why clicking on CONVERT TO DEVICE UPGRADE isn't doing anything?

Post your RMIR file and we can tell you why.

theartistisblue wrote:Thanks..... I was thinking about doing that .... but that would take me an age.

Any idea why clicking on CONVERT TO DEVICE UPGRADE isn't doing anything?

That wouldn't take ages.
You can copy the functions names and obc from the learned signal tab and paste. Also, as far as I know, convert to device upgrade only works on some basic protocol. For more complicate protocol, it doesn't work properly. Some manual editing is needed anyway.

Here's how to make an upgrade from scratch if the automatic way doesn't work. It's not that bad.
http://www.hifi-remote.com/wiki/index.p ... _Setup_Tab

theartistisblue wrote:Thanks..... I was thinking about doing that .... but that would take me an age.

Lol, we've all done that thousands of times, I'm sure you can manage doing it once.

Now I know why CONVERT TO DEVICE UPGRADE isn't working....

With this particular remote, unlike the previous one which I used, I do not get any entry for PROTOCOL, DEVICE, SUBDEVICE etc....

Kindly see: https://ibb.co/cw5xNn

What can I do please?

theartistisblue wrote:Now I know why CONVERT TO DEVICE UPGRADE isn't working....

With this particular remote, unlike the previous one which I used, I do not get any entry for PROTOCOL, DEVICE, SUBDEVICE etc....

Kindly see: https://ibb.co/cw5xNn

What can I do please?

this...

mdavej wrote:Post your RMIR file and we can tell you why.

Done! My RMIR:

https://www.dropbox.com/s/0pcvhqcf93x3c ... .rmir?dl=0


Many thanks. Would like to see what's so different this time....

Here's a copy preserved in our file section (outside sourced files have a tendency to disappear):
https://www.hifi-remote.com/forums/dload ... e_id=25107

This is a new protocol, so I have created a new executor for it. I don't have time to test it, so I am posting the KM, PB and RMDU files so you and/or others can experiment with it if it doesn't work.

https://www.hifi-remote.com/forums/dload ... e_id=25109

I don't think you mentioned what device this is.

PS. The OK button was a bad learn, so I couldn't decode that one.

Thank you.

Looks good only I cannot test it where I am ..


If I remember - thats the only button I didn't test... the OK... I will redo it and send you the RMIR again, is that ok?

This device is an ADB cable box tailor made for Melita Cable Company in Malta.

They change their boxes a lot !

Will get in touch soon.

Yes, please re-learn and re-post the OK button.

Does the ADB box have any sort of model number?

Will do - as soon as I'm back at my place.

Will give you the exact model number too

Cheers