here comes the forum pissing match, i apologize for singleing you out, for your particular question, and excuse the lapse i had tryed searching but only found more of the question i had asked and no answers, since Razorlab had helped me before (a year or so ago) with a few tables that were found for the 8-9, i trust him

 

LOL, sorry too. Dam this thread got hot and intense in the past few pages. I'm sure some of it will be gone in a day or so. Yes I'm new to tuning and Bryan has helped me out too in this thread and others, so that's why I ask here instead of the other threads. As for data logging... I have been on a personal search for a data logger for the X. And so far all we really have is the Cobb AP, not really the best option if you are on a budget and looking to use ECUFlash exclusively. And there is also PCMScan...however PCM does not detect knock as it's a Mitsubishi specific PID and they don't have an approximate release date or any plan to crack into the Evo X ECU. Also Hamish with EvoScan has seem to back off Evo X development lately. Hey got an Evo X ECU and we keep asking for updates as he said once he got one it would only be a few days till we hear/see something....but nothing. But I seem to remember asking Bryan what he's using but I don't remember the answer or if I even got one. I mean PCMScan is good and monitors an outside WB too, but it's expensive to be missing knock....which we really need.

 

glad we handled that maturely lol it isnt always so on here, again i apologize, but for what its worth if you have your ignition map in front of you and you have load and RPM you could in theory detect knock by seeing if the car was pulling timing, like running lower then what your ignition map says...just a method i remember from somewhere

and yea i knew about PCMScan but not about any others, and i had herd of lack of enthusiasm for the X by evoscan

 

Ya that makes sense. Isn't that basicaily what this pic is showing:



Okay well I guess it would make sense to look at this thread: https://www.evolutionm.net/forums/4873095-post2.html

Isn't that what they are doing. Seeing that timing is pulled and adjusting. Don't necessarily need something to monitor knock exclusively correct? Is that what you are getting at?

 

well knock is in the red there, on the prior evos every 3 counts of knock meant that 1* of timing would be pulled, so it was predictable, i wonder if it holds true for the X


but yes thats what i am getting at ...correct

 

LOL ya I see the red. I mean just say it wasn't there. Check the data log vs the map. So okay if the map reads 7* but data log says 4* then what? Scale that RPM and load back till what the map is is the same as data log?

 

you would add fuel or pull timing (depending on situation) to correct it till your data log listed what is in your map. you could reference where the problem is via load and rpm

 

for those that are worried:

Bricked ecu recovery

http://www.tactrix.com/product_info.php?products_id=50

 

in evoscan's defense......hamish had trouble getting my ecu to talk to his computer, he tried to use a dealer scantool but one wasnt available when he needed it and i needed my ecu back for a week or so. But im sending it back to him next week and he will have it for about 6 weeks so that should sort our problem.

 

you're a good man onboost!

 

^^^ this guy is helping the evo community, thanks onboost

 

[wrong log-in]

 

Thanks David for the response, but if I wanted to ask you I would have called you directly, or are you now part investor in Tactrix/Evoflash?

I don't think I saw anywhere in my post where I was putting them down for their efforts or their product. I simply would like to see more updates from them as to what time-frames are for all of the people who purchased the 2.0 cable in hopes of getting into their X's Ecu from since July.

To clarify, I'm not trying to pin them down to a "Release date will be XX/XX/XXXX" post but just to give everyone a heads up as to what kind of issues they're having and if it looks like it will be a viable solution anytime soon, or if there are a lot of issues that need to be ironed out and we're looking at many more months.

I'd be more then happy to do some testing on the current beta if needed as I rarely if ever drive our shop X and have been using stand-alones and flashing software since well before (years in fact) a lot of places got past using simplistic setups like VPCs and AFCs exclusively, if more input would be helpful.

 

Sweet!!!

 

Now someone just has to find out how to do this at home and I wouldn't care at all. When the iphone first came out I spent 2-3 months teaching people how to unbrick their iphones, so I hope one day someone would be willing to teach me this. Wait I hope this never happens to me to begin with .