Need help adding new codes to your Slingbox, this is the place to ask. You're welcome to ask general Slingbox questions here, but be aware that most of us are not Slingbox experts.
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.
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.
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.
