Leaf Spy and Leaf Spy Pro

My Nissan Leaf Forum

Help Support My Nissan Leaf Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
I am working on improvements to LeafLogger to display efficiencies of segments of your trip in different colors. Here is an example:
leaflogger_efficiency_screenshot.png

Green is the most efficient, red is the least.
It is still a work in progress but almost ready to share. If you would like a login go to:
http://leaflogger.com/Login.html" onclick="window.open(this.href);return false;
 
I am trying to figure out the protocol for connection. I have the ELM 327 Bluetooth Obdii Obd2 Diagnostic Scanner, Elm327 Wireless OBD 2, and am using an Android HTC Sprint Phone which is no longer commissioned as a telephone, now dedicated to getting LeafSpy to work.

I have not yet been able to connect with Bluetooth (BT). My phone will connect in BT mode to the car and to a BT earpiece. Thus I know that BT is working. The Obdii dongle when plugged in shows a red LED, indicating it is powered up. I have tried all of the channels setting them from Ch 1 to the "secure channel". Here is how I do it:

Vehicle is on
Android phone is on
Android BT is on
Dongle is plugged in and shows the red LED
I activate LeafSpy and go to the menu
I select the connect to Obdii and wait 90 seconds
When no pairing results, I exit Leafspy via the menu
I unplug and then replug in the Obdii dongle
I then open Leafspy and select the Port menu icon, and scroll to the next port (2, 3, 4, etc)
With each succeeding BT Port setting I repeat the above process

I would appreciate any advice in this matter.

Regards to the Group,
Dave
 
CWO4Mann said:
I am trying to figure out the protocol for connection. I have the ELM 327 Bluetooth Obdii Obd2 Diagnostic Scanner, Elm327 Wireless OBD 2, and am using an Android HTC Sprint Phone which is no longer commissioned as a telephone, now dedicated to getting LeafSpy to work.

I have not yet been able to connect with Bluetooth (BT). My phone will connect in BT mode to the car and to a BT earpiece. Thus I know that BT is working. The Obdii dongle when plugged in shows a red LED, indicating it is powered up. I have tried all of the channels setting them from Ch 1 to the "secure channel". Here is how I do it:

Vehicle is on
Android phone is on
Android BT is on
Dongle is plugged in and shows the red LED
I activate LeafSpy and go to the menu
I select the connect to Obdii and wait 90 seconds
When no pairing results, I exit Leafspy via the menu
I unplug and then replug in the Obdii dongle
I then open Leafspy and select the Port menu icon, and scroll to the next port (2, 3, 4, etc)
With each succeeding BT Port setting I repeat the above process

I would appreciate any advice in this matter.

Regards to the Group,
Dave
First I would recommend you update to the latest version of Leaf Spy which has only three port options (1,16 and secure).

Then start up LeafSpy and go to Settings and select Port 16 which is the most likely port available since you have your phone linked to your Leaf which normal uses Port 1. For this test also go to the bottom of the Settings menu and check the "Trace ELM" checkbox. Then exit and restart the app to start the Logging. When you restart the word "Logging" will be flashing bottom center.

Make sure your Leaf is On.

Go to Select OBDII and select your OBDII adapter from the list which should also include the Leaf and earpiece in the listing. When asked enter your pairing code if you have not already done so which is normally "1234" and press done. (I assume you already paired the OBDII adapter with your Phone before you ever tried to run LeafSpy or it would never have been listed as a choice.)

If after 90 seconds it does not connect just go to Settings and select the next Port. No need to unplug OBDII adapter or exit app. After selecting the next port go to Select OBDII and select the OBDII adapter again. Wait 90 seconds if it fails repeat with last Port choice.

If none of these connect send me the ELM trace located on the SD card in folder LEAF_BT_CAN/DEBUG with a name like TRC_yymmddhhmm.txt. Where y,m,d,h,m are year month day hour minute. Use email address listed on the About screen.
 
Thanks for the info, Turbo. I did all of that and THEN remembered to pair my device (in the settings area of the HTC Phone). Sure enough it needed to be paired by the phone. So, everything works now!

I have noticed that when going to the Google Market to retrieve the Leaf Spy Pro version, the market app keeps advising that it has crashed. I have the handset within 5 feet of the main WiFi server so it is getting a full signal.

