Hey guys, haven't posted in a couple of weeks, so things are obviously going a bit better(Thanks to you folks), but I have run into some issues that I'd like to ask about.
1.) Does orcad 17.2 have autoroute? I am having a nightmare of a time with a new microsd connector that has a different footprint than our last one. I made a new footprint, but i'm having trouble finding a path for my traces. Just out of curiosity I thought i'd like to try autoroute, and see if it helps even with 1 or 2 connections, but unfortunately I can't seem to find it in 17.2. Is autoroute in 17.2? has it been replaced with something else?
2.) Randomly, 'place via' is now greyed out, and I can't seem to add via's anymore unless I copy and paste one in.
3.) I'm running into all sorts of DRC errors, but some of them existed before the file was past on to me. Obviously, no drc errors would be ideal, but are they sometimes ok? Obviously, not all DRC errors are created equal, and are based on rules put in place by the previous designer, but can I leave some of them in place? Some of them seem unfixable (at the moment, with my current skill level).
The specctra autorouter is external to Orcad and Allegro. You export the other kind of DSN file from Orcad/Allegro then run the Specctra program on it. Route, then import the file (.rte) back to Allegro/Orcad.
The connector is this one. Pretty standard, but the problem is not the odd footprint of this particular connector, but the previous. Rather than one row of 8 pins, it had 2 rows of 4 on the right and left side of the connector. The board is very dense, so re-routing is pretty hard for someone this inexperienced.
I do not know the minimum via. I didn't design the board, and I'm basically a greenhorn, so I can't even answer that, but I can say, it's not that the via won't appear near the microSD card, it's that it won't appear in MOST places. It does work occasionally, and i'm sure it's something i'm doing wrong, but the problem is, it's not telling me what i'm doing wrong. I'm sorry, I sound like a hopeless case.
1) Yes. But how you need to access it depends on your license. If you are OrCAD Pro or higher, it's in the Route menu. Otherwise, I might try the suggestion to export / import. Since I have the higher license I don't use that method.
2) Makes no sense. Sounds like you have not clicked on an object first that can take a via such as: shape, cline, via, pin (set your find filter and make sure all objects are on, click on something then the via should drop down).
4) Make sure there is a non-zero setting in the tolerance field of the differential pair. Sometimes only the positive field needs a value... Without seeing your board or error message it can't be resolved on here.
5) Yes: Tools->Reports->unconnected pins, Tools->Reports->unplaced components, Tools-Reports->Dangling Lines, etc.... Summary will you give you a nutshell but won't tell you where the errors are but it should be a good starting point.
I have simple board design with 2 layers and around 70 components. I just wanna try autoroute option. I couldnt find it under Route menu. I'm not running lite version or the demo version. I have the full license. Any suggestions where to find autoroute option? i know that in the new version of the Orcad 16.6 they call it PCB router instead of Autoroute. But I cant see any of them. Please advice.
Hi, I'm new to using Ultiboard (this is my first project) but I did the the tutorial and feel somewhat comfortable with it after tinkering with it for awhile now. I drew my design on Multisim and now I'm having trouble getting my autoroute to work. It starts and is over in 2 seconds without placing a single trace. This is what I've tried so far: Adding layers, adjusting trace width, adjusting distance from pads, and toying with autoroute settings. It won't let me manually connect my nets either. I'm about to just get rid of all the nets and free hand but that would be very tedious because I have 236 connections. I've attached my file, thanks for any help.
Your default trace width is set to 8000 mil, this trace size will cause a lot of DRC errors. Turn on the Spreadsheet View if it's not already on by selecting the menu View>>Spreadsheet View, select the Nets tab and click the Trace Width heading, the column will be highlighted and when you change the width for one net the other nets will change as well. The default trace width for Ultiboard is 10mil
So I tried to use CircuitMaker's autorouter. Initially I thought it did a good job, but then I found out most autorouted tracks had vioations, so I switched on the option 'Rip-up Violations After Routing' and found out like 25%-50% was autorouted. See below.
I am sure I can improve rotating or rearranging components better, but I was hoping an autorouter could do better (or at least I hope there is 'some' solution). Afaik I have seen much more complex boards which are routed (either by hand or autorouted).
Sadly, there are a lot of inner footprint clearance violations which I don't know how to remove. See Altium's 'Ignore pad to pad clearances within a footprint' inside CircuitMaker? for a related question of me.
About the only time that would make sense is if you are doing large multi layer PCBs with thousands of nodes where you will expect a lot of changes. Manually re-routing that kind of thing would be a lot of work, so tuning the autorouter would be worthwhile.
With a board this complex, you need a policy. Simply dropping wires here and there is not going to work. I notice it's mostly DIL ICs, which means it's not an RF board. So while you still need a competent ground, you do not need a ground plane.
Now place your other tracks. Follow the same orientation on each layer, via through when you change direction, and you will always have a systematic method for getting from A to B, without topologically blocking any other connection. You may still run into crowding problems, which means you need to backtrack and change your placements.
Most/some? autorouters have an option for you to restrict tracks on certain layers, so you may be able to set up yours to follow this orientation pattern. However, working with a Manhattan layout means that manual routing is quite straightforward.
I would not recommend leaving the ground until last, and then 'filling the empty areas with copper, using vias to bridge connections between isolated polygons'. The board is so busy that you will miss something, and there is no guarantee that you can actually get ground connectivity at all. Better to start with a complete ground grid (easy to place and check), and then place a track at a time (easy to place and check).
While a two layer board is probably appropriate here, when doing one off designs the cost to go from 2 to 4 layers is often less than shipping. If your goal was to have a dedicated ground plane, and you don't want to spend a lot of time routing efficiently, using a 4 layer board would allow you to have a dedicated ground plane while greatly simplifying routing.
Things are a little up in the air right now due to corona virus, but I just punched in a 4 layer 100x100 mm board into a cheap prototyping service and it came back less than $30. I used to spend hours trying to fit parts onto 2 layers to save on 4 layer boards when they were hundreds of dollars extra, but costs have come down so far it's often not worth the time.
Set up functional blocks (I do not know if Circuit Maker permits this although it is a fairly standard part of any ECAD package these days) and place them as separate blocks (not necessarily in their final locations) and tweak any pins possible (by moving parts around within the block and / or gate swapping or function swapping as in the case of multiple amplifiers in a package) until the rats nest is the cleanest you can get for each functional block.
There are areas where autorouters do excel (high speed parallel memory interfaces with strict timing constraints come to mind); I have seen those done (as a limited set of nets for the autorouter to touch) in some circumstances. usually those nets are then locked so that once almost everything else is done you can let the autorouter do the last few tracks.
I once did a board (18 layers in that case, 95mm x 55mm) that was a GHz class PowerPC processor with 512MB DDR2 and 512MB flash (and some other bits) that exposed serial ports, PCI and PCI express to the connectors and had very complex power and sequencing requirements and we (it was a team) spent at least a week just planning the location of parts to make everything fit.
Depending on the purpose of the board and whether or not you expect it to pass certain compliance tests, it may not be necessary to have an entire layer be ground. In many cases it can suffice to route the board with traces on both sides and then fill the empty area with copper connected to ground (many CAD programs have a command to do this automatically, typically called something like Copper Fill or Polygon Pour, but I'm not familiar with what it is in CircuitMaker). It seems like the traces on your board could end up being fairly sparse, meaning you could still have a nice, low-impedance ground using the copper fill.
795a8134c1