[Ovmsdev] Collecting information on the Fiat 500e
Mark Webb-Johnson
mark at webb-johnson.net
Fri Feb 15 07:50:00 HKT 2019
Guenther,
Did you load the vehicle module? The ‘vehicle status’ command will show what is running.
Also, the firmware you are using seems to be 3.2.001. I guess you are on ‘main’ ota updates. To get the latest DBC code, you will need to be on ‘edge’.
Best is for you to get a CAN bus dump (crtd format), and send that plus the test dbc to me to verify.
Regards, Mark.
> On 15 Feb 2019, at 2:46 AM, Guenther Huck <privat at guentherhuck.at> wrote:
>
> Hello Mark
>
> Sorry that I have to ask you again:
>
> I loaded the dbc file now and this worked fine.
>
> Then I renamed one of my dbc signal names to v_c_current
>
> After this I reloaded the file and worked fine again. But if I check I do not get any information on v_c_current.
>
> Is there anything more I have to do?
>
> *************
> dbc
> load 500e /sd/dbc/test2.dbc
> Loaded DBC 500e ok
> dbc
> list
> 500e: 6 message(s); 48
> signal(s); 91% coverage
> config set auto vehicle.type
> DBC
> Parameter has been set.
> config set vehicle dbc.can1
> 500e
> Parameter has been set.
> metrics list
> <image[1].png>
> <image[3].png>
> <image[5].png>
> <image[7].png>
>
> Thx’s Guenther
>
> From:
> Mark
> Webb-Johnson <mailto:mark at webb-johnson.net>
>
>
> Sent: Thursday, February 14, 2019 1:58 AM
>
> To: OVMS Developers <mailto:ovmsdev at lists.openvehicles.com>
>
> Subject: Re: [Ovmsdev] Collecting information on the Fiat
> 500e
>
>
> This is what I get:
>
>> OVMS# dbc load guenther /sd/testdbc/test.dbc
>> Error: Failed to load DBC guenther from /sd/testdbc/test.dbc
>> E (71557) dbc-parser: Error in line 267 'syntax error, unexpected T_BA_DEF, expecting T_SEMICOLON or T_INT_VAL', symbol 'BA_DEF_'
>
> Problem is that the BA_* symbols are not currently used or supported.
>
> Removing those, I get:
>
>> OVMS# dbc load guenther /sd/testdbc/test.dbc
>> Loaded DBC guenther ok
>
> We only currently support integer (signed or unsigned) metrics in DBC files, so BA_* not really useful for us. At some point, I will add support (primarily to get string and floating point signals).
>
> Regards, Mark.
>
>> On 14 Feb 2019, at 3:11 AM, Guenther Huck <privat at guentherhuck.at <mailto:privat at guentherhuck.at>> wrote:
>>
>> Hello Mark
>>
>> I tried to load the dbc file (test.dbc) from 500e to OVMS 3 but always get the error message :
>> “Error: Failed to load DBC 500e from /sd/dbc/test.dbc”
>>
>> I can load a example file from leafpowertrain but not file from 500e.
>>
>> Maybe you can help me to find the mistake?
>>
>> Guenther
>>
>> From: Mark Webb-Johnson <mailto:mark at webb-johnson.net>
>> Sent: Tuesday, February 12, 2019 6:12 AM
>> To: OVMS Developers <mailto:ovmsdev at lists.openvehicles.com>
>> Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e
>>
>> Guenther,
>>
>> With the latest code (3.2.001-80-g731c916e or later), you should be able to try this. Instructions are pretty much the same as previously given:
>>
>> Put your DBC file in /store/dbc/<vehicletype>.dbc
>>
>> Load the DBC:
>>
>> ovms# dbc load <vehicletype> /store/dbc/<vehicletype>.dbc
>>
>> (or ‘dbc autoload’ to load all DBC files in that directory)
>>
>> Note: It should be automatically loaded on boot, and you can use ‘dbc list’ to confirm.
>>
>> Configure your vehicle type and assign the DBC to CAN bus #1 for it:
>>
>> config set auto vehicle.type DBC
>> config set vehicle dbc.can1 <vehicletype>
>>
>> Within the DBC, set the signal name the same as the OVMS metric name (you can use periods ‘.’ as separators, or ‘_’ will be converted automatically for you). Connect to the car, and the CAN bus data should start to be processed and metrics updated based on your DBC file. Only integer DBC signals are supported (either signed or unsigned should be ok), but factors and/or offsets can convert these automatically to floats.
>>
>> At the moment, you can only change the DBC on disk (/store/dbc/*.dbc) then reload it. However, it will be locked (as it is used by your OvmsVehicleDBC vehicle) . So you will have to either clear the vehicle module (‘vehicle module’), reload the DBC, then reload the vehicle module (‘vehicle module DBC’). Alternatively, you can simply reboot the OVMS. Later on I will improve on this to support hot-reloading and in-memory modification of live DBC files (via retool).
>>
>> Remember that extended CAN IDs need to have the high bit set in DBC format. So, extended ID 100 is 2147483748 (2^31 + 100).
>>
>> Regards, Mark.
>>
>>> On 11 Feb 2019, at 11:35 AM, Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>> wrote:
>>>
>>> Guenther,
>>>
>>> The code is not finished yet, so no documentation at the moment. I will document it when it is working.
>>>
>>> The overall plan (for a single CAN bus, single DBC, for example) is:
>>>
>>> Put your DBC file in /store/dbc/<vehicletype>.dbc.
>>>
>>> You should now find it automatically loaded on boot. You can use ‘dbc list’ to confirm.
>>>
>>> config set vehicle dbc.can1 <vehicletype>
>>>
>>> Configure your vehicle type as “DBC”.
>>>
>>> The above is close to completion - just waiting for the decode function which I am struggling with (eMail sent to ovmsdev mailing list earlier today).
>>>
>>> The retools system will have facilities to maintain DBC files (in memory) and save them back to disk. It will also use DBC files as its main way of working with messages.
>>>
>>> Regards, Mark.
>>>
>>>> On 11 Feb 2019, at 12:38 AM, Guenther Huck <privat at guentherhuck.at <mailto:privat at guentherhuck.at>> wrote:
>>>>
>>>> Thank you Mark!
>>>>
>>>> But my question was if there is a manual how I can use the dbc file in OVMS 3.
>>>>
>>>> I cannot find a description.
>>>>
>>>> Guenther
>>>>
>>>> From: Mark Webb-Johnson <mailto:mark at webb-johnson.net>
>>>> Sent: Friday, February 08, 2019 12:57 AM
>>>> To: OVMS Developers <mailto:ovmsdev at lists.openvehicles.com>
>>>> Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e
>>>>
>>>> This is quite good:
>>>>
>>>>> http://socialledge.com/sjsu/index.php/DBC_Format <http://socialledge.com/sjsu/index.php/DBC_Format>
>>>> There are a large number of examples here:
>>>>
>>>>> https://github.com/commaai/opendbc <https://github.com/commaai/opendbc>
>>>> (although many are not 100% standards conformant, so will not parse correctly)
>>>>
>>>> Attached is the formal specification.
>>>>
>>>> Regards, Mark.
>>>>
>>>>
>>>>
>>>>> On 8 Feb 2019, at 12:35 AM, Guenther Huck <privat at guentherhuck.at <mailto:privat at guentherhuck.at>> wrote:
>>>>>
>>>>> Is there somewhere in the net a manual how to make a dbc-file impemention?
>>>>>
>>>>> Thx Guenther
>>>>>
>>>>> From: Mark Webb-Johnson <mailto:mark at webb-johnson.net>
>>>>> Sent: Thursday, February 07, 2019 2:44 PM
>>>>> To: OVMS Developers <mailto:ovmsdev at lists.openvehicles.com>
>>>>> Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e
>>>>>
>>>>> This also looks to be a good candidate for a DBC implementation. That way, no coding required, and Gunther can tune and add metrics himself.
>>>>> With the iOS App done, and now in testing, I am back working on DBC and RE tools. Made some progress these last two days (Chinese new year holidays here), and hoping to have something usable this weekend.
>>>>>
>>>>> But, need those crtd can bus dumps to validate it.
>>>>>
>>>>> Regards, Mark
>>>>>
>>>>> On 6 Feb 2019, at 9:12 PM, Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>> wrote:
>>>>>
>>>>>> I think it best to also get a few CAN dumps:
>>>>>>
>>>>>> While car is parked, idle, asleep
>>>>>> While car is parked, but awake
>>>>>> While car is driving
>>>>>>
>>>>>> These should be in CRTD format.
>>>>>>
>>>>>> They will allow us to double-check the actual CAN bus traffic to ensure it matches what is shown in the spreadsheet.
>>>>>>
>>>>>> Regards, Mark.
>>>>>>
>>>>>>> On 6 Feb 2019, at 8:55 PM, Guenther Huck <privat at guentherhuck.at <mailto:privat at guentherhuck.at>> wrote:
>>>>>>>
>>>>>>> Hello Michael
>>>>>>>
>>>>>>> That’s perfect! Ich can send you some more CAN-ID’S. Tell me what is important for the first implementation.
>>>>>>>
>>>>>>> <image[3].png>
>>>>>>>
>>>>>>> <image[7].png>
>>>>>>>
>>>>>>> <image[10].png>
>>>>>>>
>>>>>>> <image[13].png>
>>>>>>>
>>>>>>> <image[16].png>
>>>>>>> From: Michael Balzer <mailto:dexter at expeedo.de>
>>>>>>> Sent: Wednesday, February 06, 2019 12:55 PM
>>>>>>> To: ovmsdev at lists.openvehicles.com <mailto:ovmsdev at lists.openvehicles.com>
>>>>>>> Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e
>>>>>>>
>>>>>>> Günther,
>>>>>>>
>>>>>>> yes, that looks sufficient.
>>>>>>>
>>>>>>> It's always best if an actual vehicle user does the code, but we can provide a first basic implementation to build upon.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Michael
>>>>>>>
>>>>>>>
>>>>>>> Am 05.02.19 um 18:22 schrieb Guenther Huck:
>>>>>>>> Is this ok?
>>>>>>>>
>>>>>>>> <image[2].png>
>>>>>>>>
>>>>>>>> From: Guenther Huck <mailto:privat at guentherhuck.at>
>>>>>>>> Sent: Tuesday, February 05, 2019 6:06 PM
>>>>>>>> To: OVMS Developers <mailto:ovmsdev at lists.openvehicles.com>
>>>>>>>> Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e
>>>>>>>>
>>>>>>>> Hello Mark
>>>>>>>>
>>>>>>>> I have a Fiat 500e and asked if there is anybody who is firm with the CAN Id’s.
>>>>>>>>
>>>>>>>> In the meantime I have some CAN informations for Fiat 500e and can give to you or somebody who is familiar to programm the OVMS for this car.
>>>>>>>> I don’t have enough experiance to programm this. Sorry!
>>>>>>>>
>>>>>>>> What informations to you need to insert this car to your project ?
>>>>>>>>
>>>>>>>> Guenther
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> OvmsDev mailing list
>>>>>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>>>>>>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> OvmsDev mailing list
>>>>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>>>>> _______________________________________________
>>>>>>> OvmsDev mailing list
>>>>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> OvmsDev mailing list
>>>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>>>
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>>
>>>>
>>>>
>>>> This is quite good:
>>>>
>>>> http://socialledge.com/sjsu/index.php/DBC_Format <http://socialledge.com/sjsu/index.php/DBC_Format> <http://socialledge.com/sjsu/index.php/DBC_Format <http://socialledge.com/sjsu/index.php/DBC_Format>>
>>>>
>>>> There are a large number of examples here:
>>>>
>>>> https://github.com/commaai/opendbc <https://github.com/commaai/opendbc> <https://github.com/commaai/opendbc <https://github.com/commaai/opendbc>>
>>>>
>>>> (although many are not 100% standards conformant, so will not parse correctly)
>>>>
>>>> Attached is the formal specification.
>>>>
>>>> Regards, Mark.
>>>>
>>>>
>>>>
>>>> > On 8 Feb 2019, at 12:35 AM, Guenther Huck <privat at guentherhuck.at <mailto:privat at guentherhuck.at>> wrote:
>>>> >
>>>> > Is there somewhere in the net a manual how to make a dbc-file impemention?
>>>> >
>>>> > Thx Guenther
>>>> >
>>>> > From: Mark Webb-Johnson <mailto:mark at webb-johnson.net <mailto:mark at webb-johnson.net>>
>>>> > Sent: Thursday, February 07, 2019 2:44 PM
>>>> > To: OVMS Developers <mailto:ovmsdev at lists.openvehicles.com <mailto:ovmsdev at lists.openvehicles.com>>
>>>> > Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e
>>>> >
>>>> > This also looks to be a good candidate for a DBC implementation. That way, no coding required, and Gunther can tune and add metrics himself.
>>>> > With the iOS App done, and now in testing, I am back working on DBC and RE tools. Made some progress these last two days (Chinese new year holidays here), and hoping to have something usable this weekend.
>>>> >
>>>> > But, need those crtd can bus dumps to validate it.
>>>> >
>>>> > Regards, Mark
>>>> >
>>>> > On 6 Feb 2019, at 9:12 PM, Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net> <mailto:mark at webb-johnson.net <mailto:mark at webb-johnson.net>>> wrote:
>>>> >
>>>> >> I think it best to also get a few CAN dumps:
>>>> >>
>>>> >> While car is parked, idle, asleep
>>>> >> While car is parked, but awake
>>>> >> While car is driving
>>>> >>
>>>> >> These should be in CRTD format.
>>>> >>
>>>> >> They will allow us to double-check the actual CAN bus traffic to ensure it matches what is shown in the spreadsheet.
>>>> >>
>>>> >> Regards, Mark.
>>>> >>
>>>> >>> On 6 Feb 2019, at 8:55 PM, Guenther Huck <privat at guentherhuck.at <mailto:privat at guentherhuck.at> <mailto:privat at guentherhuck.at <mailto:privat at guentherhuck.at>>> wrote:
>>>> >>>
>>>> >>> Hello Michael
>>>> >>>
>>>> >>> That’s perfect! Ich can send you some more CAN-ID’S. Tell me what is important for the first implementation.
>>>> >>>
>>>> >>> <image[3].png>
>>>> >>>
>>>> >>> <image[7].png>
>>>> >>>
>>>> >>> <image[10].png>
>>>> >>>
>>>> >>> <image[13].png>
>>>> >>>
>>>> >>> <image[16].png>
>>>> >>> From: Michael Balzer <mailto:dexter at expeedo.de <mailto:dexter at expeedo.de>>
>>>> >>> Sent: Wednesday, February 06, 2019 12:55 PM
>>>> >>> To: ovmsdev at lists.openvehicles.com <mailto:ovmsdev at lists.openvehicles.com> <mailto:ovmsdev at lists.openvehicles.com <mailto:ovmsdev at lists.openvehicles.com>>
>>>> >>> Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e
>>>> >>>
>>>> >>> Günther,
>>>> >>>
>>>> >>> yes, that looks sufficient.
>>>> >>>
>>>> >>> It's always best if an actual vehicle user does the code, but we can provide a first basic implementation to build upon.
>>>> >>>
>>>> >>> Regards,
>>>> >>> Michael
>>>> >>>
>>>> >>>
>>>> >>> Am 05.02.19 um 18:22 schrieb Guenther Huck:
>>>> >>>> Is this ok?
>>>> >>>>
>>>> >>>> <image[2].png>
>>>> >>>>
>>>> >>>> From: Guenther Huck <mailto:privat at guentherhuck.at <mailto:privat at guentherhuck.at>>
>>>> >>>> Sent: Tuesday, February 05, 2019 6:06 PM
>>>> >>>> To: OVMS Developers <mailto:ovmsdev at lists.openvehicles.com <mailto:ovmsdev at lists.openvehicles.com>>
>>>> >>>> Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e
>>>> >>>>
>>>> >>>> Hello Mark
>>>> >>>>
>>>> >>>> I have a Fiat 500e and asked if there is anybody who is firm with the CAN Id’s.
>>>> >>>>
>>>> >>>> In the meantime I have some CAN informations for Fiat 500e and can give to you or somebody who is familiar to programm the OVMS for this car.
>>>> >>>> I don’t have enough experiance to programm this. Sorry!
>>>> >>>>
>>>> >>>> What informations to you need to insert this car to your project ?
>>>> >>>>
>>>> >>>> Guenther
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> _______________________________________________
>>>> >>>> OvmsDev mailing list
>>>> >>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com> <mailto:OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>>
>>>> >>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> <http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>>
>>>> >>>
>>>> >>>
>>>> >>> --
>>>> >>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>>>> >>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>>>> >>>
>>>> >>> _______________________________________________
>>>> >>> OvmsDev mailing list
>>>> >>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com> <mailto:OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>>
>>>> >>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> <http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>>
>>>> >>> _______________________________________________
>>>> >>> OvmsDev mailing list
>>>> >>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com> <mailto:OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>>
>>>> >>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> <http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>>
>>>> >>
>>>> >>
>>>> >> _______________________________________________
>>>> >> OvmsDev mailing list
>>>> >> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com> <mailto:OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>>
>>>> >> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> <http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>>
>>>> >
>>>> > _______________________________________________
>>>> > OvmsDev mailing list
>>>> > OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>> > http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>> > _______________________________________________
>>>> > OvmsDev mailing list
>>>> > OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>> > http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>>
>>>>
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>
>>>
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>
>>
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>> <test.dbc><leafPowerTrainBus.dbc>_______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20190215/6f7cf3f7/attachment.htm>
More information about the OvmsDev
mailing list