Firmware developent status

[AndreyB]

image.png (101.25 KiB) Viewed 57403 times

rusEFI console command line now has "help" parameter and prints list of available command line tools on start:

Tool available: compile
Tool available: compile_fsio_file
Tool available: firing_order
Tool available: functional_test
Tool available: headless
Tool available: help
Tool available: ptrace_enums
Tool available: reboot_dfu
Tool available: reboot_ecu

"functional_test" is the interesting one for developers
reboot_dfu and reboot_ecu are just cool

[AndreyB]

rusEFI console time start-up time was improved by 2-3 seconds.

This would not happen without two people providing feedback. Your feedback is really important. Also at the moment it's really unclear if anyone uses rusEFI at all so please let us know

[dexter_lab]

I can test during the weekend.
Need to find a documentation how to upgrade.
As today I cannot enter DFU mode with MRE from pin 15,16

[AndreyB]

I can test during the weekend.
Need to find a documentation how to upgrade.
As today I cannot enter DFU mode with MRE from pin 15,16

Can you open the case or is your preference not to open the case?
How do you power you MRE?
Does USB on 15,16 talk to console?

"I cannot enter DFU mode" could mean at least 3 or maybe 5 different things. Please be more specific if you are looking for input.

[AndreyB]

rusEFI console now write high speed tooth log file until we have at least 300 rpm for at least 10 seconds.

Actually, console writes same data in two formats - in TunerStudio CSV format and in https://en.wikipedia.org/wiki/Value_change_dump format which could be viewed with a number of different free tools including https://sigrok.org/wiki/Downloads

https://github.com/rusefi/rusefi/wiki/rusEFI-logs-folder

[puff]

It would be handy if it could write it directly to the sd-card, regardless whether console is connected or not - in case there is some crosstalk in usb cable and the connection is not reliable (if its not implemented yet)

[AndreyB]

Tune upload using auth tokens now works from both rusEFI console GUI and command line. Command lines now how a brief explanation.

I need help with testing this a bit: I am not 100% confident in .msq files rusEFI console is producing, I wonder if some fields are not making into the tune or maybe some fields are not persisted right. If anyone can play with it and report issues that would be great.

The big theme here is the rusEFI online experience eventually with logs being published and tune modifications taken from internet.

Code: Select all

rusEfi UI console 20200531
Compiled Sun May 31 18:18:39 EDT 2020



Tool available: compile_fsio_file
	Convert all lines from a file to RPN form.


Tool available: compile_fsio_line
	Convert a line to RPN form.


Tool available: convert_binary_configuration_to_xml
	NOT A USER TOOL. Development tool to convert binary configuration into XML form.


Tool available: detect
	Find attached rusEFI


Tool available: firing_order
	NOT A USER TOOL. Development tool relating to adding new firing order into rusEFI firmware.


Tool available: functional_test
	NOT A USER TOOL. Development tool related to functional testing


Tool available: headless
	Connect to rusEFI controller and start saving logs.


Tool available: help
	Print this help.


Tool available: print_auth_token
	Print current rusEFI Online authentication token.


Tool available: ptrace_enums
	NOT A USER TOOL. Development tool to process pefrormance trace enums


Tool available: reboot_dfu
	Sends a command to switch rusEFI controller into DFU mode.


Tool available: reboot_ecu
	Sends a command to reboot rusEFI controller.


Tool available: set_auth_token
	Set rusEFI authentication token.


Tool available: upload_tune
	Upload specified tune file using auth token from settings

[AndreyB]

Saleae said It is not possible to create or modify a saved *.logicdata files.

@andreika said LogicdataStreamFile.java

rusEFI console now writes same cranking composite event logging into three files: TS CSV, VCD and logicdata formats.

[AndreyB]

@kon has just contributed E90 gauge cluster support, waiting for a sweet demo video.

rusEFI console now writes logs in binary MLQ format in addition to legacy plain text MSL format. My focus these days is on rusEFI Online, getting closer to logs auto-upload from TS, rusEFI console and small linux devices.

[AndreyB]

@dbh97 has migrated all important infrastructure batch files to bash and moved bundle generation to github actions - that means that all bundles for all boards & platforms are now ready in under 10 minutes after merge!

