TunerPro User Forum

Same issue here, I've tried a few different ADX files that have always worked, but getting blank list view (all other views are fine). One thing I noticed - if you scroll the list up or down quickly, a black/green/red dot briefly appears where the data should be. I tried removing TunerProSettings.da...

I don't believe there are any plans to publish the XDL format, but regardless of whether or not it remains the primary log format used by Tuner Pro I think it's safe to assume it will continue to be supported in it's current form for the foreseeable future.

I've had a very quick look at the code, and I think the MAF maps might be at 0xB100 (256x1) and 0xB000 (256x1). These values are read during the ADC interrupt routine and then used as factors in a multiplication function, it's certainly not a temperature sensor calculation so guess it's probably the...

The problem with doing it that way is that an hour long log would then take an hour to transfer to TP :cry: The XDL format is pretty much just a timestamp plus the data returned by the ECU anyway - if you compare a hex dump of an xdl file with it's csv export, you should be able to spot the record s...

Sounds like a checksum issue - once the ECU is running you can make changes, but on next startup the checksum fails unless you revert to an original bin.

I've done a bit more work on the xdf here - set the xdf view to 'parameter category'.
Use at your own risk etc, I've tried to work out the most important maps but some are little more than an educated guess.

Try this: <XDFTABLE uniqueid="0xC0CA" flags="0x0"> <title>0xC0CA 12x6 RPM Load </title> <CATEGORYMEM index="0" category="1" /> <XDFAXIS id="x" uniqueid="0x0"> <EMBEDDEDDATA mmedelementsizebits="8" mmedmajorstridebits="-32&quo...

I imagine the only concern would if the .XDL format changes in future Tunerpro revisions, it might breaking outside software. Exactly correct. I can share the details with you, but I'm about 90% of the way done with replacing the entire logging system with a new, custom database-like implementation...

The RT version is required - it's an RT plug-in. When it's used with a specially modified Motronic ECU and bin file, it can do real-time ECU tuning - not just download bins. That information you found looks like a good start - it shows the location of the maps, their size and axis contents (assuming...

I can trigger this by switching to the item list view if I moved the time range slider on the Monitor window prior to switching views. Moving the slider doesn't immediately cause a problem by itself though. And it's not just high CPU, TP immediately becomes unresponsive and doesn't recover. Problem ...

That would explain it!

Edit - 8202 looks great, thanks

Playing back logs in the latest Tuner Pro RT build seems to hog the CPU, consuming 100% of a core for the duration of playback.
I've tried multiple logs created with different ADXs and it's the same with all of them.

Win7 x64 dual core, Tuner Pro RT build 5.00.8200.00

Is it just me?...

You should be able to read the bin off that ECU using a $10 KKL cable and this motronic plug-in for tuner pro RT I've been working on. I think it's been tested on a volvo M1.8 ECU already. The bin download can take anywhere from 10-30 minutes. If you get the bin downloaded, I can make a very basic x...

Fitting the TS engine would avoid most of the potential problems with using the M1.7, and the immobilizer can be disabled if you don't want to fit the code box etc. If you really wanted to FI your original 1.6 engine though, an older Alfa Motronic ECU like the 0.261.200.124 from a 75 1.6/1.8 IE woul...

The M1.7 wouldn't be the easiest ECU to do this with, but it's certainly possible. I've been working on the Alfa Motronic ECUs for a while now and although I've got a basic XDF together for the 155 TS's main tables of interest, I haven't even started working on things like DTC masking etc for this E...

Thanks - the new build looks great.

close - but not quite ;) Yes I get a context menu now, but if you left-click on one table to select it then right-click on a different table, you get the context menu for the first table and not the one you right-clicked on. You can see the second table highlited while you click, but release the but...

Glad to hear it wasn't just a case of user error

I'm guessing that the 357 990 refers to the chip code - I don't have that bin, but I do have 1.267.358.299 which is a Calibra 2.5 bin for the 0.261.203.080 ECU. PM me your email address if you'd lke a copy. Or, you should be able to read the bin out via the diagnostics port. It's slow, but saves pul...

Ok, this is a laptop running win7 64 bit. Display 1 is the laptop's screen, display 2 is an LCD monitor hooked up to the laptop's docking station. Display 1 is the primary display (with taskbar etc), display 2 is the extended desktop but it's extended to the left (not to the right like normal setups...

I've seen this a few times too.
The monitor window is blank, but the data list shows correctly.

I've been having a strange issue with the latest TP5 RT (5.00.8075.00). I have dual monitors on my win7 pc, and when TP is on the main monitor everything is fine, but if I drag it to the second screen none of the right-click context menus show anymore. Drag it back to the main screen and they appear...

The help file is compiled HTML, so it will be windows/IE's security settings blocking it.
I can't remember exactly what I did to stop that, it's something like right-click on the .chm file, select properties, and click "unblock" on the General tab...

Old Motronic ECU, no emulator hardware.

For ECUs with really inefficient serial protocols and/or slow baud rates, downloading the whole bin via an emulator plugin takes a very long time. In some situations the emulator component could speed this up by only reading a predefined region of the bin that contains the cal and padding out the re...