When the Experior layout is set to default mode, you will find the connections and catalog window on the top left side of the screen. This window has a few different functions:   Catalog Connections   1. Catalog The catalog is where you can see the assemblies that are available to you. The catalogs function as a form of libraries where you can browse the different assemblies and other items. Which assemblies shows up depends on which catalogs you have loaded when you started Experior. In the very beginning you should see a window like this: If this window does not show up when you start the program, please read about the Experior startup options here.   This window is where you choose which catalogs will be loaded into the program. Make sure to at least include some of the catalogs, otherwise the catalog window will show up empty and you will have no assemblies to build your model from. Once you have chosen your catalogs they will show up in the catalogs window. To see what each catalog contains either double click on it or click the small arrow to the left of the catalogs name. This opens up any sub categories which you can in turn open up too, to see the individual assemblies. Once you have found the assembly you need, you can either click on it and then click on the model floor to insert it into the model or you can chose to drag it to where you want it placed and then click to place it. The catalogs window also has a few additional features. You can change the layout of the catalogs on the top left of the window: There are two different views to choose from depending on your preferences: Gallery view style:   Tree view style:      To the right of the catalog layout buttons in three view you have the option to zoom in and out on the content of your catalogs. Below that you have a search bar, where you can search for any specific assemblies in your catalogs. Above the zoom buttons is a small tack titled Auto Hide. Pressing this button will hide the catalog and connections window right below the Experior menu bar so it looks like this:     To reset the window to its original position either drag it back to where you want it and hover over that spot until you have the option to place it or go to the View tab in the menu bar and choose reset windows.   2. Connections   The connections tab is where you can connect to your PLCs or higher level systems. When you first open Experior the window will be empty. However, if you right click within the window a menu will show which allows you to create connections:   From this menu you can choose which kind of connection you wish to make. You can choose between low level (PLC connection) and high level. When you have chosen one or more PLC connections they show up in the connections window like this:    You then specify the IP address of the PLC in the properties window and right click on the connection in the connections window. Then a menu will show up which looks like this: CONNECT ALL: Connect all the PLCs at once (this only works providing you have entered an IP address for each connection) CONNECT: Connect this specific PLC ENABLE LOGGING: Log all the messages that the PLC sends and then shows them in the log window IMPORT: Import all addresses from the PLC in an Excel file EXPORT: Export the addresses as an Excel file ALARMS: Opens a new window that allows you to set alarms and which error messages they will display.  DELETE: Deletes the connection   Please note: The menu can have fewer options depending on the type of connection.   ALARMS WINDOW: The subscribe column lets you choose whether or not the alarm is activated. Address, bit and source shows the specific ‘address’ of the alarm. If you think of the address like an actual physical address, the ‘address’ column shows the road name, the ‘bit’ is the house number while the ‘source’ is the postcode.     If the connection to the PLC is address based you can only add alarms when the PLC is not connected. However, if the connection is tag based you can only add alarms when the PLC is connected. Read more about alarms here.   Besides being able to set the IP address in the properties window you also have the option to customize the connection here in other ways.  

  Experior has several different menu tabs:   Files Edit View Settings Tools Model 1. Files   NEW: Create a new file OPEN: Open an already existing file SAVE: Save your model SAVE AS: Choose a name and location for your saved file MERGE: Merge two different models XML: Import an XML file if its format can be used in Experior COLLADA: Export the model graphics as a Collada file (.dae) ABOUT: Shows a Popup with the details of the catalogues and plugins you have loaded HELP: Sends you to the Experior help page   2. Edit   UNDO: Undo your latest action REDO: Reverse the undo CUT: Cut out a part of the model to paste elsewhere COPY: Copy part of the model. However it does not move to the clipboard so this only works if you want to copy and paste a part of the model within the same Experior window COPY (CLIPBOARD): Places the copy on to your clipboard allowing you to copy and paste between separate Experior windows PASTE: Insert what you copied SELECT ALL: Select all assemblies   3. View   WINDOWS: Choose which windows you want to be displayed in your Experior interface RESET: Resets the window layout to the default BACKGROUND: Choose the color of the ‘sky’ in the models background ASSEMBLY: Choose the color of your models components as well as the color they display when they are in locked mode LOCK: Lock either the whole model or the selected assemblies so you don’t move it around by accident SECTIONS: You can control your individual sections here by clicking on the arrow below the icon SECTIONS OPTIONS: The first option allows you to choose, which sections are shown or hidden The second option lets you lock or unlock the sections The third option lets you enable or disable the sections     AUTOCAD: Import a .dwg or a .dxf file here to drop it on the ‘floor’ LEVEL: If you have a developers license, this lets you choose the different modes. None is the normal default mode, Debug gives you extra information in the log and Detailed allows you to see the physical features of the real model around the graphic model RESET: Resets the camera to default mode FIT: See all your components on the screen at once PROJECTION: Choose between perspective or orthogonal viewing projections. STANDARD VIEWS: See the ‘model’ without perspective. This allows you to see the model from different angles and align your components perfectly. Move the camera to return to normal view or press the reset button CAMERA 1-9: Review camera positions here. Save a camera position by pressing Ctrl + Shift + a number between 1-9 to save at the corresponding spot. Press the button with this view to return the camera position to the saved view CLEAR: Lets you reset your saved camera positions EXPORT + IMPORT: Lets you import or export your hidden camera positions FOLLOW LOAD: Follow a selected load around your model SHADOW: Set how much of a shadow the production line casts LIGHTING: Choose where to place the light source on the model MOTORS: Toggle visibility of motors on your model on/off ACTION POINTS: Toggle the marker of the models action points on/off   4. Settings   SETTINGS: Choose different settings for your model (see below) THEMES: Choose which theme you want Experior to display     SETTINGS OPTIONS:   PAN/ROTATION MODE: Invert the camera controls. Lets you chose to see the scene from the point of view of the camera or of the scene – thereby changing which way you pan NAVIGATION: Set hotkeys for camera movement RANDOM SEED: Set the number you wish to use to initialize a random sequence WARN ON DERTERMINISM LOST: toggle on/off if you want a warning if the random sequence differs from the previous random sequence GLOBALIZATION: Choose measurement system KEEP THE SELECTION: Toggle on/off if the new assembly continues to follow the arrow pointer when you move it around the model or it is placed at the position where you first click MOVE AND ROTATE: Enable this to assure that the assembly does not move unless you hold down the left mouse button while turning it MODE: Choose if anything you copy/paste is inserted where your mouse is or next to the object you copied it from SNAP: Turn on/off if Experior should snap any component you copy/paste onto the nearest component OFFSET FROM PREVIOUS PASTE: Toggles on/of if the assemblies are placed continuously after each other when you copy/paste several assemblies or if the assemblies you paste are all placed at the same position SNAPPING: Set the radius in which the assembly snaps to the nearest assembly automatically when double clicking SEE ASSEMBLIES: Shows how the model was build when you load it instead of loading it all at once DISPLAY WARNING SIGNS: toggle on/off whether or not the warning signs are displayed when you lock the model   5. Tools   SCREEN SHOT: Take a screenshot of the whole model ASSEMBLY SHOT: Take a screenshot of the selected assembly MEASURE: Measure the distance between different components by clicking the measure icon and then pressing the model where you want the measuring tape to appear. Now you can move the two arrows of the measuring tape to set the distance you wish to measure   6. Model   PLAY: Starts the time SCALE: Choose how fast you want the model to run.  1:1 sets time scale to real time RESET: Return time and machines to zero and delete all loads SINGLE STEP: (Developer only) Pause after every time step RECORD: Records what happens in the scene. When you press it again you will have the option to replay what you recorded. If you want to reset the recording simply use the reset button on the left (It does NOT record a video but rather a series of events) LOAD: Load any saved events recordings SAVE: Save your events recording SNAPSHOT: Exports information about the model as an Excel file INFO: Shows information about the model you are running FILTER: Adjust which parts of the model it is possible to select MOVE: Select loads without being able to move them EAT: Toggle on/off if you want loads to be deleted automatically when it hits the floor. It does not delete loads already on the floor when you toggle it on AUTO/MAN: Choose if you want Experior to calculate routes on the assembly line if more than one option is available or if you want to do it manually   

  The center window in Machine Expert Twin has three different tabs:   Model Script Routes   1. Model   The model floor or ‘scene’ is where you can place your assemblies. This will display your model and it is also here that you can see what happens when the model is running.   The three arrows in the middle shows the axes of the model, where the green arrow is the Z-axis, the red arrow is the X-axis and the blue arrow is the Y-axis. The floor is gray by default but if you flip the model to see it from below the floor will show as see through.   To zoom in or out on the model, scroll the mouse wheel or set the zoom shortcuts in the settings menu.   If you wish to enlarge the floor you can go to the solutions explorer and open assemblies🠖section1. Now you can set the floor width and length in the properties window. Any alterations you make to the floor are only saved with this model so next time you open a new model the size will be back to the default.   You can also add additional sections to your model. You do this by right clicking the assemblies tab in the Solution Explorer window. This opens up a menu where you can either add a section or show all sections. Press the ‘Add Section’ and a new section will show up on top of the first one. The second section will be named ‘Section 2’ in the assemblies tab. Unless you have changed the dimensions of the first section you will not be able to see the second section immediately as it is directly on top of the first. To change this click the second section to make it active. You will now see the information of this section in the properties window. One of the lines in this window is named ‘Position’ and looks like this: The first 0 represents the X-axis, the second 0 the Y-axis and the third 0 the Z-axis. by changing the numbers from 0 you can offset the second section from the first. If you for instance put 5000 in the Y-axis position the second section will raise itself 5000 mm above the first to look like this:   At the bottom of the floor window is a panel which shows information about the model: PAUSED/RUNNING: Shows if the time is running or paused SCAN: Shows how long it took to calculate last physics step. If the number becomes too high, the machine begins having trouble calculating the steps and will send a warning in the diagnostics panel LOCK: Shows if the model is locked or not TIME: Shows how long the model has been running TIMESCALE: Shows how fast time is running in the model. 1 being real time and two being double real time etc. Maximum is 10 times real time for physics DIAGNOSTICS: Next to the number is the diagnostics panel which is empty when you first start Machine Expert Twin. Any alarms or errors will show up here   2. Script   The script tab allows you to write script inside Experior while the program is running. Pressing the icon with the green arrow above the script named ‘build’ will integrate your code in the program.   The error list below the script shows if any part of your inputs have resulted in an error.    3. Routes - Only for Discrete Events Mode   The routes window is where you can see the connection between any assemblies and/or action points which are connected by a route network. It might look something like this:   You can manipulate the routes by dragging the assemblies around in the routes window. The routes are automatically updated by default. If you wish to change this so the routes are updated less frequently you can go to the model tab in the menu at the top of Experior and find the routes icon at the very end of the panel: By pressing this, you can switch between automatically updating the routes and manually updating. When you switch to manual the routes are not updated again until you switch it back to auto.   

