I am building a Sanguino now, need more memory and more digital/analog pins.
When i have completed the Sanguino i will add buttons to control a menu and a Accelerometer to measure the g-force.
What kind of protocol are used for a motorcycle?
By the way, could you explain why a horizontol line that is drawn from left to the right is not complete
Could you explain the reason to why you will run the display and OBD process on different processors? Will that really speed up the code execution or are you adding more technical candy ?
I would be interested in hearing how you guys think support for panels that required different delays should be handled
It's a shame that the Arduino only has 1Kb RAM, if it 2Kb or more you could do all drawing operations on a framebuffer in RAM and blit the changed parts to the LCD. This would speed up things a lot.
I suggest making the duration of the enable signal a compile time option.
I am not sure adding the delay in enable is the right place for your chips? Have a read of this thread from post 25 onwards and let me know what you thinkhttp://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1210427907/25
This is what I've done. I had to increase the 450ns delay to about 4.5 microseconds to get my LCD from Sure Electronics to work. There seems to be some variations between controllers here. The right controller works fine from about 2 microseconds, the left controller needs 4.5 microseconds.The example where you modify Enable() does not change the width of the pulse, it adds a longer delay after the pulse. Also, at one point in the code you're generating an Enable pulse without calling Enable(), so modifying Enable() won't suffice.My LCD needs a 4.5 microsecond pulse with a 4 microsecond delay to function properly.