€¦ · Web viewUsage: accel-list [to] List accelerometer parameters in configuration for import to Excel. accel-list -v > accellist.csv. Use -a to include alarm settings of Overall

====== ACCEL-LIST =============================================================

Usage: accel-list [to] List accelerometer parameters in configuration for import to Excel

accel-list -v > accellist.csv

Use -a to include alarm settings of Overall Use -v to include max value during last day of each parameter Use -h to search last hour for value Use -w to search last week for value Use -m to search last month for value Use -d <database> for other databases than the standard database

====== ACCEL-SENSITIVITY ======================================================

Usage: accel-sensitivity List accelerometer sensitivities for import to Excel Use -d <database> for other databases than the standard database

====== AD-CONFIG-UPDATE =======================================================

Usage: ad-config-update

List AD references where removing "xxx" from the reference would reference another existing measurement.

Existing AD references can be moved from one transducer to another by following these steps: - Use Configurer to ensure the transducers you want to reference exists. - Rename the AD reference transducers so their name is identical to the transducer you want to reference and append xxx to the first part of the transducer name. - Repeat the above for all transducers where you want the AD to reference another transducer. When done you will have a configuration with pairs of transducers: - One you want to delete, that the AD references. - One you would like to keep, that the AD should reference. - Now use ad-config-update to move the AD references. - Restart the Configurer and delete the xxx transducers.

Use -u to update the configuration. ad-config-update will make a backup of the configuration as a safety measure before performing the update.

Use -x <text> to use <text> as filter. Use -f to force update ignoring any confirmation questions. Use -s to supress outputs. Use -d <database> for other databases than the standard database

====== AD-ENABLE ==============================================================

Usage: ad-enable [machine]... Display AD method enable information, symptom statistics, value and component execution date for one or more machines.

ad-enable [-all|-pad|-iad|-<method id>] ... [machine]...

To display information for methods 33 for one machine: ad-enable -33 MBD

which could display information like:

Method 33: 3 configured 3 enabled 0 stealth Rotor Unbalance OTA 20.3.4.0 0.00 2003-09-10 23:59 + Shaft ~15.2.1.0 0.00 2003-09-01 23:59 2003-09-10 23:59 + Generator Shaft ~0.0.0.0 2003-09-10 23:59 + Exciter Shaft

The 20.3.4.0 statistics is a count of symptom values in the normal, predicted, detected and action ranges for the past month. The ~ is used when the symptom is not up-to-date.

When using the -u or -c flag ad-enable can also be used to - update AD enable status - clear AD symptom values - prepare recalculation of symptoms from specific date

When enabling AD measurements for methods that was not previously executed their component execution date will be initialised to midnight.

ad-enable -u [-|*|+][all|pad|iad|<method id>]... [machine]...

The flag affects the AD measurements using the method as follows: - : disable AD measurements * : stealth enable AD measurements + : enable AD measurements including AD alarming

To enable only predicted AD measurements for four machines: ad-enable -u -all +pad NDC02 NDC03 NDC05 NDC06

To clear symptoms and prepare recalculation for the last month: ad-enable -c -o 30 -all

Use -s for output without symptom information. Use -v for verbose output with unconfigured methods and listing all AD measurements. Use -V for extended verbose output. Use -c to clear AD measurements, set component execution date and delete AD messages for the specified methods. Use -u to update enable setting. The execution date of newly enabled components are set. Use -o <days> to use a date from <days> ago, rather than today, when setting component execution time. Use -f to force update without confirmation questions. Use -d <database> for other databases than the standard database.

IMPORTANT: Component execution time updates will use a site time of 23:59. ad-enable determines site time based on the oldest component execution time and only when no component times are available local time will be used. If the site is in a different time zone the execution times will not be from midnight to midnight, but some other time.

IMPORTANT: The component execution dates are NOT part of the configuration and is not included in a configuration backup.

====== ADAM ===================================================================

adam <dau> <serial-linenumber 1-3> <trigger string>

====== ADAMTCP ================================================================

Usage: adamtcp <ip-address> <trigger string>

Send command to ADAM-6060 Relay Output Module using TCP/IP connection. The trigger command must consist of six 0's and 1's. E.g. use

adamtcp 10.10.5.13 100000

to trigger the first relay.

====== ALARM-SCRIPT ===========================================================

Usage: alarm-script l5 l4 l3 l2 l1 h1 h2 h3 h4 h5 spu Activates relays and sends e-mails according to alarm status

Launched by alarms.bat which is launched by the Data Server everytime there is a change in the alarm status.

Files: alarms.bat -- command started by Data Server alarm-script.pl -- this command alarm-status.txt -- contains previous alarm status alarm-log.txt -- contain entry for all alarm script events ALARMADAMRELAYS -- field in SYSTEMTABLE that must be set to 1

====== ALARMS =================================================================

Can't open perl script "alarm-script.pl": No such file or directory

====== ANSWER =================================================================

Usage: answer <question>

====== AVERAGES-CLEAR-DELETED =================================================

Usage: averages-clear-deleted Delete averages from database for deleted measurements. Use -d <database> for other databases than the standard database

====== BDC-LIST ===============================================================

Usage: bdc-list [to] List displacement probe BDCraw, BDC and Wear parameters in configuration for import to Excel

bdc-list -v > bdclist.csv

Use -a to include alarm settings of BDCraw, BDC and Wear Use -v to include max value during last day of each parameter Use -h to search last hour for max value Use -w to search last week for max value Use -m to search last month for max value Use -d <database> for other databases than the standard database

====== BLOB-CLEAR-DUPLICATES ==================================================

Usage: blob-clear-duplicates <from> <to> [tdx]... List duplicate/overlapping BLOBs within period. All BLOBs partly in period will be verified for: - length - ENDR < STARTR - incorrect sequence in timestamp between BLOBs When BLOBs with identical STARTR is found the BLOB with least data will be deleted.

When BLOBs with overlapping time periods are found the BLOB with latest STARTR will be deleted.

Use -c <code> to check one measurement Use -m <machine> to check entire machine Use -a check all BLOBs of specified tdxs rather than limited period. Use -r to remove duplicate/overlapping BLOBs Use -v for verbose output Use -d <database> for other databases than the standard database

Hint: blob-clear-duplicates can be used to remove duplicate trends (BLOB) from a database-replication gone wrong due to a corrupted archive. Run blob-clear-duplicates for the period covered by the corrupted archive (Remember to extend period in case of time zone differences).

====== BLOB-VERIFY ============================================================

Usage: blob-verify <from> <to> <tdx>... Verify BLOBs within period. All BLOBs partly in period will be verified for: - length - ENDR < STARTR - STARTR != first event - ENDR != last event - incorrect sequence in timestamp inside and between BLOBs

Use -c <code> to check one measurement Use -m <machine> to check entire machine Use -q verification without verifying individual events inside BLOB Use -l to skip check between length of BLOB and size of data Use -v for verbose output Use -d <database> for other databases than the standard database

====== CLEAR-AD-CONFIG ========================================================

Usage: clear-ad-config Delete AD configuration, symptom trends and clear tracking table. Data Server and User Interface must be stopped during this command. Use -d <database> for other databases than the standard database

====== CLEAR-AD ===============================================================

Usage: clear-ad Delete AD symptom trends and clear tracking table. Data Server and User Interface must be stopped during this command. Use -d <database> for other databases than the standard database

====== CLEAR-ASDIAG ===========================================================

Usage: clear-asdiag Delete all Auto Spectra data named diag. Data Server and User Interface must be stopped during this command. Use -a to delete only accelerometer/velocity Auto Spectra Use -d <database> for other databases than the standard database

====== CLEAR-DATA =============================================================

Usage: clear-data [[from] to] Delete data and alarm history. Data Server and User Interface must be stopped during this command. Use -f to force deletion of alarms without further confirmation. Use -d <database> for other databases than the standard database Use -s to delete signature data only From/to must use the format yyyy-mm-dd hh:mm or yyyy-mm-dd hh:mm:ss

Note: Scalar events are stored in BLOBs containing up to 180 events. A BLOB is only deleted when ALL events in the BLOB are within the time period as specified by from and to.

====== CLEAR-MEASUREMENT ======================================================

Usage: clear-measurement [[from] to] <code>... Delete measurement data and alarm history of speficied measurements. Use -m <machine> to clear all measurements for a machine clear-measurement -m <machine> [from] [to] Use -d <database> for other databases than the standard database Use -v with -m to delete only measurements with physical SPU input Use -s to delete signature data only Use -f option to override all confirmations From/to must use the format yyyy-mm-dd hh:mm or yyyy-mm-dd hh:mm:ss

====== CLEAR-TMP ==============================================================

Usage: clear-tmp Clearing database for temporary tables, that may exist if a previous database-restore was aborted.

Use -d <database> for other databases than the standard database

====== CLEAR-WARNINGS =========================================================

Usage: clear-warnings [from] [to] [machine...] Delete warning history. Data Server and User Interface must be stopped during this command. Use -s to clear system warnings only. Use -f to force deletion of warnings without further confirmation. Use -d <database> for other databases than the standard database From/to must use the format yyyy-mm-dd hh:mm

====== CMP ====================================================================

NAME cmp - compare two files

SYNOPSIS cmp [-l] [-s] *file1* *file2* *[skip1 [skip2]]*

DESCRIPTION *cmp* compares two files, byte-by-byte. The result of the comparison is always given by the exit status, and may be summarized on the standard output according to the options given on the command line.

If the two compared files are identical, *cmp* will exit with a zero exit status. If the compared files are not identical, *cmp* will exit with a status of 1.

If no options are given, *cmp* will return (on the standard output), the byte number and line number where the first difference is encountered.

If one file is an initial subsequence of the other, a message will also be returned on the standard error indicating that EOF was reached in the shorter of the two file.

*skip1* and *skip2* are optional byte offsets into *file1* and *file2*, respectively, that determine where the file comparison will begin. Offsets may be given in decimal, octal, or hexadecimal form. Indicate octal notation with a leading '0', and hexadecimal notation with a leading '0x'.

OPTIONS -s silent execution; indicate results only by exit status, suppressing all output and warnings.

-l list differences; return the byte number and the differing byte values for each difference between the two files. The byte number is given in decimal, and the byte values are given in octal.

ENVIRONMENT No environment variables affect the execution of *cmp*.

BUGS No known bugs.

AUTHOR D Roland Walker *<[email protected]>*.

COPYRIGHT and LICENSE This program is copyright (c) D Roland Walker 1999.

This program is free and open software. You may use, modify, distribute, and sell this program (and any modified variants) in any way you wish, provided you do not restrict others from doing the same.

__END__ :endofperl

====== CODE-DELETE ============================================================

Usage: code-delete <code> code-delete [ -f ] <code> Delete code from database Use -d <database> for other databases than the standard database Use -f option to force delete despite of warning

====== CODE-LIST-COMPARE ======================================================

Usage: code-list-compare old-code-list new-code-list Compare code lists made by database-code-list and lists differences

====== CODE-RENAME ============================================================

Usage: code-rename <old-code> <new-code> code-rename <old-code> to <new-code> Use -d <database> for other databases than the standard database Use -f option to force update despite of warning code-rename [ -f ] <old-code> <new-code>

====== CONFIG-LOG =============================================================

Usage: config-log Show contents of config log. Use -d <database> for other databases than the standard database

====== CONFIG-UPDATE ==========================================================

Usage: config-update <database> Compare the configuration of two databases and list differences: - plants added/missing - machines added/missing - transducers added/missing or changed type - measurements added/missing, changed type or range

Only present transducers are included in the comparison Use -v to include vibration measurements in the list.

Use -u to update the configuration using <database> as reference. - for transducers config-update will update: description, angle, serialno, transducer status, MOS SPU/Server, channel, coupling, overload detection, gain, icp sensitivity and offset - for non AD and non vibration measurements config-update will update: unit, description, range and event settings config-update will make a backup of the configuration as a safety measure before performing the update.

Use -f to force update ignoring any confirmation questions. Use -s to supress outputs. Use -d <database> for other databases than the standard database

====== CP =====================================================================

Usage: cp <source>... <destination> Copy source to destination or multiple sources to folder

Use -f to force overwriting existing destinations, never prompt Use -v verbose output

====== CPB-REVIEW =============================================================

Usage: cpb-review [to] [machine] Review CPB measurements and present results for import to Excel

cpb-review -s 50 > cpblist.csv

Use -r <revision> to set noise floor according to SPM revision -r C2 will use maximum noise level of SPM revision C2 (Default) -r C3 will use maximum noise level of SPM revision C3 -r QL will use quantisation noise level

Use -h to search last hour for value Use -w to search last week for value Use -m to search last month for value Use -s <slope> to add plots of all CPBs to file plot.txt with negative slope less than <slope> Use -d <database> for other databases than the standard database

The maximum values of each line within the period is examined for: - Overall level in frequency range defined by overall measurement - Level in mV for full frequency range of defined CPB - Optimal gain setting when allowing head room of 20 dB - Noise floor of defined Overall in mm/s with current gain - Slope per octave of first 2 octaves in CPB (five if 1/1 CPB) - Ski slope warning when negative slope is less than 40% and level is - Overall warning when above 10 mm/s - Suspicious overall warning when above 20 mm/s

====== CREATE-REGISTRY ========================================================

Usage: create-registry Updates OPENpredictor registry entries.

====== CSV2RDM ================================================================

Usage: csv2rdm <CSV-file> Display event data in RDM format one event on each line. Useful for transferring Excel data to RDM. The spreadsheet must be formated as shown below:

