To support various Continous Integration (CI) setups, from Experior version 7.0.23105 onwards, you can now load unsigned catalogs and plug-ins – if using a Developer license.   The feature is two-folded. Part one is the skipping of signing the catalogs and plug-ins – this can be done in one of two ways.   Remove the Experior.Build UsingTask in the csproj – either by removing it entirely or adding a Conditional attribute. Or by configuring the Experior.Build by setting the new attribute ‘Skip=”true”‘.Example: <Experior.Build AssemblyFileLocation=”$(OutputPath)$(TargetFileName)” Debug=”true” Skip=”true”></Experior.Build> Now you are compiling/building the catalog or plug-in without signing it. Previously you would not be able to load the catalog or plug-in in Experior, but with the new version you are able to load them if you are using a valid Developer license.   A usescase could be to save time in CI pipelines. Visual Studio solutions with many plug-ins could use a substantial time just doing the signing process. These steps can now be avoided.   Note:   If you are using a non-developer license, catalog and plug-in checking is done as usual (catalogs and plug-ins must be signed) – meaning checksum and Key checking etc. will be performed as expected.   If you are using a Developer license and a valid ‘Tail’ / signing is found, then it also will be checked as usual. So the new feature is that Experior will allow catalogs and plug-ins without a tail.

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 developing custom catalogs you can add catalog restrictions to e.g. only allow specific Experior license IDs to load the catalog. The use case could be that you will restrict catalog usage to internal use only or similar.   There are 2 ways you can restrict catalog usage: using a Build.Config file or using a “Keys” attribute in the csproj   Restriction is opt-in, meaning that if you don’t wish to restrict catalog usage, then the default behaviour is that the catalog is complied without license ID / key restriction and everybody with a valid Experior license and physical access to the catalog will be able to load it.   Wildcards are supported for both subsequent solutions, so adding a license ID like ’02*’ will, allow all licenses starting with ’02’.   Using a Build.Config file: A ‘Build.config’ file can be used in the build process if you want to always restrict catalog usage and apply the restriction for all catalogs being built.   Process:   You create a file named ‘Build.config’. The contents should be valid XML <!--?xml version="1.0" encoding="utf-8"?--> <Key xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <Items> <string>0102</string> <string>0103</string> <string>02*</string> </Items> </Key>     The ‘Build.config’ file can be placed in one of three locations depending on your setup; Local to Experior.Build.dll Environment variable ‘EXPERIOR_SIGNTOOL_CONF’ %localappdata%\\Xcelgo\\Experior\\SDK\\Build”   Using a ‘Keys’ attribute   The ‘Keys’ attribute is the more explicit way, since here you are explicitly specifying per project (= catalog) which license IDs (“keys”) are allowed to load the catalog – and you can have it under version control since its part of the source code etc.   Process:   In the csproj for the catalog project, you find the signing Task (normally the <Experior.Build … /> element) and add a ‘Keys=”xxxx|yyyy|zz*”‘ attribute, where xxxx|yyyy|zz* are a ‘|’ separated list of license IDs.   Example: <Target Name="PluginSigning" AfterTargets="AfterBuild"> <Experior.Build AssemblyFileLocation="$(OutputPath)$(TargetFileName)" keys="0102|0103|02*"></Experior.Build> </Target>

Experior's Global Coordinate System   Experior 7 implements a left-handed, y-up coordinate system for its 3D environment as illustrated in the figure below, which is the view presented to the user when Experior is opened.   The x-axis is considered the forward vector in Experior. The y-axis is considered the up-vector in Experior.   For some models implemented in Experior, the different axises are also named as follows: x-axis = “Length” y-axis = “Height” z-axis = “Width”   This coordinate system is never moved. Experior's global coordinate system - left-handed, y-up.   Assemblies are placed in the global coordinate system, whereas individual parts in an Assembly are placed relative to the Assembly’s local coordinate system. An Assembly's global position in Experior (Orange dot - (1000mm, 410mm, 1000mm)). Conveyor sides (Boundaries) are objects added to the Assembly, hence they have a local position relative to the Assembly's global position.     To illustrate the concept in another way, the following images show an Assembly with 2 parts (Red/Blue Box).    In the left image, the Assembly is placed at global coordinate (0, 0, 0). The Parts are placed at local coordinates – Red box: (0, 0, 0) and Blue box: (0, 2, 0) respectively. The Blue box also has local Pitch rotation applied.   In the right side image, the Assembly is placed at global coordinate (4, 0, 3), where the individual Parts retain their local coordinate offsets.   An Assembly with 2 Parts (Red/Blue Boxes) placed at global position (0, 0, 0).   An Assembly with 2 Parts (Red/Blue Boxes) placed at global position (4, 0, 3), retaining their local offset positions.   Each Part in an Assembly also has its own local coordinate system, which is mostly relevant for rotations/orientations of the Part around its local center point, as illustrated above with local Pitch rotation applied to the blue Box Part.

