LASC 1.5. User Guide. Jeremy Thompson, Mark Dunn, Peter Reid and Michael Vowles Commercial-in-confidence

Transcription

1 ENERGY FLAGSHIP LASC 1.5 User Guide Jeremy Thompson, Mark Dunn, Peter Reid and Michael Vowles Commercial-in-confidence

2 Copyright and disclaimer 2016 CSIRO To the extent permitted by law, all rights are reserved and no part of this publication covered by copyright may be reproduced or copied in any form or by any means except with the written permission of CSIRO. Important disclaimer CSIRO advises that the information contained in this publication comprises general statements based on scientific research. The reader is advised and needs to be aware that such information may be incomplete or unable to be used in any specific situation. No reliance or actions must therefore be made on that information without seeking prior expert professional, scientific and technical advice. To the extent permitted by law, CSIRO (including its employees and consultants) excludes all liability to any person for any consequences, including but not limited to all losses, damages, costs, expenses and any other compensation, arising directly or indirectly from using this publication (in part or in whole) and any information or material contained in it.

3 Document Version Date Author Description 01/01/2014 Jeremy Thompson Initial non release draft. 21/10/2014 Jeremy Thompson Initial release version. 03/03/2015 Jeremy Thompson Added information about MySQL driver errors. Some minor text updates. 14/04/2015 Jeremy Thompson, Michael Vowles Updated document format. 02/10/2015 Jeremy Thompson Release of updated document. 09/11/2015 Jeremy Thompson, Michael Vowles Added troubleshooting section. Some minor formatting and text updates. 09/03/2016 Michael Vowles Gate exit points removed, panel width now set for both the RSS and SHC. 09/02/2017 Michael Vowles Removed entry for setting up ODBC connector as File DSNs are used as of /03/2017 Jeremy Thompson Added Shearer Speed Multiplier parameter. LASC 1.5 i

4 Contents 1 Introduction System Overview Hardware Components Software Components Installation Database Security Key Software Database Configuration Service Installation Configuration Embedded Software and Device Configuration Application and Service Configuration Database Config Device Config Operator Control Display Operation Mode Face Alignment Face Alignment History Horizon Control Horizon Control History Service Control Controls Console Mode External API General URL format Events and Status Troubleshooting General Troubleshooting Specific Troubleshooting LASC Fault Table ii User Guide

5 Tables Table 1 LASC Hardware Components... 7 Table 2 LASC Software Components... 8 Table 3 XML Parameters Table 4 Panel Configuration Parameters Table 5 Application Configuration Parameters Table 6 MUPS Parameters Table 7 IIB Parameters Table 8 CPU Parameters Table 9 Service Control Commands Table 10 URL Segments Table 11 Data Format Strings Table 12 External API Data sets Table 13 Status table fields Table 14 Events Table Fields Table 15 LASC fault table LASC 1.5 iii

6 Figures Figure 1 ODBC Data Source Administrator Figure 2 MariaDB DSN driver Figure 3 MariaDB DSN name Figure 4 MariaDB DSN server details Figure 5 MariaDB DSN automatic reconnect Figure 6 MariaDB DSN allow multiple statements Figure 7 MariaDB DSN Cursor/Results Figure 8 MySQL DSN driver Figure 9 MySQL DSN configuration and options Figure 10 LASC System Installer Figure 11 Start Menu Figure 12 Installation Folder Figure 13 Database configuration prompt Figure 14 System Configuration Figure 15 Database Config Figure 16 Panel List Figure 17 Panel Configuration Figure 18 Panel Coordinates Figure 19 Panel Coordinates Gate End Figure 20 Gate Real Levels Figure 21 Gate Real Level Import Dialog Figure 22 Application Configuration Figure 23 Maintenance Tab Figure 24 Export Dialog Figure 25 Import Dialog Figure 26 Upgrade Dialog Figure 27 Repair Dialog Figure 28 Device Config Figure 29 MUPS Dialog Figure 30 IIB Dialog Figure 31 CPU Dialog Figure 32 Bootloader Dialog Figure 33 OCD iv User Guide

7 Figure 34 Profile Axes Adjustment Figure 35 OCD Lead and Lag Figure 36 Face Alignment Armed Figure 37 Face Alignment History Figure 38 Face Alignment History legend and scale Figure 39 Horizon Control Figure 40 Horizon Control History Figure 41 Service Control Figure 42 Console Mode Figure 43 Status Figure 44 Events Figure 45 Manual Console Service Command Figure 46 Profile fault diagnose LASC 1.5 v

8 1 Introduction This document is the user guide for the LASC 1.5 system. It provides a description of the LASC system and describes how to install, configure, maintain and trouble shoot the system. 6 User Guide

9 2 System Overview The LASC system consists of both hardware and software components. This section describes these components and their relationships. 2.1 Hardware Components Table 1 LASC Hardware Components shows the LASC hardware items. Note that some hardware components also have a related software component. For example the IIB is a physical device however it also runs firmware therefore it there is also an IIB software component. Item INS CPU MUPS IIB Encoder Security Key SPMS CPU rack SPMS MUPS rack Description The INS is the primary sensor for the LASC system. It produces the raw positioning information that is then processed by the LASC system to produce the control information. The CPU is an embedded computer the runs the SPMS software. The CPU is physically located inside the SPMS CPU rack. The MUPS is a managed UPS and allows the system to handle the loss of power without degrading system performance. The MUPS is physically located in the SPMS MUPS rack. The IIB device is responsible for interfacing with the OEM supplied odometry encoder. The IIB enables the LASC system to use VMS aiding which increases the accuracy of the system. The IIB is physically located in the SPMS - CPU rack. The OEM supplied encoder for VMS aiding. LASC 1.5 uses a hardware based licence protection system. This protection is comprised in part by a USB security key that must be present on the LASC server for the LASC system to run. The SPMS CPU rack is the physical housing for the CPU and IIB devices. The SPMS MUPS rack is the physical housing for the MUPS device. Table 1 LASC Hardware Components 2.2 Software Components Table 2 LASC Software Components shows the LASC software components. Component Type Location Description SPMS Embedded CPU The SPMS is responsible for controlling the INS and communicating the raw data to the surface for processing. MUPS Embedded MUPS The embedded software that runs on the physical MUPS unit. IIB Embedded IIB The embedded software that runs on the physical IIB unit. LASC 1.5 7