| A | B | C | D | 1 | Title | | | | 2 | Code | MAD CS001 | MAD CE002 | MAD CT002 | 3 | Tacho | 1 | | | 4 | Absolute event window | 1 | 0.1 | 100 | 5 | Relative event window | 0 | 0 | 1.1 | 6 | 2002-08-28 13:34:00 | 123.4 | 0.123 | -2334 | 7 | 2002-08-28 13:35:00 | 123.5 | 0.223 | | 8 | 2002-08-28 13:36:00 | 123.4 | | -2100 |

The above spreadsheet would generate 5 events. Code row list the measurements to be converted to RDM and is required. Tacho row identifies a tacho measurement and is optional. Event window rows reduces the number of events generated and are optional. Data rows start with a time stamp in the format yyyy-mm-dd hh:mm:ss. All other rows are ignored. Note: Comma is not allowed in codes or values.

====== CURRENT-DATABASE-VERSION ===============================================

Usage: current-database-version Display current database version matching OPENpredictor software Use -m option to see MFL version

====== DACIF_GET_LEVELS =======================================================

Usage dacif_get_levels<hostname> <rpc process name> <tdx> <channel>

====== DAILY-JOBS =============================================================

The system cannot find the path specified.Can't open file daily.txt

====== DAILY ==================================================================

Usage: daily <hour> <command> Execute command provided the hour equals present time

====== DATA-CLEAR-DUPLICATES ==================================================

Usage: data-clear-duplicates Delete duplicate data from database. Use -v for verbose output Use -a for analysing without deleting data Use -d <database> for other databases than the standard database

====== DATA-SYNC ==============================================================

Usage: data-sync -d <database> [from] Sync data in local database with data in remote database Eg. data-sync @vkv brings local copy of vkv database up-to-date The local configuration must be the same as the remote Default behaviour is to sync all types of data Use -a to sync alarms Use -l to sync AD messages Use -s to sync scalar data Use -z to sync signature data Use -8 to use dbi:Oracle instead of dbi:ODBC Options -a -t -s can be combined to sync several types of data Use -m option to limit sync to a specific machine data-sync -d <database> -m <machine> [from]

Use -o option specify a timeout in minutes for the max time to wait Note for slow networks (< 1 Mbit): data-sync will often hang. If data-sync do not respond within 60 sec press c-C to abort and restart the program. data-sync will restart the transmission from where it was aborted. Performance is very sensitive to the ODBC settings and they should be: Read only mode, prefetch 1000 and disable all application options

====== DATABASE-ANALYSIS ======================================================

Usage: database-analysis [[from] to] Analyse database storage of measurements for past day. A time interval can be specified to limit the analysis of data. database-analysis [yyyy-mm-dd hh:mm [yyyy-mm-dd hh:mm]]

Note: When analysing a time interval the storage size of trend data will be based on all BLOBs partly or entirely in the time interval.

Use -s to analyse signature data Use -t to analyse trend data Use -h to analyse data for last hour Use -w to analyse data for last week Use -m to analyse data for last month Use -d <database> for other databases than the standard database

====== DATABASE-ARCHIVE =======================================================

Usage: database-archive [yyyy-mm-dd] [file] Incremental database backup to zipped archive. The incremental backup will contain all data since the last incremental backup and up to now or the date specified. The archive flag is set to 1 for all backed up data. Scalar BLOBs that have not been completely filled will be included in. the backup.

To automatically make a daily incremental archive you can add the following line to service-jobs.txt: SYSTEM: database-archive -n %DATE my-plant

When running database-archive automatically the incremental archives will be placed in the Work\Archive folder.

Use -d <database> for other databases than the standard database Use -f to force execution skipping any confirmation questions. Use -s to exclude signatures from archive. Use -n to exclude diagnostic auto spectra from archive. Use -o to exclude orbits from archive. Use -r to reset archive flag for all data. Use -S to disable archive flag of existing signature data. Use -N to disable archive flag of existing diagnostic data. Use -O to disable archive flag of existing orbit data.

====== DATABASE-BACKUP ========================================================

Usage: database-backup <file> Backup database to file. Date is added to filename. A time interval can be specified to limit the backup of data. database-backup [yyyy-mm-dd hh:mm [yyyy-mm-dd hh:mm]] <file>

Use -d <database> for other databases than the standard database You can use option -d to backup a remote Oracle 8.1.7 database on an Oracle 8.1.6 system to get a dump file in format 8.1.6 database-backup -d indi@support <file>

Use -c to backup configuration only without data database-backup -c <file>

Use -b to backup configuration less baseline signatures and data database-backup -b <file>

Use -t to backup scalar trend data only Use -a to backup alarms only Use -A to backup AD tracking table only Use -l to backup AD log messages only Use -r to backup reliability data monitoring data only Use -f to backup fatigue log table only Use -s to backup signature data only Use -o to backup orbit signature data only Use -m to backup data from specific machine only Use -e to exclude route log information from config backup Use -n to exclude diag measurements from backup

Use -z to compress backup file Use -Z override automatic compression and skip readme file Use -R to make reduced backup with only some signature data as specified by from/to parameters. It is signigicantly faster to do a database-backup / database-restore than to delete a large amount of signature data from a +20 GB database. E.g. database-backup -R yyyy-mm-dd hh:mm <file>

Use -M to backup data from last completed month. Use -W to backup data from last week. Use -D to backup data from yesterday. Usefull for Monthly, Weekly or Daily scheduled backups

====== DATABASE-CHECK =========================================================

Usage: database-check Check database and list unreferenced items Use -d <database> for other databases than the standard database

====== DATABASE-CODE-LIST =====================================================

Usage: database-code-list Display list of measurement tdx, type and code Can be used together with code-list-compare to verify configuration compatibility before updating it with database-restore -c If the codes has changed this can be corrected with fix-value-code Use -d <database> for other databases than the standard database

====== DATABASE-COPY ==========================================================

Usage: database-copy <database1> <database2> Copy content of all tables from database1 to database2. Eg. database-copy beta@support beta Database2 must already exist with tables defined. Existing tables in Database2 are truncated before copying the data. Use -f to force copy ignoring missing tables.

====== DATABASE-CREATE ========================================================

Usage: database-create <database> Create OPENpredictor database (An OPENpredictor database is the same as an Oracle user) Use -d <database> for other databases than the standard database E.g. database-create oscar@vkv to create oscar database at vkv

====== DATABASE-DELETE ========================================================

Usage: database-delete <database> Delete OPENpredictor database (An OPENpredictor database is the same as an Oracle user) Use -d <database> for other databases than the standard database E.g. database-delete oscar@vkv to delete oscar database at vkv

====== DATABASE-DESCRIPTION-LIST ==============================================

Usage: database-description-list List measurement code and description where found Use -d <database> for other databases than the standard database Use -a to list all descriptions including the empty ones

====== DATABASE-EXISTS ========================================================

Usage: database-exists [ database ] Check if database exists and sets return code accordingly Use -d <database> for other databases than the standard database Exit code 0 if database exist Exit code 1 if database do not exist

====== DATABASE-INCREASE ======================================================

Usage: database-increase Display database increase in MB. Use -d <database> for other databases than the standard database Use -o <days> to see database increase over more than one day

====== DATABASE-INTAKE ========================================================

Usage: database-intake [[from] to] Calculate database storage of measurements for past day. The calculation of trend data storage size will be based on all BLOBs partly or entirely in the time interval.

Use -h to analyse data for last hour Use -w to analyse data for last week Use -m to analyse data for last month Use -d <database> for other databases than the standard database

====== DATABASE-LOG ===========================================================

Usage: database-log Show contents of database log. Use -d <database> for other databases than the standard database

====== DATABASE-OPTIMISE ======================================================

Usage: database-optimise Optimise database by computing table statistics. Use -d <database> for other databases than the standard database

Hint: The performance gains by optimisation of the database can be dramatic for large databases or databases with many alarms. This command should only be run after coarse tuning when enough data are available in the database.

Hint: ALWAYS run this command after restoring a database.

====== DATABASE-REPLICATE =====================================================

Usage: database-replicate -d <minutes> Performs a number of database replication jobs every <minutes>: - executes all commands found in the database-replicate.txt file if found in the OPENpredictor\Commands folder

Note: The database-replicate.txt file assumes the following format: - Blank lines and lines starting with # are ignored. - A command line may be preceded with an optional keyword: SYSTEM: Command to be executed in system root folder as if it was started by AT. STOP: Execution of remaining commands stops immediately - A command may contain the following keywords: %DATE substituted with yyyy-mm-hh before executing command %TIME substituted with hh-mm before executing command %OPPATH substituted with path to OPENpredictor folder - All other commands are started in the Work folder - The remaining command line is executed - When a command do not redirect its output it will automatically be redirectred to the database-replicate-log.txt file.

Examples of command lines in database-replicate.txt: database-restore-archives -dsuez -fp"P:\<project>\Transfer

When -d option is omitted or zero the jobs are only done once.

====== DATABASE-RESTORE-ARCHIVES ==============================================

Usage: database-restore-archives Restore incremental archives to database from one or more archive files Use -d <database> for other databases than the standard database Use -p <path> to get archives from other location than current folder Use -u to unacknowledge alarms in incremental archive Use -a <first> to restore from <first> archive and onwards Use -a <first>:<last> to restore from <first> to <last> archive Use -f to override any confirmation questions asked

====== DATABASE-RESTORE =======================================================

Usage: database-restore <file> Restore database from file. When file is a zip file all backup files found in the zip file are extracted and imported.

Normally the backup file will be used to restore the database. However files containing the names below are treated differently: -trend- file will add trend data. Before the data are added all unfilled BLOBs are deleted to avoid conflicts with the new data -sign- file will add signature data. -alarm- file will add alarm data. -bdc- file will add bdc data. -log- file will add AD log message data. -rdm- file will add Reliability Data Monitoring data. -fat- file will add fatigue monitoring data. -nosign- file is complete backup without signature data. -config- file will replace existing configuration and delete data unless the -c options is used. When using the -c option the configuration is replaced without loosing data: database-restore -c <file>

Important: Before attempting to replace an existing configuration you should use compare-code-list to ensure the codes used by the configuration match the codes in the data. Otherwise you will loose data.

Use -d <database> for other databases than the standard database Use -v <version> for restoring database to non current version Use -u to unacknowledge alarms in incremental archive Use -f to avoid any confirmation questions Use -e to avoid overwriting E-tags on off-line transducers Use -b to avoid overwriting alpha & beta values even when no other baselines are set

====== DATABASE-SHOW ==========================================================

Usage: database-show Display available databases Use -d <database> for other databases than the standard database E.g. database-show @vkv to list databases at vkv

====== DATABASE-STATUS ========================================================

Usage: database-status Check and display storage status of all tablespaces and databases. Use -d <database> for other databases than the standard database E.g. database-status @vkv to examine databases at vkv

====== DATABASE-STRUCTURE-CHECK ===============================================

Usage: database-structure-check [-d <database>] Compare structure of an updated database to the empty database. If no EMPTY database of current version is found, it will be restored first.

Use -d <database> for other databases than the standard database Use -r <database> for other reference than the empty database

====== DATABASE-TIDY ==========================================================

Usage: database-tidy Deletes unreferenced items from database Use -d <database> for other databases than the standard database

====== DATABASE-UPDATE-INTERIM ================================================

Usage: database-update-interim [version] Update the database format to current database version or version specified Also updates the interim letter versions. E.g. from 2.6.3a to 2.6.3b Use -d <database> for other databases than the standard database

====== DATABASE-UPDATE ========================================================

Usage: database-update [version] Update the database format to current database version or version specified Use -d <database> for other databases than the standard database

====== DATABASE-VERSION =======================================================

Usage: database-version Use -d <database> for other databases than the standard database Displays version of OPENpredictor database Use -m option to see MFL version Use -s option to set version database-version -s <version>

====== DATABASE-VIEWLOG =======================================================

Usage: database-viewlog View contents of database log Use -d <database> for other databases than the standard database Use -n <number> to specify how many log entries to show (default=10)

====== DATABASE2RDM ===========================================================

Usage: database2rdm [[from] to] <tdx>... Extract data from database in RDM format. Only the specified measurements in the specified period are extracted. When no measurements are specified all measurements are extracted. Use list of tdx's or options -c,-M to limit the number of measurements: database2rdm <tdx>... database2rdm -c <code> database2rdm -M <machine> When no period is specified one day of data are extracted. Use to and from or options -h,-w,-m to specify the period: database2rdm [to] database2rdm -w [to] database2rdm [from] [to] Normally you want to limit both measurements and period: database2rdm [to] <tdx>... database2rdm -wM <machine> [to] database2rdm -c "<code>" [from] [to] Use -h to display data for last hour Use -w to display data for last week Use -m to display data for last month Use -a to display data since beginning of database Use -c to display data for any item Use -i to include invalid data causing range errors Use -v to print status at end of data extraction Use -S <SPU> to display data for all measurements on SPU Use -M <machine> to display data for all measurements on machine Use -H to skip header Use -r to use easy human readable float format Use -d <database> for other databases than the standard database From/to must use the format yyyy-mm-dd hh:mm or yyyy-mm-dd hh:mm:ss

====== DATE2GMT ===============================================================

Usage: date2gmt <yyyy-mm-dd> <hh:mm:ss> Converts date into seconds since 1970-01-01 00:00:00 GMT Please observe that date is in GMT time

====== DATE2TIME ==============================================================

Usage: date2time <yyyy-mm-dd> <hh:mm:ss> Converts date into seconds since 1970-01-01 00:00:00 GMT Please observe that date is in local time

