I see a lot of possibilities for the new android version of the Optimiser, especially when incorporating some the the platform's capabilities of GPS and accelerometers and the possibility to make a complete dashboard out of one.

Another possibility, because the code base is new and separate from the ECU firmware, is to make the code for the android optimiser open, allowing any of you to contribute to the features.

Please let me know if you are interested in this. It doesn't have to be writing code, laying out dialogs and  creating graphics like tacho/speedo backgrounds would also be useful as they're not my strong point.

I'd be interested in getting involved in suggested layouts / graphics etc. I'd leave the code to the brainy buggers.

When the postie eventually brings my new Nexus gizmo I'll have a play and get back to you. Depending on feedback volume may be worth a separate forum section. I do like the idea of the gps data incorporated whilst logging. I know Raz has written some stuff already for LC1 and gps links but incorporating it all on one device and time / place stamping logs would be very elegant.

Any chance of emailing the Jeffries MyECU logo as per top right. Thought of making a label up for the bike with it. I was going to redraw it but don't know the font used. Think Lubho or someone else was thinking along the same lines a wee while back.

You should be able to right click the logo and save it.

It's only 11kB - its been optimised for website use.

For those looking to try the new Optimiser here it is - http://www.cajinnovations.com/MyECU/ECUController/Optimiser01.apk

No instructions yet but there shouldn't be too many surprises. Functionality is rather limited in this version but I'm hoping to provide updates every 2-3 weeks.
Disable screen rotation - that restarts the app and only use portrait mode at this stage.

It will automatically create a time stamped log file in the MyECU directory. You should put your maps in here also. Logging is quite verbose at the moment so files could get large and you will need to manually delete them.

It will connect to the new bluetooth dongle and display the analogs, a dial for throttle and RPM and a grid that
colourises in realtime.
It transfers files to and from the ECU and to and from the MyECU directory.
User interaction is primarily through the main menu.
It has been written for Android 2.2 and I have run it
on a Samsung Galaxy S, Google Nexus 7 and in Android x86 running under virtualbox ( no bluetooth )
For those with the older bluetooth dongle it may work. I haven't tested that yet but I will add support in a future version if required.

Finally got passed all the crap security nonsense (non google certified apps etc)and up and on screen.
L.G.T.M. :)
Need to check original BT module talks to it - probably Tuesday after shift finishes for the week.
edit: the BT dongle works fine - picked up by the Nexus 7 pdq. Far better than other devices I have used. Haven't checked all the functionality but tps moves.

Good to know.

With the first BT dongle, the ECU knows it's there (SW4) and does the initialisation of the dongle.

With the latest dongle the ECU doesn't know anything about it. When the android app connects, it does any required initialisation.

Other than that, no difference. So if it connects and you see a response there should be no further issues.

OK - fired the bike up today - issue with oil seal (yes - the difficult small inner "gerra furra bassa" one) in bevel box leaking precludes actual run however bit confused.
The graphy thingy shows a nice green trace on tps v rpm and changes colour too with richness and leanness which is cool. Looked to see how to change the map inj dur and spark advance and kept arriving at the adjust map tables. Am I being dense and missing something here? How do you change the map injdurs? Is this still to be coded?

No, you're jumping the gun. I haven't got that in yet.

The realtime snail trail assumes closed loop operation at the moment and may display false colours otherwise.

Ok. Relieved in a way :-). Am "getting" Adobe CS 6 and will start a mock up gui for the Nexus 7 meantime. Will forward when sorted out.

YaBB Administrator wrote on 08/02/12 at 08:42:31:

No, you're jumping the gun. I haven't got that in yet. The realtime snail trail assumes closed loop operation at the moment and may display false colours otherwise.

Any more developments Cliff? I have good weather and time off - unusual coincidence!

Will have a new version in a few days.
New features are
Axis display on the grid
Air pressure and temps moved from text status line to graphics.
Some noise removed from log.

Here is the next version - http://www.cajinnovations.com/MyECU/ECUController/Optimiser02.apk

It may be something I have done (or not done) but the closed loop is showing as inactive on the Nexus 7. I disconnected optimiser, connected BT dongle, and flipped the dip switch to on for closed loop. Heading back later to a pals to pick the bike up (bbq + beer last night :-)) and will check dip switch is correct - maybe arse about tit. Anything else I should look for?
Also any chance of scaling up the gui to fill the Nexus 7 screen - I am a tad visually challenged. Need to chat about how to customise the gui - failing badly to make the leap. Could you send me the code rather than the app to see if I can work out how to customise the fields on the screen?
Ta in advance.
g

You might be right about that. Closed loop is next for moving to graphics.

Its too early in the development to be doing code drops.

About scaling the GUI on the Nexus 7.  Is it not possible to zoom the display?  I'm thinking about getting one, so I'm asking the question.

At the moment there is nothing fancy like scaling but I will address that in the future.

This version has the closed loop moved to a graphic
http://www.cajinnovations.com/MyECU/ECUController/Optimiser03.apk
If you see any problems send me your map and log file

Seems to be an issue with real-time data not being displayed. It is talking as you can see it in the logs. I first noticed this as an intermittent problem on the previous version but now it seems to be full on.
That's actually good as debugging an intermittent bug is a pain.
Have you try the replay function? That displays OK. Strange because it uses the same calls to display.

I've update the file at the last location. UI updates seems ok now although I'm not sure why.

Your first post mooted an open source code base, if you did go down that route it means a number of us can contribute to the project. Also helps me match the look and feel of the iPad version (currently testing the bluetooth link).
We could probably share graphics and map files etc. :-?

It is too early to be considering releasing any source code bundles. That would just create an extra burden and slow things down at this stage.

Last we communicated you were still testing your kit.
Have you got it on the bike yet and got the map to a rideable state?

You should start with a dummy iOS program that does the bluetooth connection and logs the data to a file. This would need to be done before you need any MyECU specific code.
Its probably best to give you code snippets from the windows app as it is in c/c++ rather than give you the android code that is in java. Although the java code is cleaner.

Look and feel is open to your whims. At the moment the android app is not too different to the Windows app.

Ok Cool,

Yup testing the kit at present (all your documented bench tests look good at this point). Will hook it up the the wiring harness soon and check the sensor inputs, but as the bike is a ground up restore (frame strip/paint and engine warm up /rebuild ) it will still be a few months before I get to road test it.
That will however give me time to get an iPad Optimiser up and running ready for the task !
I'm also hacking together a signal for testing the ECU and iOptimiser off bike.

After a couple of hours last night I have an iOS app which receives the ECU's outputs over the BT link.

If you do feel like sharing(pm or email) your map file saver/loader code that's an area that I felt might consume a number of hours in order to keep it compatible with the existing ASCII map files....(like you say though no great rush - plenty to do!) :D

In that case you do have a bit of time on your hands. I'll send you a zip of the android code shortly. However this is just for pulling bits for the ipad version and in no way represents how the code/classes may be arranged in future.

Next iteration.

Big feature this iteration is map entry editing. It uses a touch on/ touch off for selection of the cells. Use with caution.
Single cell edit will allow real time transfer to ECU. Multi cell edits are % based and only affect memory. Changes must be manually saved/downloaded from main menu.

Its starting to get near parity with with the main ECUController so I can start to focus on the rough edges.

http://www.cajinnovations.com/MyECU/ECUController/Optimiser04.apk

The program now runs in landscape or portrait mode ( picked on start up ) and will not allow rotation even if enabled

http://www.cajinnovations.com/MyECU/ECUController/Optimiser05.apk

Hope to give this a good going over next week providing the weather holds - definitely autumn here now. Thanks for sorting the landscape / portrait issue!

