Any tips, ideas, or recommendations on how to get data off the can bus for the 2019 Leaf Plus (60kw)? I've followed all the instructions in the OVMS docs and here's what I've tried:
- enabled edge firmware
- enabled the can buses (tried both listen and active - can can1 start listen 500000) https://pasteboard.co/J0vrinHk.png
- enabled the SD card logging and started it (can log start vfs crtd /sd/can.crtd) https://pasteboard.co/J0vs7oS.png
- tried the Network Streaming when SD card file was empty (can log start tcpserver discard gvret-b :23) in conjunction with Savvycan
https://pasteboard.co/J0vrLbM.png
https://pasteboard.co/J0vsiGa.png
I've tried all the methods above when the Leaf is off, when it's in stanby, and when it's powered all the way up ready to drive. Nothing makes any difference. In each instance I've opened doors, locked doors, drove it a few feet, etc. (all activities that generate can data). Nothing. The log file is empty. Savvycan never shows anything in the log window. The web console will show savvycan connecting to it at 192.168.4.1 but the connection doesn't last very long before it disconnects.
Does the Leaf have a different baud rate or bus speed? Something isn't lining up and I can't figure it out.
I also tried my OVMS unit on my wife's 2017 Honda Pilot and was able to successfully get some data from that. Just not the 2019 Leaf.
Wish this forum would allow me to post the screenshots I took of each of the above steps so you could see exactly what I'm seeing.
Any suggestions or ideas I can try?
Thanks in advance,
What cable are you using?
Using a console (usb terminal) connection, or ssh, both can1 and can2 should be 500000 so:
can can1 start active 500000
can can2 start active 500000
can log start monitor crtd
log level verbose canlog-monitor
log monitor yes
and you should see frames on the monitor. If that is working, you can stop logging on the monitor, and try the other approaches.
Thanks for the response. The only cable is the one going from OVMS into the OBDII port of the Leaf. (https://pasteboard.co/J0KsnC5.jpg) Connections are secure and OVMS is powered and communicating via WIFI. SD card is inserted but no CAN data is visible from the network or on the SD card despite log monitoring enabled.
You wrote you were able to get data from a Honda. I would not expect that to work with the Leaf cable, so I assume you're using the wrong cable.
You need … https://docs.openvehicles.com/en/latest/components/vehicle_nissanleaf/do... …
→ this cable: 1779000 Nissan Leaf OBD-II to DB9 Data Cable for OVMS
https://www.fasttech.com/p/1779000
Regards,
Michael
That's the exact cable I ordered from fasttech. But I do have a 2019 Leaf (60kw) so I don't know if it's wired different. https://pasteboard.co/J1xRQIC.jpg
And, here's the cable itself. Looks like the same one from the photo unless they sent me the wrong one:
https://pasteboard.co/J1xSbXY.jpg
https://pasteboard.co/J1xSr1h.png
Can you show us the output of:
can can1 status
can can2 status
Perhaps run it once, wait 30 seconds, then run again. That should tell us if any data is being received at all.
A few other comments:
* If you are logging to the monitor, you need to make sure you have log level to verbose/debug.
* If you are logging to vfs (sdcard) note that the log file will show 0 bytes and not the actual messages logged, until the log session is closed.
* Your cable is correct (the NL identifier on the cable).
Make sure everything was running and logging correctly. Here are the screenshots:
can1 status: https://pasteboard.co/J1DZILx.png
can1 status after 30 sec: https://pasteboard.co/J1E07Gx.png
can 2 status: https://pasteboard.co/J1E0hzX.png
can2 status after 30 sec: https://pasteboard.co/J1E0riU.png
And the Leaf was powered on, in park, while these commands were issued. During the 30 seconds I even did things like lock/unlock the doors, open the doors, turn lights on/off, etc. but it doesn't look like anything is coming through at all. I'm just wondering if perhaps the 2019 60kw Leaf OBD II port has different wiring than previous versions thereby resulting in zero data from the CAN.
That is very strange. Zero CAN bus data.
Can you check the pinouts on the cable? Make sure they match, and have continuity:
J1962-M / DB9-F Signal
4 - 3 Chassis/Power GND
6 - 5 CAN-H (ALTERNATE CAN)
14 - 4 CAN-L (ALTERNATE CAN)
13 - 7 CAN-H (primary CAN)
12 - 2 CAN-L (primary CAN)
16 - 9 +12V Vehicle Power
I pulled out the multimeter and verified that the above-mentioned pinout is indeed accurate--they all match up. I wonder if Nissan did something to the Leaf to block CAN access in the 60kw version.
I followed the link in our documentation… https://docs.openvehicles.com/en/latest/components/vehicle_nissanleaf/docs/index.html#models-ze1
…to https://mynissanleaf.com/viewtopic.php?f=44&t=4131&start=500
…where the assumption seems to be the new Leaf now only reacts to diagnostic requests on the OBD port.
Maybe you should try sending some OBD query, e.g. the odometer query mentioned there.
Regards,
Michael
That was it. So apparently the Leaf (since MY 2018) only reacts to commands issued and doesn't dump any CAN data unless correctly requested (active polling) when the vehicle is ON. This makes it very difficult to do anything with the Leaf via the OBDII when it's in an idle state. I'm suspecting you would have to wire directly into the CANbus to accomplish any remote service commands while the vehicle is idle.
Anyway, thanks everyone above for all the tips and suggestions. I have a lot of detective work to do on this thing like decoding the query results.
The same problem, I'm experiencing...
Leaf 40kWh, 2018, using the "NL" cable,
If I follow all above commands, and lastly issue the command
I receive this:
E (28358983) mcp2515: AsynchronousInterruptHandler: error while sending frame. msgId 0x743
E (28358983) can: can2: intr=10 rxpkt=0 txpkt=1 errflags=0x80150080 rxerr=0 txerr=135 rxovr=0 txovr=0 txdelay=0 wdgreset=0 errreset=0
W (28358983) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
E (28358983) canlog-monitor: 1586419400.682635 2CER Error intr=10 rxpkt=0 txpkt=1 errflags=0x80150080 rxerr=0 txerr=135 rxovr=0 txovr=0 txdelay=0 wdgreset=0 errreset=0
E (28358983) can: can2: intr=10 rxpkt=0 txpkt=1 errflags=0x80151080 rxerr=0 txerr=135 rxovr=0 txovr=0 txdelay=0 wdgreset=0 errreset=0
E (28358983) can: can2: intr=11 rxpkt=0 txpkt=1 errflags=0x80150080 rxerr=0 txerr=135 rxovr=0 txovr=0 txdelay=0 wdgreset=0 errreset=0
V (28358983) canlog-monitor: 1586419400.683476 2CER TX_Fail T11 743 02 21 19 ff ff ff ff ff
W (28358983) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
E (28358983) canlog-monitor: 1586419400.683929 2CER Error intr=11 rxpkt=0 txpkt=1 errflags=0x80151080 rxerr=0 txerr=135 rxovr=0 txovr=0 txdelay=0 wdgreset=0 errreset=0
W (28358983) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
W (28358983) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
W (28358983) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
E (28358983) canlog-monitor: 1586419400.684515 2CER Error intr=11 rxpkt=0 txpkt=1 errflags=0x80150080 rxerr=0 txerr=135 rxovr=0 txovr=0 txdelay=0 wdgreset=0 errreset=0
W (28358983) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
W (28358983) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
W (28358983) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
W (28358983) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
W (28358993) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
W (28358993) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
W (28358993) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
W (28358993) mcp2515: can2 EFLG: TX_Err_Passv TX_Err_Warn EWARN
V (28358993) canlog-monitor: 1586419400.693117 2T11 743 02 21 19 ff ff ff ff ff
(No CAN response arrived, of course)
Any suggestions?
Thanks in advance,
Norbert
It looks like you have started can2 in passive mode, and are then trying to transmit. You need to be in 'active' mode to transmit on the bus.
Thank you for the reply.
I think it's in active mode, because
can list says:
can1: Active/500000 dbc none
can2: Active/500000 dbc none
can3: Off/1000000 dbc none
what else can be the problem?
Maybe CAN2 has nothing on it, or the cable pins are faulty? To transmit, the CAN protocol requires at least two active nodes on the bus, as well as 120ohm termination, to operate.
I guess, it's not possible.
My situation is almost the same, which was described by user tntitan586, in this topic.
I also have a 2018 Leaf 40kWh, I'm using the good "NL" cable (this config works fine with my 2014 Leaf24kWh).
So I think, there's no such "wiring" problem.
But I don't know, what else can be the problem.