VCM Suite 3.0 Is Finally Here!!!

[schpenxel]

Not a clue--if you keep it to the broadcast parameter ones it'll stay fast and essentially be "free" as far as not slowing everything else down goes

I'd just add them all and then delete the ones that don't do what you want

[DSteck]

Damn. I love 3.0. The functionality is way better than 2.24. It comes with a learning curve, but if you really sit down and dedicate yourself to learning, you'll figure it out. I think most people expect software to just be "well I hit connect and it should just do what I want".

As with anything that has a lot of capability, it requires more user interaction. My suggestion to everyone having an issue is that you don't try to figure it out while you're doing something that you have a time limit on.

[2xLS1]

The problems I had with 3.0 had nothing to do with a learning curve or figuring it out. The software did not function. In all the years I used 2.24, it never randomly started populating the tables and charts at 10x the normal speed, nor never just started printing a line of numbers on the bottom parameter of the chart display. Closing and reopeninmg the software nor rebooting the laptop would correct this once it happened. Should I have tried reinstalling 3.0? Is that what you call a stable public release, having to reinstall the software to make it function? Never had to reinstall 2.24 to make it function correctly once it was installed. I fully understand learning a new version. I also am able to recognize software that is full of bugs. What version is 3.0 up to after how many days after it's initial release?

[schpenxel]

Do you have logs or screenshots or something of any of those issues happening so they can try to fix them? I'm not even sure what you're saying the issues were

[2xLS1]

No I was at a race. I didn't have time to capture the bugs. I had to get a functioning scanner on Dave's laptop. And I did that by installing 2.24.

[GHuggins]

Can someone tell me which throttle position I need to log to get rid of the 88% at WOT problem?

Log the ones where the (12's) are highlighted or in a colored box - seems to work better for which ever vehicle your working on...

[mowton]

Damn. I love 3.0. The functionality is way better than 2.24. It comes with a learning curve, but if you really sit down and dedicate yourself to learning, you'll figure it out. I think most people expect software to just be "well I hit connect and it should just do what I want".

As with anything that has a lot of capability, it requires more user interaction. My suggestion to everyone having an issue is that you don't try to figure it out while you're doing something that you have a time limit on.

^^^^^^^ I agree its awesome and the new filters are just what the doctor ordered...

Ed M

[2therock]

I have been reading some Dodge vehicles are having issues where the throttle is closing between or during shifts for what ever reason. Can you guys tell me which pid or channel to select to for monitoring for this?

[Niemer]

I have two of the same sensors at different locations connected to input 3 and 4 and I want to set up a math parameter for each, what is the best way of going about this? I'm guessing that using the generic transform as a variable will not work any more since there are now two of them. Do I have to manually build the transform into the equation to get around this or is there another way now?

[schpenxel]

Yeah try doing a manual one (or two). I'm not totally sure which "parameter" you'll want to set them up as though

There's a "fx" button now in the transform selector that will transfer one of the pre-defined formulas down to the user defined one, so that makes it easier

[Niemer]

I just built the transform math into the equation, just using the raw voltage signal from the input. Is there a reason for not being able to define the inputs as the applied transform and use that in maths? I know this has been brought up before, but I don't remember if there was an answer.

[ddtech]

With 3.0 What is the correct way to reset adaptions for the Trans.

[schpenxel]

I'm not sure. So instead of using a transform you're using the MPVI input voltage in a math parameter and manipulating it that way instead? Or am I misunderstanding?

[Niemer]

I'm not sure. So instead of using a transform you're using the MPVI input voltage in a math parameter and manipulating it that way instead? Or am I misunderstanding?

That was the idea, however, it didn't seem to work, nothing shows up in the chart. I'll try your way and see if I can "fake" a couple parameters. But, this seems like a silly thing to have to do when the transforms can already be applied to each input. I can't be the only one using two of the same sensors.

[ElecTech]

With 3.0 What is the correct way to reset adaptions for the Trans.

Should be the same as before. Special Functions.

The reset functions may not be available on certain platforms. GM platforms are the most likely to have support.

[schpenxel]

That was the idea, however, it didn't seem to work, nothing shows up in the chart. I'll try your way and see if I can "fake" a couple parameters. But, this seems like a silly thing to have to do when the transforms can already be applied to each input. I can't be the only one using two of the same sensors.

For some reason I thought I read that you couldn't do that? Try making the math parameter just the MPVI 3 input voltage, graph or chart that and see what you get

[Niemer]

Ok, I'll see what happens.

[Dave_62]

OK, I've searched and can't find an answer to my exact question. Can I use 3.0 to upgrade a 2004 12586243 (12585950 OS) PCM to the 1 Bar speed density COS with RTT?

[Keith@HPTuners]

Open the file in VCM Editor and open the Operating System tab. This will show you your options.

Or, just post the file here and someone might do that work for you and let you know what they find.

[LSxpwrdZ]

At first I wasn't using it just because I didn't have time to transfer all of my stuff over to it. Once they incorporated the import function it really eased the transition for me. I still use 2.24 for all of the Gen3 applications mainly only for the RTT functionality. But I'm sure once they get the bugs worked out of the RTT functions I'll move forward with using 3.0 with everything. The scanner is leaps and bounds better at logging rates especially on the byte limited Gen3s.

The one thing I would like to see moved back over from the 2.24 is the ability to input a list of voltage to value for the MPVI inputs. The transfer function forces a linear range where as I've found isn't the case for every wideband I've ever used. Getting that set really helps with error.