Stand alone Router compatibility
I have been using the pro version and have discovered some issues with its autorouting engine that I have reported HERE It is clear that the Pro version and standard versions do not share the same autorouting engine, and that the more mature standard local routing engine is far superior. I would even go as far as to say that the Pro version autorouting engine is beta level software at best. I would therefore like to propose that the option to use the existing mature local autorouting engine be integrated into the pro version. I assume that as the local autorouting engine is a standalone program it accepts an input from the editor and should therefore not be too difficult to integrate. Alternately if this is not possible can some clarification on how the local autorouting engine can be used as a workaround. i.e. is there a workflow that allows the project to be exported, run in the local autorouting engine and then reimported? /DM #FeatureRequests#
Auto Router completes but does not route all nets
Hi all. I've been using the desktop pro version to update an older project previously designed with the original online standard editor. The Editor is definitely nicer to use although the workflow of some aspects take a little getting used to. I have now however stumbled onto an issue. When autorouting I have found that in the pro version the process finishes but does not route 100% of the nets. The best I have managed to do is about 86%. No amount of manually moving and reorientation components or adjusting the routing rules will get it to complete 100%. So as a test I exported the project as an Altium package and then imported it into the standard version. I then re-tried autorouting and the project completed 100% with no issues, even using cloud autorouting. The autorouting engine is visually different in the pro version as the nets are routed at 90 degrees even though 45 degrees is selected and then at the end of the process the 'corners' are swapped to 45 degrees. Clearly the engine in the pro version is different from that used in the online and local routing engines and it does not appear to route correctly. Pro version routing .... Regular version routing .... Both are set to route at 45 degrees. I'm not sure if this is an environment issue, or that the pro version router is less permissive in its operation. However the standard version appears to be heaps better and far more refined. It also generates a result. So I have the following questions Assuming it's a setup issue, how can I set up the pro version auto routing to act the same as the regular version. Is this even possible? Is there a workflow where I can achieve the same outcome or perhaps use the existing local EDA router? Is this problem a known issue / limitation? I am happy to invite support to the project if you think that it's a project issue, but it is not a public repo so I am unable to share it here I'm not really interested in people telling me that I should manually route it. Some aspects of the project are manually routed prior to auto routing the rest, but the issue remains that the pro router fails to route what is a pretty simple project even without predefined manual nets. Thanks in advance. /DM #PCB#
Autoroute not avoiding component holes
Hi I have just noticed that autoroute is ignoring mounting hole in one of the components. Previously this was not a problem. It seems to be a problem since the last update I've manually adjusted the routing, but have already placed order for boards as I did not notice this. (Always been okay with this component - new version was only minor revision to existing design) Please advise. #PCB#
Autoroute - Prevent tracks merging
Hi. I am trying to run two small tracks from adjacent pins on a pin header to a device to help load share (rather than one large track - which fails auto routing) but when I run autoroute the two tracks merge at the pins and only one track is run to the device. Each pin has a unique net name, but they run to the common pin on the device (see below) Is there any way to force this behaviour when using auto-routing? or does anyone know of a workaround? I appreciate that I can route these manually and then lock them, but that is too labor intensive and is something I would like to avoid if possible. Thanks in advance. /DM #GeneralDiscuss#