The 27SF512 is a 64 KB chip. The BIN for your ECM is 16KB. So you should be BIN Stacking.
I've attached a modified version of the above BIN designed for a 64KB chip to this post.
If when pasting values it seems like they don't all change correctly, that sounds like the tables don't actually align between wherever you're copying them and where you're pasting them. Personally I do not like pasting tables in TunerPro for exactly this reason and would rather just type them out manually.
The 6E_expanded.xdf actually doesn't have limits set per se; the only limits it has are on the actual size of the data address. For example, if the data address is an 8-byte address, then you can only have data values of 0 to 255. What those data values translate to in "human readable" things like milliseconds or degrees or whatever depends on an equation included in the XDF (right-click on a parameter, click "Edit Parameter XDF Info," then at the bottom switch to the Conversion tab to see what equation is being used to convert raw ECM data to human-readable values). You should under no circumstances modify this equation unless you know for a fact that it is wrong. And even then you should double-check and triple-check to be absolutely certain. My recommendation is to leave the XDF well enough alone. If you're using the same one I am, it is not the culprit.
If by "turned red" you don't mean the text (which indicates that a value has been altered) but rather the background color of the cell, that color is useless and can be ignored. It's a reference color relative to other values in the table. It is perfectly normal to have a cell be "red" if it is intentionally a larger value than most everything else in the table (this happens a lot in transmission tables, for example).
Bookmarks