I've just switched to using a Macbook for tuning and am having trouble getting this thing to read any Evo X xml...

Any apple guru's out there with a clue?


Cheers!

 

That doesn't make a lot of sense to me 4ws a xml file is just plain text.

See if it got DOS encoded at some point by opening up the xml file with text edit.

If its got wierd crazy characters in it like ctrl-M which microsoft uses as a line break, you'll need to convert that file to remove the ctrl-m characters. Its more of a unix thing than mac btw .

Here's a list of commands to try if you want.

http://kb.iu.edu/data/agiz.html

 

Awesome! That'll give me something to try.... I know literally zero about this so I wasnt sure where to even begin!


Just to clarify a little more, when i copy the XML for evo x's; ecuflash isn't recognized the definition.

I'll check it out and post back up.

Thanks again Roadspike!

 

If you are just copying the text from a website like this one to an xml I would hazard a guess that it is an error with the xml form. It should spit out something like xml error at line and a number and column where it couldn't parse it.

Here's some more info on the newline problem btw.
https://ccrma.stanford.edu/~craig/utility/flip/

 

The only thing thats puzzling is wouldn't I have trouble with other files as well.. The rest of my XMLs i've made and collected over the years all work..

 

I really depends on the editor used. Notepad created files vs wordpad and so on its really a mess :P. Ecuflash itself may have a clean up method of its own that it employs.

Edit:
Aim me too if you want me to look at an xml file you got. I can find the errors really quickly.

 

What OS are you using? If you can not find a Mac solution, you could use boot camp. Just a suggestion.

 

Just run windows off your Mac.

 

Is the MacOS release new enough to support OpenPort 2.0 (which you'd need for an X anyway)? I thought it was a couple of releases too early; maybe donour can chime in?

 

I think the driver should be ok, but the Mac builds are lagging. I think the most recent is 1.38, which doesn't have Evo X support. Email colby or hop on the openecu.org forums.

There's a 'gotcha' with the xml definitions. On OSX, they live inside the application bundle, not in an external config directory. The location is somewhere like:

/Applications/ecuflash.app/Contents/MacOS/rommetadata/mitsubishi/evo

d

 

Thanks for the offer man! I think the issue is with the program itself =-( The XMLs are untouched, just standard evo x xmls.

Cheers!



That's probably the issue... I've tried everything I can on my end.. I just got back from the Apple store and 3 of them tried for a few hours to see if they can figure it out and they couldnt.. so much for "Genius" haha

Thanks for the post!


I just setup VMware for tuning 10s from the office. I have bootcamp setup for road tunes