Hi Guys .  Myself and a couple of other owners of tweaked Centauros are embarking on a mission to gain a full understanding of Cliff's My16M.
I have used one for some years with a Phil A. map installed and have done nothing than alter a couple of the prime/crank numbers at his suggestion.
I/we are going for Innovate's LC1 since reading Cliff's recommendation , that seems sound .
Could someone confirm for me please : that an LC1 hooked-up to my My16 will influence the mapping ? If it does , does it influence the entire map - I saw reference to a change factor of 20% . If what I have installed is a reasonable basemap and hook-up an LC1 is the overwriting done effectively an - 'Autotune' ?
The consensus here (glad all you guzzi owners inhabit !) seems to be that the big twins like to run a bit richer than stoichiometric. What's the plan ? Run the bike for a while then load out the - perhaps modified - map and scrutinise it ?
You must excuse what may seem like dumb questions but I'm starting out here :-/
Another question . Global Adjust . Perhaps my learning is woefully incomplete : here goes.....how to ? and is this actually an adjustment across the board as name suggests?
If the guzzi does like a richer running but the LC1 wants to put the numbers close to Lambda , how do you stop that from happening ? "correct" the map and run open loop ?

So many questions ....still more to come  :o
Hope you can begin educating us . Thanks.D.

A MyECU just running closed loop will adjust the injection duration dynamically with good results, but the base map does not change. But if you also hook up an Optimizer and put it in Auto Tune mode, the base map will be adjusted. I ran tens of thousands of kilometers that way until my LC-1 sensor went tits up. At that point the map was so good I decided to just run open loop from then on. That map is avaiable here by the way, works fine with many Daytona RS and Centauros too.

I used A/F targets of about 13:1 if I recall correctly (there should be plenty of forum history if you search) and a little leaner at cruise areas of the map.

After a look at the Raz map, this is the A/F targets I actually used at the time:


Code:

# A/F ratio        13.67  13.52  13.38  13.23  13.08  12.94  12.79 # Lambda            0.93   0.92   0.91   0.90   0.89   0.88   0.87 # CO                2.3%   2.7%   3.1%   3.5%   3.9%   4.3%   4.7% MyECU Cfg O2=0.00V,-2.10V,-2.05V,-2.00V,-1.96V,-1.91V,-1.86V,-1.81V,

Comments are inserted to show what the voltages (default LC-1 settings) mean (the CO values are a very rough formula though). For cruising, I went as "lean" as 13.7 and at WOT I went no richer than 12.8. This table settled after a crazy amount of testing.

Thanks for your prompt  response Raz.
The injection duration line is the one we're concerned with here then , from a rich/lean point of view ? Is this the only line influenced by the LC1 being hooked-up to the My16 ?
I can borrow an Optimiser but don't know the vintage . Barring the Android version being developed were they all the same , and am I right in thinking that while they display live running , they do not log a run . I have been thinking that as this is a 3way project then the purchase of Innovate's LM2 could be worthwhile .
I see the need to keep a basemap filed carefully away.
D.

The only thing that closed loop affects is injection duration. You can set target A/F per cell.

I did the logging directly from MyECU to a laptop or pocket Windows device, first using a cable and later on using Bluetooth. Some product like LM2 might be more handy but it would not log MyECU data like throttle position, rpm, temps so it can be harder to parse correctly. You can buy rpm sensors and whatnot to the LM2 but if you log from MyECU to some device (be it a smartphone) you will get all of it for free.

I haven't tried the Android stuff. Nowadays, I just ride  :)

The Android version could include speed, altitude and such stuff from the GPS built-in to the smartphone. I have no idea if that is implemented.

When you say " I did my logging from ECU via cable to pc and later by bluetooth" do you mean you checked what changes the LC1 had made to inj dur line? - you would have had to have used the optimiser to fix the changes, in order to see them yes?
Could someone confirm the Optimiser query pls.
what pre android versions capable of doing? Sorry !!
D.

When running Autotune (logging or not) I often verified the map saved before the ride with the new map when I got home. I used a little perl script that could output the diffs in a comprehensible way. I typically edit the maps manually, using a text editor no more fancy than Notepad on Windows.

When logging a ride, I also used GPS data to get speed into the mix. I wrote a plugin for Innovate Logworks that is pretty cool. It's all in this forum's history. The plugin can be found here although I have no idea if it works with latest Innovate software. Among many other things it could produce graphs like this one:

http://www.abc.se/~rasmus/logworks/090927_O2_over_realmap.PNG
Note: In this graph, the idle cell is top left. Also, this is "real thottle": Figures are re-calculated as if there was no throttle pump emulation.

I think it's time for me to do some more reading  :o

Hurrah! Raz is back.

The trouble with reading is that it leads to more questions...this one probably for Cliff. The earlier MY16 I have here we have determined to be  Mk2. I have held off from buying an LM2 for datalogging purposes .......for now.I have downloaded to my Smartphone the latest controller...question is will my vintage My16 be accomodating a Bluetooth hookup ?
D.           TIA.

Yes, even the earliest MyECU had the RJ45 connector that is still ok. What you need to do is upgrade the firmware and given the vintage you should do that by getting a spare ECU chip rather than re-flashing. This way will also give you the fall back option.

Thanks Cliff , you just answered the chip question I came back to ask
,so it is still available :-) Will get myself updated asap.
Took on board what you said re LM2 and have left it for time being.
D.

Hi again peeps. Whilst I await delivery of LC1 I ponder the wiring access into Ecu case. Raz mentions using MM diagnostic points for access but his link to Elva parts no longer work.
There are quite a few empty female sockets in OEM connector- if I source a s/h connector and pillage it for female contacts that would provide lots more ways in wouldn't it ?   My16 M!!
D.

Talking to myself here  ;D     I'm both areyousure and onecentauro !
I just refreshed my memory and looked under the seat at the diagnostics situation . If it's pin10 that is dedicated only to diagnostics and the MY is not compatible in that regard could I cannibalise the "plug-in" to effect the connection ?
D.

Mad Farquhar wrote on 02/21/13 at 07:41:27:

Hurrah! Raz is back.

Heh, thanks  :)
Like I said though, I just ride now. My only plan during this winter is replacing fork seals. Then maybe do Norway again this summer. Norway is good stuff. Our hot rod V-twins really shine on serpentine roads!

One Centauro wrote on 02/26/13 at 04:09:52:

Talking to myself here  ;D     I'm both areyousure and onecentauro ! I just refreshed my memory and looked under the seat at the diagnostics situation . If it's pin10 that is dedicated only to diagnostics and the MY is not compatible in that regard could I cannibalise the "plug-in" to effect the connection ? D.

Stein-Dinse has the stuff you need for the diag connector, search for "Superseal". Or search for AMP/Superseal at other places, they are commonly available.

Thank you Raz . That's a really good way in :-)
D.

raz wrote on 02/26/13 at 06:30:05:

Norway is good stuff. Our hot rod V-twins really shine on serpentine roads!

Yup - did a trip from Bergen to Oslo via Geilo and back several, several years ago on a LM2 - pure dead brill.