Welcome, Guest. Please Login or Register
MyECU main site
  Welcome to our forum.
  HomeHelpSearchLoginRegister  
 
Pages: 1 ... 3 4 5 6 7 ... 11
Send Topic Print
Optimiser for Android (Read 145067 times)
LOS
YaBB Newbies
*
Offline


90 Cali IIIFFI 949cc,MyP8
MkV,BT,LC-1,Android Opt

Posts: 32
Helsinki, Finland
Gender: male
Re: Optimiser for Android
Reply #60 - 12/08/12 at 14:20:49
 
Bobd wrote on 12/08/12 at 04: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.
Back to top
 
 
IP Logged
 
YaBB Administrator
YaBB Administrator
*****
Offline


I love YaBB!

Posts: 679
The Land of YaBB
Re: Optimiser for Android
Reply #61 - 12/09/12 at 16: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.

Back to top
 

The Administrator.
WWW  
IP Logged
 
LOS
YaBB Newbies
*
Offline


90 Cali IIIFFI 949cc,MyP8
MkV,BT,LC-1,Android Opt

Posts: 32
Helsinki, Finland
Gender: male
Re: Optimiser for Android
Reply #62 - 12/10/12 at 17:17:39
 
YaBB Administrator wrote on 12/09/12 at 16: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.






Back to top
« Last Edit: 12/10/12 at 20:17:21 by LOS »  
 
IP Logged
 
Bobd
Full Member
***
Offline


I am slowly developing
a relationship with MyEcu.

Posts: 150
Southampton
Gender: male
Re: Optimiser for Android
Reply #63 - 12/11/12 at 03:49:31
 
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.
Back to top
 
 
IP Logged
 
JuhaV
YaBB Newbies
*
Offline


I love MyECU!

Posts: 8
Re: Optimiser for Android
Reply #64 - 12/11/12 at 05:14:43
 
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

Back to top
« Last Edit: 12/11/12 at 05:18:07 by JuhaV »  
 
IP Logged
 
LOS
YaBB Newbies
*
Offline


90 Cali IIIFFI 949cc,MyP8
MkV,BT,LC-1,Android Opt

Posts: 32
Helsinki, Finland
Gender: male
Re: Optimiser for Android - Test results
Reply #65 - 12/14/12 at 09:01:05
 
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...
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
Back to top
« Last Edit: 12/14/12 at 09:18:38 by LOS »  
 
IP Logged
 
YaBB Administrator
YaBB Administrator
*****
Offline


I love YaBB!

Posts: 679
The Land of YaBB
Re: Optimiser for Android
Reply #66 - 12/14/12 at 10:01:05
 
Send me a screen shot of the grid and I'll see if I can optimise the layout.
Back to top
 

The Administrator.
WWW  
IP Logged
 
YaBB Administrator
YaBB Administrator
*****
Offline


I love YaBB!

Posts: 679
The Land of YaBB
Re: Optimiser for Android
Reply #67 - 01/02/13 at 13:31:01
 
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
Back to top
 

The Administrator.
WWW  
IP Logged
 
YaBB Administrator
YaBB Administrator
*****
Offline


I love YaBB!

Posts: 679
The Land of YaBB
Re: Optimiser for Android
Reply #68 - 01/22/13 at 16:41:32
 
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

Back to top
 

The Administrator.
WWW  
IP Logged
 
COnewbie
Full Member
***
Offline


97 Sport1100i My16M MkVII
2 LC-1s

Posts: 120
Central Oregon, USA
Gender: male
Re: Optimiser for Android
Reply #69 - 03/10/13 at 15:34:28
 
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.
Back to top
« Last Edit: 03/11/13 at 03:27:54 by COnewbie »  

44 1/2 degrees North,  1036m up.
 
IP Logged
 
YaBB Administrator
YaBB Administrator
*****
Offline


I love YaBB!

Posts: 679
The Land of YaBB
Re: Optimiser for Android
Reply #70 - 03/11/13 at 08:13:17
 
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
Back to top
 

The Administrator.
WWW  
IP Logged
 
COnewbie
Full Member
***
Offline


97 Sport1100i My16M MkVII
2 LC-1s

Posts: 120
Central Oregon, USA
Gender: male
Re: Optimiser for Android
Reply #71 - 03/11/13 at 10:35:10
 
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?
Back to top
« Last Edit: 03/11/13 at 10:53:25 by COnewbie »  

44 1/2 degrees North,  1036m up.
 
IP Logged
 
COnewbie
Full Member
***
Offline


97 Sport1100i My16M MkVII
2 LC-1s

Posts: 120
Central Oregon, USA
Gender: male
Re: Optimiser for Android
Reply #72 - 03/11/13 at 12:19:01
 
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?
Back to top
 

44 1/2 degrees North,  1036m up.
 
IP Logged
 
YaBB Administrator
YaBB Administrator
*****
Offline


I love YaBB!

Posts: 679
The Land of YaBB
Re: Optimiser for Android
Reply #73 - 03/11/13 at 12:20:32
 
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.
Back to top
 

The Administrator.
WWW  
IP Logged
 
YaBB Administrator
YaBB Administrator
*****
Offline


I love YaBB!

Posts: 679
The Land of YaBB
Re: Optimiser for Android
Reply #74 - 03/11/13 at 12:54:09
 
What version of ECUController have you been using to talk to the ECU
Back to top
 

The Administrator.
WWW  
IP Logged
 
Pages: 1 ... 3 4 5 6 7 ... 11
Send Topic Print