Took the bike out for a run in the autumn sunshine this pm. Set up the Nexus to log the run of about 15 miles. Returned and set about replaying. Noted that there are many lines to be replayed and the oil temp and lc1 voltage varies quite substantially. I take it a) one needs to have the actual map in the N7 that was used in the log run and b) snail trail red is rich? Is there anyway of fast forward or rewind / pause to zoom in on specific areas of the data? Typical of me to start this at the end of the motorcycle season here in bonnie Scotland (well for me anyway).
Mmm... just remembered it might not have been in closed loop. Bugger.

A map needs to be loaded for some display elements.
At the moment there is no extra ability in replaying the data.
Red is rich and its needs to be closed loop.

I'm currently working on the autotune feature.

Discovered the downside of the nexus 7 magnetic switches! Popped the device into my tank map case which has magnets in the fabric to stick to the tank - yup...you guessed the outcome?

I wasn't aware of that feature before but a quick google shows it hasn't gone unnoticed.

Seems the sensor is at the lower left of the device so you might be able to rearrange things.

You might find the built in compass doesn't work though. :)

YaBB Administrator wrote on 10/11/12 at 06:54:18:

A map needs to be loaded for some display elements. At the moment there is no extra ability in replaying the data. Red is rich and its needs to be closed loop. I'm currently working on the autotune feature.

Nice to see the Optimiser advancing towards autotune. I am eagerly waiting for it.
I wonder which comes first - snow in Helsinki or autotune.
I installed optimiser05.apk and going to test it today.
Landscape mode is now useful.
I only have a tiny 320 x 480 pixel , 3.2 inch screen so no updates possible but nice to collect data and autotune - I hope.
Great job  :)

YaBB Administrator wrote on 10/11/12 at 17:58:29:

I wasn't aware of that feature before but a quick google shows it hasn't gone unnoticed. Seems the sensor is at the lower left of the device so you might be able to rearrange things. You might find the built in compass doesn't work though. :)

That might explain why I am driving around in figure of 8's! :P

The autotune code is mostly in ( how's that snow going? )
The screen shot shows hints displayed over the grid. This happens live or in replay and also on the grid for
choosing cells to edit.
I need to work on the readability, maybe  add some zoom/panning capability
I think 'll add an option on the ChooseCell dialog to incorporate hints into the map
http://www.cajinnovations.com/MyECU/ECUController/Optsuggest.jpg

YaBB Administrator wrote on 10/14/12 at 15:08:19:

The autotune code is mostly in ( how's that snow going? ) The screen shot shows hints displayed over the grid. This happens live or in replay and also on the grid for choosing cells to edit. I need to work on the readability, maybe  add some zoom/panning capability I think 'll add an option on the ChooseCell dialog to incorporate hints into the map http://www.cajinnovations.com/MyECU/ECUController/Optsuggest.jpg

It's funny that it seems that you got rare late snow in southern Australia but we are still waiting for the first snow.
Today it's a brilliant clear day and temp now +11C.
No download link available yet?
Only found a new jpg file which shows that it's not too warm there either but your temperature is moving to a nicer direction. Version 05 was not bad at all to use in landscape mode.

This version has the autotune code in. The way it works is that suggestions are accumulated while riding or replaying. You then go to adjust map and can select/accept the suggestions. The suggestions are displayed with a count of how many times a suggestion was made and the min/max value suggested to show the degree of confidence.

The map must then be saved manually. You can send to ECU but prudence suggests you should save the file and verify first.


http://www.cajinnovations.com/MyECU/ECUController/Optimiser06.apk

A bug report and a workaround:

I started to test and succeeded to load a map which was created in a PC and replay earlier runs and then save that map but when trying to load this saved map or an earlier saved map again Optimiser06 suddenly terminates.
The reason seems to be that a saved map file contains now decimal commas used at least in Finland, Germany, and Scandinavia instead of decimal points. When I change my language setting to English instead of Finnish are decimal points OK in saved files.

Autotune appeared before the first snow in Helsinki. :)


YaBB Administrator wrote on 10/19/12 at 19:20:43:

This version has the autotune code in. The way it works is that suggestions are accumulated while riding or replaying. You then go to adjust map and can select/accept the suggestions. The suggestions are displayed with a count of how many times a suggestion was made and the min/max value suggested to show the degree of confidence. The map must then be saved manually. You can send to ECU but prudence suggests you should save the file and verify first. http://www.cajinnovations.com/MyECU/ECUController/Optimiser06.apk

So the Optimser put commas into the file when the language was Finish. But crashed while trying to read it back.

Can you send the this map,

I deleted the faulty map but when you set  language to Finnish or any other earlier mentioned language you can repeat it.
When saving a map all decimal points are set to commas in the map targets, temperatures and spark advances.
Just save a map and reload it. Loading a saved map stops at targets which is understandable when the line is now full of commas.
The item separator character and the decimal separator are now the same.
Because you are not willing to change MyEcu software the simplest solution is to force decimal separator to be a point independent of the used language using US CultureInfo
http://www.java2s.com/Tutorial/CSharp/0440__I18N-Internationalization/CreateCultureInfoenUS.htm
example:
http://tech.avivo.si/2010/10/force-dot-as-decimal-separator-and-ignore-thousand-separator-when-formatting-decimal-numbers/

Thanks for those tips

This version sets the locale to US at startup. Let me know if it works.

http://www.cajinnovations.com/MyECU/ECUController/Optimiser06b.apk

If it does I'll make a version which just does that around the file loading/saving.

It does - save and reload OK when language set to Finnish.

First snow of autumn here today! How's Helsinki?

Yes, in the morning but only about 2cm and temperature is 1-2 degrees below zero. In the northern part of Finland there is up to 40cm and -25C.
In Helsinki snow melts away (I hope) and most usually we get permanent snow in December.

Another iteration and version bumped to 0.9
App has an icon now.
Added a select all button for choosing cells to edit
A fix to RPM display for those with crank driven inputs.

http://www.cajinnovations.com/MyECU/ECUController/Optimiser07.apk

I'm not getting much feedback on the app so please start to be a bit more picky about appearances etc.
Probably best to email me with pictures and logs otherwise this thread will get messy (ier).

Thanks Cliff for this. I'll be testing this soon.

I already have a few improvement (mainly usability) ideas. I'll be gathering them in one big e-mail...

marko

A quick one;

Phone is samsung galaxy s2
Start program in horizontal mode.
Connect to a device shows mac address, not the name given in the phone settings. Connect ok.
Load map from ecu ok
Edit map
Edit cells --> can't see the bottom row of the buttons, because of the screen orientation. Can't scroll down either to get them visible.

YaBB Administrator wrote on 11/27/12 at 17:26:08:

I'm not getting much feedback on the app so please start to be a bit more picky about appearances etc. Probably best to email me with pictures and logs otherwise this thread will get messy (ier).

Bit of hibernation mode here in Bonnie Scotland - snow capped mountains and frosty morning so less inclination to play /test! Will have a look at the schematics on latest issue and make suggestions. One issue I have is selecting the cells to alter on the grid is not too easy (find I select the adjacent ones more often that not) given I have fingers like cows tits. Any way of expanding this grid without loosing the overall grid? Suspect not. Will email any suggestions tho' as I have next week off.

I've changed the layout of the cell edit dialog and made it full screen.  It should work portrait or landscape. The selecting accuracy should be improved also. I've not bumped the version number

http://www.cajinnovations.com/MyECU/ECUController/Optimiser08.apk

Much better - ta.

YaBB Administrator wrote on 12/05/12 at 16:55:29:

I've changed the layout of the cell edit dialog and made it full screen.  It should work portrait or landscape. The selecting accuracy should be improved also. I've not bumped the version number http://www.cajinnovations.com/MyECU/ECUController/Optimiser08.apk

I installed this version and found a typo and a couple bugs

1) Adjust Map Tables->Edit Cell(s)->Selected all

