Multisim and Ultiboard

cancel
Showing results for 
Search instead for 
Did you mean: 

Autorouter oddity

I attach an Ultiboard 11 project.  I have manually connected the pads on the right hand side using the logical straight line routing between the pads at the top of the board and those at the bottom.

 

If you use the autorouter to finish the board, it makes if I may suggest a "right pigs breakfast" of it - it can't be hard to to work out that the best route is a vertical straight line!  I tried changing the autorouter options, but that made little difference.

 

Thoughts, advice,  and/or comments welcome.

0 Kudos
Message 1 of 6
(4,171 Views)

Hello david_c_partridge,

 

I have opened up your project and I tried to Autoroute.  I believe that I see the mess of traces that you are describing.  From the sheet properties, I believe that your project is still set to the default settings for trace widths, clearances, and route layers.

 

If you select View->Clearances, you can see an overlay of the amout of space between pads and traces.  Clicking on the  tabs for Parts and Nets in the Spreadsheet view also shows that the defaults widths for Traces and Clearances is 10 mil. This means that when you autoroute, these rules are being inforced.

 

The last tab to look at Copper  Layers, where you will find that on the Copper Top, the Bias is set Horizontal, which means that any traces on that layer will be forced to horizontal most of the time, where as your pads are completely vertical to each other.  Changing this setting to Vertical gives you different autorouting results.

 

I believe a combination of a Vertical Bias, and allowing for routing only on the Copper Top layer will cause a straight vertical trace pattern.

 

Best Regards, 

George T.
Senior Applications Engineer
National Instruments UK and Ireland
0 Kudos
Message 2 of 6
(4,158 Views)

david_c_partridge,

 

Yes thanks for your observation and besides those already given here a few tips for you and others using the Ultiboard autorouting capabilities.  

 

Straight line routing - make the autorouter 'dumb'...

For something like this - where it appears that a straight line is obvious - what is basically happening is that based on your 'Cost Factor Settings', the autorouter is trying to over analyze the traces and optimize the trace positions.   In this case, I would make the autorouter 'dumb' by setting all of the settings on the Cost Factor tab to their lowest setting '0' or '2' in some cases and you'll see better results for straight line routing.   When you set the cost factors to their lowest setting you're basically saying to the router - 'do whatever you need to do, don't overthink it'.   Then if you see something not 'behaving' you can increase the cost factors for that particular item and it will try to pay attention to that setting more (also see about piece-meal autorouting as well).   You can always go back to 'Default' if you need to...

 

cost factors.JPG     With your design: straight_lines.JPG

 

General Tips on Autorouting...

Grid / trace width & clearance issues:   Generally, if the default copper grid for your design is too coarse (Options -> PCB Properties -> Grids & Units and then Grid step name: Copper grid), you will get poor results and the autorouter will not complete if you are using grid based routing.    I generally use the autorouter with the 'gridless' setting which does make sense most of the time for SMT designs (I see that you've set this to gridless).   By the way for designs with fine pitch parts, I usually set my copper grid to 1 mil to accomodate the precision required in routing those types of designs.  Also make sure that your trace width and clearances are set (in the bottom spreadsheet view) so that the autorouter can accomodate traces running between pins (such as with a connector) if needed.

 

Route critical traces first:  You'll probably want to hand route (manually) any critical traces first.  These might include low level analog traces, high speed traces (differential pairs) or traces that need to be kept away from noisy areas of the board.   Also it is a good idea to do all of your inner ground/power planes first before routing if possible, especially if you have specific locations or requirements for your planes (in a multilayer design).  

 

Managing nets and planes: In designs with 4 or more layers, you can usually do yourself a favor (and the autorouter) by constraining nets to run on certain planes and where it makes sense (such as not through a ground or power plane).  You can manage the routing layer on a per net basis in the spreadsheet view -> nets tab.  You'll need to include the top or bottom plane, depending on the SMT part location, if the net is originating from a SMT pad.

 

Autoroute in a piece-meal fashion:  You can select certain nets in a piecemeal fashion and this can sometimes be an important strategy for leveraging the autorouter to assist you in routing critical areas of your design first.   For instance if you click on a part or multiple parts, you can automatically route all traces attached to those parts by selecting the Autoroute -> Autoroute Selected Parts.   Similarly if you want to route specific traces, you can highlight the nets (in the spreadsheet -> nets tab) and then select Autoroute -> Autoroute Selected Nets.

 

Regards,

Pat Noonan

 

0 Kudos
Message 3 of 6
(4,151 Views)

Setting routing bias to None or Vertical didn't achieve anything 😞

0 Kudos
Message 4 of 6
(4,146 Views)

david_c_partridge,

 

Adjust the 'Cost Factors' as shown and it should produce the straight line results I was able to get.

 

The routing bias are 'guides' for the autorouter to follow for traces that are making several turns to navigate through a design.   The general trend is that most of the bends will be short for the opposite bias, and will have the majority of the length covered in the stated selection.   I believe bias is a low priority option.  (For example the router has to connect point A to point B despite the bias - such as a pin directly horizontal from another connected pin, but the bias is calling for vertical)...

 

Regards,

Pat

0 Kudos
Message 5 of 6
(4,143 Views)

Yes, but still nowhere near as sensible as the hand routed solution.  I'd hoped for better - even with all the factors adjusted, the traces still have a "jog" in most of them.  I think the autorouter needs introducing to Mr. Occam and his razor - the simplest solution is often the best.  It's just that doing it by hand took quite a long time, which the router could have saved me if it had only been (even) more simple minded.

 

Yes I do realise that auto-routing isn't a simple subject.  I'm certainly not up for designing the algorithms for it.

 

Thanks to all

Dave

 

0 Kudos
Message 6 of 6
(4,138 Views)