mejohn50

I tried a bunch of stuff, don’t remember the specifics off the top of my head right now, but nothing made it work with the key on and engine off. I bet there’s a setting or combination of settings buried down in the Workshop/Development section that could do the trick, but I haven’t found it.

Going to try giving this a brief test this weekend. Will report back what I find.

Does anyone have any idea if it’s possible to program the cooling fan to run with the key on the but the engine off? I’d like to add that into a multi-tune slot if it’s possible so I can run the cooling fan and my heat exchanger pump (heat exchanger pump always runs with the key on) after a pass at the drag strip. I’ve tried a few things but I’m not sure it’s possible. Thanks Mitch

That can happen. Gotta pay to play. You won’t be able to disable rear O2 sensors with PCMTEC, and no pro tuners will do it either. You have to deal with the check engine light or find other ways to deal with it.

Sorry I never got back to this. I’ve been pretty busy working on some other interesting stuff. I’m glad you’ve got it mostly figured out.

For the index table I’d change 4 from 1 to 10. Then in the distance table command 4, which is really mapped point 10. But, again, I’d rescale the rpm axis so it comes out of mapped point 10 over 1000rpm or something close to that. In the idle area, so in the 0.25 load line and from 450 to 1000rpm I’d start by cutting the spark 10% at a time until it has the chop you want. This assumes it’s commanding the correct mapped point 10. You also may need to adjust some of the idle parameters to make it work correctly. I will have to see if I have some time to jump on my laptop and get some screenshots.

Thanks for that very informative response. I have been working with the logger and like you suggested I have found it best to work with the least amount of channels possible to get the information needed.

Not even sure where to start. The whole thing is completely redone. Mapped point 1 is my idle MP and it’s all been redone: MBT, borderline, torque model, speed density, etc. I have left most of the “stock” Whipple idle parameters alone. I’ve got the surging cleaned up but it’s still not perfect. I’ve smoke tested the intake and didn’t find any vacuum leaks (I found an issue but not a leak). Going to do it again this weekend to make sure I haven’t missed anything.

My car has had some return to idle issues since completely rebuilding the Whipple mapped points structure. I recently went through the whole thing and found some spots where I made some questionable choices with MBT spark and speed density numbers. I re-did all that and pretty well solved the return to idle issues, but now the idle will surge about 75-100rpm starting about 10-15 seconds after returning to idle. I know there are a couple other things I likely need to work on, like idle reserve torque, seeing as I made some relatively large errors before, but I wanted to know if it was possible to have a peak at the idle learning status like you mentioned here on M6G. I’m using ZRBA18B. Thanks.

@Roland@pcmtec You mentioned on M6G that there are some idle learning parameters we can data log. Can you point us where we need to look for that? I’m messing with some idle stuff right now and I’d like to know if it’s learned yet. Thanks!

I came across this post in the how to section from 2021 and it has some details on polling rates. Does that information still apply, and if so does it apply to the US market cars as well?

I didn't realize gen 2 had different parameters than gen 3 (auF28819 and auF28820) and they appear to be populated. Very helpful in determining values to try in the gen 3. Thanks.

Hello all, At the suggestion if @Roland@pcmtec over in Mustang 6G I’m starting a suggestion thread for the PCMTEC editor interface. With all the new US market users because of the ProTuner package release there appears to be some feedback on the interface that needs to be aggregated. If you have any suggestions please post them in this thread. I’ll start with mine. Perhaps allowing us to mark parameters as favorites could do two things: - Add that parameter to a favorites drop down in the tree. Also allow us to create our own sub-sections in the favorites section and allow us to move favorites around in there how we like. - Move a favorited parameter to the top of all other parameters within its section in the tree (if desired, let us turn this on and off). Make the order customizable, but keep the favorites at the top of the section they normally reside in. This way we could create our own individual tree with a layout exactly how we want with our most commonly used parameters.

The way the Australian non-Mustang Coyotes are controlled is different than the Mustang Coyote. That method won’t work on the Mustang. You’ll need to use the distance tables and the distance table indexes to command a mapped point that has overlap at idle. I have seen people have success using mapped point 10, which is -20 intake and 0 exhaust. You’ll need to add mapped point 10 to the optimal stability index and then command it in the idle rpm and load range via the optimal stability distance table. If you play with the scaling in the rpm columns in the distance table you can get it to go back to normal cam timing as soon as you go over 1000rpm. Additionally you may need to change the max load for optimal stability. There’s a table for that, and it’s probably not scaled well for this. I’d re-scale the rpm axis so you have 1000-1100rpm defined and then set those, and any lower rpm, cells to 0.3. You will likely have to bump up the idle speed to 800-900rpm. You’ll also probably have to play with MBT spark for mapped point 10 in the idle range to get the chop you want. Idle reserve torque is another area that might need attention There may be a few other tweaks required to get it working exactly how you want, but that should get you on track.