I have a question regarding my davega
I set it up tday for a 16s5p setup with molicells42a so the pack has 20ah
I added these settings to the davega and it shows me 70v (battery is fully loaded) but a 16s pack should have 67,2v fully loaded
Wht can be the reason for this?
Kr and thx very much!!
Have you checked the battery voltage with a multimeter?
The voltage is retrieved from the VESC and it’s known not to give very accurate readings. 3 volts diff seems a lot though so I would check what the actual voltage is and make sure your battery does not get overcharged.
3 Likes
Yes the smart bms shows me 67,15 volts
So this should be fine
Should i try to reset the davega?
Btw also the range is calculated with 30km
Which dosent seem correct to me
Is there anything i can do?
Nothing to be done at DAVEGA end. This is a VESC issue. I could implement some offsetting but the question is whether the offset remains consistent throughout the discharge cycle. You may want to compare the BMS and VESC readings when the battery is discharged.
1 Like
Id rather not have a $1000 phone mounted to an ebike rocket ship. If things go belly up there is a good chance a davega can survive some road rash. The phone will be funked. Id rather my phone not be getting rained on, plus the touch screen does not really work when its all wet. And as @BenjaminF mention cool features not found in other apps. Possible street cred! 
3 Likes
Are you by chance using a Spintend?
They MUST be running the custom firmware in order to be safe and show correct voltages
3 Likes
Yepp exactly thts the issue i made the naming of tge firmware is little misleading
So now i need to update the bootloader and install the custom fw tht should solce my problem
Ill do this probably tmwr and let you know if it worked out
2 Likes
Metr Pro CAN is now available from shop.davega.eu so you can grab one along with a DAVEGA X and make use of the MeGA features (currently there are not many but more are planned).
The price is slightly more expensive than if you buy from metr.at but you save 12 EUR on shipping.
13 Likes
Quick question I have Davega but unfortunately ordered metr pro unity thinking well it’s the same thing pretty much and easy install just swap out ble module. I assume that Davega is only going to work with Can version? 
That’s unfortunately correct. We rely on the VESC to forward the communication between the two and that currently only works for one UART and one CAN device, not for two UART devices.
1 Like
@janpom are you in the process of re-stocking?
Seems no matter which option combo I choose, the davega x kit and pre-assembled are both out of stock on the website.
1 Like
Not still but rather again. 
I got a big order from a business customer and that cleared my stock. ETA for more units is 2 weeks. 
5 Likes
Congrats. It’s a great product
3 Likes
BTW, good news Kaly users. I just picked up a bunch of these babies.
I’ll be getting most of them black anodized.
4 Likes
Can I purchase one in red if I pay extra? Or even keep one RAW Aluminum if no red. I have a Kaly Deck I’m doing a DIY on.
No red, sorry. I can definitely give you a raw one though.
2 Likes
Mark me down for a raw Kaly baseplate. Let me know if a deposit is needed. 
3 Likes
Firmware v4.08
Most important updates:
- ENNOID BMS support
- cell voltages display for up to 24S
- range ramp up (range temporarily projected from lifetime data after session reset)
- demo below
- lifetime max speed can be reset
CHANGELOG entry:
- ENNOID BMS support
- cell voltages display for up to 24S
- range ramp up (range temporarily projected from lifetime data after session reset)
- lifetime max speed can be reset
- battery capacity settings: step changed from 1 mAh to 50 mAh
- session mAh in/out changed to Ah and values above 9999 mAh can now be displayed
- fix: odometer not saved upon stopping
- fix: fixes/improvements to the landscape mode view
- fix: updating config from Metr CAN with empty wifi settings
- various other minor fixes
Range ramp up demo (if you haven’t seen it yet):
I’ve been holding the v4.08 in the RC state for an embarrassingly long time. The main reason is that I wanted to test the ENNOID BMS support. I received a sample BMS unit from Kevin to use for testing but I haven’t been able to get the communication working. After double-checking I’m not doing anything wrong with Kevin we concluded the CAN circuitry must be faulty on this particular unit. So I shipped it back and now I’m waiting for another one.
Unfortunately the ENNOID support hasn’t received the testing that would be appropriate for a stable release. There are probably a few loose ends that will need addressing later. I don’t want to be holding this release back in RC anymore though so it’s coming out as is.
9 Likes