====== DIFF ===================================================================

Usage: diff.bat [{-c | -C lines -e | -f | -u | -U lines}] oldfile newfile -c do a context diff with 3 lines of context -C do a context diff with 'lines' lines of context (implies -c) -e create a script for the ed editor to change oldfile to newfile -f like -e but in reverse order -u do a unified diff with 3 lines of context -U do a unified diff with 'lines' lines of context (implies -u)

By default it will do an "old-style" diff, with output like UNIX diff

====== DISABLE-IAD ============================================================

Usage: disable-iad <state-list> [machine] ... Disable IAD alarms in the states listed. <state-list> is a list of state names seperated by colon ":". E.g.

disable-iad "Balancing:-> Stable Load:No Load" VP3 VP4

When no machines are specified all machines are updated. Use -d <database> for other databases than the standard database Use -f to force execution without any confirmation questions

====== DISP-LIST ==============================================================

Usage: disp-list [to] List displacement probe parameters in configuration for import to Excel

disp-list -v > displist.csv

Use -a to include alarm settings of Spp/Position Use -v to include last value during last day of each parameter Use -h to search last hour for value Use -w to search last week for value Use -m to search last month for value Use -d <database> for other databases than the standard database

====== DMP-FIX815 =============================================================

Usage: dmp-fix815 <file> Updates dmp file from Oracle 8.1.5 to Oracle 8.1.6 The update includes renaming of columns in tables with LONG Used by database-restore when restoring very old databases

====== DMP-INFO ===============================================================

Usage: dmp-info <file> dmp-info -h <file> Display information from dmp file Use -h option to display only header info

====== DMP-TIDY ===============================================================

Usage: dmp-tidy <file> Tidy dmp file by: - using standard storage settings - using tablespace USERS and INDX - skipping triggers

====== DOIT ===================================================================

Usage: doit <command file> Execute commands in file Use -l <log-file> to create log Use -r <count> to set retry count. Default count is 3

====== DP-EVENT-WINDOWS =======================================================

Usage: dp-event-windows Update the event windows as follows: µm : Position abs= 5 rel= - th= - µm : Overall, Smax, Sm, Spp abs= 5 rel= - th= 10 µm : OTA 1x abs= 5 rel= - th= 10 µm : OTA 1p abs= 2 rel= - th= - µm : OTA 2x abs= 5 rel= - th= 10 µm : OTA 2p abs= 5 rel= - th= - µm : OTA TRT 1x abs= 2 rel= - th= 10 µm : OTA TRT 1p abs= 10 rel= - th= - µm : OTA TRT 2x abs= 2 rel= - th= 10 µm : OTA TRT 2p abs= 10 rel= - th= - µm : AS diag abs= 5 rel= - th= 10 µm : AS, CPB, SED abs= 2 rel= 0 th= 2 µm : AS TRT abs= 1 rel= 0 th= 1

modification of calibration measurement setups like AS Cal. Event windows already set to higher values than above are not updated Event windows already set to zero are not updated to prevent to prevent modification of measurement setups like external vibration. Use -d <database> for other databases than the standard database. Use -f to avoid any confirmation questions.

====== DUMP2RDM ===============================================================

Usage: dump2rdm [[from] to] <tdx> Special version of database2rdm for counting number of events. Use -c <code> option to display configuration for any item Use -h option to specify type of harmonic (sub, res, 1x, 1p, etc.) Use -a option to print all scalars in BLOB not just those within period Use -r option to use easy human readable float format Use -w to display data for last week Use -m to display data for last month Use -d <database> for other databases than the standard database From/to must use the format yyyy-mm-dd hh:mm

====== EVENT-ADD ==============================================================

Usage: event-add <tdx> [date] <value> event-add <tdx> [date] <value> <value>/<value> <value> event-add -c <code> [date] <value> event-add -c <code> [date] <value> <value>/<value> <value> Add event to database by writting directly into database Use -d <database> for other databases than the standard database Use -r <rpm> option to add rpm value to event From/to must use the format yyyy-mm-dd hh:mm or yyyy-mm-dd hh:mm:ss

====== EVENT-STATISTICS =======================================================

Usage: event-statistics <machine> Display statistic for events been measured during last day Only BLOB with start time within period are counted Use -d <database> for other databases than the standard database Use -h to display data for last hour Use -w to display data for last week Use -m to display data for last month

====== EVENT-STEPS ============================================================

Usage: event-steps Display absolute and relative step between events

Use rdm-show to provide input to event-steps. E.g. rdm-show signatures.rdm | event-steps

====== FI-CONFIG ==============================================================

Usage: fi-config Display File Import setup file. Use this as a draft for the fileimportsetup.txt configuration file. E.g.: fi-config > C:\OPENpredictor\Data\fileimportsetup.txt Use -d <database> for other databases than the standard database

====== FI-LIST ================================================================

Usage: fi-list [to] List FI parameters in configuration for import to Excel

fi-list -v > filist.csv

Use -v to include last value during last day of each parameter Use -h to search last hour for value Use -w to search last week for value Use -m to search last month for value Use -d <database> for other databases than the standard database

====== FI-TEST-VALUE ==========================================================

Usage: fi-test-value <tdx> <value> Replace value in fitestdata.txt for tdx.

====== FI-TESTDATA ============================================================

Usage: fi-testdata [file] Read fileimportsetup.txt and outputs fi test data with baseline as initial value. To produce fitestdata.txt: fi-testdata > C:\OPENpredictor\Data\fitestdata.txt


====== FI-VALUE ===============================================================

Usage: fi-value <tdx> ... Get value from FI Use -r option to repeat command Use -d <database> for other databases than the standard database

====== FILE-EXPORT-SERVER =====================================================

Usage: file-export-server

Updates text file with values from OPENpredictor at regular intervals.

Operation defined in configuration file named: fileexportsetup.txt.

Use -d <database> for other databases than the standard database. Use -V verbose output without creating file.

To install file-export-server as a service use:

service-install "OP File Export" C:\OPENpredictor\Service\file-export-server.pl

====== FILE ===================================================================

Usage: file <file> Display standard input and save to file Use -a option to append to existing file

====== FIX-ADD-SPECTRAL-BAND ==================================================

Usage: fix-add-spectral-band List first spectral band for all CPBs on REB Use -d <database> for other databases than the standard database Use -u to automatically replace first spectral band with REB Fault band Use -f to force execution without any confirmation questions

====== FIX-ASDIAG =============================================================

Usage: fix-asdiag List or update AS diag configuration Use -d <database> for other databases than the standard database Use -a to list/update only accelerometer Auto Spectra Use -v to list/update only velocity Auto Spectra Use -p to list/update only proximity probe Auto Spectra Use -t <value> to update threshold Use -w <value> to update absolute event window Use -r <value> to update relative event window factor Use -f to force execution without any confirmation questions

====== FIX-DEADBAND ===========================================================

Usage: fix-deadband Set deadbands to absolute event window settings as follows: µm : Position abs= 20 rel= - th= - µm : Overall, Smax, Sm, Spp abs= 10 rel= - th= - mm/s: Overall abs=0.5 rel= - th= -

Deadbands already set to lower values than 1000 are not updated Use -d <database> for other databases than the standard database. Use -f to avoid any confirmation questions.

====== FIX-DESCRIPTION ========================================================

Usage: fix-description description-list Use -d <database> for other databases than the standard database Use -u option to perform update Use -p option to propagate descriptions for Overall to other measurements Use database-description-list > file to make description-list

====== FIX-DISABLED-MEASUREMENTS ==============================================

Usage: fix-disabled-measurements [version] Disable outdated measurements in the database. Use -d <database> for other databases than the standard database. Use -f to force disabling without confirmation.

====== FIX-EI =================================================================

Usage: fix-ei Create ei index Use -d <database> for other databases than the standard database

====== FIX-EVENT-WINDOWS ======================================================

Usage: fix-event-windows Update the event windows as follows: µm : Position abs= 20 rel= - th= - µm : Overall, Smax, Sm, Spp abs= 10 rel= - th= 20 µm : OTA 1x abs= 10 rel= - th= 20 µm : OTA 1p abs= 2 rel= - th= - µm : OTA 2x abs= 10 rel= - th= 20 µm : OTA 2p abs= 5 rel= - th= - µm : OTA TRT 1x abs= 10 rel= - th= 20 µm : OTA TRT 1p abs= 10 rel= - th= - µm : OTA TRT 2x abs= 10 rel= - th= 20 µm : OTA TRT 2p abs= 10 rel= - th= - µm : AS diag abs= 10 rel= - th= 20 µm : AS, CPB, SED abs= 10 rel= 0 th= 10 mm/s: Overall abs=0.5 rel= - th= 1 mm/s: OTA 1x abs=0.5 rel= - th= 1 mm/s: OTA 1p abs= 10 rel= - th= - mm/s: OTA 2x abs=0.5 rel= - th= 1 mm/s: OTA 2p abs=360 rel= - th= - mm/s: OTA TRT 1x abs=0.5 rel= - th= 1 mm/s: OTA TRT 1p abs=360 rel= - th= - mm/s: OTA TRT 2x abs=0.5 rel= - th= 1 mm/s: OTA TRT 2p abs=360 rel= - th= - mm/s: AS diag abs=0.5 rel= - th= 1 mm/s: AS, CPB, SED abs=0.5 rel= 3 th=0.05 m/s²: AS diag abs= 2 rel= - th= 2 m/s²: AS, CPB, SED abs= 2 rel= 3 th=0.2

modification of calibration measurement setups like AS Cal. Event windows already set to higher values than above are not updated Event windows already set to zero are not updated to prevent to prevent modification of measurement setups like external vibration. Use -d <database> for other databases than the standard database. Use -f to avoid any confirmation questions.

====== FIX-FSA ================================================================

Usage: fix-fsa Disable and delete all FSA alarms and measurements Use -d <database> for other databases than the standard database Use -f to force deletion overriding all questions asked

====== FIX-HARMONIC-EVENT =====================================================

Usage: fix-harmonic-event Update event window configuration of harmonics to match 2.6.3 Use -d <database> for other databases than the standard database

====== FIX-HEARTBEAT ==========================================================

Usage: fix-heartbeat Check heart beat for all SPU's in database and correct problems found. Use -d <database> for other databases than the standard database Use -f to force execution without any confirmation questions

====== FIX-IAD ================================================================

Usage: fix-iad <No-tacho-state> [machine] ... Update IAD references for OTA, scalar, signature and spectral band. Specify the no tacho state for correct IAD on spectral band. When no machines are specified all machines are updated. Use -d <database> for other databases than the standard database Use -f to force execution without any confirmation questions

====== FIX-OVERLAP ============================================================

Usage: fix-overlap Set Overlap for FFT to 0% Use -d <database> for other databases than the standard database Use -o <overlap> to set overlap to a value 25%, 50% or 75% Use -t to update only transient FFTs (meas names must end with TRT)

====== FIX-PHMARK-ORBIT =======================================================

Usage: fix-phmark-orbit [from] [to] Correct phmark for orbit to value from data Use -d <database> for other databases than the standard database Use -v for verbose output From/to must use the format yyyy-mm-dd hh:mm

====== FIX-PHMARK =============================================================

Usage: fix-phmark Update phmark definition in SignatureValueTable and correct phmark values for orbit by examining actual orbit data. Use -d <database> for other databases than the standard database Use -f to force execution without any confirmation questions

====== FIX-SCL-SCALARREF ======================================================

Usage: fix-scl-scalarref Setting UseInSCL = 0, scalarDCRef = null in ScalarTable if the measurement is not under MachineComponenent of type Radial Journal Bearing (6) Removing the measurement from sclAlarmTable if any Use -d <database> for other databases than the standard database

====== FIX-SERVERTABLEPORT ====================================================

Usage: fix-servertablePort Changes type of Port column in ServerTable Use -d <database> for other databases than the standard database

====== FIX-SIGNATURE-ALARM-LEVELS =============================================

Usage: fix-signature-alarm-levels Lists signature alarm levels Use -d <database> for other databases than the standard database Use -s <file> to set alarm levels to contents of file The file must have the same format as the list

====== FIX-SIGNATURE-BASELINE-OTA-REF =========================================

Usage: fix-signature-baseline-ota-ref Set baselineSet flag to 0 if referenceSignature does not exist. Set Code2 = null if referenceSignature does not exist. Set Code2 = code for OTA if referenceSignature exists. Use -d <database> for other databases than the standard database Use -f to avoid any confirmation questions.

====== FIX-SIGNATURE-BASELINE =================================================

Usage: fix-signature-baseline Set baselineSet flag to 0 if referenceSignature does not exist. Use -d <database> for other databases than the standard database Use -f to avoid any confirmation questions.

====== FIX-SMD ================================================================

Usage: fix-smd Correct functiontype in measurementTable. Correct typeR in scalaralarmtable. Use -d <database> for other databases than the standard database Use -f to avoid any confirmation questions.

====== FIX-THRESHOLD ==========================================================

Usage: fix-threshold Set thresholds to 2 x absolute event window for following measurements:

Overall, Smax, Sm and Spp, OTA 1x and 2x

The threshold of the remaining scalars and OTAs are set to 0

Use -d <database> for other databases than the standard database. Use -f to avoid any confirmation questions.

====== FIX-TRANSDUCER =========================================================

Usage: fix-transducer Update transducer status based on enable and MOS flag: Disabled -> Not Connected Enabled without MOS -> Connected Enabled with MOS -> Connected with calibration pending Update transducer status based on enable and MOS flag: Use -d <database> for other databases than the standard database. Use -f to avoid any confirmation questions.

