S70-R

Members
  • Posts

    800
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by S70-R

  1. Cant that overshooting be due to a too strong wg spring or a not very progressive tcv map? You should be careful with the tcv dc values around the spool up area. If you are having that overshooting the transition values should be as smooth as possible.
  2. That's a huge difference in torque (18% or so) just because of 1 point AFR difference. Are the ignition maps and boost maps the same in those 2 runs (with and without WB regulation)?
  3. Yes, with the ostrich is by far not so time consuming :)
  4. Absolutely true! Those are the main reasons why I would (or likely will at somepoint) use the wideband mod ;) Filling the VE table and hit the target straight away is also awesome, for sure! My point was just to show that even without the wideband mod it is still perfectly possible to get a good AFR control although it takes more time and it's never as accurate as with the mod. And because, being honest, a 0.2-0.3 AFR variance will not hurt anyone or any performance target by noticeable amounts. I did. I've never used the wideband mod so far so I've been doing that since the beginning. I think most of the other members with a wideband gauge have also been doing that. It's not rocket science. It is something easy, logical and intuitive.
  5. Yes, sure. No doubt about it. Just said that even without the wideband regulation mod, the VE table is still an AFR target table and that the system is still able to achieve the target AFR in open loop with a 0.1-0.4 AFR variance, which is not that bad anyway. And if we do some runs, log the achieved target AFR, match it with the target AFRs on the table we can measure the variance and then adjust the VE table further to achieve our real target AFRs. It's a bit more time consuming of course and it's not so accurate as the wideband regulation mod but it does its job.
  6. I also haven't ever touched the wot enrichment table. That table enriches or leans the mixture indeed but it does from the VE table values. Use the VE/lambda table only. Values of 1 mean stoich target (14,7 AFR). Values above 1 mean richer than stoich and below leaner than stoich. It's like inverted lambda values. So, this means you can know the target AFR values included on that table by doing the following math: 1/x*14.7 being the x the VE number on the table. That formula outputs the target AFR for a specific VE number on the table. Actually, you can easily turn all the table into a target AFR table by changing its conversion formula in the xdf definitions. Put this formula: 1/(x*0.0078125)*14.7 If everything is well calibrated (MAF and injectors) and if you have no vac/boost leaks the AFR you will get should be close to the target AFRs on the table. It may differ by 0.1-0.4 AFR. To get extremely accurate AFRs you need to use the wideband regulation mod.
  7. TMM9, I've just dropped you a PM with the link for my log.
  8. TMM9 I'm sorry I couldn't log it yet. Hopefully I'll be able to do it within 3-5 days.
  9. I can log it with mine (manual). As Rod's asked, is just to use that adx and log for 20 min?
  10. I believe it should run ok provided you disable rear o2, sas, baro sensor, etc. And of course ignition map should be custom made for that car.
  11. That's what I did before trying to solve it but it was not working anyway. Tried again after restarting tunerpro and now works. About the TPS difference yes, with the correct conversion factor it is supposed to be the same as OBDII/torque app.
  12. I had already noticed different TPS values when logging with tunerpro or when using for instance OBDII with Torque App but I didn't bother with it that much. But actually the ADX file seems to have that error on the conversionf factor. However, and at least on my adx file, when I'm on trace mode and when I'm looking at the TCV/target load tables the trace is stuck on the first column (TPS <=25). The trace just bounces up and down in the first column according to the RPMs. I noticed it is missing the X Axis DA Link but it seems I can't put it ok.
  13. I still see no need for that for 2 main reasons: 1. When you are tuning a new setup for the first time, specially a bigger turbo, you should start with very low TCV duty cycle and then you will start to raise it slightly. This way you'll have no boost spikes for sure and you are able to get the TCV settings properly, unless you are running a much stronger WG spring than you really need (in that case you can run into boost spike no matter what TCV duty cycle you run). 2. The stock ECU can do the trick for boost cut / fuel cut. Just get a MAP sensor and feed the signal to rear O2 channel for instance. Then, make a routine to set a boost cut or fuel cut if boost is higher than X limit. Doing this routine is the hardest part but the code contributors here would be able to do it (although is probably not needed). Other 2 ways of doing this mechanically (i.e. cut/limit boost) is to either use a parallel MBC or a turbo fuse along with a BOV/Recirc valve. And remember that the main cause of a rod failure may not be the boost spike itself but the ignition advance actually (which may lead to knock). Reducing ignition advance would be the first thing to do to prevent an engine damage along with boost cut/limit. Also to remember that the stock bin has load limits which can be / are used for boost cut.
  14. From your post, I'm a bit unsure about the purpose and goals you want with that. If that solution is to overcome a maxed MAF, why would you go that route instead of upgrading with a bigger MAF? Plus, a MAP (density) system is not that simple. It would require more than that I would say, such as manifold temp sensor, a real engine VE table, etc.
  15. That is fantastic Piet. Nice job! It is really useful for high power builds and I'm going to need it
  16. It's not that risky. Just keep an eye on the boost gauge on you'll be able to manage the throttle in order to not get too much boost.
  17. Check if you have no boost leaks and your wastegate actuator preload. You can also disconnect the vaccum line going to the actuator and then carefuly go for a ride to see if you can build boost earlier than that. If you do this test please be careful as you'll have no ECU boost control. The turbo will freely and fully spool. Don't go WOT, just mid throtlle or something like that.
  18. Like Piet said, do it in 3rd or 4th gear and report back.
  19. Detect detonation before it happens is virtually not possible. However, if you are a good in chemistry, physics and math, and if you are able to collect some data such as cylinder temps, IAT, density of mixture, etc. you can probably calculate the optimal ignition timing before detonation happens. This is however really difficult and or inaccurate to calculate I assume so the best option is still by finding the knocking point, either on a dyno or in the road. Dyno is better to optimize all the ignition map but it has some problems with higher IATs. On the road the IATs tend to be lower and so the knocking point will be higher.
  20. Opening times by voltage is the same as dead time.
  21. Yes, I got it. And when tmm9 says to multiply the 0xD934 map by 0.2 it really is by 0.2 (20%) and not 1.2 (120%), right? Just to be sure. PS: And by the way, just to correct, before I meant the D924 and not the D934.
  22. From what I understood about Tmm9 post, D394 is a map -> "length 16 map at 0xD934 is used." TMFWLO is a temperature set point at C922. I already configured the temperature set points on my XDF as well as the load 8x8 map at 0xDDC4. Just would like to understand if the map at 0xD934 is a 16 rows or columns map, what is the axis and the conversion factor.
  23. Very usefull. The 0xD934 is a 16 rows or 16 columns map? What is the axis? RPM/Load? and conversion factor? Sorry but hex is not my thing... :) Thank you.