Hi All,

I got a 1997 Ducati 916 Monoposto on which I have replaced the Magnetti Marelli device by a MkiV My16M.
I have also added two O2 sensor with exhaust pipe modification.
No hardware issues, quick support from Cliff and first electrical testing OK.
First "firing" test, bike completly cold, and with some efforts and with the "Sport.ecu" file provided, it fires ...
I spend some time to find a good idle, but I struggle a lot guessing that the map I got was too reach.
I finally hat to do a road test cause i was changing of house ! A bike not driveable at all ...

A few months later, I get everyhting out of the garage and work on it.
As the bike was running very badly, I got an Original Magnetti Marelli dump file from stock 916, spend 3 days to interpolate everything and calculate a new base map : Injection Duration AND Spark advance.
I build the file, load it into My ECU, start the bike ... it works. And pretty well in fact.
I ride it a few km with some idea to optimise 2 or 3 things.

The next day, I took the bike for 30 km in the morning.
Surprisingly, it seems to work not as good as the previous day : the morning temperature was quite lower ... ???
The bike stalls 3 or 4 times at very low regime.
I take it at the end of the afternoon to come back home (quite higher temperature) but same thing.
After having a look at the map, I find that at low TPS and RPM, there was a "hole" in the injection duration.
I build a new file and open the ECUcontrol1.50.
And then several issues :
- The loading operation of the map seems to "never end" : the cursor moves along the whole map and I have finally to close the program after 5 iteration of that kind. It works perfectly well with old "ecu" file -> is it a question of format ?
- More annoying issue : my idle TPS that was around 65-70 at idle is now around 300 when I turn on the bike AND the maximum achievable TPS that was around 900 is now around 700 -> Electrical Issue ??? And the RPM moves from 1500 to 5000 lots of time ...

Have a play with the beta I announced earlier. The map transfer is completely new and you should not see that issue.

Not sure about the TPS. Are you talking about the TPS base value or the real-time throttle value.

Ok, I will test the Beta version tomorrow.

I'm really confused for the TPS and try this evening to start the bike. It starts but work really bad.
The real-time RPM moves from 1500 to 5000 each 4 or 5 seconds and then comes back but the real RPM of the engine (by hear) must be ~1500.
Before starting, the real-time throttle value is about 280-300 without touching anything and the bike starts like that ...
Everything seems to work like if real-time RPM and real-time TPS were "false" ...

I will report after the Beta test, thanks !

Are you talking about what the tacho is doing?

Your throttle sounds out. Typically the idle TPS will be 50 to 150. What is the actual voltage from the throttle. It should be about 1/2V which should give a reading of 100.

Absolutly, I was talking about the Tacho : the real RPM doesn't move at all.

I download the ECUcontroller Version1.60b this afternoon.
Launch it ...
Indicated ECUcontroller TPS around 180.
I take the last modified map I got and load it to the ECU.
It seems to work well with no more loading issues, you were right.

I shut down and then dismantle the ECU connector to get the TPS measured value  as you have suggested.
Re-plug everything, contact on and WITHOUT doing anything :
Indicated ECUcontroller TPS around 60.
Max Indicated ECUcontroller TPS around 1000 when I move the throtlle !

But short time joy ...
A few seconds after, without touching the key or the ON/OFF button, the ECU re-initialize itself (fuel pump sound and so on)
AND ...
Indicated ECUcontroller TPS around 600, Pressure, Temperature and Battery Voltage completly false (1070mb / -20°/14,8 V).
I try to disconnect everything and wait some time but nothing change.
At least, this re-initialize phenomenom occurs each 5 or 10 seconds.
:-X
I've tried to measure the TPS and found around 380 mV, but really not sure ...

I Do not touch anything for an hour to change my mind !


Re-plug everyhting and this time I check with the optimiser.
Indicated TPS around 100 !
And a few seconds later after having moved the throttle : 60.
I check with ECUcontroller1.60 : same thing, real-time TPS around 60, eveything stable, a "re-init" of the fuel pump after maybe 1 minute but same values and still stable after ...
The air pressure value seems low (944 mB) but if I remember well it was a subject of another topic. The battery voltage was indicated at 10,8V, low also ?

I've checked several times in the past few hours and it doesn't move anymore.
Weather too bad for a road test today. I'll try tomorrow if I find some time and maybe play a little with the Optimiser after.