10 Database Service Server The Database acts as a central data repository for the LASC system SPMS Client Service Server The SPMS Client communicates with the SPMS device underground to retrieve the raw positioning information. NDP Service Server The NDP takes the raw position information and processes it to provide face and horizon information. This information is then used to feed back to the control systems to steer the equipment. OEM Interface Service Server The OEM Interface interacts with the OEM control systems to provide it with face and horizon control information. Monitoring Service Service Server The Monitoring Service is responsible for monitoring the LASC system and reporting its state. It also provides remote access to the status information via HTTP. OCD Application Maingate PC / Any PC The Operator Control Display (OCD) is the primary control interface for production operations for the LASC system. It displays the current and historical face and horizon information, allows the user to input correction data, and arm and disarm the LASC system. Database Config Application Any PC The Database Config tool is the primary application used to setup and configure the LASC system. The major functionality provided by this application is: create and setup panels, set device configuration, set application configuration and perform maintenance on the Database. Device Config Application Any PC The Device Config tool allows the LASC hardware devices to be configured. This configuration includes the network settings and all device parameters. Service Control Application Server The Service Control application allows the user to monitor the state of the LASC services. It also can be used to start, stop, install and uninstall the services. Table 2 LASC Software Components 8 User Guide

11 3 Installation The following sections describe the process for installing the LASC system. They should be followed in order as each step is dependent on earlier prerequisite steps being successfully completed. 3.1 Database A compatible database server is required to be installed prior to installing LASC. LASC currently supports MySQL 1 and MariaDB 2 database servers. During the installation of the database server it is important to configure the following options correctly: Root password o User Name: root o Password: Lasc101 System Path o The server should be added to the system path so that the LASC can access the utility programs. Server Port o If the server port is changed from the default (3306) this will need to be updated in each of the applications file dsn s installed under C:\Program Files\LASC\1.5\ ODBC DRIVER LASC uses ODBC to connect to the database server. MySQL provides the Connector/ODBC driver and MariaDB provides the MariaDB ODBC Driver. These drivers can be sourced from the appropriate download pages. Ensure that the 32 bit ODBC driver is installed. The 64bit driver will not work with the 32bit server. If the MySQL ODBC driver installer reports error the Microsoft Visual C Redistributable Package (x86) may need to be installed on the system. If this does not fix the error then the SP1 variant may be needed ODBC DSN As of LASC software version , an ODBC DSN is no longer required. The following has been left for any systems using previous versions of the software. 1 32bit Version bit Version Extended error codes are ODBC error 13 and System error code 193. Exact error codes may vary. LASC 1.5 9

12 Once the driver is installed a Data Source Name must be configured to provide access to the server. This is done via the Windows ODBC Data Source Administrator tool. It is important to use the 32 bit version of ODBC Data Source Administrator tool odbcad32.exe. 64 bit windows path is C:\Windows\SysWOW64\odbcad32.exe 32 bit windows path is C:\Windows\system32\odbcad32.exe On 64 bit windows the start menu Data Sources (ODBC) or Control Panel -> Administrative Tools -> Set up data sources (ODBC) link to the incorrect versions. The tools should be directly started by browsing to them. Using the incorrect version will mean that any drivers that you have installed will not be displayed. Figure 1 ODBC Data Source Administrator It is recommended that a System DSN is created as they are accessible by all users unlike a User DSN. MariaDB DSN The following images show the steps to configure an ODBC DSN using the MariaDB ODBC driver (version 1.0). 10 User Guide

13 Figure 2 MariaDB DSN driver Figure 3 MariaDB DSN name LASC

14 Figure 4 MariaDB DSN server details Figure 5 MariaDB DSN automatic reconnect 12 User Guide

15 Figure 6 MariaDB DSN allow multiple statements MySQL DSN Figure 7 MariaDB DSN Cursor/Results The following images show the steps to configure an ODBC DSN using the MySQL ODBC driver (version 5.3.0). LASC

16 Figure 8 MySQL DSN driver Figure 9 MySQL DSN configuration and options Extra options are displayed using the Details button. 14 User Guide

17 3.2 Security Key LASC 1.5 uses a hardware based licence protection system. This protection is comprised in part by a USB key that must be present on the LASC server for the services to run. The USB key is locked to the vicinity of the mine and may not be used with LASC at any other mine site without the USB key being updated. The key should be inserted into a USB port on the LASC server. Once the key has been inserted the operating system will automatically install the required drivers via Windows Update. If windows update is unavailable then drivers can be manually installed using HASPUserSetup.exe which is available on the LASC update web site. Installation of drivers, particularly from Windows Update can take an extended period of time. The key must be present during operation of the LASC system. If the key is removed then the LASC system will stop functioning. 3.3 Software The LASC software is provided as both a full system installer and individual component installers. There is no x64 version of the LASC system. Previous versions of LASC included a x64 installer due to the usage of some x64 third party components. As these components are no longer used there is no requirement for an x64 version. Running the system installer LASC_1_5_x_x.exe will install the following components: SPMS Client NDP OEM Interface Database Config Device Config Monitoring Service Service Control Figure 10 LASC System Installer The default installation location is C:\Program Files\LASC\1.5 or C:\Program Files (x86)\lasc\1.5 on 64 bit machines. Desktop shortcuts and start menu items are also created as per Figure 11 Start Menu. LASC

18 Figure 11 Start Menu The shortcut items provide access to the LASC applications and a shortcut to the LASC install folder. The folder layout of the install folder is show in Figure 12 Installation Folder. Figure 12 Installation Folder During the installation a number of command prompts will appear whilst the services are installed. These can be ignored as they do not require user interaction. 3.4 Database Configuration During the installation of the LASC tools the installer will prompt for the Database root password so that the default LASC user can be configured as per Figure 13 Database configuration prompt. The default LASC user is: Figure 13 Database configuration prompt User name: lasc Password: Lasc User Guide

19 3.5 Service Installation By default the LASC installers will install the following components as Windows services: SPMS Client NDP OEM Interface Monitoring Service The services can also be installed via the Service Control tool. Please refer to section Service Control for more information on using this tool. NOTE: The Hardware Security key must be installed for the services to install correctly. LASC

20 4 Configuration Configuration has been streamlined in LASC 1.5. Previously configuration information was stored in a number of different locations leading to problems with parameters becoming unsynchronised when they were only updated in one location. Under LASC 1.5 the primary location for configuration information is the Database. When a software component starts it retrieves it s parameters from the Database. Device and embedded software configuration is also maintained in the Database and it can optionally be automatically configured by the Monitoring Service. Figure 14 shows the configuration architecture used in LASC 1.5. Figure 14 System Configuration 4.1 Embedded Software and Device Configuration Devices maintain their own configuration locally as they do not directly communicate with the Database. Device configuration can be performed in two ways, directly or indirectly. Direct configuration is used when: The device has not been installed into the production network, i.e. during bench configuration. The device does not have access to the LASC server. The LASC server is yet to be configured. The device s network parameters need to be changed. Indirect configuration is performed when the device has previously been installed into the production network and can communicate with the LASC server i.e. reconfiguration of an existing system. 18 User Guide