2) When in CellEdit and moving Ini Duration slider response displays Injector Advance percentage not Injector Duration if you have selected several cells to be edited

3) In CellEdit there is a caption Inj Offs which should be Cyl Offset and Inj Duration and Inj Advance were better if not abreviated when several cells are selected. This just to be consistent when editing a single cell.

I suppose that O2 targets will be added later into Adjust Map Tables or somewhere else because they are necessary for optimation.

Cliff, you are advancing fine. I hope this software will boost your ecu sales because it makes map tuning so handy.

My small device is handy when driving but not so practical when editing data. I am looking for a capacitive stylus. Has anyone tried this one?
http://justgosmart.squarespace.com/stylus/
http://www.amazon.com/GoSmart-Stylus-Other-Screen-Devices/dp/B008CI4BG6


Driving season in Helsinki is now over, Temperature was yesterday -12C/14F and over 30cm/1 feet snow and icy roads.

Well spotted, thanks for that.
1) is done and will the next release.
2) is intentional. Single cell will work with absolute values and multi cell is relative. It makes more sense to say richen by 5% than to set to same value for multiple cells
3) The abbreviations you are seeing are actually the static text as opposed to dynamic text. Those last two sliders don't actually work in multi-cell. I'm not sure that Cyl Offset and O2 targets make sense in a multi cell adjustment and my thoughts are to remove them completely for multi-cell. Any thoughts on that?
I'll work on adding the O2 targets

YaBB Administrator wrote on 12/06/12 at 18:16:00:

Well spotted, thanks for that. 1) is done and will the next release. 2) is intentional. Single cell will work with absolute values and multi cell is relative. It makes more sense to say richen by 5% than to set to same value for multiple cells 3) The abbreviations you are seeing are actually the static text as opposed to dynamic text. Those last two sliders don't actually work in multi-cell. I'm not sure that Cyl Offset and O2 targets make sense in a multi cell adjustment and my thoughts are to remove them completely for multi-cell. Any thoughts on that? I'll work on adding the O2 targets

2) As anyone can notice I am not a native English speaker like many other MyEcu users are either. Advance of course is a correct word but a more common expression like change duration by % were more understandable to a person with a limited vocabulary. http://dictionary.reference.com/browse/advance

3) If you are fine tuning a working map you are right they are not very useful but if you are making more raw editing they are useful. See below.

I have now some experience of MyP8 and it's features encouraged me to explore more of injection. My Cali was maintained by a recommended engineer.
Now (after dismantle) I understand why I had to increase injection durations by 20% compared to Cali 1100 even if my 1990 Cali is 949cc.
I measured fuel pressure - 2.7bar and decided to buy new injectors because I suspected the old ones were clogged.
I chose IWP043(330cc) injectors and pico injector mounting brackets to hold them.
IW031(270cc/min) injectors had been replaced by IW040(206cc). I was told them to be 'a little smaller'.

With IWP043s I used Cliff's unmodified Cali map but AFR target 13.5. Cali started easily after farting air out of fuel line(+2C). It runs rich but now I can optimise first reducing some 10% of all injection durations but this after snow melts away. And maybe create an E85 map too.

Can you give me some more detail where you are seeing this locale issue because the original fix is still present.

I'm doing a Locale.setDefault at the start of the main activity. The notes say this can be overriden by changes to the system local.

YaBB Administrator wrote on 12/07/12 at 07:13:00:

Can you give me some more detail where you are seeing this locale issue because the original fix is still present. I'm doing a Locale.setDefault at the start of the main activity. The notes say this can be overriden by changes to the system local.

My error. I messed with an old ecu file. I tried to save file using an old file name and didn't notice an error message.
When loading the old file load failed. The old file first deleted I saved and reloaded successfully.
I deleted my wrong error report.
Sorry.

YaBB Administrator wrote on 12/05/12 at 16:55:29:

I've changed the layout of the cell edit dialog and made it full screen.  It should work portrait or landscape. The selecting accuracy should be improved also. I've not bumped the version number http://www.cajinnovations.com/MyECU/ECUController/Optimiser08.apk

An improvement request.
Optimiser starts recording immediately you start the program.
If you load a map for editing only this creates vain files.
Unsuccessful connects do that too.
It were more practical to have a button to press to actually start recording when needed.
I understand that you may need current function for program testing.

When you go and select "adjust map", edit cells, -> select a cell to edit --> make change to the values --> decide that you don't want to make changes -> press back button  -> go and view the same cell again, the changes are there. this is not right. the changes should be discarded and saved only when "commit changes" is pressed.

996SPS wrote on 12/07/12 at 19:32:05:

When you go and select "adjust map", edit cells, -> select a cell to edit --> make change to the values --> decide that you don't want to make changes -> press back button  -> go and view the same cell again, the changes are there. this is not right. the changes should be discarded and saved only when "commit changes" is pressed.

If you choose one cell this happens but when editing several cells it does not.

Is it possible in the future to separate the Optimiser function from the MyECU Controller function, possibly as two apps.  This may help reduce the number of unwanted files.

I tend to use the old Optimiser to see what is happening as I am riding and of course in Autotune. I use the MyECU Controller mainly for changing maps and logging a run using a small netbook.

It would be nice to have a full screen display of the TPS/RPM map when riding and logging to help see which cell you are in, or perhaps the display could show large numbers for the TPS and RPM breakpoints (cell numbers?) with up or down arrows similar to the small bars in the Otimiser.

Bobd wrote on 12/07/12 at 21:24:43:

Is it possible in the future to separate the Optimiser function from the MyECU Controller function, possibly as two apps.  This may help reduce the number of unwanted files. I tend to use the old Optimiser to see what is happening as I am riding and of course in Autotune. I use the MyECU Controller mainly for changing maps and logging a run using a small netbook. It would be nice to have a full screen display of the TPS/RPM map when riding and logging to help see which cell you are in, or perhaps the display could show large numbers for the TPS and RPM breakpoints (cell numbers?) with up or down arrows similar to the small bars in the Otimiser.

I think that logging data is a feature which has to work reliably before autotune is possible within Android Optimiser.
Difference between storing data to a file or to an array is minimal but testing is much easier using a file.
When the first step works implementing autotune is pretty straight forward.

Because an Android device has lots more RAM than a Hardware Optimiser more data can be collected during a run.

I do not prefer two separate programs but Cliff may do so.

Hi LOS, have you used the 'traditional' Optimiser much? I have found it useful to set the bike up the cruise or at least a steady state and see what air/fuel ratio is being seen by the lamda sensor at various points of the map.

I then adjust individuel cells and those close to it with the PC running MyECU Controller. 

I have tried Autotune but find it difficult to get the bike correctly in the cells. I have recently fitted a larger display so may find that easier now.

I like the BlueTooth approach, not so sure about the whole Android change yet.

Bobd wrote on 12/08/12 at 05:57:14:

Hi LOS, have you used the 'traditional' Optimiser much? I have found it useful to set the bike up the cruise or at least a steady state and see what air/fuel ratio is being seen by the lamda sensor at various points of the map. I then adjust individuel cells and those close to it with the PC running MyECU Controller.  I have tried Autotune but find it difficult to get the bike correctly in the cells. I have recently fitted a larger display so may find that easier now. I like the BlueTooth approach, not so sure about the whole Android change yet.

I've not used HW Optimiser at all. I read the manual and understood the problem to 'stay on the grid on the road'.
One thing to understand is that the O2 target setup is the most important line in the map because all corrections made by Optimiser are based on it. You have to decide there what you are aiming to.
For Max power:
Mike Rich: 'As far as fuel mapping goes--- Keep your air fuel ratio below 13.5 to 1 for best power ( 12.5- 13 is usually best.)' Whole story: http://cajinnovations.com/yabb/YaBB.pl?num=1353733713/2#2 
For good fuel economy AFR>14

