rreitz
Posts: 8
Joined: Thu Jul 24, 2014 6:44 pm
Delivery Date: 02 Jul 2014
Leaf Number: 302622

Re: iOS Version of Leaf Spy development discussion

Tue Dec 01, 2015 6:50 am

I have an iPhone 6s. I saw folks with an iPhone 6 had success with the LELink ODB-II. So far, the LELink does not connect to the iPhone 6s.

Turbo3
Gold Member
Posts: 1778
Joined: Mon Jul 19, 2010 8:34 pm
Delivery Date: 12 May 2011
Leaf Number: 002191
Location: San Jose, CA

Re: iOS Version of Leaf Spy development discussion

Tue Dec 01, 2015 10:24 am

rreitz wrote:I have an iPhone 6s. I saw folks with an iPhone 6 had success with the LELink ODB-II. So far, the LELink does not connect to the iPhone 6s.

Are you running LeafSpy Pro version 1.1.5? LELInk will not show up as a Bluetooth device in Wireless connections.

rreitz
Posts: 8
Joined: Thu Jul 24, 2014 6:44 pm
Delivery Date: 02 Jul 2014
Leaf Number: 302622

Re: iOS Version of Leaf Spy development discussion

Tue Dec 01, 2015 11:42 am

I'm running Leaf Spy Pro 1.1.5 en on an iPhone 6s. The LELink OBD-II (www.outdoor-apps.com) I received from Amazon yesterday will not connect with Leaf Spy. No name appears in the connection box. I see "WiFi NC", the name of my MacBook Pro and other Bluetooth LE
devices I walk by. I've never seen "OBDBLE" in the connection box.

Flyct
Posts: 186
Joined: Tue Nov 03, 2015 12:04 am
Delivery Date: 02 Dec 2015
Leaf Number: 307113
Location: Bradenton, Florida, US

Re: iOS Version of Leaf Spy development discussion

Tue Dec 01, 2015 1:27 pm

rreitz,

See if this helps.

On my iPhone 6 (not plus) this is how I set it up.

I went to the Device / Bluetooth screen on my iPhone and made sure Bluetooth was turned on.

I plugged the LELink adapter into the car and hit CAR power button

On my iPhone, under OTHER DEVICES I saw OBDBLE after a while. I don't remember if I selected it or not, but I think I did the first time.

After a minute or so OBDBLE showed as Connected

Then I opened LEAFSpy Pro v1.1.5

About 30 seconds later the connection box on the lower right turned green, started to show activity and I was connected and could view live data.

The System selection on the LeafSpy tools screen does NOT show the OBDBLE, but it shows my home network SSID Just ignore that.

From then on I don't need to do anything. I just get in the car, bring up LeafSpy Pro v1.1.5 and it connects.

----------------------------------------

If it doesn't work, my daughter has a 6+ that I can try.
2015 Pearl White Leaf SL with Premium (Bose) package
2015 Lexus RX450h Hybrid SUV
2016 Ford F-150 Super Crew
Blissfully Retired and loving it!

Turbo3
Gold Member
Posts: 1778
Joined: Mon Jul 19, 2010 8:34 pm
Delivery Date: 12 May 2011
Leaf Number: 002191
Location: San Jose, CA

Re: iOS Version of Leaf Spy development discussion

Tue Dec 01, 2015 4:26 pm

Here is an app that can use to test out the LELink to be sure it is working if LeafSpy is unable to talk to it.

https://itunes.apple.com/us/app/lightblue-explorer-bluetooth/id557428110?mt=8

To do this test the Leaf does not need to be on. Just the Red LED on the LELink.

1. Start the app and after a while you should see OBDBLE under "Peripherals Nearby"

2 Tap OBDBLE and it will read information from the LELink and take you to a new page

Image Image

3. Scroll down to "Characteristic 1" and tap it. You should now go to a new screen where we can read and write hex data.

Image

4. Tap the blue "Listen for Notification' label and it should change to "Stop listening". Responses from the LELink will now show up below the "Read again" label. It probably has "0x41" there right now.

5. Tap the "Write new value" label and you will go to a new screen with a hex keyboard.

Image Image

6. Enter in "41545A0D0A" This is "ATZ" followed by CR & LF in hex. Before pressing "Done" watch the top of the LELink for the Green/Yellow LEDs to flash. Now press "Done" and the LEDs should flash.

Image

7. Just under "Read again" label should be the data the LELink sent back in hex as follows:
"0D0D454C4D3332372076312E350D0D3E" which is the "ELM327 v1.5" response

8. You can press the string under "Write new value" to send it again and again to watch the LEDs flash.

Image Image

If this works then your LELink is good and there is something I need to fix.

Here is what the log should look like. You can see the ATZ command being echoed back. If you forgot to select "Listen for Notifications" you will not get the data back.

Code: Select all

