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

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

If you are using a Siemens 1200 or 1500 series PLC, you will need to grant Experior full access through TIA.   Open project in TIA Go to PLC properties Under General tab select Protection Make sure Full Access is selected as shown in the figure Check Permit access with PUT/GET communication from remote partner as shown in the figure below  

Connect to a PLC using a serial (RS-232/RS-422/RS-485) connection.   Properties Identification Name – Customizable name Id – Customizable Id Port Settings Port Name – Select the name of the port, COM1 for example Baud Rate – Select the baud rate at which to connect Parity – Choose from Odd, Even, Mark or Space Data Bits – Enter the number of data bits to be used Stop Bits – Choose from One, Two or OnePointFive 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 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 = False) Offset – Enter memory offset (only available if Automatic = False) Memory Allocation (PLC Output) Automatic – Activate or Deactivate automatic memory allocation Length – Enter data length (only available if Automatic = False) Offset – Enter memory offset (only available if Automatic = False)

Select this protocol if TwinCAT Controllers are being used.   Properties Identification Name – Customizable name Id – Customizable Id Communication Port – Port used for communication between Experior and “Device” IP Address – IP Address of the Beckhoff Controller Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”  

STX/ETX is a high level transport protocol used for exchanging messages with exterior systems. Can be set up to use serial (RS-232/RS-422/RS-485) or an ethernet connection.   TCP/IP Properties   Identification Name – Customizable name Id – Customizable Id Validation MVT – Select the MVT (Message Validation Template) being used for this protocol 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” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Serial Properties Identification Name – Customizable name Id – Customizable Id Port Settings Port Name – Select the name of the port, COM1 for example Baud Rate – Select the baud rate at which to connect Parity – Choose from Odd, Even, Mark or Space Data Bits – Enter the number of data bits to be used Stop Bits – Choose from One, Two or OnePointFive. 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 Communication Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”

The 3964R-Protocol is a serial point-to-point protocol for communication between two programmable logic controllers (PLC). Can be set up to use a serial (RS-232/RS-422/RS-485) or an ethernet connection.   TCP/IP Properties Identification Name – Customizable name Id – Customizable Id Validation MVT – Select the MVT (Message Validation Template) being used for this protocol 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” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Serial Properties Identification Name – Customizable name Id – Customizable Id Port Settings Port Name – Select the name of the port, COM1 for example Baud Rate – Select the baud rate at which to connect Parity – Choose from Odd, Even, Mark or Space Data Bits – Enter the number of data bits to be used Stop Bits – Choose from One, Two or OnePointFive 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 Communication Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”

The Experior implementation of the RFC1006 protocol is not the full implementation specified in the public RFC1006 protocol specification.   Xcelgo has 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 Validation MVT – Select the MVT (Message Validation Template) being used for this protocol 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” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device” 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 = True) Sign Of Life Timeout – Set the timeout value (only Available if Sign Of Life = True)