With a developer license for Experior 7 it is possible to create custom catalogs, controllers, plugins and more in your Experior model. We have three different templates packaged in a .vsix (Visual Studio Integration Extension) file that you can download and run, as long as you have Experior 7 and Visual Studio installed. This .vsix is attached in this article in a zip file - Simply download and extract to run the installer.   To avoid confusion, we recommend removing the old Catalog, Controller and Plugin templates before installing the new ones. Removing old templates   To remove the old Visual Studio templates:   Close Visual Studio   Navigate to the C# visual studio template folder. The standard path for this is: C:\Users\ your username \Documents\Visual Studio 20XX\Templates\ProjectTemplates\(Visual) C#   Delete the zip files named: “Experior-7.0-Catalog-Template.zip”, “Experior-7.0-Plugin-Template.zip” and “Experior-7.0-Controller-Template.zip”.   If you get an error dialog saying: “This extension is already installed to all applicable products” You can navigate to: c:\users\[username]\AppData\Local\Microsoft\VisualStudio\17.0[hashid]\Extensions\   If any of the folders here contain Experior template files. Delete the folder. Then try running the VSIX installer again.   Output path   By default, the output path of the templates is set to the default installation location of the Experior executable.   This is defined by the environment variable: “EXPERIOR7_BIN” which is created when you install Experior 7 - by default: (C:\Xcelgo\Xcelgo Experior 7).   This means that when you build your project, the project output (*.dll) is created in that folder.   Make sure “Copy local” is set to “false” for Experior specific dll’s.   You can change this output path through the project properties. But in order for Experior to load it, you need to provide an External Libraries location.   This can be done in several ways: – Through the catalog selector’s External Libraries dropdown when Experior is started with “-config” – Through using a Startup Configuration file when Experior is started with “-startupconfiguration <file>” – Through an External Libraries path when Experior is started with “-libs <path>”   You can also manually drag and drop the dll from the folder you build to, into the Experior installation folder.   Warning:  When using an External Library folder, any dll that is present in both the External Library folder and the Experior installation folder causes errors.  

Prerequisites As a prerequisite for creating an OPC UA connection, an OPC UA server must be configured on your controller and must be started.   For a description of the procedure required for starting the emulation of Schneider Electric controllers from EcoStruxure Machine Expert, refer to the How to Emulate User Guide in the EcoStruxure Machine Expert online help. For information about starting an OPC UA server on a PacDrive LMC controller, refer to the OPC UA Server Configuration in the LMC Device Objects and Parameters part of the EcoStruxure Machine Expert online help. For information about starting an OPC UA server on a Modicon M262 Logic/Motion Controller, refer to the OPC UA Server Configuration in the M262 Logic/Motion Controller - Programming Guide in the EcoStruxure Machine Expert online help.   Creating an OPC UA Connection To create an OPC UA connection, proceed as follows: Step Action 1 In the Connections view, right-click inside the table and run the command OPC UA Client from the contextual menu. Result: A new row is added to the table with Protocol = OPC UA. 2 Select this row and configure the connection in the Properties view. 3 In the Communication section, edit the OPC Server Address parameter to enter the IP address and the port of the controller you want to connect to. Use the following format as an example, using the default port 4840: opc.tcp://127.0.0.0:4840 4 In the Connections view, right-click the row you created for the OPC UA connection and run the Connect command from the contextual menu. 5 Enter the Username and Password in the OPC UA Credentials dialog box. NOTE: If anonymous login is allowed by the OPC UA server, select the check box "Anonymous login" in the "Properties view"  to avoid this dialog box for future logins. Result: The message Untrusted Certificate is displayed. 6 Verify that you are about to connect to the correct URL and you trust the certificate. Click Yes to proceed or No to cancel. Result: After the connection to the controller is established, you can see Status = Connected displayed in the row of the selected connection. The available tags are read from the OPC UA server, as indicated in the Logs view by the messages Started reading tags and Finished reading tags. The controller variables can be selected within Experior 7.   OPC UA-Specific Settings in the Properties View The following settings of the Properties view are specific to OPC UA connections: Parameter Description Communication Auto Re-Connect Select this option to perform automatic reconnection attempts when the OPC UA connection is interrupted. Auto Re-Connect Delay Enter a delay for starting the first reconnection attempt after the connection has been interrupted and between the individual reconnection attempts. Default value: 5000 ms Infinite Re-Connect attempts Select this option for an unlimited number of reconnection attempts. The waiting time between each attempt is defined by the Auto Re-Connect Delay parameter. Auto Re-Connect Max. attempts Enter a maximum number of reconnection attempts. The waiting time between each attempt is defined by the Auto Re-Connect Delay parameter. Default value: 5 Anonymous Login If anonymous login is allowed in the OPC UA server (for details, refer to the description of the Disable anonymous login parameter in the OPC UA Server Configuration in the M262 Logic/Motion Controller - Programming Guide in the EcoStruxure Machine Expert online help) select this check box to avoid entering credentials. Communication Interval Enter the minimum delay (in ms) that must elapse between the OPC UA client data requests sent to the OPC UA server. Default value: 16 ms NOTE: Consider the impact this polling frequency can have on the performance of the OPC UA server when reducing the value. If you transfer a large amount of data using an OPC UA connection, consider increasing the polling frequency to avoid slowing down the performance of the OPC UA server. OPC Server Address Enter the IP address and the port of the controller you want to connect to. Use the following format as an example, using the default port 4840: opc.tcp://127.0.0.0:4840 Use Publish-Subscribe Select this check box to activate the publish/subscribe data exchange between the OPC UA client and server.

