Hi, I did checked but can't reproduce it. 

Did you maybe do the changes while in run mode? Can you send the model if the issue is still existing. You can upload your model to

https://realvirtual.io/send/

Hi,

Unity's mesh-based system offers great performance, but selecting centers can sometimes be tricky. Here are a few solutions to help you overcome this issue:

• Use CAD Design Components: Often, CAD designs include components with correctly positioned pivot points. You can use these as a basis for your setup.
• Refer to Data Sheets: For robotics, data sheets often provide precise information about pivot points and other important details.
• Build Kinematics Externally: In many cases, we construct the kinematic hierarchy externally from the design itself. Check out the Kinematic and Group Script for more information.
• Move Pivot Tool: You can use the Move Pivot
  Tool to adjust and align the pivot points of your objects.
• Kinematic Tool in Realvirtual Professional: If you're using Realvirtual Professional, there's a new Kinematic Tool that simplifies defining kinematic chains.
• Select 3 Points: With either the Pivot Tool or the Kinematic Tool, you can select 3 points to move the pivot of the kinematic hierarchy. However, this method carries some risk as there’s no guarantee that the pivot will align perfectly with the actual center of the robot axis.

PLCSim is not supported officially from our side - even if there are some TCP to PLCSIM software.

All I described is true for a real PLC. If you would need to write to a "real" input which is available in the Hardware Config you would need to use our PLCSIMAdvanced Interface. PLCSimAdvanced is another product of Siemens and totally different to PLCSIM. 

This is really a little bit complicated with Siemens - With Beckhoff for example there is one "software" and "hardware" PLC and they are totally the same. But it is like it is.

Hi Andreas,

here are my answers:

1. This behavior is by design from Siemens. It's not possible to change this. If a hardware value is at a certain level, you can't overwrite it with software.
2. This is not a bug; it's a common characteristic of all software solutions utilizing real Siemens PLC hardware. To avoid values being overwritten, you can modify your hardware configuration or use a simulated PLC.

To the best of my knowledge, you don't need to change the program itself. However, you do need to adjust the hardware configuration to ensure the symbol you are using does not conflict with a real hardware input.

Solutions that Work Without Changing Hardware Configuration for Siemens Controllers:

• Use PLCSimAdvanced
• Use Simit in Combination with a Simulation Unit

It seems the issue is that the part is being gripped by two components, which is something we currently don't support. Typically, we use a combination of a Fixer (for the passive part) and a Gripper (for the active part). In the coming days, I'll be creating a test model to explore whether we can extend the functionality of the Gripper to address this.

We wanted to let you know that we won't be upgrading because Cadenas has announced the end of support for the technology we are currently using. Instead, we recommend using 3Dfindit, where you can find a wide range of 3D components online. This platform allows you to export components as OBJ or Collada files, making it a versatile alternative.

Issue is solved with newest 2022.16 release. Please use 2022.16 Professional and 2022.16 Simulation together. On Problems when updating please also consider this:

https://doc.realvirtual.io/advanced-topics/troubleshooting

I think you are talking about the mail yesterday evening. We are working in the European Timezone. I expect that we can fix all issues and release 2022.16 today.