The Transfer car is best described as a conveyor on a rail.   The conveyor can move along the rail, picking up and dropping off loads from and onto adjacent conveyors (stations).   Through the transfer car’s properties, you can assign any user created actionpoint as a pickup point or destination point.   When a load reaches a pickup point and it has its destination set to an actionpoint along the route of one of the destination stations.   The transfer car will move to the pickup point, transfer the load onto itself, move to the destination point and drop off the load.   Video demonstration (also attached)     In the video demonstration we have 3 actionpoints: AP1 - Middle of the first conveyor AP1 has its “Default Destination” property set to “AP3” AP2 - End of the second conveyor AP2 has its “Collision Mode” property set to “Leading” AP3 - Start of the third conveyor) AP3 has it set to “Center”

Experior can be used for a plethora of tasks and while it is designed for IT and/or PLC testing, the 3D graphics used in Experior make it an ideal tool for creating training or sales simulation too. Therefore, when you are creating a new model, it is important to choose the right level of details for the model. Should it be extremely detailed and look close to the real thing? Or should it have just a basic resemblance and instead focus on maximum effectivity? It depends on what the purpose of the model is.   IT & PLC tests If you want to use the model for testing, the focus should be on functionality. Basically, the less details the model has, the easier it will be for the program to run it, and the smoother the model will run in return. The more loads you want the model to run, the less details the program can render simultaneously. Of course, it should still be possible to see what each part of the model is supposed to represent in real life, but you probably do not need to be able to see every screw and button on every machine. If you need to lower the level of detail in a part of the model, take a look at our guide to how to do it HERE.    Simulation & Sales simulation For simulation the details are much more important to make the model look close to the real thing. Especially if you are running a sales-simulation you would want the customer to see, what they get as close to reality as possible. However, you probably do not need for the model to run as many loads simultaneously. Here you can focus on making the models look true to reality, even though the high level of details makes it harder for the computer to run as many loads, as you could with a lower detail level.   Examples Very detailed assemblies:   Decimated versions of the same assemblies  

Action Points is what triggers an event in a model built in Discrete Events mode. They are similar to sensors in Physics mode.   When you build a model in Discrete Events mode, you build it as a Path the loads will follow, which is a collection of Tracks. If you then want to have a certain event happen somewhere along the Path, you insert an Action Point on the desired Track. Adding an Action Point is done by right clicking on your Track, or Conveyor, and choosing ‘Insert Action Point’: The Action Point shows up as a small X in the middle of your Track. By clicking the Action Point, the properties window shows the available properties that can be changed. Behaviors related to the Action Point include: Changing the Action Point’s name. Behavior when a Load reaches the point (Stop Mode – dropdown menu). Default Destination – modifiable input string, which should be the Name of the destination Action Point. This property can be used to send a Load from a specific Action Point to another specified Action Point. Position on the Track/Route (Distance – which means millimeter away from the Track/Route’s start, as in the red arrow).  

The feeder and eater are two elements of a model that are closely connected. The feeder produces loads while the eater ‘eats’ the loads so they disappear from the model again. Read more about them beneath. Feeder As mentioned above, the feeder produces loads. Loads represent any product the model is designed to handle, for instance luggage, boxes or trays. If you double click a conveyor, it will produce a load. However, if you want to produce several loads, you will need to use a feeder. In the Physics mode, you can find the feeder in the Experior catalog under conveyors:   In the Discrete Events mode you can find the feeder in the demo catalog. From the catalog you can double click the feeder and place it in the scene. Alternately you can right click on a conveyor you wish to add the feeder to, and choose the ‘insert feeder’ option. Once you have added a feeder, it will start producing loads when you press play on the model. If you click on the feeder, you will be able to see its properties in the properties window. From here you can see, which type of load you are using as well as change load type under load>type. The default is a package but there are several options to choose from. A graphical overview of the all the available Load types – including the list shown in the image below: It is also possible to make your own loadtype by uploading your own file. You do this by selecting the loadtype called ‘file’. From here a menu will pop up, where you can upload your own. Besides showing the load type, the properties window for the feeder holds other information such as the loads size or any barcode connected to the loads. It is also possible to set a time interval for how often the feeder should produce a load. Alternately you can instruct the feeder to produce a new load when the previous load is a specified distance away from the feeder. Supported File Formats .x (Microsoft DirectX) .dae (COLLADA) .fbx (Autodesk FBX) .obj (Wavefront) .3ds (Autodesk 3D Studio) .ase (Autodesk 3D Studio ASCII) .stl (Stereolithography) .lwo (LightWave) .dxf (AutoCAD dxf) .glb 2.0 (binary) .gltf (embedded)  Eater  The eater only exists in Physics mode. You will find it under the sensor catalog>misc.>eater: When a load hits the eater, the load will get ‘eaten’ and disappear. In the properties window you can see the properties for your eater and change its size, visibility etc.  Linking a feeder and an eater It is possible to link an eater and a feeder to each other. For instance if you have build only parts of your model but still miss some functions, you can set it up so an eater eats the loads in one part of the model and then sends them directly to the feeder in another part of the model, making it possible to circumvent the part of the model, you have not yet build. If you wish to do this, you must go to the properties window of both the feeder and the eater in turn and enable the handover connection box: You also have to make sure that the port-numbers are a match and the computer does not already use this port – otherwise you will not be able to connect the two. When you have chosen matching port-numbers, that are not already in use, the feeder and eater will connect.   If you wish to connect a feeder and an eater that are not on the same device – for instance you have part of the model open on your computer, your colleague has another on his – it is possible to do so as well. You just need to make sure that the IP address in the properties for the eater matches the IP address of the device, the feeder is on. Then you can connect them.     

