Davidv

Hey guys, I got modelled fuel setup, and it's awesome! One of the reasons I switched though is that I have a bit of a thing for fuel economy currently, and was hoping to get some sort of l/100km or km/l or MPG type value (I thought this is what instantaneous fuel consumption would show me, but its not speed referenced at all) If I wire up an OBD2 port to the ECU, can an OBD2 app (such as Torque) give a fuel consumption value based on the available stats from the ECU? Or can it only show things like RPM, engine temp, etc. If it can give me fuel usage values I'll wire it up, but wont bother if not. Has anyone tried, had this working, and had some fuel stats reported back? If not, it would be cool if PClink could do an equation on cc/min divided by speed and show it on a display in real time Thanks

Great! Thats good enough.

Hi, I'm about to switch to modelled fuel soon, for interests sake but also so I can get some fuel economy readings in realtime, and more OBD information for use with a bluetooth unit and an android device. However I notice that in the help file it says that fuel economy readings do not work with staged injection. Does this mean that it'll still give me a number, but not take into account the secondary injectors at all? As I'm primarily just interested in refining my "cruising area" of the fuel and ignition maps, where the secondary injectors are irrelvant anyway. But it would be nice if it worked for both Also, in the datalogs the category labels for the staged injection are named differently compared to primary injectors. I'm not sure which datalog value represents effective injector pulsewidth, it would be good if these had the same naming convention if possible.

Took this out to Hampton, ran awesomely! Now running Yokohama AD08R, world of difference from Toyo T1Rs... These dont overheat one bit. The engine ran awesomely, no dramas apart from nuking my 3rd wideband sensor just before the start of the day. Pretty sure it's the innovate controller causing the problems so looking at alternative options.

3SGE or 3SGTE Engines always wreck the number 3 cylinder first... It's the last cylinder to get coolant, that isnt on the end of the block. Depending on intake manifold design it can bias that cylinder as well. I've rebuilt a 3S that had Cyl 3 completely nuke itself too. Regardless of whatever knock strategy and wideband you use, it might pay to pull a slight amount of timing or adding a slight amount of fuel to cyl #3. From memory this is what the Motec basemap for 3SGTE does. How far along are you with your engine build? There was a revision to the 3S Engine blocks in 1998 or so, with some extra webbing that stops the blocks from cracking with lots of power. If you still in the process of sourcing an engine block, be sure to get one of the newer ones. Starting with a Caldina GTT block and head as the base for your rebuild is an easy way to switch to coil on plug while getting the stronger block.

+1 to this, more virtual aux would be great, but if there were more than 3 conditions available then you wouldnt need to stack them together. Example... I'm wanting to setup a warning light that is triggered by different conditions. So for example, if rpm is xyz and oil pressure is below abc, then flash the light. But then also trigger the light for other functions like maybe excessive coolant temp / oil temp, etc etc.

So if you start a gauge just for the DI, it shows speed fine? Does it give an error in runtime values, a few times I've had to retry a gear because I didnt keep rpm steady enough.

Haha wow! That's perfect... How did I miss that. Thanks Simon.

I've finally started piecing together my injector test bench. I want to test: -Injector deadtime at varying pressures and voltages -CC rating / see how well injectors compare in a set -Spray pattern at varying fuel pressures So putting something together to physically acheive that is fine, I want my ECU to run it and datalog it though. What's the best way that I can control the injector with the ECU while the engine isnt running? If I use Aux injection with a 1d table for a value at 0rpm, will that do anything? Or because it's 0rpm, will it only fire once/never. The "PWM test" would be good but it only lets you specifiy the HZ with no control over pulsewidth etc. It sounds like Aux injection can acheive everything I want, so long as it's able to work at 0rpm. If there's currently no way to control the above, then could I please add to the wish list: "Injector Test" function for aux outputs (Or just expanded test PWM function) -Can specify HZ, but also ms opening time or % opening time -Run the test for a certain number of events or for a certain time period. (Run for a minute, or run for say 500 events) -Switchable on/off by a DI / virtual aux / timer -Able to datalog the above Thanks, David

Hey, Thought that it might be a cool feature to have an odometer. Just a number that ticks over in the ECU. Then you could setup warnings/lights/etc for things like oil change intervals, service intervals, or would be handy for working out fuel consumption and so on. Possibly handy for some race cars when you could work out fuel load vs % of a race left to go, or something like that. Even if it was just a dataloggable value that you could datalog internally at a really low rate, would be cool.

Okay so just tested this out, on both speedo and tacho.... bloody well brilliant! They're now both super accurate.

Looking through the changelog, I see this has been addressed... Can now specify a frequency table for GP PWM. Awesome! Will give it a go this weekend.

