TunerPro User Forum

I've finally been able to figure this out. It will be fixed in the next release.

Glad to hear it. Thanks for checking.

Moved topic. This is not a bug.

You need to find the appropriate XDF for your bin on the Internet. Then open the XDF via the XDF menu, and open the bin via the bin menu.

For a scalar, you need to use the "Z" attributes, e.g. ZOffsetInt, ZSigned, ZUnits, ZLSBFirst, etc.

I really need to document that importer. =(

This (drag and drop, copy and paste in category view) is in the next release, coming soon.

Thanks for the info. I'll try to add additional logging to the next build to see if we can figure out the cause. Saltwater, are you running Windows 7 as well?

Close TunerPro, delete the settings.dat files in your documents\tunerpro files\ folder, then re-open TunerPro and reload your files.

Cool idea. Thanks!

I've heard of a couple of reports of this and have had XDL/ADX files sent, but I have yet to be able to reproduce it. My assumption is that this is related to the paths to the files, since that is the main area of code change between the working and non-working version. Can you tell me what the full...

No, TunerPro is not a comprehensive scanner, and the ELM327-based OBDII plug-in has only basic/minimal PID support.

Noted, thanks!

Fixed for the next release. In the meantime, for the values you specify, this will work if you turn it into a signed value.

Will look into this. Thanks!

See my previous post.

Also, the fix has been released.

I'm looking into this. Will fix what I find for the next build (to be released sooner rather than later, due to a couple of other issues).

Not a bug. Perhaps you still want to patch the bin in the indeterminate condition. Thanks for the suggestion. Do you actually have a case that you could describe where this would be necessary?

Email me the ADX and XDL file (zipped, if possible) and tell me how to repro this.

What is the full directory path to your documents\tunerpro files\ folder? (e.g. c:\users\p4ndiamond\documents\tunerpro files\)

aaronc7 wrote: ↑Sat May 06, 2023 6:11 am I don't know if this was ever fixed, but it's still rolling over for me past 255, in the latest version. I can send over the XDF I'm using if that helps.

Thanks for sending more details. Fixed for next build.

Sure. Send me your XDF and the specific details to reproduce the issue. The max number of categories is currently 1024, and I haven't yet spotted any related issues.

Thanks!

Reasonable request. Thanks!

You'd need this for Win x64.

https://www.ftdichip.com/Drivers/CDM/CD ... tified.zip

If you still can't get it working, check that there's a virtual COM port in device manager when the hardware is plugged in.

https://ftdichip.com/drivers/vcp-drivers/

Reasonable idea. Thanks!

The "Initialize Hardware" is for emulation hardware, not logging cables.

Sounds like you've configured your cable correctly, per the results of "test for valid interface".

Now you simply need to find the proper ADX and start logging.

Great suggestions, thanks. I've got a long list of improvements that I'd like to make to the hex editor, including these. Hopefully some day soon!

I can reproduce this, thanks. Fixed for the next build.

I'll look into it. Sounds like Sheets uses a different clipboard formatting.

Thanks. This is fixed for the next release, which I'll put out later this week.

Thanks! Will take a look and fix what I find. Also, regarding the button, I forgot to rename it to "Compare mode", which I'll do. The idea is that you click that button to change the compare mode. One button enables compare, the other allows you to change the mode. The mode is remembered, ...

No idea why this would be. Shot in the dark: with TunerPro closed, delete the .dat files in documents\tunerpro files\. Then try opening.

This is fixed for the next build, along with the issue in the other thread, as a result of the same change.

I've gone through all of the changes related to hardware detection between 9209 and the latest, and I don't see any change that would obviously cause this. I did add support for a couple of new pieces of hardware (meaning adding new checks of 3rd byte in the hardware version response). It sounds lik...

When nothing is attached to your Toughbook, how many COM ports show up in device manager?

When you go back to an earlier build of TunerPro, does it work again?

Hit Ctrl + Alt + Shift + D to open the debug window, then hit the connect button and show me what you see for a failure.

I see why I couldn't reproduce this - it only affects tables that don't use internally defined axes. Of course I was trying to make it happen with tables that have internally defined axes.

Fixed for the next build. Thanks!

Can you outline what steps you're taking to reproduce this? I still haven't been able to make it happen, strangely.

Thanks for the feedback. Ctrl + Shift + S should do it. You can reassign this in preferences.

The selected cell address is already shown in the toolbar. Seems like that could be used for lookup up the table/location in the hac/source.

This seems to be working in the latest build.

Thanks. I haven't been able to reproduce this. I'm not sure how it would work differently per machine, or even per XDF. Do you see this with more than one XDF? Perhaps you could email me the XDF and the two bins?

Can you email me the XDF that shows this issue?

Thanks! Will add it to the list.

This works fine for me. I'm not sure what to suggest, other than to try it in the next release. =(

Can you send me ADX and XDL (log) files with instructions on how to reproduce some of these issues (example: the playback speed issue)?

Without the MAFTPro connected, do you see any com ports in device manager?

I wonder if there's another device attached as a COM port.

The data logging plug-in for TunerPro was built for generic serial logging. You could certainly create an ADX to communicate with whatever serial protocol you implement on the Arduino.

I believe it's under the "Tools" tab. I haven't looked at TPRT in a couple months. That was it, found it. Thanks! Kind of silly that it's buried in a menu rather than just be able to launch another copy, but now that I know where it is, no big deal. It's this way because launching multipl...

Where are you seeing others having communication issues? I don't believe I've touched any code at all that would cause the issue you're reporting below, but I'll take a closer look.

I'll have to look back through my logs. That's a previously-known issue that I thought was fixed. I'll take a look.

I like the idea. Thanks!

Search found 1906 matches