Richard Hill

The PLX wideband digital output is RS232 in their iMFD format.  19200 baud rate, 8 data bits , no parity and 1 stop bit.  It is output at 10Hz.  They will send you a PDF file with details of the format if you ask them.  So basically no it won't work over CAN...
Hope this helps,
  Richard. 

I have found that the CAN Lambda is quite sensitive to transient supply dropouts.  The alternative wiring below is in the new CAN Lambda instructions and includes a 22µF capacitor in the supply to the unit.  I have had several CAN lambda units that report faults and the addition of this capacitor has solved the problem every time.  
I think Link should update the online PDF file to make this the recommended setup, as the diagram below seem to only be included with the new CAN Lambda modules.  (IMHO, the addition of the 22µF capacitor inside the CAN Lambda module would solve the problem long term).

 
Regards,
  Richard.
 

you probably already have an intake air temp. sensor (or a charge temp. sensor).  If possible, turn the ignition on with the G4+ connected to pc-link, and have a look at the runtime values (F12) , see if An Temp2 is connected or if it is erroring.
You will need to cut the wire on pin 29 (which was narrowband o2), and connect that to the AEM wideband wire.
If you look at the diagram I posted above (Nissan diagram) , you will see there are multiple grounds all connected.  They are all internally connected inside the Link ECU so it doesn't really matter which one you use (although I would be inclined to use a sensor ground wire like pin 50 rather than a power ground wire)
 

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.
 

That isn't the pump manual, The 500mA current specified is the maximum output of the TinyCWA controller, not the current consumption of the PWM input pin on the pump (which will be much lower).  You can control these pumps with either a high side aux, or if none available you could use a low side (I would add a 10k pull up resistor in the pump connector) 
Also, worth noting these pumps should be installed as low as possible and work best in a "reverse flow" configuration as they cannot suck air, and so will fail to pump if coolant levels are low and mounted in the top hose
HTH, 
Richard. 

Here is one i put together.  It was done a few months ago with a pre-production unit, so might need to check that nothing has changed.
HTH,
 Richard.
 
EcumasterWBO.lcs

You can use VVT (AVCS) on auxs 1 to 4 and vvt sensors on digital inputs 1 to 4, so you might need to move other functions off those pins. 
 
No, you can not reassign inputs to outputs or digital input to an analog input, you will need to repin.  You can however reassign an analog input to a temperature input (you will need to add a pull up resistor as only temp. Inputs have these internally.) 
 
HTH, 
Richard. 

I think I made a link stream for the haltech wideband controller.  I will have a look. 
Regards, 
Richard. 

Now running 12lbs.  with a smaller blower pulley and nothing has come out the side. Yet......

Try
[email protected]
 
 

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.
 

New firmware is here :-
https://cdn.shopify.com/s/files/1/0189/1312/files/Spartan_3_ADV_Firmware_1_09.zip?52
 
You will need a Windows computer with Bluetooth.  Instructions are in the zip file.  
 
If you have any problems, give me a ring on 01474853219 UK working hours and I can talk you through. 
HTH, 
Richard.
 
 
 

If you use the stream file I attached, it will read the data into Lambda1.
 

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

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

It's probably because you don't have access permissions to save layouts to the default link folder (At the moment PC Link doesn't use the Users default write permission structure of Windows 10)
If you go to options and click on the directories tab, then untick deafults for log files and layout files, then change the two folders to the ones you have write access for (probably documents\???), then you should be able to write/read layouts and logs.

HTH,
 Richard.

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.
 

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 

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 

I have monitored the current draw of CAN lambdas during heat up phase several times from ambient, using low voltage (10 Volts and nominal Voltage 13.8) Basically on the edge of failure mode, The maximum current they draw is 1.5 Amps (worst case at low voltage) . reducing down to about 1 Amp when up to temperature.  I will post the Thunder current draw tomorrow when I can dig the values out.

You mentioned can hi and lo as green and white, just in case you have them that way round, can hi is white and can lo is green.  Also have a lookcat the can tab in the runtime values to seeing there are any errors.
HTH,
Richard.

this is how to input an ecumaster can egt board.  Should be similar (byteorders may be different )

HTH,
Richard .

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.

Can you do a triggerscope and post the log file using the Fury, as this will show more about the ECUs interpretation of the trigger signal ?
HTH,
 Richard.
 

Set up a Virtual Aux to turn on when knock level exceeds your chosen threshold,
 

 
and then set an Aux out to turn on when the Virtual Aux is active.

 
HTH,
 Richard.