TunerPro User Forum

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!

The request is on my radar, thanks!

Thanks for the suggestion. Apologies for the delay in acknowledging. Note that you could add a "Favorites" category and assign items to that category. One challenge here is that favorites would likely be saved with the XDF, but your favorites may not be everyone's favorites.

Thanks for the suggestion. This has been on my long list of things to add.

Thanks for the suggestion!

Thanks for the suggestion. Sorry for the late acknowledgment.

Thanks for the suggestion. Seems like a rare need, for which you have a solution. At the point where you're entering conversions for each cell, it's not much extra in overhead to simply create a table to link. The next build will allow you to double click an axis value to open up a linked table for ...

Thanks for the suggestion.

That's a reasonable suggestion. I don't get the impression that visibility levels are widely used.

Thanks! I used to have a "legend" window for tables that showed axis units, but it was rarely used. Will consider something for the future.

It's a good suggestion. Meanwhile, you can view bytes as binary in the hex editor (Ctrl + H)

Direct axis editing will be in the next build, along with sync groups (data linking, as I think you're calling it - e.g. keeping per-cylinder tables that you want to have identical values in sync).

Thanks. I'll fix this. Meanwhile, you can assign whatever shortcut(s) you want in the preferences->Keyboard tab.

Does it do this after selecting the XDF? If so, does it happen when you select a different XDF? If so, send me the problematic XDF.

Because it's a bug. It's fixed in the latest build.

This should be resolved in the latest build. The issue came up as a result of adding auto-coloring of table cells. I've since optimized the behavior.

This was fixed in 9503.

Hello. Thanks for reporting this. Please email me the XDF and the list of steps to reproduce and I'll get it fixed.

What OS are you running? Sounds like the VS2019 runtime isn't installed correctly. This gets installed automatically during TunerPro install, but I've heard of instances of it not working on earlier OS's (like Win7).

Acknowledging. We're working on this in email. Win7 should work, but it sounds like the VS2019 runtime isn't installing correctly on your Win7 instance.

Hi Rich,

I'm just acknowledging your report and confirming that we're working on this via email.

-M

Alright. Please email me the XDF and a bin file. I'll take a look.

I hear you guys on the quick ability to edit axis definitions. It's on the short list.

how many rows and columns? multiply those together, multiply that result by 2 (since each is 2 bytes), and add it to the base address. If the result is the same as or larger than the bin size, then the error message is correct.

Thanks. I'll investigate and fix what i find.

You can nuke the settings and start over by closing TunerPro, deleting the .dat files in "documents\tunerpro files\" folder, then restart TunerPro.

Thanks. Fixed in the next build. This only affects XDFs with a base offset set.

I've fixed the originally-reported issue (categories over 255 not being saved correctly) for the next build. Thanks!

Although it's installed with the TunerPro installer, some systems might fail this step, so you should try installing the Visual Studio 2017 redistributable manually. Here's the link: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads If you're running a 32-bit O...

Thanks for the report. I'll investigate and fix.

See the "Dock/Undock" and "Floating Utility Tabs" options in the view menu. If all else fails, reset your settings by deleting the three ".dat" files in the "Documents\TunerPro Files\" directory.

-M

Haven't been able to reliably reproduce it.

Search found 1925 matches