TunerPro User Forum

https://www.youtube.com/results?search_query=tunerpro

Here's some notes from the code. I really need to open-source the ELM327 plug-in. It's incomplete and could use some love and attention from a developer with more time than I have, at this point. // Expected command format: // Mode + PID (1 or 2 byte) + expected reply size (1, 2, etc) + Reply count ...

Hey Mark,

No, that's not possible today. You'll have to stick with the copy/paste scheme you're using for now.

Sorry.

-Mark

I haven't seen one.

I've got a half-assed implementation of a CSV importer, which is incomplete, and my intent is to finish that and an exporter to enable easier and portable editing outside of the UI. Alas, responsibilities in other areas of life have taken priority.

I can't think of what could possibly affect that. When entering the edit mode, the data is already parsed and loaded, so there's not a lot happening on the TunerPro side.

Has your OS been updated lately?

New build is now available at www.tunerpro.net/downloadapp.htm

I've finally been able to reproduce this and fix it. I'll be posting a new build that fixes this soon.

After creating your lookup table, in an ADX Value, click on the conversion tab. You'll see a check box labeled "Send converted data to lookup table." Select that, and then select your lookup table from the drop list labeled "Lookup table."

A bin file is a bin file. A bin definition is an XDF, and an acquisition definition is either an ADS (older format) or ADX (newer format).

what happens when you drag and drop the individual bin file? what error do you get? Does the title bar show that the bin opened? Then try the XDF. What error?

After downloading, make sure the file extension matches what you expect, and not (for instance) .html. If you downloaded an XDF, make sure the file extension is .xdf. If you downloaded an ADS, change it to ADS. Then drag and drop the file into TunerPro.

Unfortunately, no, this isn't possible to do.

All great suggestions, some of which won't be too hard. I'll try to keep these in mind for the next time I dig in for the next release.

Do you have more than one PC to try this on? Many of the things you describe sound like some synchronization issues (bugs, as you say), but perhaps based around the rendering and/or memory performance of the host PC. I'm not sure I'll be able to untangle this issue for you in the near term. You migh...

What's an idx file?