17:31:56.226 — Starting search for nearby peripherals
17:31:56.227 — CentralManager not on, delaying scan
17:31:56.230 — Bluetooth State: Powered On
17:31:56.279 — Starting search for nearby peripherals
17:31:56.359 — Starting search for nearby peripherals
17:32:05.398 — Discovered nearby peripheral: OBDBLE (RSSI: -52)
17:32:07.167 — Connecting to nearby peripheral: OBDBLE
17:32:07.489 — Connected to nearby peripheral: OBDBLE
17:32:08.220 — Characteristic (2A23) read: <00000000 00000000>
17:32:08.280 — Characteristic (2A24) read: <4d6f6465 6c204e75 6d626572>
17:32:08.340 — Characteristic (2A25) read: <53657269 616c204e 756d6265 72>
17:32:08.352 — Discovered nearby peripheral: (null) (RSSI: -98)
17:32:08.400 — Characteristic (2A26) read: <4669726d 77617265 20526576 6973696f 6e>
17:32:08.460 — Characteristic (2A27) read: <48617264 77617265 20526576 6973696f 6e>
17:32:08.520 — Characteristic (2A28) read: <536f6674 77617265 20526576 6973696f 6e>
17:32:08.610 — Characteristic (2A29) read: <4d616e75 66616374 75726572 204e616d 65>
17:32:08.670 — Characteristic (2A2A) read: <fe006578 70657269 6d656e74 616c>
17:32:08.730 — Characteristic (2A50) read: <010d0000 001001>
17:32:10.670 — Stopping search for nearby peripherals
17:32:13.379 — Characteristic (FFE1) read: <01>
17:33:22.269 — Starting search for nearby peripherals
17:34:05.350 — Characteristic (FFE1) wrote new value: <41545a0d 0a>
17:34:05.403 — Characteristic (FFE1) notified: <41>
17:34:05.405 — Characteristic (FFE1) notified: <545a0d>
17:34:05.471 — Characteristic (FFE1) notified: <41>
17:34:06.183 — Characteristic (FFE1) notified: <0d0d454c 4d333237 2076312e 350d0d>
17:34:06.212 — Characteristic (FFE1) notified: <3e>
17:34:37.940 — Characteristic (FFE1) re-wrote value: <41545a0d 0a>
17:34:37.985 — Characteristic (FFE1) notified: <41>
17:34:37.986 — Characteristic (FFE1) notified: <545a0d>
17:34:38.043 — Characteristic (FFE1) notified: <41>
17:34:38.764 — Characteristic (FFE1) notified: <0d0d454c 4d333237 2076312e 350d>
17:34:38.793 — Characteristic (FFE1) notified: <0d3e>
17:34:48.787 — Discovered nearby peripheral: (null) (RSSI: -100)

rreitz
Posts: 8
Joined: Thu Jul 24, 2014 6:44 pm
Delivery Date: 02 Jul 2014
Leaf Number: 302622

Re: iOS Version of Leaf Spy development discussion

Tue Dec 01, 2015 7:48 pm

Wow, lotsa help.

From "Flyct", I can see "OBDDLE" in the Setting->Bluetooth on my iPhone. However, the LeafSpy connection box did not turn green.

From "Turbo3", I installed LightBlue. I didn't have to go into the garage to see the OBDBLE peripheral.
Steps 1-5 worked, but on step 6 (OK, I went into the garage for this step) I did not see green/yellow lights flash.
Under "Read Again", all that appears is "0x41". Repeating step 6, no green/yellow lights and '0x41' as the response.

