Hi Miel, maybe mistake on my side. you need to define the constraints in a separated constraint script - not in the rigidbody itself. like this:

Hi Miel,

It seems that AGX has changed something in their API. The AGX Constraint Component appears to be missing and is somehow merged with the RigidBody. I debugged the issue but haven’t found a solution yet to access the Constraint within the RigidBody. This seems to be a recent change, as the AGX documentation still shows the Constraint Component as a separate entity.

I’ve already reached out to AGX support and hope to receive an answer soon. In the meantime, you could try using an older version of AGX if you have access to one. I would recommend using a version that’s about a year old.

Apologies for not having a direct solution right now.

Best regards,
Thomas

Hi Miel,

was not able to finish it today but I will be working tomorrow morning. Will let you know hopefully how to fix tomorrow morning.

Best regardds
Thomas

Hi,

will check it later, but would be in the evening. Received a license and will need to check.

Best regards

Thomas

Hi, you could implement your own "Behavior Model" for the Articulated body with a public PLCInputFloat.

In the fixedupdate of your code you write MyPlcInputFloat.Value = ArticulatedBody.Rotation .

This is just dummy code but I think you know how to get the correct rotation of your articulated body.

Hi, the "home" position (=position in Editor Mode) for our IK must be always this

Otherwise the IK will not work.

Ideally this would be also the OPCUA Positions where each drive has Position 0. If not you can work with Offsets in the Drives. But youh should only use Offsets for OPCUA and not for our included inverse kinematics.

Maybe it is best to define two robots. One using our IK with the correct settings and one getting the Axis values over OPCUA.

If you thing that our IK is doing something wrong (your last picture) - please send us your project where we can check this to: https://realvirtual.io/send 

Please only include what we really need and set the scene to a situation where we can see directly your problem.

So the axis positions are coming over OPCUA with a DriveFollowPosition? Easiest way is to position the axis in the OPCUA 0 Value position. But also Offset should work. Can you explain a little bit more your setup?

Hi, how long took it in total? Yes our Step file is not always very fast and it could happen that you need to wait more than 15mins for bigger files.

Hi, could you send us your file, we need to report the problem to our DLL supplier. Please send it here: https://realvirtual.io/send

Hi, for free joints you should use Unity Physic Joints, for fixed position controlled drive you should use our Drives - which are not using Physics. It is not possible to add our Drive to the Encoder you are showing.