Tuning cycle times

turtle · Post by **turtle** » Wed Feb 15, 2006 4:04 am

Trying to decide if the K-pro is the right choice for our tuning application,

Specifically what is the Cell Update speed, per increment or tuning iteration how real time is it? I?m building a very hi load large boost drag engine I would like as fast a feedback cycle as possible this is crucial for giving me some headroom in the tuning process.

Could any other users post their experience in this context with the K-pro please.

Kind regards

turtle

Post by **Spunkster** » Wed Feb 15, 2006 10:39 am

All datalogging is real-time, however you cannot make changes real-time wihth the K-Pro...this is of the limitation of the processor on the stock ecu.

turtle · Post by **turtle** » Sat Feb 18, 2006 6:30 am

Thanks, thats helps me some, I see the flash time of the stock ecu's cpu must have some issues. it would be of some help to give me an idea of this up date cycle time to put this in context please.

~ typcial cycle times per cel would do per up date event.

regards

turtle

turtle · Post by **turtle** » Fri Feb 24, 2006 4:09 am

can anyone help me with this? please it would just help me qualfy the risk.

thanks

turtle

Post by **Hondata** » Fri Feb 24, 2006 9:21 am

I don't really understand your question, but here is some information. To upload a calibration takes about 60-90 second, and then subsequent updates are non-realtime and take about 1-5 seconds. The engine can be running while you upload changes but not under load.

The generally approach is not to tune every cell, but to use a starting calibration ('basemap') and make chances over large areas of the tables. In any case, unless you have an engine dyno it is not possible to make changes in realtime while under full load, on anything other than a low hp engine, so a dyno run / interpret results / tuning change / stabilize temperature / dyno run cycle is necessary.