Optimiser tries to do exactly what you describe.
As you know the map defines injection durations at break points which are used to calculate the actual injection duration based on actual rpm and throttle values.

Optimal duration values corrected by an oxygen sensor could be obtained by collecting data to a more dense grid than break points in the map. Then a piece of math and sufficient rules to decide whether to accept results automatically. This is just the opposite to what ecu does and possible because more memory is available than in HW Optimiser

I do not know if Cliff is going to this direction but it were really useful for all newbies.
When Android Optimiser makes it so easy to change a map you can have separate sport and economy maps to choose based on your mood.

I'm really trying to move away from the way the tuning method the Optimiser uses. It takes too much attention off the road.

It scares me to think of all the mileage I did negotiating winding roads without even watching the road. I don't know how I did it.

The best approach is to set up logging and then forget it's there. You can then tune after the ride.

I'm not a fan of the multiple map theory. The portions of the map used for cruising are quite localised and distinct from those used for more spirited riding. It should be possible to tune one area for economy and another for power.

YaBB Administrator wrote on 12/09/12 at 17:03:20:

I'm really trying to move away from the way the tuning method the Optimiser uses. It takes too much attention off the road. It scares me to think of all the mileage I did negotiating winding roads without even watching the road. I don't know how I did it. The best approach is to set up logging and then forget it's there. You can then tune after the ride. I'm not a fan of the multiple map theory. The portions of the map used for cruising are quite localised and distinct from those used for more spirited riding. It should be possible to tune one area for economy and another for power.

I agree - using Hardware Optimiser is a dangerous business except on a runway.

Processing collected data afterwards using a settable threshold with a good known default to filter out data of those suggestions which have not occurred often enough to be significant were a useful feature.

A single map is of course the preference.

Imagination needed to understand the two dimensional array to find out the cruising area is quite a hard test to a newbie - if he/she is not a hard core injection hobbyist already.
Revs are easy to understand but how open is the throttle at the same time?

Cali.ecu map does not help a lot as it uses a single target.
I found Sport.ecu as a good starting point as its targets O3-O6 are very sensible for me because I am not putting together a racer.
Volts/AFR are 2.40/14.6, 2.25/14.1, 2.00/13.4, 1.75/12.6

Cali and Sport maps have different rev break points but in spite of that I copied the flags part of the sport.ecu map to my cali map.

If anyone has improvement suggestions they are welcome.

This is an interesting developement in the MyECU ethos.

Perhaps I smell Product Liability or is it just as folk grow older they become more cautious.

I have to admit that I now find it difficult to support ideas I felt very strongly about in my youth, fighting the UK helmet law was one I rather regret now - how would I feel meeting a parent who's child is now braindamaged because they followed my direction. Of course this path has no end, should I take my child on the back when he is too young to really appreciate the risk or is taking a new girlfriend/boyfriend on the back acceptable - are they blinded by love for wonderfull you.

I fitted a larger screen to my Optimiser as it did distract me from the road whilst trying to read the tiny display.  Seems a shame to waste all that time and cost in buying and building the thing, still if there is a better way.............

So, my bike now runs as well as the original ecu, except a little harder to fire up, it feels more powerful although this may be just self justification. As the map (based on sport.ecu) is reasonably accurate and I have now fitted an LC-1 I guess its time to get out in the cold and build up some logged miles.

So what is the best method to do a logging run, just ride the bike as I do normally - mildly sportingly, or go for a long run thrashing it as much as I can - always fun or is there some special method. I tried to work around the cells setting various rpm and throttle positions but found this difficult - enter the larger display!

Finally which logging method? Use my netbook with a hard cable to the the topbox as I do at present using MyECU Controller v1.66 or follow the as yet 'in developement' Android path.

Having got the log what is the best way to interpret it,  read through the file in Notepad and review the captured O2 voltages, get it into some graphical form - I have'nt managed that yet or use the Android program. I have made the Android connect via BT but only logged a start.

A few scattered thoughts from earlier experience with Sport Corsa 1100i from 2004-5 and MyECU. The current vehicles are to be fired up and tested properly next summer.

The "normal" street riding uses an elliptical area in the map reaching out from the left bottom corner to somewhere in the middle of the map. High rev and open throttle hard riding is in the right top corner of the map with hard engine braking returning via bottom part of the map and again accelerating with wide open throttle up from the left side and then shifting to the right through increasing revs.

I used to tune the left bottom part of the map (idle and slow rpm low throttle area) slightly rich to make a smooth/soft throttle response for take offs and slow riding. In terms of AFR between 12-13.

The "middle" elliptical area of normal street riding can be tuned pretty close to optimal for fuel consumption namely AFR 13-14. As lean as possible without jerky ride.

The right hand top corner I made on the rich side around AFR 12 to ensure engine safety in hard riding to prevent engine damage.

If in closed loop mode, it seemed to be preferable to keep the map slighly rich so that the lambda correction can then lean it to be on the target. This is because lambda probe is a bit slow and can react no faster than in 0.1-0.2 seconds. Therefore, with the map being on rich side you get an acceleration pump effect in quick throttle openings and accelerations. As soon as the situation evens out, the lambda correction leans the situation to target values.

A record of measured lambda values in different parts of the map seems to be the most promising method to decide on map corrections. Some averaging is necessary and some method to reject the most extreme values as they might not reflect the steady state in those cells.

br. Juha

I have tested Optimiser using HTC Wildfire S, 3.2", 320x480, 180dpi screen.
The screen is tiny, but the Edit grid could be about 0.25" higher and wider.
That were 3 more pixels per a row and a column both in the portrait and the landscape mode.

I asked if anyone has tried a GoSmart 200 stylus.
http://www.amazon.co.uk/GoSmart-Stylus-Other-Screen-Devices/dp/B008I9CFKS/ref=sr_1_fkmr1_2?ie=UTF8&qid=1355437718&sr=8-2-fkmr1
When nobody replied I purchased one.
It is possible to pick up those tiny circles one by one using this mine sweeper looking stylus tip when you can see through it.
It though requires some exercise.

I like my phone because it fits easily into my shirt pocket.
Will there be any recommendation/requirement of the screen size of a supported device?

Screen sizes of smart phones:
http://smartphones.findthebest.com/saved_search/Smartphones-by-Screen-Size

Send me a screen shot of the grid and I'll see if I can optimise the layout.

This update focus is on logging. There is a new menu item where classes of logging activity can be enabled/disabled and delete old log files.

http://www.cajinnovations.com/MyECU/ECUController/Optimiser09.apk

This update focus is primarily aimed at the look on some smaller devices. Hopefully I didn't break the larger ones.
The suggestions dialog has been re-implemented as it was too slow in its transitions.
http://www.cajinnovations.com/MyECU/ECUController/Optimiser10.apk

