Motion

Motion axes are modeled by connecting Drives to GameObjects. The Drive will move the GameObject, including its sub-components, along a defined rotational or linear axis. The Drive is a base component with some generic Drive behavior but it does not expose a Signal interfaces to a PLC. For this a Drive Behavior script is added in addition to the Drive script for the GameObject. The Drive Behavior includes special behaviors (such as pneumatic cylinders or position controlled drives) including any signals supporting the special behavior.

The standard units for drive positions in all realvirtual.io components are millimeters for linear drives and degrees for rotational drives. The standard units for speeds are millimeters per second and degrees per second. In Unity, each millimeter is represented as one Unity unit (which means what you see in the Transform component in Unity is in meters). You can adjust the scale in realvirtualController, but this is generally not recommended.

This Youtube tutorial shows how to define Drives

Tutorial Adding Drives

We supply seveal standard Behavior models, but due to the large variety of automation devices and functionality, it is most likely you will need to add your own behavior models.

The next image gives a good overview of Drives moving GameObjects. The Drive is contolled by a special Drive Behavior which is connected to one or more Signals. The Signals are then connected to a PLC (using an Automation Interface)

© 2022 in2Sight GmbH https://realvirtual.io - All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including printing, saving, photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher.