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

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

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.



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.

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

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

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:

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:

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

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

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... 

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

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