stylesuxx / esc-configurator Goto Github PK

BLHELI_32 ESC's can be flashed with AM32. It only requires initial bootloader flashing from the test-point on the ESC, from there, everything can be flashed via 4 way interface.

The initial BL flashing needs to be done manually, the configurator will not support that, but from there on, we can manage AM32 like the SiLabs chips.

When flashing AM32 Hex, interface returns to home screen immediately.

It should be possible to allow spinning of motors via MSP as suggested by @AlkaMotors

• spin all motors
• spin individual motors
• spin multiple, individual motors

Messages that are posted to the log should be translatable

Adapt the wording so that it says that Chromium based browsers are supported:

• Chrome
• Edge
• Vivaldi
• Brave (seems to have some issues)

Right now I am still using layout for Revision 0.
Two values seem to be missing here:

• beep volume
• 30ms telemetry

The "Save Log" button does nothing for now - I honestly also do not think, that the log from the bar is really worth exporting - maybe this could be used to export debug logs from the console instead.

Once a serial port has been selected it is not possible to select a different one unless you detach the device.

The og configurator has some mechanic for caching firmware files - something similar could be done here too using the local storage - but does this make sense?

There should be a screen to manage settings.

Right now it is only possible to flash Bluejay, but technically this could be a selection in the firmware selection screen and would allow for different firmwares to be flashed.

In the firmware selection Tab a new Dropdown should be added which allows to select which Firmware should be flashed.

Options:

• BLHELI_s
• Bluejay

Once this is implemented, any other variant can easily be added if it follows the structure of the configuration files.

• Implement lanaguage switcher
• Save chosen language between sessions

Once the service worker detects new code it should show a notification to the user to reload the app.

The components of the firmware selector could be refactored into separate components.

If the configuration files (escs.json versions.json) were part of the firmware file, we could get them from there and the configurator would basically not needed to be updated at all.

Only the EEPROM layouts would need to be migrated to their own JSON file too.

There should be some kind of warning - error message when flashing a local file does not work.

It should be possible to select a local HEX file for flashing.

Settings with the visibleIf condition need to be updated after a change has been made in the settings.

The checkbox is present, but does nothing yet.

Since this can be easily deployed as a SaaS, AGPL can protect this better.

It should be possible to show detailed information about each setting when the user hovers over an icon.

• Implement functionality to display tool-tips
• Add the actual tool-tips to the translation file

Pre-select the first option in the firmware selection.

The currently used Input range component for the sliders is pretty much unmaintained and a delay is needed for it to work properly - would be good to refactor this to a different library.

@Noctaro is designing a Logo, since the Bluejay Logo does not really represent the project as a whole.

A lot of things are not yet translated. I tried to use the translator function for all static strings, but there are still missing from the translation file.

Everything that is camel cases is basically not yet translated, the majority of which are settings related to og BLHELI_S.

Add functionality to reset everything back to default settings.

Use https://wwayne.github.io/react-tooltip/ for tooltips.

@AlkaMotors it would be really nice if you could document the AM32 settings here. Just explain a bit what the setting does.

Allow direct input on fields that have a slider.

Wrap the serial functionality into a state machine to remove some "responsibility" from the UI.

This will prevent restoring defaults during flashing for example.

A solution to the BLHELI_S vs. BLHELI_M problem might be, to allow the user to select which firmware is actually running.

Add functionality to show up down utilization in app bar.

@mathiasvr requested motor speed to be adjusted via DSHOT instead of MSP to benefit from the full resolution.

This could be made optional - per default the speed is done via MSP, and on user request (checkbox) the Speed can be set via DSHOT command.

We could also use this in combination with EDT. Some kind of monitor for DSHOT commands.

https://github.com/mathiasvr/bluejay/releases/tag/v0.11-test

Technically the Web Serial API remembers which serial devices access was given to. If multiple of those devices are currently connected, a drop-down displaying all of the available devices could be displayed.

Right now only flashing SiLab MCU's is possible, a lot code to support ATMEL and ARM is already present - the actual flashing part needs to be implemented and tested.

ESC hint should also be pre-set on AM32 so that the proper ESC is already pre-selected.

Settings need to be merged after flashing - so that the direction of the motors is left as it initially was.

This would allow ESC's to be flashed without a need for a flight controller as suggested by @AlkaMotors

One could simply use a FTDI adapter or arduino or anything similar.

Tracking is not implemented at all for the moment. To do so, we would need to ask the users for consent.

I am not yet sure what the best course of action for this is right now.

Config files are prepared - but it seems the BLHELI M confiugrator does something else too - the PWM settings are not showing up for some reason.

https://github.com/Asizon/blheli-configurator/tree/1.2.0-jazzmaverick-beta4

This one might be tricky, since BLHELI_M is not setting a custom name and to detect the settings it is important that we can identify what we are dealing with.

For this to work, BLHELI_M needs to set the NAME field of the EEPROM layout, only then this feature can be realized.

• If BLHeli_S v16.9 is detected, display a warning similar to JESC for people to use the dedicated BLHeli_M configurator

If an unknown layout is detected, flashing should still be possible.

It seems there are some problems when only 1 ESC is attached - the configurator still is looking for the other three.

Can you port the translation to crowdin platform? I can do Simplified Chinese and Traditional Chinese.