The measurement handler is an extension on the Kinematization feautre. It provides a way for the user to have access to different measurements related to assemblies from the Kinematization plugin. These are the main functionalities:    The user can add different measurements to Kinematization Assemblies. Body assemblies support pose related measurements, and kinematic axis assemblies support pose and scalar measurement.  Measurements can be monitored through a real-time plot.  Measurements can provide feedback to a PLC.  Measurements can be exported to a CSV file.  Currently, the user interacts with this feature through the context menu. These are the main actions the user may take:    Enable Measurement Handler To be able to use this feature with a specific assembly, the Measurement Handler must be enabled.  Open the context menu and expand the Measurement Handler menu.  Click on Enable Measurements    Add a Measurement Once the Measurement Handler is enabled, the user can add measurements. To add pose measurements (only IPoseMeasurables):  Open the context menu and expand the Measurement Handler menu.  Expand Measurements, expand Add New Measurement Relative to. Here you can see the Global coordinate system, as well as all other assemblies that implement the IPoseMeasureable interface and have their Measurement Handler enabled. This will be the reference point for the measurements that will be added.  Once you select the reference point of the measurement, a selection window will appear. Here the user can select what measurands should be added.  Click OK.  To add scalar measurements (only IScalarMeasurables):  Open the context menu and expand the Measurement Handler menu.  Expand Measurements, expand Add New Scalar Measurement to. Here you can see the name of the measurand that can be added. Select the desired measurand.    Connect Feedback to PLC Once the measurements have been added, the Feedback signals will be visible from the solution explorer. Here the user can select the signal and assign the Connection ID and path through the property window (as a normal PLC Input).      Plotting a Measurement Once the measurement has been added, a real time view of the measurement can be plotted. The user must:  Open the context menu and expand the Measurement Handler menu.  Expand Measurements, Existing Measurements, and look for the measurement that must be plotted. Expand this menu.  Click on Plot.  The plot window will open. It will update while the model is running.        Exporting Measurements The measurements can be exported to a CSV file. This is only possible if measurements have been recorded in the model, and the scene is paused.    Open the context menu and expand the Measurement Handler menu.  Select Export Multiple Measurements.  The Multi Measurand Exporter window will open. Here the user may select as many measurands they would like to export. Additionally, they can select if they want to have the measurements with respect to time, or another measurement.  Once the selection is completed, click on Export.  Select the output path for the file. 