====== FIX-UNIT ===============================================================

Usage: fix-unit Update unit and unit conversion tables Use -d <database> for other databases than the standard database. Use -f to avoid any confirmation questions.

====== FIX-USEASTACHO =========================================================

Usage: fix-useastacho Changes type of Port column in ServerTable Use -d <database> for other databases than the standard database

====== FIX-VALUE-CODE =========================================================

Usage: fix-value-code compared-code-list Rename codes in data tables according to compared-code-list Use database-code-list and compare-code-list to make compared-code-list Use -d <database> for other databases than the standard database Use -u option to perform update Use compare-code-list > file to make compared-list

====== FIX-WARNING-LEVELS =====================================================

Usage: fix-warning-levels Change sign of negative relative warning limits Use -d <database> for other databases than the standard database

====== FTPCHECKPLANT ==========================================================

Usage: ftpcheckplant -d <minutes> Pull files from FTP server, check reports and mail abnormalies every <minutes>. ISDN plants will not be contacted between 8 and 20.

ftpcheckplant must be configured before it can be used: ftpcheckplant -c

Typical configuration on Support computer for project: General: Name: <project> IP Address: 10.10.1.7 Login: <contact rovsing> Password: <contact rovsing> Source: C:\Work\ftproot\Transfer\<project> Destination: P:\<project>\Transfer Check Delete file

E-mail system: E-mail Administrator: [email protected] E-mail account: <contact rovsing> E-mail password: <contact rovsing> E-mail SMTP: 10.10.1.1

General Machine Alarming: Alert threshold: 10 -- machine with more alerts will generate e-mail Alarm threshold: 0 -- machine with more alarms will generate e-mail System threshold: 0 -- machine with more system warnings will generate e-mail State threshold: 5 -- machine with steady state duration less than 5 minutes will generate e-mail

Enter machines in machine list to deviate from these defaults: Machine: <machine code as it appears in machine report> State events: 50 -- machine with more state changes will generate e-mail Steady scalar: 500 -- machine with more steady scalar events will generate e-mail Steady signature: 50 -- machine with more steady signature events will generate e-mail Transient scalar: 5000 -- machine with more transient scalar events will generate e-mail Transient signature: 500 -- machine with more transient signature events will generate e-mail

Machine report settings: Name file: machine-report E-mail: <project manager> Destination: P:\<project>\Transfer

Info report settings: Name file: info E-mail: <project manager>

Destination: P:\<project>\Transfer Parameters in info report marked alert or ALARM will generate e-mail. The alarm status of the parameter is stored too avoid reporting the same alarm twice

TraceAD report settings: Name file: traceAD E-mail: <project manager> Destination: P:\<project>\Transfer will generate e-mails for abnormalies in traceAD

Alarm report is controlled by the mailreport settings on-site. Provided files prmc.conf and prmc.zip are present in the transfer folder the alarm report will be mailed according to the info in prmc.conf file.

To edit the list of steady states use ftpcheckplant -s Add one line for each steady state

====== FTPPULL ================================================================

Usage: ftppull Pull files from FTP server.

ftppull can also be used to fetch new archives every <minutes>: ftppull -d <minutes>

ftppull must be configured before it can be used: ftppull -c

Typical configuration on OPENpredictor servers: Name: <project> IP Address: 85.235.226.11 Login: <project> Password: <contact rovsing> Source: Updates Destination: C:\OPENpredictor\ftp\Updates Check Delete file

Special configuration on replicate servers: Name: <project> IP Address: <customer ftp server> Login: <customer login> Password: <customer password> Source: <project> Destination: C:\OPENpredictor\Archive\<project> Check Delete file unless using several replicate servers Additional projects are configured in the same way.

====== FTPPUSH ================================================================

Usage: ftppush Push all files in the transfer folder to FTP server.

ftppush must be configured before it can be used: ftppush -c

Typical configuration on OPENpredictor servers: Name: <project> IP Address: 85.235.226.11 Login: <project> Password: <contact rovsing> Source: C:\OPENpredictor\ftp\Transfer Destination: Transfer Delete files

ftppush can also be used to copy new archives every <minutes>: ftppush -d <minutes>

The configuration should then contain all projects to be pushed: Name: <project> IP Address: <customer ftp server> Login: <customer login> Password: <customer password> Source: P:\<project name>\Transfer Destination: <project> Don't delete files

====== GET-IP =================================================================

Usage: get-ip Display primary ip address of this computer

====== GREP ===================================================================

Unknown option: ?usage: grep.bat [flags] [files]

