V3 Scanner External MPVI channels freezing

[Alrubaei]

Following. got the same issue 3.0.22 LM2

[capchaos]

Same issue as well

[Keith@HPTuners]

Please e-mail support guys for access to 3.1 BETA.

We have a few customers testing it, but so far nobody has actually reported if it works or not. We need customers that will actually provide feedback to our attempted fixes so we can solve the problem for everyone.

[super6ute]

Emailing support with same issue now

[capchaos]

Emailed yesterday hope to hear back soon

[gofastwclass]

Yesterday was a holiday for them but they're really good at responding about this stuff.

[spyder09]

i have same issue waiting on support to email back. also the scanner crashes completely after the logs stop getting live data without option to send error report. im looking for how to get the debug.dat file when this happens

[Keith@HPTuners]

We've started to get feedback regarding this issue, but we need help narrowing it down:
Is it a VCM Suite 3.0 issue?
Is it a laptop issue?
Is it an MPVI issue?
Is it a vehicle issue?

[Joe6pt0]

Emailed support tonight v3.0.25. WB reading locks up after anywhere from 1min to 5min of scanning.

NGK Powerdex AFX-confirmed voltage with DMM
Laptop is a new quad core Dell 4800 3.2Ghz 16GB ram Windows 10
Older MPVI box from 2006
E38 ecu, 2015 Camaro

[Keith@HPTuners]

For those of you involved in this beta testing process, please download the newest beta (3.1.40) and report back with your results.

[rao]

As soon as I can access the beta I will give it a go.

[Keith@HPTuners]

For those involved in testing, please try beta 3.1.42 and report back.

[Joe6pt0]

3.1.42 tests:

E38 ecu 2015 Camaro. Downloaded and installed 3.1.42.

1) First attempt entire scanner locked up seconds after scanning. Closed scanner re-opened.
2) Second attempt entire scanner locked up immediately. Closed scanner. Opened 3.0.25
3) Openend 3.0.25, scanned for a few seconds. Closed 3.0.25 and opened 3.1.42 and scanner worked for about a minute before locking up. Restarted computer.
4) After computer restart, opened 3.1.42. Scanned for about a minute then WB reading froze again. Scanner didn't freeze this time just WB reading again.
5) Closed 3.1.42, reopened. Scanned for over 6min then WB value froze again. Closed 3.1.42.
6) Another attempt with 3.1.42 fired up car did a pull. WB value froze 37 seconds after starting scan.

Both 3.0 and 3.1 seem random on the time it takes to either lock up or to stop logging WB.
I can't try without MPVI tonight, trying to finish a car on the dyno. But it's something I can do tomorrow on another vehicle.
My other laptop is another DELL M4800 also but it is on Win7 still. I may have time to try that Friday or Sat.

[Keith@HPTuners]

That is some great feedback!

Do you think the current 3.0 can log longer without locking up than the latest 3.1?

Also, how does the latest 3.1 do if you don't log any MPVI input channels?

[Keith@HPTuners]

3.1.43 BETA is up, give this a try.

I need to know what it does differently when you log no MPVI AD inputs vs logging them.

Also, if you guys have another laptop to try, that would certainly help.

[Joe6pt0]

Attempt 1) 3.1.43 scanner completely froze as in locked up and had to X out. 1st try at 1:25:657 into logging. Will restart and try again.

Attempt 2) Before starting a scan, got a complete lockup requiring task manager kill when selecting a graph parameter to a MATH function.

Attempt 3) Restarted computer. Opened 3.1.43. Scanned for 4:46 then WB value froze. Scanner worked otherwise.

Attempt 4) Closed scanner from fail above. Re-opened. Logged 1:35 then WB value froze. Scanner worked otherwise.

[Keith@HPTuners]

When you say completely froze, you mean you had to kill the task with task manager, or, froze meaning it stopped logging and you had to X out of it.

[Joe6pt0]

When you say completely froze, you mean you had to kill the task with task manager, or, froze meaning it stopped logging and you had to X out of it.

Did not have to kill with task manager on that attempt but I did just get a complete lockup requiring task manager kill when selecting a graph parameter to a MATH function.
Updated to keep my dialog cleaner to read. Feel free to delete this one.

[Keith@HPTuners]

Ok, that helps a bit..

Try this.. With the beta, try scanning your normal channels and MPVI inputs, and only have the Channels display open. Close all other layout displays (gauge/chart/graph). See how this does.

If that works, add a single display (chart), if that works, remove chart and add (graph), if that works remove graph and add (gauge).. maybe we can narrow it down to a single display.

[Joe6pt0]

Another bug on Beta following your advice above, partially due to me selecting the wrong thing:

1) From WB froze state above, had full layout open and I had a log open.
2) Closed Gauge, Graph and Chart vs time. Left Channels open only.
3) Realized I really needed to grab the data from the log first on the graph to place back in the .hpt file so I meant to open my layout but instead since only Channels was open, I clicked on the Channels tab, Recent Channel Configs. I guess in my haste i saw the .xml filename I saved for my Layout (I wanted to open the old layout) and clicked it thinking it would open the layout. Layout went to default. Now if I try to go to Layout, Open Layout and select my .xml file, i get an invalid layout message and i'm stuck on default. Have to start all over with my layout.