Hahaha no agree with no bugs in your code I’m the same way… just if you have more pressing features/bugs/etc you can always deal with this after.
Feel free to ping me if you need any additional data. Idk if it’s relevant but it has dual stormcores installed with a metr module as well. (Doubt that’s helpful but who knows )
Screen customization is definitely on the roadmap. First I have to get around memory issues though. At this point it’s not possible to add any more features without causing memory errors.
My priority now is to catch up with the orders. I’m close. Then there will be more time for development.
I can never get all the battery status blocks filled with the battery fully charged and wondering why Davega doesn’t see my 10s3p 30Q battery fully charged.
It was just 1 month ago (Oct 5). I’ll contact you in a a week or two. I’m still a bit behind with handling the orders but I’m catching up. Some people are greedy and mess up my estimates. Often I look at the order list and I’m like “okay, this is just 10 orders, 2 will probably bail out, so I’ll need about 8 units to sort it out”. Then I open up the notes and there’s “I’d like 2 units”, “can I have 3 units please” so I end up needing 20 where I accounted for 8.
I implemented very basic analytics for the DAVEGA data uploaded in backups. This will work best if you have automatic backups turned on and upload your DAVEGA data to the cloud on regular basis.
You can check it out for your own device at Analytics - DAVEGA. Or, if you don’t have a device with enough data, you can look at the demo. That one currently shows the data for my own DAVEGA.
I wasn’t sure if anyone would be interested in the functionality so I didn’t spend much time on it. This was coded in one day. If people like it and use it, I’ll be happy to extend it though. The features that come to mind include:
custom time intervals
imperial units
set/save default list of datasets
additional datasets
custom chart title
shareable links
Please let me know if there’s anything particular you’d like to see implemented.
Important: If you’d like to share your analytics with anybody else, I suggest that you currently just take a screenshot. Keep your device ID confidential. User accounts will be created at davega.eu at some point and the device ID will then be used for associating the DAVEGA unit with your user account.
I’m sure somebody will ask about the “km/h delta” and “Wh/km delta”. These show the speed/consumption at the current datapoint since the previous datapoint. For example, having two datapoints with:
distance (km): 20, 50
time traveled (h): 1, 2
The avg speed would be as follows:
avg speed (km/h): 20, 25
avg speed incremental (km/h): 20, 30
The diff between the first and second datapoint is 30 km and 1 hour, which implies 30 km/h avg speed whereas the overall avg speed is 50/2 = 25 km/h. I hope that makes sense.
Haha, I was pretty close to starting on that. Fortunately I figured out ways to optimize without leaving the micropython platform. I’m really glad. Rewriting to C would take me weeks at the very least and then C vs micropython is like a shovel vs a digger.
The next batch of DAVEGA X enclosures is being made here in Brno, Czech Republic. Today, the CNC company allowed me to come see how the machining is done. It’s pretty cool. I have some vids as well that I’ll post later. A little bit of editing is needed.