The Experior 7 implementation of the RFC1006 protocol is not the full implementation specified in the public RFC1006 protocol specification.   We have focused on creating a simple and reliable communication protocol and the implementation has primarily been developed in order to meet the Siemens SIMATIC PLC requirements.   The RFC1006 protocol is designated ISOonTCP in a Siemens PLC. Note that the protocol specified in this manual is implemented in full by Siemens PLC network card, i.e. no user program necessary to implement this protocol.   Properties Identification Name – Customizable name Id – Customizable Id   Communication Port Number – Port used for communication between Experior and “Device” IP Address – Type in IP address (only available if Mode = Client) Mode – Select “Server” or “Client” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device” Auto Connect Delay – Set delay for when the connection will try to reconnect   RFC1006 Remote TSAP – Address of Remote TSAP (Transport Service Access Point) Local TSAP – Address of Local TSAP (Transport Service Access Point) Connection Id – Connection Id used Max TPDU Size – TPDU (Transport Protocol Data Units) maximum size Max TPDU Bytes – TPDU (Transport Protocol Data Units) maximum bytes used Send Connection Request – Activate or Deactivate whether or not a connection request is to be sent Sign Of Life – Activate or Deactivate whether or not Sign Of Life signal is to be used Sign Of Life Interval – Set the time interval between Sign Of Life requests (only Available if Sign Of Life is checked) Sign Of Life Timeout – Set the timeout value (only Available if Sign Of Life is checked)

The 3964R-Protocol is a serial point-to-point protocol for communication between two programmable logic controllers (PLC). Can be set up to use an ethernet connection or a serial (RS-232/RS-422/RS-485).   TCP/IP Properties Identification Name – Customizable name Id – Customizable Id   Communication Port – Port used for communication between EcoStruxure Machine Expert Twin and “Device” Mode – Select “Server” or “Client” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Serial Properties Line Signals DTR – Select if DTR (Data Terminal Ready) is to be used RTS – Select if RTS (Request To Send) is to be used Handshake – Choose from ‘XOnXOff’, ‘RequestToSend’ or ‘RequestToSendXOnXOff’ handshake protocols   Port Settings Port Name – Select the name of the port Baud Rate – Select the baud rate at which to connect Data Bits – Enter the number of data bits to be used Stop Bits – Choose from ‘One’, ‘Two’ or ‘OnePointFive’. Parity – Choose from ‘Odd’, ‘Even’, ‘Mark’ or ‘Space’   Identification Name – Customizable name Id – Customizable Id   Communication Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device” Auto Connect Delay – If Auto connect is checked you can set a delay (in miliseconds) after which the connection will attempt a reconnection

STX/ETX is a high level transport protocol used for exchanging messages with exterior systems. The message is sent as a test starting with STX (Start of Text) character and ends with the ETX (End of Text) character. Can be set up to use ethernet (TCP/IP) or a serial (RS-232/RS-422/RS-485) connection.   TCP/IP Properties Identification Name – Customizable name Id – Customizable Id   Communication Port – Port used for communication between Experior and “Device” Mode – Select “Server” or “Client” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Serial Properties Line Signals DTR – Select if DTR (Data Terminal Ready) is to be used RTS – Select if RTS (Request To Send) is to be used Handshake – Choose from ‘XOnXOff’, ‘RequestToSend’ or ‘RequestToSendXOnXOff’ handshake protocols   Port Settings Port Name – Select the name of the port Baud Rate – Select the baud rate at which to connect Data Bits – Enter the number of data bits to be used Stop Bits – Choose from ‘One’, ‘Two’ or ‘OnePointFive’. Parity – Choose from ‘Odd’, ‘Even’, ‘Mark’ or ‘Space’   Identification Name – Customizable name Id – Customizable Id   Communication Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device” Auto Connect Delay – If Auto connect is checked you can set a delay (in miliseconds) after which the connection will attempt a reconnection

