There is no specific list, but I would suggest something like: Car states StandardMetrics.ms_v_env_awake StandardMetrics.ms_v_env_on Battery StandardMetrics.ms_v_bat_soc StandardMetrics.ms_v_bat_temp StandardMetrics.ms_v_bat_range_est StandardMetrics.ms_v_bat_range_ideal Charging StandardMetrics.ms_v_charge_current StandardMetrics.ms_v_charge_voltage StandardMetrics.ms_v_charge_pilot StandardMetrics.ms_v_charge_inprogress StandardMetrics.ms_v_charge_mode StandardMetrics.ms_v_charge_state StandardMetrics.ms_v_charge_substate Vehicle StandardMetrics.ms_v_vin StandardMetrics.ms_v_type StandardMetrics.ms_v_env_gear StandardMetrics.ms_v_env_handbrake StandardMetrics.ms_v_pos_speed StandardMetrics.ms_v_door_chargeport StandardMetrics.ms_v_inv_temp StandardMetrics.ms_v_mot_temp Nice to have are the StandardMetrics.ms_v_door_* metrics. Regards, Mark
On 30 May 2023, at 5:11 AM, Solterra <solterra@kezarnet.com> wrote:
Hello,
I'm trying to determine what the minimally viable vehicle module is? I'm implemented a handful of polling PIDs (SoC, Voltage, Current, Speed, Temperature, Odometer, etc.), and am starting to consider vehicle states and transitions.
I'm wondering what I should target as a set good enough for a pull request to the main.
Thank you _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev