Since I plan on through hole soldering, it may be easiest for me to ditch the package and just mark the holes and not worry about pin names etc. Any tips on adding simple holes from a package (digispark) would be helpful as well.

Hi Jmaturner, Welcome to EasyEDA. I am sure we can fix your pin mapping issue but unfortunately the link you have posted is to a private project or file so no-one but you can see it to offer help. Can you make it public? https://easyeda.com/Doc/Tutorial/share.htm#Sharing Please note: https://easyeda.com/forum/topic/The_best_way_to_design_a_PCB_in_EasyEDA-ThR3pwqIC It really is a bad idea to try to build a PCB without a schematic and your pin mapping problem is only a temporary bump in the learning curve. :)

thanks Andy, but when i right click on the project there is no option called "modify". I only see "access control" which allows for sharing by email.

Please see: https://easyeda.com/forum/topic/Project_management_in_EasyEDA_V3_10_x_onwards-ciuQpnJVv :)

Thanks for your patience Andy! I believe the project is public now.

This? https://easyeda.com/jmaturner/spectraled-d82bc68e1d3241d6973d5d2f93210ff9

Here's your error message: ![enter image description here][1] Here's the problem with the DGSPARK symbol/DIGISPARK package. Here's the schematic symbol pin mapping (ignore the spice pin column): ![enter image description here][2] This is the PCB package or footprint pin naming: ![enter image description here][3] so here's how you fix it: ![enter image description here][4] This is what the error message says after doing that: ![enter image description here][5] Do the same thing for **both** buttons because these are the symbol pin mappings: ![enter image description here][6] ![enter image description here][7] and this is the button footprint: ![enter image description here][8] I have no idea how the switch contacts are actually connected but if we assume that one contact is on pin 1 of the package and the other is on pin 4 then this is what the fixed symbol mappings would be: ![enter image description here][9] ![enter image description here][10] After doing this, the schematic passes straight through to PCB. * However another couple of notes: 1) You need to learn to draw schematic more tidily. Please see my last post in: https://easyeda.com/forum/topic/PCB_not_what_is_on_the_drawing-KB71jdvN5 and: http://michaelhleonard.com/how-to-design-the-perfect-pcb-part2/ for some notes. 2) I'm not clear if you really want two punch buttons or if you are trying to represent a single component that implements a changeover function so it may be that your original symbol pin mappings for your switches may have been OK if the switch had been a single component with 4 pins but because you had chosen an inappropriate footprint they were split over two components so would not work. :) [1]: /editor/20161023/580bd5db84ca1.png [2]: /editor/20161023/580bd37f5b886.png [3]: /editor/20161023/580bd517043e1.png [4]: /editor/20161023/580bd41696fe3.png [5]: /editor/20161023/580bd69ce3d14.png [6]: /editor/20161023/580bd7b433e30.png [7]: /editor/20161023/580bd965a0639.png [8]: /editor/20161023/580bd7769d808.png [9]: /editor/20161023/580bd8d0525d5.png [10]: /editor/20161023/580bd8ede3d26.png

Thanks a lot Andy! I was changing the spice pin for some reason thinking that was "pcb". This is my first time so thanks for the input. I was assuming I could stretch and move the wires around once at the PCB side.

Also, I am using two buttons separately. These symbols appear to be the closest thing to the "tactile button switches" that I'm using.

Yes, you can push tracks around on the PCB but you owe it to yourself to make the effort to draw a clear and comprehensible schematic. If only because it's much easier to check it with the schematic Design Manager. One thing I forgot to point out earlier is that the wires to the buttons are at an angle and do not connect to the wires to the resistors. You can see this because the red join dots are missing. Understand the choice and connections to the buttons now. Check the package pinout though. Then search the Tips and Skill for my post on things to check before ordering your PCB. :)

Thanks again! I have found the right buttons in the library. They are the SMT tactile buttons 6x6x5mm. If you get another chance, check out the updated schematic. One question, If I use ground symbols rather than drawing wires to ground will the software find the best traces once I convert to PCB? my project is using an Attiny85 from digispark (development board), but I probably should elevate my game and use the tiny85 alone (eventually I will have to). At that point I'll be having to code in C (from atmel studios) and program the tiny. Should this programming be done prior to surface mounting the tiny, or after? Cheers and thanks for the help.

`One question, If I use ground symbols rather than drawing wires to ground will the software find the best traces once I convert to PCB?` Yes and no. You have to either draw the wires in explicitly in the schematic or join them by netnames. With most nets it is pretty ovious that if they have the same name then they will be joined. Ground is slightly different in that if you have a ground symbol then any net or pin terminated in a ground symbol will be connected and that is the recommended way to do it. Trying to join ground nets by a mixture of ground symbols and net names gets a bit messy because you can only label the ground net as `gnd`. You cannot give it an arbitrary name. However if you decode to not include a ground symbol then you can give your ground net any name such as `ananloguegnd` and all nets with that name will be joined. It is actually only in a simulation schematic that a ground symbol is mandatory. In non-simulation schematics it is optional but is generally good practice except in certain circumstances such for example a self-powered 2 terminal high side switch where there is no connection to the ground of the system in which the circuit is to be used. About tiny85 programming: sorry I can't help you on that one: never used it. I think Google might be your best friend on that one. :)

Forgot to mention that there are some rules for net names. There's a post in Tips and Skill about it. :)

I was looking at your original schematic again and spotted that the DGSPARK symbol you had used is broken. The pin grey circles on the end of the pins for the 5V, GND and VIN pin are off the grid. They therefore do not connect to the wires. The symbol need to be copied, edited to correct this and then saved to create a corrected public version. Please fully document the corrected symbol (manufacturer, links to datsheets, supplier, supplier p/n etc.) Having also redrawn a (private) copy of your schematic - and checked your latest public copy - I think you might need to check the connectivity around these three pins and/or the choice of an NPN transistor and the diode polarity. As drawn your schematic does not make sense. If you are driving LEDs then you may also like to check this: https://easyeda.com/andyfierman/LEDs_must_have_series_resistors-OoGYgCK2k :)

Thanks. I noticed no matter what I changed the pin names to, I got the PCB error message. I will go ahead and proceed with correcting the digispark symbol. I will look into those suggestions about the LED as well. I built this circuit on a perf board and it seems to function well as the led lamp draws a max of 500 mA. It is a larger lamp (flashlight style). I was using a much larger load transistor (tip120) but that's just too big. I chose the transistor in the schematic because of it's 600 mA rating. I should probably go higher, but I really need the build small. :)