Hi all, I managed to create a .hex file with Make hex and even downloaded ProntEdit 4.0. But now I am stuck. My ultimate goal is to get discretes for my PT AE 1000 PJ onto my MX 850, but maybe I am going about this the wrong way ? There is a thread in the "Discrete Hunter" forum where hex codes for discrete on and off were posted, what do I do now ?? Thanks.

PS: I should mention my MX Editor does NOT have the hex editor [ or the live update feature ] - maybe it would be easiest if I had this feature ???

.

Actually you can use the Universal browser to open pronto .ccf files.

This was the method that was used to import pronto hex before URC added the hex button to the universal browser.

Open the universal browser, click on the file folder icon, and open a .ccf file. You will then see a tree view of all the pages in the .ccf. Navigate to the button which has the code you want to import. Select the button and drag to the button on the remote you wish to program. Note that this will only work with pronto hex codes which are learned codes. If the code you are trying to import is not a learned code, when you drag the button the cursor will change to a circle with a diagonal line through it.

Also, I seem to remember that prior to opening the .ccf file in the universal browser, you need to open it in Prontoedit and open windows for all the pages you wish to access with the universal browser. After opening the windows in prontoedit save the file. For some reason the Universal browser is unable to access pages in .ccf files unless the window for the page is already open.

In case you don't know how to make a Pronto CCF, here's the procedure:

1. Open ProntoEdit and choose "Create New Configuration" for a TSU2000.

2. Under the "Panel" pulldown, choose "Add Panel".

3. Some blank buttons will appear. Double click on one of them to get the "Button Properties" screen.

4. Click on "Set IR" which will bring up the "Add IR" panel.

5. Click on "View IR", which will display an open box labeled "IR Code".

6. Paste your hex code into that box and click "OK".

7. Click on "Properties" and "Name" to enter a label for the button. Click "OK", then "Apply".

8. Repeat this with any other buttons, then save the CCF.

Mike

Damn! I totally forgot about that, it's been a long time since I've needed to use that...thanks for the reminder guys! Guess that makes my post completely useless :-)

DELETED

a-ha !!! the above should be a sticky for poor souls like me !!!

this is the info i need !! many thks to Snarf and Mike.

PS: Mike, i bought an MX 700 from you before, only reason i could not buy from you again, is that you don't ship to Canada :(. SO had to buy from Bluedo, it was not good....

I just learned a few more details.

You can go to the button editor at any time to add labels.

If you need separate composite and component buttons, label them. I labeled them CMPNT and CMPOS. The MX850 editor changed each to COMPO when I dragged a command to it, so I went back and corrected each.

Well, not exactly. I haven't been able to try the remote yet, but I learned the codes for the TV, used software to determine what manufacturer protocol and device they were, generated hex codes, then copied and pasted these into a ccf. The MX850 editor accepted all of them as though they were learned codes.

I don't know what this means. But since I had just created the ccf by copying and pasting into ProntoEdit, I had just opened all the relevant windows. By "opened," maybe it's meant that they can't be hidden, or the device can't be a template.

It means that you need to double click on the device page in the tree view on the left hand side of the prontoedit editor window. This will open the device page which will display on the right hand side of the prontoedit window. This opened page will display all of the buttons/codes for that particular device. Then save the .ccf file.

It's been my experience that if the page for a device has not been opened by prontoedit, the URC universal browser cannot open the device pages in a .ccf file. It has been a while since I've tried this, so it is possible that newer versions of the universal browser may not have this limitation.