Standard grep options:i case insensitiven number linesc give count of lines matchingC ditto, but >1 match per line possiblew word boundaries onlys silent modex exact matches onlyv invert search sense (lines that DON'T match)h hide filenamese expression (for exprs beginning with -)f file with expressionsl list filenames matchingF search for fixed strings (disable regular expressions)

Specials:

1 1 match per fileH highlight matchesu underline matchesr recursive on directories or dot if nonet process directories in `ls -t` orderp paragraph mode (default: line mode)P ditto, but specify separator, e.g. -P '%%\n'a all files, not just plain text filesq quiet about failed file and dir opensT trace files as opened

May use a TCGREP environment variable to set default options.

====== GT8B-PROCESS-DATA ======================================================

Usage: gt8b-process-data <tag>... Print process data from GT8B Process Control Database "GT8BPD" must be defined as ODBC data source Use -h option to skip header Use -r option to use easy human readable float format Use -d option to look up code and tdx in OPENpredictor database From/to must use the format yyyy-mm-dd hh:mm

====== HARMONIC-CLEAR-DUPLICATES ==============================================

Usage: harmonic-clear-duplicates Delete redundant harmonic setups. Use -d <database> for other databases than the standard database

====== HB-CHECK ===============================================================

Usage: hb-check <SPU> Check heart beat of SPU and report problems. Can be used when changing IP address of SPU to merge previous and present heart beat (HB).

The following checks are performed: - Chronological order of HB timestamps - False loss of HB where SPU is up again in less than 5 minutes - Redundant HB - Missing HB where state/tacho data are found (only option -c)

Use -c to perform cross check between HB and all state/tacho from SPU Use -u to update the HB fixing all reported problems Data Server must be stopped during this command. Use -f to force update skipping any confirmation questions Use -s to be silent about heart beat problems found Use -i <ip-address> to include HB from second ip address in check

To see the heart beat you can use: database2rdm -arc dau:<ip-address> | rdm-plot | usort -um

====== HEAD ===================================================================

head.bat (Perl bin utils) 1head.bat [-n count] [files ...]

====== HOUR ===================================================================

Usage: hour <hour> <command> Execute command provided the hour equals present time

====== HP-TRANSFER ============================================================

Usage: hp-transfer <reg>[-reg] Transfer measurement result for register <reg> from HP 3560A Dynamic Signal Analyzer and display data in RDM format. E.g.

hp-transfer -t 234 1-25

will transfer registers 1 through 25 from HP to the database as events for the measurement with tdx 234.

Use -t <tdx> or -c <code> to transfer data directly to database Use -a <seconds> to adjust the time stamps Use -r <rpm> to specify rpm value for data Use -p <number> to specify COM port Use -y <factor> to rescale the Y values from the HP Use -o <file> to output data to binary files suitable for use with HP Utility commands. Both register number and .dat will be added to the filename. E.g. test becomes test-1.dat.

====== IMPORT-LIST ============================================================

Usage: import-list [to] List import parameters in configuration for import to Excel

import-list -v > importlist.csv


====== INFO-HD-FREE ===========================================================

Usage: info-hd-free.bat Display MB free space on harddisk Use -d <drive> specifying drive letter

====== INFO-UPDATE ============================================================

Usage: info-update Update all server source measurements for the machine named "Info" with the results of their info commands as found in their descriptions. Use the Configurer to import the Info.dtd sample machine in your configuration and tailor the measurements to match your needs. An info command is a program that prints a number to stdout. The first number encountered will be used as the result of the measurement. The following descriptions can be used instead of an info command: VALUE:dbsize - size of standard database in MB VALUE:dbsizepc - database size in procent of maximum size VALUE:dbfree - free database space in MB VALUE:dbfreepc - free space in procent of maximum database size VALUE:dbifree - free index space in MB VALUE:dbifreepc - free index space in procent of maximum index size Up-to-date trends of info measurements can be ensured by using the AT command to run info-update daily: at 01:00 /e:m,t,w,th,f,s,su c:\openpredictor\service\info-update.bat Use -d <database> for other databases than the standard database

====== INSQL-INFO =============================================================

Usage: insql-info [table] Query Industrial SQL Server for table info or when. table is specified what is in that table. Use -d for extensive debug info.

====== LANGUAGE ===============================================================

Usage: language Display language setting language -s [da|de|en|es|it|pt|ru|sv] Use -s option to set OPENpredictor language setting Use -d <database> for other databases than the standard database

====== LOG-SHOW ===============================================================

Usage: log-show <filter> [ <file> ] Searches the ERRORLOG for entries matching the filter Use -n to launch Notepad with the entire User Interface log Use -c option to display entries from Configuration Server on the fly log-show -c

Use -m option to display entries from Modbus on the fly log-show -m

Use -p option to display entries from PI on the fly log-show -p

Use -h to limit display of entries to last hour Use -d to limit display of entries to last day Use -w to limit display of entries to last week

====== MACHINE2CODES ==========================================================

Usage: machine2codes <machine> Display list of measurement codes for machine The format of the list is suitable for SQL Use -p to include not present measurements in the list Use -t to list tdx instead of code Use -d <database> for other databases than the standard database

====== MAILREPORT =============================================================

Usage: mailreport Prepare alarm report in html ready for mailing. The report covers the period from the previous alarm report and up to now and contains: - Alarm history. - List of states changes for machines had alarms. - For each transducer in alarm these plots are shown: - Measurement causing the alarm. (Scalar/OTA trend/Signature) with alarm limits - Auto spectrum - if present - CPB - if present

Will generate two files in current folder provided alarms are found. The files are prmc.zip and prmc.conf.

mailreport can be generated automatically by updating the service-jobs.txt file controlling the service jobs running every night.

Typical configuration when sending report via checkplant: Plant Name: Auto Mail Server: 10.0.4.1 Mail User: <empty> Mail User Password: <empty> Alarm Report Config: Select the alarms to include in the report User: Admin Name Data Selection: Alarm report Email: <recipient>

No additional settings are needed for checkplant.

Typical configuration when using plant mail server: Plant Name: Auto Mail Server: <ip-of-customer-mail-server> Mail User: <sender-mail-account> Mail User Password: <sender-mail-password> Alarm Report Confige: Select the alarms to include in the report User: Admin Name Data Selection: Alarm report Email: <recipient> Use -p <path> to specify a different location for prmc files

mailreport must be configured before it can be used. Use: mailreport -c to launch configuration window.

====== MANUAL =================================================================

Usage: manual <machine> on|off Switch manual measurement mode for machine on/off.

Use -d <database> for other databases than the standard database.

Note: Configuration must contain measurement from FI server source containing the words switch and manual in its code.

====== MATH ===================================================================

Usage: math -m <list> [[from] to] <expression> Perform calculation on event and output result in RDM format. The expression is calculated each time an event occurs for one of the expression references. The number of resulting events will equal the combined total events with different timestamps among the references.

Use -m <master> to limit the resulting events to those with timestamps equal to the existing events of the master reference. The number of resulting events will equal the number of existing events for the master references and will have unchanged timestamps.

Expression follow the same rules as an SPU calculated expression, with the following exceptions:

- expression references can be any of: filename of RDM file #<code># M<tdx> M0 -- references the current master reference - only support for the following operators: +, -, * and / - only support for the following functions: None - expression arguments must be separated by space - nested expressions are not supported

Use -m <list> to specify multiple master references. Each master

reference must be separated by colon ":"

Multiple master references can be used to generate new events for each master reference in turn through the use of M0 expression references.

Master references can be any of: filename of RDM file -- Add RDM file to list #<code># -- Add measurement to list M<tdx> -- Add measurement to list #<transducer># -- Add all measurements on transducer to list -M<tdx> -- Removes reference from list -#<code># -- Removes reference from list

E.g. to correct the events of all measurements made on a tranducer to another sensitivity: math -ue"#MAD CY001#" "M0 / 0.98"

Use -u to replace all master reference events in the database with the resulting events Use -o <reference> to store result directly Use -e <file> to read expression from file Use -w to use event windows from configuration for master references Use -r to use easy human readable float format Use -d <database> for other databases than the standard database From/to must use the format yyyy-mm-dd hh:mm or yyyy-mm-dd hh:mm:ss

====== MEAS-BACKUP ============================================================

Usage: meas-backup <filter> [filter] <file> Backup measurement configuration of measurements matching filter.

Wildcards: % match any string ? match single character


====== MEAS-RESTORE ===========================================================

Usage: meas-restore <file> Add measurements from measurement configuration backup. Use -d <database> for other databases than the standard database

====== MEASURE ================================================================

Usage: measure <tdx> ... Perform measurement in SPU and generate event. Use -d <database> for other databases than the standard database

====== MFL-BACKUP =============================================================

Usage: mfl-backup file Backup MFL tables to file. Date is added automatically to file name Use -d <database> for other databases than the standard database

====== MFL-UPDATE =============================================================

Usage: mfl-update Update MFL tables to current version.

mfl-update [version|file] Update MFL tables to specific version or .dmp file.


Note: Please ensure that your present AD configuration is compatible with the version of the MFL tables you are restoring. Failing to do so may interrupt AD monitoring.

====== MIMIC-BACKUP ===========================================================

Usage: mimic-backup file Backup MIMIC tables to file. Date is added automatically to file name Use -d <database> for other databases than the standard database

====== MIMIC-LINKS ============================================================

Usage: mimic-links <mimic> <replace> <with> Update mimic links on mimic by replacing part of name E.g. to copy a mimic for machine 06 MKD to the identical machine machine 07 MKD:

Use mimic editor save as to make copy of 06 mimic mimic-links 07 06 07


====== MIMIC-MEASUREMENTS =====================================================

Usage: mimic-measurements <mimic> <replace> <with> Update measurement links on mimic by replacing part of code E.g. to copy a mimic for machine 06 MKD to the identical machine machine 07 MKD:

Use mimic editor save as to make copy of 06 mimic mimic-measurements 07 06 07


====== MIMIC-RESTORE ==========================================================

Usage: mimic-restore <file> Restore MIMIC tables from .dmp file.

Use -a to add mimic data instead of replacing existing tables Use -d <database> for other databases than the standard database

====== MODBUS-CONFIG-CONVERT ==================================================

Usage: modbus-config-convert <Modbus-file> Convert modbus-file in format DNIPRO1.0 to RD2.0.

====== MODBUS-CONFIG-REVERSE ==================================================

Usage: modbus-config-reverse <modbus-file> Reverse engineer Modbus configuration file ready for modbus-config


====== MODBUS-CONFIG-UPDATE ===================================================

Usage: modbus-config-update [Modbus-file] Convert modbus-file in format RD2.0 to RD3.0. Use -d <database> for other databases than the standard database

====== MODBUS-CONFIG ==========================================================

Usage: modbus-config <SPU> <Modbus-file> Displays modbus-config. SPU name is case sensitive. Use -d <database> for other databases than the standard database

====== MODBUS-LIST ============================================================

Usage: modbus-list [to] List modbus parameters in configuration for import to Excel

modbus-list -v > modbuslist.csv

Use -a to include alarm settings of Modbus measurements Use -v to include last value during last day of each parameter Use -h to search last hour for value Use -w to search last week for value Use -m to search last month for value Use -d <database> for other databases than the standard database

====== MODBUS-TEST-VALUE ======================================================

Usage: modbus-test-value -i <ip-address> <tdx> <value> Replace/add value for register/coil in modbus-n.n.n.n-test-data.txt

modbus-test-value -i <ip-address> -r <register> <value> Replace/add value for register in modbus-n.n.n.n-test-data.txt

modbus-test-value -i <ip-address> -c <coil> <value> Replace/add value for coil in modbus-n.n.n.n-test-data.txt

====== MODBUS-TEST ============================================================

Usage: modbus-test <SPU ip address or Modbus-config-file> [reg[-reg] [value]]

Reads Modbus configuration file and operates as slave or master sending simulated data to the SPU until you press CTRL-C.

Whether modbus-test will operate as master or slave is controlled by the setting in the modbus-config file. E.g. when SPU is set to operate as master modbus-test will operate as slave.

The values transmitted will be values between low and high as specified in the modbus-config file.

The following information only applies when the modbus-test operates as master:

By default a function code 16 query containing values for all registers is transmitted on COM1 every 60 seconds.

Specify register to transmit a single query with just one register. When specifying a register you can also specify the value.

The options below are available when running as master: Use -o<file> to output values to RDM file. Use -d<seconds> to specify delay between queries to SPU Use -f1 to request alert status from SPU using func code 01 Use -f2 to request danger status from SPU using func code 02 Use -f3 to request values from SPU using function code 03 Use -f15 to send coil data to SPU using function code 15 Use -f16 to send register data to SPU using function code 16 Use -D<database> for other databases than the standard database. Only used in combination with option -o.

To test single register: modbus-test 192.168.0.2 1 50

To send registers 20 through 34: modbus-test -f16 -r 192.168.0.2 20-32

To send DNIPRO function code 03 query: modbus-test -f3 192.168.0.2 1 35

To test all modbus measurements with 11 queries with values from low to high on COM2:

modbus-test -c2 -l1 -s10 -d1 192.168.0.2

To run modbus-test as master and query every 10 seconds: modbus-test -mMASTER -d10 192.168.0.2

Available options for both slave and master: Use -c<number> to specify COM port Use -s<number> to specify number of steps between low and high Use -l<number> to specify number of low high loops Use -r to repeat query to SPU. Default when no parameters are given. Use -q to ask user confirmation before closing down. Use -t to use file controlled test data. Use -T<timeout> to set timeout in ms. Default is 1000 ms.. Use -h to display hex value of registers in query 16 Use -m<mode> to operate modbus-test in special mode: MASTER modbus-test will run as master and use queries defined in modbus-config file. AB Allan Bradley PLC5 simulation using two DL3500s.

====== MSSQL-INFO =============================================================

Usage: mssql-info [table] Query Microsoft SQL Server for table info or when. table is specified what is in that table. Use -d for extensive debug info.

====== NAME ===================================================================

Usage: name <tdx> Display code of tdx Use -d <database> for other databases than the standard database

====== NAME2TDX ===============================================================

Usage: name2tdx <code> Display tdx of code or -1 if not found Use -d <database> for other databases than the standard database

====== OFFLINE-INIT ===========================================================

Usage: offline-init [from] <machine> Initialise offline machine that only use default state. Use -d <database> for other databases than the standard database From must use the format yyyy-mm-dd hh:mm

====== OP-SERVICES ============================================================

Usage: op-services List status of OPENpredictor services

op-services can be used to perform the following operations: op-services start -- start all services op-services stop -- stop all services op-services start basic -- start all basic services op-services stop datawatchdog -- stop watchdog and data server op-services stop <server> -- stop service. (Watchdog will restart service automatically). op-services start <server> -- start service op-services install -- install all non optional servers op-services install <server> -- install server op-services remove -- remove all services


op-services operates on the following services: ftp MSFtpsvc (start/stop) rpc ONC RPC PortMapper (basic) time OP Time Server (basic) log OP Log Server (basic) config OP Configuration Server (basic) data OP Data Server ads OP AD Scheduler (optional) base OP Baseline Server (optional) calc OP Calculation Server (optional) file OP File Import Server (optional) pi OP Pi Server (optional) opc OP OPC Server (optional) perform OP Performance Server (optional) fatigue OP Fatigue Server (optional) xtc OP XTC Server (optional) relay OP Relay Server (optional) oracle OracleServiceRDOPO10G (status only) watchdog OP WatchDog

====== OTA-OVERALL ============================================================

Usage: ota-overall ota-overall <show-analysis report> Display measurements where OTA 1x is more than 1.25 times Overall

====== PACK ===================================================================

Usage: pack [file]... Pack files and place them in the transfer folder in one zip file Use -l to pack the current ERRORLOG Use -a to pack all ERRORLOGs Use -u to pack User Interface logs Use -f to force overwrite in case zip file already exists

====== PARSE-RELAY-LOG ========================================================

Usage: parse-relay-log parse-relay-log <file> [machine] Convert relay-server debug file to CSV file Use -s option to see statistical distribution of delays Use -r option to output in RDM format

Note: To generate debug file for ØSB relay server: - Stop Watchdog: op-services stop watchdog - Stop Relay Server: op-services stop relay - Prepare log: server-relay-osb.pl -D SPU1 2> relay-log.txt - Stop Relay Server: CTRL+C - Restart Relay Server: op-services start relay - Restart Watchdog: op-services start watchdog

====== PERFORMANCE-REPORT =====================================================

Usage: performance-report [machine] ... Display performance report for machines in their current state.

The values displayed in the report are: DM memory used as normalised value. PM memory used as normalised value. Clock cycles used as normalised value. priority in seconds (only in verbose mode). Normalised values are normalised to 1 corresponding to the full capacity of one DSP 1000f the time. The total number of DSP's required do not consider overhead and.

Use -v for verbose output with info for each measurement.

Use -c to get output as comma seperated file format

Note: As a rule of thumb the number of DSPs should be multiplied by 2.

====== PI-CONFIG ==============================================================

Usage: pi-config Display PI setup file. Use this as a draft for the pisetup.txt Use -d <database> for other databases than the standard database Use -e <extension> to add extension to all tags, e.g. .PV Use -n use measurement name as tag Use -w <word-number> to indicate position of machine name in code This is used to group the PI parameters for each machine. E.g. pi-config -w 2

====== PI-INFO ================================================================

Usage: pi-info [table] Query OSI PI Server for table info or when. table is specified what is in that table. Use -d for extensive debug info.

====== PI-LIST ================================================================

Usage: pi-list [to] List PI parameters in configuration for import to Excel

pi-list -v > pilist.csv


====== PI-TAGS-NOT-FOUND ======================================================

Usage: pi-tags-not-found [error log] Search log file for reports about PI tags not found

====== PI-TEST-VALUE ==========================================================

Usage: pi-test-value <tdx> <value> Replace value in pitestdata.txt for tdx.

====== PI-TESTDATA ============================================================

Usage: pi-testdata [file] Read pisetup.txt and outputs pi test data with baseline as initial value. To produce pitestdata.txt: pi-testdata > C:\OPENpredictor\Data\pitestdata.txt


====== PI-UPDATE ==============================================================

Usage: pi-update <database> <pi-setup-file> List pi-setup file with new tdxs. The old tdx is found in database, the corresponding name located in the current database and the current tdx is then used instead of the old one. Use pi-update when reconfiguring a system and the pisetup have to be updated since new tdx numbers have been assigned to the measurements. Use -d <database> for other databases than the standard database

====== PI-VALUE ===============================================================

Usage: pi-value <tdx> ... Get value from PI Use -r option to repeat command Use -d <database> for other databases than the standard database

====== PI =====================================================================

Usage: pi [tag] ... Test program that send specific query to OSI PI Server. Use -u user for specifying username. Default is pidemo. Use -p passwd for specifying password. Default is no password. Use -D for extensive debug info.

====== PING-ROVSING ===========================================================

Usage: ping-rovsing Repeatedly pings ROVSING Dynamics support ISDN router. Used to establish WAN connection to ROVSING Dynamics support. Use -i <ip-address> to ping other destination than ROVSING.

====== PLOT-LAST ==============================================================

Usage: plot-last <tdx> Show last value/peak for measurement within last 24 hour period Use -d <database> for other databases than the standard database Use -c <code> to specify code rather than tdx Use -h to display data for last hour Use -w to display data for last week Use -m to display data for last month Use -i to include invalid data causing range errors plot-last -c <code>

====== PM-CONFIG-UPDATE =======================================================

Usage: pm-config-update <old database> <variables-file> Print performance monitoring variables conf file with updated tdx info.

The principle of operation is as follows: Use existing tdx to locate measurement tag in old database. Modify tag according to options o/n. Locate tdx in new database. Print updated variables conf file.

Use -o <old string> to replace this string. -n <new string> to specify replacement string. Only strings matching beginning of tag will be modified.

-d <database> for other databases than the standard database

====== RDM-CHANGE-RATE ========================================================

Usage: rdm-change-rate -r <value>:<seconds> <RDM-file> Show events exceeding allowed change rate. The change rate is specified as a maximum value of change over a specific period of time.

E.g. rdm-change-rate -r 200:10 tacho.rdm would list tacho values that has changed more than 200 over the last 10 seconds.

Use option -c to use simple comparison as performed in SPU instead of linear regression. Use option -x to replace event values with change rate.

For seconds without events the previous value is used. The change rate is calculated for the period using linear regression.

====== RDM-DELTATIME ==========================================================

Usage: rdm-deltatime <RDM-file> Display time differences between events Use -c <code> option to display time difference between measurement with ¤de> and measurement with a different code Use -d option to only display time difference between different codes Use -s option to see summary only with min, max and average

====== RDM-EVENT-WINDOW =======================================================

Usage: rdm-event-window <RDM-file> Reduce number of events according to absolute event window

Use -w <absolute-event-window> to set absolute event window Use -x <relative-event-window> to set relative event window Use -1 to examine 1x phase Use -2 to examine 2x phase Use -b to list events in brief format

The following command counts the number of events in harm.rdm after applying an absolute event window of 10 degrees to 1x phase:

rdm-event-window -1 -w 10 harm.rdm | wc -l

The following command counts the number of events in tacho.rdm after applying an absolute window of 10 and a relative window of 1.01 (1%):

rdm-event-window -w 10 -x 1.01 tacho.rdm | wc -l

====== RDM-FILTER =============================================================

Usage: rdm-filter <ranges> <RDM-filter-file> <RDM-file> Filter second <RDM-file> according to defined ranges. A range can be defined in one of the following ways: 1 value must be equal. Range is [1;1] -2.3 value must be less or equal. Range is ]-oo;2.3] 4.5- value must be greater or equal. Range is [4.5;oo[ 6.7-8.9 value must be between. Range is [6.7;8.9] All ranges must be combined into one argument using colon as seperator: 1:-2.3:4.5-:6.7-8.9 There are no limits to the number of ranges that can be defined. When ranges overlap the last range used will be used if it match otherwise the first range that match will apply. E.g. 1-2:2-3:3-4.

Filter RDM file must be scalar. Gradient time is applied when filter data changes range.

Use -o <outputfile> option to save filter. Use -g <seconds> to define gradient in seconds. Use -x <seconds> to exclude first and last part of data in range after / before values outside defined ranges.

Subsequent rdm-filter commands can then use the saved filter. E.g. rdm-filter 1 myfilter.rdm <RDM-file>

====== RDM-MATH ===============================================================

Usage: rdm-math <RDM-file> Display result of math operation on events in RDM file Use -m option to see minimum values Use -a option to see average Use -x option to see maximum values The RDM file should only contain events from one measurement

====== RDM-PLOT ===============================================================

Usage: rdm-plot [ RDM file ] Display plot for measurement data from stdin An RDM file can also be specified rdm-plot <RDM-file>

====== RDM-RESAMPLE ===========================================================

Usage: rdm-resample <rdm-file> Resample profile signature from RDM file. The default resampling is 300 samples between lowest and highest rpm found in the data.

Use -l <rpm> to use different low rpm Use -h <rpm> to use different high rpm Use -n <number> to use different number of samples Use -r option to use easy human readable float format

rdm-resample can be used together with reference2rdm and rdm2reference to modify an existing profile signature reference.

Example: To resample the profile signature reference in machine state Run-up (state index 3) for 1x amplitude of a harmonic measurement with the code "MAD CY001 Harm" do the following:

reference2rdm -c "MAD CY001 Harm" -s 3 -h 1x > profile.rdm rdm-resample -l 100 -h 3000 -s 300 profile.rdm > newprofile.rdm rdm2reference -c "MAD CY001 Harm" -s 3 -h 1x -p newprofile.rdm

In OPENpredictor version 2.6.3 it is required to resample all profile signature references before they will work.

====== RDM-SHOW ===============================================================

Usage: rdm-show rdm-show [-h] [-l] [-b] <RDM-file> Shows brief info with only one line per event Use -h option to see header Use -l option to see last events shown in RDM format Use -lb option to see brief info for last events

====== RDM-SPIKES =============================================================

Usage: rdm-spikes <RDM-file> Filter signatures with spikes. (With Spp in orbit/time domain above the filter value)

Use -v <value> to specify spike level other than 100.

Use -o <over> to specify no of samples in rolling window over which the Spp will be calculated. E.g. -o 3 will require the spike to occur over any three samples in the measurement

rdm-spikes can be combined directly with database2rdm:

database2rdm -mc"MAD CY001 Orbit" | rdm-spikes -v20 -o3

====== RDM-SPLIT ==============================================================

Usage: rdm-split rdm-split <RDM-file> Split RDM file into a number of RDM files with 100 events per file The output filenames will be the input filename with a number attached Use -l <number> option for a different limit

====== RDM-STAT ===============================================================

Usage: rdm-stat <ranges> <RDM-file> Show statistics for each of the defined ranges. A range can be defined in one of the following ways: 1 value must be equal. Range is [1;1] -2.3 value must be less or equal. Range is ]-oo;2.3] 4.5- value must be greater or equal. Range is [4.5;oo[ 6.7-8.9 value must be between. Range is [6.7;8.9] All ranges must be combined into one argument using colon as seperator: 1:-2.3:4.5-:6.7-8.9 There are no limits to the number of ranges that can be defined. When ranges overlap the first range will apply. E.g. 1-2:2-3:3-4. rdm-stat only work with scalars.

====== RDM-STATE-RECALCULATE ==================================================

Usage: rdm-state-recalculate <load-file> <ranges> <state-file> <states> Recalculate state according to load ranges: - Non-operational states will appear unchanged after recalculation. - Adjectant operational state events will be deleted. - The first operational state event following a non-operational state will be replaced by a the recalculated state. - New events for the recalculated state will be inserted according to the state recalculation. This will continue until the next non-operational event appears.

- Hysteresis can be used by specifying overlapping ranges. - Gradient state are supported in several forms: unconditional, based on previous state, based on change rate of load input.

<ranges> is a list of load ranges, separated by ":" A range can be defined in one of the following ways: -2.3 load must be less or equal. Range is ]-oo;2.3] 4 load must be equal. Range is [4;4] 4-8.9 load must be between. Range is [4;8.9] 8.9- load must be greater or equal. Range is [8.9;oo[ All ranges must be combined into one argument using colon as seperator: -2.3:4:4-8.9:8.9- There are no limits to the number of ranges that can be defined. When ranges overlap the last range used will be used if it match otherwise the first range that match will apply. E.g. 1-2:2-3:3-4.

<states> is a list of state definitions with three main parts: <unknown>:<range mappings>:<additional states>

<unknown> is the state to be used when load is unknown

<range mappings> contains one definition for each range seperated by ":". Each definition can be specified in one of the following ways: s map to state s. g-s map to state g during gradient time, then to s. g-s~x,y,z map to state g during gradient time provided previous state was either x, y or z, then to s.

<additional states> list of additional operational states to be recalculated, seperated by ":".

E.g. 3:3:4-5:4-6~2,11:7:8:9:10 means that Unknown load is mapped to state index 3. Range -2.3 is mapped to state index 3. Range 4 is mapped to 4 as gradient and 5 when steady. Range 4-8.9 is mapped to 4 as gradient when previous state was 2 or 11 and 6 when steady. Range 8.9- is mapped to 7 States 8, 9 and 10 are additional operational states to include in the recalculation

Use -g <seconds> to define a gradient. Gradient time is applied whenever the load reaches a new operational range. The use of gradient state is controlled by the <states> definition. Its use can be limited to certain states as well as based on previous state.

Use -G <seconds> same as -g but gradient state will not be overruled by operational states not using gradient state

Use -r <value>:<seconds> to trigger gradient state whenever the load change rate exceeds the specified change rate. The change rate is specified as a maximum value of change over a specific period of time. E.g. -r 200:10 trigger a gradient when the load has changed more than 200 over the last 10 seconds.

The change rate is calculated using linear regression. Use -u <unknown> to force the load value to unknown each time the state has this non-operational state index. This feature is needed for periods where there are large gaps in the load data since a value for unknown load never appear in the load file.

====== RDM-TIME ===============================================================

Usage: rdm-time rdm-time [-s] [-h hours] <RDM-file> Shows time between measured values Use -s on a RDM file containing a State to see the time at each State Use -h N to find periods longer than N hours without measurements Option -s overides option -h

====== RDM-TRANSLATE ==========================================================

Usage: rdm-translate <translate-file> <RDM-file> Translate values in RDM file according to translation file. The translation file must contain the values to be translated. One translation on each line: value <from-value> <to-value> tdx <from-tdx> <to-tdx> rpm <from-rpm> <to-rpm> code [<from-code>] [<to-code>] prefix [<from-prefix>] [<to-prefix>] skip [<code>] Empty lines and lines beginning with # are ignored.

Prefix will replace first part of code, leaving remaining code unchanged. Only values found in the translation file are translated while other values maintain their original value. rdm-translate only work with scalar values.

====== RDM2BASELINES ==========================================================

Usage: rdm2baselines [ filter ] Update baselines with values from RDM files that match filter.

RDM file name convention must be as follows: <tdx>-s-<state index>.rdm for scalars <tdx>-h-<state index>.rdm for harmonics <tdx>-z-<state index>.rdm for signatures

Use -d for other databases than the standard database Use -b <directory> for other directory than the current

You can use show-analysis with option -b to create scalar and harmonic baseline RDM files.

====== RDM2CSV ================================================================

Usage: rdm2csv <RDM-file> Display event data in CSV format one event on each line. Useful for transferring RDM data to Excel. For Harmonics only 1x ampl is transferred. For Signatures only first column of float data are transferred. Use -r to include rpm value of measurement in CSV list. Use -h option to list harmonics as 1x, 1p, 2x, 2p, 3x, 3p, 4x, 4p.

====== RDM2DATABASE ===========================================================

Usage: rdm2database [date] <RDM-file> Use -c option to clear the data for all measurements that appear in the RDM file before transfering the RDM data. Use -d <database> for other databases than the standard database Use -p option to parse file without writting to database When date is specified all time stamps in the RDM file are moved so that the time stamp of the first event match the date specified

====== RDM2REFERENCE ==========================================================

Usage: rdm2reference -s <state> <rdm-file> Replace entry in referenceSignatureTable with reference inRDM format Use -d <database> for other databases than the standard database Use -c option to override code in RDM file Use -s <state number> option to specify specific state Use -p option for profile data Use -h option to specify type of harmonic (sub, res, 1x, 1p, etc.)

====== RDM2SQL ================================================================

Usage: rdm2sql <RDM-file> Display event data as SQL inserts one event on each line. Useful for transferring RDM to temporary database storage with direct. For Harmonics only 1x ampl is transferred. Signatures data are ignored. Use -h option to list harmonics as 1x, 1p, 2x, 2p, 3x, 3p, 4x, 4p.

====== REDUCE-ASDIAG ==========================================================

Usage: reduce-asdiag [from] [to] [machine] ... Delete AS diag events. Events already marked as reduced will not be deleted. Use -o <days> to only reduce events older than <days> Use -d <database> for other databases than the standard database Use -f to force reduction overriding all questions asked

From/to must use the format yyyy-mm-dd hh:mm

====== REDUCE-MEASUREMENT =====================================================

Usage: reduce-measurement <code> ... Reduce scalar measurement by deleting all completed BLOBs Use -d <database> for other databases than the standard database Use -f to force reduction overriding all questions asked

====== REDUCE-ORBIT ===========================================================

Usage: reduce-orbit [from] [to] [machine] ... Reduce number of orbit events stored in the database and mark kept events as reduced. Events already marked as reduced will not be reduced. Use -o <days> to only reduce events older than <days> Use -d <database> for other databases than the standard database Use -k <procent> to keep a different procentage than the default 10% Use -f to force reduction overriding all questions asked


====== REDUCE-SED =============================================================

Usage: reduce-sed [from] [to] [machine] ... Reduce number of SED events stored in the database and mark kept events as reduced. Events already marked as reduced will not be reduced. Use -o <days> to only reduce events older than <days> Use -d <database> for other databases than the standard database Use -k <procent> to keep a different procentage than the default 10% Use -f to force reduction overriding all questions asked


====== REFERENCE-CLEAR-DUPLICATES =============================================

Usage: reference-clear-duplicates Delete duplicate reference signature entries from database. Use -d <database> for other databases than the standard database

====== REFERENCE2RDM ==========================================================

Usage: reference2rdm <tdx> Print reference signatures for measurement in RDM format Use -d <database> for other databases than the standard database Use -c option to display reference for measurement reference2rdm -c <code> Use -s <state number> option to specify specific state Use -h option to specify type of harmonic (sub, res, 1x, 1p, etc.) Use -r option to use easy human readable float format

====== RENAME-FILES ===========================================================

Usage: rename-files <regular-expression-1> [regular-expression-2] Rename files all files in current folder by substituting regular expression 1 by regular expression 2 in filename.

Examples: rename-files ups Special -- replace ups by Special rename-files "^HKP" -- remove leading HKP rename-files "^" HKP -- add leading HKP rename-files "\.dat$" "\.rdm$" -- replace .dat by .rdm

Regular expression metacharacters: \ Quote the next metacharacter ^ Match the beginning of the line . Match any character (except newline) $ Match the end of the line | Alternation () Grouping [] Character class

Regular expression quantifiers: * Match 0 or more times + Match 1 or more times ? Match 1 or 0 times

{n} Match exactly n times {n,} Match at least n times {n,m} Match at least n but not more than m times

====== REPORT =================================================================

Usage: report [file] Show contents of file from reports folder. When several files match the file name specified the newest file is shown. When no file is specified the newest machine report is shown. Use -n to launch Notepad with copy of the entire file

====== RPCINFO ================================================================

rpcinfo: unknown option, -?Usage: rpcinfo [ -n portnum ] -u host program [ versnum [procnum]] rpcinfo [ -n portnum ] -t host program [ versnum [procnum]] rpcinfo -p [ host ] rpcinfo -b program versnum [procnum] rpcinfo -d program versnum

====== RPM-UPDATE =============================================================

Usage: rpm-update -r <rpm> [[from] to] <tdx>... Update rpm value of data specified. Only the specified measurements in the specified period are updated. Use list of tdx's or options -m to specify multiple measurements: rpm-update -r <rpm> <tdx>... rpm-update -r <rpm> -m <machine> When no period is specified all data are updated. Use -m <machine> to display data for all measurements on machine Use -r <rpm> to specify the new rpm value Use -d <database> for other databases than the standard database From/to must use the format yyyy-mm-dd hh:mm

====== RUSSIAN-UNITS ==========================================================

Usage: russian-units Update unit table to use Russian units with html codes Use -d <database> for other databases than the standard database

====== SELECT =================================================================

Usage: select <argument> ... Perform a SQL select command. Use -d <database> for other databases than the standard database.

====== SENDFTP ================================================================

Usage: sendftp Transfer all files in the transfer folder to FTP Server specified. sendftp must be configured before it can be used. Use: sendftp -c to launch configuration window.

====== SENDMAIL ===============================================================

Usage: sendmail -t <to> <file> Send content of file as e-mail to recepients. Use: -t <to> [;<to>] ... to recipients -c <to> [;<to>] ... cc recipients -s <subject> subject line of mail

====== SERVER-IP-ADDRESS ======================================================

Usage: server-ip-address <ip-address> Updates ip addresses in system table Use -d <database> for other databases than the standard database

====== SERVICE-DOCUMENTATION ==================================================

Usage: service-documentation Display full documentation for service commands To get a hardcopy of the full documentation use service-documentation > full-documentation.txt and print full-documentation.txt

====== SERVICE-INSTALL ========================================================

Usage: service-install <service> <command> [parameters ...] Add command as service. Use -r to remove service.

====== SERVICE-JOBS-LOG =======================================================

Usage: service-jobs-log Examine service-jobs-log and display duration or other info Use -b to examine backup of service job log instead Use -a to display duration of AdmSupervisor Use -r to display duration of reduction Use -s to display duration of show-analysis

====== SERVICE-JOBS ===========================================================

Usage: service-jobs Performs a number of service jobs: - use ftppull to retrieve updates from RD - executes all commands found in the update-jobs.txt file if found in the updates folder - executes all commands found in the service-jobs.txt file if found in the OPENpredictor\Commands folder - move any archive files to transfer folder - prepare show-info report and place it in transfer folder - prepare daily show-machine report and place it in transfer folder - prepare weekly show-machine report and place it in transfer folder - move AD trace to transfer folder - use ftppush to send files in transfer folder to RD

Note: A copy of the reports are placed in the reports folder and the reports placed in the transfer folder are zipped

Note: The service-jobs.txt file assumes the following format: - Blank lines and lines starting with # are ignored. - A command line may be preceded with an optional keyword: SYSTEM: Command to be executed in system root folder as if it was started by AT. STOP: Execution of remaining commands stops immediately - All other commands are started in the Transfer folder - A command may contain the following keywords: %DATE substituted with yyyy-mm-dd before executing command %TIME substituted with hh-mm before executing command %OPPATH substituted with path to OPENpredictor folder %TRANSFER substituted with path to Transfer folder %UPDATE substituted with path to Updates folder %PPC substituted with path to ppc folder used by SPU - The remaining command line is executed - When a command do not redirect its output it will automatically be redirectred to the service-jobs-log.txt file.

Examples of command lines in service-jobs.txt: reduce-orbit -f info-update SYSTEM: database-archive copy /y %UPDATE\new-service-command.bat %OPPATH\Service show-analysis -d BFPA > %TRANSFER\BFPA-report-%DATE.txt

Use -u <file> to test update jobs file only Use -p to show paths

To run service-jobs daily use the AT command: at 01:00 /e:m,t,w,th,f,s,su c:\openpredictor\service\service-jobs.bat

====== SERVICE-LOG ============================================================

Usage: service-log Display last 20 entries in service log.

service-log <argument1> [ argument2 [ argument3 ...] ] Combine the arguments into a common description, add it to service log and displays last five entries.

Use -u <user> to specify another user than the current user when adding an entry to the service log. Use -n to launch Notepad with the entire service log

====== SERVICE ================================================================

Usage: service [ filter [ filter ]] Display this text or those commands who match filters Use -f option to display full documentation for commands found Use service . to list all service commands To get a hardcopy of the full documentation use service -f . > full-documentation.txt and print full-documentation.txt Use -? option to get additional help for each of the commands

====== SHOW-ANALYSIS ==========================================================

Usage: show-analysis [[from] to] <machine> ... Analyse machine data for each state and display result. Results that meet one or more of these criteria are flagged with #: a. Event rate less than 0.3 e/h for scalars A. Zero events and max time in steady state more than 1 hour A. Zero events and max time in transient state more than 1 minute b. Event rate for scalar in steady state higher than 100 e/d B. Event rate for scalar in steady state higher than 1 e/m b. Event rate for signature in steady state higher than 10 e/d B. Event rate for signature in steady state higher than 1 e/h m. Value below zero M. Value NaN or missing harmonic q. Baseline outside min - max range r. Baseline less than Average / 2 s. Baseline larger than 2 x Average t. Transient signature measurement not measured t. Transient scalar measurement cover less than 90% of rpm span T. Transient scalar measurement cover less than 70% of rpm span Only enabled measurements are examined

The output of show-analysis can be redirected to a file, e.g.: show-analysis 2002-02-01 00:00 2002-03-01 00:00 > result.txt This is advantageous as it allows further processing of the output.

One way to examine the result is to summarise the flagged data: grep # result.txt Also the number of flags can be counted using, e.g. all B flags: grep "#b|#B" result.txt | wc -l

Use -d <database> for other databases than the standard database Use -b <directory> to create scalar and harmonic baseline RDM files based on avg. RDM file names will be <tdx>-h/s-<state index>.rdm Use -h to display data for last hour Use -w to display data for last week Use -m to display data for last month Use -s to analyse signatures only Use -a to list measurements used by Auto Diagnosis only Use -t to analyse trends only Use -l to show values in lag


====== SHOW-CONFIG ============================================================

Usage: show-config [ tdx ... ] Show configuration of specified measurements Entire configuration is shown when no measurements are specified. Use -d <database> for other databases than the standard database Use -c option to display configuration for any item show-config -c <code> Use -e option to display equipment only Use -m option to display configuration for machine show-config -m <machine-search-string> Use -t option to display configuration templates show-config -t

====== SHOW-INFO ==============================================================

Usage: show-info Display last measurements for the machine named "Info". Use -d <database> for other databases than the standard database

====== SHOW-LAST ==============================================================

Usage: show-last <tdx> Show last value/peak for measurement within last day Use -c <code> to specify code rather than tdx Use -h to display data for last hour Use -w to display data for last week Use -m to display data for last month Use -d to specify database other than standard database show-last -d <database> <tdx> show-last -c <code>

====== SHOW-MACHINE ===========================================================

Usage: show-machine [[from] to] <machine> ... Show machine overview with states, alarms and diagnoses for last day. Event totals sometimes shown (See note). In online mode the current value of measurements used in state calculation are shown. Use -d <database> for other databases than the standard database Use -h to display data for last hour Use -w to display data for last week Use -m to display data for last month Use -o for online mode with contact to SPU Use -q for quick online mode without alarms but with contact to SPU


Note: The event totals are only shown when a 24 hour report is requested and a show-analysis report named show-analysis-yyyy-mm-dd.txt is present in either the current folder or the transfer folder.

====== SHOW-PAD ===============================================================

Usage: show-pad [[from] to] [machine] ... Show one line overview of machine PAD statistics.

Use -d <database> for other databases than the standard database. Use -h to display data for last hour. Use -w to display data for last week. Use -m to display data for last month. Use -c to make comma seperated output day-by-day for all machines. The .csv file will be placed in the current folder. Use -v for verbose output listing individual PADs for each machine.

From/to must use the format yyyy-mm-dd.

Hint: Machines without AD enabled states are skipped. Only enabled AD measurements with at least one present transducer are included.

Sample output:PREDICTIVE AUTO DIAGNOSIS OVERVIEW 2005-01-31 23:59 - 2005-02-09 23:59

Machine name State AD Data PAD Min Average Max

MAD - Steam Turbine ............ 100% 100% 100% 28 0%(2) 83% 89%(26)MBD - Gas Turbine .............. 99% 100% 100% 26 0%(1) 87% 100%(3)MBJ - Start Motor .............. 0% 0% 0% 1 -% -% -%-------------------------------------------------------------------------------3 Machines 66% 67% 67% 55 0%(3) 85% 100%(3)

LEGEND:State = Percentage of time in state with AD enabled.AD = Percentage of AD intervals where machine was in AD enabled state.Data = Percentage of AD intervals where machine was in AD enabled state during entire interval and therefore data can be assumed to be present.PAD = Number of present enabled non-stealth PAD in the configuration.Min = Minimum percentage amongst all ADs of days with symptom values for

days where data are available. The number of ADs with min percentage is shown in parenthesis.Average = Average percentage of days with symptom values for days where data are available.Max = Maximum percentage amongst all ADs of days with symptom values for days where data are available. The number of ADs with max percentage is shown in parenthesis.

====== SHOW-STATE-STAT ========================================================

Usage: show-state-stat [from] [to] <machine> ... Show machine operational state statistics Use -d <database> for other databases than the standard database Use -h to display data for last hour Use -w to display data for last week Use -m to display data for last month


====== SHOW-STATISTICS ========================================================

Usage: show-statistics [from] [to] <machine> ... Show event statistic for measurements used by AD for last day Use -d <database> for other databases than the standard database Use -h to display data for last hour Use -w to display data for last week Use -m to display data for last month Use -a to list measurements used by Auto Diagnosis only Use -s to list short listed measurements used by Auto Diagnosis only


====== SHOW-WARNINGS ==========================================================

Usage: show-warnings [from [to] ] [ tdx ... ] Show alarms for specified measurements for last day. All alarms are shown when no measurements are specified. Use -d <database> for other databases than the standard database Use -c option to display alarms for measurement show-warnings -c <code> Use -m option to display alarms for machine show-warnings -m <machine-search-string> Use -h to display data for last hour Use -w to display data for last week


====== SIGNATURE-CLEAR-DUPLICATES =============================================

Usage: signature-clear-duplicates Delete redundant signature data. Use -d <database> for other databases than the standard database

====== SIGNATURE-SIZE =========================================================

Usage: signature-size [from [to]] List actual size of each signature long as well as estimated size Use -d <database> for other databases than the standard database Use -c to check actual vs. estimated and only list differences From/to must use the format yyyy-mm-dd hh:mm

====== SLEEP ==================================================================

Usage: sleep.bat <seconds> Sleep for <seconds> seconds

====== SOFTWARE ===============================================================

Usage: software Display version of OPENpredictor related software Use -s option to calculate CRC16 checksums

====== SPLIT ==================================================================

usage: split.bat -b byte_count[k|m] [file [prefix]] split.bat -l line_count[k|m] [file [prefix]] split.bat -p regexp [file [prefix]]

Output fixed-size pieces of INPUT to prefixaaa, prefixabb, ...; defaultprefix is 'x'. With no file, or when file is -, read standard input.

SIZE may have a multiplier suffix: k for 1024, m for 1024^2.

====== SPU-CONFIG =============================================================

Usage: spu-config <tdx> Display configuration as stored in SPU Use -d <database> for other databases than the standard database

====== SPU-CONFIGURE ==========================================================

Usage: spu-configure <spu> Configure SPU.

WARNING: Only works when no measurements have been deleted.

====== SPU-LIST ===============================================================

Usage: spu-list List SPUs defined in database. Use -d <database> for other databases than the standard database

====== SPU-LOAD ===============================================================

Usage: spu-load <spu> [DSP] Show jobs distribution of DSPs in SPU.

Use -v for verbose output with tdx and box info.

DSP <dsp>: <meas>..<tdx>[box] <meas>..<tdx>[box]

When DSP is specified detailled info for that DSP is displayed:

[box] <state><priority><active> <size>/<slot>/<active> (idle) [box] <state><priority><active> <size>/<slot>/<active> (idle)

Legend: <priority> : stopped(-), low(L), high(H), unknown(?) <active> : active(a), inactive(i)

Use -a to get detailled info from all DSPs (slow)

Hint: Detailled DSP info is stored in a log file as received from SPU in the file spu-load-log.txt

Note: Differences between measurements on DSP and detailled DSP info are normal due to the delays in obtaining the detailled info.

====== SPU-LOG ================================================================

Usage: spu-log [ <file> ] Searches the ERRORLOG for restarts of the SPU

Use -h to limit search to last hour Use -d to limit search to last day Use -w to limit search to last week

====== SPU-REBOOT =============================================================

Usage: spu-reboot <spu> ... Reboot SPU Use -d <database> for other databases than the standard database

====== SPU-STATUS =============================================================

Usage: spu-status -v <spu> Show status of SPU. Use -v for verbose output.

====== SPU-VALUE ==============================================================

Usage: spu-value <spu> <tdx> ... Contact SPU directly to get latest value Use -r to repeat command Use -v to display result as voltage (Only works with scalar DC) Use -d <database> for non standard database (Needed with -v)

====== SPU ====================================================================

Usage: spu <spu> <command> <argument>... Send command to SPU and display output from SPU.

The following commands are supported:

Sender_ccr - reconfigure SPU without rebooting. Takes approx. 20 seconds. Hint: Use reboot if you have disabled/deleted measurements.

reboot - reboot SPU, download software and configuration. Takes approx. 5 minutes.

Sender_getFSize - display SPU FIFO buffer usage.

start_job <tdx> - measure measurement identified by tdx. Hint: Require that measurement is defined in the current state and that the measurement is not already in the active queue.

Scheduler_jobsDump - display job queues in SPU.

Modbus_dumpCounters - display Modbus counters.

Modbus_resetCounters - reset Modbus counter.

Modbus_debugEnable <int> - enable logging in ERRORLOG: 0 DebugTiming 1 DebugInput 2 DebugQuery 3 DebugResponse -1 All of the above Hint: Extremely verbose. Use with care or the ERRORLOG will be flooded with entries.

Modbus_debugDisable <int>- disable logging in ERRORLOG.

Modbus_dump - list modbus debug setting.

MeasId_configDump <tdx> - display configuration of measurement.

Dsp_isActiveAll - display active DSPs.

Dsp_noJobs - display DSP job distribution.

Dsp_statusGet <dsp> - display DSP status.

Dsp_statusGetToFile <dsp>- store DSP status in Daustatus-<dsp>.txt.

memShow - technical memory use overview.

i - technical task status overview.

Scheduler_dumpToFile - technical dump of internal data structures of Scheduler to file scheduler.txt.

MeasId_dumpAllMeasIds - List tdx of all measurements in SPU.

MeasId_deleteAllMeasurements - Remove configuration from SPU. Warning: Depreciated.

====== SPY-EVENT ==============================================================

Usage: spy-event <tdx> <amp> Generate event and transfer it to spy For harmonics use: <sub> <amp1x>/<phase1x> <amp2x>/<phase2x>... <res> For signatures use: <amp>@<frequency> <amp>@<frequency>... Use -d <database> for other databases than the standard database Use -c <code> to specify code rather than tdx Use -r <rpm> option to add rpm value to event Use -p option to print rdm to stdout instead of sending event spy-event [-r <rpm>] [database] <tdx> [date] <amp> spy-event [-r <rpm>] -c <code> [database] [date] <amp>

====== SPY-PLAY ===============================================================

Usage: spy-play <RDM-file> Passes RDM file to SPY for playback of events Requires that SPY is running in the same directory

====== SPY-SHUTDOWN ===========================================================

Usage: spy-shutdown Passes shutdown command to SPY Requires that SPY is running in the same directory

====== SPY ====================================================================

Usage spy <server name> <spy ip address> [SPU|AD|CALC|PI|FI]

====== SQL-FILTER-INDEXES =====================================================

Usage: sql-filter-indexes <file> Tool for assisting in make database-update. Reads an sql table script file created by TOAD and displays only indexes and primary keys in a format suitable for database-update

====== SQL-FILTER-TABLE-MODS ==================================================

Usage: sql-filter-table-mods <from-file> <to-file> Tool for assisting in make database-update. Reads two sql table script file created by TOAD and displays required modifications in a format suitable for database-update

To create a file from toad use the following settings: Export -> Table Scripts with these settings only: - Include indexes in script - Primary Key with Indexes Script - Add trailing semicolons

====== SQL2PL =================================================================

Usage: sql2pl <file>Display content of sql file in a format suitable for perl

====== STATE-BEAUTIFY =========================================================

Usage: state-beautify Display beautified state expressions.

To beautify a state expression from a file: state-beautify <file>

To beautify the state expression for a machine in a database: state-beautify <machine>

To beautify all state expressions in a database and update them: state-beautify -u

Use -u to update state expressions in the database Use -f to force update without confirmation questions Use -d <database> for non-standard databases

IMPORTANT: When using state-beautify -u on a database any problems in one of the updated state expressions will go undetected until the next time it is changed by the Configurer and downloaded to the SPU. Problems will be reported in the ERRORLOG after download of the configuration.

====== STATE-CLEAR-DUPLICATES =================================================

Usage: state-clear-duplicates Delete duplicate state dependent entries from database. Use -d <database> for other databases than the standard database

====== STATE-COPY =============================================================

Usage: state-copy <machine> <state> <new-state> <meas-filter> ... Copy measurements matching filter to new state including alarm limits. E.g. to add all the measurements defined in the state Run-up to the new state Warm Run-up for the machine BFP-C:

state-copy BFP-C Run-up "Warm Run-up" %

Use -d <database> for other databases than the standard database Use -a option when you do NOT want to copy the alarm settings

Note: Last meas-filter MUST match last part of measurement name Note: In details state-copy performs the following: Verify that machine is unambigurous Verify that state is defined for the machine Verify that new-state is defined for the machine Copy all measurements from state to new-state except those already defined in new-state Copy alarm definitions from state to new-state

====== STATE-DELETE ===========================================================

Usage: state-delete <machine> <state> Delete state from machine. Use -d <database> for other databases than the standard database Note: In details state-delete performs the following: Verify that machine is unambigurous Verify that state is defined for the machine Update all relevant tables

====== STATE-INDEX-CHANGE =====================================================

Usage: state-index-change <machine> <state> <new-index> Change state index of state. Use -d <database> for other databases than the standard database

Note: In details state-index-change performs the following: Verify that machine is unambigurous Verify that state is defined for the machine Verify that new-index is not already in use for the machine Update all relevant tables except state expressions

IMPORTANT: After running state-index-change the state expression must be updated using the Configurer. Failure to do so will cause the SPU to calculate the wrong state!

====== STATE-LIST =============================================================

Usage: state-list List states for machines in configuration Use -d <database> for other databases than the standard database

====== STATE-REVISE ===========================================================

state-revise discontinued. Use state-trim instead.

====== STATE-TRIM =============================================================

Usage: state-trim -m <machine> [from] [to] Trim data in period by deleting data not supposed to be measured according to state.

state-trim is only relevant after state recalculation. E.g. following a clean up of state changes toggling between Stopped and No tacho. state-trim trims all measurements for the machine, using the state data and measurements configuration to determine if a measurement has to be deleted.

Use -f to force execution without any confirmation questions Use -d <database> for other databases than the standard database From/to must use the format yyyy-mm-dd hh:mm or yyyy-mm-dd hh:mm:ss

====== STORAGE-COMPARISON =====================================================

Usage: storage-comparison <from> <to> <tdx>... Convert data storage from database format to float Use -c <code> to check one measurement Use -m <machine> to check entire machine Use -v for verbose output Use -l to convert to long Use -Z <level> to specify compression level (1..9) Use -z to zip data Use -t to compress scalar trend data only Use -f to place BLOB in files named <tdx>-yyyy-mm-dd-hhmmss.s.dat Use -s to compress signature data only Use -r <file> to print converted data in RDM format Use -u update database (Not yet fully supported) Use -d <database> for other databases than the standard database

====== STRING =================================================================

Usage: string <text> <file> Display string containing text. Only the first occurence is shown

====== SUM ====================================================================

Usage: sum <file> ... Calculates CRC16 for each file in the argument list.

====== SYSTEM-WARNINGS ========================================================

Usage: system-warnings [from [to] ] [ tdx ... ] List system warning totals per transducer for last day for specified measurements. System warning totals for entire plant are shown when no machine/measurements are specified. Use -r for displaying range errors Use -d <database> for other databases than the standard database Use -c to display alarms for measurement system-warnings -c <code> Use -m option to display alarms for machine system-warnings -m <machine-search-string> Use -h to display data for last hour Use -w to display data for last week


====== TACHO-LIST =============================================================

Usage: tacho-list [to] List tacho parameters in configuration for import to Excel

tacho-list -v > tacholist.csv

Use -v to include max value during last day of each parameter Use -h to search last hour for value Use -w to search last week for value Use -m to search last month for value Use -d <database> for other databases than the standard database

====== TACHO-REF ==============================================================

Usage: tacho-ref <machine> Show tacho reference information for machine.

tacho-ref <machine> [tacho ref] Update tacho reference of all measurements on machine, provided they are performed by the same SPU as the tacho reference.

tacho-ref <machine> [tacho ref] [transducer] ... Update tacho reference of measurements on the specified transducers. Use -d <database> for other databases than the standard database

====== TAIL ===================================================================

Usage: tail [-f | -r] [-h] [-b number | -c number | -n number | [-+]number] [file ...] xtail [-h] file ...

====== TDX ====================================================================

Usage: tdx <meas-filter> ... List all measurements that match filter and show tdx, channel, data source and enable status (~) Use -d <database> for other databases than the standard database

====== TEST-ICP ===============================================================

Usage: test-icp [ undo ] Changes ICP setting to No ICP and stores original settings When undo is specified the original settings are restored Use -d <database> for other databases than the standard database

====== TEST-OTA ===============================================================

Usage: test-ota [ undo ] Disable OTA event window for transient states When undo is specified the original settings are restored Use -d <database> for other databases than the standard database

====== TEST-OVERLOAD ==========================================================

Usage: test-overload [ undo ] Updates configuration to ignore overload and saves original settings When undo is specified the original settings are restored Use -d <database> for other databases than the standard database

====== TEST-TACHO =============================================================

Usage: test-tacho [ undo ] Changes tacho setting to 0V and stores original settings When undo is specified the original settings are restored Use -d <database> for other databases than the standard database

====== TEST_CRASH =============================================================

====== TIME2DATE ==============================================================

Usage: time2date <time> Converts time from seconds since 1970-01-01 00:00:00 GMT into date Please observe that date is in local time

====== TIMEOUT ================================================================

Watchdog timer (pid=17132) sleeping 0 secondsWatchdog timer (pid=17132) will kill pid=0

====== TOUCH ==================================================================

Usage: touch <file>... Update access and modification time of each file to the current time. Files that do not exist will be created.

Use -a to change only the access time Use -c do not create any files Use -m to change only the modification time Use -r <file> to use this file's time instead of current time Use -t YYYYMMDDhhmm[.ss] to use this time instead of current time

====== TRANSDUCER-REPORT ======================================================

Usage: transducer-report [[from] to] Prepare transducer report. One page per transducer with a trend plot and a signature plot.

The plots shown are according to transducer type: Tachometer : Tacho and Time Displacement Probe : Spp and AS Accelerometer/Vel. : Overall and AS

When more AS have been set up the one with the lowest upper frequency is chosen. When no data are available the plot is blank.

Use -h to ignore heart beat (same as -g beta) Use -b to make black/white report Use -c to override default country for selected language Use -o <days> to change the length of the trend plot Use -g beta to ignore heart beat on plots Use -g gamma to ignore state filtering on plots Use -g epsilon to ignore all filtering on plots Use -p <path> to specify a different location for report Use -d <database> for other databases than the standard database From/to must use the format yyyy-mm-dd hh:mm

====== UI-LOG =================================================================

Usage: ui-log Display last 20 lines in User Interface log Use -d <database> for other databases than the standard database Use -n to launch Notepad with the entire User Interface log Use -a to display all lines in log

====== UI =====================================================================

Usage: ui Launch OPENpredictor User Interface. Use -d <database> for other databases than the standard database Note: Specifying a non-standard database will automatically invoke -j and -o unless -O specified Use -l to set language to one of da|de|en|es|fr|it|pt|ru|sv

Use -h to ignore heart beat (same as -g beta) Use -p <port number> Port for JavaServer Use -r for reduced bandwidth connection (same as -smlen) Use -R for remote client with reduced bandwidth (same as -smajolen)

To launch a remote reduced bandwidth User Interface in English use: ui -Rd @china

Advanced options: Use -a to skip reading warnings during program launch Use -c to override default country for selected language Use -m for mimics to skip background images Use -o to work offline without connection to Data Server Use -O to force online with connection to Data Server Note: -O only applicable with -d <database> Use -j to not setup JavaServer for acknowledgment of warnings from remote clients Use -v to skip version check Use -s to skip splash during startup Use -g beta to ignore heart beat on plots Use -g gamma to ignore state filtering on plots Use -g epsilon to ignore all filtering on plots Use -w to wait for User Interface to exit before finishing Use -D to display debug information when using Data Collector

====== UPDATE =================================================================

Usage: update Update system if new updates are available: - start installation - unzip update to work folder - look for newest update

====== UPDATESPECTRALBANDBASELINE =============================================

Unknown option: ?Update from to not specifiedUse -d <database> to specify the database to updateUse -simulate to avoid saving of baselines in databaseUse -build19to21 to update from 2.7.2 build 19 to 2.7.2 build 21Use -build21to280 to update from 2.7.2 build 21 to 2.8.0Use -build19to280 to update from 2.7.2 build 19 to 2.8.0

====== USORT ==================================================================

Unrecognized flag '-?'Usage: sort [options] [files...]Summary of options: -u Output single line for each set of lines with equal keys. ("unique") -t STR Set the field separator to string STR. -: RE Set the field separator to Perl regular expression RE. -D Enables debugging output.

-b Ignore leading whitespace. -d Ignore everything but letters, digits and whitespace. ("dictionary") -f Fold upper case letters to lower case. -i Ignore non-printable characters. -m Merge already sorted files, do not sort -n Compare fields numerically. -r Reverse the sense of comparisons.

+FIELD1[.CHAR1][bdfinr] [-FIELD2[.CHAR2]][bdfinr] Specify starting [and ending] position for sort key, counting fields and characters from 0. Ending position is first character after key. Letters specify options for current key; otherwise use global options. -k FIELD1[.CHAR1][bdfinr][,FIELD2[.CHAR2]][bdfinr] Specify starting [and ending] position for sort key, counting fields and characters from 1. Ending position is last character within key. Letters specify options for current key; otherwise use global options.

See documentation for details.

====== VALID ==================================================================

Usage: valid Request and verify authorisation from user Use -d <database> for other databases than the standard database Exit code 0 if valid Exit code 1 if unvalid

====== VALUE ==================================================================

Usage: value <tdx> ... Get value directly from data source Use -r option to repeat command Use -v to display result as voltage (Only for scalar DC on SPU) Use -d <database> for other databases than the standard database

====== VIEW ===================================================================

Usage: view <project> [file] Show contents of file from projects transfer folder. When several files match the file name specified the newest file is shown. When no file is specified the newest machine report is shown. Use -n to launch Notepad with copy of the entire file

====== WARNING-FLAGS ==========================================================

Usage: warning-flags Display setting of general warning flags

To change setting of general warning flags use: warning-flags [+|-][SYS|Performance|Maintenance|Operation|MOS|AD|IAD]...

E.g. to enable AD and IAD: warning-flags +AD +IAD


====== WARNINGS-OK ============================================================

Usage: warnings-ok <machine> ... OK all warnings for machine. Use -d <database> for other databases than the standard database Use -f to override any confirmation questions

====== WC =====================================================================

Usage: wc [option]... [file]... Print line, word, and byte counts for each file, and a total line if more than one file is specified. read standard input. -c print the byte counts -l print the newline counts -w print the word counts -a -p -m

====== WEEKLY =================================================================

Usage: weekly <weekday> <command> Execute command provided the weekday equals today

====== WHAT ===================================================================

Usage: what <file> Displays what string in file Use -s option to only print first occurence of @(#) Use -h option to perform search in hex file

====== WILD2TDX ===============================================================

Usage: wild2tdx <meas-filter> ... Display tdx matching meas filter or -1 if not found Use -d <database> for other databases than the standard database

Documents

€¦ · Web viewUsage: accel-list [to] List accelerometer parameters in configuration for import to Excel. accel-list -v > accellist.csv. Use -a to include alarm settings of Overall