openinverter forum

So, as discussed earlier I want to implement a parameter database as soon as the Patreon goal is hit: 2 more $ needed

So in this thread I want to discuss the design.

• Only forum members can post parameter sets to avoid spamming
• Hitting a button on the web interface will transmit your current parameter set to openinverter.org
• You will then be asked things like "What motor do you have, what inverter, what battery voltage"
• Your parameters will be stored to a database and categorized by the data you entered above
• Should it be linked to your forum username? This is a GDPR question merely
• The web interface will be extended to carry an offline copy of the parameter database, I think json.gz should fit the flash
• The advantage: you DON'T need to be connected to both the internet AND the ESP module to use the database
• You can update that database
• You can then choose something like "Apply inverter parameters of inverter X to my controller". Likewise for motor, throttle pedal etc.
• There will also be the possibility to browse the parameters on openinverter.org

More ideas?

johu wrote: ↑Mon Oct 26, 2020 7:10 pm More ideas?

Probably should have a category for vehicle weight and one for drivetrain (FWD vs RWD).

Some people might be interested in a field for driving/tune style, i.e. street/track, smooth/aggressive, commuter/racecar

Yes that makes much sense

Assuming that vehicle weight and wheel diameter are factors that would effect the tune, is it worth including that, or is there another calculation for that? Final drive ratio for RWD or AWD (if a motor with reduction gear is centre mounted, in place of a transfer case) may also be a factor.

Nice idea!

I wonder if the upload could be added to the user Profile and viewable in the "Manage Attachments" option. Associating with a UID is a good idea I think, to aid in searching.

Joined your Patreon, hopefully that gets you to your goal. This is a pretty cool idea, would be handy to have maybe versions to subscribe to and the car can automatically check for parameter updates and notify the user somehow that they might want to update. Also direct downloading and updating of firmware would be cool.

Just wondering how the database would appear for selection. If someone uploads several versions of their parameters (i.e. they've made improvements) they should be able to remove their previous uploads, however they may want to host multiple iterations of the same setup for different tunes (e.g. race track, commuting).

In terms of GDPR, you could have a brief GDPR warning and asking users to confirm they are happy to have their username appended without warranty to the parameters.

I don't think GDPR is an issue for usernames.

They are displayed on the forum anyway. You just have to state what it'll be used for and how long you're storing it, I think you have to have a way to annonomise it on request too. That's my understanding.

Thanks for jumping on Patreon and joining development.
I take it away that metadata implementation must be very flexible All questions to the poster will be stored in the database. Some items (like AWD, FWD RWD) are maybe better off as enums instead of free text to avoid semantic duplicates like "FWD" vs. "Front wheel drive".

Every parameter set that is posted does have a date attached to it. The user who posted it can delete their own set.

Concerning GDPR I'll just have a checkbox and a description of how the data is used.

I think the database will be free for all to view, even non-forum members. I will have a "digikey" style filter that lets you filter the posted parameter sets by the metadata suggested above.

I'm also now thinking whether to have a list of parameters that are highly custom to you personal preference or your setup. For example "dirmode" or the various regen parameters. Those parameters can then be excluded when applying the set to your inverter.

Bigpie wrote: ↑Tue Oct 27, 2020 4:09 pm Joined your Patreon, hopefully that gets you to your goal. This is a pretty cool idea, would be handy to have maybe versions to subscribe to and the car can automatically check for parameter updates and notify the user somehow that they might want to update. Also direct downloading and updating of firmware would be cool.

Yes, goal reached
The only challenge with automatic updates is to setup your connection. By default you connect to the inverter via wifi (be it your phone or laptop) and thereby loose internet connectivity. Easy to solve, as you can just enable mobile data (and disable "use for internet" in wifi options) or plug in an ethernet cord. Just something people need to be made aware of so they don't write "it doesn't work" forum posts

Otherwise it would be easy to subscribe to a specific parameter set by its numeric id.

When you post a parameter set you can choose to update the existing one which will get people notified or create a new one with different goals, that will NOT get people notified.

Shouldn't we use svn or git in this design? Comparing files becomes then easy and version administration is included.
Perhaps we can build an interpreter for the differences and for storage of the individual parameters and for storage git and then save the git link with the user.

It won't be file based but based on parameters and categories. So you can use for example motor parameters from one set and inverter parameters from another.
I'm using a mysql database for now. Source code will go on github.

Just want to let everyone know we (Dima, me) are making good progress with the database.

Thank you both. You guys rule, can’t wait to see how you get on

It is done
Huge shoutout to Dima who designed the graphical interface on the server side.
Now, to use it:
- Download https://github.com/jsphuebner/esp8266-web-interface
- Upload the files inverter.js, index.js, index.html to your ESP module (via Update on top of the page)
- Refresh
- Upgrade your inverter firmware to 4.95.R if you want to submit parameters (release coming)
- If you think your parameters are awesome, submit them with the apparent button

To download parameters
- Go to https://openinverter.org/parameters
- Choose a parameter set
- Choose the parameter categories you want to download, e.g. just "Motor"
- a) download as json file and apply that to your inverter
- or b) subscribe to the parameter set - now every time it is updated you will be notified!
- Subscription is done by pressing subscribe, copying the token and pasting it into the ESP web interface + <Enter>

In order for this to work your computer/phone must be connected to the internet AND the wifi module simultaneously.

Awesome, many thanks to you and Dima for implementing this feature. You guys rock!

Very nice

Nice job!

I wrote about it on the DIY EV forums: https://www.diyelectriccar.com/threads/ ... ne.204096/

One suggestion: Allow people to name them, or number them, or something, so people know what they're using and can refer to them.

Is it possible to calculate the power and torque output (at the output shaft) from the parameters?

MattsAwesomeStuff wrote: ↑Sun Nov 15, 2020 9:38 pm One suggestion: Allow people to name them, or number them, or something, so people know what they're using and can refer to them.

They are numbered internally so you can post links like that: https://openinverter.org/parameters/view.html?id=10
That said we can add arbitrary metadata if needed.

jalovick wrote: ↑Mon Nov 16, 2020 4:05 am Is it possible to calculate the power and torque output (at the output shaft) from the parameters?

Very hard for sine software, possible for FOC (100*throtcur*udc/sqrt(2) ). Maybe easier to let people specify it in the metadata, at least for sine.

MattsAwesomeStuff wrote: ↑Sun Nov 15, 2020 9:36 pm I wrote about it on the DIY EV forums: https://www.diyelectriccar.com/threads/ ... ne.204096/

Thanks

Just posted Tesla SDU and LDU parameters.
Please start posting your parameters for other hardware

It doesn't seem to let me post. I'll have to try re-uploading the new files to the web interface. It seems to be missing the token parameter as it goes through to the open inverter website for login etc.