I have previously used Altium to create circuits, but this software is not free and all the libraries for the components for the Hello World board are already there in EagleCAD, so Eagle it is!
This week started off straight forward, follow the tutorial on editing the original Hello World board in schematic format and then transport that into board format. It seems simple but EagleCAD has nuances that can delay a new user in getting a good result. Firstly the schematic and board editor work together so closing one will affect the other because it does not transfer the changes. It also took me some time to work out how to do remote nets instead of wiring up manually. The issue was that I forgot to create a Net name, and then go about renaming it. I also managed to neaten it up by adding a frame (it seems silly to have to pick a frame, surely it should automatically frame your work?).
I found time to try some laser etching spray I acquired from a company awhile ago. I saw uses for it with labelling boards in specific areas (e.g. R1, R2, C1 etc).
The spray is very simple but you need to play with the settings on the laser cutter to get a good imprint on the board without it rubbing off too easily. The first picture is my first attempt which just followed the original png file but with some extra labels for components. This worked well but it rubbed off slightly too easily. The settings on the Epilog Laser for etching were 50% Power / 50% Speed.
My next attempt was on my actual board, but I didn't want to try to label the components because I felt it wouldn't be that effective with the milling removing some of the available copper left for etching. So I tried adding an image on the right hand size that could be used to label the board, obviosuly it had to be the batman logo. This time I hade 60% Power / 50% Speed, this produced a more robust image which didn't rub off as easily. Maybe even more power next time for more perfection
Using Eagle, I also created some text using the Eagle software. I wanted to label the incoming pins to show the polarity rather than just trying to work it out each time. This worked out ok but the text was too small for the toolbit to effectively give it a good finish.
My final attempt of changing the appearance of the board was to try and etch into the back of the board which I thought might get rid of the stickiness (it didn't). All of my attempts at etching or milling into the board were to make the boards more acceptable as opposed a fully designed board from a board house. I believe my findings show that it is possible to give the boards a nice silkscreen, but the results can be hit and miss.
The first board I made had one major issue which I did not diagnose until I had made the board. This made me heed the advice of the electrical rule check (ERC), which I had observed before but did not notice one major issue which was the VCC and GND traces were directly connected (for which I have no idea how that happened). After this incident and wasted man hours trying to fault find the board, I went into the the ERC and checked the rules. There were certain issues where pins have no value or do not conect to anything (valid reasons), if I am happy with these, I can approve them and move on. I did try and go back and purposely make a mistake but the software did not recognise there to be an issue, I put this down to Eagle not being intelligent enough to recongise that VCC and GND should never meet directly. I am still trying to work out how to add this rule.
This is where I can set the minimum distance between the traces and the pads. The drill bit we use for milling is around 15mil, so 16 mil is used to keep a distance between them. I can also set the trace thickness in the design rules, if I have more power going to a certain component I can increase the thickness of the trace.
This is a rough guide on how to use Eagle to achieve a finished circuit board. Please note that the milling process is excluded from this guide as it is covered in more detail in a previous week.
Without wanting to wait a week to see if my board worked, I set out to check it simply with my tutor Michael. I am not paying attention this week to the process of configuring the board (that's next week) but I did manage to get my board to do a basic arduino blink programme. There were teething issues such as me forgetting to solder one of the FTDI pins which meant the board had no power, but it eventually started working. There was a brief moment where the board was not working properly (the green LED was really dim), I checked the LED was OK by passing 5v across it and the resistor, it was fine. I then thought the board was broken so I decided to make a new one...
The 3rd board I made was really the board I wanted to make in the first place because I added a red LED and resistor in parallel to the VCC trace, which showed when the board was powered up. I soldered it all and powered it up (yay red light!) and it programmed fine through my ISP header and Macbook. I then decided to check my 2nd board again, and repgrogrammed it and it was fine afterall. I'm blaming that on one of the computers at FabLab!. So now I have 2 working fab boards, time to programme them to do something interesting.
Please watch this space whilst I try out simulation packages