The Logic Configurator is accessible as a view within in Experior 7s user interface. It allows you to configure logical relations between the elements of the scene in a graphical editor. You can use the Logic Configurator to create flow simulations by adding logical operations and connecting them with elements of the scene. The Logic Configurator provides element inputs and outputs and allows you to configure the relations between them without a controller.   See the attached video Logic-Configurator-demo.mp4 for a quick demo.   Creating Connections To establish a relation between blocks, follow these steps:   Click an output of one assembly block. Hold down the left mouse button and draw a connecting line to the input of another assembly block. The connection between two blocks is indicated by a solid line. Connections can only be established between inputs and outputs of the same type. To remove a connection, follow these steps:   Right-click the connection in the Logic Configurator. Click Delete from the contextual menu.   NOTE: Each input can be connected to only one signal, whereas each output signal can have multiple connections   Good Practices Accessing the Commands You can access the contextual menu commands by typing the first letter of the command.   Examples: Right-click in the Logic Configurator view to open the contextual menu and type: t  to create a Timer block. c  +  c  to create a Counter block because this is the second command in the list starting with  c . m  +  n  to create a Number block. It serves as a shortcut to use the command Mathematics  >  Number.   Creating Multiple Blocks for the Same Assembly To create a clear arrangement of blocks and connecting lines for the same assembly or motor, you can use multiple blocks. To achieve this:   Select the assembly or motor in the scene. Right-click anywhere in the Logic Configurator view and click Create Register Node(s) several times until the desired number of blocks is created.   NOTE: If you create multiple instances of the same assembly or motor and you establish multiple connections to the same input, the block uses the last updated input value as the default input.   Example: To establish clear visibility of connecting lines when representing an output signal located on the right-hand side of the assembly block (Basic Surface Motor 1 in this example) connecting to another block located on the left-hand side (Timer in this example), it is a good practice to create an additional instance of the block (Basic Surface Motor 1 in this example) and position it on the left-hand side (of the Timer block in this example).   Creating Multiple Blocks for the Same Assembly To create a clear arrangement of blocks and connecting lines for the same assembly or motor, you can use multiple blocks. To achieve this:   Select the assembly or motor in the scene. Right-click anywhere in the Logic Configurator view and click Create Register Node(s) several times until the desired number of blocks is created. NOTE: If you create multiple instances of the same assembly or motor and you establish multiple connections to the same input, the block uses the last updated input value as the default input.   Example: To establish clear visibility of connecting lines when representing an output signal located on the right-hand side of the assembly block (Basic Surface Motor 1 in this example) connecting to another block located on the left-hand side (Timer in this example), it is a good practice to create an additional instance of the block (Basic Surface Motor 1 in this example) and position it on the left-hand side (of the Timer block in this example).   Displaying Boolean and Numerical Values   The values of Boolean and numerical inputs and outputs are, by default, not displayed for all blocks in the Logic Configurator. To make these values visible, create the following blocks and connect them to the inputs or outputs:   Boolean Display blocks to visualize Boolean outputs. Number Display blocks to visualize numerical outputs.   Managing Blocks To create blocks, right-click in the Logic Configurator and select a command from the contextual menu to create a specific block.   To remove a block, right-click the block and use the Delete command from the contextual menu or select the block and press the Delete key on your keyboard.   Configuring Blocks You can configure a block in two different ways:   Select the block in the Logic Configurator and configure the corresponding parameters in the Properties view on the right-hand side of the Experior window. Create other blocks, for example, Mathematics blocks, and establish relations between the blocks within the Logic Configurator.

