|
Weston@PPE
|
 |
« Reply #30 on: May 07, 2012, 05:58:16 pm » |
|
We've run some tests today, the iPad 3 is not as slow as you guys are making it out to be. And, after our changes in the last release, the data you see on the dashboards should be closer to real-time than any previous version on any device -- since we've revamped the logging engine. Here are the results:
iPad 3 with OBDLink WiFi
Main Menu: 21 FPS 13 OFPS
Landscape Tuxedo: 4 FPS 12 OFPS
Portrait Tuxedo: 5 FPS 12 OFPS
Boost: 14 FPS 13 OFPS
Default Portrait: 5 FPS 12 OFPS
iPhone 4 with OBDLink WiFi
Main Menu: 30 FPS 13 OFPS
Landscape Tuxedo: 8 FPS 7 OFPS
Portrait Tuxedo: 9 FPS 7 OFPS
Boost: 20 FPS 10 OFPS
Default Portrait: 11 FPS 12 OFPS
iPhone 4S with OBDLink WiFi
Main Menu: 51 FPS 13 OFPS
Landscape Tuxedo: 13 FPS 12 OFPS
Portrait Tuxedo: 13 FPS 12 OFPS
Boost: 30 FPS 12 OFPS
Default Portrait: 16 FPS 12 OFPS
iPad 3 with CLK Devices WiFi
Main Menu: 21 FPS 12 OFPS
Landscape Tuxedo: 4 FPS 7 OFPS
Portrait Tuxedo: 5 FPS 7 OFPS
Boost: 14 FPS 10 OFPS
FPS is referring to the dashboard update speed, in frames per second. OFPS is the OBD-II data logging frames per second, which indicates how far "out-of-date" the data being drawn to the dashboards is. Note we did this test using the CAN protocol, older vehicles will respond slower just because they're older.
As you can see, using a cheaper eBay WiFi device is actually slower than a big-brand device, by an average of 5 OBD-II frames per second (~40%). The OFPS will directly influence how smooth the log looks when you play it back -- especially on a computer with ScanXL. With some skins is possible to get 15FPS or higher on the iPad 3, which is easily usable and looks smooth. If you turn off persistent PIDs, many dashboards can get an OFPS of 24 or more with the OBDLink WiFi (this test has persistent PIDs turned on).
Also, the average OFPS before this latest release was 4 or 5, on most all devices. The latest update does speed things up quite a bit, and greatly reduces the gauge lag even if the dashboard refresh rate isn't any faster.
Even at the worst case of 4 FPS and 7 OFPS, thats (1000 / 4) + (1000 / 7), which is roughly a 350ms delay maximum that the iPad 3 could be behind the vehicle. The last version would have had maybe 4 FPS and 4 OFPS (on a good day), giving a delay of 500ms or more.
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #31 on: May 07, 2012, 06:26:28 pm » |
|
Note to users that don't want to parse the numbers, but want it to work faster:
Turn off Persistent PIDs in the settings.
Then download and install the "boost" dashboard.
|
|
|
|
|
Logged
|
|
|
|
|
RennGent
|
|
« Reply #32 on: May 08, 2012, 05:45:12 am » |
|
I've been using the update since it was released on my iPad 3 and have done a 2 hour drive and a 30 minute drive with it, here are my observations. Using the GoPoint BT1 I did not get a single noticeable connection drop during either trip. Using the default tuxedo skin it was responsive and, while not exactly smooth, the update time was acceptable and usable while driving. I'm going to try the boost skin mentioned above and see how it goes though.
The only issue I have to report is I couldn't load a picture from the library on the vehicle setup screen, seems to glitch out and not bring up the photo library screen. Performance wise I've found it to be wwhat I was looking for.
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #33 on: May 08, 2012, 07:44:04 am » |
|
Thank you for the report Renn. We'll get a fix out for the picture glitch.
|
|
|
|
|
Logged
|
|
|
|
|
awilbourn
|
|
« Reply #34 on: May 09, 2012, 05:29:53 pm » |
|
I have the same setup for a bluetooth reader and the software. I found it was working, but on occasion it would not respond to my touching the screen. So I still think there is an issue. I am using the base install, no other skin/dashboard being used.
I will keep playing with it, but thought I would chime in.
|
|
|
|
|
Logged
|
|
|
|
|
Weston@PPE
|
|
« Reply #35 on: May 09, 2012, 05:56:33 pm » |
|
What were you trying to touch exactly? We can look into any specific problem areas if you can point us to them.
|
|
|
|
|
Logged
|
|
|
|
|
DiMattia
|
|
« Reply #36 on: May 22, 2012, 06:21:15 am » |
|
I did not read all of this threads post yet but dash command is not working on my iPad 1 either, HP/TQ #'s say N/A and does not work, really makes me mad because I bought a GoPoing GL1, DashCommand, & a iPad Car Mount all to use in my 98 VW Jetta VR6 and I can not use my darn iPad!  |
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #37 on: May 22, 2012, 08:39:41 am » |
|
Hi DiMattia. I replied to your other thread. We'll help you solve this.
|
|
|
|
|
Logged
|
|
|
|
|
DiMattia
|
|
« Reply #38 on: May 22, 2012, 02:44:34 pm » |
|
Thanks
|
|
|
|
|
Logged
|
|
|
|
|
awilbourn
|
|
« Reply #39 on: May 22, 2012, 05:26:14 pm » |
|
What were you trying to touch exactly? We can look into any specific problem areas if you can point us to them.
The different buttons at the bottom when the dashboard is up. Seems like a threading issue from my days of programming. With multi-core processor can see how threads are not in sync. I guess I need to try this App on my iPhone, or iPad 2, but much prefer the new iPad. |
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #40 on: May 23, 2012, 11:42:12 am » |
|
If you have an iPhone or iPad 2 I would suggest trying it out, just to see if you have the same issues.
Without seeing you actually touch the buttons myself it's hard for me to say what is going on.
On the other hand some users have actually posted videos of themselves touching stuff and it not working. So if you post a video I'll take a look.
|
|
|
|
|
Logged
|
|
|
|
|
