View Single Post
  #10   Spotlight this post!  
Unread 06-02-2010, 07:52
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,748
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Slow Dashboard Images SOLUTION

Ah. I misunderstood what size you wanted. The JPEG image size is the string size coming from the TCP read on the attachment. To find the VI, you can Ctl-F, change to text, click the checkbox at the bottom to include vi.lib VIs, and search for 1.0.0.0 or something similar.

As for the difference at 5%. I saw a pretty strong correlation to the 16K number using LV. Joe Hershberger saw less of a correlation using C++. I believe his numbers started dropping earlier, but didn't drop as fast. He and I were also running with a DS update which is still being tested and is not released. So, I'd pay less attention to the exact numbers and more to the fact that the image size, and thus the camera resolution and compression has a pretty big impact on frame rate back to the dashboard. A bigger impact than I'd thought.

Greg McKaskle
Attached Thumbnails
Click image for larger version

Name:	TCP JPG.png
Views:	106
Size:	40.5 KB
ID:	8529  

Last edited by Greg McKaskle : 06-02-2010 at 07:56.
Reply With Quote