With the inclusion of fix #170, "Fix for 0% SOH on 30KWh models with Nissan BMS update" in the new 3.2.001 firmware, the user guide needs updating. I do not seem to have the right to do that, so can someone do it for me? It concerns the "OVMS v3 Advanced User Guide", Chapter "NL Nissan Leaf", section "Configuration": - The former [2016] section title should be updated to [2016-2017] - The section about the 30 kwh models should be taken out of the [2016-2017] section and into its own section (there are 2015 30 kwh models, I own one...) - The new section about the 30kwh models needs an extra command to also update the "newCarAh" setting to 79 (from 66) Full new text: [2011-2015 models] To enable remote commands, either Unplug any CARWINGS, Nissan Connection or TCU units or on Generation 1 Cars, wire the RC3 to TCU pin 11 (see MyNissanLeaf post) [2016-2017 models] Set the model year as follows config set xnl modelyear 2016 or config set xnl modelyear 2017 [30 kwh models] For models with a 30 kwh battery pack, set the capacity manually as follows config set xnl maxGids 356 config set xnl newCarAh 79
Hi Anko, I will update it. Rob --- On Sun, 03 Feb 2019 02:24:11 +0000 Anko Hanse <mailto:anko_hanse@hotmail.com> wrote ---- With the inclusion of fix #170, "Fix for 0% SOH on 30KWh models with Nissan BMS update" in the new 3.2.001 firmware, the user guide needs updating. I do not seem to have the right to do that, so can someone do it for me? It concerns the "OVMS v3 Advanced User Guide", Chapter "NL Nissan Leaf", section "Configuration": - The former [2016] section title should be updated to [2016-2017] - The section about the 30 kwh models should be taken out of the [2016-2017] section and into its own section (there are 2015 30 kwh models, I own one…) - The new section about the 30kwh models needs an extra command to also update the "newCarAh" setting to 79 (from 66) Full new text: [2011-2015 models] To enable remote commands, either Unplug any CARWINGS, Nissan Connection or TCU units or on Generation 1 Cars, wire the RC3 to TCU pin 11 (see MyNissanLeaf post) [2016-2017 models] Set the model year as follows config set xnl modelyear 2016 or config set xnl modelyear 2017 [30 kwh models] For models with a 30 kwh battery pack, set the capacity manually as follows config set xnl maxGids 356 config set xnl newCarAh 79 _______________________________________________ OvmsDev mailing list mailto:OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Hi Anko, I have updated the document. On a slightly different, if OVMS was more plug-and-play it would be easier for users to setup and be more attractive to less technical users. Do you think it is technically possible to use the VIN number to set the year and capacity related parameters automatically? https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/180 https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/181 I have VIN numbers for an early 2011 Leaf and a 2014 Leaf if that helps. Rob --- On Mon, 04 Feb 2019 13:33:42 +0000 Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe@evergreen-consulting.co.uk> wrote ---- Hi Anko, I will update it. Rob --- On Sun, 03 Feb 2019 02:24:11 +0000 Anko Hanse <mailto:anko_hanse@hotmail.com> wrote ---- With the inclusion of fix #170, "Fix for 0% SOH on 30KWh models with Nissan BMS update" in the new 3.2.001 firmware, the user guide needs updating. I do not seem to have the right to do that, so can someone do it for me? It concerns the "OVMS v3 Advanced User Guide", Chapter "NL Nissan Leaf", section "Configuration": - The former [2016] section title should be updated to [2016-2017] - The section about the 30 kwh models should be taken out of the [2016-2017] section and into its own section (there are 2015 30 kwh models, I own one…) - The new section about the 30kwh models needs an extra command to also update the "newCarAh" setting to 79 (from 66) Full new text: [2011-2015 models] To enable remote commands, either Unplug any CARWINGS, Nissan Connection or TCU units or on Generation 1 Cars, wire the RC3 to TCU pin 11 (see MyNissanLeaf post) [2016-2017 models] Set the model year as follows config set xnl modelyear 2016 or config set xnl modelyear 2017 [30 kwh models] For models with a 30 kwh battery pack, set the capacity manually as follows config set xnl maxGids 356 config set xnl newCarAh 79 _______________________________________________ OvmsDev mailing list mailto:OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
On Mon, Feb 04, 2019 at 01:55:59PM +0000, Robert Sharpe (Electric Vehicle Consultant) wrote:
On a slightly different, if OVMS was more plug-and-play it would be easier for users to setup and be more attractive to less technical users.
Do you think it is technically possible to use the VIN number to set the year and capacity related parameters automatically?
Although only 24kWh was available before some point in time (2015?), both 24 and 30kWh size options were later available in the same model year. It seems likely that we will also need to deal with that situation again in future, when the 60kWh pack is available becomes an available option (alongside the 40kWh).
https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/180 https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/181
I have VIN numbers for an early 2011 Leaf and a 2014 Leaf if that helps.
At least some LEAF VINs, like my own, don't use the 10th character for a year (or if they do, they use a different decoding table). For example, decoding my UK-built 24kWh 2015 VIN yields: Characters 1-3 "World manufacturer identifier": SJ = UK N = Nissan Characters 4-9 "Vehicle descriptor section": FAAZ = LEAF? E = Electric? 0 = check digit? Characters 10-17 "Vehicle identifier section": U = year? 6 = plant code? nnnnnn = serial The year-letter code table for North America does not give a value for 'U' (it jumps from 'T'=2026 to 'V'=2027). However, there may be easier (and perhaps more reliable) ways to determine what we need to know from other CAN signals. For example, issue 170 (cited earlier in this thread) is relevant: Turns out the PollReply for the battery info is 41 bytes long on these models instead of the 39 bytes we have previously seen on the 24KWh models. So that gives us an automatic way to tell the difference between 24kWh and 30kWh pack sizes. For me, a major difficulty in knowing that such differences exist, and confidently writing code to deal with them, is that I generally only have access to logs from my own car to experiment with. Having access to an annotated collection of logs from other model years with different battery pack sizes, regional differences and other options would be very helpful in checking ideas and code. I would certainly be willing to contribute my own logs to such an effort.
Looking on github, I just noticed that I hadn't posted the separate changes for the LEAF BMS (disentangled from the wider issue of generalizing IncomingPollReply). Sorry about that. Rather than clutter up the previous messy branch, I made a new pull request: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/199
Merged this one. Regards, Mark.
On 5 Feb 2019, at 3:50 AM, Robin O'Leary <ovmsdev@caederus.org> wrote:
Looking on github, I just noticed that I hadn't posted the separate changes for the LEAF BMS (disentangled from the wider issue of generalizing IncomingPollReply). Sorry about that. Rather than clutter up the previous messy branch, I made a new pull request:
https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/199 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
participants (4)
-
Anko Hanse -
Mark Webb-Johnson -
Robert Sharpe (Electric Vehicle Consultant) -
Robin O'Leary