DAVEGA X Updates

you have to update it by plugging it in to a computer

3 Likes

I see. Why is that? I can get the other versions just fine via Wi-Fi.

Edit: nvm, found it

5 Likes

Here’s a plug-in that you should be able to modify and use:

from frozen.display import DISPLAY
from frozen.buttons import BUTTON_UP
from frozen.config import load_config, save_config

BATTERY1_MAH = 15000
BATTERY2_MAH = 20000

# hold button-up at start up to trigger the switch
if not BUTTON_UP.value():
    config = load_config()
    if config.battery_mah == BATTERY1_MAH:
        new_battery_mah = BATTERY2_MAH
    else:
        new_battery_mah = BATTERY1_MAH
    DISPLAY.print("switching battery mAh to %i" % new_battery_mah)
    config.battery_mah = new_battery_mah
    save_config(config)

start.py (534 Bytes)

Here’s how to install it:

And here’s a demo of how it works:

Here’s a list of all config options (as of firmware v5.04):

class Config:
    motor_pole_pairs = 7
    motor_temp_sensor = True
    wheel_diameter_mm = 100
    motor_pulley_teeth = 15
    wheel_pulley_teeth = 40
    motor_count = 2
    cells_in_series = 12
    cell_type = "liion"  # liion, lipo, lifepo4
    battery_mah = 12000
    battery_usable_capacity = 0.8
    imperial_units = False
    farenheit = False
    wifi_ssid = ''
    wifi_password = ''
    wifi_connect_timeout_secs = 10
    delay_switch_screen_on_stop_secs = 5
    delay_switch_to_bms_screen_secs = 5
    riding_screen_main = "speed"  # speed, battery_amps, motor_amps, duty, speed_and_motor_amps, speed_and_battery_amps, speed_and_motor_temp, speed_and_esc_temp
    initial_distance_km = 0
    show_unexpected_restarts = False
    show_total_voltage = True
    reset_session_on_charge_up = False
    max_cell_voltage_diff = 0.1
    get_voltage_from_bms = False
    backup_each_km = 10
    range_ramp_up_km = 1.0
    bt_enabled = False
    update_interval_ms = 100
    project_energy = False
    detect_charger = True
    parts = [
        {'name': 'motors', 'new_km': 0},
        {'name': 'wheels', 'new_km': 0},
        {'name': 'belts', 'new_km': 0},
        {'name': 'VESCs', 'new_km': 0},
        {'name': 'battery', 'new_km': 0},
    ]

8 Likes

This is pretty neat, I’ll have to install this on mine while you continue working on the other part of the board config thing

Version 5.04 is not working with vesc 6.0 error msg says that only 3.x - 5.x version of vesc fw are supported, or something…

That’s expected. VESC FW 6.0 hasn’t been around for long. I’ll try to spend some time on it this week.

1 Like

VESC FW v6.0 is now supported by DAVEGA FW v5.05 (currently available as a release candidate).

12 Likes

Hey Jan! I have one of your davegas (close to a couple years of use and love it!

Today it stopped working :frowning:

I have checked all the connections as this has happened before and the connector had simply come out. I checked voltage with a multimeter all the way up the line to the davega. There is a red light on on the davega board but the screens doesn’t turn on… is my davega dead?

Thanks in advance!

1 Like

Hard to tell. Please see if you can reinstall the firmware. Follow the same steps as if updating to v5:
https://davega.eu/install-v5

1 Like

Was able to update to v5 but the screen will still not turn on :confused: anything else I can try?
It also did not turn on when connecting to usb, not sure if it normally does or not through usb, just thought I’d mention it.

1 Like

That sounds like the display has died. I’ll PM you about it.

Is there a default Pin associated with the Davega to get it to connect to an LLT BMS? Its seems like it connects on boot then fails because of wrong pin. I’ve tried several generic and its must be at lest 6 digits. Any help is appreciated, thanks!

1 Like

There’s no pin. It connects over bluetooth. However, the functionality is experimental and may not work correctly with all types of LLT BMSes. If you’re getting an error please send the error screen to me and I’ll see if there’s anything I can do to fix it.

1 Like

It goes through about 6 boot cycles typically trying and once it connects reboots and tries again until that “failed to connect”. Then boots up without bms connection

I see. Is the mac address it’s trying to connect to (70:3e:97:07:ee:85) actually the address of the BMS?

I’m not sure how to find the address

Maybe this can help?

Just open the Xiaoxiang app. It should list the BMS along with its mac address.

1 Like