Nubo wrote:Got the unit yesterday, and it seems to work fine with the app.Nubo wrote: I was just about to also. But... "shipping speed: 17 to 28 business days"?
update: I figured having a switch wasn't as big a deal as waiting a month and a half for the slow boat from "Jeff-Store". So I'll be trying out this one:
http://www.amazon.com/dp/B00HVV60HI/ref ... 00_TE_item" onclick="window.open(this.href);return false;. Fulfilled by Amazon. It's already shipped.
On those rare occasions when I don't drive the car for more than 3 days, I can just disconnect it.
- This is one of the "tall" units, which means it sticks down noticeably into the footwell area. I haven't bumped it and don't think it will be a problem for me, but if someone were to drive who is unaware of the dongle, it could potentially be a problem. Might be better to run this off a cable, or get one of the low-profile units.
- Still not sure of the power consumption. The device does get noticeably warm. It was even warm this morning, though not as much as when I was actively using it with the car on. Warmer than I'd expect for dissipating less than one watt, so I'm going to have to measure the current drain and see if the .75 watts specification is accurate.
All in all I'm leaning towards a low-profile unit with a switch as being the better solution here.
But this gets me playing. It may well be that I only want the info occasionally or for taking extended range trips.
The location is not particularly useful since as soon as your rotate the tires the location is off. There is a way to register the sensors so they are in the proper location again but this probably more work than it's worth.Nubo wrote:Anyone know in which order the tire pressures are given?
My Western brain wants to say
But, not sure. I guess I can play with the tire pressures to find out.
After using a telnet program to send an "at sp 6" command to force the protocol, the app seems to be working again. Not quite sure how it was locked into a different protocol, but that got it to work once anyway.adspguy wrote:So I have a 2012 SL and have been using a wifi obd2 adaptor for about a year now. I've been using my iPhone4S to talk to it with just a telnet program. With this setup I've just been sending at commands and dumping from group 79b, later sending the responses to my computer to process, graph etc. Been working fine.
I bought the app and tried to get it to work. The first time, the car was not on (oops) but it was charging. I've been able to dump 79b data like this before so I tried it. I thought, well sure, it shouldn't work no problem. Next I turn the car on (while still charging) and low and behold the program fires up. I get data and it looks fine. Life is good I think.
Then I try it again later, with the car unplugged and turned on, ready to drive. The app responds that it can talk to the obd2 but not the leaf. Weird. So I delete the app, reset the obd2 (unplug and plug in) and reload the app. Still the same message. Hmmm I say, lets delete the app, reset the obd2 again and try to talk to it with my old telnet method. I can talk to it, it responds to at commands but the sequence I previously used ends up with "Searching...." and I end up with no response. Very wierd. So I try various resets (atz, atd, atppffoff etc...) still no love.
So now I have nothing working. Does the app set something that stays even after a poweron reset that I can turn off that might make it work again. Are there any other resets that I just don't know about? Anyone have any ideas? Is this the behavior that you are trying to reproduce to debug the app on a 2012?
No, sorry. Only portrait mode.BrainDonor wrote:Does LEAFStat support iPhone landscape orientation?
I just use screen capture before disconnecting. That works fine for me.Nubo wrote:Suggestion for the app:
I find that I'd like to be able to look at the display at some point after the drive, to see the last-obtained values.
Unfortunately, being off the OBDII network, the app immediately throws up the big white dialog to tell you you're not connected. This obscures most of the display. "Retry" makes it go away briefly, but doing this repeatedly is awkward.
It would help to have an option to dismiss the dialog and be able to view the previous display values, with perhaps an "offline" status indicator and "reconnect" button. Alternatively (don't know if this is possible), if the offline dialogue box had some transparency, one could see the old values without any further programming changes.
I might have a long trip coming up soon, and I don't do Android so I'm very happy to have this app. Thanks!