The code originally intended for modifications to the torque requests to be cancelled if ECO button was selected. This is not working for some reason, investigation needed.

Noticed this on my personal car (2015 LEAF with 40kWh battery). The 160kW inverter is limited to 400A, which makes the kW output sit at roughly 145kW. The real 2019+ 62kWh LEAF will push 500A momentarily (180kW and 160kW to wheels).

There might be some CAN message that the inverter sees, so it limits to 400A instead of 500A. Further investigation needed.

Affected? Please list your setup!

EDIT: I am 99% certain that some message is not shaped/contain the same content as on the 2019 e+, that is causing this limit. One log file is all it takes to solve this, so if you know someone with a 62kWh LEAF that wants (AND IS TECHNICALLY CAPABLE) to take logs, let me know.

EDIT2: If you have an e+ and want to help: Please note that the EV-CAN system is not available from the OBD2 port. Nissan moved it away from the OBD2 port with the introduction of the ZE1 LEAF. You will need to first get a proper CAN logging tool (Kvaser, PCAN, Arduino Due, etc.), and connect it somewhere on the EV-CAN line. I have no schematics, but the EV CAN should run quite similar around the car like on the AZE0 LEAF. It is a blue/green twisted pair. Blue is high, green is low. You will have to splice into the wiring to read the CAN, so this is a potential warranty void action. Plug adapters are possible to avoid this, but no such exist to my knowledge, then they have to be custom made. Once you have connected to EV-CAN and can start logging to a file, also start up Leafspy Pro via the OBD2 port so that you can verify that the log you create actually contains 500A 180kW. That's it, quite advanced level of skill required for this unfortunately! Happy CAN-log reading!

EDIT3: We have CAN-logs! They are here: https://github.com/dalathegreat/EV-CANlogs/tree/main/Nissan%20LEAF/62kWh Been experimenting with generating more missing messages towards inverter, but no luck getting 500A yet!

After upgrading and adding CAN-bridge, the GOM will be confused since the returned torque value is lower than actual. This will affect the range estimate negatively, it will be overly optimistic. The instant consumption values will also be slightly inflated.

How should we solve this? If we return actual torque applied fault codes will be set, since the returned values cannot differ much from the requested.

One quick fix we could try is to instead of always returning the demand as request, we could find the limit on how much it is allowed to deviate, and just report back the values on the edge of what is allowed. This would make the situation a bit better, but how much?