Jump to content

TechDave

Members
  • Posts

    212
  • Joined

  • Last visited

  • Days Won

    27

Reputation Activity

  1. Thanks
    TechDave got a reaction from Ducie54 in 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"
  2. Like
    TechDave got a reaction from mapper in 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"
  3. Like
    TechDave got a reaction from Davidv in G4x Base map   
    Just fired it into the issue tracker, cheers @Davidv
  4. Like
    TechDave reacted to Davidv in G4x Base map   
    Just a note 

    If you go to add calibration data to a sensor, use Cal table 1, if you space them apart at say 0.5v, 1v, 1.5v etc 

    It ends up reverting to full numbers and then does weird stuff if you look at it in the map view by pressing K 

    So the cal tables need some bug fixing to be usable (unless it's a quirk of this empty basemap)

     
  5. Like
    TechDave reacted to cj in help for porsche 986 2.5   
    So basic engine/idle theory... **assuming your trigger1 offset is correct**
    engine power output is from compressing & igniting fuel + air. The more fuel + air you have in the cylinder, the more potential power. The ignition angle (ie "when" you ignite the mixture in the 360* cycle) determines how much of that potential power is actually created. In 95%+ of petrol/ethanol engines, you "control" the air intake, and the computer/carb adds an appropriate amount of fuel to match.
    To have a stable idle, the engine output power (torque) must equal the amount required to keep the engine turning over. Any less & it stalls, any more and the revs increase.
    So the 2 levers you have to pull to get a stable idle (at any rpm) are
    1) how much air you let in
    2) what ignition angle you fire the spark plugs at
    You are only changing #2 here, but it sounds like you have #1 a bit off vs the factory specs. 25* ignition at idle is quite high, so I suggest you need to increase the air flow at idle - either idle stop screw on the throttle, or increase the idle control settings in the ECU to allow more air. You will then see your idle jump up to higher rpm, and when you reduce the ignition table values it should come back down. I cant give you exact values, but typical factory ignition idle angles are usually in the 10-20* range, and in your case it sounds like the manual says 5*. You dont have to match this exactly as your idle numbers can also differ from factory, but its usually a reasonable starting point.
    You are extremly unlikely to have knock or other spark related damage at idle speeds, so there is no real "dangerous" ignition number for idle, its just what works well for your car. Knock only becomes an issue as the engine comes under mid-high load (note that low rpm can still be high load however when you press the throttle hard)
  6. Like
    TechDave got a reaction from Simon in OBD II Android is a Joke! Seriously??   
    We have a really nice colour display:
    http://dealers.linkecu.com/MXS_street

    Completely customisable, you can display any parameter inside the ecu over CAN Bus.
  7. Like
    TechDave reacted to ZipTieTECH in LINK G4+ and IQ3 dash communication help   
    UPDATE!
    So i have connected my Racepak IQ3 street dash finally after 3 days of tinkering around with the software. Turns out that when i installed the program from the USB Drive, I needed to download all other data for IQ3 dash configurations. It wasn't giving me the EFI channels for the Link ECU configuration. I followed the steps on Racepak's Datalink2 software to configure for link (emailed tech support) and then i configured Link with the instructions that Adamw posted above. I have only tested water temp and TPS so far. I have not checked if everything else works because I haven't finished setting up the ECU. i need a few more sensors before i start up the car.
    I appreciate the help!
  8. Like
    TechDave reacted to Tim D in New ECU has died   
    Thanks all for your help guys!
    It turned out to be fuse number 11 in a fusebox I didn't know existed!  Hidden away behind the immobiliser keypad, which you have to pull off it's hinges to reveal the fuses.
    Apparently this fuse feeds Engine ignition system and SRS airbag.  It pretty much immobilsed the whole car!
    Not sure why it blew, perhaps I have an underlying fault that will come back to bite me!
    Thanks too to https://shopbhp.com/ - great tech support as always
  9. Like
    TechDave reacted to cj in Repeating Fault Code 75   
    Unfortunately that log doesnt contain values for TP Error Accumulator or TP/Target Error Accumulator. If we cant fix it here, add these 2 into the logged parameters for next time so we have better info next time it faults.
    For now, we can see here that the accel pedal has no issues and rule that out - both main and sub track nicely together and show no AP errors
    Comparing TP main & Sub we see the 2 of them track together quite nicely so its unlikely to be a TPS error. These 2 values seem to be within 0.2 - 0.3 at all times which is fine.
    comparing e-throttle target against TP main & Sub postitions however, we see that every time you get off the throttle, the TPS postition almost "bounces" back up a couple %. Usually this is caused by PID setting issues in the ethrottle control. in your case it looks like they might be a bit too aggressive, and its causing some pretty bad overshoot (and for it to not quite oscillate, but still jump back in the wrong direction once it overshoots). This screenshot shows the worst example I could find of both the "bounce" when you go from full throttle to 0%, and for general poor tracking of target -> actual TPS angle. Note the blue TPS line overshooting by 10% ish repeatedly between 10:04 and 10:08. There is another good example at 13:40 +/- 5 seconds.
    I'd suggest setting your ethrottle to "always run", then with the engine off, tune your PID settings a bit while logging these same values, until you get TPS to track target reliably thorugh both slow and fast throttle transitions

  10. Like
    TechDave got a reaction from fdenes in Force GDI no output on DI pump driver   
    Attach your basemap or send it to [email protected]
  11. Thanks
    TechDave got a reaction from iecku.tavea racing in ARF Choice   
    http://dealers.linkecu.com/can-lambda

    CAN Lambda
  12. Thanks
    TechDave got a reaction from Zuni_R33 in ARF Choice   
    http://dealers.linkecu.com/can-lambda

    CAN Lambda
  13. Like
    TechDave got a reaction from MagicMike in [UPDATE] PCLink 5.6.6.3564 (on hold)   
    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.
  14. Thanks
    TechDave got a reaction from bocia79 in start attempt force gdi   
    Correct.
     
  15. Thanks
    TechDave got a reaction from bocia79 in start attempt force gdi   
    Hi guys,

    I'm based in the UK, send your basemap to [email protected] or attach it here.
  16. Thanks
    TechDave got a reaction from Rob W in PCLink Software Issues   
    It's a graphics driver issue, fixed it for 5.6.6
  17. Like
    TechDave reacted to mapper in 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. 
  18. Haha
    TechDave got a reaction from mapper in PRI News   
    No no no, we're not releasing two new plugins. Fake news.
  19. Like
    TechDave reacted to whittlebeast in TPS vs. MAP fuel mapping   
    Here is a video I did on that subject.
     
    Also see
    and
    https://youtu.be/MJ1V0A9uKLE
     
     
  20. Like
    TechDave got a reaction from Adturb in [UPDATE] PCLink 5.6.6.3564 (on hold)   
    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.
  21. Like
    TechDave got a reaction from andpdas in IAT Sensor Choice for turbo charged vehicles   
    Yeah IATB is the better option. Faster acting.
  22. Thanks
    TechDave reacted to cj in Ignition angle in logs vs table   
    You havent logged a lot of parameters so its hard to check exactly how this happened, but yep your log says you had 40.6* at 185kpa. 
    Looking at your config I think this has happened because you have dual ignition table set in overlay mode (ie table 1 + table 2 = value to use). Looking at the rest of your config you either didnt intend for this to be used at all (4d ign used instead), or you intended to have it in interpolate/switchover mode between the 2 ign tables (table 2 is roughly 1* higher values than table1, and your "enable" switch for table2 overlay is the say DI9 meth switch you use for 4d enable). You probably want to set dual ignition to disabled given you are handling this in 4d overlay anyway.
     
     
  23. Thanks
    TechDave reacted to vonnyph in Unlock VL Link G4+   
    I have replied to your email, so please check your inbox and let me know how you go.
    Regards,
    Vonny.
  24. Thanks
    TechDave reacted to mapper in Questions about the capabilities of a WRX9+ G4+   
    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. 
     
  25. Like
    TechDave got a reaction from DOLFO in [UPDATE] PCLink 5.6.6.3564 (on hold)   
    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.
×
×
  • Create New...