Hi,

I am planning the buying full version but I have some questions;

1- I downloaded the trial version. But I could not open my ecu rom file. I would like to see which maps ecuedit have and its structure. But how?

2- Will there be ecu definitions like in ecuflash or romraider or should I obtain definitions somewhere in the net?

3- I tried to use ecuflash and romraider definitions to open my rom but I could not.

3- I have an 2006 EDM STI. After buying, shall I get definition support just for my current car? If so should I buy new one when I change my car?

4- Can I install more than one notebook and use. Because I have more than one.

5- Can I use openport 1.2 dbw usb cable for flashing/editing/logging?

6- I want to have a user friendly program. I don't want use different programs for flashing, different ones for editing and collecting ecu definitions somewhere from the net by spending hours which I am not sure about its reliability. I just want install the program and focus on tuning of my car that is all I want. Does ecuedit provide these to me?

I am looking forward to hearing from you.
Thanks.

sti_06 wrote:Hi,

I am planning the buying full version but I have some questions;

1- I downloaded the trial version. But I could not open my ecu rom file. I would like to see which maps ecuedit have and its structure. But how?

2- Will there be ecu definitions like in ecuflash or romraider or should I obtain definitions somewhere in the net?

You needs XML ECU definitions. Program don't distribute with ECU XML descriptions.

For Subaru ECU you can use xmlwrite for automatic generation XML. XMLWrite
generate descriptions which are equal Ec#Tek descriptions.

Also I have XMLs for most EVO and Subaru ECUs, which are available for registered users.

sti_06 wrote:3- I tried to use ecuflash and romraider definitions to open my rom but I could not.

ecuEdit have built in convert functions for converting ecuFlash and enginuity (romraider) definitions to self format. You can use it in trial-version.

sti_06 wrote:3- I have an 2006 EDM STI. After buying, shall I get definition support just for my current car? If so should I buy new one when I change my car?

No, I don't support definitions.

sti_06 wrote:4- Can I install more than one notebook and use. Because I have more than one.

Yes, license is per-user

sti_06 wrote:5- Can I use openport 1.2 dbw usb cable for flashing/editing/logging?

Yes, but reading/flashing for DBW Subaru is not supported yet. Coming soon.

sti_06 wrote:6- I want to have a user friendly program. I don't want use different programs for flashing, different ones for editing and collecting ecu definitions somewhere from the net by spending hours which I am not sure about its reliability. I just want install the program and focus on tuning of my car that is all I want. Does ecuedit provide these to me?

This is your choice All that you need (that not included in ecuEdit package) is ECU descriptions (which are can be converted or generated by XMLWrite). DBW flashing is coming soon.

Hi,

I am a little bit confused therefore I have some more to ask you,

1- You mean that you'll not support XML ecu definitions(Especially for my 2006 EDM STI) if I buy the Ecuedit.

2- In trial version, I used built in converter in ecuedit to convert ecuflash and romraider xml ecu definitions. It works, but MAF Table Map was not converted smooth. The values in table are mixed. Why? I tried both ecuflash and romraider definitions to convert but the result was same.

3- You mention about converting and generating XML ecu definitions. Do you mean by ''converting'' is the same that I talked about above? What is ''generating'' ecu desribtion by using XMLwrite? I am not a computer expert, how can ı do that? Can't you provide them for me?(especially just for my ecu)

4- If I buy the ecuedit Logger only, Also Will there be XML definitons problem while logging?

5- You say there is no reading/flashing support for DBW ecus yet. So, I will use ecuflash for reading/flashing. Will there be any problem since I will edit maps by ecuedit and flashes by ecuflash?(any sync. problem?)

6- Another question is in your PM. That is quite important for me and any help about it will be appreciated.

Thanks. Looking forward to hearing from you.

sti_06 wrote:1- You mean that you'll not support XML ecu definitions(Especially for my 2006 EDM STI) if I buy the Ecuedit.

Exactly. I don't edit descriptions, don't add new maps, don't add new ECUs, etc. ecuEdit have built-in map descriptions editor.

sti_06 wrote:2- In trial version, I used built in converter in ecuedit to convert ecuflash and romraider xml ecu definitions. It works, but MAF Table Map was not converted smooth. The values in table are mixed. Why? I tried both ecuflash and romraider definitions to convert but the result was same.

Try to open this map in EcuFlash/Enginuity. If it looks correct, please point me ECU ID, and I check it. If not, problem is in descriptions.

sti_06 wrote:3- You mention about converting and generating XML ecu definitions. Do you mean by ''converting'' is the same that I talked about above? What is ''generating'' ecu desribtion by using XMLwrite? I am not a computer expert, how can ı do that? Can't you provide them for me?(especially just for my ecu)

XMLWrite contains descriptions for most Subaru ECUs, and it's generate description by request.

sti_06 wrote:4- If I buy the ecuedit Logger only, Also Will there be XML definitons problem while logging?

No, Logger descriptions are included

sti_06 wrote:5- You say there is no reading/flashing support for DBW ecus yet. So, I will use ecuflash for reading/flashing. Will there be any problem since I will edit maps by ecuedit and flashes by ecuflash?(any sync. problem?)

No, all be fine.

sti_06 wrote:6- Another question is in your PM. That is quite important for me and any help about it will be appreciated.

Ok