21 4.1.1 DIRECT CONFIGURATION Direct configuration is performed by the Device Config tool. See the Device Config section for more details on using this tool. Direct configuration must be used when changing the network configuration of the device. Ensure that you disable indirect configuration if you intend on changing a device s parameters via direct configuration. If you do not then the updated parameters will overwritten INDIRECT CONFIGURATION Indirect configuration is performed by the Monitoring Service and the Database Config tool. The Database Config tool can be used to enter the device configuration (excluding network configuration) on the Application tab and if the Auto configure option is checked then the device will be checked by the Monitoring Service and updated if the configuration does not match the details specified. See the Database Config section for more details on using the Database Config tool. 4.2 Application and Service Configuration As with previous versions of LASC, each application and service still maintains a configuration file (configuration.xml) in the install location. Unlike the previous version of LASC these files do not typically contain the full configuration for the application or service. The following is an example configuration file: <configuration user="/" source="remote"> <database dsn="lasc" /> <logging level="debug" console="true" colour="true" debugger="false" file="true" filename="" rolling="true" count="15" limit="true" size=" "/> </configuration> The full configuration is stored in the database and is set and updated using the Database Config tool. This change was made to avoid duplication of the same parameters across different configuration files and allows common parameters to be updated in a single location. Table 3 lists the elements common to all configuration files. Tag Attribute Description configuration user The user that the application will run as. Currently only two users have been defined; the default user / and a control user /control. The control user is intended to be used by the OCD to identify the underground control instance. source Defines where the application will get its configuration. The default is remote which indicates that the application will use the database for its configuration. Specifying local indicates that the XML file contains the complete configuration information. database dsn Defines the Data Source Name to be used. Logging level The minimum logging level to output. Messages output with a lower level then this will be ignored. Valid options are: debug, warning, critical and fatal. Note fatal messages will also abort the application as they represent unrecoverable errors. console colour When true messages will be output to the console. When true console output will be coloured based on the message LASC

22 level. debugger file filename rolling count limit size minidump When true messages will be output to the debugging console. When true messages will be output to file. Specifies the base log file to log too. The file name can contain a path (relative or absolute). If no filename is specified a default log file is created using the applications name. The default log directory is C:\ProgramData\LASC\log. When true log files will be rolled i.e. when the application is started the old file appname.log will be rename to appname.log.0. If that file already exists it will be rename appname.log.1 etc. The maximum number of log files to keep. After the maximum number is reached the oldest file is deleted. When true log file will be limited to maximum file size. If both limit and rolling logs are enabled then the log files wills will rolled otherwise it is simply truncated removing the oldest records in the file. The maximum file size in bytes. When true a minidump will be created when an unhandled exception is encountered. This option should only be enabled when debugging. Table 3 XML Parameters LOCAL CONFIGURATION As well as the common parameters, a configuration file can optionally specify part or all of its parameters. This is done by setting the source attribute of the configuration tag to local. If a parameter is not specified in the local configuration then the remote database value is used. 4.3 Database Config The Database Config tool is the primary application used to setup and configure the LASC system. The major functionality provided by this application is: Create and setup panels. Set device configuration. Set application configuration. Perform maintenance on the Database. Figure 15 Database Config shows the Database Config tool. 20 User Guide

23 Figure 15 Database Config SERVER CONNECTION To connect to the Database server select the DSN and click the connect button. For more information regarding DSNs see the ODBC DSN section PANELS LIST After connecting the panels will be displayed in the Panels list as shown in Figure 16. LASC

24 Figure 16 Panel List The panels list will contain all the schemas on the database server that contain LASC panels. Panels that have unsaved changed are highlighted in red and have a star appended to the panel name. Selecting a panel in the list will display the panel s information and allow actions to be performed on that panel. The following operations are available on the Panel list: Refresh reloads all the panels from the server. New creates a new default panel. Clone copies the currently selected panel into a new panel. Import imports a panel from file. Delete deletes the selected panel from the server. Save commits any changes made to the panel back to the database server. Set Active sets the currently selected panel as active. Only one panel can be active at any one time. The Active panel is used by any application that does not explicitly define a schema in its configuration file PANEL CONFIGURATION The Panel Configuration tab summaries all the panel parameters and is shown in Figure User Guide

25 Figure 17 Panel Configuration Table 4 Panel Configuration Parameters describes the panel configuration parameters that are displayed on the tab. Parameter Description Unit General Database Schema The schema name that contains this panel. LASC panel schemas are always prefixed by lasc_panel and are set when the panel is created. Name The name of the panel. String Cutting Mode Nominal Advance Distance Number of Supports Discontinuity Threshold The cutting mode of the panel. Where UNIDIMG indicates that the straight cut is towards the maingate. The advance size of each push. The number of supports on the face. The maximum amount of missing data before a profile will be Non editable string UNIDIMG or UNITG or BIDI Metres Number Metres LASC

26 Horizon Points Per Metre marked as discontinuous. The number of horizon points to generate per metre of travel. Geometry SHC Width The distance the shearer traverses across the coal face. This width should match the distance reported by the SHC. RSS Width The width of the face. This width should match the distance reported by the RSS. Number Metres Metres Length The length of the panel. Metres Heading The panel heading. Degrees Easting Reference Northing Reference The easting value of the panel origin. The northing value of the panel origin. Metres Metres Zone The UTM zone. UTM zone Altitude Reference The altitude of the panel origin. Metres Shearer Left Arm Length The length of the left shearer arm. Right Arm Length Odometer Offset The length of the right shearer arm. The distance from the panel origin to the centre of the shearer when the shearer is reporting zero odometry. Gates Maingate Orientation Which side the Maingate is when standing on the face looking in the direction of retreat. Maingate Entry Tailgate Entry The entry odometry for the Maingate zone. The entry odometry for the Tailgate zone. Metres Metres Metres LEFT or RIGHT Metres Metres Table 4 Panel Configuration Parameters Unidi Cutting Mode definitions are not the same as the LASC 1.0 definitions. Please ensure the correct cutting mode is specified otherwise the wrong profile will be displayed on the OCD and used for corrections PANEL COORDINATES The following diagrams, Figure 18 Panel Coordinates and Figure 19, illustrate the panel coordinate system used by the LASC system. 24 User Guide

27 Figure 18 Panel Coordinates LASC

