If you would have to get a new simulation software...

ABB Robot Studio.

By far most capable and true motion representation.

If You are asking about brand specific simulators, I agree with hz69.

None of the competitors can beat RobotStudio today.

But...

It is specific to ABB robots. You can't simulate or generate KUKA code with it, for example.

I think specific simulators worth only when You have big assignments with lots of robots from the same brand.

On the other hand, there are a lot brand agnostic simulators out there, that enable You to program/simulate the most known robot brands.

I work with Process Simulate, that is a very powerful (and expensive) tool. But, sincerely, I think it is somewhat overkill on some situations.

I'm always looking at RoboDK.

Some years ago, someone start compiling this kind of software on a topic here in the forum, but looks like the post is gone, now.

Hi guys,

If you want, write me a private message with your email address and I can send you a free 30-day license of RoboDK.
You can then try and see if it fits your needs as a brand agnostic robot simulator and offline programming software. I can also send you some training material so that you can be up and running as fast as possible.

Have a great day.

Jeremy

Hi Joan,

I just answer your email.
But I feel the need to clarify some things.

RoboDK, as many other robots agnostic simulator and offline programming software, does not simulate the behavior of the robot controller as a whole.
It only simulates the movements of the robot according to the mathematical model of the robot in the controller.
We are not equipped with a "virtual controller".

On the offline programming side, our goal is to generate the code linked with a challenging path.
We can output code for any of the robot brands we support (ex Kuka, ABB, Fanuc, UR, Yaskawa, etc).

You can think of challenging paths like welding, glue dispensing, remote TCP, machining, deburring, painting, etc.

In other words, RoboDK can generate the code for the robot controller, it can even use some controller specific function, but it's not meant to go from the real controller to RoboDK.

For some robot brands, you can import hand written programs (ex KUKA) but the only thing you will really get out of it are the move commands and the position.

On the simulation side, you can create pretty much any robotic process involving robot. It can be used for reach study, cycle time study or as a selling tool.

I hope it helps clarify things.
Jeremy

Hi Joan,

Perfect, if you need any help, let us know.

Jeremy

Try using Visual Components