Go Down

Topic: Shield Pin Usage Table (Read 10 times) previous topic - next topic

TBAr

The chart version makes it a lot easier to see which shields conflict with other shields, so thanks for putting that format up for comparison to the original tables.

Do you foresee "Notes" in the left column, under the shield name (like you entered for the AsyncLabs WiShield 2.0)? Some of the notes in the table format are pretty extensive already, with more complex shields to come, I'm sure.

bhagman

#6
May 10, 2010, 07:55 pm Last Edit: May 10, 2010, 07:55 pm by bhagman Reason: 1
This morning, I altered estranged's table (concept from Mark Bramwell) a bit.

The ordering of the pins is important.  People often overlook the fact that the analog pins can also be used as digital pins (since they are not labeled as such on the board).  For example, our uMMC can also use "analog" pins 0 and 1 (digital pins 14 and 15) as a soft serial port.

To help with this, I put the analog pins at the end of the list instead of at the beginning, and also labeled them with their digital pin number equivalent.

Also, because the table will potentially get quite long, using the pin number to indicate usage, instead of just an x, will help with understanding column position - you know those long, wide tables where you have to scroll back a hundred times because you can't remember what each column is for.

What do you think about the positioning of the description/notes field under the pin usage?  It's really the only place to put that data, unless you have links to another section - but that gets complicated fast.

Thoughts?

b

mowcius

Quote
I like the stacking of the analog/digital pin idea, it makes it clearer that the analog pins can do double duty as higher number digital pins.

I don't really like the notes field interrupting the grid though.  Having a continuous grid you can scan your eyes up and down really makes a chart like this much more readable.  I think simply minimizing the notes as much as possible, and putting them in with the description is a better way to go.  Some of the comments seem unrelated to pin requirements (Arduino ethernet/xbee)

We could lobby for a wider playground page, that would alleviate this whole problem.

Quote
What do you think about the positioning of the description/notes field under the pin usage?  It's really the only place to put that data, unless you have links to another section - but that gets complicated fast.

Regarding the notes, I think that is a bad idea as it clutters up the table and also makes it more complicated to modify and add to.

I think that the pin numbers is a good idea but really we want a 'compare shields' part with a user selection thing to be able to get any 2 or 3 shields next to each other so they can easily compare the pin usage and other requirements. This would not be easy though (well maybe to some people - speak up!)

Mowcius

bld

#8
May 10, 2010, 09:31 pm Last Edit: May 10, 2010, 09:32 pm by bld Reason: 1
Hmm, wonder if I can make my webserver dynamic generate images like the one from Mark Bramwell...

Plus the option to easily add new to it.
captain-slow.dk | non contagious!

Coding Badly

Quote
Hmm, wonder if I can make my webserver dynamic generate images like the one from Mark Bramwell...

I've used the PHP image library to do that sort of thing and it was fairly easy.

But, an HTML table would be much easier to generate.  It generally amounts to: output "top stuff" (<table> tag, header row), output each row in a loop, output "bottom stuff" (footer row, </table> tag).

Go Up