Log in

View Full Version : Dashboard port question

patTeam241
09-02-2005, 15:11
Ok, I'm writing my own data capture program for the OI, which would run from the Dashboard port. The goal is to have a more versatile recorder. However, I don't know the Baud rate, Parity, number of data bits, and the stop bit. Anyone have this information? Thanks
Mark McLeod
09-02-2005, 15:29
I don't know the Baud rate, Parity, number of data bits, and the stop bit. Anyone have this information? ThanksFrom the Dashboard Spec (dashboard-specification.pdf) in the IFI Robotics zip download.

19200 baud, No Parity, 8 data, 1 stop
Astronouth7303
09-02-2005, 17:16
Here's another one: How can a program tell if it is recieving OI or RC packets? My best guess so far is that there are specific channels for each.
patTeam241
13-02-2005, 21:12
For the OI/RC difference, there is a jumper right under one of the ports, I think it's the dashboard port.
seanwitte
14-02-2005, 09:21
Here's another one: How can a program tell if it is recieving OI or RC packets? My best guess so far is that there are specific channels for each.

From what I've seen there isn't a way to differentiate between an OI frame and an RC frame. The control bytes in the OI frame are the same as a type-2 data frame. I guess you could check for the frame type and assume its OI data if you're only receiving type-2 data frames.
lynca
16-02-2005, 02:23
From what I've seen there isn't a way to differentiate between an OI frame and an RC frame. The control bytes in the OI frame are the same as a type-2 data frame. I guess you could check for the frame type and assume its OI data if you're only receiving type-2 data frames.

There is a way to rewrite the RC/OI dashboard progam in which you can implement a custom packet structure. This is probably way too much work with the current FRC system. I believe Innovation FIRST should consider making the dashboard progam more expandable. These changes could be adding more/less packets or different timing baud and protocol options.

For instance, You could implement a timestamp function on the RC which relays timing infromation through one of the dashboard ports to get a more real time control feedback.

~Andrew Lynch