28 Figure 19 Panel Coordinates Gate End Setting the correct panel coordinates and geometry is vital to the correct operation of the LASC system. An invalid configuration can result in the following symptoms: No profiles. Invalid profiles. Flat profiles. Extremely deviated profiles. Inconsistent profiles. Common errors that have been observed when setting up are: Incorrect panel heading Incorrect boresight Incorrect UTM zone UTM COORDINATE SYSTEM The LASC system uses the UTM coordinate system to specify the panel coordinates. These coordinates consist of an easting value, northing value and a zone specification. The zone specification consists of a longitudinal zone number and latitudinal zone letter. For example coordinates of CSIRO QCAT are east, north zone 56J. Alternatively the latitudinal zone letter Z can be used to denote that the LASC system should use the sign of the longitudinal zone number to indicate the correct hemisphere. Using this representation the previous zone coordinates of QCAT could be written as -56Z where the negative longitudinal zone number indicates the southern hemisphere. Setting the incorrect zone hemisphere will stop the INS from aligning correctly. 26 User Guide

29 The northing can sometimes be referred to as southing in some applications. For example when viewed with Google Earth the QCAT coordinates would be displayed as 56 J m E m S GATE REAL LEVELS TAB The Gate Real Levels are required for both the main gate and tail gate roadways. The real level values can be entered on the Gate Real Levels tab as shown in Figure 20. Gate Real Levels Data Figure 20 Gate Real Levels A Gate Real Level data point consists of three values: a distance along the gate road, absolute roof high in metres and absolute floor high in metres. It is important to note that the values should encompass the full extent of the panel length i.e. from the panel origin and past the expected length of the panel. Manual Entry Values can be entered manually by entering values in the last row of the table marked Add Row. Note that when values are entered via this row they will be inserted into the table according to the distance value. Import Data Data can be imported by right clicking on the table and selecting the Import option. This will open the Import Dialog shown in Figure 21. LASC

30 Figure 21 Gate Real Level Import Dialog Data can be either loaded from file or the clipboard and formatting options such as delimiting and header rows can be specified. Clicking the Import button will parse the source and display the results in the table APPLICATION CONFIGURATION The Application Configuration tab is shown in Figure 22 and allows the configuration to be set for the applications, services and devices. Configuration options are described in Table 5. Figure 22 Application Configuration 28 User Guide

31 Parameter Description Unit OCD Control Instance IP Restrict control instances Panels FA Control Mode HC Control Mode FA Scale FA line width FA marker size HC primary scale HC secondary scale This parameter specifies which system that the control instance will be restricted to. If a control OCD is started on another system it will be restricted to view only mode. Specifies if the control instance will be restricted or not. If not set then control instances of the OCD will be allowed to start on any system. The list of panels that will be displayed on the OCD. Available panels are FAPanel, HCPanel, FAHPanel and HCHPanel. Defines the type of control mode used on the FA panel when the OCD is started in control mode. CONTROL Standard control. AUTO Issue corrections is automatically rearmed. Auto mode can be toggled by user. LOCKED_AUTO Issue corrections is automatically rearmed. Auto mode cannot be toggled by user. HEADLESS The NDP will re-arm the RPCs after a new profile meaning that the OCD is not required to be open in order for corrections to be issued. Defines the type of control mode used on the HC panel when the OCD is started in control mode. CONTROL Standard control. AUTO Issue corrections is automatically rearmed. Auto mode can be toggled by user. LOCKED_AUTO Issue corrections is automatically rearmed. Auto mode cannot be toggled by user. The scale that will be used on the Face Alignment tab. The line weight used to draw the profiles on the Face Alignment tab. The control marker size used on the Face Alignment tab. The primary axis vertical scale on the Horizon Control tab. The secondary axis vertical scale on the Horizon Control tab. IPv4 address i.e true or false String i.e. FAPanel HCPanel FAHPanel HCHPanel CONTROL or AUTO or LOCKED_AUTO or HEADLESS CONTROL or AUTO or LOCKED_AUTO mm points pixels mm mm LASC

32 Parameter Description Unit HC line width Shearer Speed Multiplier The line weight used to draw the profiles on the Horizon Control tab. The multiplier required to convert the OEM supplied shearer speed value to metres per minute. For example if the value reported is in 0.01 metres per second (default) then the multiplier would be 0.6. SPMS Client Status Reports the status of the SPMS Client service. This parameter is non editable. OEM Interface Status Reports the status of the OEM Interface service. This parameter is non editable. RPC Advance Target Limit Maximum RPC Delta Face Alignment Enabled RSS IP Address RSS Port RSS Packet Timeout Horizon Control Enabled SHC IP Address SHC Port SHC Packet Timeout Scaling factor applied to the outgoing RPCs. Limits the maximum value of the RPC to a percentage of the nominal advance distance. If the calculated RPCs are greater than this value the whole RPC vector is scaled by the target amount. Limits the maximum change allowable between two adjacent supports. When enabled face alignment correction information is sent to the OEM System. The IP address of the roof support control system. The port number to connect to the roof support control system on. The packet timeout for the RSS. Requests that do not receive a response within this period will be deemed to have timed out. When enabled horizon correction information is sent to the OEM System. The IP address of the shearer horizon controller system. The port number to connect to the shearer horizon controller system on. The packet timeout for the SHC. Requests that do not receive a response within this period will be deemed to have timed out. NDP Status Reports the status of the NDP service. This parameter is non editable. Fully Aligned Only When enabled only fully aligned INS records will be used. Points Number NA NA Percentage mm true or false IPv4 address Integer Integer true or false IPv4 address Integer Integer NA true or false Horizon Algorithm The horizon control algorithm to be used. Standard or Flightpath Cache Size The horizon forward projection cache size. Integer 30 User Guide

33 Parameter Description Unit Monitoring Service Status External API Enabled External API Port Push Status Information Remote Status Server Address Remote Status Server Port Reports the status of the Monitoring service. This parameter is non editable. When enabled LASC data can be accessed via the External API. The port number to accept external api requests on. When enabled summary status information will be sent to the remote monitoring server. The address of the remote monitoring server. The port number of the remote monitoring server. Push Update Rate The rate at which to push status information. ms Push Site Identifier A unique site identification string. CPU Auto Configure If enabled the Monitoring service will check the CPU configuration and automatically configure it if it is incorrect. NA true or false Integer true or false IPv4 address Integer string true or false IP The IP address of the CPU. IPv4 address INS Type Odometry Source Using VMS LN270 Logging The type of the INS being used. 0 = LN270 1 = Landins The source used for odometry. 1 = reserved 2 = IIB 3 = EIP When enabled the CPU will use VMS aiding to improve its performance. Determines if the CPU will generate an onboard log of LN270 data. number number true or false number LASC

