The SOH did come back the next time I started the car. Thanks. On Tue, Feb 5, 2019 at 12:23 PM, ovmsdev-request@lists.openvehicles.com<ovmsdev-request@lists.openvehicles.com> wrote: Send OvmsDev mailing list submissions to ovmsdev@lists.openvehicles.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.openvehicles.com/mailman/listinfo/ovmsdev or, via email, send a message with subject or body 'help' to ovmsdev-request@lists.openvehicles.com You can reach the person managing the list at ovmsdev-owner@lists.openvehicles.com When replying, please edit your Subject line so it is more specific than "Re: Contents of OvmsDev digest..." Today's Topics: 1. LEAF SOH (was: OvmsDev Digest, Vol 85, Issue 5) (Robin O'Leary) 2. Re: LEAF SOH (Robin O'Leary) 3. Re: Collecting information on the Fiat 500e (Guenther Huck) 4. Re: Collecting information on the Fiat 500e (Guenther Huck) ---------------------------------------------------------------------- Message: 1 Date: Tue, 5 Feb 2019 10:29:04 +0000 From: Robin O'Leary <ovmsdev@caederus.org> To: OVMS Developers <ovmsdev@lists.openvehicles.com> Subject: [Ovmsdev] LEAF SOH (was: OvmsDev Digest, Vol 85, Issue 5) Message-ID: <20190205102904.GB19577@mail.ro.nu> Content-Type: text/plain; charset=iso-8859-1 On Tue, Feb 05, 2019 at 02:46:40AM +0000, Dean MacGregor wrote:
With the new firmware version the SOH reading doesn't work but it used to.? That's in both the 'Vehicle Info' and 'metrics list' command. I have a 2015 Nissan Leaf.?
Is this with the car switched off? Can you check with the the car ready to drive? Most other values we display are passively read whenever the can bus is active, but to get more detailed values from the battery (v.b.soh, xnl.v.b.hx, v.b.cac), we need to send an active poll request. We don't want to do this when the car is asleep, since it causes modules to wake up and consume power. We did previously get v.b.soh from a passive message 0x5b3, which is a 7-bit value (0--100%) available whenever the car is awake. The active poll to 0x7bb.6101 gives better resolution (~11 bits). We had a similar situation with the SOC, where I think we have a better solution. We now report both low- and high-resolution values as separate LEAF-specific metrics: the simple percentage in xnl.v.b.soc.instrument and the high-resolution value scaled as a proportion of the "new car" value as xnl.v.b.soc.newcar. By default, the standard metric v.b.soc reports the value from xnl.v.b.soc.instrument; there is a config option if you want it to report xnl.v.b.soc.newcar instead. I think it would be better if we followed the same pattern with SOH. ------------------------------ Message: 2 Date: Tue, 5 Feb 2019 13:16:47 +0000 From: Robin O'Leary <ovmsdev@caederus.org> To: OVMS Developers <ovmsdev@lists.openvehicles.com> Subject: Re: [Ovmsdev] LEAF SOH Message-ID: <20190205131647.GD19577@mail.ro.nu> Content-Type: text/plain; charset=us-ascii On Tue, Feb 05, 2019 at 10:29:04AM +0000, Robin O'Leary wrote:
... We did previously get v.b.soh from a passive message 0x5b3, which is a 7-bit value (0--100%) available whenever the car is awake. The active poll to 0x7bb.6101 gives better resolution (~11 bits).
We had a similar situation with the SOC, where I think we have a better solution. We now report both low- and high-resolution values as separate LEAF-specific metrics: the simple percentage in xnl.v.b.soc.instrument and the high-resolution value scaled as a proportion of the "new car" value as xnl.v.b.soc.newcar. By default, the standard metric v.b.soc reports the value from xnl.v.b.soc.instrument; there is a config option if you want it to report xnl.v.b.soc.newcar instead.
I think it would be better if we followed the same pattern with SOH.
This is implemented in: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/200 Report SOH from passive 0x5b3 in private metric "xnl.v.b.soh.instrument". Report SOH from active 0x7bb.6101 in private metric "xnl.v.b.soh.newcar". Standard metric "v.b.soh" copies from "xnl.v.b.soh.instrument" by default, or from "xnl.v.b.soh.newcar" if config option "xnl.soh.newcar" is set to "true". ------------------------------ Message: 3 Date: Tue, 5 Feb 2019 18:06:40 +0100 From: "Guenther Huck" <privat@guentherhuck.at> To: "OVMS Developers" <ovmsdev@lists.openvehicles.com> Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e Message-ID: <3DF31B4F6313452380B2A0C536D4CC8B@GuentherPCHP> Content-Type: text/plain; charset="utf-8" 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 From: Mark Webb-Johnson Sent: Saturday, June 30, 2018 3:52 PM To: OVMS Developers Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e I?ve had a user in Australia contact me about this recently. It seems there is some activity on Fiat forums, with people discussing this? I am told the factory app is non-renewable after 3 years, and many cars are being exported out of USA. This user is a Fiat and Alfa technician, so has quite some knowledge of the cars. Regards, Mark. On 30 Jun 2018, at 6:21 AM, Jason Perkins <perkins.jason@gmail.com> wrote: I had trouble with the Arduinos I'd gotten, they seemed to garble the 2nd CAN whenever the baud rate was set correctly. I only got a single day to play with it before the telematics was cut off on our roomates 2014 :( Another local friend just got a 2015, don't know if his telematics work or not though. -J On Fri, Jun 29, 2018 at 3:36 PM, Guenther Huck <privat@guentherhuck.at> wrote: Is here anybody working on Fiat 500e can bus sniffing? (Maybe perkins.jason) I have also some sniffing done and send you file for arduino. This works for SOC. Maybe we can share information? greetings Guenther _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev -- Jason Perkins 313 355 0085 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev -------------------------------------------------------------------------------- _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev