TunerPro User Forum

The workspace itself should show its own scroll bar in these situations to allow you to scroll to the edges of the table editor itself. Your screenshots are cut off.

Thanks!

On the per-table basis, is reversing the order of row/col cells defined in the table (and/or adjusting step) insufficient? If there's a global setting for this and a per-table setting as you suggest, how should those be combined? If the global setting is set to reverse, and the table is set to rever...

Yes, this is on my list of things to do. Thanks!

Is it your intent to add your CSV importer to TunerPro? If so, I'd be happy to use your code as a reference to potentially add this functionality natively.

Yes, I agree, this has been on my list. Thanks!

Thanks! I'll take a look and fix what I find.

This should be fixed now, as of build 5.00.9786.00. Is it not?

They should fix their firmware, as I believe the fix on the TunerPro side wouldn't be fair to other manufacturers.

Can you please email me an example, so that I can fix this?

New build is now available. www.tunerpro.net/downloadApp.htm

Finally came across a repro (this also seems to be tied to the graphics configuration - my Win10 laptop on its own did not repro, but when I hooked it up to an external monitor, I could get it to repro). I have a fix for the next build, hopefully out in the next week or so. This seems to be a bug in...

Thank you. I'll look into the issue.

The hardware has to support address hit tracing, and in this case, has to implement the appropriate commands for it to be enabled.

This is Major Stride.

Ah, no, it's not corruption. It's a change in Windows that has exposed a bug either in TunerPro, or in the Windows control or runtime. As soon as I can get a repro, I can fix it. I'm taking opportunities to try it on machines that I have access to.

Sorry, I don't follow. What file? This isn't an issue with any of the files.

I'm not entirely surprised that this would be tied to OS or the runtime, which explains why not everyone is seeing it. I'm still unable to repro on every one of the 8+ machines I've tried it on.

Not yet. Out of curiosity, are you also a Reflex user? So far, the reports I've received are from those using the Motiv definitions. I'm guessing those definitions are exposing an underlying bug in my code.

Thanks for the info. This was difficult to work out last time, first because I couldn't repro, and then when I could, it was a pain to figure out the cause. Here's hoping I can find a way to reproduce this.

Will keep looking.

Thanks for reporting this. I'm not sure what the issue could be. I've tried to reproduce this on a couple of machines I have available to me and cannot. I'll peruse the code, my changes, and continue to try to figure out why this might be happening for you or your customer (I received an email with ...

I'm sorry, I don't understand the request. Processor access?

I don't believe that's coming from TunerPro, but I don't know what it would be coming from. Perhaps the XDF is loading a checksum plug-in that has a dependency? Perhaps something more nefarious like a virus? Sorry I can't help more directly.

When both are 0, the output should be 0%. I'll fix that case.

I would assert that this is the desired behavior. If the original value is 0, but the compare value is, say, 20, what is the percent difference? If the original value is 20, but the compare value is 0, what is the percent difference? Mathematically, they're infinity which has no meaning in percentag...

Where [0:2] means bits 0 through 2? That's a tidy solution.

I'll think about other ways to handle this. One way might be for me to add nibble support - for size, the option are currently 32, 16, 8 bit. I could add 4 bit upper nibble and 4 bit lower nibble. Something like that. It's really rare, though. Probably better to go for the flexible solution. I'll th...

This looks like it's probably a side effect of the way that I convert value entered in the editor back to the stored value. The algorithm isn't really designed with binary operators (and other situations, like multi-root equations), which is a problem in this case. What I've had on my list to do is ...

Thank you. I have fixed this and have uploaded a new build.

multibyte to wide string conversion flag and buffer issue. not sure why it only affected a few people.

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.

Search found 1936 matches