I'm in the process of closing down the next release of all the components and require some advanced users to help check it out. Preferable those already familiar with the firmware upgrade procedure outlined here - http://www.cajinnovations.com/MyECU/Support_and_troubleshooting.htm .

Please email me at ecu000@cajinnovations.com to participate.

New features are

MyECU
- serial baud rate changed from 38K to 56K
- throttle pump reduced to half of its original value ( still not configurable )
- Bluetooth ready.
- Change to o2 inputs configuration . (This requires 1 line change to map )
- My16M has code to activate a fan ( requires minor hardware mods )

Optimiser
- Required changes to keep it in sync with MyECU.
- New menu for o2 inputs.

ECUController
- Required changes to keep it in sync with MyECU.
- New menu for o2 inputs.
- Easier logging and formatting of logged data.
- Some logging diagnosis. Colourise map with o2 corrections

There is also a version of the ECUController for Windows Mobile 5 ( probably requires bluetooth to connect )

I'd thought I'd show off some of the new features.
First off the ECUDiagnotsics has a menu that allows easy logging of ECU data.
This can be simultaneously as raw data or formatted or the formatting can be done later.
http://www.cajinnovations.com/MyECU/pics/ECUDiagnostics.png

The Colorize allows the data to be more easily visualized. The following is of My Cali after a 1/2 hour ride. One is dots the other is lines. The bike was suffering a harsh on/off at the time.

http://www.cajinnovations.com/MyECU/pics/ECUColorize1.PNG
http://www.cajinnovations.com/MyECU/pics/ECUColorize2.PNG

Looks promising. :)
Could the logging show how close to AFR targets in closed loop as well?

I have previews of the next ECUController v160.

This version is a major departure from the previous versions in terms of the UI. One of the main aims of this redesign is a simplification. The main dialog has a lot of stuff removed so it's not in your face.


Some points to note

• Map transfer has been rewritten and presents a progress bar rather then the grid traversal.
  
• The ECU data display is removed - no more strange hex strings.
  
• Individual cell adjust has been moved into global map adjust.
  
• WRT global map adjust, the selection is with the mouse - left button down, drag, release. Selected cells turn red.
  
• Engine running warning displayed when necessary
  

With the global map adjust, if one cell is selected you get  the realtime ECU updating and exiting via ok commits the change. Selecting multiple cells is for offline use and does not update the ECU.




The Windows Mobile and Windows versions has been merged so some dialogs sizes may seem strange.

You can get the betas here. Expect bugs and please report them.
Suggestions for enhancement also accepted.

Only those with current version 15X can use this to talk to the ECU. Other users can play with offine mode only.

http://www.cajinnovations.com/ECUController160aWM5.zip
http://www.cajinnovations.com/ECUControl160aWin32.zip

