Jump to content


Popular Content

Showing content with the highest reputation since 07/12/2018 in all areas

  1. 2 points

    Mixture map defined by log window

    Wondering if it is possible to have the mixture map data filtered by the window selected by the time plot range? As in, if I have a section of log I want to zero in on, and be able to run only that section through the mixture map, similar to how the XY plots work?
  2. 2 points

    Knock Control G4+

    It would be nice if these base tables could self populate whilst performing a known "safe" run to fill in the base tables with a background noise level. Then simply add the 10-20% to those values the table could average over a few pulls if need be.
  3. 2 points
    Hi, Currently with mixture map you set a threshold so that samples within say 25% of the centre of a cell vertically and horizontally. This pool of results are used to contribute towards an average value in the centre of the closest cell. However this means that you've got 25% variation of rpm and load, contributing to a static value in the centre - and you need to throw away 75% (?) of recorded values. I have another idea that can let you use all of the data instead, and improve the results. For simplicity's sake imagine a 4x4 grid, and our current load and rpm point is 25% of the way towards the lower RPM value and 25% of the way towards the lower Load value. If we interpolate these values, as per what the ECU does. Note: I have just titled the columns and rows with percentages to show what percentage of the each cell we are interpolating from. We get a value of (25% * 25* 10) + ( 25% * 75% * 30) + (25% * 75% * 20) + (75% * 75 * 40) = 0.625 + 6.075 + 3.75 + 22.5 = 32.95 is the table value that interpolation produces. Now lets say that you wanted to add 10% to this value. If we just adjust the closest cell by 10%, as per current Mixture Map strategy. Then our bottom left cell changes to 44 so our table now looks like this: If we do the interpolation again, but with the new value to represent running the car again after the update: We get a value of (25% * 25* 10) + ( 25% * 75% * 30) + (25% * 75% * 20) + (75% * 75 * 44) = 0.625 + 6.075 + 3.75 + 24.75 = 35.2 as the new overall value. Which is only makes 6.8% difference to the interpolated value, rather than the 10% we wanted. On the other hand... If PCLink De-interpolated the 10% that it wants to add. Instead of adding 10% to the one cell, we split the 10% addition across the 4 cells based on the same percentage that the value was interpolated from initially. So: Top left cell: (10 * 1.1 * .25 * .25) = 0.6875 Bottom left cell: (30 * 1.1 * .25 * .75) = 6.1875 Top Right Cell: (20 * 1.1 * .25 * .75) = 4.125 Bottom Right Cell: (40 * 1.1 * .75 * .75) = 24.75 = 35.75 is the table value that de-interpolation produces. We were trying to add 10% and this new value produced is 10.5%. So that's pretty good! (The 0.5% error comes from rounding to 3 decimal places in my example) So it's accurate to the provided data in every instance. Which is especially relevant when it's applied 1000s of times across all of the cells. You dont need to throw away any of your recorded data, it all contributes to the cell values. Mixture map is pretty good for roughing out a map initially but because of the inaccuracies of the "nearest cell" method I don't really use it that much anymore when trying to dial in a fuel map. You always overshoot or undershoot unless you set your cell tolerances impossibly tight and have millions of samples. And, since this is all only done in PCLINK rather than the ECU, there's not really any worry about the overheads of the extra maths involved. It's worth having it chug away for a few minutes longer if you can get an awesome result on first or second iteration of Mixture map logging. So - that's my Friday night suggestion. Thanks for reading if you got this far, haha.
  4. 1 point
    Hi All, The developers of RealDash have been working with us to make their app compatible with Link ECU's. It is now compatible. For those that havent seen it you can learn more here: http://www.realdash.net/ In my short play it seems to work well and has lots of cool features. Lap timing, navigation, configurable alarms, live graphs, live streaming of data, music player, etc. The app and a selection of basic "skins" are totally free, then there are some more fuller featured paid for "premium skins" that do more stuff such as data logging and may look cooler these are still relatively cheap ranging about $3-$10. One example below. Right now it wont work on the Atom or Monsoon as the serial stream is not enabled in those ECU's but we hope to enable that setting in the next couple of months. Right now it will work in the Storm, Xtreme, Fury, Thunder, all Plug-ins, Force & Kurofune. It will also work on old G4/Vipec V series ECU's. Connection to your tablet/smartphone is direct using your normal Link USB tuning cable, for phones/tablets that only have a micro USB port you will need a "Micro USB OTG adapter". Instructions for setup and connection attached to bottom of this post. RealDash.pdf
  5. 1 point

    Analog pressure sensor

    Also, have a watch of Paul Yaw's seminar on this subject. It can be caused by a range of factors, such as "non-rubber" fuel lines etc, but quite often it is just resonance based. If it is particularly bad at certain RPM's you can often tune that out by changing the length of hose to the FRP reference port. https://www.youtube.com/watch?v=4QF5BmQtXZA&t=409s
  6. 1 point

    Mixture map defined by log window

    Yes, I think this is needed too and I have put it on the wish list.
  7. 1 point
    I took the laptop down to the shed last night, worked straight up, no mess no fuss.
  8. 1 point
    The Lambda trace actually isn't in the correct position as the reading lags so I would say its going lean on a throttle blip, best way to see by how much the Lambda is lagging is to set a switch on a DI and when selected add 10% to the fuel map, hold it at 4k rpm and switch the DI on, by logging the DI and the Lambda you will see how long the lag is, you can then read the log better. I would say if the fuel table is correct then you need to adjust the accell Enrichment. Logging TPS delta along with the TPS trace will help you work out whats going on. Hope this helps.
  9. 1 point

    Base timing on ez30r

    The crank pulley is keyed and there are 2 round indents on the crank pulley itself. When turning the engine clockwise (ie normal bolt tightening direction), when the second one it straight up is tdc. Have a watch of this video to see for yourself, or remove your crank pulley and shine a torch in the timing cover behind it. There is an arrow on the chain pulley that points up at TDC, this means the key on the crank is at 3 oclock position, and the second dot faces straight up. I'll check on the one I have out of the car later on but I dont think there is a mark on the timing cover, so just set the engine at TDC and get your white marker pen and make one. Make a line on the crank pulley instead of just that round dot while you're at it. You can also pull the number 1 spark plug and turn the engine by hand with a screwdriver/drinking straw/anything similar pushed into the spark plug hole to get TDC within a few degrees if the crank pulley is hard to remove.
  10. 1 point

    350Z+ G4+ questions

    distance to empty?
  11. 1 point

    VVT Settings for Mazda 3 Engine

    Hi. Is the problem a symptom like a movie? I am troubled with this symptom. Is Trig2 waveform changed in idlespeed and about 3000rpm?
  12. 1 point

    2JZ VVTI Monson ECU Map

    It is a Monsoon ECU so only has 4 inj outputs. It will be firing them in multigroup mode. Research what "absolute pressure" means. MAP = Manifold Absolute Pressure. 0Kpa MAP is total vacuum. 100Kpa MAP is atmosheric pressure at sea level (0Bar boost). 200KPa MAP is 1Bar boost. On top of that, all limiters have a "control range", for the MAP limit the default range is 10KPa, so if the limit is set to 186kPa, the limiter will start to limit at 176kPa (or 0.76Bar boost). Rather than ask us what is wrong with your map, it would be better if you explain what the actual problem is that you have and supply a log showing it.
  13. 1 point

    2JZ VVTI Monson ECU Map

    Both maps look almost identical. Neither look like they have been tuned on a dyno steady state as both the fuel and igntion maps are just too artificially smooth. Otherwise the ignition numbers look pretty normal. You have the MAP limit set to 186kPa so the engine is not going to run more than about 0.75bar. If you are using stock coils/ignitors then you might want to reduce dwell time to about 1.8ms.
  14. 1 point
    Usually there is good info in the "test calculator" to show how the parameter is scaled/stored but it looks like the detail for those parameters is missing. Usually we use unsigned integers with an offset to allow for negative values, so this is probably what you are seeing. I suspect it will be something like a 3G offset, so the accel can read from -3G to +3G. I will see if I can get some more detail for you tomorrow.
  15. 1 point
    It is a $98 tablet so wouldn’t surprise me It seems fine with the 12Hz so might leave it for the sake of some sympathy on the old V44 hardware. I think a hearty thanks is in order for your support through something that is essentially 3rd party. Really does not go unnoticed.
  16. 1 point
    Here's how you do it: https://drive.google.com/open?id=1_ynfTPGEdv66t1SfTVrf1hsk6QOM3AkX