rusefi.com

This ECU project is somewhat stalled in beta version: the hardware design is pretty settled and looks good, software is still lacking a bit but kind-of-good-enough, but no one with advanced car & tuning experienced has played with this yet to really test it. Until someone who would really be able to evaluate it tries it, I am in the dark in terms of what is missing to make the last steps towards having something useful.

I have a prototyping shop assembling these boards for us, a bunch of people got these but troubleshooting this is really requiring some advanced skills.

http://www.miataturbo.net/ecus-tuning-54/anyone-get-involved-diy-ecu-74678/page4/#post1307884

I'm willing to help and debug this ecu.

I have a lot of experience with the Megasquirt ecus and I also tune cars.

I know very well toyota 7m, 1jz, 2jz engines and I can test on my 2jz.

I really like the fact that you're using tuner studio instead of trying to build an other software that would take a lot of years to beat what tuner studio can do.

I think the main problem with DIY ECU projects is the lack of software features. Software developpement is a lot more work that doing the hardware. It will take years for a programmer alone to develop a complete sofware with features that will be as advanced as the other plateforms.

But I think that this ecu projet has a lot of potential.

Suprazz wrote:I'm willing to help and debug this ecu.

I have exactly two assembled boards in stock at https://www.tindie.com/stores/russian/ and I advice against buying a kit since 90% of these are never assembled - it's ~300 soldering points which is 30 times longer an average attention span these days
The next batch would realistically be the same version 0.4

https://svn.code.sf.net/p/rusefi/code/trunk/firmware/tunerstudio/rusefi.ini now has SettingContextHelp tooltips.

4 fields are already documented, about 450 more fields to go! By the way, that part of TS definition file is generated based on https://svn.code.sf.net/p/rusefi/code/trunk/firmware/integration/rusefi_config.txt file - this was C-header is always in sync with the TS definition.

TunerStudio has outputs testing now:

Still on vacation - not much progress to happen till the end of this week

AS long as we get to crack the whip on you as soon as you're back to negate all the relaxation you may have experienced, we'll be OK with you being out for now.

Bugfix: https://sourceforge.net/p/rusefi/tickets/281/ red LED now stays on even for fatal errors happening right on startup. Also better FATAL handling in console software.

new feature: dizzy mode output is needed to have functioning oem tachometer if converting an older car to COP

SD card logging fixed & documented - http://rusefi.com/wiki/index.php?title=Manual:Software:logging

https://sourceforge.net/p/rusefi/tickets/286/ fixed - thank you @ for reporting the issue!

Based on that Lemons race I am changing the status @ http://rusefi.com/wiki/index.php?title=Main_Page from Beta to RC1.

[video][/video]

Sweet, and it needs some close ups of that sweet enclosure.

Thank you @ for reporting https://sourceforge.net/p/rusefi/tickets/294/ - fixed now. Still need to fix https://sourceforge.net/p/rusefi/tickets/199/

Well, now https://sourceforge.net/p/rusefi/tickets/199/ is also fixed.

TunerStudio project now allows auto-tube based on MAF sensor.

Well, now https://sourceforge.net/p/rusefi/tickets/199/ is also fixed.

When calibrating TPS, the settings appear to be "backwards"

What is the correct direction for TPS voltage sensing?
I wired mine to be about 0v for closed, and 3.25v for wide open.

Mine shows backwards in TS now, and I have firmware from 6/14 that should have this fix, right?

tomiata wrote:Mine shows backwards in TS now, and I have firmware from 6/14 that should have this fix, right?

I've actually reverted part of the changes yesterday or the day before yesterday. I am a bit confused about what exactly went wrong, but I suspect that only one thing was broken and I have changed two things.

Direction does not matter, just use TS Tools->calibration. I've seen it working for @ yesterday.

After updating to 6/18 firmware calibrating tps shows sane results for 0 to 100% rather than 100 to 0. TPS report is good now

Usability: 'pause' button on the gauge tab
Tiny feature: 'vehicle speed to rpm ratio' gauge - know what gear you are in and if any tire spin.

New feature: extra idle valve air while cranking - this should make cold start easier https://sourceforge.net/p/rusefi/tickets/297/

FSIO bugfix: https://sourceforge.net/p/rusefi/tickets/298/

There will be incompatible configuration changes soon - once you update firmware you would need to check the whole config. That's about making tune maps smaller & adding more generic output maps for VVTi.

[video][/video]

It's pretty hot here these days and @ has his ECU under the hood.

New features: logging CPU internal temperature https://sourceforge.net/p/rusefi/tickets/302/
gauge name is "internal temperature"

Congrats to @ and his 6.0L v8 from https://en.wikipedia.org/wiki/ZIL-130

[video][/video]

russian wrote:Congrats to @ and his 6.0L v8 from https://en.wikipedia.org/wiki/ZIL-130

[video][/video]

Are my eyes deceiving me or are there a pair of turbos waiting to be hooked up? Sounds mean!

Things are still a bit slow - family members staying with me for another week and then a race on the 12-14 Aug weekend, this one on the border of CT MA and RI.

Yeah, same this way, have to deliver a car this week on fueltech, piece of crap ECU it is, this Brazilian guys are 15 years behind.

That recent RTC hardware progress http://rusefi.com/forum/viewtopic.php?f=4&t=460 was about making log file names use current date and time, this is now working. Probably not the most important thing I should have worked on but wanted to have this for the coming race this weekend.

I am working on bug fixes, stay tuned.