This guide will cover constructing a model, adding controls and controllers, setting up PLC Inputs and Outputs on the components that need them and finally running and testing the model.   In this article a simple model using standard Experior components will be built and the guide will provide more information on some of the properties used by those components.   This is a screen-shot of what the model looks like when finished. Note the tracks are gold because they are locked in place.     Building the Model   To begin select the Basic catalog by clicking the tab Then click and drag a Conveyor (Straight) into the construction area Adjust the length of the straight by either clicking and dragging from one of the endpoints or by selecting the straight and in the properties window scrolling down to Position and changing the first number in either the Start or End row to adjust the length As a note, tracks, by default, run from the red point to the blue point, so when attaching additional items opposite coloured points must be snapped together to ensure the model flows correctly Next a motor should be added to the straight To do this select the straight and right click it Then move down so Insert Motor is highlighted and then move across to Surface so that is now highlighted and finally click New   Note the arrow that appears, this is the motor and indicates the direction in which it will be driving the conveyor A feeder now needs to be added to the conveyor, so once again right click on the conveyor, move down and click Insert Feeder     Lastly a sensor needs to be added To do this click on the Sensor tab in the catalog area and then click and drag a Photoeye into the working area When dropped reselect the photoeye and drag it to the edge of the conveyor so that it also becomes highlighted as shown   Now press the CTRL button and the photoeye will automatically align and re-size itself so that it fits across the width of the conveyor Now a curved section of conveyor will be added to the blue end of the straight In the Basic catalog find the Curve(Clockwise) item and drag it across into the working area Drop it away from the straight so it can be worked on first Select the curve so that it is highlighted In the Properties panel scroll down and find Yaw under the heading Orientation Change this value from 0 to 180 Now select and drag the curve to the blue end of the straight so the the blue and red points overlap and turn a pinkish colour Hold down CTRL when and it will snap the curve into place Lastly a motor needs to be added to the curve To do this select the curve and right click it Then move down so Insert Motor is highlighted and then move across to Surface so that is now highlighted and finally click MOTOR1 This then adds a motor to the curve which shares the properties of the motor that was added to the straight     Next a straight with a slight incline needs to be added As before select and drag a straight onto the working area Before connecting it to the curve, select it and in the Properties window scroll down to Position Adjust the second value in the End row to 1470, this changes the height at the end of the straight   Now the straight with an incline can be attached to the curve Now add a motor to the straight Add MOTOR1 in the same way as detailed for the curve above The next 4 parts to be added to the assembly are 2 curves, 1 straight and a photoeye sensor to go on the straight They will need to have their height adjusted to match the end of the straight that was just added The height of the parts will be 1470 and the value that needs modifying is the second one in the Position row These 3 parts will also have motors, to be added as MOTOR1 as before Finally two more straights need to be added, one with a downward slope and one short straight For the sloping straight the height should first be made 1470 in the second value of the Position row, then modify the second value in the End row to be 820 Next scroll down the Properties to Friction Expand the section by clicking the arrow on the left Next using the Coefficient drop down change the value to Slippy This straight will not have a motor as a gravity lane is being simulated here     Insert the last straight and ensure the height is set at 820 and link it to the downward sloping straight Add MOTOR1 to the last straight   Adding Controls Now some basic controls need to be added to the model. The Control Panel is located directly below the Catalog/Communications pane. Firstly a 2 state switch to control the motor should be created Select the first empty square in the Control Panel, move down to Switches On the pop out move across to 2 States and then on the final pop out select Classic   Now add a lamp, this will be used to show when a load has entered the simulation On the second empty square in the Control Panel select it, right click and select Lamp on the drop down   Lastly a simple push button will be added. This will be one method of introducing loads into the simulation On the third square select it, right click and then scroll down and select Button to insert a push button   To rename the controls to make them more easily identifiable, select them and in the Properties pane under Appearance change the Name field   Adding Communications and Symbols   Some of the items in the model have yellow triangles with exclamation marks in them next to them.   The reason for this is because the items or controls are waiting to be linked to a PLC and have either an Input or an Output associated to them.   For the purpose of this exercise three methods for testing inputs and outputs within Experior will be covered. These can be used as a temporary stopgap if you don’t have a PLC, SoftPLC or Controller available for testing. Click on the desired method, follow the guide and return to this guide when ready to run the simulation: Siemens Fetch & Write Adding an OPC Server and Symbols   Running the Simulation To run the simulation the communication device(s) must be connected and running If using the Fetch/Write method then in the Communications pane double click on the Write device and then double click on the Fetch device If an OPC Server is being used then it should automatically connect when the model is loaded, otherwise double click the OPC line in the Communications pane The Communications pane should now look like this:   Now press the Play button located at the top of the screen to start the simulation   Click the Motor Control switch into the ON position, so the arrows representing the motors change colour from red to green signifying that the motor is now running Press the Feed Load button to enter a load into the system and watch it as it passes through the system Note how the lamp lights as the load passes through the first sensor Also note how when the load passes through the second sensor a new load is introduced into the system

