HolyCrapItsFast
Drinks beer!
I was mistaken... I have EvoScan 2.8... it only does SSM not can for subaru... here is a screen shot. RR Logger is much better for logging because it has the fast poll feature. I think it it very intuitive and capable.
TD_D mod journey. From stock to the 'bastardmobile'
- Thread starter Td_d
- Start date
-
- Tags
- meth injection td_d tuning
I was mistaken... I have EvoScan 2.8... it only does SSM not can for subaru... here is a screen shot. RR Logger is much better for logging because it has the fast poll feature. I think it it very intuitive and capable.
Td_d
Commander In Chief
Yeah, I've never managed to get evoscan working in anything other than ssm. In any case, as George says, romraider's fast poll feature is great. Since you've got CAN as well, SD card is much easier - I can set it up for you, just takes a rom patch. There's a great utility called logcfg.exe which automatically generates a logcfg.txt file for you, very straightforward.
It's great to have constant logging...
It's great to have constant logging...
HolyCrapItsFast
Drinks beer!
BTW does do circular logging on the SD card?
HolyCrapItsFast
Drinks beer!
I'm guessing autocorrect
Circular logging?
When it reaches the end will it over write the oldest data or will it just not log
Td_d
Commander In Chief
Ah! :doh:
No - it does not overwrite the old logs - it creates a new log file and then corrupts it, unfortunately. Then again - pop a big-ass SD card in there, and you'll have enough space for many, many logs. I find an hour log is about 17Mb or so, and I log quite a few parameters.
I have hundreds of logs on there, and just dump them regularly onto the hard drive. The one real down side, small but irritating, is that the tactrix cannot properly timestamp the files (since it does not have an onboard battery). It's always 1 January 2009 :tard:
No - it does not overwrite the old logs - it creates a new log file and then corrupts it, unfortunately. Then again - pop a big-ass SD card in there, and you'll have enough space for many, many logs. I find an hour log is about 17Mb or so, and I log quite a few parameters.
I have hundreds of logs on there, and just dump them regularly onto the hard drive. The one real down side, small but irritating, is that the tactrix cannot properly timestamp the files (since it does not have an onboard battery). It's always 1 January 2009 :tard:
HolyCrapItsFast
Drinks beer!
Td_d
Commander In Chief
Sure does - I'm logging my MTX-L straight through the SD card. Innovate is supported out of the box with the tactrix, and with the other's, there's a spare pin on the tactrix that can be use to patch in the analogue serial signal, and will log just about anything that can do 0-5V.
Td_d
Commander In Chief
So, the possibility of running E100 has popped up again - I've bumped into a member on the local forum that runs pure ethanol. He says other than some few cold start issues when it's very cold (very cold here is 0 celsius or slight lower 
) it's worked out well for him.
He gets 3 drums delivered to his place every couple of weeks, and pumps straight from the drum into the car. I'm seriously thinking of doing this - I don't drive long distances, and the bonus is that I would basically top up every night, easy. At the same time, I've been offered an HFS 6 as a thank you for helping out on tuning advice, a very generous offer to say the least. I'm in two minds - at least with the HFS6, I can drive basically anywhere, as the meth last very long, and is easy to get hold of.
Yeesh... decisions, decisions. Maybe I should do both, then I have the flexibility to switch off the HFS when I'm running E100, and on when I need to run gas. Seems like such a waste of a serious piece of hardware though...
) it's worked out well for him.He gets 3 drums delivered to his place every couple of weeks, and pumps straight from the drum into the car. I'm seriously thinking of doing this - I don't drive long distances, and the bonus is that I would basically top up every night, easy. At the same time, I've been offered an HFS 6 as a thank you for helping out on tuning advice, a very generous offer to say the least. I'm in two minds - at least with the HFS6, I can drive basically anywhere, as the meth last very long, and is easy to get hold of.
Yeesh... decisions, decisions. Maybe I should do both, then I have the flexibility to switch off the HFS when I'm running E100, and on when I need to run gas. Seems like such a waste of a serious piece of hardware though...
Td_d
Commander In Chief
AEM. simple stuff
Fuji - here's that link http://forums.evolutionm.net/09-ral...tandalone-logging-0-5v-adc-op2-0-pin-8-a.html
I would even try to see if the way I'm doing it works (using the 2.5 mm jack with a serial connector to the analogue signal of the AEM) - might well work.
Td_d
Commander In Chief
So, I'm testing a theory with the Five-O injectors, namely that the published latencies are nowhere near accurate in my circumstance. Jury's out still, as I now have to completely redo MAF scaling and load compensations, but increasing the dead time (quite significantly - 15%) seems to have made idle correction swings less erratic, and has reduced the pulsing I felt. Once I have the scaling nailed down again, I can make a call on it.
Td_d
Commander In Chief
Let me guess - much higher, right?
I'm thinking that these injectors are much slower than the advertised rates - which isn't necessarily a problem in and of itself, but time consuming as all hell.
HolyCrapItsFast
Drinks beer!
I'm staying tuned!
Grinder34
Track Monkey
nice pun!
HolyCrapItsFast
Drinks beer!
LOL... Oh yeah... Look at that :lol:
Td_d
Commander In Chief
Hehehe... [Drumroll]!
Alright - I am now officially running a speed density tune
Using the spreadsheet tool that's up on the Romraider forums, with a couple of tweaks of my own, managed to get a workable (well, actually a pretty decent) SD map to load on and ran it, with a couple of iterations and edits today.
I left closed loop switched on (Cobb also recommends doing this) as it leaves you with a bit of a safety net in terms of heat soak with the IAT in the cold air intake. Zeroed the load compensation table completely (which I am loath to do, as I have major resonance issues) and ran it. Open loop is remarkably close in terms of tracking the fueling tables.
Closed loop is going to need a lot of attention. Trims are quite erratic - although I believe that also has to do with the zeroed load comp tables. My thinking is that the VE map is in a better position to deal with resonance, given that it is using the same input parameters as the problem - RPMs and MAP. And you can see it in the map as well - the areas where the load comp tables previously compensated have similar patterns. I'll make up my mind as I go along as to whether I revert to using the load comp tables strongly or only to smooth things out.
Idle was actually relatively stable, although there is a specific situation where I managed to get it to basically create a circular feedback loop - it swung from -7 to 7 and so on corrections. High IAT after heat soak, and a tap to accelerator and letting go (creating a peak, and then a trough). My gut feel is that the latencies are still not right. I'm running 1.05ms now, as opposed to 1ms which is the advertised deadtime at 14V. Looks like I'm going to have to test different values - but I'm thinking that the pulsing (which I can see in the AFR's on the wideband swinging wildly) is likely due to the injectors being slower than the advertised rate. We'll see. Frankly, I wish I had some input from other people running 1200cc five-O injectors... If any of the mechanics on here have encountered them, would greatly appreciate feedback.
Once I have a relatively stable VE map, which I need to make sure is done at a relatively similar atmospheric temprature (it's been damn hot lately...), I will need to proceed to the g/s vs IAT compensation tables.
This is going to be a lot of work - but I suspect worth it.
