TechDave

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.
I have also really enjoyed working with the LINK team over all of these years and hope to continue doing so.
So congratulations LINK and very well done.
Keep going on this fantastic journey.
Regards
Dave Kriedeman
PRO TUNING.

Example of how this could be done on a G4X using Aux 1 as the tacho output, anv 1 as the oil pressure and DI1 as the switch
Tacho as gauge.pclx

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 don´t like it...

It doesnt bother me.  I just like to be informed so im not over selling the product.  

Also i was under the impression that with G4x everything was the same, just updated processor due to the previous micro ending life.  

I don't have any experience with that particular motor but you should just need to connect your trigger 1 to the crank sensor (I assume the 1.8vvt motor has a crank trigger unlike the earlier 1.6 with cam sensors only) and trigger 2 to your cam sensor. Connect an aux (one of aux1-10, aux ign5-8 or aux inj5-8) and a switched power wire to the vvt solenoid. That should be all you need to do specifically for the vvt wiring.
You might have to add wires to the loom for inj3&4 to run sequential fuel as they are connected to the ECU header but the earlier vehicles don't use them and so might not have wires connected to those pins.
Other than that have a look through the plugin pinout and the loom in your car to make sure you have all the wires you need to do what you want, you may even be able to use another pin like aux7 (purge) for your vvt control instead of adding an expansion loom.
One final note, the factory wiring for the early mx5s has the MAF turning on the Fuel pump so you may want to rewire that.

I just tried it, works great.

There is no error state for the E-Throttle going outside of bounds.

Use the table import/export functions, this brings axis settings over too.

Works on almost all tables but not AFR/Lambda target

 

As per my email to you:
 
It's super easy.
Select the Toyota 1JZ cam control mode, then under "cam angle test", select calibrate.
Go to Inlet Bank 1, select a cam sensor input (trig 2) and a PWM output.
Make sure the engine is above the ect lock out, run the engine up to 4000ish rpm
All of the offsets, teeth etc are filled in automatically for you, you only need to set up your target table.

It's a 32 bit single precision float.
so there are a few answers to the question.

https://en.wikipedia.org/wiki/Single-precision_floating-point_format

The dealer hasn't followed the instructions properly.

Go back to them and explain that when they enter the unlock code online, they need to enter 2442 not 02442

A JZX100 plugin was announced to dealers today.

The X just uses the Multi tooth mode. Set tooth count to suit and if no sync set trig 2 sync mode to none.
 

my understanding is Overrun Fuel cut > 0.5 will only show cells where overrun is active.  I usually set mine to show Overrun Fuel Cut < 1

Hi, what directory have you installed PCLink to?

We added Semi-Sequential as a mode to keep the unused pins free for other aux uses.

Added "Custom CEL functions" a few weeks back, no ETA but it's in there.

March to June I'm told.

Accel fuel has been changed to a simplified X-Tau model

Accel fuel has been changed to a simplified X-Tau model

G4X solves this with a VA on the starter switch DI, but I do wonder if we need to move the start position function setting into the starter control settings. I'll put it to the engineers.

Done.
 
Should also be fixed.

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.
 

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.
 

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.