TunerPro User Forum

8040, I guess time to upgrade.
Thanks.

Trying to update a single 8 bit value fails with "Upload failed". Data tracing on 8 bit maps results in "Error". For 8 bit it only works if you select to upload whole maps and select a map that is 16 bit aligned and has an even number of values. If it has an odd number of values ...

Thank you. I don't really care if they are editable by the UI or not, but the problem is if I assign names to them inside the XDF, then the names "stuck" for only the 100 ones. So 0-100 worked fine and then they were all named Category 101, Category 102, etc. I know that i defined them the...

Mark, could you consider adding a simple ASCII type or an ASCII() function to the conversion editor?

You thought it was a good idea six years go

Hello, Currently TunerPro has a category (folder) limit. Only the first 100 categories can have names assigned. And only 255 categories are supported altogether, with names not shown for the rest. Could this be increased? Perhaps a lot? I don't really mind if I can't change their names in the UI, bu...

Bump...

Would you consider implementing this? or can I do this already?
I am in the same boat.

I can use the hex editor, just a question of convenience really.

I know that TunerPro supports wiring two Ostrich emulators together to provide 16 bit emulation capability, but it does not support address tracing in a such mode.

Does TunerPro support address tracing on the Roadrunner emulator, which is a 16bit emulator from the get-go?

Then consider using Excel. Sure, that is not an issue at all. Don't take this wrong, I am not trying to whine or anything, just saying that if you want to change the axis parameters, then it is currently not really feasible to do so in TunerPro. I don't really mind, since I don't edit my XDF's by h...

Of course it changes the others - the whole point of this axis design is that it cascades. Each cell uses the preivous cell's values. Yes, but that makes it completely useless for editing. You don't want to change all axes usually - perhaps the 2-3 last ones. I am changing one value - I don't want ...

dfddfd2 wrote:You can pass -multiinstance as a command line parameter.

Dave

Doh.
It took me less time to find the place to patch in IDA than to find the parameter.

Epic fail on my part.

Thank you.

Am I missing something or how do you open multiple instances? When launching the second one, it always says that TunerPro RT is already running. However, it is possible to launch two instances... patch the check: Search for: 1C 00 75 44 6A 30 Replace with: 1C 00 EB 44 6A 30 And then you can open as ...

I finally got around to testing this.
It doesn't work properly.

I can make the axis values get calculated, but if I change one value all the other ones change as well.

I see why this is programmatically, but it makes the entire feature completely useless, so we're back at square 1.

Read both from the ECU and compare them?

1. Both MAF's have to be voltage, not frequency based.
2. If there is no MAF linearisation table in that ECU, you will need to either add one or create a circuit, which will be ADC -> uC -> DAC and convert voltage in the uC.

GL.

Yeah, that I know how to do. It will just be annoying to create tables for each axis, but since I generate the XDF anyway, I can do it programmatically. Why is it any more annoying than defining the axis for the table that it's part of? Need to change my XDF generator more :P Also, the point of cre...

Yeah, that I know how to do.
It will just be annoying to create tables for each axis, but since I generate the XDF anyway, I can do it programmatically.

Use per-cell equations. First cell is: (256 - THIS()) * 40 All other cells are CELL(INDEX() + 1) - (THIS() * 40) How do I use a per-cell equation for an axis? Do you mean that I have to create a table for each axis and then link that table as the label source? That works, but seems a bit cumbersome.

Build 5.00.7004.00

Crashes if I enter the following into the formula box (axis formula) and press OK:
SUM(1;2;3;4;5;6;7;8;9)+SUM(1;2;3;4;5;6;7;8;9)+SUM(1;2;3;4;5;6;7;8;9)+SUM(1;2;3;4;5;6;7;8;9)+SUM(1;2;3;4;5;6;7;8;9)

The following as well:
CELL(INDEX()-1;FALSE)

The math engine was updated, but every way that I come up with to do this in axis math crashes TunerPro. There just seems to be no way to reference the calculated value of the previous or the next cell. CELL(INDEX()+1;FALSE) or CELL(INDEX()-1;FALSE) both crash TunerPro. SUM() can not be given an add...

Because TunerPro uses XML, you can write (I did...) a program that will parse the map table and add all tables in the ECU with axis values to the XDF. You can even transform those axes...

Bumping this...
Could this be done? Pretty please?
I can make the adapter, it is easy, but because TunerPro is closed-source I really only have two options with the software:
1) Write my own
2) Hook TunerPro
Neither are very appealing...