Page 14 of 17

Re: Firmware developent status

Posted: Tue Jun 04, 2019 9:08 pm
by AndreyB
russian wrote:
Sat Jun 01, 2019 8:33 pm
https://rusefi.com/build_server/ is back in business
Now it's really back in business using USB-TTL instead of ST native VCP.


Next step trying different USB controller
https://www.amazon.com/gp/product/B01G85LFEK

Re: Firmware developent status

Posted: Sat Jun 08, 2019 1:35 am
by AndreyB
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! :)

Re: Firmware developent status

Posted: Sun Jun 16, 2019 11:43 pm
by AndreyB
Initial setup could be a bit easier for future users once we document how to use https://rusefi.com/build_server/st_files/silent_st_drivers.exe

More details on this at https://github.com/rusefi/rusefi/issues/845

Re: Firmware developent status

Posted: Sun Jun 23, 2019 2:46 pm
by AndreyB
I have added some Windows 10 into my life so https://github.com/rusefi/rusefi/issues/849 and https://github.com/rusefi/rusefi/issues/816 were resolved

Can use some help with https://github.com/rusefi/rusefi/issues/858 investigation

Re: Firmware developent status

Posted: Mon Jul 01, 2019 4:51 pm
by AndreyB
Usability improvement: rusEfi console now comes with ST drivers and a button to install those. https://github.com/rusefi/rusefi/issues/845

Image

Re: Firmware developent status

Posted: Sun Jul 07, 2019 1:10 am
by AndreyB
Minor usability improvement - if your cranking fuel is zero due to corrections, at least you get a warning code now.

https://github.com/rusefi/rusefi/commit/1fce0201a55c45f8333883cc95589c701d5723d5

Re: Firmware developent status

Posted: Sun Jul 07, 2019 9:38 pm
by AndreyB
@mck1117 has contributed TunerStudio tooth logger implementation - currently works only for single VR channel but that's a great step forward!


Re: Firmware developent status

Posted: Sun Jul 07, 2019 10:12 pm
by puff
where do we read about it?
the window to the left - what is it?
what's needed to get into this tooth logger?

Re: Firmware developent status

Posted: Sun Jul 07, 2019 10:15 pm
by AndreyB
puff wrote:
Sun Jul 07, 2019 10:12 pm
where do we read about it?
what's needed to get into this tooth logger?
There is a slack room for this feature https://rusefi.slack.com/messages/CL8EYJSUX/details/

Re: Firmware developent status

Posted: Sun Jul 14, 2019 1:26 pm
by AndreyB
Too much usability maybe? Not sure. rusEfi console now has an icon to launch Device Manager since that's how you know which COM port to select.

Re: Firmware developent status

Posted: Sun Jul 14, 2019 10:13 pm
by AndreyB
Build server now uses gcc 8.3 (8-2019-q3-update arm) - as of yesterday it was gcc 7 from 2017.

Re: Firmware developent status

Posted: Sun Jul 28, 2019 5:07 pm
by AndreyB
A stepping stone for better firmware upgrade experience is "software DFU switch", this now works at least on stm32f4 - see https://github.com/rusefi/rusefi/issues/809

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.

Re: Firmware developent status

Posted: Mon Aug 26, 2019 4:40 pm
by AndreyB
I put a lot of emphasis on infrastructure and testing automation. In my opinion it was important to get https://rusefi.com/docs/unit_tests_coverage/ and we now have it :)

Re: Firmware developent status

Posted: Tue Sep 10, 2019 12:56 am
by AndreyB
https://github.com/rusefi/rusefi/issues/924 fixed & some CI coverage added. Thank you @Fantomiaso for error report!

Re: Firmware developent status

Posted: Sat Sep 14, 2019 2:39 pm
by AndreyB

Re: Firmware developent status

Posted: Sun Sep 22, 2019 10:17 pm
by AndreyB
ETB target is using integer values #945 fixed https://github.com/rusefi/rusefi/issues/945

While originally discovered in relation to ETB, same defect was probably affecting VVT target value and maybe some other table lookup.

Thank you @mck1117 for spotting the issue!

Re: Firmware developent status

Posted: Mon Sep 23, 2019 6:04 am
by AndreyB
Another juicy defect - https://github.com/rusefi/rusefi/issues/948 - good old buffer overrun!

this time it's the other way around - I've discovered and @mck1117 fixed :)

Re: Firmware developent status

Posted: Sun Sep 29, 2019 1:58 pm
by AndreyB

Re: Firmware developent status

Posted: Thu Nov 07, 2019 8:24 pm
by AndreyB
Build server now uses brand new GCC 9 compiler https://github.com/rusefi/rusefi/issues/1001

Re: Firmware developent status

Posted: Tue Jan 14, 2020 8:02 am
by AndreyB
https://github.com/rusefi/rusefi webpage now has a lovely icon for https://www.patreon.com/rusefi

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

https://github.com/rusefi/rusefi/issues/1284
https://github.com/rusefi/rusefi/issues/1285
https://github.com/rusefi/rusefi/issues/1286
https://github.com/rusefi/rusefi/issues/140

Re: Firmware developent status

Posted: Sun Apr 19, 2020 1:05 am
by AndreyB
FSIO usability progress - rusEfi console now has decode_rpn command. More at https://github.com/rusefi/rusefi/wiki/FSIO

Re: Firmware developent status

Posted: Sun Apr 19, 2020 2:20 am
by AndreyB
Someone has asked about Renix 44-2-2 trigger support. Well, it's really easy to add triggers into rusEfi so we have it now :)

https://github.com/rusefi/rusefi/wiki/All_Supported_Triggers

Re: Firmware developent status

Posted: Mon Apr 20, 2020 1:44 am
by AndreyB
We now use TunerStudio native mechanism for critical error messages and less critical messages are displayed on Base Engine dialog.

Re: Firmware developent status

Posted: Mon Apr 20, 2020 7:53 pm
by AndreyB
Apr, 20 2020 status:
* Nick and Chris are focusing on GDI progress
* Matt is focusing on ETB https://github.com/rusefi/rusefi/issues/1240 https://github.com/rusefi/rusefi/issues/1336
* x number of Andreys are focusing on data gathering usability https://github.com/rusefi/rusefi/issues/1337