ORIGINAL: olnico
ORIGINAL: cgroen
Good input Oliver!
I'm currently looking at changing/adding screens to the device, my only concern is that there simply is too much data.
So it all boils down to try to minimize the number of screens, but still be able to ''deliver'' the most important data to the user, without having to wait for a high number of screens to pass by
What you could do is have the system display the important in flight data while the engine is cooling down.
Once the temperature of 100 degrees is reached, you could return to the ''before start'' screen.
Thats also a possibility, but here in the "cold north", my P160SX's cooldown in a few seconds during the winter, so maybe not much time.
I don't know if it's a problem with "all the data" in idle, the engine is not doing anything "usefull", so the display might as well show 5 different screens, maybe 3 seconds each, it's just sitting there anyway, so maybe not a problem in practice ?!
Guys, I really thank you for all your input, it's very nice to get a different opinion on stuff like this, when doing things like this, it's very easy to focus on something, very nice to get input in the process, thank you!
PS Sandor, the soldering of two cables on the board is a no-go, the GSU needs the 2 centre wires of the 6 pin connector (it uses I2C comms, SCL and SDA), so we would have to add 2 "spare" pads on the board, which there is not much room for. I think the splitter is a better idea