View Single Post
  #6   Spotlight this post!  
Unread 04-03-2007, 12:53
Dave K.'s Avatar
Dave K. Dave K. is offline
Engineer/Mentor
FRC #0930
Team Role: Mentor
 
Join Date: Jan 2007
Rookie Year: 2005
Location: WI
Posts: 91
Dave K. is a splendid one to beholdDave K. is a splendid one to beholdDave K. is a splendid one to beholdDave K. is a splendid one to beholdDave K. is a splendid one to beholdDave K. is a splendid one to beholdDave K. is a splendid one to behold
Re: How to Hook up LCD

Quote:
Originally Posted by magical hands View Post
Hey Dave thanks for sharing that info its really amazing. Thats exactly what I am planning on doing with my Tablet, I don't want to use the IFI's Dashboard. or infact use it but have more features to it example it shows ur gyro angle and GTS tooth count, camera values etc. So Dave would the process be still the same for tablet? the fact that I would have to create a cross platform between what Dashboard recevies and what info shows up on my tablet? and what programming language do you prefer this platform to be made in? V.B? C? C++?
If you search a little here on CD you'll find previous discussions and pointers on dealing with the dashboard data. Included with IFI's dashboard download you should find their documentation on the serial protocol.

In short, each frame consists of 26 bytes, with the start of the frame consisting of 0xff 0xff. There are three frame types, and you need to look at bits within control bytes to figure out which frame of data you've just received.

The 'dashboard' port is simply the raw data from either the RC->OI OR the OI->RC, the shunt near the connector controls which half of the conversation you are monitoring. The bit rate is 19200.

Remember, this is the raw, unchecked data passing between the OI and RC. There are two "checksum" bytes in the middle of the packet that the RC and OI use to determine whether the packet was good or whether it was corrupted.

For some odd reason, IFI won't document the "checksum" works, and I guess once you know how it works, we aren't supposed to reveal their "secret".

I suppose for just displaying data, data from an errored packet will be quickly replaced by good data and any resulting 'glitch' will probably go un-noticed by the end user. If you use the 'user' bytes to multiplex more data at a slower speed, then understanding how the "checksum" works becomes more important.


As far as the language choice, VB, C, C++, Delphi, will all work fine. It is more a matter of which platform and compiler you are most comfortable and experienced working with.
__________________
--Dave