search

sirapol / glcd-arduino

Automatically exported from code.google.com/p/glcd-arduino
0 stars 1 forks source link

wiring diagrams and table disagree in documentation #49

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
In both your HTML and pdf versions of GLCD documentation, the connection 
diagrams or the connection table has a wiring error.  The chip select lines in 
the "KS-108 Pin Connections Table" is opposite what is shown in the Connection 
Diagram for panel B (and C). The chip select lines are reversed in one of 
these.  Which is correct - the table or the diagram?

Original issue reported on code.google.com by purchase...@comcast.net on 16 Dec 2012 at 6:48

GoogleCodeExporter commented 8 years ago 
There is an issue here.
Ultimately what matters is what is in the config file and the glcd datasheet.
The config file for the m328 boards wires a0/d14 to CS1 and a1/d15 to CS2
This agrees with the tables.
It is the wiring diagrams that are not correct.
Unfortunately, Michael did the wiring diagrams and I don't have the visio files
to fix it.
Another issue is that the ks0108 playground wiki has been altered (quite some 
time ago) and changed type C. (there is no panel C in the v3 HTML documentation 
- it was removed because of the wiki change to avoid confusion)
However, the pdf documentation is not being maintained. It does have a type C 
panel, so now the panel types on the wiki don't agree with the panel types in 
the pdf v3 documentation included with the library.

On the bright side, crossing the CS1 and CS2 wires will not keep the glcd from 
working. It will merely swap the left and right halves of the display which is 
easy to correct.

I'm not happy with the state of the documentation related to these tables, 
diagrams, and the wiki. I haven't quite figured out the magic bullet to get it 
all tied together. I'm also looking at either eliminating the PDF document or 
generating
one from the doxgen files that create the HTML documentation.
The playground wiki is forever a potential issue since anyone can edit that.

But fixing the diagrams is now on the list of things that need to get updated.

Original comment by bperry...@gmail.com on 16 Dec 2012 at 7:46