TunerPro User Forum

Dragging and dropping an ADS into the main window will automatically import it to ADX. You can then save the file yourself, or wait for TunerPro to prompt you to do so when you attempt to close the session. FWIW, on your '87, if it's running $32B, you can actually use the 1227165_6E.adx to get data ...

You'd think.

try A & K. Sounds like your K pin should actually be B.

Ini a generic sense, this is a great place to start: https://www.youtube.com/results?search_query=APU1 https://www.youtube.com/results?search_query=tunerpro More specifically, in order for the community to assist you, it will be helpful for you to include the year, make, model, and engine of your ve...

The redist should solve the problem, and it's run automatically when installing TunerPro. Perhaps the redist installation isn't successfully completing? When you install the redist by itself, does it fully complete successfully?

https://www.microsoft.com/en-us/downloa ... x?id=52685

Sounds like you did. There are two retailers through which you can register TunerPro. Myself (TunerPro.net) and Moates.net.

-M

Yes, cool idea. This is something I thought about when the APU1 came out, using the additional 3 channels of A/D for the same purpose. For your suggestion here, though, it would have to be behind another feature that's near the top of my current list, which is to enable the ability to log from multi...

Bin editing is not exposed to the plug-ins via any TunerPro interfaces. The emulation plug-in interface does expose read access to the memory being passed through to the emulator, though it won't serve the purpose you outline below. You could always crack the bin yourself (CreateFile/ReadFile/WriteF...

Thank you. I'll get this fixed.

It's there, now, at the end of the definition list under BMW.

I'll get the XDF posted to the site. Sorry for the delay, evilm3666.

What language/locale do you have windows set to?

I'm also running Win10 x64 pro on most of my machines and can't get it to happen. I'll ask around if others can repro.

Strange that I can't reproduce this on any of my machines.

In what path do you have TunerPro installed?

Can anyone else corroborate this issue?

The last segment is the one that is not fixed, and resizes based on window width. This is typical.

Tell me more about the hardware you have attached, there. I'm not familiar.

ECU files are bin definitions, like an XDF. This is why it works when you load it from the XDF import menu.

ECU files have nothing with data acquisition, which is why it fails when you try to import it through the data acq menu.

Sorry for the delay. I'm at the tail end of implementing a more "involved" feature that has me at an inconvenient point to spin a build.

I'll try to get something out in the next week.

there's a *.xdlcache file in your c:\users\all users\RusnaMark\ folder. Delete that and then re-open the ADX and XDL. See if that gets you running.

86-89 TPI Camaros, Firebirds, and Vettes used MAFs with the 1227165.

This is fixed for the next build. =)

OK, I can reproduce the issue now. I'm not sure this is something I can fix (again - the open file window is entirely controlled by Windows), but let me look around.

The data isn't directly exposed by the ECM. The best you can do is create a histogram with RPM on one axis and LV8/MAP on the other, and BLM in the Z axis. Then do some logging.

Fuel trim is stored in a course table that overlays the fuel table. One of the ALDL output values is "Fuel Trim Cell" (may be names slightly differently in each definition). This tells you what trim cell the vehicle is running in. The long term trim (BLM) value for that area of the table i...

Please Mangus, take another look in it, I have all PC's on windows 10 and all have it. You're telling me you have this issue on Win10? I run Win10 on all my machines and haven't hit this. Note that TunerPro uses a standard Windows API to bring up the file open dialog. Windows does all the work to d...

Drag and drop the TDF into TunerPro.

email me the changed XDF.

See the "Base offset" field in the XDF header (Ctrl + F2)

Not that I'm aware of. The plug-in as it stands today only works with COM-based interfaces (serial or VCP-based USB interfaces).

You're welcome and encouraged to write a plug-in to make it work. =)

It's unlikely to be the chip.

Check your ALDL wiring in the vehicle, and ensure that you're not in limp home mode (no check engine light, engine running reasonably). If the Snap-On doesn't connect, I don't expect that TunerPro will.

What ADS or ADX definition file are you using?

Very nice!

You can send updated XDFs to me, along with info on what was updated, and the source of the information used for the updates.

Select 32-bit floating point as the type, but note that you cannot have a conversion equation with 32-bit floating point yet. That's something I still need to implement.

Thanks. I'll look into these.

Can you email me the XDF, bin, and custom checksum plugin you're using? I'm unable to reproduce the issue with blank checksum plugin info when the last XDF is automatically loaded.

There are two different XDF formats - old and new. New is XML. Don't expect to view raw XML in your browser without the browser trying to render it like HTML (like you see in your third screenshot). Old format will probably work just fine in your browser (like your first screenshot). That's probably...

That's a bad practice on your part. The files are fine, as you can prove yourself by opening them in a plain text editor.

Right-click, save link as.

This is a screen shot of the link clicked directly - By the way a guy I was helping with an xdf spotted this, I just thought I woudl follow it up so its not just me ;) http://media2.turbosport.co.uk/2013/11/2016032822578657433Screen Shot 2016-03-28 at 21.57.35.png You're trying to view XML in a web...

Open them in a hex editor. Search for 0x0d 0x0a (newline and carriage return characters). Note that they exist.

Do the files fail to open in TunerPro?

Those screenshots look fine to me, clearly showing that lines are broken. Also, view them in your favorite hex editor and note that they clearly have line breaks.

I'm seeing line breaks (/r/l) in those files just fine.

Drag and drop it into the TunerPro window after dismissing the timer window. Or follow the steps in the email with your key.

Where did you get the file?

Please email me the XDF and the two bins with exact repro steps and I'll investigate and fix this.

I just chatted with Paul at Code59, and he's looking into fixing this.

Here's a great article on setting up TunerPro to datalog your Wideband. This one focuses more on the Ford side, but the concepts apply generically.

http://support.moates.net/logging-a-wid ... nerpro-rt/

both the O2 and MAF values while the car isn't running aren't particularly useful. You'll need to get the car running first before really exploring those values. The O2 should oscillate, centered around 500 mV, once the O2 is warmed up.

Can you run the stock tune?

1. ADX files are used by TunerPro to interpret live data from the vehicle or a device connected to the PC via USB or serial. The ADX is to the live data stream what the XDF is to the bin/calibration file. 2. In short, this is because you're truncating the numbers that come after the radix in the res...

Unfortunately, columns are not realizable in the current version.

Thanks for your suggestion!

This is a good idea, thank you.

TunerPro User Forum

Search found 1925 matches

Datalogging widebands in TunerPro