I did, I set it lower, like 2 seconds, (so DFCO would kick in faster), but no change. It shows that I?m going into open loop on decel (even adter enabling closed loop), it was doing it when I had it in open loop at all times (tuning MAF) and after enabling closed loop (Done tuning MAF). even though I have it set to only go into open loop decel at 0.00 load or under (stock settings), my decel load is usually around 0.16-0.19. It?s Really wierd. so this obviously messes up my EQ error when logging in the lower cells of the MAF. I?m sure ill figure it out, just weird.
there is still issues with logging data with newest beta, works for about 2 seconds before starting to glitch, attempted to remove pids and change the polling intervals with no success, get about 10-15 seconds in before it locks up sometimes a minute or so but still glitches in between. i notice the cluster on the car cuts out when it happens too. rpms drop to zero same with temp and then lines across the odometer and then check engine light pops on for about a solid 3-5 seconds then it all goes back to normal and the process repeats
Mine is glitching in real time also but the vcm scanner software will fill in the blanks so if you're review the datalog you wouldn't really notice the glitch if it's less then a second. If it hangs for 2 to 3 seconds you can notice it in the log. I'm just wondering why the cluster is acting up when this happens. In mode 10 it would only aquire the data not transmit. Someone correct me if I'm wrong here.
Mine has been doing the exact same thing. I haven't notice it filling in accurate numbers during the glitch in my case it just locks in previous value so you get a nice flat line. Cluster issue has to be from the communication process with the mpvi2, support suggested it could be wiring issues, but I didn't find any and a few others who are having the issue didn't find any either.
Its definitely not a wiring issue. I did notice the volts on pcm peg at 14.5 I wonder if their values in vcm dont exceed 14.5, it's a communication error on their end threw the controller and software. J1850 is much slower then canbus and the amount of data the bus can handle is significantly less
I just hope they can sort it out. Their software is outstanding in regards to what we're able to do when it's working properly lol. If they got it working on j1850 vpw (gm) they can make it work on j1850 pwm
We are in search of a vehicle to bring in house for testing, if anyone is close to the Chicago area.
Eric Brooks
HP Tuners, LLC
If I was closer I would in a heart beat. Im up in canada. Hopefully you guys find someone that is willing
hp tuners still cant find a mustang to test...something is so wrong with that.
Daily Driver= 2003 BMW 330xi
Weekend Cruiser= 2009 Pontiac G8 GT (Vararam, TSP LS3 N/A Stage 1, OBX, CTS-V converter, MagnaFlows w/ J-Pipes, 160 t-stat)
Project Car= 1991 Chevrolet Camaro RS (LQ4 w/ Gen 4 Rods, LS3 heads, turbo...)
Truck= 2007 Chevy Silverado 1500 LT LY5 4x4
That couldn't be anymore true. Looking at the posts and how long hpt been "working" on the eec-v and not making any gainful progress they should really put a disclaimer in their supported vehicle for eec-v mustangs and making people aware that it's only partially supported.
I’ve done 5 01-04 eec cars with hptuners to date, making from 300 to 775 rwhp. We plan on doing more. At the shop we are trying to condense our softwares. I hope they keep working on the software to get the bugs worked out of the scanner. So we can exclusively use hptuners on our domestic cars.