ecuEdit v2.4 - ECU Tuning & Logging solution

[Jeramie]

For free, oc. We are developing soft in different tools and I'm made offer to use ecuEdit as DLL, with export functions thats Calvin need. I said, that would be good, bc Calvin may start to realize Log viewer for ecuExplorer that most required than map editor, imho...

Thats great to hear. Open source is a wonderfull thing!

[Xmicho]

Hi Epifan, just wanted to say what a great job you're doing and that this is a wonderful software. Thanks for taking the time.

Also a question, would you be able to post the rom image that you used for the xml definitions for this version. It would make it easier for me to find the same info on my ecu (Euro A4SE900D). Many thanks, again.

[calvinc]

Month ago I'm propose to Calvin to use ecuEdit ability in ecuExplorer, but Calvin refused this... So, may be, he have some own different vision of map editor functionality and realization.

For free, oc. We are developing soft in different tools and I'm made offer to use ecuEdit as DLL, with export functions thats Calvin need. I said, that would be good, bc Calvin may start to realize Log viewer for ecuExplorer that most required than map editor, imho...

epifan did contact me to include his app but i made the decision not to purely based on the fact that i couldnt include the source code. it would have to be a dll file. if the source for ecuExplorer gets released i would prefer it to be complete and able to be modified in its entirety.

that said, i think epifan is doing a great job and his app is certainly helping this community.

the reason for ecuExplorer not having any graphical portions yet is because i have been battling to find a free charting tool in source code form. i have recently found something that may do the trick. i do agree that this is 1 of the big missing features from ecuExplorer.

next release will have OpenPort 1.2 support along with the Innovate Motorsports LM-1 wideband sensor protocol for true AFR logging. thereafter map editing and hopefully the starts of graphing functionality.

everybody has different ideas and features that they think are useful and neccessary. having a few different apps available makes the development pot and choices that much more exciting.

calvin.

[west_minist]

Nice Calvin!

Hopefully, it will have LC-1 support

Sounds very nice.

Good luck.

[crazymikie]

Hi Calvin-

I have an AEM Uego wideband which I like a lot- more compact than the LM1, although in the end, they do the same job.

Any chance of supporting that? It's just a serial output or ASCII data. You can simply log into the gauge via hyperterminal and read the output.

Thanks
Mike

[west_minist]

try the LC-1 & XD-1

[calvinc]

Any chance of supporting that? It's just a serial output or ASCII data. You can simply log into the gauge via hyperterminal and read the output.

if you have any details on the protocol please send it on. if i recall someone has also asked for PLX support. i chose the LM-1 because i believe it to be the best product in its arena, plus its the one i use for remapping.

calvin.

[gregsachs]

The uego seems to just spit out 14.1^m, 14.0^m, etc at I think 9600. (documentation is at home). (^m is linefeed/control m charatcter).

[Kha0S]

calvin --

I currently use the TechEdge WBO2 20A, which has a publicized protocol... I would love to be able to use it in ecuExplorer.

I know that implementing every wideband is very time consuming... perhaps it would be possible to implement a plugin-type architecture which motivated programmers (like myself) could write ecuExplorer plugins for WB meters, LabJack and other A/D acquisition boards, etc.?

[gregsachs]

could xml be used to define auxilary variables to be read in/time stamped? IE define a variable as WB02, comX, 9600, and then a basic protocol format? There are some OPC servers that work like that.(kepware, omniserver) I'd think most of what is needed for interpreting a serial variable is knowing the delimiter and how frequently it updates, right?

[Kha0S]

greg -- neat idea... another interesting option is having a TCP/IP local connection, so an application designed to talk over the serial port can simply connect to ecuExplorer and feed it data, or vice versa.

[Freon]

I actually used to work on serial data acquisition software for collecting data from output ports on phone systems (through SMDR). We had a nice piece of software that funtioned on simple bitmask config files in text format. It was a pretty good system considering the different types of phone systems with which we could make it work. Basically you need basic serial port info (port#, baud, D-P-S bits), and create the bitmask, something like
[Number]<startbyte=4><length=9><Mask=##########>
[Date]<startbyte=15><length=5><Mask=##/##>
[Time]<startbyte=21><length=8><Mask=##:##:##>
[OtherFlags]<EOLasciicharnumber=11><Linesperdata=1>
etc.
The data input would look something like this
$K 8881239876 01/18 13:13:43 00:43
With Ascii char 11 as a line feed.

That's something the average Joe could grasp. It really only failed if the output from the phone system either liked to die for no reason, or if it was variable width or something. Anyway, something to think about.

If you're doing LM-1 support, do you plan on including the ability to log the aux inputs of the LM-1 as well as just the AF?

[crazymikie]

[quote="gregsachs"]The uego seems to just spit out 14.1^m, 14.0^m, etc at I think 9600. (documentation is at home). (^m is linefeed/control m charatcter).[/quote]

That's it- 9600 baud N/8/1

Please let me know if I can help at all.

Thanks!
Mike

[epifan]

New ecuEdit v1.2.0.33
- Log Viewer: Custom 2d, 3d graphs and other improvements
- Support different file and description sizes: open 160K bin file by 192K-offset description and vice versa
- Map clipboard (Copy and paste data from another maps)

Download ecuEdit v1.2.0.33

Insert in your ecuEdit.xml <config> tag for support 160K... by 192K...

Code: Select all

   <config>
      <map_id offset="#00200" length="8"/>
      <region offset="#00209" length="2"/>
      <offset_calc desc_size="#30000" file_size="#28000" func_val2="if(([value] >= 131072),[value]+32768,[value])" func_2val="if(([value] >= 131072),if(([value] >= 163840),[value] - 32768,131072),[value])"/>
      <default_desc_size value="#30000"/>
   </config>


[epifan]

New ecuEdit v.1.2.0.36
- Support 32-bit ECU
- Log Viewer: functions support for convert log data (time and data conversion)
- New tag <ecu_desc> in <config> for describe map ID's

Download ecuEdit v.1.2.0.36

Code: Select all

   <config>
...
      <ecu_desc file_size="#30000">
         <map_id offset="#00200" length="8"/>
         <region offset="#00209" length="2"/>
                </ecu_desc>
      <ecu_desc file_size="#80000">
         <map_id offset="#002000" length="8"/>
         <region offset="#00200B" length="2"/>
                </ecu_desc>
...
   </config>