The tacho behaviour could be that you have that rpm/throttle function enabled. Your switches in the ECU should be set to On,Off,On,Off

Not sure about your over symptoms. Fortunately they occur with out you having to get on the road.

Did you clean the circuit board after construction? The MyECU input circuits are high impedance and can be affected dirt.

60 sounds like the value you should be getting.

The resetting could be a power supply issue. A LED and limit resistor across the input of the 5V regulator and ground  is  good way to see if there are interruptions.

Quote:

The battery voltage was indicated at 10,8V, low also ?

Very low. You need a battery showing 12.5V or more.
Lotsa strange behaviour can occur if low voltage.
Is it that low measured directly at battery?

- Tacho behaviour : thanks for the SW3 tip. I've read 10 times the documents and even missed it ... It seems to work after correction.
- Battery voltage : it was the value displayed on the optimiser ... I've checked directly on the battery, quite better. The battery is almost new but you're right. If such phenomenon keeps appearing, i'll try to change it.

I've made more tests this afternoon and have done some work on the map. As I've seen in another post, I have to adjust the Prime table because the bike needs some throttle to start.
I have also set the TPS Base to 0, it recalculates each time.
My Idle configuration has to be optimised also I guess : Tps Base = 39 / Idle at 57 / Fast Idle around 80. The bike does not handle very well and finally stalls at idle.
What annoys me is that after having stalled, the TPS Base and Idle values are some times quite higher : base at 60 or 70 and Idle at 85 or 100 ... ??? And at a previous TPS value (80) where it was running quite well a few minutes earlier, now it struggles and stalls ...

Other question : I've kept for the moment the SW1 "ON". In the ECU file, i let the O2 sensors to 0.
Does the 2 sensors work with the Optimiser - Autotune menu with such a configuration ?
I'm waiting for the bike to get hot but still have the "Man" setting in the Autotune menu.

Until you get correct values for all the analogs and not have the ECU resetting for no reason, it is pointless to even start the bike.
Closed loop you should also not be considering at the moment.

The changing TPS values could indicate wear in the throttle bodies/linkages but in light of the other strangle behaviour it may be something in the ECU.

The analog inputs ( 7 of them ) are on the main chip are from pin 40 down. That's the top left pins of the chip. Find out which one corresponds to the throttle and you can use that as a convenient test point. Let us know which one it is as I'm not near any bikes at the moment. This will be for the My16M only.

Hi,
Thanks for your feedback.
I spend some times in the last weeks to check the "basics" :
dismount of everything, re-put in place the MM1.6, complete check-up of the TPS and setting of the TPS Base by adjustment of the TPS sensor after having cleaned and putted some lubricant.
With all that, I check that the bike starts well.
I then re-put in place the MyECU 16M.
The TPS at idle seems now OK around 64, and even better it seems stable.
I will test the start this week-end, and therefore I'm currently checking my Map and have a last question !
I apologize in advance if I've missed something ...

The Power stoke TDC reference : "TDC=0x1600", which corresponds to a number of Pulse equal to 22 on the 47 teeth (one missing) timing gear if I've well understood ?
Why "22" ?
Does it come from the factory with the way the timing gear is implemented on the camshaft ?
How do you determine it ?

Regards ...

Yes thats the way it comes from the factory. Don't change this.

OK.
Therefore, the InjAdv and SpkAdv info in Degrees are given relative to a 0-720° full cycle,
with the absolute reference 0° = TDC Power Stroke = Pulse 22 on the timing wheel.
I am right ?

That's correct.

Perfect, thanks !
Just to be sure : InjAdv specifies the leading edge or trailing edge of the injection pulse ?

Trailing edge

I finally check everything on Saturday and reload a clean map.
TPS at idle still at 64.
The bike starts well, runs perfectly on fast idle to get warm.
Some optimization to do on idle as it stalls, but everything in order.

I decide to take some time on Sunday to finalize the idle setting.
Contact On ... No fuel pump noise !
:-/
I check the fuse, and the 15A master under the seat seems to have face a very hot period.
I change it ... nothing better.

I put in place the original MM1.6, and then it works ...
I will try to redo the basic testings of the board after its build, but it sounds not good at all ...

The only components that can draw significant current are the spark FETs. Check them and the PCB in that area for any signs of heat.

I think I know what has gone wrong with your board as I've recently become aware of a weakness in the My16M MkIV design.