The Startup configuration file is used to launch experior with a set of predefined options.   In order to generate this file, you first start Experior with the command line argument -startupconfiguration new   This will create the file “StartupSettings.json” in the install directory folder, which as standard is set to: C:\Xcelgo\Xcelgo Experior 7   You can now navigate to the folder and edit this file with a text editor.   To make use of the settings, start experior with the command line argument -startupconfiguration (filepath)   Note: Remember to include the filename and extension in the filepath. Referencing the directory is not enough.   The command line arguments have a higher priority than the configuration file options. This means, that an option set in both the configuration file and the command line, will use the command line argument.   The options in the configuration file that are available as command line arguments are listed in the “Startup options” article.   The data is formatted in JSON and the file looks like this:   { "Config": false, "Headless": false, "DebugLevel": "None", "LogMode": "FileDate", "LogDir": null, "WorkDir": null, "SelectedEngine": "Events", "PhysicsFrictionType": null, "TimeScale": 1.0, "ContinuouslyRunning": false, "Seed": 0, "OEM": false, "WebApiEnabled": false, "GraphicsServerEnabled": true, "ModelToLoad": "C:\\Projects\\ExampleProject\\Models\\ExampleModel.Experior", "AutoStart": false, "StopAfterSec": 0, "AtStart": "", "EventFile": "", "LicenseSource": "", "LicenseUsage": "", "ImpersonateProfile": "None", "ForceCheckIn": false, "FingerprintReport": false, "SelectedCatalogs": [ "Experior.Catalog.Training.dll", "Experior.Catalog.ExampleCompany.Conveyors.dll", "Experior.Catalog.ExampleCompany.Feeders.dll", "Experior.Catalog.Xcelgo.GuidedPath.dll", "Experior.GuidedPath.Base.dll", "Experior.Catalog.Xcelgo.Buildings.dll" ], "SelectedExternalLibsPath": "", "ExternalLibsPaths": [], "BetaFeaturesEnabled": false, "ValidateSerialization": false, "LicenseServerFallback": false, "WebApiConfigurationFilePath": "" }   Config: Option type: boolean (true or false). Description: true will force a display of the ‘Catalog selector’ during startup, false will only display the dialog in case an input is needed. Default: false.   Headless: Option type: boolean (true or false). Description: true will start Experior in ‘headless’ mode (i.e. console mode with no UI other than console input/output), false will start Experior in UI/IDE mode. Default: false.   “DebugLevel”: Option type: string (“None”, “Debug” or “Detailed”). Description: Set the desired debug level. Default: “None”.   “LogMode”: Option type: string (“None”, “File”, “FileDate” or “FileModelName”). Description: Set the desired log file mode. Default: “None”.   “LogDir”: Option type: filepath string (null, empty or a valid directory path). Description: Set the desired log file directory path. Default: null (will result in debug.log in %localappdata%\Xcelgo\Experior\7\Work\Logs\debug.log).   “WorkDir”: Option type: filepath string (null, empty or a valid working directory path). Description: Set the desired work directory path. Default: null (will result in workdir being %localappdata%\Xcelgo\Experior\7\Work\).   “SelectedEngine”: Option type: string (“Physics”, “Events” or “Engineering”). Description: Set the desired engine type. (Only functional with the right license privileges). Default: “Physics” if several engines allowed otherwise the single allowed engine.   “PhysicsFrictionType”:  Option type: string (null, empty, “Patch”, “OneDirectional” or “TwoDirectional”). Description: Starts the physics engine with the chosen friction type (only available in Physics mode). Default: “Patch”.   “PhysicsEngineDynamics”:  Option type: string (null, empty, “Classic” or “Advanced”). Description: Enables advanced dynamics of loads which provides a more realistic motion of loads produced by conveyors and stacks stability (only available in Physics mode). Default: “Classic”.   “TimeScale”:  Option type: floating point value (positive). Description: Specify the time scale to use. Default: 1.0. Example: 2.5   “ContinuouslyRunning”: Option type: boolean (true or false). Description: Prevents the model from stopping automatically when certain situations occur. (Example: In “Events” engine mode, the last load in the scene is deleted.) (Only applied in case of an applicable engine type) Default: false.   “Seed”:  Option type: integer. Description: The seed used by the random generator. Default: 0.   “OEM”:  Option type: boolean (true or false). Description: Start Experior in OEM licence mode. See OEM Setup (coming soon) Default: false.   “WebApiEnabled”:  Option type: boolean (true or false). Description: Enable or disable WEB API. Default: true if headless is true, otherwise false.   “GraphicsServerEnabled”: Option type: boolean (true or false). Description: Enable or disable Graphics Server. Default: true if headless is true, otherwise false.   “ModelToLoad”: Option type: filepath string (null, empty or valid filepath). Description: Set the desired model file to load after startup. (example: “C:\\Projects\\ExampleProject\\Models\\ExampleModel.Experior”) Default: null   “AutoStart”:  Option type: boolean (true or false). Description: Run the model when it is loaded. Default: false   “StopAfterSec”:  Option type: integer. Description: Stop the model and close Experior after a period of time – ‘duration’ defines the time in seconds before the model stops and Experior starts closing. Default: 0   “AtStart”:  Option type: string (null, empty or valid symbol or assembly name). Description: Here you provide a symbol name or assembly name that should be activated when a model is started (after connections are established) so that this can initiate some action in the model. Default: empty   “EventFile”:  Option type: filepath string (null, empty or valid filepath). Description: Loads an event file (*.events). (this is only possible when a model file is loaded at the same time) Default: empty   “LicenseSource”:  Option type: string (null, empty or valid filepath). Description: Specify either a specific license type to use (dongle, offline, or weblicensefile) or specific license (dongle:id). (example: -license C:\Experior\license.key) (example: -license dongle:xxxx) Default: empty   “LicenseUsage”:  Option type: string (null, empty or any string with maximum length of 50 characters). Description: Set the licenseusage property for web license usage tracking. Default: empty   “ImpersonateProfile”: Option type: string (“None”, “Viewer”, “Tester”, “Commissioner” or “Builder”). Description: Start Experior at a lower license level than the one you have access to. (See: Types of Licenses ) Default: “None”   “ForceCheckIn”: Option type: boolean (true or false). Description: Check-in web license when Experior closes without asking user. Default: false   “FingerprintReport”: Option type: boolean (true or false). Description: For License debugging, appends a log file with a timestamp and license information. Default: false   “SelectedCatalogs”: Option type: array of strings (null, empty or an array of valid filenames). Description: A list of catalog dll filenames for catalogs that should be loaded when Experior starts. Default: empty   “SelectedExternalLibsPath”: Option type: directory path string (null, empty or a valid directory path). Description: A path to any libraries (dll’s) not within the Experior installation folder, that Experior should reference on startup. Any catalog dll’s contained within this folder will appear in the catalog selection window, when starting Experior. Default: empty   “ExternalLibsPaths”: Option type: array of directory path strings (null, empty or an array of valid directory paths). Description: Any other paths to catalog dll’s can be set here, these paths will be selectable in the dropdown of the catalog selector window, when starting Experior. Default: empty   “BetaFeaturesEnabled”: Option type: boolean (true or false). Description: Certain experimental features can be enabled with this set to true. Default: false   “ValidateSerialization”: Option type: boolean (true or false). Description: Validates loaded catalogs to make sure there are no issues with serialization (saving/loading). This is useful for debugging catalogs, as you dont need to load a model or create assemblies in the scene to trigger an error. Default: false   Example: If 2 catalogs have an assembly infoclass that uses the same xml typename, Experior won’t know which one to load.   “LicenseServerFallback”: Option type: boolean (true or false). Deprecated (no longer used) Default: false   “WebApiConfigurationFilePath”: Option type: filepath string (null, empty or a valid filepath). Description: The webapi configuration file. See: “Startup Options” article -webapi Default: empty (will result in default values)   “CoordinateSystem”: (optional) Option type:  string (“LeftHanded” or “RightHanded”). Description: Determines whether Experior should use a Righthanded or Lefthanded coordinate system. Default: “LeftHanded”

 An issue can arise when trying to use Experior on a laptop that has both an integrated and external graphic cards, while using that laptop on an external monitor. With this setup the external graphics drive will be used on the external monitor.   The issue originates when Experior uses the integrated graphics drive and is then dragged onto the external monitor. This will result in the external graphic card crashing.   The problem is fixed by setting your external graphic card as the one being used with Experior. This is done in the graphics cards setting on your laptop.   Errorlog after crash  

