eCtune

calvin wrote:There will be some changed soon in a better way. I was in europe for some personal shit. that is working really bad on me. I cann't talk to much about it. I'm going to start to work back on ectune. fix little things. You all will be informed.

Glad to see you back.

Anyone get any replies yet? I am still waiting. I have a customer that wants a re-tune on meth injection but I can't schedule him until Calvin gets back to me.

I am also waiting on his reply. I sent two emails to him via info - at - ectune.com If Calvin isn't going to be around to take care of his business, he needs to hire some one to handle it for him.

DMTune wrote:nice numbers do you got the graphe to the 607whp pull

The graph is on this page

Update: Car made 607whp. Had issues with the gm solenoid dropping boost off. We will have to re-configure with a mac solenoid next time around.

The issue did not occur for me on my p28 with the romulator. I disabled \"closeloop+ve disable(stock)\" and re-checked the tune & reburned the chip. The random code 10 went away thus far.

I have never heard of this from any of the cars I eCtuned... Admittedly, most of them leave my hands with closed loop carefully tuned and enabled. Could it not be an intermittant IAT sensor problem? (CEL=10) /Allan I doubt it as the car never had this issue while tuning on the ostrich/laptop. I had...

Using the latest devel version with .54 bin I did not click \"closeloop+ve disable(stock)\" and I have a customer reporting a random code 10. Is this bug still around ? I assumed the bug was resolved so I didn't select disable \"closeloop+ve disable(stock)\"

Nice

zeeman wrote:

mtber wrote:Doesnt make a lot of sense, I wish we had other testers online.

I can test, and am available pretty much all the time to do so. Let me know if i can help in any way.

The issue has been resolved.

Newest r6 version seems to work w/ autoscan for me using ostrich 1 w/ 10.9.O firmware.

calvin wrote:fixed and test please

Testing in 10 minutes.

zeeman wrote:i haven't had any problems connecting my ostrich (v1) or datalogging with R6, i'm using the firmware (OST10190) that calvin emailed me.

I think the issue is related to baud settings/firmware/software changing combined...

zex_cool wrote:hmm maybe im looking at a wrong thing. thats what i get then i go moatesfirmware>moatesfirmwareupdater>properties>version tab. its probably the wrong thing, but i thought i'd try.

Open burn1 while your ostrich is connected Read the 2nd line.

zex_cool wrote:1.13.16.0 is the right number i think.

For your firmware ? No... More like 10.9.0 or etc...