VCM Suite 3.0 Is Finally Here!!!

[schpenxel]

But aren't two of those channels absolutely wrong (1mph in the pic, always less than 2mph) where the other is 59mph)? If they were closer, it might not be such a big issue (if I'm understanding the issue properly).

Why not just delete stuff you know is wrong (or that is not reporting the info you're after), making it a non-issue?

[chaas]

Looks correct. You're plotting against a Sensor, most likely,so it will take into account all Channels that represent that Sensor.

How does one plot a "channel" versus a "sensor"?

[richsoucie]

That is a feature I'd like to see working as well (also, the import feature..)

I can always copy/paste to Excel

Its just so much easier when someone has no clue and your tuning it for them to send them file to import at least i think it is anyway.

[yonson]

Does this software have GPS built into it and it knows when you are on the dyno? EVERYTIME I get on the dyno the 3.0 scanner F's up, it's been working fine on the street, get on the dyno, lock converter and gear and after 30 seconds the lambda freezes (hasn't ever done this on the street). I've been using 2.24 for most of it, but it won't let you lock the converter and gear, so you can't do any loaded low RPM in gear mapping.

[jtrosky]

Why not just delete stuff you know is wrong (or that is not reporting the info you're after), making it a non-issue?

That might be a workaround for this particular situation (I don't know what @chaas was going for here), but regardless, if the PID (or sensor or channel or whatever) isn't reporting the correct values, it still needs to be fixed - that was my point.

[schpenxel]

How does one plot a "channel" versus a "sensor"?

When you're selecting a parameter that is a section labeled "Specific Parameters" which are specific PID's, then a section labeled "Generic Sensors" for sensor parameters

If using specific you'll oftentimes get a message asking if you want to use generic sensor instead.. just hit no if you don't want to

1.png

[jtrosky]

So while sensors are normally preferred (becuase they are "broadcast" right?), it sounds like using a sensor can also be problematic (or at least give different results) than a PID, since the sensors show "averaged" data in the charts/graphs. Is that a correct statement? If so, it sounds like an important difference to remember. Or will PIDs do the same thing?

Just trying to understand some of the differences between the two a little better... I've just never seen an scenerio where they data shown in teh charts/graphs is different than the data shown in the channels/table (in 2.24 at least).

[chaas]

Thanks schpenxel - that helps. :-)

Keith - is fixing the two inoperable broadcast speed PIDs something that will be investigated?

[schpenxel]

So while sensors are normally preferred (becuase they are "broadcast" right?), it sounds like using a sensor can also be problematic (or at least give different results) than a PID, since the sensors show "averaged" data in the charts/graphs. Is that a correct statement? If so, it sounds like an important difference to remember. Or will PIDs do the same thing?

Just trying to understand some of the differences between the two a little better... I've just never seen an scenerio where they data shown in teh charts/graphs is different than the data shown in the channels/table (in 2.24 at least).

My understanding is broadcast vs. not is a totally different thing than generic vs. specific. Broadcast parameters are parameters being "broadcasted" at a very high rate, all the time, even if HPT isn't hooked up. They're common on items used on factory gauge, i.e. RPM, vehicle speed, coolant temp, etc.

Generic vs. specific parameters is better looked at as universal vs. vehicle specific parameter when setting up charts/graphs/gauges.

If you're using the generic sensor for engine RPM for example, it should work no matter what RPM channel you're logging and no matter what vehicle it's on. It's a much more universal way of setting up charts/graphs so you don't have go in and change what parameter you're plotting on a chart every time you switch from logging an E40 to logging an E38, just as a random example that may or may not actually make sense. Some of the PID #'s are different between different ECM's, so to make say a MAP sensor reading show up on a graph, when using specific parameters you would have to go in and change it to whichever PID that particular vehicle uses. When using generic sensors you don't have to do that.. it will display whatever MAP data it has from whatever MAP PID is valid for that vehicle automatically.

[Keith@HPTuners]

What version of VCM Scanner are your broadcast speed parameters not working?

[chaas]

What version of VCM Scanner are your broadcast speed parameters not working?

3.0.37

[GHuggins]

Does this software have GPS built into it and it knows when you are on the dyno? EVERYTIME I get on the dyno the 3.0 scanner F's up, it's been working fine on the street, get on the dyno, lock converter and gear and after 30 seconds the lambda freezes (hasn't ever done this on the street). I've been using 2.24 for most of it, but it won't let you lock the converter and gear, so you can't do any loaded low RPM in gear mapping.

Mine seems to be just the opposite - Won't work at all on the street (constant restarting - miss the self shut down that 2.24 did that only required hitting the start button again), then somewhat works on the dyno

[mbray01]

keith

I messaged you a few days ago about a 2006 mustang gt that would not start after a flash with 3.0
but would start after flash with 2.25 and a previous tune file

well I have a 2007 mustang gt
will not start after flash with 3.0, and I do not have a previously saved 2.25 file, as this car is here for the first time today
I forgot about the glitch, so I didn't try 2.25 first. now Im dead in the water
I sent the files and info logs to support.
this is obviously more than a glitch something is wrong!!!!!!!!!

[GHuggins]

keith

I messaged you a few days ago about a 2006 mustang gt that would not start after a flash with 3.0
but would start after flash with 2.25 and a previous tune file

well I have a 2007 mustang gt
will not start after flash with 3.0, and I do not have a previously saved 2.25 file, as this car is here for the first time today
I forgot about the glitch, so I didn't try 2.25 first. now Im dead in the water
I sent the files and info logs to support.
this is obviously more than a glitch something is wrong!!!!!!!!!

Do you experience this or any other weird problems happening with any other platforms? Just wondering... Been having some very weird issues with one I'm working on right now.

[spyder09]

Those of you having freezing lambda or afr with the scanner try setting the affinity of the scanner after its opened before using it. Open scanner, open task manager, go to the vcm scanner process, right click and set affinity, uncheck all cpu except for 1 (I use the first one can't remember if it's labeled cpu0 or cpu1) then hit ok and close task manager then do some logging...hope it helps some of you seems to have helped some of us users that have had this issue consistently and have been reporting on the other thread

[jtrosky]

My understanding is broadcast vs. not is a totally different thing than generic vs. specific. Broadcast parameters are parameters being "broadcasted" at a very high rate, all the time, even if HPT isn't hooked up. They're common on items used on factory gauge, i.e. RPM, vehicle speed, coolant temp, etc.

Generic vs. specific parameters is better looked at as universal vs. vehicle specific parameter when setting up charts/graphs/gauges.

If you're using the generic sensor for engine RPM for example, it should work no matter what RPM channel you're logging and no matter what vehicle it's on. It's a much more universal way of setting up charts/graphs so you don't have go in and change what parameter you're plotting on a chart every time you switch from logging an E40 to logging an E38, just as a random example that may or may not actually make sense. Some of the PID #'s are different between different ECM's, so to make say a MAP sensor reading show up on a graph, when using specific parameters you would have to go in and change it to whichever PID that particular vehicle uses. When using generic sensors you don't have to do that.. it will display whatever MAP data it has from whatever MAP PID is valid for that vehicle automatically.

Thanks for the detailed explanation. Let me ask this - for someone like me who tunes one car and one car only, is there any advantage/disadvantage to using generic parameters instead of specific parameters? To me, it sounds like the generic parameters would mainly benefit professional tuners who tune all different kinds of cars. Just curious if there are any "cons" to using generic parameters when only tuning one car.

While I'm still using 2.24 for flashing and scanning, I am trying to get more familiar with and better understand 3.0 as well. I do like some of the features of 3.0 (mainly channel filtering and broadcast parameters), but still much prefer the interface of 2.24 (mainly the "floating" windows and true scroll bar on the chart window). I'm hoping that we can at least get a dual-column "Channles" display soon so I can try to make the switch to 3.0 (also waiting for the scanner logging hangs to get resolved). I think I can live with the 3.0 interface if I can at least get a dual-column Channel window - it's just that right now, I can get so much more information on the screen at once with the 2.24 scanner. It's kind of strange - 3.0 allows you to log more information, but display less! :-)

Anyway, thanks again for the explanation - I appreciate it. I was confusing broadcast parameters and generic parameters (thinking that generic parameters were also broadcast parameters).

[AlexDiag]

I have been your loyal customer for years. I am very excited about a release of VCM Suite 3.0., its a great scanner! Thank you for adding many new functions to it, especially I appreciate that now I can enter data through the serial port.
At the same time, I've got a few concerns. In the new version 3.0.
When I open "Show Difference" mode, and highlight some area, the functions: smooth between horizontal bounds/verticalbounds, smooth selection, interpolate selection, interpolate between horizontal bounds/vertical bounds, become inactive, so I am unable to use them at all.
At the same time, when I try to enter numbers in a specific area in the "Show Difference" mode and work with functions such as add, multiply, delete, it does not work properly as well. So, for example, if I enter to add numbers, it does add them to where I want them to be, but if try to undo it, then it does not brings it back to the originals, but shows some random (coming from nowhere) numbers.
In the end, I simply cannot copy data when I am in "Show Difference" mode to paste it to the different map.
As I said, I have heavily worked in the "Show Difference" mode, and being unable to use those crucial functions really limits my work. I would really like to know if the functions, I listed above, are removed in 3.0 release, and you are not planning to add them back?

[schpenxel]

I have had the "undo" issue as well and it can be quite frustrating.. and I also wish the smooth features would work in "differences" view.. Hopefully both will get fixed soon.

[schpenxel]

Thanks for the detailed explanation. Let me ask this - for someone like me who tunes one car and one car only, is there any advantage/disadvantage to using generic parameters instead of specific parameters? To me, it sounds like the generic parameters would mainly benefit professional tuners who tune all different kinds of cars. Just curious if there are any "cons" to using generic parameters when only tuning one car.

While I'm still using 2.24 for flashing and scanning, I am trying to get more familiar with and better understand 3.0 as well. I do like some of the features of 3.0 (mainly channel filtering and broadcast parameters), but still much prefer the interface of 2.24 (mainly the "floating" windows and true scroll bar on the chart window). I'm hoping that we can at least get a dual-column "Channles" display soon so I can try to make the switch to 3.0 (also waiting for the scanner logging hangs to get resolved). I think I can live with the 3.0 interface if I can at least get a dual-column Channel window - it's just that right now, I can get so much more information on the screen at once with the 2.24 scanner. It's kind of strange - 3.0 allows you to log more information, but display less! :-)

Anyway, thanks again for the explanation - I appreciate it. I was confusing broadcast parameters and generic parameters (thinking that generic parameters were also broadcast parameters).

I'd still try to use generic sensors so you don't have to make changes between cars but it's not going to be a huge deal either way if you're only doing a car here or there.. as long as you understand how to setup charts/graphs to do what you want then you're ahead of a lot of people

[XDR]

Is there a change log with the updates? Also, HP Tuners admins, would you be able to incorporate which version is available for download, so I'm not downloading the same one over and over.