Pulsonix User Forum

Technical advice from Pulsonix engineers and the wider community.

 All Forums
 Help with using Pulsonix
 Connected Jumper

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkInsert EmailInsert Image Insert CodeInsert QuoteInsert List

* Forum Code is ON

   Upload a file

Check here to subscribe to this topic.

T O P I C    R E V I E W
StefanThiel Posted - 29 Dec 2016 : 19:17:03
how can I create a "connected jumper". It is a mixture of using a starpoint but with 2 pad, which are connected by default without getting DRC errors.

The idea behind is to have a measurement connection without using the same netname but have it closed by default. -> For the first prototypes I can scratch the connection, and later on for series production it will stay connected, so I don't have to change the design anymore. I do not know how this is called in english.

Image Insert:

14.63 KB

5   L A T E S T    R E P L I E S    (Newest First)
jameshead Posted - 07 Jan 2017 : 17:13:51
Cool solution, I like it. You could create it in a schematic and a con and add to your library and use apply layout pattern the next time to save time placing and routing it in the new pcb.
StefanThiel Posted - 07 Jan 2017 : 16:35:20
ok, I finally found a workaround, which has all the features I wanted to have.
I created a block including 2 starpoints with a net connecting it internally.
Also I created a nice symbol for the block.
After translating this to the PCB, I moved the 2 starpoints nearby, routed the net and created a tight group with these 3 elements.
Advantage: In schematic the block looks like a device and can be reused and multi instanced.
In PCB it is a litte manual work at the moment ( as do not know how to create and use prerouted blocks ) but after grouping, you see that both nets stay at their own pad.

Image Insert:

91.66 KB

jameshead Posted - 01 Jan 2017 : 21:09:31
Your pictures look like what I was trying to explain.
The wires layers aren't really suitable for what you are after since they don't give you a physical copper pattern and the net name is the same both sides. They are used for insulated or non-insulated wire links across the pub for a single net. If you use them and output an ipc-d-356 netlist then your pub fabricator should come back to you with queries about open circuit nets when they check the imported Gerber and manufactured board against the netlist.
Some people use the wire layers to connect pads in footprints that use the same net such as a sot-223 heatsink pin or a fuse holder with two legs but there are other (better?) ways of achieving this.
StefanThiel Posted - 01 Jan 2017 : 19:07:55
Thanks for the advice, I got some steps further ( however this was a lot of trial and error )
This is what I got so far, a star point where I could use an alternate pad style of style type "special" which I designed by Setup->Define Pad Shape ( in the PCB Editor ).

Image Insert:

15.75 KB

After conneting and some routing trials, I found that there is no DRC error on this:

Image Insert:

11.28 KB

hm, I will continue.
What do you think of using this "Wire" Feature? Could this be a solution? I had no luck with it up to now, but maybe I am just missing how to use it for SMT pads.

jameshead Posted - 29 Dec 2016 : 20:05:24
I'd perhaps create it as a new type of star point. You can add your own types of star point. You can use define pad style to edit a rectagular pad to thin it out in the middle by making to opposite cut ins to get a single pad dumb bell or dog bone shaped.