Purpose of the article Recent Windows updates have introduced additional steps necessary for Experior to run optimally. In this article, we aim to share recommended settings that we advise customers to apply to their PCs to enhance performance. We are happy to extend the list with advice provided by you the customers, so feel free to get in contact with us and let us know how you setup your work stations.   Windows With recent updates to Windows, both we and our customers have noticed that the display settings in Windows can override those set in the Nvidia Control Panel (and possibly other graphics card providers as well). Therefore, it is crucial for Experior users to ensure that Experior is designated as a high-performance application in the Windows graphics settings. Here’s how to do it easily:   Open Graphics Settings: In the Windows search bar, type “graphics settings” and select the matching result.    Enable Hardware-Accelerated GPU Scheduling: In the graphics settings window, start by choosing “Default graphics settings” and ensure that “Hardware-accelerated GPU scheduling” is turned on. Add Experior as a High-Performance App: Back in the graphics settings window, you need to add Experior with custom options. Click the “Browse” button under the “Add an app” menu. This will open a file explorer window. Navigate to the Experior installation directory, which is as standard set at  C:\\Xcelgo\\Xcelgo Experior 7 . Select  Experior.exe  and click “Add.” It should now appear in the list below. Set Experior to High Performance: By default, the app will be set to “Let Windows decide.” Change this setting to “High performance” to ensure that Experior utilizes your high-performance GPU.   Nvidia Control Panel To ensure that Experior runs smoothly in Physics mode, it is still important to configure your Nvidia settings properly.   Open Nvidia Control Panel: Right-click on your desktop and select Nvidia Control Panel from the context menu. Manage 3D Settings: In the Nvidia Control Panel, click on Manage 3D settings from the left sidebar. Select the Preferred Graphics Processor: Under the Global Settings tab, find the option labeled Preferred graphics processor. From the dropdown menu, select High-performance Nvidia processor.  Set PhysX Configuration: Next, go to the Program Settings tab. In the Select a program to customize dropdown, find and select Experior (if it’s not listed, you can add it using the Add button). Below that, locate the PhysX settings section and choose your high-performance GPU from the dropdown menu.   Apply Changes: Once you’ve made these changes, click the Apply button at the bottom right corner of the window to save your settings. By following these steps, you can ensure that Experior utilizes the high-performance GPU for optimal performance   improvement tips for extended period model runs When running a simulation for an extended period of time, it is important to ensure that Windows runs stable. For this we suggest that you:   Disable hibernation Disable power optimizations (CPU throttling, screen off, hd off, USB power etc.) Disable windows update Don’t logoff/logon while running

