Skip to content
Snippets Groups Projects
Commit 588cf1b5 authored by James Khan's avatar James Khan
Browse files

Update 6 files

- /docs/assignments/week04.md
- /docs/files/week04/jamesk-elec-design-F_Cu.svg
- /docs/files/week04/toolpath file.c2d
- /docs/images/week04/week04-scrn-new01.png
- /docs/images/week04/week04-scrn-new02.png
- /docs/images/week04/week04-scrn-new03.png
parent 668c9579
No related branches found
No related tags found
No related merge requests found
Pipeline #545391 passed
......@@ -18,10 +18,12 @@ However 2023's group assignment didn't have the PCB board house component, so I
### Rewritten assignment
- I initially did this assignment in a previous cycle heavily documenting the production of the [Quentorres RP2040 hello board](https://gitlab.fabcloud.org/pub/programmers/quentorres) design given to us.
- I had a lot of issues with the software used for generating the toolpathing for cutting my traces. I didn't want to lose all that insight, since I thought they were a great learning experience and may be useful for other students who might encounter similar problems.
- I later made my own board that I designed in the [electronics design week](https://fabacademy.org/2021/labs/vancouver/students/james-khan/assignments/week08/). Instead of removing the detailed explainations from when I initially wrote the assignment, I decided to instead just add in extra notes and pictures from my personnaly designed board.
- I later made my own board that I designed in the [electronics design week](https://fabacademy.org/2021/labs/vancouver/students/james-khan/assignments/week08/). Instead of removing the detailed explainations from when I initially wrote the assignment, I decided to instead just add in extra notes and pictures from my personally designed board.
### Development board
### Board Design
#### Development board
I won't be designing the board myself. Instead I made the Fab Academy's recommended board, the [Quentorres RP2040 hello board](https://gitlab.fabcloud.org/pub/programmers/quentorres), a development board based on the [XIAO RP2040 microcontroller](https://en.wikipedia.org/wiki/RP2040). I won't be making the Quentorresaurus board just yet. The purpose of a development board is to be able to easily connect "things" to your microcontroller to try programs on it. The "naked" [SEEED rp2040](https://www.seeedstudio.com/XIAO-RP2040-v1-0-p-5026.html) board would be difficult to use without building a larger board around it since its connection points are small and very close to one another. Making a development board helps alleviate this problem.
Here are the original files given for this test board:
......@@ -37,9 +39,20 @@ Here are the original files given for this test board:
![Quentorres Hello interior- board cuttout border](../files/week04/quentorres_interior.png)
[Quentorres Hello interior- board cuttout border](../files/week04/quentorres_interior.png)
#### My Design (Update)
My Board Design was developed in [electronics design week](https://fabacademy.org/2021/labs/vancouver/students/james-khan/assignments/week08/), so you can see the details there. The final design file that I needed for producing my board was the SVG file.
![](../images/week08/week08-19.png)
[My Board (SVG File download)](../files/week04/jamesk-elec-design-F_Cu.svg)
![](../images/week08/week08-22.png)
## generating toolpath
I had allot of problems developing the toolpath for milling the board. It should have been a fairly straightforward process since we were given the design. I will try to articulate my issues here [problems with toolpath](https://fabacademy.org/2021/labs/vancouver/students/james-khan/assignments/week04/#problems-with-pocket-toolpath).
### Development board
I had allot of problems developing the toolpath for milling the board. It should have been a fairly straightforward process since we were given the design. I will try to articulate my issues here: [problems with toolpath](https://fabacademy.org/2021/labs/vancouver/students/james-khan/assignments/week04/#problems-with-pocket-toolpath).
I used [Carbide Create](https://carbide3d.com/carbidecreate/) to generate my toolpath. Our precision desktop CNC mill is the [Carbide3D Nomad 3](https://carbide3d.com/nomad/). Carbide 3D are also the makers of Carbide Create, so it was the recommended software for generating the toolpath.
......@@ -92,8 +105,28 @@ The final step was to select the outer border line of the circuit and set it up
I then saved the completed toolpath file to load into the software to do the milling.
### My board (Update)
- I did the same procedure for generating my personal board's toolpath as I did for the development board above. And the end results were the same.
- I made some minor changes to the board in the Carbide Create software itself. Most of them were not related to the circuit's traces, instead they were things like labels on the board and cutouts for screw holes.
- I did make some changes to the actual circuit traces and these are discussed in the [Problems with pocket toolpath] section.
- My board took longer to cut than the development board (as expected), because it was a bigger board with more details.
- I encountered the same types of problems generating the toolpaths for my personally designed board as I did for the development board, and had to make some similar alterations.
Heres the [Carbide Create File](../files/week04/toolpath%20file.c2d) for my board.
![toolpath](../images/week04/week04-scrn-new01.png)
![design](../images/week04/week04-scrn-new02.png)
### Problems with pocket toolpath
#### Development Board
I had allot of problems with the pocket toolpath cutting away 2 sections traces and pads that it shouldn't. (highlighted in red)
![problems](../images/week04/week04-4b.png)
......@@ -118,6 +151,17 @@ Of course I couldn't just make the traces or pads arbitrarily big and still fit
Hopefully they can fix this error in the software in the future.
#### My board (Update)
- I encountered the same types of problems generating the toolpaths for my personally designed board as I did for the Development board.
- The solutions also ended up being the same. Small alterations to some pads and traces that were being erased.
- Seeing what ended up working was a bit of trial and error, just like before. The area circled in red below is the area where I was forced to make design alterations to account for the toolpathing errors in Carbide Create.
![pocket path prblems areas](../images/week04/week04-scrn-new03.png)
## milling the board
Milling the board was relatively simple.
......
This diff is collapsed.
File added
docs/images/week04/week04-scrn-new01.png

318 KiB

docs/images/week04/week04-scrn-new02.png

171 KiB

docs/images/week04/week04-scrn-new03.png

43.4 KiB

0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment