Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 10/25/2018 in all areas

  1. Adamw

    PC Link New Layouts

    Hi All, The default layouts in the current G4+ PC Link are pretty dated, I recently done a couple of new ones that will be included as the defaults in the next PC Link update. But in the meantime here they are so you can use them now. FYI, if you use both G4+ and G4X ecus and you have highly customised layouts, you can copy the same layout into both PC Link versions by just changing the file extension. G4+ extension is .llg and G4X uses .llgx. Feel free to add to this post if you have any layouts you want to share. 1366 x 768.llf 1920 x1080.llf
    6 points
  2. Thats not a nice way how you say that. On every product you buy the updates stops someday and you have to invest in the new generation unit if you want get all the recent features. Besides I'm 100% sure you would have been in the same situation with the other ECU manufacturer. And if your fuel table is properly tuned, there is no need for long term fuel trims. I recommend to use Mixture Map.
    5 points
  3. Hi, My other car has been off the road for ages, and life has been in the way. So I thought it might be fun to just wire up my ECU into the Echo so I could have a play around with some tuning stuff again. It's a 1300cc economy engine so not going to set the world on fire. But a bit of fun. I need/want to revert it all to factory though, so I bought a spare ECU from wreckers and cut the plugs out to make a patch loom. This car has VVTI on the intake side, which means I could do my usual sweep through the vvti angles and see which delivers the most airflow into the engine.
    4 points
  4. Not super fancy, but I use a math block to filter my speed signal with the average function (av). Works really well.
    4 points
  5. 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 .
    4 points
  6. mldc

    Water Pump PWM

    Hello, Did some testing, results are below. Pump: Any pump CWA50, CWA200 or CWA400 would work with these settings. We use CWA200. Wiring: 1 - wired 12V from the PMU16, 25A channel. 2 - wired Aux high state signal. 3 - wired to ecu signal gnd. 4 - simple chassis GND. ECU settings: 50% on cranking is for waking up the pump. After that, You can use higher values then 50%. If your idle is lower then 1000 RPM, adjust the PWM table axis and values to suit your application. Results: Our race car working temperature is 70
    4 points
  7. Gregconboy158

    Unhappy

    To jump in on this I've always felt the advice and guidance from the team (Adam) to be 2nd to none, I've always had the help and resolutions I've needed and would in turn recommend link to anyone.
    3 points
  8. The pressure compensation is non-linear and applied to the pump current before conversion to lambda (also non-linear) so it is a fairly complex relationship, generally done with look up tables. I suspect that RBR calulator linked above uses some simplified equation as it seems to give very optimistic results for the NTK sensor. They are typically about 4 x more sensitive to pressure than the LSU4.9 in my experience. For the LSU4.9 there are a few slight variations of the pressure compensation curve but this is the one that is generally used from what I have seen: So a couple
    3 points
  9. I get that Link are a relatively small company, with limited resources. I'm not expecting large features to be back-ported, but there are a number of longstanding known bugs and issues with the G4+ range (cruise active light, as one simple example that directly affects me), and we feel abandoned, because there's something new and shiny, and existing features on our product aren't working properly. I'm intrigued to see the new advances coming in the G4x range, and I might be tempted to upgrade in the future, but I'm currently wary about upgrading and having another issue that's
    3 points
  10. 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.
    3 points
  11. 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
    3 points
  12. 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 run
    3 points
  13. 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.
    3 points
  14. Simon

    G4x Base map

    Yep Multi fuel and traction control will be coming
    3 points
  15. 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.
    3 points
  16. 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
    3 points
  17. 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.
    3 points
  18. 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
    3 points
  19. 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.
    3 points
  20. Disagree, Link already has a whole bench of different wire in ECU's, like no other manufacturer. Price diff is not that biig between Furry and Thunder to add another one. 2x DBW and only 1x Lambda does not make sense in most applications. Thats my oppinion.
    2 points
  21. To verify deadtime, you can set injection mode to multipoint group and switch the injection rate back and forth between 1 cycle and 1/2 cycle, while at constant fast idle. Lambda should settle to about the same value on either rate setting. If lambda changes when injection rate changes then adjust the deatime up or down until lambda is the same with either rate. Give it a few seconds to stabilize each time you make a change.
    2 points
  22. Knox

    G4X 2D launch control

    Thanks, I make driven wheel speed source to gp speed 1 (like driving wheels) and 3d mode with single axis like Vaughan wrote and works perfect now.
    2 points
  23. Thats a typo you have found there sorry, I will get that fixed up. Corrected note below. So yes you can use A8/Aux 8 & A11/Aux 7 for what ever you wish and you dont need to worry about A9/10.
    2 points
  24. I think some people need to be speaking to the dealers that sold them the G4+ ecus knowing fine well they were going to be superceded. I was all set to get a G4+ in Feb it was Paul @ TCB who actually told me to wait for the G4X
    2 points
  25. I think it is interesting technology when you look at prospects of closed loop peak cyl pressure angle control, but I think that is still a long way off the aftermarket world. As for ion current knock control, it is not very useful in anything but OEM applications, there are just too many combustion irregularities to allow it to be implemented in a DIY scenario. On the moderm BMW's with it for instance even a small change to the fuel mixture completely upsets it.
    2 points
  26. Yes, mixture map can be used from road logs. Set up a Transient filter Eng speed < 250rpm/sec and another with TP<5/sec will get rid of a lot of the inconsistent data. Here's a video I done for someone else earlier with some further info: https://1drv.ms/v/s!AiYbYlZQuRHPszz5hTxJ8ec0MitL?e=2JbDVh
    2 points
  27. Ducie54

    Cranking time

    Add pre prime fuel or increase it. Try lowering your injector timing table values, and make sure fuel rail volume does not drain back to the tank as it will take longer to build fuel pressure.
    2 points
  28. 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.
    2 points
  29. The V number on the base map file refers to the bottom board revision, so for your V1.8 board you should be using the Base map "Mitsubishi EVO 9 PCB V1.6+ G4+ Xtreme Plugin".
    2 points
  30. I wanted to share my success using a bluetooth adapter since I have not seen any other posts about using one on this forum. So far I have only tested it with an Android tablet and RealDash. It has been working perfectly. Connection is fast and very reliable. There is no noticeable lag on the dash interface. There are a few advantages of using Bluetooth over USB for a tablet dash. 1) The usb port on the tablet is freed up to be used for charging (this can also be used to automatically turn the tablet on/off with key power) 2) The usb port on the ECU can be dedicated to th
    2 points
  31. I have a couple of customers with the 1.8 VVT engine, they run great on the LinkG4+ wiring ecu. And they upgrade from the MS ECU actually, one of them because of a faulty regulator on the alternator. Without warning the alternator start to make spikes of voltage, and burn the MS ecu... We wire in the Link (without knowing about the problem), after just a few seconds of the first start, the engine shutdown. Looking at the log, we saw voltage of over 18V, the ecu cut the fuel and save everything, the ecu never burn like the MS. I have work with MS ecu, and have customers with them on, I really d
    2 points
  32. Adamw

    AVCS

    No, I used to think the same - it would be easier to use MAP for the VVT load axis as then it has more relationship to your VE table and it would then be easier to account for the change in VE due to cam position. But, as I have been doing more VVT recently I have learnt that theory is not true and it is better to use TP for the VVT load axis. The reason is that cam timing significantly affects the MAP, so if you have MAP as an axis on your VVT table, then in some situations you get the cam becoming unstable bouncing backwards and forwards because it is both affecting MAP and controlled
    2 points
  33. 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!
    2 points
  34. Here's a quick video to give you an example. Gear shift knock.mp4
    2 points
  35. 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.
    2 points
  36. I think with engine temps of 10°C and 94% ethanol you are going to struggle with cold start and there will be little you can do from a tune perspective to help. The vapour pressure of straight ethanol is very low so there will barely be any vapor in the port at that temp no matter how much fuel you dump in, it will just remain as liquid. Somewhere below around 10°C there is not enough vapor produced to support combustion. This is the reason why pump E85 gets reduced to E60-E70 in winter so there is a little more of the volitile solvents available to create some vapor in the port. In reg
    2 points
  37. Simon

    S15 plug in

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

    R8 Coil wiring

    Pin 4 is on the left, pin 1 on the right. Pin 4 is the main power ground so needs to be decent sized wire. Pin 2 is signal ground so can be smaller. Ground both to cyl head. Pin 3 is the ign signal from ECU. Pin 1 is +12V, again needs to be decent wire. Dont give these too much dwell, they pull about 16A at 2.5ms, I usually stick around 1.8ms which is about 8A.
    2 points
  39. 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.
    2 points
  40. 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...
    2 points
  41. I would say the timing doesnt look unusally high for 8.2CR with E85, but it also doesnt look tuned at all to me, it looks like someone has just made up the numbers. Why have so many rows with exactly the same numbers on them? You would be better to just delete them all. Seems pretty odd to have the same timing at 207Kpa than you have at 138Kpa. And as JMP says, that big step between 1500 & 2000 is gnarly.
    2 points
  42. Attached below. 1&2 are sensor ground. 3&5 are supply voltage (I assume 5V) 4&6 are AP sub and main. E-throttle Module Instructions.pdf
    2 points
  43. TechDave

    ARF Choice

    http://dealers.linkecu.com/can-lambda CAN Lambda
    2 points
  44. 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 mai
    2 points
  45. There we go. Granted the RPM line itself is smoother than what i suspected. Could be because of slow logging rate. What gives it away to me though is looking at the RPM ROC parameter. Thats RPM Rate Of Change. How much the RPM changes over a second. Anything over 0 meens RPM is rising at a certain rate and below 0 means its falling. We bot KNOW you are accelerating so the CRANK is certainly not slowing down, right? However you can see i both my screenshots that the ECU is logging a very erratic RPM ROC. It should ALWAYS be on the positive side when the engine is accelerating. That IS the
    2 points
  46. mapper

    Rotary switch

    I'm using AEM 30-2056 and for Highend Application Motec 9 Position. Doesn't matter much which one you use, it just should give you signals between 0 and 5 Volts. Besides, Adamw / Link ECU that would be a nice Accessory in your product lineup!
    2 points
  47. You will never see 300psi, nor will 2x1000cc nozzles be as efficient as smaller nozzles. Well other than when the pump is pumping against the closed valve and if the pump has been adjusted to see a higher pressure. In fact, with nozzles that large I'd be surprised if you ever see much over 100psi. The pumps simply do not flow what the suppliers claim, and any pressure claims are against a dead head. I've tested the AEM big pump under load and in the real world at pressures required....realistically they're only around a 1200-1300cc pump, and that was with a quoted 1600cc worth
    2 points
  48. 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.
    2 points
  49. 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 w
    2 points
  50. Okay so there are a few stages to setting it up. 1. Wiring Run one wire to the knock1 or knock2 wire on the link loom, and one to sensor earth, polarity unimportant. must must must must use shielded wire. The knock sensor outputs a very low voltage signal that's prone to interference. 2. Initial settings Since you are using the 'wideband' knock sensor and an engine with an ~86mm bore has a knock frequency in the ~6khz range select your Freq Channel as 4-10khz Wide Band. Set Ignition Retard limit to 0 degrees. Set the RPM high and low lockouts however you like. (500rpm likely not ideal for
    2 points
×
×
  • Create New...