Your comments

Hello Bo,
We have fixed the bug. You have received an update for your version by email. The bughas been fixed for further downloads.

Hi, the number of signals is not an issue, I have seen models with more than 1000 signals. Have you tried changing (reducing) the MaxPdu Lenth (e.g. to 40). Did you tried the AreaReadWriteMode (but I don't know if that works with nettoplcsim).

Hi Bo, can you send an example project with just one scene in where we can debug the issue?

Hi Bo, based on your picture it is not totally clear to me. In general physics and colliders is not always behaving like reality so very often some simply dummy colliders (best for performance is box colliders) are needed.

In realvirtual.io Professional, inverse kinematics for robots is included. You can also use an external tool like RobotDK or ABBRobotStudio to move the robot. These interfaces are also included only in the Professional version. The Starter version does not include a solution for inverse kinematics - not even the ABB RobotStudio or RobotDK interfaces. For this reason, we used Unity animations to set the robot in motion for the generic demo model. However, this is a relatively inconvenient task to move all axes to reach a certain position.

@Brian: Did you also made the changes in SceneMouseNavigation.cs as described below?

Hi Adam, yes please, if you have a solution or know an alternative library, please mail what you can share to info@realvirtual.io. Thanks a lot.

Please check the demo model or this demo which shows several ways for gripping parts: Assets/game4automation/Scenes/DemoGripping.unity

To make the conveyor stop you can use a script (you need to check the property occupied of the sensor and you can stop the drive by Drive.JogForward = false.


Or you can use Unitys Visual Scripting:

https://realvirtual.io/documentation/current/unityvisualscripting.html

Another possiblity (only with Professional Version) is to use LogicSteps:

https://realvirtual.io/documentation/current/logicsteps.html


You can stop the Conveyor (in a script or by using visual scripting) as soon as Drive.CurrentPosition is greater than a certain value.


I changed some things in our code - it's certain that the certificates didn't work after switching to LibUA- but I still have the problem to generate a working certificate. See the posts here:
https://github.com/nauful/LibUA/issues/94

So for now, I don't have a solution. If you want, you can test it yourself and I'll give you the beta version where I still get the missing CRT message.


Best regards

Thomas