MagicMike

For Lambda 2, unplug the first lambda so that only lambda 2 is connected to the bus, (you dont need to change anything on the main Mode tab - leave only one channel set to Link CAN lambda and ID 950), then go to CAN devices tab, click Find Devices, when it finds the device, change the parameter drop down box to "Lambda 2" and then hit the send button.  Press apply, ok, do a store, power everything off.  Plug all CAN lambdas back in and re-power up, both should now be identified and working.
For power, prefereably they should just be connected to an ign switched source - let the ECU control it.   With it powered from the FP relay you will get CAN errors logged every power-up - it will still work fine, just the errors will annoy you everytime you look at the runtimes screen.  
 

Yes they are fine in the engine bay.

Would it be possible to have an option for the the mixture map function to take into account correction made from closed loop lamda?  I like the idea of having CLL running as an added safety margin when road tuning and it would be good if the mixture map could look at what corrections are are being made to make permanent changes to the fuel map.

It duplicates the basics.  It doesnt have all of the Link statuses but the basic OK/Error comes through.  Sensor temperature comes through.  CLL disable works correctly.  It doesnt have bi-directional comms so doesnt turn off when the engine is not running like the Link.    

In terms of dual channel the only one I really have experience with is the Motec LTCD.  They seem reliable but are a bit pricey.  HV Electronics have a dual channel one which seems reasonable on paper but I have no personal experience.  @Ducie54 was using a couple from memory, he may have some feedback.   Neither of these will provide much in the way of native error/status reporting.
I believe the new Haltech one has a mode that is compatible with Link but again have no personal experience.  The old silver cased ones were very slow, not sure if that has been improved in the newer one.
Otherwise you can buy two Link Lambdas for about the same $ as the LTCD but will give full integration in terms of status/errors etc.  Also maybe worth  considering the 14point7 spartan 3 - has worked well for me on several budget cars.  

Im using 2 Emtron dual wide band controllers. I dont have the latest software for them so I have to power them up from a Aux output. They power up after 20sec from ignition on without a CAN signal.
I have CAN set up for errors but it shows just a number. I then have to go back to the manual to work out what it is.
If i was to do it agian I would just buy 4 of the LINK sensors. So much less hassle setting them up. 

Put Ign angle on a time plot and you will see the issue.  You go from ~6deg target timing in your idle ign table to 35ish in the main table when you blip it, so the extra 30 deg timing is enough extra torque to hold the RPM high.
Various ways you could fix this such as allowing the idle ignition to kick in earlier but I think that may have some negative effects when driving.  I think the best fix would be to drop the timing in these 3 cells in the main ign table quite a bit:

 

Thanks Adam,   Made the timing 15' in all of 0% TP and is better.
https://www.dropbox.com/s/l2ja46c08cybrst/Idle Blip.png?dl=0
 

Would this be at all possible?
Instead of having to save each individually?

I only see one around time 1:04, is this what you are talking about?  This would typically indicate an interruption of USB comms.  So it just draws a straight line between the points where is lost comms and when it started again.  The reason for that will be harder to diagnose.  What sort of connection speed do you normally see at the top right of your screen?
 
I only had a quick look, but my feeling is just before that point the MAP drops from around 39/40 to 34KPa, this reduces the injector PW from 0.44 to 0.37, but the lambda actually goes richer.  I suspect maybe your injectors are just hitting the point where they are becoming erratic - some are behaving differently than others.  Try setting your min effective pulse width limit to something like 0.42 and see if you can reproduce it.

Confession time: the hose I thought was going to the wastegate was going to compressor and the other way around I switched them around and now target boost seems to come around 25 % wastegate and controllable. 
I'm sorry to have wasted your time and to have driven the car in overboost dozens of times while trying to understand what's going on.... unfortunately I was just too sure of how those hoses were connected and I thought of any other complicated explanation but this.
So car pulls strong and it seems that soon the tuning will be done. Next priority is getting the cold start decent but I'll meet you in other topics about that
Thank you for your help and good luck!
 
Best regards,
Florin

Not sure if this has been asked for already, but is it possible to allow user controlled assignment of the X axis in cal tables 7-10.  The option is almost there but greyed out.  For instance, I would like to assign the X axis to a can voltage and then output kPa for MAP.
 

 
Thanks,
  Richard.

Ages ago I was using cruise control to do some road tuning for best fuel economy. 
I'd drive a set piece of road at a set speed. Then had digital inputs on the dash that added different combinations of ignition timing.
So I'd go do a run at XYZ speed, which has lots of ups and downs in it to vary the load. Record a log file.
Then come do that same thing again, with different amounts of ignition advance added by the switches. 
This showed clear as day in the CC per min fuel usage logs, and TPS, which was best. 