34 Parameter Description Unit Boresight Roll, Pitch and Yaw Determines the angles used to correct for the INS mounting inside the shearer. The Boresight is calculated by rolling, pitching then yawing the LN270 from the mounted position to the reference positon. The reference position of the LN270 is base down with the cables pointed towards the tail gate. Note the axes of the LN270 is described in the following diagram noting roll about the x axis, pitch about the y axis and yaw about z the axis. degree VMS Roll, Pitch and Yaw Defines the orientation of the VMS source relative to the INS. IIB Auto Configure If enabled the Monitoring service will check the IIB configuration and automatically configure it if it is incorrect. degree true or false IP The IP address of the IIB. IPv4 address Encoder Pulse Distance Encoder Direction Sense The distance in micrometres of each pulse generated by the OEM encoder. The direction sense of the encoder pulses. MUPS Auto Configure If enabled the Monitoring service will check the MUPS configuration and automatically configure it if it is incorrect. micrometres positive or negative IP The IP address of the MUPS. IPv4 address Initial Delay The initial power up delay period. seconds Sequential Delay SPMS Heartbeat SPMS Cycle Monitor SPMS The delay between each device supply line being energised. The maximum acceptable period between each SPMS heartbeat packet. The period that the SPMS will be cycled if the heartbeat period is exceeded. When enabled the SPMS is monitored and will be power cycled if the heartbeat period is exceeded. seconds seconds seconds true or false 32 User Guide

35 Table 5 Application Configuration Parameters MAINTENANCE TAB The maintenance tab as shown in Figure 23 provides access to a number of useful maintenance tasks. The table shows the state of the LASC database including the schema version and table data sizes. Rebuild Figure 23 Maintenance Tab The Rebuild task forces the LASC system to rebuild the panel. The LASC system will discard all computed data and rebuild it from raw data. Reinitialise The Reinitialise button will reset and reinitialise the panel to the default values. This will discard all data and settings. Export Export allows the panel to be exported to a file via the Export Dialog shown in Figure 24. This is useful for archiving or backing up panels. The panel will be exported to a SQL file and for large panels the export can take an extended period of time and result in a large file. It is recommended that the resulting file compressed. LASC

36 Import Figure 24 Export Dialog Import allows a previously exported panel to be imported into the current panel schema. All data in the current schema will be overwritten. Importing large panels can take an extended time. Upgrade Figure 25 Import Dialog The Upgrade task allows the LASC database schema to be upgraded to a new version. The Upgrade Dialog shows the current schema version and allows the target schema version to be specified. Upgrading to a version will also apply any intermediate updates. Repair Figure 26 Upgrade Dialog In the event of the LASC database tables becoming damaged the repair task allows the user to check the state of the tables and repair them if necessary. The tool will check the state of all tables and report if repairs where performed. 34 User Guide

37 Figure 27 Repair Dialog Repair is unavailable when using the MariaDB ODBC driver due to a known issue with the driver. 4.4 Device Config The Device Config tool as shown in Figure 28 allows the LASC hardware devices to be configured. This configuration includes the network settings and all device parameters. If the Automatic Configuration is enabled via Database Config then the devices will be automatically reconfigured by the Monitoring Service if the configuration is not correct. LASC

38 Figure 28 Device Config LOCATING DEVICES After selecting the appropriate network interface devices can be located using one of the following methods Broadcast - Devices are located using a UDP broadcast on the specified network. Manual Scan An IP range and mask can be specified to find the devices. Direct If the IP address is known, this can be entered directly to connect to the device. If a device responds to the network broadcast it will be displayed as an unknown device. Double clicking on a device in the list or pressing the Identify button will attempt to identify the type of the device. This process may take an extended period of time, particularly if the device is using old firmware. Note that if the tool was required to add a local network address for the target device (i.e. the device was on another subnet) then you will need to retry the identification. If the device is successfully identified its type is displayed in the list and a separate dialog is display allowing the device to be configured NETWORK CONFIGURATION After the device has been identified the network configuration of the device can be set by selecting the device and clicking the Update button. Note that it is not recommended that a Gateway address not be set on the device as this can interfere with the device location process. 36 User Guide

39 4.4.3 MUPS DIALOG If the target device is identified as a MUPS then the MUPS dialog is displayed as shown in Figure 29. Power supplies and relays Figure 29 MUPS Dialog The display at the top of the dialog depicts a connectivity diagram for the MUPS. It shows the OEM power supplies (48V, 24V and 24V DC-DC) and the current voltage present on the supplies. It also shows the state of the MUPS control relays where green indicates closed. Double clicking on a relay will toggle its state of the relay. While the Monitor button is checked the state of the supplies and relays will be constantly updated. Parameters The parameters section of the dialog allows the various board parameters to be modified. See Table 6 for a description of each parameter. Operations available on the Parameters section are: Get reads the parameters from the device. Set writes the parameters to the device. Save saves the parameters to a file so that they can backed up or reloaded. Load loads previously saved parameters from file. The parameters can then be written to the device. LASC

40 Note that it is not recommended that the voltage parameters be modified as they are calibrated when the device is manufactured. Parameter Description Unit OEM 24V Reference Value The OEM 24V power supply reference value. Volts OEM 24V Set Point The OEM 24V power supply set point. Volts OEM 24V Overvoltage Low The OEM 24V power supply over voltage lower bound. Volts OEM 24V Overvoltage High The OEM 24V power supply over voltage upper bound. Volts OEM 48V Reference Value The OEM 48V power supply reference value. Volts OEM 48V Set Point The OEM 48V power supply set point. Volts OEM 48V Overvoltage Low The OEM 48V power supply over voltage lower bound. Volts OEM 48V Overvoltage High The OEM 48V power supply over voltage upper bound. Volts UPS 24V Reference Value The UPS 24V DC-DC power supply reference value. Volts UPS 24V Set Point The UPS 24V DC-DC power supply set point. Volts UPS 24V Overvoltage Low UPS 24V Overvoltage High The UPS 24V DC-DC power supply over voltage lower bound. The UPS 24V DC-DC power supply over voltage upper bound. Volts Volts CAP 48V Reference Value The Capacitor Bank 48V power supply reference value. Volts CAP 48V Set Point The Capacitor Bank 48V power supply set point. Volts CAP 48V Overvoltage Low CAP 48V Overvoltage High The Capacitor Bank 48V power supply over voltage lower bound. The Capacitor Bank 48V power supply over voltage upper bound. Volts Volts Initial Delay The initial power up delay period. Seconds Sequential Delay SPMS Heartbeat SPMS Cycle Monitor SPMS The delay between each device supply line being energised. The maximum acceptable period between each SPMS heartbeat packet. The period that the SPMS will be cycled if the heartbeat period is exceeded. When enabled the SPMS is monitored and will be power cycled if the heartbeat period is exceeded. Seconds Seconds Seconds NA Board Information Table 6 MUPS Parameters The board information section displays the installed firmware version and serial number. It also displays shutdown statistics. Operations available in this section are: 38 User Guide

