The Pi can only drive one display at a time from either the HDMI or Composite video ports. You might be able to make a USB display work, though. You could get 2 Pis and connect them via ethernet. One would poll for data, and provide it to the other one while they both drove a display containing different gauges.billgiacheri wrote:It will be interesting to see if the pi can drive more than one display since most dashboards are much wider than tall and a normal rectangle will likely not be big enough width wise and still fit height wise. 2 7 inch displays side by side, on their side would probably work for the IROC, there is also a 10 inch single display that might work in the Monte.
Can't find a good source of information about this, but Kevin makes a good point. Start at 10 Hz/FPS. This is way less than you should be able to get data out of a CAN-BUS system. See how the gauges perform, and adjust as necessary. 10 FPS is low for full motion video, but should be about adequate for gauges. It needs to be enough so the animation of your fastest moving gauge (tach) doesn't look choppy. Might need 15 or 20 FPS. It will probably be limited by Pi performance. You could get real fancy and only update the tach and speedo at a higher rate and just do the others at 1 Hz or even slower.billgiacheri wrote:I want to do some research to determine how fast the OBD updates so I am not attempting to update the pi before the OBD has a new value because that will be a waste of resources, and the pi is pretty limited.