In order to be the best open source project in our field we have to rely on best infrastructure. While rusEfi is probably the only open source ECU with unit tests and continues integration testing already, we still can use more tools to be even better. If anyone is interested to help here are some of the boring tickets: https://github.com/rusefi/rusefi/labels/INFRASTRUCTURE
Re: Firmware developent status
Posted: Mon Jun 10, 2019 12:44 am
by AndreyB
rusEfi bundle files on https://rusefi.com/build_server/ now have a bit nicer folder structure and a bit less files to reduce confusion. Also readme.html is now included!
Clive Two.Zero is the guy on ST community forums without whom I would not be able to implement this so quickly. I've just paypalled him some $$ and I would encourage everyone to consider the same. His PayPal, Venmo and Amazon Gift Cards info at https://community.st.com/s/profile/0050X000007vuogQAA
Re: Firmware developent status
Posted: Thu Aug 15, 2019 2:41 am
by AndreyB
rusEfi console new usability feature: auto-detect serial port.
Right now my firmware focus is on ETB safety and multi-channel VVT. Vacation is over, this Saturday I hope to land in a warm country without a beach so should have time to code peacefully
Re: Firmware developent status
Posted: Tue Mar 03, 2020 12:14 am
by AndreyB
Mar, 02 2020 status:
* playing with some GDI software, but now waiting for repaired MC33816 to come from Seattle
* Matt and DronoGus are working on different parts of getting stepper control using two universal H-bridged, that would give us stepper idle control on microRusEfi.
* A _lot_ of hardware to play with - v12 on Manhattan, v12 on Proteus, setting up microRusEfi fabrication.
Re: Firmware developent status
Posted: Thu Mar 26, 2020 5:51 am
by AndreyB
@mck1117 has contributed a bunch of great code recently!
We have CAN status broadcast - our own custom protocol since ODB-II or else does not do broadcast as far as we know.
And now we've just merged multi-spark!
Re: Firmware developent status
Posted: Sun Mar 29, 2020 12:16 am
by AndreyB
A few usability improvements:
Human-readable critical errors (what used to be called 'fatal' is now renamed to 'critical') are now available in TunerStudio, in the "Base Engine" dialog for now.
Some settings are now marked 'requiresPowerCycle' in the project - we would need to mark few more with this attribute, but at least we have a sample now.
Re: Firmware developent status
Posted: Sun Apr 12, 2020 3:35 pm
by AndreyB
In light of my hardware issue with trigger and while I am waiting for a Rigol @andreika and I will look into the state of tooth logging in rusEfi