I finally convinced my wife that I desperately needed a tablet computer, and I bought a Samsung Galaxy Tab 2 7.0 with Android 4.1.1 on it.  I mounted a Sparkfun BlueSMiRF (pn#10269) on a PCB with a Cat5 socket so I can either plug in my Optimiser or the BlueTooth dongle. (I have a Cat5 cable running from the ECU to my handlebars).  The Tab 2 says it is paired with the BT dongle but the status light keeps flashing red and the connect light never comes on.  I have a Palm Pilot with BT, so I just powered up the dongle from a 5V supply, and the Palm Pilot was able to connect right away after doing the BT setup.  I am at a loss as to why the Tab 2 "pairs" but does not connect.  I am using your Optimiser10.apk in the Tab 2.  It downloaded and installed with no errors, and I get the initial screen when I start the APP.
     I did some checking, and found that the Tab 2 has Bluetooth 3.0.  Could that be the problem?  I would have thought that it would be downward compatible.

Pairing and connecting are not the same thing.
You can pair with the standard BT management but this wont connect.
The connect has to be done from the Optimiser.

One gotcha is that you need to do the connect within 1 minute of powering up the BT dongle. This is because in default mode the BT has a configuration timer and when it expires the Optimiser is unable to set the required comms parameters. It will still look like a connect is successful but it will no talk to the ECU

OK, I'm confused.  I tried the following:
1) Unpair the BT on the Tab, turn OFF BT on the Tab, IGN ON, start MyECU App-> no connect
2) Unpair the BT on the Tab, turn ON BT on the Tab, IGN ON, start MyECU App-> no connect
3) Turn ON and Pair the BT on the Tab, IGN ON, start MyECU App-> no connect
4) Pair the BT on the Tab, turn OFF BT on the Tab, start MyECU App-> no connect

In case #s 1 and 4, when I started the MyECU App, it requested permission to turn on BT, and I poked the OK button, and it flashed a quick message, but that's all.  I think the message was about setting up a log file.  Where am I going wrong?

New info:  I downloaded the Bluetooth SPP App from the google store, and it connected to the BT just fine, so I took the BT and Tab out to the bike, turned IGN ON, and the App connected, and downloaded unreadable characters (understandable).  The point is, the SPP App connected.  Just to verify I am using the correct App, I downloaded v0.93 of Optimiser from your website, and the installed size is 228K.  Does that seem right?

Yep you're confused.

Just starting the Optimiser is not sufficient. You then need to go to the menu and choose connect.
First enable BT and pair.

What version of ECUController have you been using to talk to the ECU

Mostly, I have been using the Optimiser. which I have mounted on my handlebars.  The ECUcontroller version I have been using is 1.66. 
     I found the menu, and I was able to connect and load the map from the ECU (I think).   :)
Tomorrow I will try to find the map on the Tab 2. 
What is the default folder, or does it vary from tablet to tablet?  I need to recharge the battery on the Tab, so I am done for today.  :(

There is a MyECU directory where everything goes - maps and logs

I think I know the source of my earlier confusion.  The SPP app I was using for testing, popped up a connect dialog initially on startup, so I was expecting that to happen with the Optimiser APP.  Once I knew that it was a menu selection, everything worked fine.
     I found the log files and ECU map and uploaded them to Google Drive so I could look at them.  They all seem to be OK.  I took pictures of the front and back of the dongle, and its temporary location on the bike.  I will seal it in clear heat shrink and make an adapter so I can snap it into the Optimiser's holder on the handlebars.  I have posted pictures at:https://picasaweb.google.com/106090307548421468637/Bluetooth?authuser=0&authkey=Gv1sRgCJXV173m6LbXlQE&feat=directlink

     Now for a minor quibble:  As you can see from the two pictures of the Tab 2 screen, the battery voltage appears to be 2.61V (the first 1 is on the battery symbol border, and my old eyes didn't recognize it at first).  Also, there are some unidentified voltages and percentages to the right of the battery symbol, and they are almost on top of each other.  I know you have to make the APP work for both phones and tablets, so it's not a big deal, I just need to know what they are.
     Finally, thanks for all your hard work and help with this!  :)

I'll fix the voltage display on the next version.
Those numbers to the right are for the o2 correction/gas sensor voltage. Do you have two?

You air pressure seems low at 900 are you much above sea level

Yes, I have two O2 sensors installed, and I am at 1036m, so the barometric is probably about right.  Thanks for the info on the two readings.  Now I have to get out and log some data.   :)

When I try to open a .ecu file in the MyECU directory on my Tab 2, it tells me I don't have the right app to open the file.  Which app should I have?

What are you trying to do with it?

Generally you open the map from the app from the menu not the other way around.

I was thinking in terms of editing the map from the Tab 2 instead of uploading it to my computer.  I know that there are text editor apps available, so I assumed that I just needed the right one.

I use an app called Ghost Commander, it quite good as a file navigator and allows viewing / editting.

But you're getting ahead of yourself. Aren't you still trying to get it to connect?

No, I got it to connect and loaded the map from the ECU, then saved it to the MyECU directory (see #77).  What I still need to do is to get out and log some data.  Thanks again for your quick response!  :)

Hi guys

Here is the optimiser in action.

http://www.youtube.com/watch?v=LeoCTy86hrY

Hi Cliff. Snow and frost just given up on Denmark, or almost, so my 907 just been out the last two days. The app is great, thanks and downloaded and work just fine on my Sony Xperia S.
BT connection takes getting used to, but got it going every time on the last rides to work just to get to know it.

Not begun using it to tune or change my current map - need to get my Winter-tired brain back in bike tuning mode. The map I use, and rode to WDW 2012 at Misano, does quite reasonable anyway, but fine tuning could make it just perfect. About AFR I have mine with a minus in front where some mentioned in this thread did not show the negative - in front of the value. I have added a LC-1 to the rear header.

A great season of riding to you all.
Per (Rasser54)

Is it possible to get the "browse.." functionality to the "load map file" button? I.e. I have several different ecu files in different folders and want to open them without moving them first to the myecu -folder. Naturally the same thing could be applied to the "save map file" button.

Cheers

Marko

I think that's a good idea, Marko.  Both load and save could use that feature.  Is that a big change, Cliff?

I assume the use case for this is you copied the file using BT and it's in the BT folder. I can't see an issue with when the device is connected to the PC with USB as you can get directly to the MyECU directory easily.

Android for some bizarre reason doesn't have the expected file chooser dialog that most other OSs have. So it needs to be coded manually. There are even some add-ons to do this but that's not pretty either.

I think it is tidier to have everything in the one spot rather then anywhere. You would be better served by adding a decent file manager to your device. I use Ghost Commander. It will even remember the last folders you were in so copying maps around is easy.

Actually I use google drive. And I can't figure out  how to dl the file from there.
The phone tries to open it which of course does not succeed.

Hi All !
First of all, thanks to 996SPS for his help. I endly got the BT working with his advice.
I think I am in the right direction to finalize a good map for my 916. I have to buy a LC1 to improve the accuracy of my analysis.

I just want to share today's issue with you.
I try to load an updated map last week with the android optimiser. It seems to work well, and I check the job by download it after and then check the files.
As usual, some changes in the numbers ...
but lots of them in fact !
SparkAdv moves a little as usual, but also InjAdv and InjDur. And for InjDur, the changes were so high that it completly kills the improvement put in the file !
I try to upload and download several times, same results.
A very annoying point is the TPS value change : I request a TPS=1 and gets each time in the download file TPS=150 !!!

I just think about Cliff advices in the past and then use the ECU Controller 1.66 with the cable ...
and ...
it works, with very slight changes in the SpkAdv table.
I got the files if necessary if it can help to fix some problems.
Regards !

The changes are due to rounding but the Android Optimiser shouldn't be producing significantly more.

Can you send me the before and after maps and the log file that produced it.

Just to let you know that my latest test with a better interpolated map allows me to "rediscover" my bike.
Great acceleration and driveability, even if some minor adjustment will be requets at idle.
As i got a LC1 on the bike now, lots of data to analyze and optimize. i will test soon the closed loop mode.
SO : Thanks a lot to Cliff for all that developpment job !
:D

I still got the map loading issue explained further with the BT module, but it works fine with the ECU Controller.

Regards !

Is it me or is the latest version of myECU android optimiser on the website (0.94) in the wrong format 8-)?

You're right.  The link is pointing to the AndroidOptimiser manual in .odt format, not the App itself.  Odt is the Open Document Format version.  LibreOffice can read that format.  It's free, and it reads MSOffice formats, too.

Aye, that's what I thought. CAJ must have a lot on his mind.

