I've come up with a solution that seems to work well for me. The bike is running stronger than ever.

First, a thanks to Raz for his plug-in. Although I couldn't get it to work with Logworks3 (seems to be a port conflict problem on my computer) it has turned out to be the most reliable way for me to log from MyECU.

I spent way too much time chasing trim, trying to get every cell of the map perfect before realizing I should focus on where 98% of my riding is done.

Closed loop mode worked great when I was in cruise mode, but caused my grief when I was in the quickly changing sections of the map. So I identified where the "cruise cells" were and only activated closed loop mode for them, turned out there were about 15 total.

The bike accellerates like it was shot out of a gun, and cruises smoothly.

Pete

Yeah it's amazing how few cells are used in even a fairly long ride. Logging with O2 sensor is the best way to quickly get a good map.

Rat Patrol wrote on 01/10/11 at 07:08:03:

I couldn't get it to work with Logworks3 (seems to be a port conflict problem on my computer)

That's a pity cause logging in Logworks is way better for later analysis. Note that the plugin -> LW communication is very fragile. Always start the plugin first, then LogWorks. If you quit the plugin, you must quit LogWorks and restart the plugin, otherwise they will never find each other again. I can't do anything about it, I blame the API.

http://www.abc.se/~rasmus/pics/090927_O2_over_realmap.PNG

I really love this output from Logworks, the above is from a 45 minute ride and just a few processing steps. Note that WOT is bottom row here.

Oh, and another silly obstacle: You need to have the sensor digital output connected to Logworks in order for it to listen to the plugin's channels. They did this because otherwise anyone could use Logworks without even having Innovate equipment, but it's a real PITA when testing stuff.

I'm not giving up yet! I'm running the DL-32 inputs through a usb-serial adapter and the 16M data through the serial port. I'll play around with the setup some more.

I'm using an older laptop with winXP and the thing is just barely chugging along. The problem is more with LW3 than your plugin.

The plugin will initialize and run normally, but nothing comes in on LW3 other than the LC-1's and the DL-32 inputs. Do I need to do any kind of setup on LW? or should I just see the additional channels?

When I've got some time, I'll take my front line laptop and give that a try. Problem is it doesn't have a serial port and i'll have to run both units off a usb-serial adapter.

Is there any way to take a log file and import it into LW after the fact?

I have been able to pull the log files into Microsoft Excel and do some cool things with them manually. It's been a great help.

pete

Hi Raz,

can you enlighten me a bit where to get the plug in and how to use it? Do I have to have the Laptop running and connected to the LM-2 and the My16M during riding to get these figures?

Thanks a lot

Rat Patrol wrote on 01/11/11 at 10:11:05:

The plugin will initialize and run normally, but nothing comes in on LW3 other than the LC-1's and the DL-32 inputs. Do I need to do any kind of setup on LW? or should I just see the additional channels?

Given you can create MyECU logs with the plugin, it should just work right away. I think the first time the plugin is running when LW3 is started (with a live DL-32 and/or LC-1 connected to laptop too), a window should pop up asking you to confirm all MyECU channels. Otherwise you should be able to add them manually (Channels->Configure, or Configuraion Wizard).



Rat Patrol wrote on 01/11/11 at 10:11:05:

Is there any way to take a log file and import it into LW after the fact?

Sure, here is the one (I think) that made the chart I posted: http://www.abc.se/~rasmus/logworks/0909271529b.log (there were some problem with the GPS cable so speed is not always logged). You should be able to load this file in LogWorks3 and see all data, filter it in numerous ways, and even re-create the chart (with filters if you like) from menu View->Chart from Template



Laverdalothar wrote on 01/11/11 at 18:51:31:

can you enlighten me a bit where to get the plug in and how to use it? Do I have to have the Laptop running and connected to the LM-2 and the My16M during riding to get these figures?

Plugin and readme here: http://www.abc.se/~rasmus/logworks/. You need a laptop in a tank bag, connected to the LM-2 as well as to the "Optimiser cable" from the ECU. All cables and shite make a greater mess than you can imagine. Then just log and ride, all the magic is performed afterwards. Do backup the log file, it's easy to destroy data.

...and use the latest LogWorks version, from here: http://www.innovatemotorsports.com/support.php

Raz, thanks for your response. After reading your comments I'm certain that my problem is related to port conflict issues.

I won't have a chance to address this until this weekend. But I'll try to sort things out then.

Pete

Hi Raz,

thanks a lot, but the info in the Readme does not tell how to install it etc.

Maybe you could update that with a section telling what to do how to install it. Also - which one to choose? There are I think 5 different versions...

thanks

Laverdalothar wrote on 01/15/11 at 02:50:27:

Hi Raz, thanks a lot, but the info in the Readme does not tell how to install it etc. Maybe you could update that with a section telling what to do how to install it. Also - which one to choose? There are I think 5 different versions... thanks

There is no installation. Unpack it wherever you like and run it off there by double clicking the .exe file. Create a shortcut to the desktop or the start menu manually if you like.

There are currently three versions there, MyECUplugin_090927.zip, MyECUplugin_091006.zip and MyECUPlugin_100214.zip. The digits are the date, in YYMMDD so MyECUPlugin_100214.zip is the latest and this one has the 56K baudrate. The MyECUplugin_091006.zip could be used if you have older firmware with the slower baudrate. The oldest one I suppose I should remove, there is no reason for using it.

The files with "_src_" in the name are source code archives for the respective version and only used if you want to modify it or recompile it in a newer environment.

Thanks - much clearer now... :-)

have two to three other projects waiting, but I guess when the weather starts getting better, I will be starting with your plugin. Would be great if that could be part of the "how-to" section on Cliffs homepage...  ;)

LaverdaL,

One bit of advice i'll offer. My computer is very picky about ports. If I have any other device connected it won't read the data from the plugin.

Also, if I have the ECU connected through the serial port and am usung the ECU controller software I have to power down the computer and restart.

This is an older laptop with XP.

thanks for the hint, hope to remember that once I get started with the controller...

Rat,

I have looked into logworks and seam not to be able to set the values like in the map (TPS, Rev-brake-points). Did you manage to change that? I only tried it with your maps, so not sure if that makes any change?!?

Logworks only allows for a range of values and number of values and then makes the steps itself...  :-/

I may be misunderstanding the question, but Logworks is a program for recording and displaying data. It doesn't allow any changes to any of the monitored inputs.

It works very well for displaying and analysing data, but it does require hardware from the folks at Innovate Motorsports to work.

ECU controller, on the other hand, allows full control over most any engine parameter, and the ones that aren't directly controlled can be easily edited in a text editor.

pete

Hi Pete,

I am well aware that you need the according HW (LM-2 - which I have...). The point is, that with Raz plug in, you can track the Data from the MyECU16 f.e. into the LogWorks Software as far as I understand it (the right tools assumed...), but you only track the measured values, not the brake-points of a map (which is - as you correctly said - changed and programed via Ecu Controller software).

Now - when you track the Data into Logworks, Logworks is capable to show you the values as in the picture above shown by Raz, but you have to tell Logworks which STEPS you want to be shown. This is where the problem starts, as the Steps in Logworks are never the same as in your Map as far as I understand it.

But maybe Raz can comment a bit better than me with my just slightly improved school english. Maybe², I might be thinking into the totally wrong direction - Raz might be able to tell maybe?!?

What I tried as an output is showing the AF-Ratio against TPS-Value and Revs, just like Raz did. As you can see on his chart, the values are RPM 1- 15.000 in steps of 1.000 and TPS in values of 0 - 14. This is for sure NOT what the map looks like on his myECU. You can either make it more granular until you end up with values that are very close to your Map (maybe close enough to get the rest sorted with the Optimizer) or change your Map accordingly which I think is no good Idea, as you need more granular settings on lower revs where the higher you get the less changes will be done (just like with carbs: low end is influenced by more parameters than WOT).

Clearer now?  :-/

Got it. Although I had some success with Raz's plug-in, my computer would not let me run it and LogWorks simultaneously, so I was never able to take advantage of the advanced features. Port conflicts tied me in knots.

I used it solely to log data which was not being monitored by the DL-32. I then pulled the Raz log into excel and played with charts and graphs there.

pete

Laverdalothar wrote on 02/08/11 at 03:43:00:

What I tried as an output is showing the AF-Ratio against TPS-Value and Revs, just like Raz did. As you can see on his chart, the values are RPM 1- 15.000 in steps of 1.000 and TPS in values of 0 - 14. This is for sure NOT what the map looks like on his myECU.

I don't remember all the details, but I might actually have used linear breakpoints when I played with this. My THR breaks has always been linear and my RPM breaks works just fine in steps of 500 rpm (it's actually not that uncommon in ECUs and I've seen at least one "pro" recommending it). I have tried that a lot and sometimes I even thought it worked better. One reason for that may be that Autotune got "more stable" readings low end as the breakpoints was more spaced so it tuned a larger part of the map. I actually never experienced any downside. I went back to the default RPM breaks only because it's easier to compare my maps to others!

Anways, Logworks is very very powerful but it is also buggy (random crashes) and this map-correction feature is a pig to complete. I never got beyond playing with it. I'm sure a future version of ECUControl software could do this better, quicker and easier, if we can persuade Cliff to implement it.