These articles will go through building a basic routing model and coding a simple controller in the Discrete Events mode of Experior.   Building the Model   Open Experior using the config shortcut Select the options as shown below when the start-up screen appears   The screenshot below shows the final layout of the model Note the positions of the action points and their names   To begin select the Track catalog by clicking the tab Then click and drag a Straight into the construction area Adjust the length of the straight by either clicking and dragging from one of the endpoints or by selecting the straight and in the Properties window scroll down and adjust the value in the Length field As a note, tracks, by default, run from the red point to the blue point, so when attaching additional items opposite coloured points must be snapped together to ensure the model flows correctly Add the rest of the components, re-sizing as necessary To join the components together move them together so the the blue and red connection points merge, while holding down CTRL to snap the two components together To merge components to make diverters, simply drag one component over the other until both highlight, then hold the CTRL key to snap them together   To add an Action point right click on the component on which you want the Action point and selecting Insert Action point and then click Action point The Action point is represented by an X, initially in the center of the track   The Action point can be moved and modified by selecting it and editing the properties The ones needing to be changed as part of this exercise are outlined     You can add more than one Action point to a component Use the Distance property to ensure they are spaced apart correctly It is recommended to add them and position them one at a time so they don’t end up on top of each other Add a feeder to the first straight, by selecting the straight, right clicking and selecting Insert Feeder The properties for the Feeder should be as below As with the Action point, the properties that need changing are outlined in red   Once the model is built and all action points are added and named as in the initial picture, click the Routes tab and it should look like the one below   Creating the Controller Within Experior a simple controller can be programmed to dictate the actions of loads when they reach certain action points on the route The code has been included below in its entirety with comments to provide guidance in what the code is actually doing First, open the controller tab in Experior. It’s located on the same pane as the Model Construction area.   Copy the code below and paste it into the Controller pane so that it overwrites the default lines already present public class Main { //This line is autogenerated as part of the model. public void Arrived(INode node, Load load) { //If the Actionpoint is named CHECK then if (node.Name == “CHECK”) { //Generate a random number from 1 to 5 & if the number equals 3… if (Experior.Core.Environment.Random.Next(1, 5) == 3) //…move the load to Actionpoint REJECT1… load.MoveTo(“REJECT1”); else //…if the number is not equal to 3 move the load to Actionpoint ROUTE1 load.MoveTo(“ROUTE1”); } //If the Actionpoint is named REJECT1 then… if (node.Name == “REJECT1”) { //…remove the load from the model/system load.Dispose(); } //If the Actionpoint is named ROUTE1 then… if (node.Name == “ROUTE1”) { //Generate a random number from 1 to 5 & if the number equals 3… if (Experior.Core.Environment.Random.Next(1, 5) == 3) //…move the load to Actionpoint INSPECT1… load.MoveTo(“INSPECT1”); else //…if the number is not equal to 3 move the load to Actionpoint INSPECT2 load.MoveTo(“INSPECT2”); } //If the Actionpoint is named INSPECT1 then… if (node.Name == “INSPECT1”) { //…move the load to Actionpoint ROUTE2 load.MoveTo(“ROUTE2”); } //If the Actionpoint is named INSPECT2 then… if (node.Name == “INSPECT2”) { //…move the load to Actionpoint ROUTE2 load.MoveTo(“ROUTE2”); } //If the Actionpoint is named ROUTE2 then… if (node.Name == “ROUTE2”) { //Generate a random number from 1 to 5 & if the number equals 3… if (Experior.Core.Environment.Random.Next(1, 5) == 3) //…move the load to Actionpoint REJECT2… load.MoveTo(“REJECT2”); else //…if the number is not equal to 3 move the load to Actionpoint PACK load.MoveTo(“PACK”); } //If the Actionpoint is named REJECT2 then… if (node.Name == “REJECT2”) { //…remove the load from the model/system load.Dispose(); } //If the Actionpoint is named PACK then… if (node.Name == “PACK”) { //…remove the load from the model/system load.Dispose(); } } }   What the code basically does is randomly determine where loads should go if the Action point has more than one destination More advanced controllers can be scripted using Visual Studio. This topic is covered here: Build a Controller When the code has been entered into Experior, press the Compile button to compile the script   Now when the model runs loads, it will act according to the Controller code   Running the Simulation   Introduce loads to the system by selecting the feeder and pressing the Space bar Next, under the Model menu, press the Running Man button so that it turns blue Finally press the Play button to run the model

The Accessories Catalog is accessible in both Physics and Discrete Events Mode.     Its purpose is to allow users to import custom items for use within models, but with only very basic properties as opposed to coding a custom catalog item for example.   To import an item, right click within the catalog and select Import.   The supported file formats for import are shown in the drop box in the bottom right of the import file dialog.     One thing to bear in mind when importing CAD files is that the dimension units will differ between it and Experior.   That is to say the CAD drawing will generally be measured in metres while Experior components are measured in millimetres.   This could lead to the item, when dragged into the model, being to large for the floor and needing re-sizing for it to be visible on the model.  

Introduced in Experior build 47248 the measure feature can be used to calculate the distance between 2 objects.   The Measuring feature can be found under the Tools menu in the Options section.   To activate click on the measuring tape icon so that goes from being black and white to color.   Now click on the component you want to measure from so that the measuring line appears.   Then click on the second component and the distance between the 2 is shown below the line in between the 2 objects.

The messages/telegrams are typically written as part of the PLC/Controller code or a custom dll file that gets added into the Experior model.   Within the dll code the different types of telegrams are generally coded as case statements, the case being the identifier used within the Validation file in Experior.   Adding Validation in Experior   To add a message/telegram for validation in Experior the following must be done: Open the model, if the model is locked, you must unlock it before proceeding You can tell if the model is locked by the padlock icon on the very top toolbar being closed   Unlock the model by clicking the icon, it now changes to that of an open padlock   In the Solution Explorer pane right click on MVT and select New   A new validation template is created. It can be re-named by double clicking it and typing in a new name Right click on the newly created file Select Edit, the validation template opens   If you wish to add a new message validation check, click the green + at the top of the screen.   A new block with a length of 3 appears, initially defined as ASCII (by the A in the center of it).   To re-size the new block just added, select it so the border becomes blue and then click and hold down on the right hand edge The cursor should change to look something like ←|→, then simply drag to the left or right until the size is as required Now double click on the selected block to bring up the properties Under the Format tab of the properties are options for modifying format of the particular telegram/message section   Under the Padding tab select the value according to how the telegram is setup   To add another block on the same line, ensure the first one is deselected (black border) and right click and select Add The 3rd block, generally, contains the message/telegram identifier Add the block as normal and re-size if necessary Then right click on it and select Identifier   Now double click to open the properties for that block and there is now an Identification tab available Click it and then enter the 3 character code identifier for the message/telegram   Now the block has a red outline with the 3 character code below it   Now just add the rest of the blocks as required so the validation fits the telegram it refers to            

When running Experior in Discrete Events Mode and, for instance, testing communications between controllers and warehouse management systems, it is possible to record a telegram sequence.   In some setups it can be very difficult to reproduce a specific error/exception when a WMS/MFC is controlling the model. This is because it demands that the high-level controller has to have the ability to go back to a well known state and then be deterministic when the test is repeated.   All incoming messages (on high-level connections like STX/ETX) are recorded if the feature is turned on.   All messages are recorded with a time stamp, a telegram sequence can then be replayed, once the recorder has stopped   When the Replay is started, it is controlled by the model timer, and then the different connections receives messages in the same way and at the same time as when the WMS/MFC was on-line (note: the Replay can only be started if the elapsed model time is 0).   The last menu item in the communication context menu is for saving a recorded telegram sequence. The telegrams are listed chronological in a text file.  

It may become necessary at a point during development to merge two models. This section provides a brief walk-through and example of how to do this.   Open the model you want to merge into   With the model open click the Merge button under the File menu     Select the model you want to merge into the currently open model and click OPEN When the message appears asking if a new section should be created for the merged assemblies   click YES The merged assembly now appears in the build area   In the Solution Explorer select Merged1.   In the properties the rotation, size and position of the merged assembly can be altered   Control Panels merged into an existing model can have the same name as one of the Control Panels (a tab page) that already exists   Before starting the merge process Experior will now verify if the model that is being merged contains one or more connections that already exists in the current model. The user is then asked if the merge process should be terminated

A collection of assemblies (or a group of assemblies) can be saved in “My Catalog” to enhance re-usability.    In the picture above a photo eye and a conveyor are grouped together and saved in “My Catalog“.   Organizing the “My Catalog” To organize “My Catalog” items please switch to the tree view mode. To change the name or if you want to delete it then right click on the assembly and use the context menu.   To organize the assemblies sub folders can be created (sub folders can be renamed or deleted in the same manner).   Just drag the assemblies between the sub folders or back to the “My Catalog” parent folder.   Note: The items in the “My Catalog” folder just reflect the folder structure in the MyCatalog folder of the working directory of Experior.   This means that you can share the saved collection or group of assemblies just by copying the files!  

Scripting allows you to make demonstration models that can run without being connected to a PLC.   The model below has been set up with a script that allows the motor to start when a load activates the first sensor and a new load to be released when the load activates the second sensor.   Open Experior in Physics Mode Place two basic conveyors on the 3D scene and add a motor to the conveyors For the second conveyor instead of adding a new motor select MOTOR1 from the context menu Place a photoeye from the sensor catalog at the red end of the 1st conveyor and one in the middle of the 2nd conveyor Pick a feeder from the basic catalog and place it above the photoeye in the 1st conveyor’s red end   Switch to the scripting tab and enter the code as shown below public void On(object trigger, string symbol) { if (symbol == "SENSOR1") { Motor.Start("MOTOR1"); } if (symbol == "SENSOR2") { Assembly.Activate("FEEDER1"); } }     Press F5 to compile the script Switch back to the model Press P to activate run mode Release the first load by double clicking on the feeder The motor starts and when the first load activates the sensor When the load activates the second sensor a new load will be released   Target Methods   In addition to the default target methods, you can add the methods listed in the tables below from the context menu which is accessed by right clicking in the scripting area.     Motor Started: Use if you want to be informed when a motor starts. Input Changed: Use if you want to be informed when a defined PLC output changes value. Value Changed: Use if you want to be notified when a defined PLC output changes status (only relevant in connection with I/O registers). Position Changed: Use if you want to be informed when an assembly changes position. Message Received: Use if you want to subscribe to telegrams which are received at the connection in question (can only be used with STX/ETX and RFC1006 connections). Telegram Received: Use if you want to subscribe to telegram received events. Step:  Called at every frame update. Activation Assembly specific method, only used for certain customized assemblies.   Script Methods   From the script environment you can access all public classes, methods and properties in all the different plugins and catalogs that are linked to Experior.   There are some static classes that makes it easy to make a script. This is not an object oriented approach but for some situations this is okay.  

The example below illustrates how to control a grouped assembly with a simple script.   Open Experior in Physics Mode Build a model using two conveyors, one photoeye sensor and a pusher   The pusher is located in the Advanced Catalog The pusher should be added to the side of the first conveyor so it is adjacent to where the second conveyor intersects on the other side Under the Edit menu click Select All                 Now right click on the selected assemblies and select Group   Select SENSOR1 in the Solution Explorer   In the Properties under Scripts -> Event open the editor for the Entering event   Complete the line by selecting “PUSHER1”   Press F5 so the script compiles Close the script editor Right click on the grouped assembly and choose “Save in My Catalog“   Now when a load activates the sensor it triggers the Entering event which activates the pusher

Normally Loads are created by a Feeder.   A Feeder can be added by either: Right clicking on the track/conveyor and selecting Insert Feeder from the context menu Dragging and placing a feeder from the Basic catalog. This is only possible in Physics mode   The only difference between the two types of feeders is that the feeder from the catalog can be re-sized and re-orientated and be freely moved about the model.   All other configurable properties are identical between the two.   The feeder can be used to feed loads into the system in two ways: Set up the feeder properties for Automatic Feeding Use the Feed property under PLC Outputs to setup a output symbolic to trigger the feeding of a load by, for example, a button push   The type of load being generated by the feeder can also be changed and configured.   In the Feeder properties under the Load category you can use the Type field drop down to select the load type.   The other properties in this section can be used to change the loads dimensions & orientation, its density and rigidity, the loads center of mass and its color.    

Action Points are the nodes in the route graph. You can give a load a destination and based on the route graph the shortest path is calculated.   When a load arrives at an Action Point the load can stop and pass that event onto a controller/script.   To add an Action Point, right click on the component on which you want the Action Point and select Insert Action Point. Then click Action Point. The Action Point is represented by an X, initially in the center of the track.   You can move the Action Point along the route (by moving the mouse).   The Action Point can be released from the route by holding down the ESC key (release the ESC key again to drop the Action Point on a different route).   While moving the Action Point along the route, you can hold down the CTRL key to move the action point a step of 100 mm.   The properties for the Action Point are defined as follows:   Identification Name – Customizable name Type – Catalog reference   Operation Enabled – Set to determine whether Action Point is enabled or not Collision Mode – Should the load arrive at the leading, center or trailing edge of the Action Point Highlight – The load gets the same color as the Action Point (only usable if the Stop Mode is set to anything other than “None”) Stop Mode – Defines the behavior when the load arrives. Choose from None, Stop, Capacity, Interval or StopMotor: None – The load just passes the by Stop – The load stops when it arrives Capacity – Defines how many loads that may leave the action point per minute Interval – The loads stop for a period of time (can be controlled by a normal distribution) StopMotor – The motor that controls the routes is stopped (all loads on the route are stopped) Capacity – Loads/Min. Disabled if the value set to zero (only usable if Stop Mode set to “Capacity”) Distribution (only usable if Stop Mode set to “Interval”) Mean (µ) – Set the mean value Std. Deviation (σ) – Set the value for the standard deviation Base – Select the base units. Choose from Neutral, Millisecond, Second, Minute or Hour Default Destination – If a load without a destination is arriving at the Action Point, its next destination is defined by this property.   Position Distance – The distance for the start of the track to the position of the Action Point   Scripts Events – The events “Arriving” and “Leaving” can be handled by a script (this is an alternative to the script or controller)   Statistics Enabled – If this is enabled every load that arrives is counted and is visible in the report   Visualisation Colour – Select the colour of the Action Point Visible – Select whether the Action Point is visible or not

In Physics Mode motors can be added to tracks.   To add a motor to a track you, select the track and right click.   Select a motor from the context menu.   When a motor has been added to a track, it will be listed in the motor menu as Motor1 and so forth according to the order in which they are added.   The numbering runs across the different types of motors.   A motor can be used on an unlimited number of tracks.   After a motor has been added to a track, it will become available to other tracks through their context menu and properties window in the motor menu drop down list.                     A motor is visualized by an arrow that points in the traveling direction.   The arrow is red when the motor is stopped and green when the motor is running.   The default motor direction is from the track’s red fix point to its blue fix point.   To start/stop a motor for standalone test purposes, either right click on the arrow and select start, double click the arrow or select it and press the plus (+) key.   Selecting the motor and pressing the minus (-) key will change the direction of the motor.   When the same motor has been used on several tracks, start, stop and change of direction will apply to all identical motors.   There are several different types of motor available for use: Surface Motor – A surface motor moves loads. Vector Motor – A vector motor lets the track ascend and descend. The direction angle for a vector motor can be defined in the properties. In the operation menu you set the x-y-z coordinates in the direction property. Rotation Motor – A rotation motor lets the track rotate horizontally. After a rotation motor has been added, you will find a rotation property in the motor menu in the properties window for the track, where from you can select the rotation motor’s position on the track. Eccentric Motor – An eccentric motor lets the conveyor move from a fixed angle. After an eccentric motor has been added, you can set its fixed angle, in the properties window for a conveyor, to be at the start, end or center of the conveyor. Vertically fixed angle lets the full length of the conveyor ascend/descend. In the properties window for the eccentric motor you can set a limit value (mm) for the +Y direction and the -Y direction, and disable/enable automatic stop.   Modes All motor types have four different operation modes. Operation modes are accessible through a motor’s properties window. When Experior is connected to a PLC, you can set up the motor modes according to the tables below.   The following tables shows the four different Experior motor modes that can be used for interpreting the PLC’s motor inputs and outputs (note that the modes works differently when the Frequency Converter is enabled).   Without frequency converter   Normal Forward = 1, Backward = 0 -> forward direction Forward = 1, Backward = 1 -> forward direction Forward = 0, Backward = 1 -> backward direction Forward = 0, Backward = 0 ->  stop Stop Forward = 1, Backward = 0 -> forward direction Forward = 1, Backward = 1 -> stop Forward = 0, Backward = 1 -> backward direction Forward = 0, Backward = 0 -> stop Two Modes Forward Speed1 = 1 -> motor runs forward at speed1 Forward Speed2 = 1 -> motor runs forward at speed2 Backward Speed1 = 1 -> motor runs backward at speed1 Backward Speed2 = 1 -> motor runs backward at speed2 Forward/Backward Start = 1, Forward = 0, Backward = 0 -> stop Start = 1, Forward = 1, Backward = 0 -> forward direction Start = 1, Forward = 1, Backward = 1 -> ignore Start = 1, Forward = 0, Backward = 1 -> backward direction Start = 0, Forward = 0, Backward = 0 -> stop Start = 0, Forward = 1, Backward = 0 -> stop Start = 0, Forward = 1, Backward = 1 -> stop Start = 0, Forward = 0, Backward = 1 -> stop   With frequency converter Normal Start = 1, Reverse = 0 -> run forward Start = 1, Reverse = 1 -> stop Start = 0, Reverse = 1 -> run backward Start = 0, Reverse = 0 -> stop Two Modes Forward Speed1 = 1 -> motor runs forward at speed1 Forward Speed2 = 1 -> motor runs forward at speed2 Backward Speed1 = 1 -> motor runs backward at speed1 Backward Speed2 = 1 -> motor runs backward at speed2 Forward/Backward Forward = 0, Backward = 0 -> stop Forward = 1, Backward = 0 -> forward direction Forward = 0, Backward = 1 -> backward direction   (note: the direction can’t be changed before the motor is stopped – the feedback signals can tell when the motor is stopped)  

Tracks are usable in both Physics and Discrete Event Mode.   In Discrete Event Mode the tracks are the base components for doing discrete simulation.   The idea is to route loads around in a network for routes.   By connecting routes (snapping tracks together) the route graph is calculated based on the nodes (action points) in the network.   Tracks, by default, run from the red point to the blue point, so when attaching additional tracks, opposite coloured points must be snapped together to ensure the model flows correctly.   To join the tracks together, move them together so the the blue and red connection points merge, while holding down CTRL, so the two components will snap together.   To merge tracks drag one track over the other until both highlight, then hold the CTRL key to snap them together.  

Some assemblies have embedded help information.   The information can be instructional or even dynamically updated if the state of the assembly is changed.   The popup appears every time the assembly is selected (if help information is created).   The popup closes automatically after 10 seconds if the Clock icon is checked.   The popup can be hidden permanently if the Don’t show again option is checked.   The popup appears if you hit the H key while an assembly is selected.  

File handling: New project: Ctrl + N Open project: Ctrl + O Save project: Ctrl + S   Assembly editing: Copy (selected assembly/assemblies): Ctrl + C Cut (selected assembly/assemblies): Ctrl + X Paste (copied or cut assembly/assemblies): Ctrl + V Snap two assemblies together: Drag assembly and press Ctrl when the assemblies’ snap points overlaps Unsnap two snapped assemblies : Press Ctrl and drag one assembly away from the other Alter assembly size (only certain assemblies): Shift + drag with mouse Multiple selection of assemblies: Shift + select with mouse Group assemblies (multiple selected assemblies): Ctrl + G Ungroup selected assemblies: Ctrl + U Delete all assemblies: Multiple select + delete Lock/Unlock selected assembly/assemblies: Ctrl + L Undo (only certain assemblies): Ctrl + Z Redo (only certain assemblies): Ctrl + Y   Assembly control: Activate (only certain assemblies, must be selected): + Deactivate (only certain assemblies, must be selected): – Release loads where cursor points: F (run mode only)   Load control: Stop/Release a load on a track: S Release a load (already stopped): R Jump back 100 mm an release (A load stopped on an Action Point): J Ungroup (release a selected load that are a part of a group): Shift + Space Enable/Disable a load : Space   Run control: Pause/Start: P Reset model (delete all loads): Ctrl + R Start/stop motors: select and press + (or double-click motors) Alter motor direction: Ctrl + left mouse click. When motor is selected: – (minus button)   Scene / viewing: Default camera view: F5 Save camera views: Ctrl + Shift + 1-9 Jump to saved views: Shift + 1-9 Fly to saved views: 1-9 Toggle orthogonal / isometric view: F12 Toggle full screen: F11 Zoom in and out: +/- (or roll mouse wheel) Follow a load: Select a load and press: F Alter the centre of the 3D scene: Position cursor in new centre + Ctrl + right click   Scene / details: Lock/unlock 3D scene: Ctrl + L Show/hide motors: Ctrl + M Toggle labels: Ctrl + E Toggle primitives: Ctrl + P Toggle shadow: Ctrl + Q Debug (developer license only): Ctrl + D