V3 Scanner External MPVI channels freezing

[dville_gt]

Having issues with the V3 scanner MPVI channels freezing after some period of time. Have to disconnect and reconnect to get the channel back online.

[Keith@HPTuners]

Another user reported this issue as well, and I'm working with him via support.

If you remove the MPVI Input Channel, it works fine right?

[jimbos'ss]

Mine is doing the same, I thought it was just my WB crapping out.

[Keith@HPTuners]

This is a known issue that we're looking into.

[gofastwclass]

Well darn. I've been trying to track this for ages but thought I was crazy or on my side.

[Keith@HPTuners]

You guys are only having scanning issues if you have an MPVI input in the channels display, correct?

If you remove the MPVI input from the channels display, it works ok right?

[gofastwclass]

You guys are only having scanning issues if you have an MPVI input in the channels display, correct?

If you remove the MPVI input from the channels display, it works ok right?

I thought I tried that but I honestly can't remember. I'll remove the input from my next log and let you know.

[gofastwclass]

I made several logs this evening after removing the MPVI input and the scanner never locked up. I created a few logs in the two to five minute range, a 20+ minute log and a 30+ minute log without a single problem.

[rao]

Same issue here...

[Keith@HPTuners]

This is a known bug.

We just put up VCM Suite 3.1.17 BETA to test, it might solve this issue. We need feedback. Please contact support and request access to the beta in regards to this bug.

If this solves the issue, we'll merge this fix into the 3.0 build.

[gofastwclass]

I did a 24 minute log with the wideband and no problems so far... I'll run a few longer logs and see what happens later this evening.

[gofastwclass]

Just got the opportunity to log an hour and a half without issue using the 3.1.22 beta.

[rao]

Great news, I look forward to the fix being folded into 3.0

[Keith@HPTuners]

Just got the opportunity to log an hour and a half without issue using the 3.1.22 beta.

So 3.0 doesn't work for you, but 3.1 BETA does?

Once again, we have received no feedback for the fix we've added to the beta.

[gofastwclass]

Well, darn. I spoke too soon. I just had a lockup at 3:47. I'll keep you posted.

UPDATE:

I sent an infolog to support. I also gave my name here and a link to this thread in case there is any question.

I just realized this lockup was different in that the application actually saved the file I recorded and didn't go unresponsive / 50% CPU as before. I simply closed the application, place the laptop on standby and went inside assuming the log didn't auto save.

My very next log was around 5 minutes and worked fine.

[Keith@HPTuners]

That doesn't tell me what version you're using.

Still zero feedback from users that are testing the fix we've added to the beta.

[gofastwclass]

That doesn't tell me what version you're using.

Still zero feedback from users that are testing the fix we've added to the beta.

Sorry, can you not see the emails to support?
The version I used today was 3.1.22.

Let me know what you need or want me to try and I'll get it to you.

[Keith@HPTuners]

Ok so the new beta is NOT working for you.

After you see the scanner MPVI inputs stop. disconnect the scanner, then e-mail the debug.dat file to support with a description of what you saw, and we can look into it further.

[gofastwclass]

Will do.

[gofastwclass]

Keith, I just sent another email to support with some additional data. Support #26242.
In this instance the scanner stopped displaying live data, but it did not stop logging. This is in Beta 3.1.25.