41 Get reads the firmware version, serial and shutdown counts. Reset Counts resets the stored shutdown counters. Control The control operations available are: Reset MUPS resets the board. Bootloader displays the bootloader dialog which allows new firmware to be uploaded. Monitor when checked the supply voltages and relay states are continuously updated IIB DIALOG If the target device is identified as an IIB then the IIB dialog is displayed as shown in Figure 30. Parameters Figure 30 IIB Dialog The parameters section of the dialog allows the various board parameters to be modified. See Table 7 for a description of each parameter. Operations available on the Parameters section are: Get reads the parameters from the device. Set writes the parameters to the device. Save saves the parameters to a file so that they can backed up or reloaded. LASC

42 Load loads previously saved parameters from file. The parameters can then be written to the device. Note that to set the across face position you check the Position checkbox. This avoids inadvertently setting the position and forcing it to be resynchronised. Parameter Description Unit Encoder Pulse Distance VMS Pulse Distance Debounce Distance The distance in micrometres of each pulse generated by the OEM encoder. The distance between each VMS pulse sent to the INS. The debounce distance to stop spurious VMS pulses being emitted. Note that this parameter is not used in the 1.5 firmware and will be disabled when communicating with 1.5 devices. micrometres micrometres micrometres Position The across face position. metres Direction Sense Encoder Monitor Status Encoder VOdo The direction that each encoder pulse represents. This should be configured such that the position increments when travelling away from the maingate. When enabled the encoder monitoring circuitry of the IIB will be overridden. When disabled the encoder pulses input circuitry will only be enabled when a valid encoder is attached. Indicates that the output supply to the encoder is operating correctly. Positive (checked) or negative Enabled (checked)or disabled NA Status Encoder Monitor Indicates that a valid encoder has been detected. NA Board Information Table 7 IIB Parameters The board information section displays the installed firmware version and serial number. Operations available in this section are: Get reads the firmware version and serial. Control The control operations available are: Reset IIB resets the board. Bootloader displays the bootloader dialog which allows new firmware to be uploaded. Monitor when checked the position and status information is continuously updated CPU DIALOG If the target device is identified as a CPU then the CPU dialog is displayed as shown in Figure 31 CPU Dialog. 40 User Guide

43 Parameters Figure 31 CPU Dialog The parameters section of the dialog allows the various board parameters to be modified. See Table 8 CPU Parameters for a description of each parameter. Operations available on the Parameters section are: Get reads the parameters from the device. Set writes the parameters to the device. Save saves the parameters to a file so that they can backed up or reloaded. Load loads previously saved parameters from file. The parameters can then be written to the device. Parameter Description Unit Default Software Version The software version running on the CPU. text Not editable Data directory The data directory used to store pending records for transfer. text Not editable Display enabled When enabled the console display is shown. flag Not editable CM mode CM operation mode value. number Not editable Ignore MUPS When enabled the MUPS will be ignored. flag Not editable Source The type of INS used in the system where: 0 = LN270 1 = Landins number 0 LASC

44 Parameter Description Unit Default Maingate on left Low speed port High speed port This defines the configuration of the Gate End. Checked means Main Gate on left when standing in the goaf, looking at the face. The communications port used by the SPMS to talk to the LN270. The communications port used by the SPMS to talk to the LN270. Easting UTM of the start point of the panel. m na Northing UTM of the start point of the panel. m na Zone UTM zone i.e. 56 number na Zone Letter Altitude Latitude Longitude Roll Pitch Yaw UTM zone letter. Note entering Z will mean that the CPU will rely on the sign of the Zone number to determine hemisphere. The Altitude in real levels of the start point of the panel. This is the location of the start point of the panel. This is the location of the start point of the panel. Roll value is the angle to rotate by if the LN270 is mounted on it's side. Pitch value is the angle to rotate by if the LN270 is mounted on it's end (i.e. cables pointing up or down). Yaw value is the angle to rotate by if the LN270 is mounted rotated (i.e., cables pointing towards the face, away from the face, or towards main). flag text NA A-Z m number number true Not editable Not editable na na degrees 0 degrees 0 degrees 0 VMS roll Roll angle of the VMS odometry source. degrees 0 VMS pitch Pitch angle of the VMS odometry source. degrees 0 VMS yaw Yaw angle of the VMS odometry source. degrees 0 VMS inhibit Inhibit VMS input into the system. boolean true VMS scale factor The scaling factor for the VMS odometry source. micrometres 500 Not editable Not editable Force non stationary Force the non stationary state. boolean Not editable In travel lock Use in travel lock. boolean Not editable Longwall mining mode Use longwall mining mode. boolean Not editable 42 User Guide

45 Parameter Description Unit Default LN270 logging Odometry source Log LN270 data records: 0 = Disable 1 = Enable 5hz data (regardless odometry) 2 = Log e8. Selects the Odometry source used by the SPMS system: number 0 number 3 1 = Reserved 2 = IIB 3 = EIP Odometry Log delta Odometry logging delta m 0.5 SHC IP address Address of the Shearer Controller. IP address na SHC EIP port The port of the Shearer Controller. number IIB server IP address Address of the IIB. IP address na IIB server port Port of the IIB. number IIB client address IP address of this CPU. IP address na MUPS server IP address Address of the MUPS. IP address na MUPS server port Port of the MUPS. number MUPS client address IP address of this CPU. IP address na Board Information Table 8 CPU Parameters The board information section displays the installed firmware version and serial number. Operations available in this section are: Control Get reads the firmware version and serial. The control operations available are: Reset CPU resets the board. Bootloader displays the bootloader dialog which allows new firmware to be uploaded BOOTLOADER DIALOG Clicking on the Bootloader button on any of the device dialogs will display the Bootloader Dialog as shown in Figure 32. Using this dialog new firmware can be uploaded to the device. The following details and commands are available on the dialog: Device Type The type of device that the bootloader is communicating with. Note this is set automatically however it can be overridden by the user (not recommended). Device Status The device details. Firmware File The path to the firmware file to upload. Browse Allows the user to select the firmware file. LASC

46 Encoding The firmware file encoding type. For IIB and MUPS firmware files the encoding is Intel and for CPU firmware file the encoding is Raw. This will be set automatically and shouldn t be changed. Hash When enabled the dialog will check the firmware s file directory for a MD5 hash file to validate the integrity of the firmware file. Upload Starts the upload process. Cancel Cancel an upload if running. Progress bar Displays the current process message and completion percentage. Log Shows a text log of the firmware upload process. Figure 32 Bootloader Dialog 44 User Guide