[AndreyB]

Bundle has bin/ folder now, inside bin/ folder we now have dfu_program.sh which runs rusEFI own DFU tool on Linux and Darwin. On Windows there is just too much drama with drivers to use this tool.

[AndreyB]

New feature: We now have access to SD card logs via rusEFI TunerStudio plugin.

[AndreyB]

Bosch Quick Start wheel is now supported for VVT - that was https://github.com/rusefi/rusefi/issues/883

[AndreyB]

New official release https://github.com/rusefi/rusefi/releases/tag/20200831

[AndreyB]

Two new trigger wheels, one of these VVT

[Simon@FutureProof]

Ohhh, ST170/focus SVT, previously people were disabling the VVT to use OMEX etc.

[AndreyB]

Forum is quite but a lot is happening

A recent amazing change by David is the new connector meta info file format, for example in case of Hellen72 it's https://github.com/rusefi/rusefi/blob/master/firmware/config/boards/hellen/hellen72/connectors/main.yaml

[AndreyB]

Matt strikes again. rusEFI now gives access to SD card via USB. We are like proper adults now! The magic of composite USB device allows us to tune ECU while downloading logs as well!

[mck1117]

We also report a serial number over USB now - so multiple rusEFI devices should always show up as the same COM port on your PC (if you're a weirdo like me and have literally 10 ECUs sitting around).

image.png (106.76 KiB) Viewed 56583 times

[Simon@FutureProof]

What's the serial number based on? MCU serial?

PM me if you don't want that out in public.

[mck1117]

What's the serial number based on? MCU serial?

PM me if you don't want that out in public.

ST burns a serial number in to the chip in the factory, and that's the one we send over USB. They guarantee that no two STM32 devices will ever have the same serial number.

[mck1117]

More neat USB features:

Built in ini file for TunerStudio means if you have the ECU, you never have to go hunting for the matching ini.

[AndreyB]

A lot happens on Slack see https://rusefi.com/forum/viewtopic.php?f=13&t=1198

we now have fancy auto-detect of HSE speed https://github.com/rusefi/rusefi/commit/15353ae3b26274bf300dab34719ac506d3612eb7
rusEFI console starts up a bit quicker now https://github.com/rusefi/rusefi/issues/2964

but same as before same as always we are constantly looking for C/C++/Java/PHP developers

[AndreyB]

it has major usability issues but at least there is a way to get human readable warning messages via tuner studio

image.png (51.35 KiB) Viewed 54733 times

[AndreyB]

We now support VQ30DE cam wheel - just the cam wheel I think should be enough to begin with. Lovely engine pictures at https://github.com/rusefi/rusefi/issues/2974

[AndreyB]

Now that we have dozens of different firmware versions

image.png (7.85 KiB) Viewed 53848 times

[AndreyB]

We are very excited about user-defined Lua and converting some of the system logic into Lua. Nothing definitive yet but it's really recommended to use at least stm32f42x with 256K of ram to future proof your hardware.

[AndreyB]

Let's welcome third generation of live data/live logic/live view feature of rusEFI: the top side of the screen is the new stuff, console shows actual snippets of C/C++ code annotated with live field state.

Bottom side of this screenshot shows TeX approach to live view, it's going to be removed in a couple of days. While it looks amazing it's just too much effort to keep ECU firmware in sync with TeX live view. Second approach to live view was about annotating ECU firmware code but again that was just too much effort. Yesterday I've realized that simply showing ECU source code as is could be the best way for us considering lowest costs of keeping ECU and tools in sync.

image.png (139.23 KiB) Viewed 53504 times

[AndreyB]

Incompatible change in Makefile affecting existing clones https://github.com/rusefi/rusefi/pull/3505

please manually remove firmware/pch/pch.h.gch this used to be a file and now it's a directory

Code: Select all

git clean -f -X

could be a way to reset your local clone to as-freshly-cloned state, assuming you do not have valuable uncommited changes.

[AndreyB]

Snapshot version of console now has a couple of new options:

"Switch to DFU" works on all operating systems
"Full Erase" works once ECU is in DFU mode, only on Windows

image.png (27.73 KiB) Viewed 52595 times