Good to hear Dave, hope you get well. I and many others appreciate your input, long may it continue

Hey, I'm running a beams motor, not with ITBs though. However... Your tune is going to change a lot depending on the length of your intake runners, they cause huge peaks and dips on the powerband. (and fuel table) Are you using Alpha-n (TPS only) or using a map sensor? Would love to see some pics and some more details of your setup!

Hey Scott, My netbook is 1024x600 so that should work fine

Hey, Let me just first say, that the cruise control function is BRILLIANT. In conjunction with e-throttle, it's turned my car into something very jerky and uncomfortable to drive, into something silky smooth while cruising. Total game changer, absolutely love it. However, as always there are a few extra features which could be a cool addition. 1. Being able to assign a DI to a preset "set" speed. As an example... I only ever turn cruise control on to either 80kph, 100kph, etc. It would be cool if in the cruise control menu there was: Set1 = 70kph Set2 = 105kph Or something like that. Then you could assign Set1 to DI5 or whatever and it will always go to that speed when you hit the button. 2. Some up and down speed buttons, so you can increase or decrease the Set speed in 5kph increments or something like that. 3. Being able to change the Set value in Pclink in realtime by either wheel speed or rpm. One unexpectedly awesome feature of cruise control, is being able to hold the car at the dead centre of a column of cells. When you go up and down hills (or load it up with handbrake or dyno or something) You move through the various load zones which works awesomely for getting great results with the mixture map or Quick tune. So it would be cool to be able to set the "set" by RPM so you can get it bang on the centre of a column of cells for this purpose.

When you datalog with a PC plugged in, either by pressing F8 or pressing the button in PClink. When you finish datalogging, if you accidentally double tap, it deletes your entire log because it starts running a new one. Would be cool to have an optional prompt that asks you to save first, or something like that.

Oh thanks... Yes it's fine currently, would just speed things up slightly. Actually after helping a friend tune an MX5 this weekend just gone with a competitor's ECU I've come to appreciate just how awesome the Link datalogging is! It make all the difference.

I'm meaning something a bit different If you look at the grey vertical markers in the background, these relate to rpm divisions that scale depending on how far zoomed in you are... Imagine if they indicated the rpm divisions in your fuel table instead, and you could jump your point on the log straight to one of these vertical markers. What I mean is, instead of hitting the right arrow key and it slowly scrolls through the log. If you could press the left arrow key, and it jumps straight to the next part of your log that's centred on a column in your fuel table

Yeah that's what I am trying to do, set them to manual... when I set the min and max values to say 12:1 and 15:1 for AFR. That's when the values turn to garbage (between 176 and 205, as per the highlighted text) If I set it back to auto, the values drop down to sensible AFR readings again.

You could run one of the fans from a temp switch in the radiator, and then the other triggered by the ECU. Does your radiator have a fitting for a temp switch already? You can buy different ones which come on at different temps, depending on what thread pitch etc it is.

The answer is helmholtz Shooting flames with a rotary engine I dont think the provided instant fuel value would be much use in your scenario, because it gives a litres per km result that relies on a wheelspeed DI input for the km part of the equation. Which I'm imagining will be wildly inaccurate in the case of a big HP rotary driving on dirt! It sounds like a litres per minute figure is what you'd be after instead, you can probably get a good enough approximation of this from datalogging Effective Injector Pulsewidth.

Do you have the injector deadtimes correctly entered? If the injector dead time was incorrect, then at very low pulse widths it might be showing that you need a whole heap of fuel... But in reality 3/4 of that time is just dead time. Hence the high numbers to get a "normal" AFR

If I manually specifiy min and max values for AFR on the time plot (set them to 12and 14) it shows nothing on the graph and the numbers on the scale jump right up to gibberish. Something else weird, my speedo signal comes from LRwheel speed. But if I download the log from the ECU, it shows up as 0 all the way across the board. But if I look at driven wheel speed, it shows up fine even though this comes from LRwheel speed, both are specified for ECU logging.

Hey, When looking at datalogs, say of an RPM pull through the rev range. Essentially I'm looking to refine the value in a cell, so I end up manually shuffling through to until the engine rpm (or whatever) matches a row on my table. So for example if I click on a random spot and it's at 6300rpm. I'll manually scroll across until it gets to 6500rpm (the closest cell) and then look at the AFR value and adjust it. It would be cool if there was an option to turn on an option that when you scroll with the keys, it "snaps" to either the horizontal or vertical rows of a table. So you click "left" and it jumps forward to 4000rpm. then 4250. then 5000rpm. then 5500rpm. etc. And maybe show them on the plot as well, something like this but not so crappy looking haha.