Cannot open file, doesn`t seem to be valid
is the message when downloaded these.

Did you try and run the Windows Mobile version under Windows?

I also was unable to extract the zip file (Win32 version).

Message I got was that it was not a valid archive. Tried with two different unzip utilities.

pete

i have no problem to extract the file, download it again

When and by what method will the plebs get these ECUControl updates?

Nice. It still seems to work fine under Linux/Wine. I ran it with no ECU connected though.

So, when do we get an iPhone version?   8-)

I'm not sure what's going on with the invalid archives. At first I thought it was because I created files under linux but these where created under Windows XP.

I've uploaded the uncompressed executibles.

http://www.cajinnovations.com/ECUController160aWM5.exe
http://www.cajinnovations.com/ECUControl160aWin32.exe

An Android version is more probable than an iphone version. Maybe when Mr Jobs releases an SDK that doesn't require me to own  a Mac.

Upgrades are usually when required or desired. There hasn't been much need to upgrade in practise.

Seem to get max of 4096us on InjDur on cell edit page on all cells - is this an issue? No ecu connected - ovbiusly. EcuControl 1.60 used on Vista (ach spit) via Mac.

Might I suggest O2 targets are (also) given in volts on cell edit screen to avoid having to look up the text file / flick back to MyEcu config page for them. (minor)

Tried load from ecu to see what happened - seems to hang for ages - but it would, as nothing attached. Abort poll after say 30 secs might be useful.

Been remarked elsewhere I think - it's kind of a small screen presence. Overall feel pretty good.
Can files saved have a date/time stamp added to top line on map?

YaBB Administrator wrote on 02/06/11 at 06:13:21:

I'm not sure what's going on with the invalid archives.snip.

That worked for me.

Running on Windows XP, downloaded from ecu fine, logged fine, all seemed to work, but could not get a colorized map. I'm sure it's operator error. Can you run through the steps necessary?

Didn't attempt any changes to the map, but the click and drag selection seemed to work.

Also noticed the dispaly of a max injector duration of 4096 although a quick check with the earlier version showed the correct numbers.

For what it's worth, the error I was getting from the compressed files was that they were not a complete file, as though they were spanned.

Thanks for all your hard work.
Pete

The injector duration is a bug, well done.

For the colourised map you need two prerequisites

• A map loaded
  
• raw ecu data already captured  in a file from a ride - in closed loop
  

win32.exe now works f me, XP at home, no bike connected. Max Inj dur 4096 f me, too.

Does v1.60 work w W98 SE?
Now you don`t need to update eeprom after altering map?
What is AnEcho0-6 ?

YaBB Administrator wrote on 02/06/11 at 11:34:03:

...For the colourised map you need two prerequisites A map loaded raw ecu data already captured  in a file from a ride - in closed loop

This seems to work. I had to use an existing log file. The weather is rotten this weekend.

In the colorized map, what do the colors signify? Red=Lean? etc?

Also, could you eplain the function of the "Next" and "Previous" buttons?

pete

update eeprom is no longer needed as it is done automatically when you click ok. Click cancel if you don't want to keep changes.
Windows NT is required. This is the case with the 15X version also.
AnEcho0-6 is where the analog inputs will appear when online.
Red is rich, blue is lean. Normally all the ride is displayed. Options all you to select a number of data points displayed, hence the next/prev.

Hi Cliff,

