Proteus ARES Does Not Auto Route All Components

Hi All,

I'm seeing an issue when doing an auto route where (and it used to work), a couple of components do not route at all even though the ratsnest connects them to the correct end points. I've also had cases where I end up with an error because another track runs through the pins of the component.

One of the components footprints I created and the other is from a standard library (and used by other components). It just seems as though these two are being picked on.

Can someone point me in the right direction to solve this issue.




Regs,
Paul

Read also the following link
Auto routing would not know which placement will get you a better trace pattern which will enable you not only to make an efficient design but also to minimize noise in the circuit. Similarly auto routing doesn't know that shifting a component slightly to the left or right would enable you to route a track in a better way. These tools will just give you a design which is correct according to the circuit. But when it comes to real world performance, things are different.
For example:

• Decoupling capacitors should be physically close to the IC.
• There should be loops of least enclosed area.
• Ground plane should be as solid as possible.
• No interfering signals should be close to your crystal oscillator etc.

,https://electronics.stackexchange.c...sign-why-doesnt-auto-placing-components-exist

thannara123 said:

Read also the following link
Auto routing would not know which placement will get you a better trace pattern which will enable you not only to make an efficient design but also to minimize noise in the circuit. Similarly auto routing doesn't know that shifting a component slightly to the left or right would enable you to route a track in a better way. These tools will just give you a design which is correct according to the circuit. But when it comes to real world performance, things are different.
For example:

• Decoupling capacitors should be physically close to the IC.
• There should be loops of least enclosed area.
• Ground plane should be as solid as possible.
• No interfering signals should be close to your crystal oscillator etc.

,https://electronics.stackexchange.c...sign-why-doesnt-auto-placing-components-exist

Click to expand...

Hi,

Thanks for the reply, however it didn't actually answer my question. I'm not concerned with placement of the components, I've done this manually. My concerns are over the fact that
the auto router didn't even attempt to route the two components on the layout. I'm questioning whether anyone else has had this issue with Proteus.

Regards,
Paul

IF your happy to manually place your components why on earth are you autorouting them?

WHen you manually route your tracks "you" are in control and think of a million and one things at the same time, is it ollowing the circuit, the design rules, the dtandards, the regulations, low voltage directives, EMC etc.
AUtorouters dont think like that.

IMO Its a simple design - manually route it.

Hi,

I want to auto route as I have 226 object and a total of 707 pins, so no, it isn't a simple design. Without trying to sound "too" rude my original question wasn't answered, all I get back are lectures on how something should be done rather than either answering the question or saying "Gee, I don't know the answer, but you might try looking here" in typical forum fashion.

regards,
Paul