No we don't send out pulses so far on a drive. But it should be simple to add. I only see a problem if drive is to fast. Pulses could be needed faster than communication cycle is.

Thanks a lot for the positive feedback. We are not planning to do that. The Starter version is meant for for free usage. In very rare cases we are developing things together with universities, companies or students in bachelor thesis and in this case we are suppling for free licenses based on special test contracts.

Best regards

Thomas

No WebGL is not supported - sorry. I also think that communicating in a Web application over OPCUA might also be not wished from the security point of view.

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