I'll get back to you as soon as I can upload the Pro version.

I can pair the phone to my netbook which is in the luggage compartment (used for some ham radio applications - and active 24/7). Wondering if I can dump the data directly to the netbook via BT?

Regards,

Dave
 
kevinleaf said:
I am working on improvements to LeafLogger to display efficiencies of segments of your trip in different colors. Here is an example:
Green is the most efficient, red is the least.
It is still a work in progress but almost ready to share. If you would like a login go to:
http://leaflogger.com/Login.html" onclick="window.open(this.href);return false;
That's really nice!

One minor problem: the javascript on your login form makes it difficult to use on the Android browser.

Also, the dropbox uploader displays the JSON
Code:
{"error": "Origin does not match any app domain"}
 
Could you add a TRIP meter that actually reads miles traveled from the ECU (not GPS)??

for example right now you have that bottom right hand window where I set my m/kwh and it shows estimate remaining range?

split that in half top and bottom where the bottom I "SET" a mileage and have it count DOWN to zero using ECU miles not GPS miles (ie actual rolling miles)

this would be very very handy for those of us who push the limits of the battery. My commute is 53 miles I could input 53 miles and watch it count down to 0 as I also watch the battery power and m/kwh estimate count down and get a good sense of whether I am going to make it or not and plan accordingly (detour for some power or realizes I can detour on a side trip since I have enough power etc...)
 
jlv: the site in general doesn't work so well on mobile platforms. I hope to fix that soon. Really it is meant for viewing on a larger screen. Also the dropbox functionality was never finished so ignore that for now.

I had started a separate thread on LeafLogger:
http://www.mynissanleaf.com/viewtopic.php?f=44&t=14646" onclick="window.open(this.href);return false;
I will put updates in there as to not hijack this thread.
 
nerys said:
Could you add a TRIP meter that actually reads miles traveled from the ECU (not GPS)??

for example right now you have that bottom right hand window where I set my m/kwh and it shows estimate remaining range?

split that in half top and bottom where the bottom I "SET" a mileage and have it count DOWN to zero using ECU miles not GPS miles (ie actual rolling miles)

this would be very very handy for those of us who push the limits of the battery. My commute is 53 miles I could input 53 miles and watch it count down to 0 as I also watch the battery power and m/kwh estimate count down and get a good sense of whether I am going to make it or not and plan accordingly (detour for some power or realizes I can detour on a side trip since I have enough power etc...)
Here is what the display would look like with this trip countdown counter. I split left and right not top and bottom to be able to use the largest font. It is also the easiest to implement. You do a long tap on the field to enable/disable the countdown counter. The value to use will be entered on the Settings menu.

The countdown counter is the first number and will be in integer format followed by a down arrows followed by the normal distance to event range. The odometer reading is only available in km units so whole units for countdown makes more sense plus there is not the room in the available space for two three digit numbers with tenth units each.

fkdEV7.png
 
nerys said:
Nice! And this uses the cars data for distance ie like odometer not gps?
Yes, odometer changes are used.

For now I have added the ability to increase or decrease the font size of those two numbers since larger screens can take a larger font. When you are in freeze mode pressing the + or - button changes the font size. I may not keep this in the final version if I can find a way to automate a large font when appropriate.
 
Turbo3 said:
nerys said:
Could you add a TRIP meter that actually reads miles traveled from the ECU (not GPS)??

for example right now you have that bottom right hand window where I set my m/kwh and it shows estimate remaining range?

split that in half top and bottom where the bottom I "SET" a mileage and have it count DOWN to zero using ECU miles not GPS miles (ie actual rolling miles)

this would be very very handy for those of us who push the limits of the battery. My commute is 53 miles I could input 53 miles and watch it count down to 0 as I also watch the battery power and m/kwh estimate count down and get a good sense of whether I am going to make it or not and plan accordingly (detour for some power or realizes I can detour on a side trip since I have enough power etc...)
Here is what the display would look like with this trip countdown counter. I split left and right not top and bottom to be able to use the largest font. It is also the easiest to implement. You do a long tap on the field to enable/disable the countdown counter. The value to use will be entered on the Settings menu.