List and modify Assembly names Changing part of Assembly name for all assemblies which name contains “UC1”   int startindex = 5; string changefrom = "MC02"; string changeto = "MC01"; foreach (var item in Experior.Core.Assemblies.Assembly.Items.Values) { if (item.Name.Contains("UC1")) { int lenght = item.Name.Length - startindex; Log.Write("Assembly name = " + item.Name.Substring(startindex, lenght)); Log.Write("Assembly name = " + item.Name.Replace(changefrom, changeto)); item.Name = item.Name.Replace(changefrom, changeto); item.Name = "=" + item.Name; Log.Write("bool " + item.Name.Replace(changefrom, changeto)); } }   List and set Normally Closed on photocells Search for all photocells in “Model” Set “Normally open/Normally closed” to “normally closed Print status and name foreach (var item in Experior.Core.Assemblies.Assembly.Items.Values) { if (item is Experior.Catalog.Logistic.PhotoEye) { ((Experior.Catalog.Logistic.PhotoEye)item).plcActivation.NoNc = NormallyClosed; Log.Write(((Experior.Catalog.Logistic.PhotoEye)item).plcActivation.NoNc.ToString()); Log.Write("Photcell name = " + item.Name); } }   List and modify Cylinder Lookup all Cylinders (Basic Catalog Cylinder) in model   Change cylinder Roll by 90 degrees foreach (var cyl in Experior.Core.Assemblies.Assembly.Items.Values) { if (cyl is Experior.Catalog.Logistic.Cylinder && cyl.Color == Color.Yellow) { Log.Write(cyl.Name); cyl.Roll = (float) Math.PI / 2; } }   Modify Motor Frequency Converter Symbol Look for a specific motor (contains “CO400) in its name Set Motors Connection ID Set the frequency converters symbol Print out motor name and symbol name foreach (var motor in Experior.Core.Motors.Motor.Items.Values) { if (motor.Name.Contains("CO400")) { motor.InputSpeed.ID = "Connection1"; motor.InputSpeed.Symbol = "CO400.M1_FQ1"; Log.Write("Name = " + motor.InputSpeed.Name + " Symbol = " + motor.InputSpeed.Symbol ); } }   List and modify Motor Names Changing part of Motor name for all Motors which name contains “UC2” int startindex = 5; string changefrom = "MC02"; string changeto = "MC01"; foreach (var motor in Experior.Core.Motors.Motor.Items.Values) { if (motor.Name.Contains("UC2")) { int lenght = motor.Name.Length - startindex; Log.Write("Assembly name = " + motor.Name); Log.Write("Assembly name = " + motor.Name.Substring(startindex, lenght)); Log.Write("Assembly name = " + motor.Name.Replace(changefrom, changeto)); motor.Name = motor.Name.Replace(changefrom, changeto); motor.Name = "=" + motor.Name; } }   List and modify PLC Inputs Changing or updating a Symbol name will result in overwriting current symbol name( or tag) on the Input.   foreach (var i in Experior.Core.Communication.PLC.Connection.Inputs.Items) { Log.Write("ID = " + i.ID + " Source = " + i.Source + " Symbol = " + i.Symbol + " Name = " + i.Name); i.Source = "0 - CON1"; i.ID = "0 - CON1"; i.Symbol = i.Name; Log.Write("input name = " + i.Symbol); }   List and modify PLC Outputs Changing or updating a Symbol name will result in overwriting current symbol name( or tag) on the Output.   string changefrom = "string1"; string changeto = "string2"; foreach (var o in Experior.Core.Communication.PLC.Connection.Outputs.Items) { Log.Write("ID = " + o.ID + " Source = " + o.Source + " Symbol = " + o.Symbol + " Name = " + o.Name); o.Source = "0 - CON1"; o.ID = "0 - CON1"; o.Symbol = o.Name; o.Symbol = o.Name.Replace(changefrom, changeto); Log.Write("output name = " + o.Symbol);   Set Output Bit From Code public class Main { public void On(object trigger, string symbol) { if (symbol == "Init") { //Connection id /*Output.On(string Symbol)'*/ /*Output.On(String Symbol,string source)'*/ /*Output.On(int id, int byteno, int bitno)'*/ /*Output.On(int id, string source, int byteno, int bitno)'*/ //for AB plc Output.On(1, "Local_4", 231, 6); // connection id 1, source, Byte, bit //for Siemens Output.On(0, "1", 1, 6); // connection id 0, source (DB1), Byte, bit } } }

Before you start, make sure you have the Universal Robots Experior catalogs: • Experior.Catalog.UniversalRobots.dll • UniversalRobotsCommunication.dll   Afterward, follow these steps   Robot controller connection The following steps will connect the Experior URX assembly to the robot controller in URSim.   1. Place the Experior UR catalog (.dll) files in the Experior 6 installation folder (usually C:\Xcelgo\Xcelgo Experior 6).   2. Download and unpack/install the following: a. UR Non-Linux Offline simulator virtual machine (URSim):  b. VMware Workstation Player    3. Open VMware Workstation. Open the URSim virtual machine (Player-File-Open, then browse the file explorer to where you unpacked the files from 2.a., then select the .vmx file).    4. When the virtual machine is running, open the file with the name of the robot that you want to simulate. Then, turn the virtual robot on using the button on the bottom left. Then click ON and START.   5. Open Experior 6.0. Make sure the UniversalRobots catalog is selected in the catalog selector. Drag and drop the desired robot from the Catalogs panel to the model.   6. Go to URSim and open the robot settings.   In the settings menu, select System-Network. Note the URSim IP address.   7. Connect URSim to Experior. Do this by going to your Experior model, selecting the robot, and writing the URSim IP address in the IP Address field, under Robot connection. 7.1 Afterward, right-click on the robot and select Connect to robot controller. After this, the robot in Experior will snap into the position of the robot in URSim.       After this, the robot in Experior will replicate the trajectory of the robot in URSim.   Connecting robot I/O through Modbus TCP The following steps show how to connect the robot I/O through the URSim Modbus server and the Experior Modbus client.   1. In URSim, go to Installation- Fieldbus- Modbus- Add a new signal. (Initially, the variable list will be empty) In the dropdown menu, select the variable type: Digital Input/Output, Register (byte) Input/Output. Rename the variable (this is the name that will be used in the UR programming interface)   2. Assign the memory address for the variable. For this, you need to take into account that all the addresses have specific uses (see here).   3. In Experior, add the Modbus client by right-clicking the Communication panel, and selecting Modbus.     4. Select the Modbus client, and in the Properties panel, write the URSim IP address in the IP Address field, under Communication.     5. Assign Input/Output variables to the desired components. To do this, first set the Connection id to the id corresponding to the Modbus client. Then, assign the memory address of the Modbus server (assigned in step 2) in the Address field for the specific Input/Output. Modify the Register value, depending on the variable type defined in step 2. For Register Inputs/Outputs, Modify the Size value to UInt16 (WORD).   6. After all the memory addresses have been set in Experior, right-click on the Modbus client and click connect. While the connection is active, you won´t be able to modify the associated I/O in Experior.     After this, the variable values will be represented in the Experior model.   (This example was made with the Display assembly, found in the Advanced catalog)   

Downloading ABB RobotStudio   Go to http://new.abb.com/products/robotics/robotstudio/downloads Click Download Robot Studio x.xx.xx. Wait for the file to download.   Installing RobotStudio Right click on the desktop, select New and click Folder. Rename it to Robot_temp. Open the folder by double clicking it. Locate downloaded zip file and double click to open. Select all files and folders in the zip and drag across to the open Robot_temp folder. When the files have finished copying double click the file named Launch. If you get the User Account Control pop-up click YES. Select English (USA) from the drop down list and click OK. Click the Install Products button. Click the Robot Studio button. When the Welcome window opens click NEXT. Select I accept the terms in the license agreement. Click NEXT. Click ACCEPT. Leave destination folder as presented and click NEXT. Select Complete and click NEXT. Click INSTALL. When the install is complete click FINISH.   Installing RobotWare On the Install Products window which should still be open from previously, click the Robot Ware button. When the Welcome window opens click NEXT. Select I accept the terms in the license agreement. Click NEXT. Click ACCEPT. Leave destination folder as presented and click NEXT. Select Complete and click NEXT. Click INSTALL. When the install is complete click FINISH. Click Exit and Exit again to close the installer. Delete the Robot_temp directory.

With a developer license for Experior 6 it is possible to create custom components, catalog, controllers, plugins and more in your Experior model. We have three different templates you can download and use, as long as you have Experior 6 installed.   You can download the templates attached in this article.   Setting up templates for use in visual studio To set up the templates you first need to copy the template in the C# visual studio template folder. The standard path for this is: C:\Users\ your username \Documents\Visual Studio 20XX\Templates\ProjectTemplates\Visual C# Sometimes you can experience problems with Visual Studios cache, that will fail to refresh the templates and display them in the browser, it is necessary to open the Visual Studio command prompt, which is located in following folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Visual Studio 20XX\Visual Studio Tools Run the ‘Developer Command  Prompt for VS 20XX’ as administrator and write: devenv /installvstemplates   Please note Due to changes in the Experior API will the plugins not compile without a reference to Experior.Common.dll. Setting this reference is done by right clicking ‘References’ in the Visual Studio solution explorer, pressing ‘add reference’ and choosing Experior.Common.dll from the list. If the  dll is not found on the list, press browse and choose the dll from the Experior install directory.  

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.INT16 this is signed 16 bits DataSize.UINT16 this is unsigned 16 bits DataSize.DWORD this is unsigned 32 bits DataSize.DINT this is signed 32 bits DataSize.INT32 this is signed 32 bits DataSize.UINT32 this is unsigned 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.UINT64 this is unsigned 64 bits DataSize.INT64 this is signed 64 bits   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.   [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 { 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.NoNcChanged += 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 adress " + sender.Byte ); 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.Drawing.Color.Green, Core.Environment.DiagnosticAction.STICKY, 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.Drawing.Color.Green, Core.Environment.DiagnosticAction.TEMPORARY, Core.Environment.Signs.Check); // send a message to info.outputdata OutputData.Send("Hello World!"); } void inputbit_NoNcChanged(Register sender) { Experior.Core.Environment.Diagnostic.Message("Input " + sender.ToString() + " changing NO/NC value to " + sender.NC, System.Drawing.Color.Green, Core.Environment.DiagnosticAction.ALARM, Core.Environment.Signs.None); Experior.Core.Environment.Diagnostic.Message("Input was defined for byte " + sender.Byte + " and bit " + sender.Bit); } 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.NoNcChanged -= new Register.NoNcChangedEvent(inputbit_NoNcChanged); } if (((ExampleInputOutputInfo)info).inputdata != null) { ((ExampleInputOutputInfo)info).inputdata.Received -= 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 System.Drawing.Image Image { get { return Common.Icons.Get("Cube"); } } }

Disable screensaver In Experior version 5.2.11165 or later this is no longer required Causes problems when Graphic device becomes unavailable for Experior   Power Settings Disable all power saving modes. Set Power Options to maximum performance Note that domain rules affect this While using Experior dongles, any power loss on usb will result in Experior closing   Labels (2D Graphic) Adding a large amount of “external” graphic, using labels, enabling of assembly text or similar can dramatically decrease performance. As movable objects, each one are rendered separately. Using lots of this on a large model on pc with limited capability equals low performance   Increase Performance Improve performance by disabling shadows, lowering antialiasing or setting detail level to “Normal” or “Primitives”. Settings can be found in the Pane “View” under section “Visibility”. Close windows you do not need. Especially closing the Solution Explorer in model with thousands of assemblies can help quite a bit. Window layout can be reset or single window added, if later needed

‘Getter’ vs. ‘Auto-Property Initializer’   A normal ‘getter’, like; /// <summary> /// Gets the image. /// </summary> /// <value>The image.</value> public override Image Image { get { return Common.Icons.Get("StraightElevator"); } }   or the newer ‘Expression Bodied Property’ style public override Image Image => Common.Icons.Get("StraightElevator");   will call Common.Icons.Get("StraightElevator") and return the image reference every time it is called.   But did we really intend this ? In above example we know from our domain knowledge that the image resource should probably have been a const or readonly reference since the image is loaded from disk and never changed during runtime.   So why; Push a string argument to stack Make ‘Icons.Get() fetch the image resource from it’s storage Push the image reference to the stack over and over – just to get the same result again and again ?   A better solution would be to fetch the image once and store it in a readonly field.   But instead of doing the whole cermony of; declaring a readonly field, initializing it in the contructor and create a getter – you can simpy use the ‘Auto-Property Initializer’ (C#6.0 syntax feature), like so; /// <summary> /// Gets the image. /// </summary> /// <value>The image.</value> public override Image Image { get; } = Common.Icons.Get("StraightElevator");   This creates a readonly field, initializes it once and gives you a public property all in one line of code. And used in the right scenarios it helps performance, while at the same time minimizes SLOC count – a win-win ?.

The Working Area is where the construction of the model takes place and items dragged from catalogues are placed and worked with. It is also referred to as the Floor or the Scene.     On the 3D scene you can alter floor size and texture. The default floor size is 30x30m, while the default floor texture is cement.   If you select the floor texture “None“, the graph sheet will be invisible in both locked and unlocked mode. Selected floor texture will only be visible when the 3D scene is locked (ctrl+L).   Alterations to the floor texture and floor size will only apply to the current project – not as new Experior settings.

The Catalogs window contains the developed assemblies that you can use to to build a layout/model    

The Communications window is located in the same area as the Catalogs pane but on a different tab.   PLC controls and Communications protocols can be added – for instance to connect to Siemens S7 series or Beckhoff PLCs.  

The Control Panel is only available in Physics mode.   Buttons and switches, used to control elements within the working area, can be added.   To add a control, right click and select the desired item from the pop-out menu.   The alignment of the Control Panels can now be set to Top, Right or Left. Right click on the tabs and go down to Alignment. In the pop out menu Top, Right or Left can be selected.     Depending on the alignment of the tabs they can either be moved left to right or up and down.   To do this, right click on the Control Panel tab and select the option as shown below.   The Control Panels can be copied by right clicking on the appropriate tab and selecting the Copy command.   

Located at the bottom of the screen, two panes display the PLC symbols and information that have been assigned to the various items and controls within the model.   Clicking on a line in either panel will display the properties for that symbol.