Oops, sorry about that. Will fix right now.

Should be fixed now.

Yup. Needed to clear the browser cache though. It did have a penchant for the .odt file!!
BTW. Just getting back to the 1100 sportie and I note the throttle dial has a numerical tps value and er.. another which looks to be a follower of the needle. Can't find mention in the instructions to these. Is the number of value? How do you see it being useful? Just curious.
Also when the log gives +8.6 or whatever on the grid and I chose apply, how do I know it does and more importantly how do I know it doesn't if I repeat the task. Maybe have to compare the two maps. Its been a while since I had a good play with this. Suffering from withdrawal symptoms.

Re browser, you need to reload the frame. For some silly reason the normal refresh doesn't reloaded frames in a page.

The throttle value would be the index of the map with fractional parts, ie idle 0.0

Did you have a read of the manual ( the odt file or one of the other options. ) That might make that clearer.

Re: throttle and index fraction:-
Ah! I failed to make the final link - just lazy.

RTFM? Now that's a good idea. Perhaps I should  ::)

edit:
OK - re-read and understood - need to action AND send/save to ecu or file. Will have a play this am.

I am having trouble with v0.95. The app fails when I try to edit >a< map cell.

I load the map from ecu ( it does it automatically I see ) and the device automatically pairs which is right grand. Then in adjust map tables sub menu I select edit cell(s), hit a cell, get the yellow circle and edit selected get "Unfortunately, MyECU Optimiser v0.95 has stopped" message. Bike ignition is on and not turning during this process.

The map loaded is the last one from file, not the ECU

Can you repro the problem and send me log and map.

Cliff,

not sure it will head you in a possible direction for a fix, but I had this exact same issue before I replaced the last failed cap, if you remember the one, it was C5: it was making cold starts impossible since it did not spark at crank speeds.  Since I fixed it by replacing the cap, I stopped having the issue.  Just an idea, but it could be the board itself, with a failed component somewhere.  Then again, a symptom similar may have different causes, but this failed C5 created this problem with the optimiser for me.  I also got the issue if I had 'tabs' instead of spaces in the map, or an extra empty line between the big map blocks, i.e. 2 lines empty rather than 1.  Loading the base map to test helped me identify the issue was with the map (when it was not the failed c5).

Stef

Stef - thanks for that but there has been a lot of to-ing and fro-ing of emails and CJ has sorted the issue for me (not sure if its just me but it appears so) and I have my very own ver 0.95! It was a problem with the edit of cells - it crashed the app when I went to edit a cell. This a.m. I installed the new version and bingo - it worked offline! Just tried it on the m/c a couple of minutes ago and it works. Happy bunny. Many thanks to Cliff - I can spot a man who likes a challenge a mile off - or even on the other side of the globe  :)

Isn't the man God's gift to 16M owners!  Happy it works for you.  Got to admit, this post had the very positive side of informing me of the auto map loading (previous map by default) and autoconnect features. 

Maybe one suggestion, if this optimiser can be even better than it is now, and maybe only my personnal need/desire: I'd like to do 'zone selection' so I can select a cell and it would select, let's say, 4 cells right, left, up and down.  I could more easily work on zones and then use excel with graphs to smooth out the resulting map.  Makes for a quicker 'on the raod' gut feel tuning.  My 2 cents

stef

Stef G Canada wrote on 07/16/13 at 18:19:42:

...  I could more easily work on zones and then use excel with graphs to smooth out the resulting map...

Have you tried TunerPro(.net)? You'd still need Excel for the data transfer between our text based maps and the binary format that T/P prefers, but then it's a very relaxd tool for comparing maps, editing maps, comparing them and so on.

Hubert

I know of it but didn't actually try it yet.  So thanks for the tip, I forgot about its existence. 

Still, what I was meaning is that I like to tune 'on the fly' while riding: say I load a map, ride the bike, and notice an area where tj=he bike is a bit flat, power delivery wise, I would stop in gas station for example, select the 'zone' I recognize is a bit flat, and adjust InjDur or SpkAdv by + or - 5%, then ride to see what it did, and do it until I fine tune to about +/-1%, zone by zone, and finally smooth it out in textedit or excel.  Does that make sense?  I guess being a native French speaking makes my English a bit hard to understand, sorry about this.  Stef

Something less sophisticated is DiffMerge - but great for comparing text files and highlighting changes.

Mad Farquhar wrote on 07/17/13 at 00:01:30:

Something less sophisticated is DiffMerge - but great for comparing text files and highlighting changes.

Thanks for the info about Diffmerge.  It's available for Mac and Linux, so I think I will install it on my Linux computer.

Stef G Canada wrote on 07/16/13 at 21:08:11:

.. and finally smooth it out in textedit or excel.  Does that make sense?  ...

I think I understood your plan. It's the final smoothing that might be easier with TunerPro.

Hubert

COnewbie wrote on 07/17/13 at 05:17:07:

Thanks for the info about Diffmerge.  It's available for Mac and Linux, so I think I will install it on my Linux computer.

It was Raz (or someone else on here) that put me on to it - or something similar.

Thanks Hubert about tip for the smoothing made easier in tunepro.  I'll try DiffMerge since I am Mac at home, or else use the old mac and install windows on it for tunepro.

stef

New version of the Android Optimiser available - http://www.myecu.biz/MyECU/AndroidOptimiser/index.html

New version of the Android Optimiser available - http://www.myecu.biz/MyECU/AndroidOptimiser/index.html

This version has major improvements to the way cell selection works. It is now easier to select the top half of the map for example  ( a function that had me running back to the windows version ).

Thanks for the update.

Weather crappy here in the UK (not sure how much longer it will be United), endless rain so not much happening on the bike front.  We are still here though.

Thank you for the update,  and for keeping the earlier versions up too.  You never know when you've got to take a step back.....

I was finally able to take the bike out for a ride last Friday, and I got a couple of logs using Android Optimiser v0.98 on my Samsung Tab 2.0 running Android v4.2.2.  I believe that I was successful selecting the suggested changes and saving them back to the ECU.  I know from reading the postings that Red is rich and Blue is lean, and I assume that Green is spot on, but when I replay the log file, I get some Yellows and Oranges in addition to the other colors.  How do they relate to rich vs. lean?

It's meant to be a spectrum type display.
Red means the map is rich and needs to be leaned off, blue is the opposite.

Do you see the suggestions?

I saw the suggestions at the end of my logging run after going to Adjust Map >Edit Cells.  I selected them, accepted them, and saved the map to MyECU.  I didn't replay the logging file to its conclusion yesterday, because I was just trying to become more familiar with what the different controls do.  I'm going to replay the map to its conclusion now.  Would those same suggestions reappear at the end of the replay of the log file?

Yes those same suggestions will appear but you will need to load the previous map or you may apply them twice.

When applying suggestion keep in mind the number of times a suggestion is made to gauge the integrity.

Does that mean if I edit the log file I can find the suggestions, or is that a dynamic calculation that only appears in the Android ram while the app is running?

Also, I noticed that the battery voltage gets as high as 14.3 volts.  I have a LiFe battery.  Is that a problem?

There should be indicators in the log but you wont get the big picture with statistical averaging. You can search the file for "Tune"

14.4V is the max for LiFe. Check with the head light on and off as sometimes this is different unless you've modded your bike with relays for the headlight.

Thanks again for the prompt reply.  I was just curious about the map suggestions, and I will trust the Optimiser in any case.

The headlight is still wired in its stock form, although I was considering adding a headlight relay to improve the brightness of the lighting. 

Hi all

I've just noticed a bug that may affect those with a MKVII MyECU.
The bug is that the saved map may have all the RPM values half what they should be ( The MkVII chip runs at twice the speed ).