You can use a sensor to test your PLC. When a load passes a sensor, the sensor sends a signal to the PLC. You can program your PLC to react in different ways when a sensor sends a signal.   In the Experior catalog window you can find the sensors catalog. From there you can choose between several different sensors. The basics tab holds the Photoeye, Cylinder, Box and Square sensors: These sensors offers the most basic functionality; to send a message to the PLC when a load passes them. The Photoeye sensor is special in the regard that it will adapt its size to fit your conveyor, while the other sensors come in a default size. However, you can adjust the size of all the sensors in their properties window. To install a sensor simply click it and place it over the conveyor you wish to install it on.    The scanners tab holds a few sensors with different functionalities: The X-ray sensor can be set up to randomly flag some of the loads which passes it. You can choose how large a percentage will be flagged in the properties window of the sensor under screening>percentage   The Angle sensor registers at which angle the load hits it, and sends the information to the PLC.   The OMNI sensor and the barcode sensor has the same functionality, they only differ in size and look. Both will register when a load passes them and then scan the barcode related to that load and send this information to the PLC in the form of text. You can set the barcode for a load in the loads property window under Identification Under the scale tab you will find the weight sensor: When a load hits the weight sensor, it will register the weight of the load and send the information to the PLC. It is possible to use different data types depending on your need but as default, the weight is measured in grams. The last tab is the Misc. tab. Under this one you will find the Counter, Eater, Beamer and Laser: The Counter has a little number above it that shows how many loads have passed it. In the properties window for the counter you can see how many loads has passed it in the last hour and the last minute.   The Eater eats the loads so they disappear from the scene. Read more bout the eater here.   The Beamer is made up of two connected parts. When a load hits one end of the Beamer, it is teleported to the other end of it. This allows the Beamer to work as a stand in for any part of the model, you have not yet finished. The load will simply skip the unfinished part when it hits one end of the Beamer and reemerge at the other end to continue its journey around your system.   The Laser sends out a laser beam. When a load hits the beam, the Laser figures out how far away the load is, and sends the information to the PLC in milimeters.   Some sensors can be observed. You mark a sensor for observation by right clicking it and choosing ‘observe’ in the menu: When you have activated the observation feature the sensor wills how up in your statistiscs window like this:   Now you can see, how many loads have passed the sensor. It is possible to rename the sensors in their properties window, so it becomes easier to tell them apart.   For more information see also Connecting an assembly to a PLC. 

Conveyors are the most basic, and most important part, of any logistic model. In this guide we will show you how to interact with conveyors and fix them together.   Select the conveyor catalogs. From here you can click and drag the component into the workspace.   Snapping To snap two conveyors together, hold ctrl and drag until the red and blue point snaps together. When two tracks are snapped together, they are locked in place.   As a note, tracks, by default, run from the red point to the blue point, so when attaching additional items opposite colo red points must be snapped together to ensure the model flows correctly.   Adjusting Size   To adjust the length either drag from one of the endpoints (hold ctrl to make sure it stays in position) or by selecting the straight and in the properties window scrolling down to size and adjusting the Length. Here you can chose to edit Height and Width.  See attachment "length"   Adjusting Orientation   Rotate your component by selecting it, and using Mouse-wheel. Using Shift + Mouse-wheel will rotate by 45 degrees instead.   It is also possible to type the exact rotation you want in the properties tab. Go to Properties > Orientation > Yaw. The initial value is ∠0° and the possible values are from ∠-180° to ∠180°.   See attachment "rotating"