47 5 Operator Control Display The Operator Control Display (OCD) is the primary control interface for production operations for the LASC system. It displays the current and historical face and horizon information, allows the user to input correction data, and arm and disarm the LASC system. Figure 33 shows the OCD. Figure 33 OCD 5.1 Operation Mode The OCD can operate in either control or view mode. When in control mode the OCD allows the user to modify the correction information and issue and reject corrections. When in view mode no control operations are allowed. The operation mode is controlled by the user setting in the configuration.xml parameter file. In the following examples the first enable view mode and the second control mode: <configuration user="/" source="remote"> <configuration user="/control" source="remote"> It is expected that only a single control instance of the OCD will be running on the network. This is normally running on the Maingate PC. This behaviour is enforced if the Restrict control instances configuration option is enabled (via Database Config). A panel s specific control behaviour is further defined the panel s operation mode which is set on the Application Configuration tab of the Database Config tool. See section FA Control Mode and HC Control Mode for more details on control modes. LASC

48 5.2 Face Alignment Face Alignment control operations are conducted on the Face Alignment tab as shown in Figure 33. The profile panel shows a number of splines. They are as follows: Green profile is the current face profile with an arrow indicating the direction of travel. Blue profile is the current desired profile. Red profile is the currently uncommitted desired profile. This profile will become the blue profile when the corrections are issued. Orange profile is the RPCs for the current desired profile. Light green profile is the Corrected profile which is the result of RPCs applied to the to the Face profile. Red boxes are the spline control points. Red diamond is the lead/lag control point. Note that a legend is provided at the top of the profile display PROFILE AXES The horizontal axis on the profile panel is in support numbers and the vertical in millimetres. Note that the vertical axis range can be modified using the up and down arrows near the maximum and minimum values on the axis as shown in Figure 34. Figure 34 Profile Axes Adjustment LEAD AND LAG To introduce lead or lag in a gate to perform a wedge cut the Maingate control point can be dragged as shown in Figure 35. Lead and lag operations are one shot and will reset on the next cycle. They can also be performed simultaneously as straightening cuts. The OCD does not allow the user to enter Tailgate lead or lag directly however it should be noted that a Maingate lead is the same operation as a Tailgate lag. 46 User Guide

49 Figure 35 OCD Lead and Lag ISSUING AND REJECTING CORRECTIONS Dragging the control points will modify the desired profile shape. Once the desired profile is set then clicking on the Issue Corrections will arm the LASC system. The OCD Face Alignment tab will change from the image displayed in Figure 33 to that shown in Figure 36. Note that the Corrected spline shows the RPC applied to the current Face profile. LASC

50 Figure 36 Face Alignment Armed Arming the LASC system does not issue corrections immediately. Corrections will only be sent to the OEM system when it next requests them from the LASC system. Once the corrections have been sent to the OEM control system the LASC system is automatically disarmed. The following buttons are available on the Face Alignment tab: Reset Desired button will reset the modified desired spline (red) to the previously desired (blue). Straighten Desired will reset the desired spline to a straight line FA CONTROL MODE The FA panel can operate in a number of different control modes: Mode Control Options Description Control Automatic Locked automatic The basic manual control mode. The user is entirely responsible for arming the LASC system. The LASC system will be automatically rearmed however the user can toggle this mode off. The LASC system will always automatically rearm. 48 User Guide

51 Mode Control Options Description Headless The LASC system will be automatically rearmed by the NDP, an OCD instance does not need to be running. Corrections can still be rejected by a control instance of the OCD CHAINAGE The current panel chainage can be updated manually by entering the Maingate and Tailgate values on the Face Alignment tab and clicking Update. Updating the chainage values will force a rebuild of the LASC system. 5.3 Face Alignment History The Face Alignment History tab allows the user to view historical face alignment and RPC information and is shown in Figure 37. Figure 37 Face Alignment History The profile view can be modified using the controls on the right of the panel. LASC

52 Control Description Always view the current profile. Go to the current profile. Page up the view range. Zoom in and reduce the profile range. Set the viewing profile. Zoom out and expand the profile range. Page down the view range. Go to the last profile LEGEND AND SCALE The legend for the Face Alignment History panel is displayed at the top left hand corner of the panel. The scale of the panel can be modified using the up and down icons located next to the legend as shown in Figure 38 Face Alignment History legend and scale.. Figure 38 Face Alignment History legend and scale. 5.4 Horizon Control Horizon control operations are conducted on the Horizon Control tab as shown in Figure User Guide

53 Figure 39 Horizon Control The following buttons are available on the Horizon Control tab: Reset Extraction Height button will reset the extraction height modified desired spline (red) to the previously desired (blue). Straighten Extraction Height will reset the extraction height desired spline to a straight line. Reset Floor button will reset the floor modified desired spline (red) to the previously desired (blue). Straighten Floor will reset the floor desired spline to a straight line EXTRACTION HEIGHT The extraction height spline panel allow the user to manipulate the extraction height of the face. Positive adjustments will increase the face opening and negative adjustments will close it. The following splines are displayed on the Extraction Height panel: Blue profile is the current desired profile. Red profile is the currently uncommitted desired profile. This profile will become the blue profile when the corrections are issued. Green profile is the recommended adjustments. The recommended adjustments are a guide for achieving a constant in panel horizon path. Orange profile is the roof profile. This is taken from the heights of the shearer drums. The Extraction Height only controls the face opening. It does not directly define the roof horizon profile. LASC

54 5.4.2 FLOOR The floor spline panel allow the user to manipulate the floor horizon profile. The following splines are displayed on the Floor panel: Blue profile is the current desired profile. Red profile is the currently uncommitted desired profile. This profile will become the blue profile when the corrections are issued. Green profile is the recommended adjustments. The recommended adjustments are a guide for achieving a constant in panel horizon path. Orange profile is the current normalised floor horizon Note that a legend is displayed at the top of each panel. The scale can be modified using the up and down arrows located next to the max and minimum values on the scale. Note that normalised floor horizon profile uses the secondary vertical axis HC CONTROL MODE The HC panel can operate in a number of different control modes: Mode Control Options Description Control Automatic Locked automatic The basic manual control mode. The user is entirely responsible for arming the LASC system. The LASC system will be automatically rearmed however the user can toggle this mode off. The LASC system will always automatically rearm. 5.5 Horizon Control History The Horizon Control History tab allows the user to view historical horizon control information and is shown in Figure User Guide