I've not yet determined the sequence to produce this as I only noticed this today. I thought I had filled up with dud fuel.
Please keep an eye out for this till I fix it.

I may have run into the same issue, but I am not sure.  I took a ride to Springfield, 140 mi. away, over Santiam Pass (~4900 ft).  When I got there, I attempted to save the suggested changes to the map, and the app crashed.  I also noticed that I wasn't able to get the bike to run much over 4000rpm, but I was assuming it was because of the altitude, and that I was in 5th gear all the time.  The problem seemed to go away while I was in Springfield, (~160ft), and it seemed OK until I got up in altitude again.  Since the Tab2 was in a pouch around my neck, I don't have any more info at this time.  I will take a look at the last map logged tomorrow to see if there is anything worth looking at.

I wasn't able to determine from my logs how the issue occurred. It  seemed to just spring up about a week ago and I can't recall what I was doing then.

I have been swapping bikes so think it may be some side effect of that.

It will be obvious in the map, just look at the RPM lines.

This

MyECU Cfg RPM=8012, TPS=65
RPM         500  1100  1500  1800  2000  2304  2600  2900  3360  3656  4044  4648  5340  6156  7064  8116

became

MyECU Cfg RPM=4006, TPS=65
RPM         250   550   750   901  1000  1151  1299  1450  1680  1827  2023  2323  2671  3079  3531  4058

It won't just come good. You need to go back to a map which isn't trashed.

I loaded the map from the ECU, and it did not seem to have the problem you described.  Unfortunately, I had failed to check the setting to keep old logs, so I have lost the log file that had the information that crashed the Optimiser app.  I have now checked that box, so if it happens again, I will at least have the log file.  I think this question has been asked before, but is there a way to save the log files to the SD card by default?  I have a 32GB SD card installed, but it is only an 8GB Tab 2.0.  Sorry I couldn't be more help.

Not at this time. All files are in the one location.
I use Ghost Commander as an old style file manager. It can even work with windows shares. Then I offload file occassionly.

COnewbie wrote on 07/25/14 at 06:42:09:

I loaded the map from the ECU, and it did not seem to have the problem you described.  Unfortunately, I had failed to check the setting to keep old logs, so I have lost the log file that had the information that crashed the Optimiser app.  I have now checked that box, so if it happens again, I will at least have the log file.  I think this question has been asked before, but is there a way to save the log files to the SD card by default?  I have a 32GB SD card installed, but it is only an 8GB Tab 2.0.  Sorry I couldn't be more help.

I Have all files on the SD card.
You can move MyEcu optimiser to the SD card.
Go to Settings -> Applications -> Manage applications then open MyEcu optimiser and push the "Move to sd card" button.
When MyEcu folder is on the SD card all files will go there.

I tried your suggestion, LOS, but the "move to SD" button was greyed out, and inoperable.  Does that mean I have to "root" my tablet?  I've been avoiding doing that, but I will if it is necessary.

Update: I have further information that according to numerous forums, the ability to "move to SD" has to be enabled in the APP.  There was mention of a feature called A2SD.  Did you compile MyECU from source?

Cliff: can you easily add this feature to MyECU?

COnewbie wrote on 07/26/14 at 02:08:51:

I tried your suggestion, LOS, but the "move to SD" button was greyed out, and inoperable.  Does that mean I have to "root" my tablet?  I've been avoiding doing that, but I will if it is necessary. Update: I have further information that according to numerous forums, the ability to "move to SD" has to be enabled in the APP.  There was mention of a feature called A2SD.  Did you compile MyECU from source? Cliff: can you easily add this feature to MyECU?

I Have not rooted my device.
But when I looked at MyEcu optimiser's management screen I noticed that "Move to phone" button  is missing which means that I have not used "move to SD card" either.
I now remember that I
- downloaded Optimiser098.apk to my pc
- copied it to the SD card folder using a usb cable to connect my phone as a disk.
- removed the phone from the usb cable
- Used AndroXplorer(you may use some other file manager) to browse to the SD Card
- double clicked the apk file to install it
Now Optimiser creates MyEcu folder on the SD card where all data resides

I have a tiny HTC Wildfire with Android 2.3.5

Cliff:
I checked into Ghost Commander, and even though it is free, the first thing I had to do was give a credit card number to Google.  Google already knows too much about me, so I decided to just use the MyFiles app that was on my Tab 2 by default, even though it is somewhat awkward to use.  Thanks for the info, though.

COnewbie wrote on 07/26/14 at 09:02:17:

Cliff: I checked into Ghost Commander, and even though it is free, the first thing I had to do was give a credit card number to Google.  Google already knows too much about me, so I decided to just use the MyFiles app that was on my Tab 2 by default, even though it is somewhat awkward to use.  Thanks for the info, though.

I updated my reply to how to move Optimiser to SD Card
And I probably created MyEcu folder and put the apk file in it before installing.

Thanks for the update, LOS, I will try that tomorrow, and let you know how it went.

Hi again, I tried the suggestion from LOS, and here is what I have found: I moved the .apk file to the SD card, uninstalled the MyECU app, deleted the MyECU folder, and then installed MyECU from the SD card.  I ended up with a MyECU folder in both the SD card and the internal folder, and the app still logs to the internal folder, so I think the best option is if allowing the "move to SD card" is not too difficult for Cliff to implement. 

As to the app crashing in Springfield, it was evidently my fault.  I had turned off the engine to take a break, and when I turned the ignition on again, I immediately started the bluetooth and then tried to do the update.  Evidently, the Map was not loaded, and that caused the app to crash.  Since I had set the logging options to NOT retain old logs, the information was then lost when I restarted the app.  Lesson learned...

This is not an official release but has
android:installLocation="auto" which should allow moving the SD

You shouldn't really be storing more than a few 10s of MB on your device and in the scheme of things this is a negligible part of your 8G.
If space is really tight, it may be better to move other apps to the SD card.

---

Thanks, Cliff, I will try it tomorrow.  Also, I found another way to do it using ADB, which is available in my Linux machine.  I will let you know about both of them.f

COnewbie wrote on 07/27/14 at 08:29:51:

Hi again, I tried the suggestion from LOS, and here is what I have found: I moved the .apk file to the SD card, uninstalled the MyECU app, deleted the MyECU folder, and then installed MyECU from the SD card.  I ended up with a MyECU folder in both the SD card and the internal folder, and the app still logs to the internal folder, so I think the best option is if allowing the "move to SD card" is not too difficult for Cliff to implement.  As to the app crashing in Springfield, it was evidently my fault.  I had turned off the engine to take a break, and when I turned the ignition on again, I immediately started the bluetooth and then tried to do the update.  Evidently, the Map was not loaded, and that caused the app to crash.  Since I had set the logging options to NOT retain old logs, the information was then lost when I restarted the app.  Lesson learned...

It may have worked if you had deleted the MyEcu folder from the internal folder.
The later Android versions may also be more tight with security.
But fortunately it has worked for me because I  really have lack of space.

Cliff: thanks for the new version.  I have moved the app to my SD card.  However, the original problem remains: the MyECU folder where the log files reside is still in the device folder, not the SD card.  I understand what you are saying, but an 8GB Samsung tablet has a lot of BLOATWARE installed on it by default, which is why I installed the SD card originally.  I will take your advice and make sure I clean out old log files on a regular basis, and try to move some of the BLOATWARE to the SD card.  One of the old log files I have is 6.6MB, however, and looking at the elevation and RPM readings, I would guess it is from a trip to Bend, OR, 35mi away. 

1) Based on that, I would guess that the file I lost from the trip to Springfield, 140mi away, would be much, much larger.  Maybe it crashed the app because it was too big?

2) Since the Mk VII runs twice as fast, does it also log twice as much data?