Connect to a PLC using a serial (RS-232/RS-422/RS-485) connection.   Properties Line Signals DTR – Select if DTR (Data Terminal Ready) is to be used RTS – Select if RTS (Request To Send) is to be used Handshake – Choose between ‘XOnXOff’, ‘RequestToSend’ or ‘RequestToSendXOnXOff’ handshake protocols   Port Settings Port Name – Select the name of the port – ‘COM1’ as an example Baud Rate – The baud rate at which to connect Data Bits – Enter the number of data bits to be used Stop Bits – Choose from ‘One’, ‘Two’ or ‘OnePointFive’ Parity – Choose from ‘Odd’, ‘Even’, ‘Mark’ or ‘Space’   Identification Id – Customizable Id Name – Customizable name   Timeout Frame timeout – To mark the end of a message, the serial raw connection waits for a timeout. You can set the time for when the timeout triggers an end of message but the default is after 0.1 seconds   Communication Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Memory Allocation (PLC Input) Automatic – Activate or Deactivate automatic memory allocation Length – Enter data length (only available if Automatic is unchecked) Offset – Enter memory offset (only available if Automatic is unchecked)   Memory Allocation (PLC Output) Automatic – Activate or Deactivate automatic memory allocation Length – Enter data length (only available if Automatic is unchecked) Offset – Enter memory offset (only available if Automatic is unchecked)

If Allen Bradley or Omron controllers are being used then Ethernet/IP-CIP needs to be selected from the list of protocols.   Properties Identification Id – Customizable Id Name – Customizable name   CPU  Slot Number – Enter the slot number of the PLCs CPU Rack Number – Enter the rack number of the PLCs CPU Type – Controller family: LGX, SLC, PLC5 Max Package Size – How much data you can send pr. package   Size Choose between SINT, INT and DINT   Communication Type in IP address (only available if Mode = Client) Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device” Port – Port used for communication between Experior and “Device”   Memory Allocation (PLC Input) Automatic – Activate or Deactivate automatic memory allocation Source Name – Input – static value, can’t be changed (only available if Automatic = False) Length – Set data length (only available if Automatic = False) Offset – Minimum offset (only available if Automatic = False)   Memory Allocation (PLC Output) Automatic – Activate or Deactivate automatic memory allocation Source Name – Output – static value, can’t be changed (only available if Automatic = False) Length – Set data length (only available if Automatic = False) Offset – Minimum offset (only available if Automatic = False)

Fetch/Write is a protocol to communicate with a Siemens PLC. If you are using a Siemens 1200 or 1500 series PLC, you will need to grant Experior full access through TIA.   Properties for Fetch Identification Name – Customizable name Id – Customizable Id   Communication Port – Port used for communication between Experior and “Device” IP Address – Type in IP address (only available if Mode = Client) Mode – Select “Server” or “Client” Source – Choose the data area to be read from. Options are Flag Area(M), Input(I), Output(Q), Data Block(DB), Counter Cells(C) or Timer Cells(T) Update Interval – Measured in milliseconds. Less than 25ms activates fast mode updating Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Memory Allocation Automatic – Activate or Deactivate automatic memory allocation Length – Set data length (only available if Automatic = False) Offset – Set offset for data (only available if Automatic = False) Properties for Write Identification Name – Customizable name Id – Customizable Id   Communication Port – Port used for communication between EcoStruxure Machine Expert Twin and “Device” IP Address – Type in IP address (only available if Mode = Client) Mode – Select “Server” or “Client” Destination – Choose the data area to be written to. Options are Flag Area(M), Input(I), Output(Q), Data Block(DB), Counter Cells(C) or Timer Cells(T) Synchronized – Activate and Deactivate synchronization Auto Connect – Activate or Deactivate whether EcoStruxure Machine Expert Twin should try to automatically connect to the “Device”   Memory Allocation Automatic – Activate or Deactivate automatic memory allocation Length – Set data length (only available if Automatic = False) Offset – Set offset for data (only available if Automatic = False)

The S7 Functions is a protocol to communicate with a Siemens PLC.   Important: The S7-3xx PLCs have a limitation (that cannot be changed) of PDU (Protocol Data Unit) data size 220 bytes. This is the number of bytes that can be read/written in single operation. The most obvious way to overcome this is to add multiple connections if you expect to exceed 220 bytes in length.   In Experior it is possible to allocate more than 220 bytes per connection but data will then be transmitted in fractions of maximum 220 bytes. Allocating 440 bytes on one connection should have same impact on the PLC performance-wise as setting up two connections with 220 bytes allocated on each.   In both cases Experior will make two read/write operations.   But it is very important not to have too many unused bytes allocated: If there are some addresses in Experior that are positioned in the address area between 0 and 100 and the next address area of interest to the emulation is in the address area from 300 to 500 then it is important to split into two connections: one connection operating in the area between 0 and 100 and another connection operating in the area from 300 to 500. Unless there will in the current example be three read/write operations instead of only two.     If the length exceeds 220 bytes there will be a notification on the connection icon:   It is also important to consider the update internal (see the description of the different properties below): If there are signals that has to be transmitted to the PLC as fast as possible, it is advised that these signals are isolated in a separate connection where only inputs are associated with this connection (like encoder and pulse generator signals). In the same way, if there are signals that does not have to be updated that frequently (like buttons and lamps) it is advised to isolate those signals on a separate connection and then set a higher update interval. Then the PLC have more “time” to answer the request from the connections with a smaller update interval.   Properties Identification Name – Customizable name Id – Customizable Id   Address Rack – Number of rack that is being connected to Slot – Number of slot where CPU is located   Communication IP Address – Type in IP address Update Interval – Measured in milliseconds. Less than 10ms activates fast mode updating Auto Connect – Activate or Deactivate whether EcoStruxure Machine Expert Twin should try to automatically connect to the “Device”   Memory Allocation (PLC Input) Automatic – Activate or Deactivate automatic memory allocation Source Name – Input – static value, can’t be changed (only available if Automatic = False) Length – Set data length (only available if Automatic = False) Offset – Minimum offset (only available if Automatic = False)   Memory Allocation (PLC Output) Automatic – Activate or Deactivate automatic memory allocation Source Name – Output – static value, can’t be changed (only available if Automatic = False) Length – Set data length (only available if Automatic = False) Offset – Minimum offset (only available if Automatic = False)   If you are using a Siemens 1200 or 1500 series PLC, you will need to grant Experior 7 full access through TIA.

