13. Networking and communications

"design and build a wired &/or wireless network connecting at least two processors"

page contents:

eagle practice

asynchronous boards

iterations

I2C

learning points

Eagle practice

In this assignment we made boards that could communicate with each other. This is very useful for projects that need to run on several processors or over a distance. I took Neil's asynchronous board as a starting point and made my own design. In Eagle, I am adding identification and revision numbers to my boards as good practice.

Eagle also offers the possibility to add descriptions to project files. This is good practice I think, because it helps others to be able to work with and build upon your design more easily later on. Also, if you need to redesign boards at some point in the future, you probably forgot details of what you did. So adding notes about versions, their intended functions and most important components and features is a good idea. Right click on a project name and click on Edit Description. Descriptions can be marked up with HTML, like so:

asynchronous boards

I have made it a habit to check traces before cutting out my boards. It has helped me at least once to save a board (and material!) that otherwise would have had to been thrown away.

Iterations

Sometimes, when you are creating new boards, it is good practice to develop it in iterations. It helps to build understanding of what you are trying to build. Throughout the Fab Academy, working with the Modela is a quick and easy way to produce prototype boards. I like this prototyping-mindset where you focus on iterations and improvements instead of aiming for a fixed end-goal (which always changes anyway).

I ended up making board #2 with the buttons. Version 3 might be useful if I wanted to make a network at some point where I want to have the freedom to change sensors for every node later on. After making the boards, I used Neil's code to test them.

I2C boards

After making the first boards, I also made designs for I2C boards. I might use them later during the Fab Academy.

Learning points:

• I am using identification and revision numbers for my boards helps to keep track of what I made and what the boards can do
• add descriptions (use HTML markup) to Eagle files makes it easier to improve on boards in the future
• develop boards in iterations, starting at basic functionality and expanding on that in steps

top of page