Thanks, will check this later today.

Can you provide us your ABB RobotStudio project or a simplified example and we will check?

Please try the current G4A professional beta on our download page  https://game4automation.com/download/customers/  we did some changes on the OPCUA side.

Please also check this thread - maybe it is related to the security policy ID. In the new beta there is an additional setting for Security Policy ID - please try to change this to 1 (instead of a 0).

We are not deep experts in ABB  robotsudio and did on our side only a small test project. On the G4A Side all I can say is that you need to enter empty signals so that the structure is without emtpy bits and bytes. Some information about the configuration (Simit is using the same interface) can be found in this video:

https://search.abb.com/library/Download.aspx?DocumentID=9AKK107492A4208&LanguageCode=en&DocumentPartId=&Action=Launch

Hi, not all Interfaces are working on all Platforms. Unity is cross compiling to the destination platform but sometimes we need windows specific DLLs. PLCSim Advanced is not working on Android. But you could connect to it using the S7 interface. More information about platform limitations can be found here:

https://game4automation.com/documentation/current/platforms.html#Known-platform-limitations

Best regards

Thomas

Hard to say what your problem is. Yes for sure, Starter is supporting S7 interface. 

Is it an input or an output what you would like to use. Please make sure, that both are well outside the existing hardware IO adresses, otherwise the hardware status could overwrite the signals from the G4A S7 interface. Do you get any error messages in the console log. Please also check that your PLC is configured like described here:

https://game4automation.com/documentation/current/s7tcpip.html#Configuring-the-PLC

Hi, 

did you use the function Parent Drive, please check our demo scene under Assets/game4automation/Scenes/MovingTransportSurface.unity where a rotating transport surface is done. 

The Transport Surface has to be in parallel (not as a children) to the rotation drive. And in Parent Drive you need to reference in the Transport Surface to the Rotation Drive. This is necessary due to some limitations in Unity Physics. A "IsKinematic" movement can't be combined with a physical movement (like the transport surface) in a hierarchy.

We don't need it there because the CAD users don't have AML exporters in the project (and even not the kinematic information in the CAD) - so STEP and defining everything in G4A is fine for our current research project (as well as for most of our users).

I think there are two main reasons why AML is so uncommon:

- very complicated format (specification is hard to understand even for myself....)

- there are no exporters available - this is main reason why nobody is using it and there are no importers)

My favorite would be to define an open and easy standard like a JSON together with a Step CAD export. The simple JSON export would be easily implemented by macro programming in most CAD systems. If you are interested in this we can cooperate - we have first drafts for it but so far nobody who implements the CAD macro.

The focus in our research project changed, AML is not needed any more, so an official AutomationML interface is not planned any more. In general I am missing very much the availability of AML exporters for common CAD systems. As soon we see, that there affordable standard exporters available (besides the very special solutions for automotive) we will change our mind. But you are free to develop your own importer - it should be not to much work because reading in XML and Collada into Unity should be very easy.