Experior.Core.Communication.PLC.Input and Experior.Core.Communication.PLC.Output are classes used to communicate with a PLC.   When they are added to an assembly and made available through a property in the Property window then the Experior user will be able to link the Input with an available connection and specify the address or Byte/Bit depending on the Size. By default this is DataSize.BOOL and hence corresponds with one bit.   You can obtain the corresponding connection through the Connection property and get the address/byte/bit through the properties Byte and Bit (in case the Size is not a DataSize.BOOL the starting address can be found in the Byte property and the Bit property will be “None”).   DataSize Size   The Size property returns what type of data is defined to be exchanged using Input/Output. By default this is DataSize.Bool.   Other possible values are: DataSize.BYTE this is a single byte (8bits) DataSize.WORD this is unsigned 16 bits DataSize.INT this is signed 16 bits DataSize.DWORD this is unsigned 32 bits DataSize.DINT this is signed 32 bits DataSize.STRING this is an array of characters DataSize.ARRAY this is an array of bytes DataSize.FLOAT this is a floating point DataSize.REAL this is a floating point DataSize.REAL32 this is a signed 32 bits DataSize.LINT this is a signed 64 bits DataSize.LREAL this is a 64 bit floating point DataSize.LWORD this is unsigned 64 bit DataSize.SINT this is a signed 8 bit   When the Size property is either DataSize.STRING or DataSize.ARRAY then the length of the string/array can be specified in the Length property.   In the example below the creation of different input output objects is illustrated. In addition, the usage of events to react upon receiving of input and sending of a string messages is shown.   using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; using System.Windows.Media; using System.Xml.Serialization; using Experior.Core.Assemblies; using Experior.Core.Communication.PLC; using Experior.Interfaces; [Serializable] [XmlType(TypeName = "Experior.Catalog.ExampleAssemblies.ExampleInputOutputInfo")] public class ExampleInputOutputInfo : AssemblyInfo { // we add our Output and Input objects into the corresponding info object of // the assembly so that is completely saved (serialised) and restored (deserialised) // when saving and loading the model it is in. public Output outputbit; public Output outputdata; public Input inputbit; public Input inputdata; public int maxnumberofcharacters = 12; } public class ExampleInputOutput : Assembly { private ExampleInputOutputInfo info; public ExampleInputOutput(ExampleInputOutputInfo info) : base(info) { if (info.outputbit == null) { //create Output object by default the size is one bit info.outputbit = new Output(); // give it a description info.outputbit.Description = "Block/Unblock"; } //add the output to the environment so that it becomes visible in the Output window Add(info.outputbit); // send the initial value // 0 when NoNC is Normally Open // 1 whent NoNC is Normally Closed info.outputbit.Off(); if (info.outputdata == null) { info.outputdata = new Output(); info.outputdata.Description = "Send Barcode"; } info.outputdata.Size = DataSize.STRING; info.outputdata.Length = MaxNumberOfCharacters; //add the output to the environment so that it becomes visible in the Output window Add(info.outputdata); // create a Input object to receive a signal (usually from the PLC) if (info.inputbit == null) { info.inputbit = new Input(); info.inputbit.Description = "SignalA"; } info.inputbit.On += new Input.OnEvent(inputbit_On); info.inputbit.Off += new Input.OnEvent(inputbit_Off); info.inputbit.OnNoNcChanged += new Register.NoNcChangedEvent(inputbit_NoNcChanged); //add the input to the environment so that it becomes visible in the Input window Add(info.inputbit); // create a Input object to receive a signal (usually from the PLC) if (info.inputdata == null) { info.inputdata = new Input(); info.inputdata.Description = "LoadDestination"; } // we will receive a string of maximum MaxNumberOfCharacters info.inputdata.Size = DataSize.STRING; info.inputdata.Length = MaxNumberOfCharacters; info.inputdata.OnReceived += new Input.ReceivedEvent(inputdata_Received); //add the input to the environment so that it becomes visible in the Input window Add(info.inputdata); } void inputdata_Received(Input sender, object value) { if (value != null) { // because inputdata.Size = DataSize.STRING the value we receive will be a string so we can cast it to a string string data = (string)value; Experior.Core.Environment.Log.Debug.Write("Received " + data); Experior.Core.Environment.Log.Write("Received " + data); } Experior.Core.Environment.Diagnostic.Message("Inputdata was defined at address " + sender.ByteNo); Experior.Core.Environment.Diagnostic.Message("Inputdata has value " + sender.Value); } void inputbit_Off(Input sender) { // this will be called when we received an Off message for the input bit // this is 0 when NO (NormallyOpen) or 1 when NC (Normally Closed) Experior.Core.Environment.Diagnostic.Message("Input " + sender.ToString() + " off value " + sender.Value, System.Windows.Media.Colors.Green, Experior.Core.Environment.DiagnosticAction.STICKY, Experior.Core.Environment.Signs.Warning); } void inputbit_On(Input sender) { // this will be called when we received an Off message for the input bit // this is 0 when NO (NormallyOpen) or 1 when NC (Normally Closed) Experior.Core.Environment.Diagnostic.Message("Input " + sender.ToString() + " on value " + sender.Value, System.Windows.Media.Colors.Green, Experior.Core.Environment.DiagnosticAction.TEMPORARY, Experior.Core.Environment.Signs.Check); // send a message to info.outputdata OutputData.Send("Hello World!"); } void inputbit_NoNcChanged(IRegister sender) { Experior.Core.Environment.Diagnostic.Message("Input " + sender.ToString() + " changing NO/NC value to " + sender.NormallyClose, System.Windows.Media.Colors.Green, Experior.Core.Environment.DiagnosticAction.ALARM, Experior.Core.Environment.Signs.None); Experior.Core.Environment.Diagnostic.Message("Input was defined for byte " + ((Register)sender).ByteNo + " and bit " + sender.BitNo); } public override void Dispose() { if (((ExampleInputOutputInfo)info).inputbit != null) { ((ExampleInputOutputInfo)info).inputbit.On -= new Input.OnEvent(inputbit_On); ((ExampleInputOutputInfo)info).inputbit.Off -= new Input.OnEvent(inputbit_Off); ((ExampleInputOutputInfo)info).inputbit.OnNoNcChanged -= new Register.NoNcChangedEvent(inputbit_NoNcChanged); } if (((ExampleInputOutputInfo)info).inputdata != null) { ((ExampleInputOutputInfo)info).inputdata.OnReceived -= new Input.ReceivedEvent(inputdata_Received); } base.Dispose(); } public Input InputBit { get { return ((ExampleInputOutputInfo)info).inputbit; } set { ((ExampleInputOutputInfo)info).inputbit = value; } } public Input InputData { get { return ((ExampleInputOutputInfo)info).inputdata; } set { ((ExampleInputOutputInfo)info).inputdata = value; } } public Output OutputBit { get { return ((ExampleInputOutputInfo)info).outputbit; } set { ((ExampleInputOutputInfo)info).outputbit = value; } } public Output OutputData { get { return ((ExampleInputOutputInfo)info).outputdata; } set { ((ExampleInputOutputInfo)info).outputdata = value; } } public int MaxNumberOfCharacters { get { return ((ExampleInputOutputInfo)info).maxnumberofcharacters; } set { ((ExampleInputOutputInfo)info).maxnumberofcharacters = value; } } public override string Category { get { return "ExampleInputOutput"; } } public override ImageSource Image { get; } = Common.EmbeddedImageLoader.Get("Cube"); }

There are two different ways to connect to a PLC depending on whether you use a tag based or an address based connection. If you wish to use a tag based connection you have to start by connecting to the PLC in the Connections window. If you want an address based connection you have to wait to connect to the PLC in the connections window until you have chosen the right settings for the object, you wish to connect.    It is possible to connect most assemblies and controls in the model to a PLC, such as connecting a lamp or a sensor. You have to choose which PLC you wish to connect to for each individual input and output, not just for the assembly as a whole.  If you only have one PLC in the connections window, the object will automatically choose this PLC. If you have more than one PLC  you can choose which PLC to connect to in the assembly’s properties window under ‘connection id’. Having the PLCs connected already only works if you want to use a tag based connection on the object. Then, when you have chosen which PLC to connect to, you can see a list of tags in the properties window. Choose the corresponding tag and the object will be connected to the PLC.   If you wish to use an address based connection you have to start by going to the properties window for the object you wish to connect. Here you should find the PLC input or PLC output category and press the toggle arrow on the side of the category:   Now you can go to the Address field and type in the address for your PLC. You can also choose the right source in the source field. Then you can go to the connections window and connect the PLC so the object will begin sending information to your PLC.

Below the model window is a broad window with multiple functions:   1. Logs   The logs are where you can see feedback from Experior. It will give you different information on how the program is running as well as error messages and warnings if something is not working correctly. All the feedback comes with a timestamp, so you can see when it happened. This makes the logs a great tool for debugging. The feedback comes in four different colors as well as a color that matches the theme (which in this example is white):   Above the feedback window is a checkbox marked ‘tail’: By checking this checkbox you make sure that the logs window is always showing the bottom of the feedback reel.   If you right click on any of the messages in the feedback reel you will see a menu which looks like this:   CLEAR: Delete all messages in the log. COPY: Copy the highlighted text INSERT SEPARATOR: Insert a separator line at the bottom of the feedback reel.   If you click on one of the log messages you will see further information about it and be able to customize the log in the Properties window: MESSAGE: FONT: Set the font in which the log messages are displayed MODE: Choose between displaying the messages in color or monochrome TIME/CLOCK: Choose the log format for the messages. The chosen format is displayed below in the ‘log format’ line SEARCH: Will highlight any assemblies whose name matches any word in the chosen log message FILE: MODE: Choose the way the files name is displayed LOGFILE WRAP MODE: Lets you choose if and when a new log file is created FILTER: TEXT: Write any text you want the log to filter by from then on. Only messages containing this text will be shown in the log TYPE: Choose which types of messages you want to be shown in the log HIGHLIGHT: TEXT: Write any word you want highlighted in the log COLOR: Choose the color which is used to highlight   2. Loads   This window shows the loads in the scene. When you open a new model, the loads window will be empty like above. If you then add one or more loads to the scene, right click in the loads window and then press refresh the loads will show up in the window like so:   The ‘Identification’ column shows the identifier (usually a barcode) of each load (here called Unknown). If you wish to change the identifier of the load you can do so in the identification box in the properties window.  The ‘Next’ column shows the next action point the load will hit. ‘Destination’ shows the loads final destination.   If you select one of the loads, the model window will show you this specific load. The Properties window will then display the information of that specific load:   Here you can get information about the loads weight, position etc. The ‘Identification’ line will let you give the load a name to distinguish loads from each other. The color line will let you change the color of the load.    3. Inputs & Outputs   The input/output (IOs) are only relevant when dealing with low level connections. The inputs tab shows which inputs the PLC gets while the outputs tab shows the outputs from the PLC. The tabs look like this when empty:   If you right click on the empty input or output window you will see a menu that looks like this:   ADD: Add a new input or output for the PLC. You can also add a new input or output through assemblies REFRESH: Refresh the widow. The window will normally refresh automatically, but you can refresh it here manually if you want to EXPORT: Export inputs or outputs as an Excel file    From this menu you can add an input or output. They will then show up as a line in the input or output tab like this:   The lines turn black when you select them (see the first line in the picture above). Any red boxes inform you that the box has not yet been correctly filled out. In the Properties window you can change the symbol and the description of the IO.   4. Alarms   The alarms window is where you can see any alarms which you have set. You can set an alarm by right clicking a connection in the connections window and choosing the ‘alarm’ feature. Once you have added an alarm, the window will look like this:   The ‘Connection’ column shows which PLC connection the alarm belongs to. The ‘Alarm’ column shows the description which you have set for the specific alarm (in this case set as ‘alarm description’).   When the alarm goes off it shows up in the alarms window but it will also show up as a warning in the display below the model:   5. Nodes - Only for Discrete Events Mode   The nodes window shows your action points in discrete events mode. When the window is empty it looks like this:   If you want to add an action point first you must make sure you have a conveyor or a track in the scene to add the action point to. Right click the assembly and choose ‘insert action point’. The action point is represented by an x on the assembly. If you then right click in the nodes window and press ‘refresh’ the action points will show up:   Now you can see the properties of the action point in the properties window. From there you can change different attributes of the action point such as its name, color and visibility as well as whether the action point is locked or not.    6. Schedule     The schedule is where you schedule certain events to happen at specific times. If you right click in the schedule window a menu will pop up giving you the option to add a scheduled event. When you have added an event you will be able to change the settings for the scheduled event in the properties window:   TIME: Set the time for when the event will occur ACTION: Choose which action happens when the set time occurs DESCRIPTION: Enter a description of the scheduled event ENABLED: Set whether the event is active or not   ACTION MENU PAUSE: Pauses the model RESET SCENE: Resets the model RESET REPORTS: Resets internal counts (e.g. statistics)  REPORT SNAPSHOT: Save a report of the model. The report will be saved as an Excel file at the same location as your model is saved. It will be named the name of the model + the time stamp CHANGE VIEW: Change the camera angle (see below) TERMINATE: Terminate Experior SCRIPT: Write your own code to determine what happens when the event occurs (see below)   CHANGE VIEW PROPERTIES WINDOW: With the change view action you can get Experior to change the viewing angle on the model when the event occurs. In the ‘view’ box you can choose any camera view you have preset (click here to see how). You can also set if you want the action to fly to the new camera view or jump to it. If you choose fly, you can set how fast it flies.   SCRIPT PROPERTIES WINDOW: The script action is a little different from the others. By pressing the source box three little dots at the end of it will appear. When you click on them it opens a script window where you can write your own code to specify what is supposed to happen when the event occurs.    When an event occurs it will be highlighted in blue in the schedule window. To delete a scheduled event simply right click the event and choose ‘delete’.   7. Change History   When you place an assembly on to the model or change something in the model, the change will be recorded in the ‘change history’ window like this:   If you right click on any of the actions in the change history window you will be able to undo the action. You can undo your latest actions with the ‘undo’ button in the edit menu but by going in to the change history window you will be allowed to undo specific changes you did further back without loosing everything you have done since.

  The properties window displays the developer defined properties of the selected item. The window can show properties for objects like assemblies, buttons in the control panel or connections. For instance every assembly has a properties panel where alterations and specifications to different attributes can be made. Some of the properties of each item are customizable while others are locked stats which are displayed.   The customizable properties show up in white while locked information shows in gray:   The search bar at the top of the window allows you to search for any specific properties. Next to it are two buttons that lets you choose how your properties are displayed:   These buttons lets you choose if you wish to see all properties as one long list or if you prefer to have them separated into different categories.    

When the Experior layout is set to default mode, you will find the Solution Explorer and Statistics window on the top right side of the screen. This window has a few different functions:   1. Solution Explorer   The Solution Explorer contains a tree structure that lets you see every assembly you have placed onto the model floor. It has three different categories: assemblies, motors and controllers. Assemblies is sorted into sections which then shows each assembly that section contains. In the Solution Explorer you can get a quick overview of every single thing, you have placed. If you click on any of them, the model will highlight that assembly for you. You can move assemblies between different sections by dragging them into another section tab or by choosing the assembly you want to move and then changing the section it is placed under in the properties window. You can rename sections by clicking on the section and then change the name in the properties window.   If you right click on the assemblies tab, you will see a menu that looks like this:    In the menu you can choose to add a section or show all sections. You can also Collapse All which will close all the subcategories you have open. If you right click on the motors tab (motor tab is only available in Physics Mode), you will also be able to collapse all. Right clicking on the controllers tabs will open a menu which says ‘Load’. Here you can load a controller file (.DLL format) into Experior. When the controller is loaded it shows up in the Solution Explorer window like this:   If you open the assemblies menu and right click on the sections you will see a new menu:   HIDE ALL SECTIONS BUT THIS: See only this section SHOW ALL SECTIONS: See all the sections again HIDE ASSEMBLIES: Hides all assemblies as well as the floor of that section LOCK ASSEMBLIES: Locks every assembly you have placed up to that point but does not not lock new assemblies you place FIT: Resizes the floor to fit around the assemblies placed in the model DELETE (Name): Delete the chosen section. It is not possible to delete the last section to have no sections DISABLE ASSEMBLIES: When you disable the assemblies of a section all the assemblies placed in that section will turn gray to show they are disabled. When you for example place a load on a disabled assembly it will fall trough the assembly when you start the model COLLAPSE ALL: Collapses the tree hierarchy    If you right click on one of the assemblies in the assemblies tab, you will have the choice to either disable the assembly or delete it. If you right click on a motor you will have the choices to start the motor, copy it, disable it or delete it.    The solution explorer window also has a few more options to individualize the window. In the right corner you will see a small tack which will allow you to ‘auto hide’ the window. Pressing this will place the window as a bar just below the Experior menu like this:     To reset it go to the View menu and press reset. Below the tack is a search bar where you can search for any assembly or motor you have placed on the model floor and next to that is a button with three lines that will let you choose whether or not you want to see the assemblies assorted into categories.   2. Statistics The statistics window displays information about the loads in the model:   You can get information from a specific sensor or button by adding it to the statistics window. To do this you right click on the sensor you want to display and choose ‘Observe’. Now the sensor shows up in the statistics display under the Loads line:     You can observe different types of sensors, scanners, weights, counters and eaters. The scanners will show information about how many loads they have scanned, while the buttons show how many times they have been pressed.   If you want to change the name of any of the sensors just click on the sensor in the model and its information will show up in the properties window. From here you can change the name. To display the new name simply right click the sensor, uncheck ‘Observe’ and check it again. Now the sensor should show up in the statistics window with its new name.

The control panel allows you to insert controls for communicating with the PLC. By right clicking on an empty square of the control panel you will open a control menu, from which you can choose different types of controls:   The only difference between the first six controls is variation in design. The buttons work when you press them while the lamps light up when a specific PLC signal is sent. The knob button allows you to switch between many different values, which you can choose in the properties window. The gauge will show values sent from the PLC. ‘Switches’ allows you to choose between two state and three state switches:     When you have chosen a control, you can see its properties in the ‘Properties’ window. You will also be able to change its name and color here as well as changing different other values for the control:   If you right click the button you can either delete it or copy it to get another button with the exact same attributes.   If you right click on the ‘controls’ tabs at the top of the control panel you will see a menu allowing you to make changes to the tab:     RIGHT: Allows you to move the controls tab right to change the order of the tabs. NEW CONTROL PANEL: Create a new control panel DELETE (Tab name): Delete the tab with the corresponding name DELETE ALL: Delete every controls tab UNDOCK: Move the controls tab around to another position in the Experior window ALIGNMENT: Choose where in the control panel the controls tabs are situated