TechDave

Voltage on pin 8/45 needs to stay above about 8.2V to keep the ECCS relay on. If it does drop then it will need to recover to about 8.7-9V for the ECCS relay to come back on and for the ECU to start up again. This can take a few seconds to happen. Try pulling your ignition barrel apart and cleaning the contacts, this seems to make the biggest difference to voltage during cranking.

Yeah IATB is the better option. Faster acting.

Hey Brad, it's firmware too, I too noted its absence from the changelog and have been trying to get a chance to test it but haven't yet.

Records show it was VMS Tuning: VMS Tuning 10 Forrest Crescent, Redbank Plains, 4301 QLD, Australia Tel: +61422414413 Email: [email protected]

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.

Surprise!

Did you install a 120 Ohm terminating resistor? The CAN-Lambda Manual is available at the bottom of this page: https://www.linkecu.com/manuals/ It includes a specific diagram on wiring a CAN-Lambda.

Wait, so have you tried connecting while the ignition is on and/or the engine is running?

Unless CAN has been added, plugins only have 1 flying lead for USB coms (but hey, best to check) "unable to connect to the ecu but usb connection is present." means the USB chip is able to communicate with the PC. The fact the engine runs means the micro is getting power. So it's something getting in the way of the RS232 communications between the USB chip and the micro, usually this is something connected to the CAN1 connector on the bottom board and the unused RS232 TX and RX wires are acting as antennae.

Already do a bunch of this, have a read of this in the manual: G4+ ECU Tuning Functions > Engine Protection > GP RPM Limit

Trig1 isn't showing any signal, it's just sitting at 10V. Was the engine cranking while you pressed capture?

No sorry, they are stored in memory until saved.

UnicornGarage, Please save your dxdiag information and copy-paste or attach it here or email [email protected]

Interesting that a driver rollback works. I identified an issue in Nvidia graphics card drivers back in October 2017. @rocklizzard91 can you post here or send me a link to the drivers that you used?

Sorry I missed the bit about throttle. So Aux 14 can only consider 2 conditions, I've used a virtual aux to wrap up your RPM and TPS requirement (change that 50% to whatever you need). If the RPM and TPS condition is met, and the DI 9 switch is in the on position, then the function will work, if you switch the DI 9 switch to off, it will turn off the function, or stop it from occurring.

So we've used GP Output on AUX 14 and said if RPM is > 1500 AND DI 9 is in the ON state, then become "ON",

Moved into G4+ for you.

We don't show the contents of a view while dragging by the way, so you should only expect the outline but it should be the same size and position as the view. If your outline isn't the same size and position as the view you're clicking and dragging then you need to set your windows display resolution scaling to 100%. If the font sizes are too small after this you can scale them up in PCLink in options > preferences.

No, but windows does. Applications user address space is physically limited to 2GB for 32bit applications - you can't change this. I'll +1 the solution to this issue for you. In the mean time, go to the PC logging setup window, remove all, and only add what you really want to see:

There is no temp file. Does the machine go to sleep in that 90 minute period? When it crashes, how much memory is the PCLink process using?

@Ken Dunkley you can scroll along the time plot and the pink "logged cross hair" will traverse tables with the associated axis run times. If they don't show up, you may need to right mouse click the table and turn on "Logged Value Cross Hairs".

I think what @Quad4444 wants is a button on his tablet he can press to switch Anti-Lag tables. This and a few other bits are on my "Things that would make PCLink much nicer to use as a tablet dash"

Hey guys, Just an update to this one. The surface view issue seems to be on Nvidia drivers with the new OpenGL 4.6 standard. For me these drivers were released back on the 9th of October version 387.92, so rolling back to 385.69 (Sept 21st) fixes the surface view, your mobile graphics might be different versions. Obviously working to fix this properly. As for "lag" no body has followed up with sufficient information for me to investigate further.