Icons and Mesh folders Icons and Mesh folders are used to allocate resources such as images and CAD files.   Supported formats are: Image: .png, .jpg, .bmp, .gif, .svg Mesh: .x, .dae, .fbx, .obj, .3ds, .ase, .blend, .stl, .lwo, .dxf    NOTE: Some formats are not fully supported as embedded resources as they reference other files for data. Such as .obj files that reference a .mtl file for their color data. If you have problems loading your resources, try referencing it using the filepath instead of the EmbeddedResourceLoader.   Our Import functionality uses the Assimp open source library, some format features may not be supported. If you run into issues importing your files, try simplifying your imported object. For example, removing an armature or other unnecessary components. See “Import issues” below for notes about unsupported features or issues you may run into when trying to import certain files.   Once a resource has been added to the appropriate folder (Icon/Mesh), set the property Build Action to Embedded Resource.   Accessing resources in the code Resources are accessed through the public static fields contained in the Internal class Common located in Create.cs internal class Common { public static Experior.Core.Resources.EmbeddedImageLoader EmbeddedImageLoader; public static Experior.Core.Resources.EmbeddedResourceLoader EmbeddedResourceLoader; }   Getting access to images: public override ImageSource Image => Common.EmbeddedImageLoader.Get("Example.png");   Getting access to CAD/Mesh files: var exampleMesh = new Experior.Core.Parts.Model(Common.EmbeddedResourceLoader.Get("Example.stl"));   Import issues We do not currently support COLLADA (.dae) files containing armatures.   .obj files as embedded resources do not display any color/shading, since they currently have no way of referencing their .mtl file.

