Hi, an Input Area of a PLC is there to be written from the Outside (sensors, buttons or realvirtual in case of virtual commissioning). 

To 1) maybe you did something wrong - you are able to clearly set signals which stay on the value from realvirtual.io. We provide realvirtual.io Support Hours for teaching you the basics if needed

To 2) there is no right way for doing it. Usually there is a company plc programming standard. from our side you can read and write to M, DB and to Inputs (only write) and Outputs (only read). The rest is up to you to decide depending what you want to do on the PLC side

To 3) No - realvirtual.io is made to support all possible customer standards. we are not experts in PLC programming, this is usually done on the side of our customers. 

Honestly I don't kow in detail your setup so hard to answer. For sure there is no a very basic bug in our interface. PLCInputs are purely for writing to a PLC, PLCOutputs are purely for getting signals from a PLC. Sometimes PLC code or hardware inputs are overwriting values if wrongly configured but it is hard to give a detailed answer based on your setup.

Hi, this is exactly what a PLC is used for. There is a logic inside the PLC to react on Inputs and based on custom logic set the outputs. There is no real use case for an Input directly setting an Output. If you need some more deeper PLC Knowledge we have partners providing custom online training.

This is usually like this in all automation systems. Outputs and Inputs are clearly separated (also for security reasons). You can only write to outputs and read inputs on a PLC or RobotController.

can you explain a little bit more. What is exacly your setup - how is a Input modifying the output?

Hi, this is a PLCOutputBool so it is going from the PLC to Unity. You can only toggle from Unity Side PLCInputBools (which are signals from Unity to PLC).

For everybody who needs it - we have a patch for Unity2022. In the next realvirtual 6 release there will be an update also supporting Servers with a large number of MQTT Topics and better failure handling for unsupported datatypes. Also BestMQTT Dependency will be removed.

I will send you a patch for testing. With the patch you are able to limit the number of imported topics and null messages and unpossible date formats are automatically filtered. You will get a private message.

OK, understood. Do you import during PlayMode? Currently implementation is not supporting to import signals during play mode because subscription and signal preparation is done when interface is getting connected which is usually when starting play mode.