The countdown counter is the first number and will be in integer format followed by a down arrows followed by the normal distance to event range. The odometer reading is only available in km units so whole units for countdown makes more sense plus there is not the room in the available space for two three digit numbers with tenth units each.

fkdEV7.png

Once again, great incorporation of suggestions to increase the utility of LeafSpy. Thanks.

The LeafSpy app probably now provides more data than Nissan has provided with the Consult tool
to the dealers and also with their in-house Leaf development tool. If Nissan engineering wasn't
supplementing their in-house tools with the LeafSpy, it would be very short-sighted on their part.
 
They have TWO STN adapters available. MX and LX

is there anything in the MX model that is useful to us leaf owners? the LX model is $30 cheaper :)
 
I've noticed what seems to be a necessity to close and restart the Pro Ap. Also, a "connection refused" message frequently. I've reset everything and made sure my handset shows that it is paired with the OBDII dongle. The handset shows "paired but not connected" which status I think is correct untill after the Pro ap connects tto my dongle. The system was working as expected until yesterday when with no other warning returned the "connnection refused" message.

Q: shall I enable "debug and logging" and then post results herein, or send you the file?

Q: how likely is it that my dongle has stuck or broken? It shows the red LED when plugged in, but the connection LED and data LED now do not light (showing that it has not connected"

Q: my iPhone connects with the car ok, I assume that is not an issue since the BT connection of the iPhone is with the car, not with the dongle, while the connection between Android HTC phone and dongle is a direct handshake between those two devices, exclusive of the car BT. Gist of my Q is can the two BT connection interfere with each other?

Q: i've retried connecting using the channels shown on the Pro Ap, there are three: 1, 16, and secure. All return the "connection refused" message. Are these the only channels available in Pro?

This is a good challenge for me and I am working to sort it out.

The Android OS can be run on the Linux platform. I am preparing a trial run of your Ap on a laptop with Linux and Android running on top of the Linux OS. I'll proably start a new thread for that -- if it works.

My gratitude for your hard work!
 
AH HA! The dongle was making an intermittent connection! Pinche cabron! I figured I needed to look for possible mechanical problems after eliminating the electronic glitches. Seems the Leaf's obdii socket plastic POS enclosure was slightly cracked, thus making a solid holding connection impossible. Hijo de Puta! After all that other trouble shooting. So, I used a bead of Gorilla Glue with a rubber band to secure the broken plastic. I opine that somehow the socket was damaged previously by roughly jamming in the plug during testing. Lesson learned: check for the least obvious. I have an extension cord on order for the permanent install of the LeafPro system. Now to track down why the Ap believes the 32mb sd card is full when it isn't. More reporting later.

Reminded me of a time when we had a batch of rocket arming cables delivered. Seems the manufacturer had a color-blind tech since the blue-green wire (arm for release) was switched for the green-blue wire (ignite rocket engine). A PFC maintenance specialist discovered that when she started to load 2.5" rocket pod and she ran a self-test from the cockpit. That was exciting. Our tax money at work, but I digress.
 
I get bt errors a couple times a day. The solution is to turn off bt and turn on bt in android. Then it connects fine. No idea why it does it.
 
Since my Blink SD card died I have often been leaving LEAF Spy Pro running and the LEAF in Ready foot on brake single button push (although not truly in Ready to drive because EVSE is plugged in and LEAF is charging). Did that so the 12 volt source would be active to power inverter that is maintaining Note 3 battery.
I thought in that mode the DC to DC converter would stay active until I turned the vehicle OFF.

But today I discovered that once the LEAF timer hit the 80% charge level it was set for and the LEAF stopped charging the DC to DC dropped out.
In essence the infamous double button push ON mode.
It sagged the 12 volt battery all the way down to 10.48 volts before it turned the DC to DC back on and started charging the 12 volt back up at 14.4 volts.

Is that how it is supposed to work?
Not what I was expecting.
Certainly a good way to kill the 12 volt battery.
 
Turbo3 said:
jlv said:
Turbo3 said:
Yes, I broke the Wh counter on that version. Fixed in next release.
It also always displays 00:04:39 at the top.
Yes, same bug. Basically the trip never starts so the counter does not get reset and start counting the next trip and the Wh never changes.
Any timeline on the next build (even for testers)? I'd love to get this back!
 
Back
Top