TunerPro User Forum

Thanks Mark. I appreciate the quick response on this.

Jeff

Thanks Mark. Glad to hear it's not likely a bug as that should mean an easy fix. I double checked the math but that doesn't mean I didn't make the same mistake twice! The PROM I am emulating is for the very first GM TPI which was 4 kB (the only year for that size as far as I can tell). So I found an...

I have a bin in the middle of a stack that I am trying to tune. Under TP4 I created an XDF for the offset I needed and built the stacked BIN and could tune away with my Ostrich with no issues. Recently I upgraded to TP5 and I can load the XDF and the stacked BIN I created in TP4 without issue. I can...

Mark got things resolved. Turns out that the trick is to set the XDF bin size to be the size of the entire stack, not the size of each bin in the stack. In my case I had 16 32Kbit bins in a 512Kbit stack, so the bin size needed to be set to 0x10000 (64Kbyte). No changes were necessary to the origina...

Sorry, I only glanced through, but I think the desired outcome is to have a stacked bin, and be able to tune each bin in the stack individually. Yes. More specifically, I want to be able to RT tune a single bin in a stack. If so, here's a for-instance (using fake numbers). 4x 4KB tunes, stacked in ...

assuming you opened it as a normal BIN, then you would have to adjust checksum addressing as well. Yes I opened it as a normal BIN. The original XDF had these checksum settings: Data Start: 0002 Data End: 0FFF Store Address: 0000 I assume everything else stays the same anyway so I won't list those....

uhh...... someone with an emulator will have to help you at this point, because you just lost me. OK, hopefully someone can help with the emulation thing, but maybe you can help me get the file part right. I went ahead and created a stacked bin with two bins, one in position 0 (offset $F000 within ...

well, if you offset the BIN, then you MUST have it stacked correctly or you will get bad data in the XDF. Well, yes of course. But what is unclear is how the emulator is used vs. the saved file. If I open a saved file and upload to the emulator using 0xF000 as an offset in the XDF it works. So this...

1000 in hex does come out to 4096 in decimal. as a test, i would set the BIN size to $2000 and change the offset to $1000... i really can't understand why you're trying to offset it so far. unless your bank switcher will only work in 64KB increments. I tried making the changing you suggested and th...

in that case, yes your only option might be to have a different XDF specifically for that... you MAY need to adjust BIN size at the same time to get the crash to stop. OK. The BIN size is in the XDF currently 0x1000 which seems correct for a 32K bin. All the BIN files are of size 4096 bytes. What s...

robertisaar wrote:why exactly are you messing with the offset?

the BIN stacker and splitter does wonders.

I want to do RT tuning which, as far as I know, can only be done with an offset. Is there another way?

I have been using TunerPro RT (registered) with XDF ECM_1F for a while with no issues. Recently I built a bank switcher and now I need a new non-zero offset. I went into XDF->View/Edit XDF Header Info and changed the base offset from 0000 to F000, then saved the new XDF as a new name. However, whene...