Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 08/05/2018 in all areas

  1. 4 points
    mapper

    Ethanol Content Clamp Function

    The continental Ethanol Content Sensors will read significant lower when low flow goes through the sensor. This means during a WOT run the ethanol content will read significantly lower at high load and rpm than at idle, because the flow in the return line is low. I attached a Log to show the problem. With more boost, I see values 20% lower at WOT than at idle. This is a well-known problem and other ECU manufacturers have an Ethanol Clamp function for a good while. The Ethanol content does with activated clamp function only update when the Injector Duty Cycle is below a certain level. Once the INJ Duty Cycle is higher than the threshold the ECU takes the last value read below the threshold and update Ethanol content only when InjDC goes below the threshold. So a quite simple function, but with a big need! Please implement it asap. Thank you.
  2. 4 points
    Adamw

    Logging setup for ECU logging

    Yes, that was one of the first Efi engines I done about 20 years ago when I was a teenager. Motec M48. Couldn’t get many SR20 parts in those days so had to make throttle bodies, camshafts, dry sump system etc from scratch. Datsun 510 rally car.
  3. 4 points
    Guys relax a bit. I've mapped and I'm supporting several 600-800hp 2.0 to 2.3l time attack engines/cars with a Link ECU and multimap strategy. Such an engine runs usually for 5000 race track kilometers until a rebuilt is needed. That's a similar distance to a 24h race. I like to answer your question.: All LINK ECU use the same PC-Software and the same Firmware. The main difference between all LINK G4+ ECU's is only the hardware. your tuner should tune the main Fuel and ign Maps from the lowest to the highest boost levels. There are 3 main Boost Maps in the LINK ECU. You can additionally span one of the axis of the Boost Wastegate or Target table to a driver Rotary Switch. So it's possible to have up to 33 different boost maps, which all can be switched on the fly. On top of that, you can activate 4D fuel and ignition tables on one or several of the boost maps. This allows trimming Ignition and Fuel on some maps if you or your tuner like to do that. The Link Ecu is really flexible. Usually, the only limit what you can do is the creativity of the tuner. As an example, we installed 3 rotary switches in a Time Attack/ Hillclimb car. One 12-Position Rotary Switch is used to choose between 12 different torque maps (mainly altered by boost strategy). The Launch RPM can be chosen over another 12-Position Switch, depending on whether and Track conditions. And lastly, we have a 3-Position Rotary Switch to choose one of 3 Drive by wire Throttle Maps. For engine Safety, we set up Limits for too low and to high Coolant temp, Oil temp, Oil press and Fuel press. We are also using full time closed loop lambda and sending a lot of Data over a custom CAN. As you see, the LINK is a very capable system. But as every ECU, it needs a capable tuner to use it properly.
  4. 3 points
    Dave Kriedeman

    NEW WEB SITE IS STUNNING.

    Hi all, I just wanted to congratulate the team at LINK on a truly stunning upgrade to their WEBSITE. The colours and the layout etc really catch the eye. Very pleasant to scan through the pages. The format is very well laid out. Also not just the WEBSITE, but the company and products in general. I have been with LINK as a user and dealer since the conception of ViPEC and it has been sure great to be part of and also a witness to the transformation and growth of an already great product and company to a world leader in the Electronic Fuel Injection Industry. I have also really enjoyed working with the LINK team over all of these years and hope to continue doing so. So congratulations LINK and very well done. Keep going on this fantastic journey. Regards Dave Kriedeman PRO TUNING.
  5. 3 points
    Simon

    G4x Base map

    For those looking for a base map to have a play with. Software can be found at http://www.linkecu.com/pclink/PCLink 6.15.15.exe Monsoon FW 6.15.6.pclx
  6. 3 points
    TechDave

    Share your Math Channel List

    So this afternoon I sat at the simulator and started mucking about with a few ideas. I wanted to calculate my average speed based on some event, I used a digital input latching on. In the UK we have average speed camera zones, you get snapped at the start and end and they do a distance over time calculation. Often you'll get slowed down by a Karen in an X5 not paying attention, I've always been curious how much I could safely speed up again to catch back up to 50 mph average over the trip. You can do this in log analysis with the statistics view, but this is obviously operating at runtime. So there's a few things here I've done that aren't documented yet, yes they will be. The first is that maths channels can do reassignment, x = x + 1 etc The next is that they're evaluated at 1000 Hz Lastly I know of a few built in functions too. I figured out two methods, of averaging, the first could be used not only for wheel speed, but for really any parameter, lambda, throttle position, you could use another maths function to find lambda, vvt, boost, etc error then feed that function into this one and have an average of error over some time period. This one uses this algorithm: newAverage = oldAverage + (newSample - oldAverage)/sampleNumber the cnt function is a real good cnt function, it counts 1 per cycle (so 1 per millisecond) while c is greater than or equal to 1, so if you feed it a status which evaluates to 0 OFF and 1 ON, then you're away. If you want to use this for Anti-Lag active we might have to get a bit imaginative about an offset, iirc Anti-Lag OFF = 0, ON = 1, Active = 2...etc I had to add a +1 to cnt because on the first cycle it's 0 and that's div by 0, plus the first cycle is the 1st sample too. The 2nd method I came up with was to calculate distance, which of itself is a useful function, then calculate distance/time, again using that good cnt function: Again using reassignment in the Distance function, multiply speed by 1/100th of a second, of a minute, of a hour to get distance travelled per millisecond (rate is 1kHz), I multipled by status to simply switch it on and off. This gives me km. distance a over time, divide by the same multi as above gets us back to an average. You don't need to use 8dp for this, I was just using it while getting my exponents sorted. My functions agree with each other and track to my expectations, but if you spot an error in my maths then shout out edit: unfortunately this is all in kph as I started running out of characters to add the mph multiplier, I've spoken with engineering and we'll see if we can get the length increased, 2.77e-7 helped a lot, but still lost a bit to parenthesis too.
  7. 3 points
    Ducie54

    G4x Base map

    As a feature request can we have the option on which Lambda sensor is used for CLL. As example I'm using 5 lambda sensors. One in the turbo dump pipe and 4 in the turbo manifold using a CAN module. The software uses a average for CLL but would be nice to use Lambda one so manifold pressure is not an influence. Currently to get around this from happening I've set the 4 CAN lambdas as CAN TC.
  8. 3 points
    Simon

    G4x Base map

    Yep Multi fuel and traction control will be coming
  9. 3 points
    Hey everyone, I know you've been hanging out for this one. PCLink Version 5.6.6 3564 (DLL rev 3544) 15/08/2018 New Features Right Mouse Click on a time plot to add a marker or section. File Directory tab in Options window lets the user specify a folder to always load from/save to Hinged axis titles in Surface View. Locked Surface view (similar to old surface view behaviour) Chinese language added coming soon Spanish language added also coming soon Changes Some lists have had their default layout changed (alphabetical still works) Minor improvements to the Logging Setup window. Minor improvements to parameter selection. Improved b marker drawing on the time plot. Changed how parameter colours are named (see Parameter Menu and Setting up a Dial Gauges Runtime Values for details). Improved consistency of keyboard shortcut keys across PCLink. Searching CAN Parameters now takes into account transmit/receive filter. Fixes Fixed few bugs with saving log files and holding F8 key. Fixed bug in Aux Output where Diff Fuel Pressure was not triggering correctly. Fixed bug with compare file and cell colours not changing. Fixed bug where PCLink would crash if the computer (laptop) was put to sleep. Fixed Cal tables 1-3 from wrapping around when output table start is set to a -ve number. FP Speed Table now resizes correctly when double clicked. DI14 now displays wheel speed label properly. Imperial units in table axis setup improved. Surface Graph fixed for Nvidia graphics chipsets. G4+ Firmware Version 5.6.6.3557 – 15/08/2018 New Features Added trigger modes for LS2 with moved cam sensor, Rover K series with CAM sync, Nissan VQ35HR and Mitsubishi Colt 4g15. Added Astra CAN mode. Added Single-Point Every TDC Injection Mode to activate all injectors on every TDC for throttle body injection kits. Added CAN stream for Link AIM MXS Strada Dash. Changes Added 3D tables option to Closed Loop Lambda FTrim Limit. Added options to GPOutputs. Added Cruise Control power toggle switch mode. Fixes Remove unused settings from Kurofune and Monsoon. CLL dual channel mode now controls the second bank. AFR average is now averaged correctly. Add 3D Secondary Injection Deadtime table. Fuel Pump FP table now interpolates correctly. Knock Control High RPM lockout has been increased. Gear Status can now be written from CAN input. Fuel pump mode “80Hz 33/66/100 %DC” now reports duty cycle correctly. Cylinders 9-12 now trigger injectors when configured as Semi-Sequential Injection. Solenoid Idle Speed Control now shows status correctly. Stepper Idle Speed Control now stops at the Minimum Clamp. As always, make sure you save your basemap, do the firmware update, load your basemap, then do a compare to check changes. https://www.linkecu.com/software-support/pc-link-downloads/ Post any issues you have here, rather than starting new threads, or my favourite, at the bottom of a completely unrelated thread.
  10. 3 points
    Adamw

    What is wrong with my tune?

    I just had a quick look. There is some pretty odd stuff in there. It looks like it has been tuned for flex fuel but there is only one ignition map and no other corrections for ethanol content. Usually E85 can take a heap more advance than petrol so what fuel was that ignition table tuned for? VVT looks like the offsets are set incorrectly. The RH inlet cam is showing 10deg advance when it is in the fully home position. That means it will be getting 10Deg less than what is commanded. The VVT and ignition tables both have big "holes" in them around the cruise area that is going to make it drive pretty horrible. Boost control not working great at all. Fuel control is not great either. I would say this is due to there only being 1 VE table set up, which doesnt usually cover flex fuel well enough especially when injectors havent been flow tested on both fuels. I think the saving grace is you are running it on relatively high eth %, which is relatively forgiving. I wouldnt give it a hard time especially on petrol until it is looked at by someone more competent or interested. If you want to PM me the tuners name I will pass it on to the right people to consider.
  11. 3 points
    Adamw

    X-SERIES AEMNET CAN BUS GAUGE

    this is all you would need to send lambda from a fury internal wideband to the aemnet gauge. this would be channel o2-1 on the gauge.
  12. 3 points
    Thank for Realdash developing such a powerful app that I don't have to buy expensive AIM racing instruments. My car is Subaru GRB, ej25 with link G4 + thunder. I developed a protocol conversion module using STM32. Then can convert the Can signal of the link G4+ into a Realdash protocol, and then connect to the mobile phone through a TTL to Bluetooth module, so as to display almost all the data on the mobile phone (as long as the PClink can display). Welcome to exchange SM-A6050_20181227180733.mp4 https://www.youtube.com/watch?v=fNeBGatmBSc https://www.youtube.com/watch?v=eKJzVRUp09c
  13. 3 points
    mapper

    Nos control

    I think its much better to have all universal function like virtual aux, timers, 4D, 5D, fual fuel table etc. than a dedicated NOS function. This way you can build your own NOS function excatly how you want it. You just habe to be a bit creative with the universal functions.
  14. 3 points
    Adamw

    CANBUS OIL Temp from AN8

    Hi Mark, I suspect the problem is your oil temp sensor being on a AV input is not actually assigned to the "oil temp" parameter but rather a "GP Temp" parameter that is not sent in the standard generic dash stream. Attached below is a configurable version of the generic dash stream where I have replaced "oil temp" with AN 8 - Oil temp. MarkHellier.lcs For any others that want it I will also attach an un-modified configurable generic dash stream. Configurable Generic Stream.lcs
  15. 3 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.
  16. 2 points
    Davidv

    dashboard arduino

    Forget about the CanID you really need to think about Frame ID instead. Your frame ID takes up one of the bytes in the message. So in this example below, it is Frame number 13 . When this can frame is received by your teensy, you need to look a that first byte to tell you which frame it is. If the number is 13, then you know that your values in the frame are Inj timing, Ign Angle, and Inlet / LH target. So you can update those values.
  17. 2 points
    I don't have any experience with that particular motor but you should just need to connect your trigger 1 to the crank sensor (I assume the 1.8vvt motor has a crank trigger unlike the earlier 1.6 with cam sensors only) and trigger 2 to your cam sensor. Connect an aux (one of aux1-10, aux ign5-8 or aux inj5-8) and a switched power wire to the vvt solenoid. That should be all you need to do specifically for the vvt wiring. You might have to add wires to the loom for inj3&4 to run sequential fuel as they are connected to the ECU header but the earlier vehicles don't use them and so might not have wires connected to those pins. Other than that have a look through the plugin pinout and the loom in your car to make sure you have all the wires you need to do what you want, you may even be able to use another pin like aux7 (purge) for your vvt control instead of adding an expansion loom. One final note, the factory wiring for the early mx5s has the MAF turning on the Fuel pump so you may want to rewire that.
  18. 2 points
    dx4picco

    Ignition Corrections

    4D ignition table with gear as one axis.
  19. 2 points
    orlando bello

    Engine protection

    Would like to have more gp protection rpm limits tables. Not only rpm limit but also warnings under conditions.warning pop up on dash .
  20. 2 points
    Thanks guys for the quick response! I have to say the help documentation is some of the best I've ever seen for a bit of control equipment. Keep it up!
  21. 2 points
    Adamw

    GM IAT Sensor Calibration on V44

    The GM sensor uses the same calibration as the link sensor so you dont need to change anything. If you are still getting a t2 @ 5V error that means the ecu is not seeing any sensor connected (open circuit). It could be a bad connection or dead sensor. You can confirm the sensor is good with a multimeter, it should measure around 3000-3500ohms at typical room temperature.
  22. 2 points
    You are correct, spark duration and arc duration are the same thing. In your case this setting may only just start to come into play a high rpm. The spark duration setting usually only comes in to play when you have a distributor with single coil and more than 4 cylinders. It is used to shorten the dwell at high RPM when there is not enough time to both charge the coil and spark for the full duration. As an example think of a V8 with a distributor running at 6000RPM. At 6000RPM one engine cycle (two crank revs) takes 20ms. All 8 cylinders have to fire in that time. Lets say your coil needs 2ms of dwell to charge and the spark lasts for 1.0ms. You have to do that 8 times in those 2 revolutions, 8 x 3ms = 24ms - but wait - you only have 20ms to do that in? The ECU cant do anything about the spark so if it knows how long the spark needs and there is not enough time then it can shorten the dwell to make everything fit into the time that is available. A rotary in direct spark mode at 8000RPM will have 7.5ms of cycle time to charge and spark. So if you have a spark duration of 2.9ms that leaves you with about 4.6ms for dwell. You generally dont need much more than 3ms on those coils unless very high boost or Methanol. With it set at 2.0ms now is not a big problem because as you can see it is quite likely you are not running into cycle time issues anyway.
  23. 2 points
    You can connect both 5v and 12v sensors (and VR sensors etc that have varying voltage output) all to the same sensor ground. The reason to chose 1 type of ground over another is not input voltage, but more: 1) how stable does the signal need to be for the engine to run well (crank trigger = really important, any of the temp sensors = not a big issue if the signal bounces around a few percent). And as part of this, will a ground offset cause an incorrect reading that still looks legit. (eg voltage offset on any analog sensor) 2) How much load is expected to go through the ground circuit. eg do not use a sensor ground as the ground side for a vtec solenoid or anything like that. As long as everything on the sensor grounds is low *current* then adding a flex fuel sensor to sensor ground wouldnt hurt, and generally anything that is an ECU *input* you would lean towards putting on the sensor ground circuits. But if you do see issues that seem like sensor noise once you add it, you can probably move the flex sensor to use a direct ground and not see too many issues. These dont report an analog output anyway so should work just fine with slightly noisy voltage/ground.
  24. 2 points
    Brad Burnett

    AEM Water/Meth Boost Safe

    Can wire that wire into a digital input on the ecu. Then could configure the ecu to change boost, timing, and fuel values when that is active.
  25. 2 points
    Ducie54

    G4x Base map

    Is it possible to have a Math block drop down box with the maths all ready worked out?
  26. 2 points
    TechDave

    G4x Base map

    @Ducie54 I get that if I haven't turned on a fuel mode yet. Switch on a fuel mode and you get it, I'll add a note to the engineers to show a message "no fuel mode selected...blah blah etc"
  27. 2 points
    Simon

    MR2/ST205 and Knock

    Highly likely.
  28. 2 points
    Ok, all the CAN is done, I havent added any of the new channels to displays or whatever but they should now be available. I have kept all the channel names pretty much as per the BPM datasheet. The only one that is a bit ambiguous is Fuel level. He has used 2 bytes like it is expected to cover a large range of numbers but then says the range is only 0-53L. Just one byte can do up to 255 and 2 Bytes is capable of 65000. So I suspect he might be sending it as "0.1L" rather than whole Litres but that is not clear. If your fuel level says "500 Litres" when you have it all working then set the scalar to 0.1. Marvin-LinkG4UpdatedV2Port2CAN Adam.aemcd7
  29. 2 points
    Yes, Spartan has a termination resistor built in and it is enabled by default. I would use the Spartan in its default mode, use 1Mb/s and 1024 as ID. Use the attached stream definition. From the testing I have performed, the Spartan doesn't actually work in Link mode, the stream appears to be incorrect. (you would have needed to log in via serial bluetooth to change the mode/ID to Link CAN Lambda mode) HTH, Richard. Spartan3ADVDefaultMode.lcs
  30. 2 points
    Richard Hill

    Thunder lambda wiring - 12v

    Here are some measurements from a single 4.9 Lambda sensor running on a Thunder on the bench. The maximum the sensor drew was 1.43A at the end of the heating phase
  31. 2 points
    Sorry I haven't logged in for ages. Have just seen your comments are re-uploaded photos, should all be good now.
  32. 2 points
    I see, I wish that it would always ask if I wanted to load write the changes to the ecu, no matter how large. Because when it just loads the config out of the ecu and doesn't notify about anything, it's easy to think there were not any changes in the tune file. Then you carry on, tuning the config loaded from the ecu, until you realize there is no filename associated with the open tune file. Then you have to open the old file and see what's different, plus the changes you've recently made to the config file that was automatically loaded.... I've lost a good bit of time this way. If it's not possible for PCLink to ask if you want to load a tune with large differences, there should at least be a dialog that notifies what's going on (tune uploaded from ECU is replacing the open tune).
  33. 2 points
    Simon

    S15 plug in

    Jump on and download the PC link tuning software. The help file will have 99% of your questions covered.
  34. 2 points
    Adamw

    Link monsoon wiring

    I think I would avoid that, it looks very suspicious. Look at the main connector, it is missing the housing and looks like the wires are attached directly to the pins??
  35. 2 points
    Adamw

    ECU Unlock fails

    Someone has done a typo by the looks, The last two characters should be b7, not 67.
  36. 2 points
    On my setup I use a 3d table to PWM an engine water pump. After a lot of testing I found using the temp output from the radiator and ECT the best way to control the pump. Takes into account out side temp and vechile speed. Would recommend you try that way to control the thermostat. Ive also connected a 2nd Digital output to the same soild state relay as an override. So if I'm at a set TPS or boost range the pump goes to 100%. After a bit of testing during different conditions I can keep the ECT within 2deg in all situations.
  37. 2 points
    Richard Hill

    programmable logic

    I moved away from using generic dash as it employs a compound CAN message, which can be a bit of a mouthful for both the ECU sending and the device receiving. I prefer to use messages which are split over several CAN IDs such as transmit generic dash 2. The only problem with Generic Dash 2 is there's appears to be a bug in the non driven wheel speed (1 byte assigned, but shows as 0-1000kph, guess the text was copied from generic dash). Not a problem though if you aren't planning on going more than 158 MPH...
  38. 2 points
    Im not sure if you are asking a question or making a statement? Of course the fuel table and ignition tables (and all other tables) will need to be tuned to your specific engine before it will run well. It sounds like you dont even have a good grasp of the basic fundamentals yet so Im reluctant to advise you touch it yet. I would not attempt to tune a turbo car with this level of understanding. I would suggest you start by doing something like the low cost EFI tuning fundamentals course here to get a better understanding of the theory behind it: https://www.hpacademy.com/courses/efi-tuning/ If you try to tune without a good understanding of the basic theories then it will just end in disappointment.
  39. 2 points
    I had time to play with this today. It looks like you can make it work as is. In the ECU's that dont have the serial data stream settings visible In PC link, it seems that the "requested short" data stream method is enabled by default. Realdash is compatible with that. In PC Link set the baud to 57600. In Realdash set the baud the same and set it to "use short datastream". Let me know if it works for you. I tested it on a couple of my test ecu's and it seemed to work.
  40. 2 points
    We see lots of wideband controllers here, the worst for sensor failure are AEM, Innovative seem to be better, there is a noticeable difference as you really don't see sensor failing that often on the LINK CAN Lambda, we put the sensor failures down 100% to the heating strategy not shocking the sensor and allowing time for residual water / condensation to be cleared. The other thing is that the AEM sensor supplied with the kit does not appear to be bosch, but although you could argue that is the reason they fail, replacement genuine bosch dont seem to last that long either. That is the main reason we try and get people to buy the Link sensor and we always ask about the placement of their Lambda bung. PLUS you get EGT with the Link CAN Lambda an invaluable device that has saved my customers $1000's in turbo rebuilds.
  41. 2 points
    Adamw

    Closed Loop fuel trims

    Yes, in the next 5.6.6 firmware the CLL trim has 2 fully configurable 3D tables, so you can have different limits for adding fuel than for subtracting fuel and have those limits mapped against MAP, RPM, or almost any other parameter you like. I dont think the release is far away.
  42. 2 points
    Adamw

    12v PWM Output

    The aux outputs have a pull up resistor to 12V, so they are 12V when "off" and ground when on. These can be directly connected to an aux out with nothing extra. As Richard says though, the logic may be inverted ie 0% = max flow 100% = min flow, I have set one up before but cant remember if they work that way or not. What is important though is they need a 3ms "wake up" pulse, so to do this you have a cell in one corner of your PWM table that it will always pass through during at startup (say 500RPM), then you can drop back to normal numbers after that. Use 150Hz frequency and 50%DC to give the 3ms. Read this for the min/max DC: https://www.tecomotive.com/download/PWMinfo_EN.pdf
  43. 2 points
    ayjayef

    Trigger Errors - troubleshooting?

    Good to hear I'm not the only one ever to be confused with that. Even knowing to imagine another wave in the missing teeth gap makes my brain hurt. I can see it sometimes. That fixed it! Was 245deg and now -119deg offset (after a 4deg timing light adjustment). Trigger scope during idle looks good and NO TRIGGER ERRORS! Starts easy now, timing is steady, idle is good. Now we can actually start tuning. Thanks for your patience and odd hours troubleshooting! Log 2018-11-12 9;11;38 pm-idle.llg Trigger Scope Log 2018-11-12 9;08;33 pm-idle.llg
  44. 2 points
    Another way to work around the missing inputs on the Thunder (or to divide an input frequency down on other ECUs) is to use a CMOS 4018 IC. No external components required and can be powered from the ECUs +5 Volt supply. To divide by 10, the inverted Q5 output is fed back into the data input pin. I used this last week to divide by 8 on a fury (I fed back the inverted Q4 pin to data) Hope this helps, Richard.
  45. 2 points
    Adamw

    Traction control with DBW

    E-throttle is generally too slow to be the primary torque reduction to control slip. I believe there are some ECU's that use DBW as part of the TC strategy but it gets far more complicated - basically they will still use a traditional fuel/ignition cut as the primary torque reduction to get the slip under control quickly, then only reduce throttle if the cut has to be applied for a sustained period of time. I have played with it a little before (you can put slip on one axis of your E-throttle target table if you want to experiment) but found it to be pretty useless. To reduce torque by say 20% with an ignition cut you only need to cut 2 out of every 10 sparks. To reduce torque by 20% using throttle only on a typical turbo car you need to close the throttle by something more like 50%. What's worse is if you suddenly regain traction you then have to move that throttle all the way open again and wait for the turbo to come back to speed before you have full torque recovery.
  46. 2 points
    Adamw

    Blown engine!

    Coils running low on energy is just going to cause a misfire, it is not going to harm the engine.
  47. 2 points
    iecku.tavea racing

    3sgte knock gain

    Attached a typical 3SGTE Gen3 Knock Setup with the Bosch Sensor....
  48. 2 points
    Richard Hill

    turbo potentiometer

    As Simon mentioned, you will need to wire the output of the potentiometer to a spare analog input (with the other two pin on the pot wired to +5 Volts and sensor ground). AN Volt 4 is shown in the example below. Then select a spare Cal, I use 4 as it is a 2 point linear cal instead of a table. Next, in the cal settings choose % as the output unit. IT doesn't have to be %, you could leave it as 0-5 Volt raw. I would start with open loop boost control, as you will need to find out what duty cycle is required to achieve a particular boost target. In the wastegate %DC table, select the an volt input as the y axis and populate the table with the %DC required for each boost step required. In the example above I have used 50% duty cycle as maximum boost. That is the easy bit done! I would suggest looking at the help file for information about setting up boost control and when you are happy with the open loop mode, progress on to closed loop boost as this will give you more consistent boost levels which will be met and maintained by the closed loop algorithm. Regards, Richard.
  49. 2 points
    RVL

    EGT Conditioner

    Hi Guys, EGT-K 2CH power consumption is ~2-3mA @ 12V. OUT ground is internally connected with IN ground. Sensors ground in your ECU is chassis ground with separate filtering for analog circuit - right? You can connect it in two ways: Using vehicle ground (chassis ground): - EGT-K OUT signal to Adc input in ECU - EGT-K OUT ground left floating - EGT-K VCC input to +IGNITION or +BAT - EGT-K GND input to -BAT or chassis ground. Using ecu sensor ground: - EGT-K OUT signal to Adc input in ECU - EGT-K OUT ground to ECU sensor ground - EGT-K VCC input to +IGNITION or +BAT - EGT-K GND input left floating Both cases will work. Second case will be more immune for external noise on ECU's power line. Hope it helps.
  50. 2 points
    mapper

    Closed Loop fuel trims

    Regarding Lambda control error correction table. I spend alot of time to tune these. The base map is adjusted the wrong way around. Because the error correction tables is a % corretion of actual error, you want big corrections like 15% on small errors (0.03 lambda error) and small correction (like 5%) at the biggest error on the table. This is because a fuel film built up first in the ports when big correction are applied. This means it needs several burn cycles to get the whole change applied and measured. This means lambda control applies big changes two or three times for big corrections which leads to Lambda oscillation. On small changes fuel film built up is much less. Lambda change is done and measured much faster and within same burn cycle. This means the Lambda correction can be set much higher, because the change in AFR is measured instant. I have attached a tuned example.
×
×
  • Create New...