that looks really like a big step into the right direction! ;) It currently looks like you have two layers of independent graphics laying above each other (the map-grid and the colorized brake-points). If you could manage to a) get the graphics larger (I'm getting old...  :-[) and get closer to the logworks look with Raz plug in which shows the cells that are not correct instead of points or lines, that would be just fantastic! Next step would be the auto correction function where - just like with the optimizer - the cells get updated automatically while you ride. THIS would be a killer feature I'd say... Not sure how much work that is, but I guess that would help people like me with very limited knowledge of the hole unit and it's programming to have fun with the thing.

Next then is a G-force sensor for best acceleration...  :D

just kidding (the last one I mean...).

Great job!

Laverdalothar wrote on 02/07/11 at 17:29:52:

If you could (...) get closer to the logworks look with Raz plug in which shows the cells that are not correct instead of points or lines, that would be just fantastic!

I agree with that. It's hard to read. Just make it a grid and color the whole cells. Unless you show some aspect of it now that would be lost? You don't really show cells now but coordinates with decimals, no? Theoretically this is probably better but still, it's very hard to read.


Laverdalothar wrote on 02/07/11 at 17:29:52:

Next step would be the auto correction function where - just like with the optimizer - the cells get updated automatically while you ride. THIS would be a killer feature I'd say...

I almost agree... I think it would be better to log a ride (or a dyno pull) and then have the program auto correct the map afterwards. Autotune has lots of limits that logging does not, especially if you log a long ride (or several dyno pulls) and look at the averages. I think the best results would be to ride in open loop but with an active sensor, then process the log.

Quote:

I think it would be better to log a ride (or a dyno pull) and then have the program auto correct the map afterwards. Autotune has lots of limits that logging does not, especially if you log a long ride (or several dyno pulls) and look at the averages. I think the best results would be to ride in open loop but with an active sensor, then process the log.

+1.

That`s what Logwork & Tunerpro does, seems to work wonderfully. You can make the software calculate how fuel to add from logged averages to get your A/F targets. 8-)
Gonna do this way this spring.

For those who are having problems with the download:  Windows sometimes downloads files as 8-bit ASCII instead of 16bit hex.  In that case you will get an error trying to unzip.  Check to make sure your download utility is configured properly.  Unfortunately, I don't know the specifics so I download with Linux and then extract it in Windows.  Hope this helps.

Next drop of the beta.

Changes since previous
1) Colorize map has been moved into the adjust map dialog.
2) Adjust map dialog is re-sizable in Win32.
3) Improvements in map cell selection.
4) Fixed injector duration bug. Now goes to 16K.
5) O2 voltage displayed for the o2 slider when adjusting cells.

For Windows Mobile 5 -  http://www.cajinnovations.com/ECUController160bWM5.exe
For Windows NT - http://www.cajinnovations.com/ECUControl160bWin32.exe

Hi Cliff,
is it possible to get a Controller 160 build especially for WInCE 6 320x240?

I recently bought meself a WinCE-6 based Tourmate MX350 motorcycle navigation unit. The desktop is accessible via 'MioPocket Mini 4.0 ', so I thought I might give this new Controller version a try.

Before I try to connect the My15M to bluetooth I thought it would make sense to get a working CE version before that. The actual WinMobile_5 version has problems with the screen size, especially the map is 3 or 4 times the screen size and there is no possibility to move it over the screen.

Maybe it's enough if you could just add two sliders to move around the windows on the screen.

Thx, Hubert

I'm fairly certain that my PDA is the same resolution. The program is designed to be run in portrait mode not landscape.

Then I'm out. Tried several apps, from t-man to rotate.exe, the screen is nailed to landscape. It's not Windows Mobile, it's a (chinese) CE-6.

I'll try and get a new version that supports landscape but it wont be soon.

That sounds good. Not having too much time for "leisure" projects not always is a bad thing :)

In the meantime I could try to attach the BT Module to the MyEcu. Is there a HowTo posted somewhere? 

hubert

And some raw data example for playing with it could also be helpfull I think.

There are only 4 wires you need to connect, 0V, 5V, Rx and Tx.

The 0V and 5V are actually in two conductors each but you only need one of each.

The easiest way to find them in the cable is to plug it into the ECU and use a multimeter to find the wires.
The Rx and Tx are easy to find on the My15M. They're the 2 plate thru holes between the chip and the crystal.


I don't have a BT module in front of me at the moment so I can't recall if it is marked. I'll check this evening.

From the ECU side, make sure that SW4 is on. You should notice a few seconds delay in priming the fuel pump because of the time to initialise the BT modem.

PS: I've just posted a link to the data for the bluetooth module.

Luhbo, just sent you an experimental version for landscape mode.

Yes, got it last weekend. Sorry for not answering immediately. In fact I wasn't prepared to get it so soon, so I still haven't the BT module running. Besides that all buttons work, I can load and save maps and so on. The window with the map grid still is too large (buttons still above the grid, large font, ...)
More as soon as I have a connection to the MyEcu.

I haven' done the Adjust map dialog or the Cell Edit. The breakpoints dialogs should be ok.

That's correct. Some screens work, some not yet.

No need to hurry btw. Wednesday night I bricked the GPS while trying to solve the Bluetooth comms problem by renaming the bluetooth.exe. Now the startup screen loops endlessly. No chance to get through to the desktop or to connect it to a pc. The problem is that it's a rom-less no-reset china cheapo :( It depends now on whether I can organise a warranty replace or not.

Update:
Got my China GPS back, new and working, but the unit wont connect to anything other but a headset. So I upgraded an HTC Magician to WM 6.x - and now I'm on :)

One problem is worth mentioning: get the Com port wrong and the proggy is stucked :( I changed it from Com1 to Com5 for instance (instead of Com6) what made the PDA freeze each time I started EcuControl. I found no other cure but making a hard reset. Where is this foggy .ini file hidden? Searched the registry even!

Once the bonding was successful the PDA / EcuControl connects quick and easy. No delay for the fuel pump btw. All menus work and have the right size.

More as soon as I'm back from the first test ride.

Hubert

Update II
From start http://img545.imageshack.us/img545/2984/startoptimise.jpg to a very good intermediate milestone http://img97.imageshack.us/img97/4780/endoptimise.jpg it took not more than 10 rather short logging sections. The result is a very much noticeable improvement both of driveability and topend power.
The combo ECUControl 1.60b/Bluetooth in my opinion absolutely sets the standard for the WM16/WM15 tuning tools. It works very efficiently onroad, on a dyno this will be even more the case, probably.

Problems? Of course, but mainly because WM6.5 is not XP, everything works different on this platform. The proggy itself is very much ok. You could pay for it even (still no Donate button on your site)!

Here you see how the module looks on the bike for now. Steampunk! I rather won't change it. Attach it when needed, the rest of the year keep it in your pocket.

http://img830.imageshack.us/img830/240/btmodule1.th.jpg http://img28.imageshack.us/img28/6950/btmodule2.th.jpg

Too bad the Navi/GPS idea was impossible. Anyone an idea how to upgrade BT on a WIN-CE device? BT is present, but only for an audio headset :(

Hubert

Sorry I lost momentum on this.

Here is the latest to try for win32

I've defaulted to the landscape dialogs over portrait.
I've added a simple tacho to the main dialog.
The colourise map now asks for the data file.

I've added code to automatically update the map from the captured data. At the moment this is done everytime the colourise is updated on screen so there is the danger of applying it multiple times if you resize the dialog. Only the memory image of the map is affected. You should either save the map to a new file or reload the map if no changes are wanted.


I've bundled the executable with the latest owners manual. Hopefully that will make it easier to keep in sync.
http://www.cajinnovations.com/OwnersManual163.zip

The tacho broke the mobile version as the functions I used aren't supported in WinCE, thanks Microsoft.

Found this posting only today, right after sending the V11 into hibernation (forced by a blown oil cooler hose). So no real life testing for some weeks from my side. Thank you anyway.
Those of you downloading the zip: rename the unzipped file to xy.zip and unzip it again. Then you'll have the .exe and the manual.
Hubert

Ditto - hibernation about to ensue in the northern hemisphere. However I do have a few bits and bobs to do to the machine for next year and will have a play with the new 163 interface. It looks promising on the Mac (via Parallels / Vista). Only concern is the size of the text and detail - must be getting decrepit or the resolution is too large.

I didn't get enough logging done this year but used it to sort out some dips in the mid range that were bugging me. Choice of voltage setting is critical! What I am discovering however is that the 1100 Sport is quite a thirsty brute and without the logging I would still be running on the weak side. A pal is now converted to using an AFR gizmo to sort out the carbs on his Norton 650 SS - oh what fun we have watching our spouses eyes glaze over as we discuss our findings!

Is there to be a WinCE follow up minus the tacho or .....?

Version 164

The Windows Mobile version is back, with the new tacho.
The colourise map function has been improved with the addition of a new button to save a modified map based on raw data. You colourise first, then save.
http://www.cajinnovations.com/OwnersManual164.zip

3 weeks vacation as of tomorrow. Temperature dropping but will fire up the Sporti and try the new stuff. Thx for that Cliff.

I hope to have my bike back on the road this weekend. I've got some catching up to do.

I'll let you know how things work out.

Thanks,
Pete

Grabbed it. Too bad I can't test the 'correct map' button right now...

Hubert

I tried out the 164 Mobile version today (WM6 Professional / CE OS 5.2.1620). The basic functions  work, of course. What's not working properly is the tach, it stays hidden behind the Echo lines :(

Another thing is: in case you turn off the engine prior to EcuControl the device freezes and requires a hard reset to come alive again. Maybe an internal time out for a lost bluetooth connection could help, don't know.

For the wishlist: I'd like to see a separate screen with tach and, similar to the Optimiser, an indication bar which shows where in the map the engine actually is running. For me that would make tuning different maps easier (still I somehow miss the Optimiser).

Hubert

Today I started it with the smartphone set to landscape and voilà, the screen looks as it should. You should not start the proggie and then change to landscape, at least not using a tool like TMan for that. The Win functions are obviously working somewhat differently.

Hubert

Here is the latest version of the ECUController, version 166.
Just as a test I'm making them available as a google doc share.

Here is win32 program - https://docs.google.com/open?id=0B1AiSuHdacfBTl80TUhPRHg5RXc
The Windows mobile version is here - https://docs.google.com/open?id=0B1AiSuHdacfBcEVfeWZCSkxybDA

Both are zip files of about 150K.

The main change since the last version is a simplification of the log files. No longer is there a raw and a formatted version. It's all in one now. There is no checkbox to say log or not.

When you go to colourise the map it will ask for a log file to load. Loading the one you are currently writing may cause issues so don't do that. A log file will be closed by terminating the program.

Now can i upgrade firmware with only serial port connected and selecting ECU upgrade?

This is a feature I am working towards but it is not there yet.

It's a chicken and egg issue though as it will require a firmware upgrade to have this.

On another front I'm about to look into an inexpensive USB programmer for the chip. Its about US$15.

I tried the new controller, to record a log.  It appeared to give me only one option, to log only raw logs. 

The new version also seemed to load the map as soon as I turned on the controller.  Because the "load from file" button was highlighted, I'm unsure where it was loading from, from a file, or the bike. 

The visual rpm meter is the new controller nice, but I like the visual "map" of version 151.

It says raw file but the result is a combined file.

If a map hasn't already been loaded, the ECUController will get it from the ECU when it is turned on.

Regarding the latest controller.  What does "Correct Map" on the "Adjust Map" page do?  Does it automatically change the map based on the O2 adjustments (the colorization)?

As Luhbo suggested, I request a display that shows what map you have loaded. 

That's the adjust map feature I mentioned in the other thread.
It will change the map that is loaded in the ECUController based on the closed loop feedback. This should then be save to another map and compared

The main window title should change to reflect the name of the map loaded or saved but not for the automatically uploaded map.

YaBB Administrator wrote on 05/07/12 at 07:27:54:

The main window title should change to reflect the name of the map loaded or saved but not for the automatically uploaded map.

Ok, I'll take a look at that.

I'm using ECUControl v1.66 WM5 actually.

First thing I noticed was that it does maybe connect automatically but does not show it, means update the tach resp. dashboard values. Only after you say 'Get Map' or so.

Second thing is that sometimes it echoes 'InvCmd1' and higher numbers, too. This comes when I try to upload and also download a map. I then repeat the action and the second time it seems to work. One ends with 'Lock ECU', the other one with 'Done'.

Is there anything wrong, can this affect the 'internals', or is it enough just to do it twice in this case?

THX
Hubert

InvCmd is from the ECU when it doesn't understand. What comes after InvCmd is an echo of the command received.
It could mean I need to increase delays. Can you try and capture that to the log file and send it to me.

I'll search the folders and send you one of the logs.

A separate button 'Connect to ECU' would be better, as actually the proggy gets really slow if/when the ECU doesn't answer (ignition off for instance). Maybe 'Connect/Disconnect' as a toggle switch.

What operations are you doing that are slow?

Any. In this case it's exclusively busy with BT. The screen then doesn't response any longer. For instance press 'get map from ecu' with the ecu off and 'game over'. Or 'global map adjust', it's all the same. It's only trying to BT connect.