I tried different setting and I found that if I press TAB during manual routing I can choose "Ignore obstacles" mode which made me possible to connect the pins (I will just ignore the errors I will definitely get during DRC): After that I can press Ctrl-C and add the component easyĪctually this was described in the gray box in the upper left corner of the screen.Press Ctrl-C (I can use context menu as well).I find the way PCB editor doing the Copy-Paste: The second problem is that I can not multiply pads and components: Ctrl-C -> Ctrl-V is not working. I can add components, pads - but I can't add traces (I can start the trace but I can not go to another pad - which is reasonable as there is no net created in schematic). They will need to be using a 3rd party GIT tool like Tortoise GIT or something similar and have a GIT repository set up on a shared server.I'd like to make a PCB but I don't really need a schematic for it (it is just a prototyping board). If they want to use Altium Designer + GIT outside the Altium 365 environment, this is still possible but there are some things that must be done for it to work correctly. It's integrated with Altium Designer so there's no need for 3rd party software or to manage your own data repository on a server. Altium 365 uses GIT as the internal repository and is designed for just such a usage with multiple engineers collaborating on a design. If we start new projects that are derivative works, i'll fork the reference and start from there.Īltium 365 has a solution. In worse case, becuase we include all history, we can revert, so it's minimal impact on the layout end. if it stands a chance for conflict, then one of us will verbally have the ball until we release the verbal lock. if i need to update elements of the pcb repo that I know will not affect the layout, then i'll tell them to occasionally pull, etc. I make it easy for him and the process works. In my situation, I have a pretty good understnading of how to work with git however, the layout engineer does not. I can work on changes to the design in different git branches and merge them when ready. project_sch/schematics/fpga_bank2.schdoc for example) ** pcb repo: keeps pcb, outjobs, project file, the pcb library, and the schematics are linked using relative paths to the schematic repo (so. ** schematic repo (project_sch, above): keeps schematics, schematic library, a project_file_1 which includes relative links to the pcb in (project_pcb), schematic history (why we need the separate project_file_1), schematic outjob mnt/c/users/idiot/documents/project/project_pcb mnt/c/users/idiot/documents/project/project_sch ** cloned as folders at an equal level, for example: This is just how i do it, so if someone has a better way please lmk. I use git extensively in a patch-work collab setup with altium.
0 kommentar(er)