So I took this a step further and made an arduino canbus unit that would wait for certain conditions to be met (cruise control on,steady driving no tps movement)
When cruise control is turned on, a virtual aux is triggered by the Teensy which sends a digital canbus input to turn on a 4D ignition table that has an analog canbus input as the load axis.
Then the Teensy has a full separate ignition table in it, and outputs the can value that represents ignition advance for the table.
It would collect 100 samples of fuel economy. Advance the ignition 3 degrees. wait for conditions to stabilize again. Then collect another 100 samples. 
Then it would compare the results of the test. If the results were better above a certain margin, it deinterpolates the current load/rpm ignition timing addition back over the 4 cells that its interpolating from.
Then it checks that if there is any lower load area or lower rpm that has less ignition timing than this, it will update those values too.
If the economy got worse, it would creep the ignition timing slightly back from where it started from, and do it again.
Basically it's auto road tuning for MBT. (But only works in a fairly narrow rpm and load range, because you dont have cruise control turned on at 8000rpm WOT)

So it iteratively builds up an ignition timing map on its own and keeps fine tuning it.
Starting with 10 degrees timing everywhere, it builds up a relatively sane ignition timing map in about an hour or two which is really cool. 
But whats nice is that when the car comes to a stop I can store the values to Eeprom so they're not lost when car shuts off.
So I'm also planning to shuffle the knock sensing logic over to this board too, so I can store long term knock trims instead of losing everything when car turns off.

However, this then also scope creeped into a context sensitive plug and play digidash / 3d printed housing.
With a whole bunch of other crap going on like auto dimming, changing screens based on what you're doing, xy plots, histograms, etc etc.
Also takes all of the standard dash inputs like lights, indicators, etc etc. Work in progress! (Its for an 80s car hence LCD type look) 
Working through some bits at the moment like estimated range off remaining fuel, and things like that. Has been a good learning experience and I'm pretty happy with the results so far.
Once the auto dimming became functional It's been really nice to drive with.

Trust me though, you dont want to see the code hahaaha.

I know its a bit of a bodge, but I've done this by using CAN inputs and outputs. 

You can output variables over can, do maths/programming/etc on your canbus device using the information, then send the variables back into the ECU. 

I do this to log a litres per 100km parameter into the ECU so I can view it in the logs with everything else (only cc per min is available otherwise) 

I've also used a canbus input as the load axis on an ignition table and had my device trim the ignition timing with more logic than is available on the ECU. 

Check out Teensy 3.6 and the IFCT library for it.
 

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.
 
 

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.

It is up now 

Thanks,
I drilled a sensor today and tried it before and after. No difference at all when using a 10-8mm stud and 8mm hole, or using an M10 bolt and drilled sensor.
Same knock levels, same background noise etc etc.

A PCLink update!

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 of nozzle...and tested not fighting against boost pressure which would reduce flow further.
Even with only a 600cc nozzle...my  factory set 200psi pump, could never create 200psi.
 
With 1600cc worth of nozzle, in the car, in real world use max pressure I see is around 140psi....so if using say 40psi boost, that's now only 100psi of effective pressure to inject, so even less flow.
 
But stick a pressure sensor on the line and log it for yourself and use this to control any fuel/spark adjustments, rather than what you're currently doing which offers no failsafe. It's a cheap and easy way to monitor what the system is doing, and could be an eye opener.
It's a pity nobody seems to have done much testing on the various systems and pumps out there to prove or disprove the suppliers claims.

Can i swap the boost target and rpm x and y axis around to take advantage of the additional length of the x axis, instructions say rpm must be x?, but i am not so sure
Clarification, i am talking about the wastegate %DC active table

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

looks like i've managed to solve this myself thankfully.
After i sense checked all my connections and double checked the canbus cable short loom that connects to the ecu i discovered
that the wiring is all wrong compared to pictures i've seen online.
So i picked the cables off and put them in the proper locations and hey presto its working.
Just shows you you shouldn't trust ebay and double check the wiring connections when buying cables that are not oem.
 
 

A single screenshot without factoring in everything else within the tune means little.
 
Perhaps even more so as the scalings on the table have also been altered. But you can be sure that if it's busted 2 pistons and was knocking/detonating....maybe choose different friends ?
 
Or at least never let them near your car again.

Of course it works, I see it set up and working in nearly every log I look at.  
 
If you didnt look at the runtimes screen then you obviously didnt follow the instructions.  You dont need an F12 key to access the runtimes, thats just a keyboard shortcut, you can click on the menubar>tuning>runtime values.  The runtimes is a key part of the set up as it will tell you if it is happy or not, when its finished and when you can move on to the next gear.