Commit 25e891ce authored by Árni Björnsson's avatar Árni Björnsson
Browse files

Updated weeks 05 and 11

parent 4d249e11
Pipeline #312535 passed with stage
in 55 seconds
......@@ -8,7 +8,7 @@ Oh boy, oh boy! This will be interesting.
I do not have so much experience in this field but I'm excited about it. A few weeks ago I took some time to get to know our tools and equipment related to making circuit-boards.
I tried out [KiCad](https://www.kicad.org/), [FlatCAM](http://flatcam.org/) and tested out our Wegstr CNC router. We also have a Roland CNC, but it's been giving us a bit of a hard time lately.
I tried out [KiCad](https://www.kicad.org/), [FlatCAM](http://flatcam.org/) and tested out our [Wegstr](https://wegstr.com/) CNC router. We also have a Roland CNC, but it's been giving us a bit of a hard time lately.
What I did then was to make a ATTiny45 programmer. I only did the cutting and soldering, I did not program it.
......@@ -18,7 +18,14 @@ This week is not about designing from the ground up, but to make a board from ex
### KiCad
I cloned the repo and opened the project in KiCad. Only thing I did there was to place a new __origin point__ so that I save on matieral and use scraps to practice. From there I generated new trace files, for the circuit itself and the cutout.
I cloned the repo and opened the project in KiCad. Only thing I did there was to place a new __origin point__ so that I save on material and use scraps to practice. From there I generated new trace files, for the circuit itself and the cutout.
Image files from the project:
| File |
| ---- |
| [Programmer-UPDI-D11C-B_Cu.svg](../images/week05/Programmer-UPDI-D11C-B_Cu.svg) |
| [Programmer-UPDI-D11C-F_Cu.svg](../images/week05/Programmer-UPDI-D11C-F_Cu.svg) |
<figure markdown>
![KiCAD](../images/week05/boardKicad.JPG)
......@@ -66,6 +73,8 @@ You would then repeat this process for the cutout.
Wonderful!
Please note that in [week11](./week11.md) I have a further step by step guide to using FlatCAM and the Wegstr CNC router.
### Cutting
I loaded the circuit trace file and started milling on the __Wegstr__.
......@@ -82,7 +91,7 @@ We have two Wegstr in the FabLab, one new and one old. The new one was occupied
<figcaption>Oh oh!</figcaption>
</figure>
It was to loose!
It was too loose!
<figure markdown>
![Attempt #2](../images/week05/board03.JPG)
......@@ -99,11 +108,22 @@ It was to loose!
<figcaption>Cutout</figcaption>
</figure>
### Soldering
<figure markdown>
![Pick and place](../images/week05/board06.JPG)
<figcaption>Pick and place</figcaption>
</figure>
| Name | Component | Quantity |
| --- | ---------- | -------: |
| Microcontroller | ATSAMD11C14A | 1 |
| Resistor | 4.99k | 2 |
| Voltage regulator | LM3480-3.3V-100mA | 1 |
| Pinheader | 2x02_SWD_P2.54mm_Vertical_SMD | 1 |
| Pinheader | 2x03_P2.54mm_Vertical_SMD | 1 |
| USB | Conn_USB_A_Plain | 1 |
After cutting it out, I filed the edges and scratched the surface loosely to get better tin adhesion.
<figure markdown>
......@@ -213,9 +233,43 @@ Before further ado, let's meet the Wegstr!
<figcaption>Wegstr CNC mill</figcaption>
</figure>
#### Wegstr interface
Here we have the Wegster interface. The screenshot below is taken during the line test milling documented below.
<figure markdown>
![Wegstr interface](../images/week05/wegstrInterface.JPG)
<figcaption>Wegstr interface</figcaption>
</figure>
In the upper left/middle part, you have power controls and X,Y,Z values and reset buttons along with START, PAUSE, STOP, GO ZERO buttons.
On the right part, you get a preview of the milling path along with the mills current position (the little green dot).
On the lower left part you have device status (device ready / offline), auto level control, movement controls and a movement speed slider.
In the lower middle, you can load, close and rewind G-codes. To the left of it, you have the G-code progress bar.
#### Start milling
After mounting a PCB plate and the appropriate bit, you must:
- Open the Wegstr interface
- Move the mill to the correct position and reset x,y values (using the buttons)
- Either use the auto level function or manually set the zero point. (I seem to get fine results by using the manual method of lowering the bit to the top of the PCB and zeroing).
- Load the g-code file using the load button.
- Hit start, monitor the machine move to it's starting point and confirm that the correct tool is mounted and the machine will start milling.
You should monitor it's progress and use your ears to possibly adjust the speed. This is hard to describe in words, experiment and see what works best.
### Line test - Weekend fail
During the weekend I tried to simultaneously entertain my three year old son in the FabLab and do the line test. Well, that was not very succesfull!
During the weekend I tried to simultaneously entertain my three year old son in the FabLab and do the line test. Well, that was not very successful!
<figure markdown>
![The line test image](../images/week05/linetest.png)
<figcaption>The line test image</figcaption>
</figure>
<figure markdown>
![Epic fail!](../images/week05/line-fail.JPG)
......@@ -228,7 +282,7 @@ tl;dr: I had a bit of a failure using Fab Modules and had a bad drill bit.
So, after a few cups of coffee, a good chat with my colleague, I went for a second run.
This time I managed to do things a bit better. I used [Fab Modules](http://mods.cba.mit.edu/), specifaically these steps:
This time I managed to do things a bit better. I used [Fab Modules](http://mods.cba.mit.edu/), specifically these steps:
`Right click -> open server program -> mill 2D PCB png` and got familiar with the options.
......@@ -243,11 +297,6 @@ All in all, I made and used the following files:
The Wegstr has an autolevel function, but I did use the manual/gravity based method to zero the bit. I have my doubts about the function, though we might need more testing.
<figure markdown>
![Wegstr interface](../images/week05/wegstrInterface.JPG)
<figcaption>Wegstr interface</figcaption>
</figure>
I used a flat 0.4 bit first, doing most of the milling. It did a good job!
<figure markdown>
......
......@@ -167,7 +167,10 @@ Note about the Wegstr CNC machine. There is no information displayed in the GUI
But you can adjust the speed by dragging a slider in the GUI. The default is set to 100% speed.
TODO: Missing screenshot from Wegstr software.
<figure markdown>
![Slider on the bottom left](../images/week11/wegstrInterface.jpg)
<figcaption></figcaption>
</figure>
##### Importing the gerbers
......@@ -278,14 +281,10 @@ This is the machine. It needs a bit of cleaning. Let's do that later, get going
<figcaption></figcaption>
</figure>
TODO: Missing screenshots of software of milling software
Using the tiny hex key provided with the machine, I install the milling bit, which is a V-shaped one.
I manually move the spindle to the lower left corner, as close as I dare, and zero the X and Y axis.
<figure markdown>
![X-Y zeroing](../images/week11/weg02.jpg)
<figcaption>X-Y zeroing</figcaption>
......@@ -309,8 +308,6 @@ The moment it touches, the spindle stops moving and you have your can zero your
Next up, I load the milling NC file and start the milling!
TODO: Missing screenshots of milling software
<figure markdown>
![Started milling](../images/week11/weg05.jpg)
<figcaption>Started milling</figcaption>
......
<?xml version="1.0" standalone="no"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
"http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink"
version="1.1"
width="6.276340cm" height="4.015740cm" viewBox="0 0 62763400 40157400">
<title>SVG Picture created as Programmer-UPDI-D11C-B_Cu.svg date 2022/02/26 16:05:41 </title>
<desc>Picture generated by PCBNEW </desc>
<g style="fill:#000000; fill-opacity:1.000000;stroke:#000000; stroke-opacity:1.000000;
stroke-linecap:round; stroke-linejoin:round;"
transform="translate(0 0) scale(1 1)">
</g>
<g style="fill:#000000; fill-opacity:0.0;
stroke:#000000; stroke-width:0.000000; stroke-opacity:1;
stroke-linecap:round; stroke-linejoin:round;">
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
</g>
<g style="fill:#FFFFFF; fill-opacity:0.0;
stroke:#FFFFFF; stroke-width:0.000000; stroke-opacity:1;
stroke-linecap:round; stroke-linejoin:round;">
</g>
<g style="fill:#000000; fill-opacity:0.0;
stroke:#000000; stroke-width:0.000000; stroke-opacity:1;
stroke-linecap:round; stroke-linejoin:round;">
</g>
<g style="fill:#000000; fill-opacity:0.0;
stroke:#000000; stroke-width:100000.000000; stroke-opacity:1;
stroke-linecap:round; stroke-linejoin:round;">
<path d="M55034524.999999 13040477.000000 A500001.000000 500001.000000 0.0 0 0 54534525.000000 12540477.000001" />
<path d="M55034524 13040477
L55034524 24040477
" />
<path d="M54534525.000000 24540476.999999 A500001.000000 500001.000000 0.0 0 0 55034524.999999 24040477.000000" />
<path d="M43034523 29540477
L11034525 29540477
" />
<path d="M54534525 24540477
L45034525 24540477
" />
<path d="M45034525 24540477
L45034525 27540477
" />
<path d="M11034525.000000 7540479.000000 A1999999.000000 1999999.000000 0.0 0 0 9034525.000000 9540479.000000" />
<path d="M9034525.000000 27540477.000000 A1999999.000000 1999999.000000 0.0 0 0 11034525.000000 29540477.000000" />
<path d="M43034523.000000 29540477.000000 A1999999.000000 1999999.000000 0.0 0 0 45034523.000000 27540477.000000" />
<path d="M9034524 9540477
L9034524 27540477
" />
<path d="M45034525 12540477
L45034525 9540477
" />
<path d="M45034523.000000 9540477.000000 A1999999.000000 1999999.000000 0.0 0 0 43034523.000000 7540477.000000" />
<path d="M43034523 7540477
L11034525 7540479
" />
<path d="M45034525 12540477
L54534525 12540477
" />
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
<g >
</g>
</g>
</svg>
This diff is collapsed.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment