TechDave

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

March to June I'm told.

Abnormal Program Close thing is usually caused by installing PCLink to a write protected folder (program files) But yeah, doesn't usually matter with the drivers, we haven't changed them for ages too.

Exactly what path did you install to?

It's entirely ease. Chopping up the knock sensor loom isn't a recommended installation process, XS connectors make installation easy and reliable. No dip switches.

March is what the boss man said.

I've been thinking about this. The ECU doesn't know you're PC Logging, it doesn't do anything differently when you press F8, therefore the issue must be in PCLink, memory access or the drawing.

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

Hi, yeah I'm technically on leave for a few more days. I haven't had any replies to my email, the only missed call I have is from while I've been on leave. You said in your email that you tested it on a 1998 gen 5, that won't work, the ST205 only supports the gen 2 and gen 3 from '93 to '95. If the pinout is wrong I suspect the car is not a gen 3. As I said in my email, I'm happy to help fault find etc, but if it requires repair or replacement then your customer's friend in the USA will be able to handle that. Give me a bell in the new year and we can get it sorted.

...possibly? I never touched the firmware. I'll have a go at bench testing that in the new year, unless you already have a sim and some spare time? @Ducie54 if you go to device manager, right click on the Link drivers, then go to settings or properties or something, there's some stuff in there about the buffer size? Sorry it's a bit vague, I'm not in the office at the moment, otherwise I'd fire in a screenshot.

If I remember correctly it's bound to the rate at which the USB returns data from the ecu, we send a data request to the ecu, it fires back a huge packet of data, we use the new data to draw, then we repeat. So the size and rate of the data retrieve is the limiting factor on G4+ for the rate, which ought to be about 65Hz, you can't really do much to speed this up because you're physically bound by the connection speed and size of the data packet. When you log, there are a bunch of extra functions going on, saving all your data to memory, and the drawing functions become more intense, this increases the time between data retrieval and the request for new data. In my experience, drawing the screen wasn't really a major contributor to rate, but it has been a few years since I clocked all of it. This is high on my hit list for G4X.

http://linkecu.com/documentation/EVO9+.pdf

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.

You can do this by way of a virtual aux, but I'll ask them to add the Aux/ign/inj outputs too.

@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"

Just fired it into the issue tracker, cheers @Davidv

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.

RS232 is present on the CAN 1 port, this is the same RS232 that the micro chats with the USB. As a quick test, unplug CAN 1 or switch to CAN2 (no RS232)

You'll want to put your clutch switch into that brake DI too so pressing the clutch deactivates the cruise system too (otherwise it flips out). Or if you want to geek out you could wire your clutch switch to a different DI, that gives you a method of doing launch and antilag and flatshifting etc

Yes the Storm has 20 GP tables. Click here to review them: Bigger ECUs have up to 30: https://www.linkecu.com/products/ecu-comparison-chart/

Ray forwarded me an email from Banks, this is the case, Generic Dash, ID 1000, 20 Hz, 1 Mbit/s

What do you mean locked out? What error or message is stopping you?

Link CAN Lambda is the best way to get Lambda into that ECU http://dealers.linkecu.com/can-lambda