NEWBIE question: creating new device upgrade

[heavyharmonies]

My apologies, but this process has me completely stumped. I've tried searching the forum, but 15 years of different versions of RMIR and different processes is a bit overwhelming.

So I'm using an Xsight Touch. Installed RMIR, updated firmware, am able to load upgrades, tweak them, save them, and upload them to the remote. Fine. Spiffy.

Where I am struggling is creating a new device upgrade where there is no starting point/template in the existing database.

The device is an AWOLVISION LTV-2500 UST projector. I've learned all of the buttons via the remote directly, and have tested the Xsight with the projector and all is well.

When I connect and download the data to RMIR, it appears that I cannot save this device as a new upgrade file. The data ends up being empty beyond the initial header information in the file.

My assumption is that there are fields that should be populated, e.g., Setup Code, PID, Protocol, etc., but damned if I know what I should put in those fields. The functions in the botton tab all have "Learn: __missing#", and the Key Map form is empty.

What am I missing in this process? I'm flummoxed.

Thanks.

[The Robman]

Can you post the RMIR file that has the learned signals in it, in the Diagnosis Area folder, then post a link to it here, and I'll take a look.

[heavyharmonies]

I'm away from where that computer is located, but will upload in the morning.

To clarify, are you wanting the device-specific file saved from the device page in RMIR, or the entire remote's save file?

Thanks.

[mdavej]

The .RMIR file.

When your situation occurs it's a new protocol unknown to us or bad learns. But we can usually figure something out for you by looking at the raw data.

[heavyharmonies]

Filu uploaded, thanks: http://www.hifi-remote.com/forums/dload ... e_id=26886

[mdavej]

Here's a starter upgrade. To load it, go to Devices - New - Open, and browse to this file. It's only a partial upgrade at this point.

The ** None ** in your learns are bad learns. Try learning them again. If all the data fills in the next time around you can type in the OBC value in the Functions tab of the attached file on top of the 255 I put in those few commands.

http://www.hifi-remote.com/forums/dload ... e_id=26887

EDIT: I went ahead and added the new upgrade to the TV device in your original file. Just download from your link above and upload to your remote to give it a try.

[heavyharmonies]

"new upgrade"? Not sure what you mean. Also, am not sure what time you made that edit vs. posting the original, so I don't know if I've been working from the original or your updated version.

I've gotten close. Through several learning iterations, I've got all the commands learned.

Problem though: In the process of trying to clean things up and export the device as a standalone upgrade file to ultimately be added to the DB, when I import the fresh device file, the SOURCE soft button falls by the wayside, and I'm not sure why.

Here is my updated RMIR file:

http://www.hifi-remote.com/forums/dload ... e_id=26888

The device name and some other aspects would need to be cleaned up, but as is this operates my LTV-2500 completely.

Thanks.

[The Robman]

heavyharmonies, let me explain how this process works, as I think you are making some assumptions as to what happens automatically that are not true. When a JP1 user gets a new device that is not supported by the built in setup codes in their remote, they set about building a "new upgrade". To do that, they first learn all of the buttons from their original remote using their JP1 remote so they can see what protocol the signals use and what the various device codes and button codes (OBCs) are. They then use that information to build a "new upgrade" which they can then add to their remotes memory. This new upgrade goes into a temporary memory section, it doesn't get added to the built-in setup code list.

So, when you posted your RMIR file, it clearly showed us which protocol (NEC1) was used, which device codes (0.206) and all the OBCs (except for the bad learns). So, Mike took that information and built a new upgrade file, which he posted for you. Then, just in case you didn't know how to add an upgrade to your RMIR file, he went ahead and did that too.

If you're curious how he did all that, read the following Wiki article:
http://www.hifi-remote.com/wiki/index.p ... y_Is_It%3F

[The Robman]

I have just updated Mike's RMDU upgrade file to reflect the latest batch of learns that you posted:

http://www.hifi-remote.com/forums/dload ... e_id=26887

I have also added it to your RMIR file, and removed the learns, here:
http://www.hifi-remote.com/forums/dload ... e_id=26889

[heavyharmonies]

Thank you... I think.

It's still a very non-intuitive process IMO.

I think that's the extent of the learning I need to do, as my remaining devices are bluetooth, and thus unless I get a FLIRC or other dongle solution, HDMI-CEC is my only solution (I believe).

I was able to get the Fire TV Max that is installed inside the AWOL to work via CEC with the Xsight. My nVidia Shield Pro, on the other hand is not cooperating... although that routes through the Denon receiver to the AWOL. HDMI-CEC is enabled on all 3 devices, but no bueno.

[The Robman]

It's still a very non-intuitive process IMO.

We welcome any suggestions that you have on how we could make it more intuitive.

[chuliu]

If all the learned signal have the same NEC1 and 0,206, you can highlight them all and convert to upgrade. Then an entry will be in device tab.

That's very intuitive, right?

In your rmir there was an entry with NEC, but not NEC1. I think that's what was stopping you from converting to a device upgrade.

[The Robman]

In your rmir there was an entry with NEC, but not NEC1. I think that's what was stopping you from converting to a device upgrade.

That was a result of poor learning.