The web license file (with the extension: .key) have to be located in the Experior installation folder (which is usually C:\Xcelgo\Xcelgo Experior…).   When Experior is started, it contacts the Xcelgo web license server to investigate whether the license is valid and whether a license seat is available. If the investigation is successful, a seat checkout is performed and the usage of Experior is granted.    When Experior is closed: Depending on the customer and license setup, Experior might give the user the option to contact the Xcelgo web license server for a check in of the license seat – or to keep it reserved for the user for later use. If checking in the license seat, the seat is available for checkout for other users with access to the same license.   The communication between Experior and the Xcelgo web license server is a bit different depending on the Experior version:   • Experior 5.x, Experior 6.0 and Experior 6.1 (prior to and including release Experior 6.1.19245) need access to port 8080 at ‘license.xcelgo.com’. They use a proprietary protocol for the license server communication.   • Experior 6.1 (from and including release Experior 6.1.19246) as well as Experior 7 need access to port 443 at ‘https://licenseapi.xcelgo.com’ for license server communication. They use a TCP protocol for the license server communication.   So: in order to check out or check in an Experior web license seat, access to and communication with the Xcelgo web license server is required. If this access is unavailable due to personal or company network restrictions and the access cannot be provided, then it is recommended to use a USB dongle licence instead.

On occasion, it can be useful to launch Experior with certain startup options to change the program’s functionality.   This article lists each command line argument, that you can use when launching Experior.   You can also view a list of these startup options by using the -help or -? command line argument when launching Experior.   Inputting the argument Command line (cmd) Open a command prompt (cmd.exe) Write path to your install directory, by default: “C:\Xcelgo\Xcelgo Experior 7\Experior.exe”  Append the argument and press enter (How it would look with default directory: “C:\Xcelgo\Xcelgo Experior 7\Experior.exe” -help)   Shortcut Right click the shortcut you use to launch Experior Click on Properties Go to the Shortcut tab In the field labelled Target:, append the text with your argument Click Apply and Ok Here is an example with the -help argument:     Visual Studio Right click the project that launches Experior Click on Properties Go to the Debug tab Go to Start options > Command line arguments Type in your argument Save (ctrl+s) Here is an example, once again using the -help argument:     Full list of startup options -help|-? Opens a command prompt with a list of all command line arguments available for the current Experior version.   -startupconfiguration <filepath> or new Specify a startup configuration file to use. You can read more about this here.   -config Displays the ‘Catalog Selector’ dialog during startup.   -headless Starts Experior in headless mode. NOTE: this will also enable webapi and graphicsserver   -webapi [off|filepath] Enable webapi or [off] to disable it or enable webapi and specify the webapi configuration file to use.   -graphicsserver [off] Enable graphics server or [off] to disable graphics server.   -model|-modelfile <filepath> Experior opens a model if the argument matches the name of an existing Experior model.   -phy|-physics Starts Experior in physics mode. (Only functional with the right privileges)   -variable Using variable time steps (physics mode). (Default: Experior is using fixed time step method)   frictiontype <Patch|OneDirectional|TwoDirectional> Starts the physics engine with the chosen friction type (only available in Physics mode). (Default: Experior is using Patch mode)   -physicsenginedynamics <Classic | Advanced> 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: Experior is using Classic dynamics)   -des|-event|-events Starts Experior in discrete Events mode. (Only functional with the right privileges)   -eng|-engineering Starts Experior in engineering mode. (Only functional with the right privileges)   -builder Starts Experior using ‘Builder’ profile. (Only functional with the right privileges)   -commissioner Starts Experior using ‘Commissioner’ profile. (Only functional with the right privileges)   -tester Starts Experior using ‘Tester’ profile. (Only functional with the right privileges)   -viewer Starts Experior using ‘Viewer’ profile.   -oem Start Experior in OEM licence mode. See OEM Setup (link)   -license <filepath|dongle[:id]>|offline[:id]> 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)   -licenseusage <id> Set the licenseusage property for web license usage tracking.   -forcecheckin Check-in web license when Experior closes without asking user.   -libs <directory> Set an additional libraries directory. (example: -libs C:\Projects\Demo\)   -logfilemode <none|file|filedate|filemodelname> Set the log file mode. (example: -logfilemode file)   -log <filepath> Set a temporary log directory. (example: -log C:\Experior\Logs\)   -workdir <directory> Set working directory (permanently). NOTE: this argument will not work in combination with another argument. The application will not be started – only the directory will be set. (example: -workdir C:\Experior\)   -debug [none|debug|detailed] Enable debug level ‘Debug’ or optionally set debug level to specified level.   -reset Reset the Working directory and reset configuration files to default settings.   Automated Testing -continuous Keep discrete event engine running.   -autostart Run the model when it is loaded.   -stopafter <duration> 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.   -atstart <sym/name> 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.   -timescale <scale> Specify the time scale to use. (example: -timescale 2.5)   -seed <seed> The seed used by the random generator.   -eventfile <filepath> Loads an event file (*.events). (this is only possible when a model file is loaded at the same time)

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