Page 1 of 1

How To: Manual Settings in RM

Posted: Sat Apr 25, 2009 11:16 am
by gfb107
The first thing is to check to see if there's already a protocol with name "pid: XX XX" in the protocol drop-down. These are generated for entries in protocols.ini that only have the PID and some protocol code, but which don't have details about device and command parameters and how to convert those to fixed and variable data. There are a lot of such protocols. If there is an entry for the protocol you want to use, don't use Manual Settings at all, use this entry. RM will have automatically determined the number of fixed and variable bytes used by the protocol and created appropriated device and command parameters, and provides control in the Protocol Parameters of how the device and command parameters are mapped to the fixed and variable bytes. For protocols that use multiple variable bytes, use the Cmd Byte Index parameter to control which variable byte is the command byte, which is used for the OBC and EFC.

If your protocol isn't already in the list as described above, and it's known to be present in some remotes, it should be added to list of known protocols. Please make a post here about it so it can be added.

Here's the instructions for using RM's advanced support for Manual Settings.

Click on Advanced -> Manual Settings...

Enter the Protocol ID

If you have a raw protocol upgrade, copy it into the clipboard, then double click in the cell next to the appropriate processor, and paste the raw upgrade code there.

If you have a formated protocol upgrade, copy it into the clipboard then click the Import Protocol Upgrade button and RM will put it in the correct place. A formatted protocol upgrade might look like

Code: Select all


At this point RM will have generated default protocol and command parameters based on the imported protocol code.  You can change the number of bits for each protocol/command parameter, as well as the way it is encoded into hex (LSB/MSB, COMP or not).  You can also rename the paremeters if desired (just double-click the name and edit it).  

If the protocol uses more than 1 variable byte, you can also control which variable byte contains the command code, by changing the Command Index.  Note that changing the Command Index will automatically change the command parameter names so the matching command parameter is named 'OBC'.

You may use the "View Ini" button to see a starter protocols.ini entry based on what you've done.

Press OK to save your changes.

Back on the Setup tab, use the "Protocol" combo box to choose the manual protocol you have just created.  It will have the name "PID XX XX", and will be the last item in the list.

Now you can enter protocol and command parameters in the same way you would using a known protocol.

Posted: Sat Apr 25, 2009 11:44 am
by The Robman
Just FYI, when I create upgrades that use protocols that I've written myself, I always use $01FF as the protocol id, which is not an official protocol id so it's not in any remote.

If I'm creating a Manual Settings upgrade that uses an official protocol, but it's one that's not supported yet, I use the official protocol id.

My suggestion would be that when RM is used to open such an upgrade, it should check to see if the remote already has this executor installed. If the supplied protocol code matches the code in protocols.ini, a protocol upgrade should not be presented.

Posted: Sat Apr 25, 2009 2:09 pm
by gfb107
The Robman wrote:Just FYI, when I create upgrades that use protocols that I've written myself, I always use $01FF as the protocol id, which is not an official protocol id so it's not in any remote.
So it might be a good for RM to default the PID for Manual Settings to 01 FF?
If I'm creating a Manual Settings upgrade that uses an official protocol, but it's one that's not supported yet, I use the official protocol id.
OK
My suggestion would be that when RM is used to open such an upgrade, it should check to see if the remote already has this executor installed. If the supplied protocol code matches the code in protocols.ini, a protocol upgrade should not be presented.
Note sure I follow. You are talking here about Manual Settings with PID other than 01 FF, right? And the RDF for the remote has the PID listed in the protocols section, but there is no entry for it in protocols.ini? I would expect, but I haven't verified, that RM would not require a protocol upgrade in that case. Sounds like that isn't happening. Do you have an RM file I can use to debug?

Posted: Sun Apr 26, 2009 12:23 am
by The Robman
I'm suggesting that if protocols.ini does have the protocol code for the processor that the remote uses, and it matches the one provided in the manual upgrade, it should not present a protocol upgrade. But, if the protocol code is different, it should present an upgrade.

Posted: Sun Apr 26, 2009 8:36 pm
by gfb107
I think RM v1.92 handles this better. Please give it a try.