LOS: I am running Android 4.2.2, and it was tricky to get around the security, but I was finally able to use Android Developer Bridge to set the default install location to SD card, but as I said, the MyECU folder still ended up in the device folder.  As a result, I reset the default location back to Auto, so as not to cause problems with updates or new installations.  Thanks for your efforts to help, anyway.

Just looked at the code and this is what I use to get the path


           mPublicPath = Environment.getExternalStoragePublicDirectory("MyECU");
           mPublicPath.mkdirs();


According to the docs this is all that is required. It could be something specific to the device

Yeah, it looks right, but I found the following info:
http://stackoverflow.com/questions/17215466/environment-getexternalstoragedirectory-getabsolutepath-gives-a-different-pa

and this:

http://stackoverflow.com/questions/5453708/android-how-to-use-environment-getexternalstoragedirectory

So, I think there must be a problem with the symlink in my Tab 2.  I will try to get a look at that.

It looks like I can't set extSDcard as my default location without rooting my tablet; the option is greyed out.  I'll have to think about that for awhile. 

BTW, Cliff, I certainly don't want to have a special version.  Maintaining special versions is a nightmare.

I did some research using ADB, and found that the app is located in /mnt/asec/.  Is that where it should be if it were installed on the SD card?

Where would it be if it were installed internally?

Also, sdcard0 is a link to /storage/emulated/legacy/ .  Is that what you expected, Cliff?

Do you think I can just create a link from ./MyECU/ on /storage/emulated/legacy/ to /storage/extSdCard/MyECU/ ?  I am asking because I have no experience with Android before now.  If it is workable, I will post what I did to make it happen.

COnewbie wrote on 07/30/14 at 03:18:47:

Do you think I can just create a link from ./MyECU/ on /storage/emulated/legacy/ to /storage/extSdCard/MyECU/ ?  I am asking because I have no experience with Android before now.  If it is workable, I will post what I did to make it happen.

Just for grins I tried to create that link, but apparently Android doesn't like links across devices, although I read somewhere that you can do this as root.  I tried to accomplish that from the ADB shell, with no success, so it looks like the only option is to root the tablet.  I'm still thinking about that.

I have been reading in
https://developer.android.com/guide/topics/data/data-storage.html#filesInternal
and it looks like I need Android 4.4.2 on my tablet, so the question is:

Do I wait for Samsung to get around to the update, or root my tablet and install it myself? 

Still weighing risks vs benefits.

I've updated the Android Optimiser manual - http://www.myecu.biz/MyECU/AndroidOptimiser/AndroidOptimiser.pdf

COnewbie wrote on 07/31/14 at 12:18:14:

COnewbie wrote on 07/30/14 at 03:18:47: Do you think I can just create a link from ./MyECU/ on /storage/emulated/legacy/ to /storage/extSdCard/MyECU/ ?  I am asking because I have no experience with Android before now.  If it is workable, I will post what I did to make it happen. Just for grins I tried to create that link, but apparently Android doesn't like links across devices, although I read somewhere that you can do this as root.  I tried to accomplish that from the ADB shell, with no success, so it looks like the only option is to root the tablet.  I'm still thinking about that.

Are you talking about UNIX links, that you do with "ln"? In that case "ln -s /storage/extSdCard/MyECU /storage/emulated/legacy" should work fine. But maybe I misunderstand the problem completely  :o

YaBB Administrator wrote on 08/29/14 at 07:31:39:

I've updated the Android Optimiser manual - http://www.myecu.biz/MyECU/AndroidOptimiser/AndroidOptimiser.pdf

Thank you.  It's always good to have a reference.

Hi Raz,
     Yes, I tried the Unix link, but it didn't work.  It turns out that Android is based on Linux, and has a lot of the Linux functions, but linking across hardware devices doesn't seem to work, at least in the case of the Samsung Tab.  I will try your suggestion just in case I got the syntax wrong.

Cliff, thanks for the manual update.

Just to be sure, I tried the link command again.  Here is the link command and the result:

ln -s /storage/extSdCard/MyECU /storage/emulated/legacy/MyECU                                <
link failed Cross-device link

COnewbie wrote on 09/05/14 at 04:32:18:

Just to be sure, I tried the link command again.  Here is the link command and the result: ln -s /storage/extSdCard/MyECU /storage/emulated/legacy/MyECU                                < link failed Cross-device link

I bet that error message is incorrect (it's a normal message from trying to create hard links). The real problem is likely that /storage/emulated/legacy is on a file system that doesn't support symlinks at all. This knowledge doesn't help you much... unless you can change it?

I think my only solution is to replace the Samsung OS with CyanogenMod version to get that ability, Raz.  I am going to try that soon.  Wish me luck.  :)

I've released an update to the Android Optimiser - http://www.myecu.biz/MyECU/AndroidOptimiser/index.html

The last change is the main functional change and will make it easier to do things like fix starts as you can more easily modify the prime table and test.
Best strategy here is to start lean and increase as the opposite can produce confusion as excess fuel is cleared.

YaBB Administrator wrote on 11/15/14 at 14:00:02:

I've released an update to the Android Optimiser - http://www.myecu.biz/MyECU/AndroidOptimiser/index.html

Congratulations now we have version 1.01 (production) available!

I deleted the old version and installed the new one and moved it to the SD card using "manage applications" .
When launched my old maps and logs on the SD card were found without problem.
I run Android 2.3.5.
I had a test ride at the temperature of 4C.
Full fairing is nice.
Bike run pretty cool at the speed of 140kmph (EngT=56 and AirT=11).
I guess the conditions were not the best for optimising.

It seems that my driving season is over within a week.

My driving season is over.  -5C and 38cm of snow.  But it's not Winter yet.  It's not Winter 'till you see your first dog stuck to a Fire Hydrant. ;)

COnewbie wrote on 11/18/14 at 06:23:36:

It's not Winter 'till you see your first dog stuck to a Fire Hydrant. ;)

Yelp!

A positively balmy 8c here.

By the way - how are your linear TPS tests advancing?

Didn't get past removing from packaging I'm afraid. Will revert when I have some demonstrable progress. One or two folk on the UK Guzzi club forum are interested too so I suppose I better get off my lardy ass and do something.

Which model tps did you end up buying?  I'm interested, too.  My bike seems to run unevenly at around 2-3000 rpm.  I need to check for an air leak, but maybe the tps is giving up.  I spend a lot of time around that rpm range when I am in town.

I suspect the ratio of suspected TPS problems and actual TPS problems is something like 1000:1. Check everything else first. Don't buy a new TPS unless you see a definite and significant problem on your multimeter (or optimiser).

But that's just me!

Hi Raz, was it you that had details of substitute seals for the TB butterflies? Seem to remember / think they are from some carb variant off a Yam or something. I have a dribble of fuel on the starboard one and am thinking about checking it out over the winter.

My Samsung Galaxy Tab 2 7.0 died just before Thanksgiving.  It turns out there are a lot of complaints about battery issues on the Samsung tablets, so I bought an ASUS ME572C as a replacement, and downloaded the latest Optimiser app.  The ASUS is running Android 4.4 (KitKat) and the Optimiser works just fine with it.  I just wanted to let you know.  By the way, I like the improvements in 1.01.  Well done, Cliff! :)

Mad Farquhar wrote on 11/20/14 at 04:46:11:

Hi Raz, was it you that had details of substitute seals for the TB butterflies? Seem to remember / think they are from some carb variant off a Yam or something. I have a dribble of fuel on the starboard one and am thinking about checking it out over the winter.

Yes, I used ones for Yamaha XS 650 (carb!), 256-14997-00-00. Note how they are mounted, ambient pressure is the HIGH pressure here!

When I replaced them I broke a starlock washer, they are not made for re-use. I managed to source new ones locally. I also added shims (8x0.5) at the top, which took some play away.