Jump to content

Puffwagon

Members
  • Posts

    862
  • Joined

  • Days Won

    140

Posts posted by Puffwagon

  1. That's all good mate. I'll start the thread after if you want it up. 

     

    Haha ironically I've had to fix the spark tables to read one decimal place but it'll solve the issue that will15 and i had.

     

    I did think of another thing tho. Being able to highlight one line at a time so they're isn't a mess of lines to look through with the new feature. 

     

    It's a good addition however ☺️

  2. On 7/27/2018 at 1:57 PM, Roland@pcmtec said:

    Any other UI suggestions you guys have don't hold back, anything that can help speed up the process of building a tune we would like to implement.

    This should go into a new thread methinks. It'll have much better visibility.

  3. Off the top of my head without thinking into it too much...I love a good brainstorm ?

     

    Prefilled injector data for most mainstream injectors at stock reg pressure.

    Perhaps a fuel pressure offset table for guys running aftermarket regs at different/constant pressures. Could you do a fuel pressure input and have a variable speed pump control output?

    You want one decimal place for spark as it is pretty common to use half a degree.

    Would it be possible to have a wideband input, a desired afr map and some type of histogram to show the offset needed to achieve it along with influencing tables/scalars? Something similar for spark and knock would be good but I spose that is pretty standard. Being able to change the whole table by the logged offset, ala winlog/tewblog, would enable quick map adjustments.

    You've already mentioned data tracing and highlighting every affected table/scalar. This will be awesome.

    A basic zf tuning manual highlighting which shift tables need to be changed to increase pressure and shift speed/points for paying customers. On that topic perhaps varying degrees of prefilled zf tune that can be used at ones own risk.

    We've already got reds and greens but perhaps a warning system for clearly incorrect or dangerous cell entries. Although there is a range for the cell, we already saw today that an incorrect entry can cause problems. This could be limited to (final?) spark, fuel and wastegate areas.

    Basic stock tune upgrade wizard. Detect the pcm/tcm and providing everything is stock (confirmed by the tuner/customer), load a suitable tune from a higher powered car such as f6, sprint etc. This will help noobs upgrade safely, at their own risk of course.

     

    Wideband input with throttle blade close function on lean out. This could be tuned with map vs afr voltage.

     

    There's a few spelling mistakes in the software as well, not that I'm picking. I guess that's part of getting it polished.

     

    Anyhow, hopefully there's something good in there.

  4. Maybe we need a "HOWTO: Boost Control (FG)" thread as anyone jumping in here from the title will be expecting to see BA/BF related info.

     

    9 minutes ago, Roland@pcmtec said:

    auF1679 is actually auF3184 in your calibration.

     

    It will be especially confusing when this happens.^^

  5. 7 minutes ago, will15 said:

    I would like to dial in open loop before I even consider closed

    As you should. This can be done quite quickly by logging map, wg duty cycle and boost error. You can also wing it by watching your boost gauge if you're feeling deadly.

    What turbo are you running?

     

    Edit: I'm used to tuning a bf so you'll have to forgive me if I miss stuff ?

  6. Haha I was just dropping the lad at school but had already written this 5 minutes ago.

     

    Running in open loop is a bad idea if you want accurate boost control as a cold night will add a few psi over a warm day. If you are at a boost level on 98 octane that wont allow more timing then you will have issues with detonation.

     

    From what you are saying it seems that you should run the factory boost control as it was intended with a mixture of open loop and closed loop.

     

     

  7. Full numbers would be good as well as the cells fitting the whole number.

    I did think it was odd that a couple of the cells had a 0.03 number in them but it didn't click the the decimal place was out even tho I've had that same issue in excel once or twice.

    Now that we know whats going on it could be made into a thing that people are made aware of if needed.

  8. Lemme preface this by saying that I haven't tuned my car with this yet but I had a quick look in the software and it looks like there are a couple of ways of limiting the open loop underboost dc. I also wrote this for a bf turbo but fixed up one of tables that is labelled differently and has other tables linked to it.

     

    auF1898 looks like the exact scalar to change the issue at hand. Second to that auF0308 would affect it as well. I'm not sure what would take precedence if you put say 0.8 into auF0308 or auF1898 and commanded 1 in auF0307  auF2894 but you could always log it with another logger or put a smaller number into auF0308 or auF1898 to feel the difference easier.

     

    It should be pretty easy to work out what does what when you play with it and take a lap around the block. It will be a lot easier to mess with this stuff when the boost is near stock levels as you won't need to get right into it to create high boost levels.

     

    Anyhow I can't guarantee that this is all correct or that there isn't more to it but it should give some idea of where to look if nothing else.

  9. Hi all :D

     

    I've just read and licensed the tune in my car and some injector data is missing, specifically the high and low slopes, breakpoint and pw min.

     

    I noticed that this data is missing from the stock file that I looked at from the strategy code but I expected that it would show up when I read the vehicle. I emailed a copy of the read to support today (for the custom os) so hopefully we can work out what's going on.

×
×
  • Create New...