Hi,

best would be to do it with Game4Automation Professional and the included OPCUA interface.

With the OPCUA interface, you can get the data from the PLC and with the standard Unity UI and AR functions, you could display it on your android phone. Like in this example:

Best regards

Thomas

Hi Jeff,

you will need the Professional version because all the "advanced" interfaces are part of Professional (like the needed Shared Memory Interface to PLCConnect).

Currently the PLCConnect developers are developing a "special" Game4Automation Interface what will be a "special" PLCConnect Interface on the Game4Automation Professional side. But the current version and standard Shared Memory should also work.

I will get you a PLCConnet trial and some documentation on it. It might take until end of this week. Could you please send me your full contact data to info@game4automation.com.

Thanks and best regards

Thomas

Hi Leve,

I assume that you are having PLCInputs and PLCOutputs in your project after importing from TwinCAT:

Now you can write to the PLCInput with 

PLCInput.Value = YourValue;

You should write your own behavior scripts and attach this to the Gameobject with the rigid-body where you want to measure the velocity.

Here is a simple example of a behavior script (it is the Sensor_standard script from the Game4Auomation Framework).

This script is sending a "High" to the PLC when the sensor is occupied.

namespace game4automation
{
    [RequireComponent(typeof(Sensor))]
    //! The Sensor_Standard component is providing the Sensor behavior and connection to the PLC inputs and outputs.
    public class Sensor_Standard : BehaviorInterface
    {
       
        [Header("Settings")] public bool NormallyClosed = false;  //!< Defines if sensor signal is *true* if occupied (*NormallyClosed=false*) of if signal is *false* if occupied (*NormallyClosed=true*)
        [Header("Interface Connection")] public PLCInputBool Occupied; //! Boolean PLC input for the Sensor signal.

        private Sensor Sensor;
        private bool _isOccupiedNotNull;

        // Use this for initialization
        void Start()
        {
            _isOccupiedNotNull = Occupied != null;
            Sensor = GetComponent<Sensor>();
        }

        // Update is called once per frame
        void Update()
        {
            bool occupied = false;
        
            // Set Behavior Outputs
            if (NormallyClosed)
            {
                occupied = !Sensor.Occupied;
            }
            else
            {
                occupied = Sensor.Occupied;
            }

            // Set external PLC Outputs
            if (_isOccupiedNotNull)
                Occupied.Value = occupied;

        }
    }
}    

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.

I am closing this. We can't reproduce it.

For anyone experiencing similar issues.

Problem was that the compile settings were not set correctly:

https://game4automation.com/documentation/current/compilerdefines.html

, that collision layers were not set correctly:

https://game4automation.com/documentation/current/physics.html

and that Prostprocessing was not included in the Assembly Definitions:

https://game4automation.com/documentation/current/game4automation.html

https://game4automation.com/documentation/current/assemblydefinitions.html

Hi,

we don't know this error. Could you upload your project? I will send you via email a link for uploading.

Hi,

usually it should also work with 2019. But we recommend to use LTS (Long Term Stable) releases because Unity is sometimes changing to fast for industrial use cases. We develop and test in 2018.4. On our build server we also try to compile and build with 2019, but it is more risky that we miss something in 2019. So I would recommend to only use 2019 if you really need it.

I just checked latest release and 2019 and it works on my computer without problems. The main menu is available and the demo model is working as expected.

You should also check that you are using .Net4. compatibility level - even if this should be not an issue with the main menu. But some interfaces might not compile without .Net40

There seems to be an issue / collision with anything what is already in your 2019 project. I don't know what. Could you please check the Console log for some more information.

You can do so, but you are not allowed to use one Unity or Game4Automation license on two computers at same time.

Hi,

the license is tied to the organization who purchased the Asset. There seems to be no official way to transfer a license to another organization (e.g. from school to you personal) if you purchased on the Unity Asset Store.

You could purchase the license directly from us. For doing so please just fill out this form (Button "Request a quote" and you will get an offer: https://game4automation.com/en/buy

We could allow you the transfer if needed later on based on a simple mail you are sending to us.

Best regards

Thomas