Version 5 Feature Requests
Added 2023-06-08 21:00:03 +0000 UTCStarting to think about putting together ideas for V5. I have some features that I want to add, but I'm open to adding to the list. Also if you would like to see one of the current features improved please comment about that too.
Here is my current list:
- MAP based spark tables (2 & 4 Bar) - High Octane Table, Low Octane Table, Coolant Spark Table, IAT Spark Table, Flex Spark Table
- Update EGR Position with Boost Control Duty Cycle when EGR is disabled. This would allow logging with a standard PID
I've already gotten these suggestions:
- Boost scramble button
- Closed loop boost control (Would be a lot to code)
- Traction control (Might not have enough inputs to PCM)
- Fuel Pressure Safety (Not sure how this should work)
- Real Time Tuning (Might not be feasible, and would be a lot of work)
I would need to understand if there is enough interest for any of these.
There are 2 things I'm looking for with new feature requests:
1. Details on when/how it should work
2. The tuning parameters needed
Thanks,
Branden
Comments
should do MAP based factory tables, delete the low octane table table as its annoying to have to copy high to low all the time. seen in the current version that 2BAR spark table is possible but when your on stock MAP sensor you lose a bunch of table resolution running on a 2BAR based table. changing the stock spark tables axis should be relatively easy, just look at the how the stock VE table reads its axis and pretty much copy that. also add other units of measure like AFR instead of lambda and PSI relative to atmospheric press instead of KPA. not super difficult to do that either. for example, take your base equation for lambda and multiply it by 14.7. to convert KPA to PSI relative to atmospheric pressure you just take the base KPA equation put this after it, *0.14503773800722-14.6959494. like this in tuner pro, (X/value for KPA)*0.14503773800722-14.6959494. also all of the various tables for things like spark and desired AFR are not really necessary. you could just have 1 for E0 and another for E80 if you use some math and a few clever ways to just rescale the pressure axis of the table by a factor and offset. than its as easy as having 1 constant value that you pick your MAP sensor from and once chosen all of the axis's automatically rescale for that sensor. like set the constant to 1 and thats the stock MAP, set it 2 and thats a 2BAR MAP, etc. uses far less code space in the ECU and reduces the number of maps so people just learning this stuff dont get confused.
scott bradford
2024-09-01 00:05:39 +0000 UTCNo, but it’s on my radar to look at implementation for the next release. I believe the brake pedal input (auto) or clutch pedal input (manual) would be used to start the timer. This is already how the launch spark vs. time works.
Branden Butella
2024-06-17 17:16:58 +0000 UTCIs boost duty cycle vs time available? Where an input would reset timer and release would start it?
Blake Matney
2024-06-17 15:46:03 +0000 UTCI signed up and commented on the discord server. I would love to help if i could. I have a fair amount of programming and fair amount of tuning experience. Little understand of how to edit these files but am eager
Nisan Catron
2024-05-31 21:43:03 +0000 UTCSorry I meant Discord.
Branden Butella
2024-05-31 20:37:23 +0000 UTCWhat community are you referring to? This is the first time I've been on patreon and signed up for the $5 monthly fee I believe
Nisan Catron
2024-05-31 20:17:59 +0000 UTCThat all is possible right now. It would be a good idea to join the Patreon community. It’s better for chatting about current and new features.
Branden Butella
2024-05-31 20:00:50 +0000 UTCNeeds 3 bar maps for fuel and timing. Map based. More resolution on the rpm axis. Race style ecu
Nisan Catron
2024-05-31 13:43:01 +0000 UTCMy idea is to have more of a race style ECU, striped down tables. Remove all the TQ management tables etc
Nisan Catron
2024-05-31 13:41:50 +0000 UTCNot sure what you mean by that. Can you provide an example?
Branden Butella
2024-05-31 13:34:50 +0000 UTChow can I delete unused PIDs?
Nisan Catron
2024-05-31 00:11:18 +0000 UTCI would join the Discord Server as there has been a lot of discussion about this on there.
Branden Butella
2023-06-24 15:14:39 +0000 UTCFuel tank pressure sensor is 5v.
Stokes1114
2023-06-24 04:38:44 +0000 UTCI still believe a delta lambda table for launch control would help. Typically in boost the ve is a bit rich, and would be nice to be able to lean it out when staging under LC only. Maybe delta lambda vs map?
Stokes1114
2023-06-23 02:01:06 +0000 UTCBranden, an upgraded, more informative, and more accurate version of the spreadsheet has been uploaded to your pm on pcmhacking. For onlookers, the information source was switched from Alldata to this: LS Gen III Engine Wiring Systems 1997-2007 ISBN-13: 9781613257913 Publisher: CarTech Inc. Publication date: 05/03/2022 The way I am interpreting the Gen III book data is that Alldata does application filtering by year/make/model, the book DOES NOT. What this means is that the actual functions of the ECM's are presented in the case of every pin, and not a re-interpreted version of pin function based on specific applications. In other words, you have the full set of ECM capabilities presented, per pin, with better descriptions, rather than an inaccurate per-application interpretation. Refer to chapter 7, "The 2003-2007 P59 PCM", page 78.
gilius
2023-06-14 20:37:45 +0000 UTCThat's right it isn't an input anyhow just an output. A/c pressure sensor and oil pressure sensor inputs. Some won't want to lose the oil pressure input tho. On my setup I use a 1 pin to the oem gauge on 99 Silverado but other use it to datalog from. It's a dead input for me. Maybe one day I will utilize it who knows.
Billy Bowerman
2023-06-13 18:20:36 +0000 UTCYou can PM me with the files. Also the Evap doesn't have a 5v input. I think the A/C Pressure Sensor is the most likely the best option.
Branden Butella
2023-06-13 12:46:07 +0000 UTCI have the entire set of pin definitions from Alldata in the spreadsheet I was msg'ing you about, but no email address to send to, the pcmhacking forums don't have that flexibility
gilius
2023-06-13 07:11:04 +0000 UTCIs the evap purge a 5v?
Billy Bowerman
2023-06-13 04:18:11 +0000 UTCIf you two could provide what 0-5 volt input you would suggest using for the second wideband input.
Branden Butella
2023-06-12 13:37:07 +0000 UTCThat was me lol
gilius
2023-06-12 13:14:14 +0000 UTCThis is my official feature request for dual bank wide band closed loop. Ideally this would be with two Innovate wide band controllers. Thanks for any consideration you can provide.
gilius
2023-06-12 12:45:06 +0000 UTCI saw someone mention on PCMHacking about dual wideband closed loop, and I thought that would be pretty cool. My setup is NA, so I don't use many of the available inputs.
Chad R
2023-06-11 00:41:43 +0000 UTCMake 2 new tables: 1) Multiplier to your current DC table over time after LC. 0 - 1.00. Axis is time in seconds. Every .2ms for 4-6 seconds (0.0 0.2 0.4 0.6, etc). “LC boost multiplier vs time” 2) Max DC vs Gears 1-4. “Max DC vs Gear”
Anthony Avila
2023-06-09 00:27:56 +0000 UTCI think even with the current version, maybe v4.5 make boost DC vs time/gear tables using launch control.
Anthony Avila
2023-06-09 00:01:29 +0000 UTCMap based spark, and boost control would be great! Especially based on fuel content. While I love the idea of traction control, and the p59 has traction control tables depending on the os, the best way to implement it? One idea I've seen on some aftermarket traction control systems is to monitor the speed output of the driveshaft (or speed of the drive tires) and if it is accelerating at an unusual rate, it cuts boost, or timing, or fuel (not good for boost) to pull power out and bring the tires back to an acceptable rate of increase. You would need the speed signal from the transmission and a way to determine what the rate of increase is, and then a way to decide what you want your target wheel slip to be to achieve an acceptable level. Then comes how to achieve that wheel speed when you go over it. I would suggest boost cut first on boosted cars, then timing or reduced throttle on ETC cars in whichever order makes sense. Then if you still need power removed to get it under control and you still haven't taken your foot off the gas, fuel cut as a last dich effort to get the tire spin under control. And no, I have no idea how to code it and tie it in to the existing traction control tables, or if it is even possible to use the existing tables on anything other than the ETC cars with the traction control abs system.
Paul West
2023-06-08 23:41:34 +0000 UTCI agree with boost vs RPM. Boost vs. time, and boost vs gear would be great tables to have.
Anthony Avila
2023-06-08 22:29:05 +0000 UTCI was thinking the 4l80s uses 2 speed sensors and if it was possible? to use one for a driveshaft sensor and have tables for driveshaft rpm vs time, activated off the launch control. When it exceeds the set rpm limit pulls timing/pedal/fuel. Most of my customers street race here on not great roads. I would rather have the oil pressure sensor to log but if there was another way to get fuel pressure input, use it with closed loop fueling. Scramble just sounded like a cool extra feature if it was easy to do and an input to ground.
Anthony Avila
2023-06-08 22:17:14 +0000 UTCI believe the evap canister purge solenoid is still open territory as well
Billy Bowerman
2023-06-08 22:09:25 +0000 UTCI agree with Billy. Map based spark and closed loop boost control are excellent ideas. I think if ditching the MAF tables and using it as an input or if it frees up space for other tables idk. I don’t plan on ever running a MAF.
Anthony Avila
2023-06-08 21:45:59 +0000 UTCBoost scramble can also be done externally with a separate pwm controller going to the mac valve as well. I feel like map based spark map and closed loop boost control are the main two on the list that can't be performed by a cheap or easily obtainable standalone unit.
Billy Bowerman
2023-06-08 21:12:07 +0000 UTCMap base spark tables and closed loop boost control would be my vote. Traction control can kinda already be done thru launch control settings. Real time tuning I feel like is going to be a lot of work and hassle for not as much return. As for closed loop boost control I would say an e85 and an e0-10 map. Do an rpm axis and a desired boost in kpa so then the user could target boost by rpm if wanted which also helps in the traction control area. I kinda do this now with the DC setting I leave on gate then ramp duty cycle up from 0-60% 4500-5400.
Billy Bowerman
2023-06-08 21:09:22 +0000 UTC