Are you sure the emulation header is properly socketed in the ZIF in the ECM? Also, it's a good idea to disable the checksum if you haven't already. Do this by changing the mask ID byte (stock is either 0x32 or 0x6E for the '165) to 0xAA.

Loosely, something like this: 0. Attach Ostrich to ECM/vehicle 1. Attach Ostrich to PC 2. Start TunerPro RT 3. Load BIN file 4. Load XDF file 5. Click the blue up arrow in the toolbar to upload the bin to the Ostrich 6. verify bin via toolbar button. Now you can key on the vehicle 7. To make increme...

Thanks for the report. TunerPro itself shouldn't rely on anything but the VS2017 runtime, but I'll verify and fix any references to older libraries.

You should also be sure that third-party plug-ins aren't the culprit, as they may require older runtimes.

Thanks for the report. I made some changes here several versions ago, and must have broken it. Will investigate.

This is fixed in the latest version, which you'll have to download from the link Matrix mentioned. Once you're on that version, you should see the version check succeed again.

Sorry for the confusion.

I've removed these DLLs from the installer for future versions, so this should no longer be an issue with the next release.

Thanks.

You won't run into other errors if you leave it as is. In general, what runs in Win7 runs fine in Win10.

Try deleting all of the DLL files in my documents/TunerPro files/ plug-ins.

Sounds like some plug-in component you're using requires the VS2013 runtime, but it's not installed on one of your machines. The latest builds of TunerPro and TunerPro RT were built with VS2017, so it wouldn't be a core component causing this (hence your ability to run after you click through the er...

The blank listview is another known issue, probably with the same underlying cause (bugs in the Microsoft C runtime).

I'll be rolling another build soon in hopes to address this, and I'll post it here for y'all to try ahead of general availability.

Thanks for trying. I don't know how to tackle this at the moment. Hopefully I can find a local machine that reproduces this.

Please help me out by installing this: https://aka.ms/vs/15/release/VC_redist.x86.exe

Then run windows update, take any missing updates, reboot, and try to repro.

None of my machines repro it with files sent from other reporting parties. I suspect it has to do with different versions of the CRT being installed on different machines. I'm still trying to figure out how to fix this.

What does "not functioning" mean? Are you not seeing any data/text at all in the data lists? Could it be the issue described here?
http://forum.tunerpro.net/viewtopic.php?t=4529

Why not define a scalar for exactly this purpose?

''88 uses the $32B defintiions. For data logging, you can use the 1227165_6E.ads/ADX. You can also upload and use a $6E tune and use the full 6E definitions, but you'll need to unplug the cold start injector when doing so.

Sorry about that. The feature is only partially implemented, with no documentation (obviously). I mean to get back to work on it, and to post some minimal documentation. One day soon.

Thanks Dex.

Undo is also there, but on a per-editor basis. If you close the editor (e.g. a table editor), then the undo history is reset.

Thanks for pinging me about this. I can't reproduce it on the machine I'm now, but will try a few others.

The latest version now requires the Visual Studio 2017 redist. The TunerPro installer should automatically install it, but some folks still seem to be seeing issues. You can manually download and install it from here: https://go.microsoft.com/fwlink/?LinkId=746572 Then run Windows Update, reboot, an...

The settings files are written to your documents\tunerpro files\ folder. Perhaps something on your computer is preventing TunerPro from accessing that.

You shouldn't need to, but try running TunerPro as an administratore (right-click on the shortcut, select "run as administrator").

Pretty much any USB based OBDI GM ALDL cable should work. Moates.net makes the ALDU1 for this purpose. There are others out there as well.

Actually looking at the ECM should yield the part number for the ECM. Looking at the chip or memcal should yield the BCC code. Those two things combined, along with what engine is in it, should give you the info you need to determine the definitions to use.

You'd have to reach out to whomever wrote the checksum plug-in. They would have implemented their licensing logic on their own.

No, it doesn't require a license. You'll need to set the interface type to "AutoProm/MAFTPro" on the data acquisition tab of preferences. Then you'll need to load the definition (ADS or ADX file) provided by the MAFTPro folks to enable logging.

-Mark

I've made no changes to XDFs in between. The major change was moving to a new compiler, and ultimately a new C runtime.

Maybe try running windows update to make sure your PC has the llatest runtime installed?

I'm grasping at straws; I have no explanation for why it would work on mine and not yours.

Is there any way to generate a log file of the crash? Not unless you have Visual Studio installed, and can attach and generate a crash dump. Are your settings the same between the two machines (win7/win10)? I can load both XDFs, here. What happens if you load it on the Win7 machine, save it out in ...

Can you please email me a bin? Does it crash if you don't have a bin loaded?

Aside from that, you're using exactly the same setup I am, and I cannot repro.

We'll need more info to be helpful.

What vehicle? What definitions?

What do you see when you test for valid cable? Do you have your COM port set to match the one your cable uses in preferences?

Are you using the latest build? I can load it without issue. What language/locale is your PC set to?

This is an intentional feature in the XDF, according to its author.

The issue described here has nothing to do with loading XDFs. If you see a crash loading an XDF, best to email me the files I need and instructions to reproduce the issue. Regarding the original issue (crashing when entering the custom tools configuration), I haven't been able to reproduce this, but...

If you have a 1227165 ECM, I recommend using a 6E tune, then use 8192 baud. Unplug the cold start injector, since it isn't used in the 6E mask.

With that, you only need the 10k while connecting to t he 8192 baud stream. Once you start getting data, you can remove the 10k.

After you connect, you can disconnect the 10K. That'll help the running issue when the cable is connected. Also, for some masks, there is a spark adder in ALDL mode. In $6E, I zero this value out. I'm not sure if this exists in the $32 mask. It'll have to be a point of research for the reader. =) MA...

Correct. Install this one, specifically:

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

You may also need to check for Windows updates after you install the above.

I'll fix this issue in the next release.

TunerPro User Forum

Search found 1925 matches

Re: DOWNLOADING BIN FILES

Re: ADX file ELM setup (Hex cmd String)

Re: Import data from excel to tunerpro.

Re: XDF To CSV Exporter

Re: Slow opening "Edit parameter XDF info"

Re: Missing data in List view

Re: Missing data in List view

Re: lookup tables

Re: DOWNLOADING BIN FILES

Re: DOWNLOADING BIN FILES

Re: DOWNLOADING BIN FILES