Appears to be fixed. Thanks!
Printable View
I spent some time messing with this. If I open the on screen keyboard and use the +/- keys on the "number pad" then the zooming works. When using the +/- (with and without shift) that are right after the number keys on the main part of the keyboard, it doesn't work.
I thought it was just a quirk of running HPT in VMWare but it appears that isn't the case
Zooming works fine in 2.24, for whatever that is worth
Oh, and I really like the left/right arrow keys scrolling and the control + left/right combo jumping by larger amounts.
I don't understand what it would filter?
averages the value over the last X ms. Makes the # smoother for users to read during a session.
Oh, got it
New beta up with user defined transforms (for inputs).
I really like the way this feature came out in 2.25 compared to how 2.24 does it.
In 2.25, you define your user defined transform, and that gets saved with your channel config. Your custom transform is specific to the specific input on the channels list.
You can open/save your transforms to build a library.
When you share your channel configs, or save them for a later date, they retain your custom transform. This should really help out users and tuners share channel configs with others, without also needing to share a specific custom transform.
Now, when you define your custom transform for a channel input, you must select the "target parameter". Essentially, what you're telling the scanner is how to convert the input to your desired unit, and what the result actually represents. You must pick a parameter from the list we provide you. This allows you to then "tie" to that parameter in gauge/graph/charts to plot it.
If you have a specific sensor/parameter/application that we don't have a well represented parameter in that list, let us know and we can add it.
Also, lets say you have an LC-1, but you have a voltage offset. Here's a quick way to take care of this.
Channels, Add Channel, select MPVI A/D Input 1
Right click on this channel in the Channels list, and click Transform
Expand Oxygen Sensors->Air/Fuel Ratio, Select Innovate - LC1 and click the Fx (down arrow) icon at the top
This preloads the LC-1 information, and sets it as your "target parameter".
Now all you need to do is adjust the scaling factors for your voltage offset.
Note that the Description field is only for your reference on this Transform Selector window. It is not used anywhere else in the software.
Nice. I'll have to give this a try this afternoon!
I have a slightly out of the ordinary case where I'm logging methanol system pressure. Any reason that wouldn't work?
I see how it works now. I like it.
If you could add a category for methanol pressure or something like that then that would be awesome. I just put it under a different category for now and it's working great. It's logging so much faster than 2.24. I used 150ms filter on the charts and that smooths things out a little bit
Yes, that looks good.... tomorrow morning will test it. thanks!
Keith,
Can you look at the LC1 Lambda output display value? When logging from the serial port I get a four or five digit number instead of something like 1.10 or 0.85 and the values don't look quite right. At first I thought it might just be an order of magnitude issue, but I'm not sure that's the case.
This is version .2636
http://www.hptuners.com/forum/attach...id=54754&stc=1
That one hadn't bothered me until today.. but today it bothered me a few times, so I'm also glad to see it being changed
I went through and setup most of the histograms I typically use (I know, I know, I'm going to call them that anyways) so I'm going to try to use it exclusively for a bit
It's quite usable now that the whole "transform" thing is working
The only thing that hasn't grown on me is the windows layout. In 2.24 I usually have windows on top of windows so I can see piece of different ones. Obviously there's no way to do that in 2.25. Hopefully I get used to it.
Oh--I got it to crash earlier when I was entering a formula for the whole transform thing. I'll try to reproduce it.. but I think it was when I hit a decimal or .0. I can't remember.. I sent in the error report though
Here it is. When I hit the decimal point it crashes.
Attachment 54770
Awesome.