Doubtless there are people here looking into designing Shields for the PICAXE base device. And, no doubt, they will also have an eye on making it compatible with 'that other' processor
Obviously people can do what they like in terms of design and code , but it would be nice for users if some standards or considerations were made.
I'm sure there are many areas up for discussion, so can I start a ball rolling with considering SERIAL COMMUNICATIONS.
In many cases separate pins are used, but to save pins we may decide to share a serial data line. Thus , in effect, we have a Serial 'bus'.
I've attached some thoughts on a common standard if we all design Shields.
And I'm really referring to Shields which use a separate Micro which communicates serially to the Micro on the Shield Base.
It's all a bit scrunched up but I hope you get the idea.
Thus if we conform to a few basic standards then our shields can work together. Result: Smiles
(If you don't like the term "shield" then this method could also be appropriate on a serially joined Daughter Boards.)
Have a Look... electrically similar to I2C which everybody seems happy with.
(Please note: In some cases the Coder can set the Port.pin to O/P , send and then set back to I/P mode. Pefectly good in 99% cases. My suggestion is merely an electrical solution.)
It may be good to discuss other proposed thoughts in separte threads with similar titles.
Obviously people can do what they like in terms of design and code , but it would be nice for users if some standards or considerations were made.
I'm sure there are many areas up for discussion, so can I start a ball rolling with considering SERIAL COMMUNICATIONS.
In many cases separate pins are used, but to save pins we may decide to share a serial data line. Thus , in effect, we have a Serial 'bus'.
I've attached some thoughts on a common standard if we all design Shields.
And I'm really referring to Shields which use a separate Micro which communicates serially to the Micro on the Shield Base.
It's all a bit scrunched up but I hope you get the idea.
Thus if we conform to a few basic standards then our shields can work together. Result: Smiles
(If you don't like the term "shield" then this method could also be appropriate on a serially joined Daughter Boards.)
Have a Look... electrically similar to I2C which everybody seems happy with.
(Please note: In some cases the Coder can set the Port.pin to O/P , send and then set back to I/P mode. Pefectly good in 99% cases. My suggestion is merely an electrical solution.)
It may be good to discuss other proposed thoughts in separte threads with similar titles.
Attachments
-
94.3 KB Views: 69