Rant about 2.25 Scanner

[schpenxel]

So I got a few graphs going. The throttle position vs. speed works.
All the others, (spark advance, retard, trims etc. run for 11 seconds and quit. Tried it several times. All the graphs quit after logging a few seconds except the throttle one. Any idea on that?
Charts do the same thing. Run for a few seconds and quit. The numbers are still scrolling across the chart screen on the bottom, but the data quits streaming.

I had the same thing happen a while back. Uninstalling/reinstalling latest version and restarting everything got rid of it for whatever reason. I never figured out why it was happening

[LEDbetter]

I just tried out the latest version and I admit that I spoke too soon. The latest updates are a just what I've been looking for! Thank you for keeping on top of things HP Tuners!

[Andy@A&A]

I completely uninstalled and reinstalled 2.24 and 2.25 yesterday. This is just weird.

[schpenxel]

True.. I haven't had that problem in a few weeks so I'm not really sure what's going on. I logged for an hour or so this morning on 2.25 and all went fine

[Andy@A&A]

It started scanning graphs and charts for some unknown reason. It wouldn't do it yesterday and now it does.
The next hurdle seems to be the wideband. Keith says it works but I can't see where I can get my PLX to work with 2.25.
I had Josh look at it for a while. He's pretty good at this stuff but he couldn't figure it out either.
Does anyone have some input on what to do?

[schpenxel]

Right click in the Channels window, add channel. Go down to external inputs, MPVI Pro, double click MPVI A/D Input 1 (or whatever one you are using). That adds input 1 to the channels window (you can close the "channel selector" window that popped up for this step)

Now there should be a channel listed as MPVI 1 in the channel window. Now right click on that channel, hit transform. Find your wideband in AFR or Lambda, double click whichever one you're using and that should now show up in channels and be usable in charts, etc.

That should do it.

[Andy@A&A]

Right click in the Channels window, add channel. Go down to external inputs, MPVI Pro, double click MPVI A/D Input 1 (or whatever one you are using). That adds input 1 to the channels window (you can close the "channel selector" window that popped up for this step)

Now there should be a channel listed as MPVI 1 in the channel window. Now right click on that channel, hit transform. Find your wideband in AFR or Lambda, double click whichever one you're using and that should now show up in channels and be usable in charts, etc.

That should do it.

Thanks. I appreciate the help. Josh got the wideband going but now we hit another wall.
We don't see a way to make a user defined channel so we can make a MAF Hz. / AFR error graph.
When you click on "user defined" nothing comes up. Are we going about this the wrong way?

[schpenxel]

User defined variables don't work yet, so you're not missing anything.

What I've done is created two histograms.. One with commanded afr/lambda then one with wideband afr/lambda. Then you can at least flip between the two and see where differences are. Not ideal but should work.

[Andy@A&A]

User defined variables don't work yet, so you're not missing anything.

What I've done is created two histograms.. One with commanded afr/lambda then one with wideband afr/lambda. Then you can at least flip between the two and see where differences are. Not ideal but should work.

Seriously. Thanks a lot. You're going above and beyond.
This is a prime example of why we shouldn't be forced to use this until it actually works.
I think I may have enough to get it on the dyno tomorrow if I have time. I put a 3.6 pulley on it because it was pretty much out of control with the 2.85. :-)

[Keith@HPTuners]

Andy, I understand your frustrations.

Continued development on 2.24 pushed 2.26 back, so at some point we need to say that we're 100% committed to getting 2.26 completed, which is what we've done.

There's only a few features left to complete 2.26, math parameters being one of them.

The plus side is though, the math back end in 2.25 is 300% faster than 2.24's, and supports Slope() and Avg() functions over a user supplied time span.

All across the board, 2.25 editor and scanner are far more feature rich than its 2.24 counterpart. Speed/Efficiency has increased dramatically for both applications as well.

[schpenxel]

Seriously. Thanks a lot. You're going above and beyond.
This is a prime example of why we shouldn't be forced to use this until it actually works.
I think I may have enough to get it on the dyno tomorrow if I have time. I put a 3.6 pulley on it because it was pretty much out of control with the 2.85. :-)

No problem.

I bought an air filter from you the other day too! lol. Much nicer than what I had from the other guy.

Z06 with a YSI sounds nasty!

[schpenxel]

Andy, I understand your frustrations.

Continued development on 2.24 pushed 2.26 back, so at some point we need to say that we're 100% committed to getting 2.26 completed, which is what we've done.

There's only a few features left to complete 2.26, math parameters being one of them.

The plus side is though, the math back end in 2.25 is 300% faster than 2.24's, and supports Slope() and Avg() functions over a user supplied time span.

All across the board, 2.25 editor and scanner are far more feature rich than its 2.24 counterpart. Speed/Efficiency has increased dramatically for both applications as well.

No doubt 2.25 is way faster when dealing with a lot of data. Zoomed way out on a log from an E38 or newer 2.24 is quite slow. 2.25 doesn't seem to care how much data I'm looking at which is nice given the logging rates of the newer ECM's

Hopefully 2.26 puts a lot of the finishing touches on the "new" scanner.

[Andy@A&A]

No problem.

I bought an air filter from you the other day too! lol. Much nicer than what I had from the other guy.

Z06 with a YSI sounds nasty!

Haha.I got chastised on the CF for saying "the other guys" Someone took real offense to that.

[RonSSnova]

Myself, I'm now totally thrilled that we can log the wideband.
I built a histo for WB vs rpm and pressure ratio that mimics the dodge VE table and could finally see where I needed to make changes......in Diablo.....ugh!

I have noticed however that when I have the table show last data point, and I'm moving the cursor, table does not match the chart display.

[Keith@HPTuners]

The "last data point" view option for Graphs is only available during live scanning.

If you update your beta, it should grey out that icon when you have a log file open, or during playback, further showing that it is not a valid option during playback.

[RonSSnova]

That explains it. No issue. The chart view and cursor data is what I used.

[schpenxel]

Haha.I got chastised on the CF for saying "the other guys" Someone took real offense to that.

lol that doesn't even surprise me over there!

[MikeOD]

For the serial port logging, you plug the wideband controllers serial output directly into your PC.

Have you tested (or can you test) any specific USB to serial port adapters? I haven't had a PC with a com port in years. I'm happy to get an adapter...but I want to get one that I know will work.

[waynehartwig]

Have you tested (or can you test) any specific USB to serial port adapters? I haven't had a PC with a com port in years. I'm happy to get an adapter...but I want to get one that I know will work.

USB is technically a serial port. I could be wrong, but I assume when they say 'serial port', it will encompass the traditional 9pin as well as USB

[schpenxel]

Any USB to serial adapter should work. The serial output on widebands is more akin to an old com port style port, not USB. Of course a USB to serial converter can make a USB port work just fine, but ultimately it will just make it behave like an old school serial port.

I may try to get it going on mine this weekend, we'll see

One question though.. how does it know which port to use if you have multiple com ports on a computer?