When you buy a license for Experior it comes in two different types of mode: Physics mode or Discrete Events mode. Many of the functions of the two work in the same way, but there are some differences. If you are in doubt about what the difference is, you can read on here.   In Physics mode we pretend that the model follows the same rules of physics as applies in the real world. This means that we use physics to move the loads in the model. This also enables us to see, what happens if for instance a load falls off a conveyor, where it will then fall to the ground. In Discrete Events mode you build a route for the loads to move along. The loads will then follow the route no matter what else happens in the model, meaning that it is impossible for a load to fall off the route. In Discrete Events mode the loads only exists when they are on the route. If you start the model without finishing the route, the loads will simply disappear when they hit the end of the last conveyor/track.   If you build a route for your loads to follow and you want a particular event to happen at a certain point in the model you have to use a sensor in Physics mode. This differs from Discrete Events mode, where you would use an action point to trigger an event. The action point and the sensor have roughly the same functionality in the two modes.   In Physics mode you have to let the model know which way the load is supposed to move through the production line whereas in Discrete Events mode you can simply instruct a load where to end up and it will find the shortest way there on its own (This is called the ‘shortest path function’).   In the grand perspective of things you can say that Discrete Events mode is a bit simpler than Physics mode. For instance two loads can not be in the same location in Discrete Events loads, whereas it is possible to have two loads next to each other in Physics mode. In Physics mode you also have the option to simulate what will happen if the product line malfunctions, this is not as easy in Discrete Events mode because the loads always follow a specific path meaning there is no room for ‘unintended’ actions to happen. However, where Physics wins on detail level, Discrete Events win on speed. Discrete Events is the only mode where you can run a model faster than real time and because the level of detail is smaller, the model will run more smoothly when you have bigger production lines.   So to sum up, in a very simplified version it comes down to speed vs. detail level, where Discrete Events can deliver on model speed and ability to handle extremely massive models while Physics mode delivers on functionality and level of detail. 

An Experior License can be issued for either physics simulation, discrete event simulation or both modes.   Each license also contains the functions of the lower level licenses, so if you buy the level 4 license ‘Builder’, it also contains level 3 ‘commissioner’ and 2 ‘tester’ functions and the 1 ‘viewer’. For the complete overview see the license matrix at the bottom of this article.   You can check your current license in the ‘about’ menu when running Experior.   Viewer - A viewer license restricts you in every possible manner except for opening up Experior. It is a showcase license essentially. Tester - With a Tester License you can open and run existing models, feed loads into models from feeding points, modify and remove loads and change run time scale. Commissioner - A Comissioner License has the same properties as the Tester License but with the possibility of changing component configurations such as IP-addresses. Builder - The Builder License enables you to build models from components in the catalogs - both own developed catalogs and the standard catalogs. You can modify the properties of the components and write code for controlling the model. Developer - With the Developer License you can access the Experior platform and API to modify existing components, develop your own components, and manage the catalog content. It also lets you modify the Experior Application by adding new windows, menus etc. to create your own user specific applications within Experior.   License Matrix     Active Active Active Active Active In progress Unconfirmed   Function Code Viewer Tester Commissioner Builder Developer Server DT Suite Details IDE (UI) "ExperiorUI" x x x x x       Instances allowed "InstanceLimit" 1 1 1 1 1 1 1 The listed values are the defaults; it can be overwritten (per license) in the 'features'. Open "Scene.Open" x x x x x x x   New "Scene.New"       x x       Save "Scene.Save"     x x x       Model Execution "Scene.Play"   x x x x x   Play/Pause/SetSpeed, View.Schedule Model Configuration "Scene.Configure"     x x x     Edit certain model/assembly properties, basefeeder.propertyedit etc, SolutionExplorer.ControllerNode.Add+RemoveScript Model Building "Scene.Build"       x x     Engine.SingleStep, View.CatalogSelector, View.Catalogs, Scene Unlock, View.Script (Edit), AlarmEditor contextmenu, PathFinder.MoveLoadTo, ConveyorMyMotor.Selectable, Settings.CopyPaste, Settings.PointerPanel, Assembly.EventEditor, PLC.x.OMem+IMem, StandardActions.ChangeView+Terminate+Script ?, Script Editor (Readonly if not available) Event Recording "Scene.Recording"     x x x       Import "Scene.Import"       x x       Export (Collada, Autocad) "Scene.Export"       x x       GrahicsServer "GraphicsServer"   x (1) x (1) x (1) x (1) x (50) x (50) "Contact us for more clients..." WebApi "WebApi"   x x x x x x   Load custom controllers, plugins and catalogs*   x x x x x x x *: catalog loading can be restricted per license/customer. Build custom controllers   x x x x x x x   Build custom plugins Profile="Developer"         x       Build custom catalogs Profile="Developer"         x       Context menus     x x x x       Developer tools, incl live-debug "Env.DeveloperTools"         x     Extra debug info, in-scene assembly edit  

