TURN MXD FILE INTO WEBMAP CODE
TURN MXD FILE INTO WEBMAP DOWNLOAD

From my looking and testing there are two entries for each device and one 'points' to the other, probably an index or an offset as you point out.

Spent about a 2 hour block working on it before I simply ran out of time and have never gotten back to it since. Good work! When I got my remote I opend one of the files in UltaEdit-32 and poked around at trying to determine if I could figure out what the structures were for the file so I could do this. But have no CCF file for that remote from which to make any comparisons. I see a similar oddity with IR codes learned from a Channel Master antenna rotator remote control, with a couple additional variations in IR bursts, as opposed to just 2 or 3.

TURN MXD FILE INTO WEBMAP CODE

I also suspect there's a clock multipler value stored somplace that would make all this match up with the values that would be obtained doing the same with the CCF version of the code and the preamble portion where the clock multiplier is specified. I haven't yet spent much time trying to determine how it's indexed but it seems to hold some promise based on the actual values there. It appears to exist just prior to the first learned code.

I'm beginning to suspect that there's a lookup table in the MXD file that these individual bytes are referencing for the actual IR burst timing. Simply reviewing both files for each version of the same code will let you determine how the conversion needs to be done, then you can convert any other codes found in a CCF file and use a hex editor to modify the MXD file. Maybe at some point I can figure enough of the MXD file format out to create a program to do this more simply, but at least there is a way to get created discrete codes into the device without having to use a different remote.Ģ20120101220120120Which matches the CCF file version exactly. If you look closer at the MXD file, you'll also see the bytes immediately prior to the learned code identify the number of bytes, and a few prior to that identifies a unique ID for the learned code which corresponds to the label you'll see elsewhere in the MXD. The actual numbers and sequences of characters do change with different devices, and so far I've found one device - a Zenith HD-SAT520, that seems to defy figuring out using this method, but I'm still working on it - but the concept remains very similar in most cases. I was able to add all the discrete codes for aspect ratio changes and power on/off for the Fujitsu this way, one at a time, by learning the POWER TOGGLE code, exporting the device, changing that code with the hex editor, and reimporting the device and then learning the POWER TOGGLE code again on the next button, et.

TURN MXD FILE INTO WEBMAP DOWNLOAD

Save those changes and in MXEditor import the updated device file back over the original device and download to the MX-700 remote, and now that learned code functions as POWER ON instead of POWER TOGGLE.īy starting with a known learned code, you can find it using a search in a hex editor, so you know which to update. The second to the last grouping becomes 'TUUU'. I had some discrete codes I needed to create and no way to do so with just the MX-700, but did find a simple way to do it after reviewing the MXD file in a hex editor. Because the data stored varies a bit between devices, this can only be an example, but it shows the general process. Here's the steps using a specific example. I'd been playing around this weekend a bit and figured some of the innards out so I could manually create discrete codes without using another IR/remote product. I recently returned a Harmony SST-768 and bought a Home Theater Master MX-700. I was just going to post this on, but their server is having a bit of a problem posting messages right now and won't let me do anything but read, so I thought I'd post it here in the meantime, just to get it out of my system.

Turn mxd file into webmap