[Ovmsdev] v2 android clients crashes while v3 is charging

Michael Balzer dexter at expeedo.de
Tue Nov 7 01:37:48 HKT 2017

Am 06.11.2017 um 09:57 schrieb Tom Parker:
>> I also started the work on expanding the structure for ovms_server_v2 in general. It handles peer connections, and the blinking antenna on the App works well
>> now. We should now be able to implement all of that as all the tools are in place. I think that should be my next target - get the ovms_server_v2 100%
>> compatible with OVMS v2. The features/parameters are going to be a challenge.
> Given users can do setup with the usb console with no special hardware, it might not be necessary to bring all the features and parameters to the v2 protocol.
> Instead it might be better to work on the v3 protocol & clients and make the early users use the console? I haven't looked much at what the other vehicle
> modules do with the features and parameters, are there any vehicles that users adjust them so much plugging into the usb is inconvenient?

You'll be able to submit all commands via SMS/text command as well, you just need to use the new syntax.

I've implemented my specific features as config vars now, as they give much more freedom. I think it's good to map at least the old standard parameters and
features to their respective new config variables, i.e. PARAM 5 <=> config modem apn, so clients can continue using these, but that should be sufficient for

>>> I also sent another pull request for a minimal implementation of the charger state related values in the v2 protocol, and some small leaf fixes.
> This pull request ( https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/7 ) is still outstanding

I think deriving the car_chargestate string from the charge flags is not correct. We've currently got…

    OvmsMetricString* ms_v_charge_state;      // charging, topoff, done, preparing, heating, stopped
    OvmsMetricString* ms_v_charge_mode;       // standard, range, performance, storage
    OvmsMetricString* ms_v_charge_substate;   // tba...

…but no longer their numerical equivalences as metrics -- assuming they are no longer necessary. Are they? I.e. do we need the numerical values other than for
the old V2 protocol?

I'd else translate the old codes to their old numerical values just for the "S" msg.


Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

More information about the OvmsDev mailing list