Page 1 of 1

Limitations of Parameter Entries

Posted: Thu Jul 31, 2025 11:28 am
by modellfan
Is there any limitation of parameter entries in place? On the first look scrolling through the ESP8266 repo I didn't find any. I added arround 30 additional to Zombie VCU and it got realy laggy .

Re: Limitations of Parameter Entries

Posted: Thu Jul 31, 2025 12:13 pm
by tom91
The main limits are based on how the web interfaces populate, as it is all dynamically driven. This requires pushing alot of information each time it updates or connects.

Re: Limitations of Parameter Entries

Posted: Thu Jul 31, 2025 2:23 pm
by modellfan
So ESP32 CAN Interface should solve the problem, right?

Re: Limitations of Parameter Entries

Posted: Thu Jul 31, 2025 2:34 pm
by tom91
No thats literally the same, force all param info down a communication pipe line. When requesting spot values it will pull the same info as the esp8266.

Re: Limitations of Parameter Entries

Posted: Thu Jul 31, 2025 4:32 pm
by johu
The CAN is different as it only downloads the parameter descriptions once then only polls the values. That said over wifi always the full json blob is transferred but that's usually not the bottleneck

Re: Limitations of Parameter Entries

Posted: Fri Aug 01, 2025 8:01 am
by modellfan
I added all this parameters. I know, it is a lot of characters I could save. I would realy like to have the categories also for values :-) .

Code: Select all

    VALUE_ENTRY(mlb_chr_DC_Max_ChargePower, "W", 2111)                             \
    VALUE_ENTRY(mlb_chr_DC_Max_ChargeVoltage, "V", 2112)                           \
    VALUE_ENTRY(mlb_chr_DC_Actual_Current, "A", 2113)                              \
    VALUE_ENTRY(mlb_chr_DC_Max_ChargeCurrent, "A", 2114)                           \
    VALUE_ENTRY(mlb_chr_DC_Min_ChargeVoltage, "V", 2115)                           \
    VALUE_ENTRY(mlb_chr_DC_Min_ChargeCurrent, "A", 2116)                           \
    VALUE_ENTRY(mlb_chr_Status_Grid, "dig", 2117)                                  \
    VALUE_ENTRY(mlb_chr_ChargeManagerMode, "dig", 2118)                            \
    VALUE_ENTRY(mlb_chr_ChargerRequestingHV, "dig", 2119)                          \
    VALUE_ENTRY(mlb_chr_ChargerErrorStatus, "dig", 2120)                           \
    VALUE_ENTRY(mlb_chr_PlugStatus, "dig", 2121)                                   \
    VALUE_ENTRY(mlb_chr_LoadRequest, "dig", 2122)                                  \
    VALUE_ENTRY(mlb_chr_ChargerState, "dig", 2123)                                 \
    VALUE_ENTRY(mlb_chr_Charger_AC_Volt_RMS, "V", 2124)                            \
    VALUE_ENTRY(mlb_chr_Charger_VoltageOut_HV, "V", 2125)                          \
    VALUE_ENTRY(mlb_chr_Charger_CurrentOut_HV, "A", 2126)                          \
    VALUE_ENTRY(mlb_chr_Charger_Temperature, "°C", 2127)                           \
    VALUE_ENTRY(mlb_chr_ChargerSystemState, "dig", 2128)                           \
    VALUE_ENTRY(mlb_chr_Status_LED, "dig", 2129)                                   \
    VALUE_ENTRY(mlb_chr_MaxCurrent_AC, "A", 2130)                                  \
    VALUE_ENTRY(mlb_chr_LockRequest, "dig", 2131)                                  \
    VALUE_ENTRY(mlb_chr_Charger_Ready, "dig", 2132)                                \
    VALUE_ENTRY(mlb_chr_ChargerTemp_Reduction, "dig", 2133)                        \
    VALUE_ENTRY(mlb_chr_ChargerCurrent_Reduction, "dig", 2134)                     \
    VALUE_ENTRY(mlb_chr_SocketTemp_Reduction, "dig", 2135)                         \
    VALUE_ENTRY(mlb_chr_MaxChargerOutput, "W", 2136)                               \
    VALUE_ENTRY(mlb_chr_CableCurrentLimit, "A", 2137)                              \
    VALUE_ENTRY(mlb_chr_ControlPilotStatus, "dig", 2138)                           \
    VALUE_ENTRY(mlb_chr_LockState, "dig", 2139)                                    \
    VALUE_ENTRY(mlb_chr_ChargerWarning, "dig", 2140)                               \
    VALUE_ENTRY(mlb_chr_ChargerFault, "dig", 2141)                                 \
    VALUE_ENTRY(mlb_chr_OutputVolts, "V", 2142)                                    \
                                                                                   \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_SOC, "%", 0, 100, 50, 153)               \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_SOC_Target, "%", 0, 100, 100, 154)       \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_BMSMinVolt, "V", 0, 1000, 300, 155)       \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_IDCSetpnt, "A", 0, 200, 10, 156)          \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_HVDCSetpnt, "V", 0, 1000, 400, 157)       \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_BMSBattCellSum, "V", 0, 1000, 350, 158)   \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_BMSMaxVolt, "V", 0, 1000, 450, 159)       \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_BMS_Cell_H_Temp, "°C", -40, 100, 25, 160) \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_BMS_Cell_L_Temp, "°C", -40, 100, 20, 161) \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_BMS_Cell_H_mV, "mV", 0, 5000, 4200, 162)  \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_BMS_Cell_L_mV, "mV", 0, 5000, 3000, 163)  \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_Activation_Crg, "dig", 0, 1, 0, 164)      \
    PARAM_ENTRY(CAT_MLB_SIM, mlb_chr_sim_Lock, "dig", 0, 1, 0, 165)
The strange thing is, is that it is not just slow or not working at all. Some times after reset I am able to see all parameters and then get the red connection error. Sometimes it just don't load at all. This unstable undetermined behaviuor is weired and no good sign for a computer system.

Re: Limitations of Parameter Entries

Posted: Fri Aug 01, 2025 11:10 am
by modellfan
With CAN interface it runs smooth.