Jump to content

bradsm87

Members
  • Posts

    60
  • Joined

  • Last visited

Everything posted by bradsm87

  1. I'd love to see "generic parameter maps" where I could use existing parameters as axes then put my own data in the table cells then have the output from this map (just a number from 0 to whatever) available as a parameter to use elsewhere (eg. an axis on another table). I can do a dodgy version of this now using a GP PWM output but that option needs a spare physical output and it seems a bit pointless having a PWM out using a pin when all it needs to be is a number held in RAM.
  2. I'm familiar with that. What I am talking about is using the throttle blade to target pressures in the intake manifold after the throttle blade, using the throttle blade, which is very possible. Why not get predictable output from your accelarator pedal all the way from closed throttle up to your WOT target boost like all modern factory DBW cars? Use throttle blade to regulate manifold pressure below wastegate actuator setpoint and normal boost control above wastegate actuator setpoint. I already use accelerator pedal position between around 70% and 90% to dictate target boost between actuator boost and full throttle boost targets. It'd be nice to better use the zone between around 55% and 70% to use the throttle blade to regulate boost below wastegate actuator boost. That way if you put your accelerator to say 65%, throttle will open wide open until say 5psi is reached then gradually back the throttle off to maintain that 5pi. This is better than the old school driveability issue of going to 60% accelerator pedal and having not enough torque then boost kicks in and suddenly you have more than you want and need to back off a bit. This would effectively automate that process.
  3. So I had a play with a base map file. Am I missing something with the definition of general purpose table? I want to create a new separate table somewhere with say X axis as RPM and Y axis as MAP then fill in table values myself manually (say between 1 and 100) then use the output from that table as an axis on another table (in this case, the throttle 1 table) so that I can still use both RPM and MAP as influences on the throttle table rather than just being able to choose one or the other. Here is an example of roughly how I'd want to use MAP to influence throttle position, subject to in-car testing and making sure it's not aggressive to the point of oscillating.
  4. I'm still undecided what would be the simplest way to implement or present this but long story short, I'd really like to have closed loop manifold pressure for targeting boost below the wastegate actuator's setpoint for some zones of the accelerator pedal's travel. An example scenario. 10psi wastegate actuator setpoint. 15psi WOT boost target. If I hit the accelerator pedal to 50%, I'd like the throttle to snap wide open but have it pull back to maintain 100kpa absolute manifold pressure once boost starts to build. If I hit the accelerator pedal to 60%, throttle to snap wide open and pull back once boost reaches 5psi to maintain 5psi. If I hit the accelerator pedal to 75%, throttle stays wide open and normal boost control is used to maintain 11psi. It would of course need a table for default accelerator pedal to throttle angle mapping which it defaults to after sudden pedal changes and go open loop with sudden pedal changes. Maybe have the closed loop control inactive until manifold pressure goes above a bit above atmosphere pressure and only start applying closed loop above that point so that everything below that is still very predictable. I get that there are a shitload of variables involved but damn it would be nice to have the car effectively go full throttle then pull back as boost builds for me! Edit: Actually closed loop probably isn't needed. Using current manifold pressure as an axis or influence by another means for throttle angle would be enough to get that basic control which I'm guessing is already available. I'll play with it in some base maps while I eagerly await the G4X Fury's release.
  5. Excellent. Yes that makes sense. I saw that piece in the datasheet. Thanks.
  6. https://dealers.linkecu.com/CANF_2 Your plug looks like the Amphenol LTW AU-06BFFA-LL7001 but with a sleeve over the top of the centre according to the pic on your web site. What's the go with the sleeve?
  7. Wow thanks very much. It's simple once you look at it already done but I never would have thought of doing it that way. Cheers!
  8. Oh bugger. I didn't realise that Links don't use long term (stored) fuel trims. I'm in the market to buy an ECU this week. Yes this would be a really good feature to be able to check up on LTFTs and manually apply the changes back into the main VE table periodically if needed.
  9. I'd love to be able to temporarily display user-configurable parameters on the tacho. Eg. if I press a momentary switch (or switch a switch), the tacho temporarily displays oil temperature with a user-configurable scale. As a pulsed output with tacho position proportional to the pulse frequency, it seems like something that could possibly be easy to implement? Some things aren't worth the extra cost and complexity of an extra gauge but handy to be able to quickly check without having to pull the laptop out!
×
×
  • Create New...