Here is the log generated:
20:17:40.784 — Starting search for nearby peripherals
20:17:40.784 — CentralManager not on, delaying scan
20:17:40.786 — Bluetooth State: Powered On
20:17:40.818 — Starting search for nearby peripherals
20:17:40.864 — Starting search for nearby peripherals
20:17:47.122 — Starting search for nearby peripherals
20:17:54.561 — Discovered nearby peripheral: zippy (RSSI: -47)
20:18:43.205 — Discovered nearby peripheral: Apple TV (RSSI: -101)
20:18:48.656 — Stopping search for nearby peripherals
20:20:25.825 — Starting search for nearby peripherals
20:20:25.861 — Discovered nearby peripheral: Randy’s iPad (RSSI: -49)
20:20:25.871 — Discovered nearby peripheral: OBDBLE (RSSI: -76)
20:20:26.561 — Starting search for nearby peripherals
20:20:29.902 — Connecting to nearby peripheral: OBDBLE
20:20:30.011 — Connected to nearby peripheral: OBDBLE
20:20:30.802 — Characteristic (2A23) read: <00000000 00000000>
20:20:30.862 — Characteristic (2A24) read: <4d6f6465 6c204e75 6d626572>
20:20:30.982 — Characteristic (2A25) read: <53657269 616c204e 756d6265 72>
20:20:31.072 — Characteristic (2A26) read: <4669726d 77617265 20526576 6973696f 6e>
20:20:31.132 — Characteristic (2A27) read: <48617264 77617265 20526576 6973696f 6e>
20:20:31.192 — Characteristic (2A28) read: <536f6674 77617265 20526576 6973696f 6e>
20:20:31.282 — Characteristic (2A29) read: <4d616e75 66616374 75726572 204e616d 65>
20:20:31.403 — Characteristic (2A2A) read: <fe006578 70657269 6d656e74 616c>
20:20:31.462 — Characteristic (2A50) read: <010d0000 001001>
20:20:33.640 — Stopping search for nearby peripherals
20:20:52.162 — Characteristic (FFE1) read: <41>
20:22:09.799 — Characteristic (FFE1) wrote new value: <41545a0d 0a>
20:22:09.921 — Characteristic (FFE1) notified: <41>
20:23:34.571 — Characteristic (FFE1) wrote new value: <41545a0d 0a>
20:23:34.675 — Characteristic (FFE1) notified: <41>
20:23:43.674 — Characteristic (FFE1) re-wrote value: <41545a0d 0a>
20:23:43.796 — Characteristic (FFE1) notified: <41>
20:24:11.128 — Characteristic (FFE1) notified: <41>
20:24:15.431 — Characteristic (FFE1) re-wrote value: <41545a0d 0a>
20:24:15.537 — Characteristic (FFE1) notified: <41>
20:24:19.491 — Characteristic (FFE1) re-wrote value: <41545a0d 0a>
20:24:19.587 — Characteristic (FFE1) notified: <41>
20:27:09.092 — Characteristic (FFE1) read: <41>
20:27:23.649 — Disconnected from nearby peripheral OBDBLE with error: The connection has timed out unexpectedly.
20:37:22.954 — Starting search for nearby peripherals
20:41:01.062 — Stopping search for nearby peripherals
20:41:16.433 — Starting search for nearby peripherals
20:41:17.172 — Starting search for nearby peripherals

I'm going to assume I have a bad LELink. I'll return it to Amazon for a replacement.

Thanks,
Randy

Turbo3
Gold Member
Posts: 1778
Joined: Mon Jul 19, 2010 8:34 pm
Delivery Date: 12 May 2011
Leaf Number: 002191
Location: San Jose, CA

Re: iOS Version of Leaf Spy development discussion

Tue Dec 01, 2015 8:27 pm

If you were in the San Jose area I would want to swap it with a good one so I could see what the problem is. Normally a bad solder joint. I have seen it before on other OBDII adapters.

Turbo3
Gold Member
Posts: 1778
Joined: Mon Jul 19, 2010 8:34 pm
Delivery Date: 12 May 2011
Leaf Number: 002191
Location: San Jose, CA

Re: iOS Version of Leaf Spy development discussion

Mon Dec 07, 2015 6:07 pm

I have fixed a lot of connection and crash problems in v 1.1.5 when using the LELink so the next release should be much better.

Received a Viecar 4.0 OBDII Bluetooth 4.0 LE adapter today. After making a few changes the iOS version will now support it. However, when I went to test it on an Android device I found that for Android it reverts back to just a standard Bluetooth OBDII adapter requiring pairing. So to me it is not as good as the LELInk with is Bluetooth LE for both iOS and Android.

I have a Kiwi 3 on order which I hope has a lot of functions as it is very expensive. We will see.

Turbo3
Gold Member
Posts: 1778
Joined: Mon Jul 19, 2010 8:34 pm
Delivery Date: 12 May 2011
Leaf Number: 002191
Location: San Jose, CA

Re: iOS Version of Leaf Spy development discussion

Tue Dec 08, 2015 11:40 am

Test version 1.1.6 is now available to all testers. Should fix LELink connection problems and crashes.

Also includes support for the dual mode Viecar 4.0 Bluetooth 4.0 OBDII adapter. It is different from the LELink which operates as a Bluetooth 4.0 LE adapter for both iOS and Android. The Viecar operates in Bluetooth 4.0 LE mode for iOS but in Bluetooth 2.0 mode when connecting to an Android device.

For LeafSpy the LELink is best as Bluetooth 4.0 LE is the easiest to connect to as there is no pairing or port number in LeafSpy to handle and it works for both iOS and Android the same.

If however you also have Android devices and Android apps that only support Bluetooth 2.0 then the Viecar would be your best option at this time.

rreitz
Posts: 8
Joined: Thu Jul 24, 2014 6:44 pm
Delivery Date: 02 Jul 2014
Leaf Number: 302622

Re: iOS Version of Leaf Spy development discussion

Wed Dec 09, 2015 6:52 am

I received a replacement for the defective LELink. The replacement LELink works as advertised. No setup required. The iPhone connects automatically when LeafSpy is running.

LeafSpy 1.1.6, iPhone 6s iOS 9.2

Return to “LEAF CANBus”