You need to define it as PLCOutput not as an Input.

Hi, it is hard to say what the problem is. Generally we only support and test with the latest Unity LTS Release (which is Version 2019.4). I am sure that you could get it running with 2020 but that might require some changes.

If you don't get it working with 2019 you could send me your project and I will check what the problem is.

Best regards

Thomas

Hi Jacob,

if I understand you right you will need to have a limit to the number of monitored items per subscription. We could generate a new subsription when we are reaching this limit.

Currently there is only one subscription for an infinite number of monitored items.

If I understood you right we are going to put this into the next release. Planned for end of september.

Best regards

Thomas

Nein leider nicht. Es gibt mehrere möglichkeiten einen Roboter bewegen zu lassen. Die beste ist eine externe Inverse Kinematik zu verwenden (RoboDK, ABBRobotStudio....) in der man die Roboterpositionen an einer Robotersteuerung teacht. Der Roboter in Unity ist dann mit den einzelnen Achsen der Robotersteuerung verbunden.

In Game4Automation selbst ist keine Inverse Kinematik enthalten. Hier kann man nur die einzelnen Achsen verfahren was relativ mühsam ist. Im Demomodell haben wir das so gemacht un in einer Unity-Animation die einzelnen Achspositionen festgelegt.

Hi, I just checked.

It is not possible but it will be feasible with some work. We are planning this for the next release. Because of summer vacation this will be available around end of September.

Best regards

Thomas

I need to check next week if and how we can enable that.

Did you tried to create the PLCOutput object manually - instead of importing it via the symbol table?

No URP seems to work. But the same issue with demo scenes - they are build based on the default render pipeline.

Do you need OPCUA and HDRP in your project?

We are working on the next Update of our OPCUA interface which should be Hololens2 compatible. We will try to solve in this update also the HDRP issue for OPCUA but it might take some weeks.

The OPCUA interface seems not to be compatible with the HDRP render pipeline. If you delete the folder OPCUA4Unity game4automation should work. But all demo models are built for the default Render Pipeline.

The reason is the System.Private.ServiceModel.dll which is needed for the OPCUA dll.

I have no short term workaround for this and I hope that you don't need OPCUA in your HDRP project.