55 Figure 40 Horizon Control History The profile view can be modified using the controls on the right of the panel. Control Description Always view the current profile. Go to the current profile. Page up the view range. Zoom in and reduce the profile range. Set the viewing profile. Zoom out and expand the profile range. Page down the view range. Go to the last profile. LASC

56 6 Service Control The Service Control application displays the current state of the LASC services and allows the user to control them. The Service Control must be run on the LASC server. Figure 41 shows the LASC Service Control. Figure 41 Service Control Hovering over the Exe, Srv and Run columns will display extra information regarding each service: Exe displays the version and installation location. Srv displays the service installation state. Run displays the running state of the service. Note when minimised the Service Control will minimise to the taskbar and display the following icon. 6.1 Controls A number of control options are provided by the Service Control application. The available options are dependent on the current state of each service. Table 1 outlines the control options. Control Prerequisite Service State Description Service is not installed. Service is installed. Service is installed but not running as a service. Service is installed and running as either a windows service or in console mode. Installs the service as a windows service. Uninstalls the service from the windows service control. Starts the windows service. Stops the windows service or console instance. 54 User Guide

57 Service is installed but not running. Starts the service in console mode. Table 9 Service Control Commands 6.2 Console Mode Running the service in console mode will run the service in the foreground and display the command window shown in Figure 42. Console mode is useful for trouble shooting issues. Figure 42 Console Mode LASC

58 7 External API A new feature in the LASC 1.5 is the External API. This API allows LASC data to be accessed via HTTP. Data can be return in the JSON, CSV or HTML format. This standardised API simplifies access to the LASC data and allows the back end database to be changed without breaking any customised data access systems. The External API is provided by the Monitoring Service and detailed documentation on using the API is displayed on the API s index.html page. Note the External API is enabled using Database Config -> Application Configuration -> Services -> Monitoring -> External API Enabled. See section Application Configuration for more details. 7.1 General URL format Segment Description server The server host. port The server port number. format The returned data format data The data type being requested param1 An example parameter being supplied to the request. param2 An example parameter being supplied to the request. Table 10 URL Segments VERSION The version string is in the form of v1.5.x.x and the current version of the API is FORMAT The format string determines what format the data is returned in. The API can currently provide data in the following formats: Format String json csv html Description Data is returned in the JSON format. Data is returned in comma separated values format. Data is returned in html format. 56 User Guide

59 Table 11 Data Format Strings DATA TYPES The data sets that are currently available via the API are as shown in Table 12. Data Set insinstant inslog ln270data profiles cutmodel face faces facedesired faceall horizon horizonsnapped horizonpredicted horizonrequired horizongradients horizonadjustments horizondesired horizonall oemlog events status panelinfo rpc fp ha ef fg Description Returns the latest INS record. Note that this data is not linked to odometry changes and it will be updated when the values change. Returns the log of the INS mode and status. Note that this data is not linked to odometry changes and it will be updated when the values change. Returns the raw LN270 data records. Returns the profile data records. Note these records contain the meta data relating to the profiles not the profile themselves. Returns the cut model data for a profile. Returns a face profile. Returns a set of face profiles. Returns the desired face profiles entered by the user. Note that these profiles will be cleared on database rebuild. Returns the face and desired profiles. Returns the horizon profile. Returns the snapped horizon profile where the maingate and tailgate are zeroed. Returns the predicted horizon profile. Returns the required horizon profile. Returns the horizon adjustments profile in gradients. Returns the horizon adjustments profile. Returns the desired horizon profile. Returns all horizon profiles. Returns OEM communications log records. Returns event log records. Returns the current status of the LASC system. Returns the panel information. Returns an OEM RPC record. Returns an OEM Floor Profile record. Returns an OEM Horizon Adjustment record. Returns an OEM Extracted Floor record. Returns an OEM Floor Gradient record. Table 12 External API Data sets LASC

60 8 Events and Status LASC 1.5 includes a new events and status system. Each LASC component logs a range of events and maintains its current status information. These items are stored in the events and status tables respectively. The easiest way to access this information is via the External API as shown in Figure 43 Status and Figure 44 Events. Figure 43 Status 58 User Guide

61 Figure 44 Events LASC

62 9 Troubleshooting This section will provide guidance on some common troubleshooting scenarios. 9.1 General Troubleshooting STATUS AND EVENTS TABLES The primary mechanism for diagnosing faults within the LASC system is the new status and events system which can be accessed via the External API. Any warnings or errors indicated on the status table should be investigated. The status table provides an overview of the overall system operating state. Each LASC system component has a range of different status elements associated with it which will be updated as the LASC system transitions through different operating states. Each status entry has a number of fields which are described in Table 13. Field Component ID Status ID Name Description State State Description Logged Updated Description The source component ID. The status ID of the Component. The human readable source component name. The description of the status. The state of the status element. The description of this state. The timestamp when this status first transitioned into this state. The timestamp when this state was last updated. Table 13 Status table fields The events table contains all events generated by the LASC system. Each event has a number of fields which are shown in Table 14. Each status table entry will have an associated events table entry that may contain extra information relating to the state change. Field ID Source Code Type Description Data Timestamp Logged Description The event ID. The source component. The event code. The event type. A description of the event. Any debug data associated with the event. The timestamp when this event was generated. The timestamp that the event was logged to the database. 60 User Guide

63 Table 14 Events Table Fields FILE LOGS The LASC services and tools also generate 4 file logs. These logs can contain more information that is not contain in the event table logs. By default these logs will be locate in C:\ProgramData\LASC RUNNING SERVICES IN CONSOLE A common troubleshooting technique is running the LASC services in console mode. This can be done either manually by passing the console parameter when running the service from the command line as shown in Figure 45 or by using the Service Control tool. Figure 45 Manual Console Service Command 9.2 Specific Troubleshooting SECURITY KEY LASC 1.5 requires the security key to be inserted into the LASC server to install and run. If the key is not present or detected correctly then the some services will not install, run or process data correctly. Refer to section 3.2 for more information regarding the installation of the security key. To check that the security key has been correctly detected view the following link on the last server LASC 1.0 IIB AND MUPS FIRMWARE UPGRADE Pre V3.2 hardware versions of the IIB and MUPS have a fault that may inhibit automatic firmware upgrading. If you are unable to upgrade the firmware, inspect what version of hardware is in use. If a pre V3.2 board is in use it should be replaced PROFILE ISSUES There are a number of potential issues that can affect the proper generation of profiles. Due to this a fault finding flowchart has been provided to assist in diagnosing profile related issues. This flowchart is shown in Figure File logging is a configurable option. Please refer to section 4.2 for more information. LASC