This guide will show you where you find your license details, as well as a list of active users and the license activity.   Overview To find the status of your web licenses you go to dashboard.xcelgo.com. Here you click on ‘license details’ You login with your given userID and password.       You can see is the license details including privileges, engine, current active users, limit of active users and the expirations date on the license.   You’ll find a list of active users. This is computers that have a license checked out from the total license pool and active on the computer.   There is a tool to check the license activity, so you can check on the uses of the license in different periods of time. It is possible to download the activity logs in a csv format.     If you have any questions or corrections to the license, feel free to contact us at: Experior.license.support@se.com Error message - out of licenses If all of your available licenses are checked out of the license pool and your Experior instanse can’t find license to use your will get the following error message. You can use the active users list, combined with your own information about the computers that are using Experior, to check if all of the licenses are used actively. If that is the case then you can always buy more licenses.    

When you have downloaded the desired version of Experior, run the .exe.    Before you install, please take the time to read the license agreement. When you have read it, choose I agree to continue: Experior is as default installed as ‘C:\Xcelgo\Xcelgo Experior 7’. If you want a custom installation directory click the Options button. Otherwise click the Install button. The program will now install. If a User Account Control window appears click YES to allow the .exe to install Experior in the defined install directory.   Once the installation is complete, click CLOSE to finish. Using a web license To use Experior with a web license you must place the license key file in the Experior installation folder. As default this is: C:\Xcelgo\Xcelgo Experior 7   The License key file name has the following signature: license.(LicenseID).(LicenseType).key   Minimum PC Requirements CPU – Quad Core CPU with 8MB Cache and DDR3 Graphics card – Nvidia Gt 710 2GDH3 or equivalent Memory – 8GB Ram Disk Space – 900MB Operating System – Windows 10 Recommended PC Requirements CPU – Hexa Core CPU with 12MB Cache and DDR4 Graphics Card – Nvidia Gtx 1070 8GB or equivalent Memory – 16GB Ram Disk Space – 900 MB Operating System – Windows 10/11  

When working with CAD designers we sometime receive a CAD file that looks like this. Getting this model into Experior and using it as a part of a PLC- or IT-testing model we would need to reduce the amount of detail. As an indicator of detail we count the triangles(tris) in the model.     Following is some of the steps our developers do to ready the model for testing in Experior.   We start the tris reduction process with the program PiXYZ. This is because PiXYZ has some inbuilt powerful tools for decimation of CAD files. We use a script that automates the process and ends up with the model on the left. This model has 83.000 tris at this moment. Sometimes PiXYZ doesn’t automatically reduce all the ‘hidden mesh’ inside og the machine. Therefore, we need to work on the additional unnecessary mesh manually. For this we use the freeware ‘Blender’, to reduce tris further.   Splitting up different parts in Blender Even though this part of the machine has been through PiXYZ, it still has around 26.000 tris. After having been through Blender, this part of the machine is down to 12.000 Sometimes it makes more sense to rebuild a part with more simple objects in Blender. The part below was easier to rebuild. In the first picture it is shown as it was original in the CAD drawing delivered, the part has around 34.000 tris, and in the second we created from scratch it is at 3300 tris. The Final Model When all different parts of the model has either been manually decimated or rebuild, all of them are joined together and put back in PiXYZ.   Back in PiXYZ we run the script one last time to shave off the last few tris. Depending on how complicated the model is, this will still have a big impact.   The final model shown here has been reduced down to 23.000 tris, from the original 83.000 after in the first step.  

In Experior it is possible to import graphic files into the scene via different methods. For instance, when you are developing a component from scratch using our templates.   You can also import graphics straight into the scene: This can be done in the accessories catalog. You must view the catalog in ‘gallery view’ and then right click and press import   In the ‘feeder’ you can choose to show a file instead of one of our standard load types. Simply choose ‘file’ in the drop-down menu and then click the three dots to choose the file you want to show as a load.      Down below is the list of whitelisted formats that we allow for graphics import. .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) .gltf (embedded)

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"