To test, put the ECU on the bike with the ignition OFF.
Check the voltage on the small surface mount FET nearest to the inductor L2. The tab of that FET should be at battery voltage as it should be off. If it is not that transistor has failed.

This transistor drives the ECU power relay so in fact the ECU is now permanently powered. That's the reason you don't hear the fuel pump, the ECU hasn't powered up. Its been up all the time. If you crank, it will probably start.

To fix the problem you will need to replace that small FET and in addition a small 0.1uf capacitor should be soldered across R9G, just below that FET, to prevent the problem occurring again.

If I've well understood, I've checked the voltage on the Q6 upper tab which is the closest from L2.
I've searched before for any signs of heat but no evidence.
Everything shut off, I find 13,20 V.
This transistor seems to be still alive, no ?

However, which voltage for the 0,1uf capacitor across the R9G ?

Yes that sounds ok.
Just a standard monolithic cap like all the blue ones. They're typically rated 50V.

At any stage you can send the ECU to me and I'll sort it out.

The next thing to check are the voltages on the voltage regulator. 0V off and about 14V in and 5V out when on.

Does the ECU still communicate?

Check the operation of the small FET next to the one we just looked at. It drives the fuel pump relay. Do you see a 5V pulse on its gate for 2 seconds? Does its tab pull to 0V for that time?

"At any stage you can send the ECU to me and I'll sort it out."
Thanks. I'll try to test everything before !  :)

"Does the ECU still communicate ?"
It doesn't seem. The Controller1.60b doesn't manage to complete an upload or a download ...

"The next thing to check are the voltages on the voltage regulator. 0V off and about 14V in and 5V out when on.
heck the operation of the small FET next to the one we just looked at. It drives the fuel pump relay. Do you see a 5V pulse on its gate for 2 seconds? Does its tab pull to 0V for that time? "
Some tests tonight after having reloaded the battery.
Contact OFF :
- small surface mount FET nearest to the inductor L2
   Base 13,55V / Gates from left to right : 0 / 13,55 / 0
- small FET next to the first one
   Base 0V / Gates from left to right : 0 / 0 / 0
- voltage regulator
   Base 0V / Gates from left to right : 0 / 0

Contact ON :
- small surface mount FET nearest to the inductor L2
   Base 0V / Gates from left to right : 6,6 / 0,01 / 0
- small FET next to the first one
   Base 13,14V / Gates from left to right : 0,003 / 13,14 / 0
   No signs of any 5V pulse (checked twice ...)
- voltage regulator
   Base 0V / Gates from left to right : 19 (?) / 5

I think the lack of comms and 5V pulse means that the chip needs to be reflashed.

Do you want to give that a go?
Here is a link to the procedure.

http://www.cajinnovations.com/MyECU/FirmwareUpgrading.htm

TDC=0x1600 means that TDC is 22 pulse after the missing one?
if i want to set the TDC for example 1 or 2 pulse after the missing pulse how i have to set?
thx

You would set them to 0x0000, 0x0100, 0x0200, ...
Why would you want to do that? That is a ECU/bike configuration item, not a tuning item.

because i have to put myecu not in a ducati or guzzi engine, and i have to set another pulse weels and another TDC position, 0x0100 at what pulse after the missing one is?
thx again

YaBB Administrator wrote on 06/15/11 at 08:01:20:

I think the lack of comms and 5V pulse means that the chip needs to be reflashed. Do you want to give that a go? Here is a link to the procedure. http://www.cajinnovations.com/MyECU/FirmwareUpgrading.htm

Thanks !
Why not, I think it's worth trying it ...
and it should be usefull in the future.
I need to buy the different parts needed for the cable and I'll tell you when I got everything as I will need the "hex" file I suppose ?

Send me an email when you're ready and I'll send you the hex file.

Hi,
Back on the forum ...
The FLASH operation seems to have work fine.
I've done some map comparisons before/after having loaded them into the ECU.
I've understood that InjDur should be a multiple of 16.
Is there such a rule for RPM or for SpkAdv as there are some minor differences between the 2 files when I get it from the ECU ?

There's no simple rules for the rounding of the others.
The RPM is actually stored as a time period and spark advance depends on the ECU configuration.

The main thing is the difference will be small and only occur the once after hand editing.

It makes sense to upload the map after download and use that map as the basis of future maps.