[Ovmsdev] Nissan Leaf updates
mark at webb-johnson.net
Wed May 2 07:57:17 HKT 2018
Really strange. I guess the Europeans have a different numbering scheme and don’t have model years?
Gary had this for US cars (produced in Japan):
was seen, apparently on one of the Test-Drive LEAFs.
JN1 = Nissan Vehicle, Produced in Japan
AZ0C = model, engine, etc. does not seem to make sense, conflicting with existing models.
A = Engine Type, but A is already assigned
Z0 = Model: Z-series ... is this the LEAF designation, or perhaps, Unassigned, or Pre-Production?
C = Body type is what?
P = Safety type: Passive restraints. Maybe no airbags in this particular LEAF?
5 = Checksum digit, for checking VIN validity
B = Model Year 2011 (2010 ... is A, B, ...)
T = Manufacturing Plant: Tochigi or Oppama (both Japan)
000082 = Serial number, normally in "completed" order.
Wikipedia says <https://en.wikipedia.org/wiki/Vehicle_identification_number> "One consistent element of the VIS is the 10th digit, which is required worldwide to encode the model year of the vehicle. Besides the three letters that are not allowed in the VIN itself (I, O and Q), the letters U and Z and the digit 0 are not used for the model year code. The year code is the model year for the vehicle.”, but that is obviously wrong for the VINs you show.
So, maybe only possible on US cars… Seems strange. I wonder how the dealers know which model year.
> On 1 May 2018, at 11:20 PM, ovms <ovms at topphemmelig.no> wrote:
> Here is a list of EU-versions of different years, all are my/previous cars,
> SJNFAAZE0U6046184 2016
> SJNFAAZE0U6033068 2015
> SJNFAAZE0U6020423 2014
> On 2018-05-01 15:59, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
> Suggestion: Can the model year of the car be determined from the VIN? We do that for a few other of the models.
> Regards, Mark.
> On 30 Apr 2018, at 5:54 PM, Tom Parker <tom at carrott.org <mailto:tom at carrott.org>> wrote:
> I've replied, copying here for completeness:
> Hi meiniac,
> I'm very sorry I haven't updated the Leaf parts of the OVMS manual. 2016 Leafs are supported with some configuration. It looks like you might have a 30kWh battery which, in theory, is also supported but you're probably the first to test it. I have a 2016 24kWh Leaf and everything works for me (almost).
> Set the configuration option xnl.modelyear to 2016 to enable 2016 compatible remote commands:
> config set xnl modelyear 2016
> However you also have to unplug the TCU if fitted or it will override the OVMS module's messages. In previous model year cars, this hasn't caused any problems but in the 2016 model year they routed the handsfree microphone through the TCU and the microphone stops working when you unplug the TCU. You assistance in this matter is appreciated as I haven't had time to try to override the TCU using the OVMS.
> Set the configuration option xnl.maxGids to the appropriate maximum gids for a 30kWh Leaf:
> config set xnl maxGids 356
> I have observed the SOC flapping with a v2 module in a 30kWh Leaf but we never got to the bottom of the problem, we found that the module was sending the SOC correctly and the server was not always sending the correct value to the app. It's possible the server doesn't like SOC above 100% and it will go away when you configure the maxGids correctly?
> The xt_set_error_handler_callback error is because your esp_idf is out of date. You need the latest from https://github.com/openvehicles/esp-idf.git <https://github.com/openvehicles/esp-idf.git>
> Please join us on the mailing list if you can (I don't know why you would get permission denied).
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
> _______________________________________________ OvmsDev mailing list OvmsDev at lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev