Jump to content


Popular Content

Showing content with the highest reputation since 07/17/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
    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.
  3. 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, Monsoon, Kurofune or Black Storm 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 Blue Storm, Xtreme, Fury, Thunder, all Plug-ins & Force. 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
  4. 1 point

    Track-display logging with G-force sensor

    Hello It would be really nice if you upgraded the logging features to include a track view with the ability to render the track with the help of a g-force sensor or gps data import. Also with a simple Video render feature like the one AEMData have i think this would make Link both more of a "professional" tool (evaluate driving/chassis) and "in-line" with todays demand to use actioncams everywhere. These features with the "Vehicle plan" next to it would look really nice. Also when configuring analog inputs you are not able to input negative values even if you choose "Output units" to be "NONE", Only Celcius can go sub-zero and then you can change to NONE and keep the negative values. To be able to mount an aftermarket G-sensor it would look nice to have G as a Output units in the cal tables. And also a filter function if you really want to add support for aftermarket sensors and make the data look smooth.
  5. 1 point

    E throttle cl idle control

    I think this maybe the same bug that the original poster has, I believe this has been fixed in the next firmware version which should be released in the near future. Let us know if you still see something odd once updated.
  6. 1 point

    Installing monsoon into 13b pp help

    Current help file PDF attached Link Help_File_ENG.pdf
  7. 1 point
    An volt 11 & 12 on the expansion connector is correct as per the top photo. The second picture you show of the "pin functions" list is for the 2007 ECU, not the 04-06. So AN Volt 11 will work provided your wiring and cal table is correct. You can attach your map if you want us to confirm the cal table is set up correctly.
  8. 1 point

    engine stalls whith ac on

    Ok, your idle base position table doesnt look tuned at all. Your idle ignition control table is set up all wrong. Turn off the idle ignition control table while you initially tune the ISC. Set ISC back to openloop mode and follow the instructions in the help file. Once you have a good open loop idle, change to closed loop and follow the closed loop tuning procedure in the help file. Once closed loop is working reasonably then you can turn the idle ignition table back on and set up the table something like below then tune from there. Also, your trigger 2 is set up wrong, sync mode should be set to "Cam Pulse 1X", you have it set to crank pulse. You may need to check your base timing again after correcting that.
  9. 1 point
    Brad Burnett

    MAP problem

    I would try a different map sensor. May also want to see if there are any other trouble codes in the ecu.
  10. 1 point

    What ecu for dual DBW

    a Thunder would be my choice, no need for external controllers or extra complications: https://www.linkecu.com/products/wirein-ecus/g4-thunder/
  11. 1 point
    The s13 base cal in the software should be good enough to get you moving with some small adjustments.
  12. 1 point
    Absolutely! I run the older one in my drag car, remember that the older cas is adjustable and you need to use a timing light to set the base timing after you install it and get it to run.
  13. 1 point
    ROC stands for Rate Of Change. Or dRPM (delta RPM) if thats a more failiar term. Its a parameter that tells you how fast rpm is changing pr second. If it rises from 2000 to 3000 rpm in one second you have a value of 1000. Does it use 2 seconds to do the same ROC is 500. If rpm is dead stable ROC is 0. In the attached picture you can see an example. Base timing in that is 12 degrees but when rpm drops when i clutch the car (it is usually more than -1000 dRPM) timing is at about 22 degrees falling towards idle arget. Dropping as dRPM drops. Thats not a screenshot from the link software but the same can be done there.
  14. 1 point
    If you change the y axis from etc (which you really arent using anyway) to rpm roc you can fix the idle ignition going low when you dont want it to.
  15. 1 point
    Need to get an OTG and charging solution before making the mounting more permanent but it functions very well.
  16. 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
  17. 1 point

    Mixture map defined by log window

    Yes, I think this is needed too and I have put it on the wish list.
  18. 1 point
    I took the laptop down to the shed last night, worked straight up, no mess no fuss.
  19. 1 point
    Yes you can do that. I did it with my 3sge beams Altezza plug in when I went to ITBs. Although now I have made the ITBs DBW. LOL.
  20. 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.
  21. 1 point

    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.
  22. 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.
  23. 1 point
    will borrow a HoloLens from work to see how it looks on that given it's supported
  24. 1 point

    E throttle cl idle control

    I've expierienced the same problem. Besides it seams no possible to find good PID Settings which control idle very precise and makes the throttle enough fast with less overshoout at big changes. I use a 82mm throttle on 2,2 liter engine, means idle is controlled within 1-1,5%. Even with idle control turned off, the PiD controller oscillate slowly arround target especially when in gear, because TP seams to jump once integral has summed up enough to overcome friction. Think the push-pull driver must apply current from both sides to control and hold the throttle with more force arround idle. I've used Nichols Ziegler methode, measured step response, phase margin etc. to adjust PID's. I also tried Link VDO PID (which oscillate heavy after a step btw!) and spent a lot of time to find sensible PID empirically. Unfortunatelly nothing seams to work well for idle. Bad E-thrrottle idle control was discussed a lot over past years. Think it's really time that link engineers investigate into this Problem.
  25. 1 point

    Closed Loop fuel trims

    Hi Marc Good to hear back from you. How much does your AFR oscilate? Where is the wideband located? Depending on position, you need to adjust Lambda rate and Gain. You should do some testing. Tune your VE table with CLL off as good to your Target AFR as possible. Adjust your target AFR table to the rich side with one task by the amounts listed in the gain table 0,33 0,66 etc. And log, with a high logging rate, how long the sensor needs to get to a stable reading. Lets say it needs 0.3 seconds. This means your frequency in the lambda rate table may be max. 1/0,3 = 3.333 This test should be done at different loads and rpms to work out best CLL settings. Best place to do that is a load bearing dyno.