VCM Suite 3.4 is here!

[Mark@HPTuners]

Please understand I'm not asking for an ETA, just if its something you quys are still working on, or abandone . Thank you.

Nothing is off the table. We already have operating systems mapped out for JTEC and we covered 07+ RFE earlier this year, so going back 06 and older should be do-able. So in short, no we did not abandon either of those.

[Trguy79]

Took a look, but didnt see any changes for the GPEC ecm... Is this correct (havent plugged in and looked on the Scanner yet, just referring to Editor).

I too would be VERY interested in support for PRE 04 fords...

[tbrtuning]

I would love the older Ford support also. I've been asked about tuning several 99-04 Mustangs but can't justify the purchase of other software just for this. It would be very nice to be able to start tuning them with no additional investment.

[Area47]

rtt still has issues with loading. says failed when trying to pull the ve table. then it adds 40% to the entire "shown" ve table. ::shrugs:: back to 2.24 for rtt...

so nothing on the rtt issue?

[Keith@HPTuners]

so nothing on the rtt issue?

Did you open a support ticket?

[Area47]

just did.

[GHuggins]

Unless I'm doing something wrong - in the scanner under graphs - view setup - will only let you see an average - won't let you use any of the other settings...

[schpenxel]

Do you have it set for display all data or display zoom range only?

[GHuggins]

All data - does it need to be on zoom?

[LSxpwrdZ]

rtt still has issues with loading. says failed when trying to pull the ve table. then it adds 40% to the entire "shown" ve table. ::shrugs:: back to 2.24 for rtt...

so nothing on the rtt issue?

I had the RTT tables loading and functioning properly in 3.4.9 last week however the scanner would freeze or the wideband data would freeze again when I would pull the RTT data down from RAM. To get around this I pulled the RTT data first before starting the log and that seemed to work perfect and wideband data was functional.

Now another issue I discovered was HPT Editor was not correctly displaying the VE % table data in some Gen3 OS's. I could pull the same exact tune up in 2.24.1172 and 3.4.9 and the VE table data would be completely different (scaled). So I assume the new version wasn't referencing the cylinder volume correctly but rather a preset value which will skew the VE% values. The Scanner VE that was pulled down seemed to be correct values compared to the older 2.24 version. With that said this obviously caused all sorts of fueling problems when copying back and forth between the Editor 3.4.9 and Scanner for RTT tuning. Looking at 3.4.20 now and the VE % seems to be working correctly now.

[StopGap]

I am right in the middle of tuning my newly FIed setup (e38) on 3.2; and in major tune learn mode as well.

A couple of NOOB Qs:

1. Would it be wiser to stay with 3.2 for now, until I get through all of the fine tuning (I am street tuning; not dyno)?

2. If I do download 3.4 will it automatically overwrite 3.2, or will it create a new folder?

[schpenxel]

3.4 will overwrite previous versions

3.4 is very close to the same as 3.2 in most cases. Not saying it isn't an improvement, but for the average people tuning gen 4 vehicles there isn't really much of anything you'll notice. It's nothing like the jump from 2.24 to V3+ was or anything like that. It adds support for tuning 2017 vehicles and some other stuff like that, but it isn't a huge jump to a whole new interface or anything like that

So, either one will be fine. I doubt you'll notice any differences (I haven't)

[Area47]

I had the RTT tables loading and functioning properly in 3.4.9 last week however the scanner would freeze or the wideband data would freeze again when I would pull the RTT data down from RAM. To get around this I pulled the RTT data first before starting the log and that seemed to work perfect and wideband data was functional.

Now another issue I discovered was HPT Editor was not correctly displaying the VE % table data in some Gen3 OS's. I could pull the same exact tune up in 2.24.1172 and 3.4.9 and the VE table data would be completely different (scaled). So I assume the new version wasn't referencing the cylinder volume correctly but rather a preset value which will skew the VE% values. The Scanner VE that was pulled down seemed to be correct values compared to the older 2.24 version. With that said this obviously caused all sorts of fueling problems when copying back and forth between the Editor 3.4.9 and Scanner for RTT tuning. Looking at 3.4.20 now and the VE % seems to be working correctly now.

Guess i need to update it again. This was on thursday when i was messing with a gen 3 and fighting some issues with it. It dumped an automatic 40% into the ve table, fuel trims tanked and the car damn hear shut off till i shut down the rtt side. Been playing with a 99 c5 for about 3 weeks now that was done on the 3.2 1 bar setup with rtt. been doing it the copy and paste way to get it to work right as the rtt did the same thing on it. I am more or less annoyed that something that so usefull as this was not 100% tested . just me bitching about it is all. Thanks for the heads up.

[Keith@HPTuners]

There was a bug in the way VE % was being displayed on LS1 P01/P59 controllers that were VCM Enhanced. That was corrected in today 3.4 update.

Bugs reported on the forum are hard to keep track of.

When you guys submit support tickets for these bugs, we will fix them ASAP!

[[email protected]]

Nothing is off the table. We already have operating systems mapped out for JTEC and we covered 07+ RFE earlier this year, so going back 06 and older should be do-able. So in short, no we did not abandon either of those.

Thank you for your informative response. That's exactly what I wanted to know.

[gofastwclass]

When you guys submit support tickets for these bugs, we will fix them ASAP!

I can attest to this, thanks again guys.

[DSteck]

GM FPCM support would be nifty even if it's just disabling codes...

[gofastwclass]

I agree, nice one Dave.

[Brice]

GM FPCM support would be nifty even if it's just disabling codes...

[* _ *]

Was hoping 3.4 would enable the scan feature to be used across all obdII compliant vehicles. Tested it out on some that the old version was not able to recognize and still same thing.

Any reason to this?