With Pattern Editor click on Con Headers: Type Rows Pins T and TH=Through Hole Pitch HDR - 1 x 2 T 2.54 HDR-2X1T/2x2/ Two row one pin (two pins total) 2mm pitch
HDR means MALE pins HDRF is the female receptacle
HDRF-1X2T/1.27 is a female 1 row 2 pin 1.27mm pitch receptacle
If you have a question what it is click the Datasheet the PDF will open
My personal favorite one: HDRF-2X36S/2.54 (S and SZ are Surface Mount) A 2X36 72 pin surface mount female header that no one stocks... I found them in China Match STM Nucleo boards.
Spend some time in the library looking at what you have before you start building your own or downloading.
You can check the 3D model for each part by clicking , 3D Model... button
Another good place to spend some time is the Con Jacks and Memory Cards - They have SD sockets from everyone.
Statistics : Posted by KevinA • on Today, 06:18 • Replies 2 • Views 22
So, if I made my first pass at a PCB using 170725_BatterySchematic, and 3 months later I want to update it using 171004_BatterySchematic, how do I proceed? 3 Months later, I might not even remember which of the many schematics I used to create the PCB, so at the very least I need to be able to find the filename of the 'related schematic' so I can overwrite that filename with the most current one. Ideally though, I'd like to be able to redirect the 'related schematic' entry to point to the most current one in my list.
TIA
Frank
Statistics : Posted by paynterf@gmail.com • on 41 minutes ago • Replies 5 • Views 4910
Changing the related schematic 1) In the Main Menu of the PCB Layout editor select File and choose Layout Information... in the drop-down menu. 2) Click on the [ ... ] button in the Related Schematic section of the Design Information dialog window. 3) Navigate to and select/highlight the desired schematic file in the Open dialog window and click on the [Open] button. 4) In the Design Information dialog window make sure the correct file path is showing in the Related Schematic section and select [Close]. 5) Resave the PCB.
p.s. Running the Renew Layout from Schematic tool will also allow you to change the related schematic. Don't forget to resave the PCB.
Statistics : Posted by Tomg • on 38 minutes ago • Replies 6 • Views 4911
I'm a new DipTrace user so I may be missing something here, but using net ports for cross-sheet signals in multi-sheet or hierarchical schematics looks all wrong to me.
Net ports don't change the name of the net they connect to. Why not? Why connect cross-sheet signals by means of a net port component name, rather than the net name? Using net port component names to connect signals with some invisible unrelated net name makes no sense to me.
Using net ports with different names for each cross-sheet signal also means you have a proliferation of net port components in your design, which makes a mess of your component libraries.
Also, net ports look wrong on the schematic. Net names appear in one font and color while net port component names are quite different, so you see a mixture of the two in a design which has named nets and cross-sheet signals. I'm of the old school which believes schematics should be aesthetically pleasing, used and easily comprehended by humans in addition to being netlist generators.
I experimented with all three methods of connecting nets without wires as described in Help, and they all have their problems. I ended up with some custom components which graphically show the signal direction:
These port components have no pattern, and their ref des is PORT. I set Main Marking = None on the first one I use and then copy/paste it for subsequent ports. I name the net connecting to the port component by the desired cross-sheet signal name. The second time I do this I am asked if I want to connect by name, which I do. This verifies that I typed the net names correctly. Then I display the net names.
This is quick, works well, and looks nice too. The only problem is when I create or update a PCB from the schematic it complains that "PORT1, PORT2, PORT3, ... have no patterns". It is easy to recognize that all the offending components are called PORTx, so I can tell that this warning is okay and move on.
If Novarm would add a component type which is not added to the netlist or layout, then the above error wouldn't occur. Altium has something like this. Does that sound like something I should request, or am I missing something already there?
(I've attached my cross-sheet port components in case anyone is interested.)
Statistics : Posted by Exality • on Today, 13:28 • Replies 0 • Views 3
My original library files for these components are gone due to poor library management and a drive fail. I was wondering if it is possible to re-create components from the schematic (.dch) or the pcb (.dip) file? It seems all the information is there, I just can't seem to figure out how to move it to a new user library for re-use.. Thanks in advance, dmac
-- 09 Oct 2017, 07:16 --
never mind, did it
Statistics : Posted by dmac • on Yesterday, 11:21 • Replies 0 • Views 15
@TomG: I like your suggestion for modifying the NetPort behavior, but to me it still looks funny, puts redundant information on the schematic, and muddles the concepts of a component name and a net name. (Your posting link has disappeared now -- I think you edited your original response on this thread from yesterday?)
I think I'll make a suggestion about providing a non-netlist component type. They can be used not only for cross-sheet signals like this, but BOM-only and "cosmetic" parts too.
Statistics : Posted by Exality • on 17 minutes ago • Replies 5 • Views 59
Thanks for your thoughts, TomG. Your suggestion is a great way to make NetPorts work for cross-sheet signals -- I just think they're a klugey way to do it in the first place!
Statistics : Posted by Exality • on 2 minutes ago • Replies 7 • Views 62
Just tried to update the 'library' thing and it does use the 'Name', no internal ID, the 'Name'.... Didn't know that... It appears they created the 'Net Port' from a component but didn't finish the job. As it stands I won't have an issue with mangling the net cause I didn't name the port since I've done that and found deleting the Net Port fixes it. And I can't see me editing a net port so that is not an issue for me. Your suggestion on what is needed are good, let us hope they have a few minutes to look at the issues and either fix the existing component or create something like the Buss Port with options.
Statistics : Posted by KevinA • on Yesterday, 20:25 • Replies 8 • Views 89
In Schematic v3.1.0.1, if you delete a wire with a net name which is visible, the net name is left dangling by itself. It can't be selected by clicking, only by dragging the mouse around it.
Statistics : Posted by Exality • on 34 minutes ago • Replies 0 • Views 3
In Schematic 3.1.0.1: draw a horizontal wire and a vertical wire below it, both separate and not connected. Switch to Edit mode and drag the upper end of the vertical wire up to the horizontal wire and drop it to form a T. It does not connect, and there is no Place Wire method which will connect them.
Statistics : Posted by Exality • on 26 minutes ago • Replies 0 • Views 3
Dragging a pre-existing wire to another won't give you a connection unless you are in the Place Wire mode. (In the Place Wire mode you won't really be dragging the wire, you will actually be adding a connecting wire.) Or just add a connecting wire from the end of the first wire (the one you were trying to drag) to any part of the second wire with only two left-clicks after enabling the Place Wire mode; more left-clicks if you need to turn corners of course. Things should automatically clean up after that.
Statistics : Posted by Tomg • on 56 minutes ago • Replies 1 • Views 14
