maintenancecenter, writer
115
edits
Difference between revisions of "ORBIGate Manual User's guide"
Jump to navigation
Jump to search
m
Making English edits. Did first half of this page so. Saving it in case it may timeout.
m (Making English edits. Did first half of this page so. Saving it in case it may timeout.) |
|||
| Line 10: | Line 10: | ||
- Choosing "Load Project" allows the user to load measurement settings. | - Choosing "Load Project" allows the user to load measurement settings. | ||
- Choosing "Load Measurement", the acquired measurement data | - Choosing "Load Measurement", will load the acquired measurement data. | ||
- Choosing "Load Signal" will allow the user to display a measurement based on a recorded signal | - Choosing "Load Signal" will allow the user to display a measurement based on a recorded signal. | ||
To get started, choose "Create New project" and press GO. | To get started, choose "Create New project" and press GO. | ||
| Line 50: | Line 50: | ||
''The analysis window configuration'' | ''The analysis window configuration'' | ||
The next step, is the set-up of the alarms: alarm conditions and alarm actions. For the getting started stage, one doesn<nowiki>’</nowiki>t need to go through that step and | The next step, is the set-up of the alarms: alarm conditions and alarm actions. For the getting started stage, one doesn<nowiki>’</nowiki>t need to go through that step and can just press next. | ||
[[Image:ORBIGate_16.png|framed|none]] | [[Image:ORBIGate_16.png|framed|none]] | ||
| Line 98: | Line 98: | ||
===Start<nowiki>’</nowiki>n Go=== | ===Start<nowiki>’</nowiki>n Go=== | ||
The Start<nowiki>’</nowiki>n Go function helps the user to immediately start the test or set-up. If a set-up has already been defined, it can be loaded at this stage. Otherwise a new project can be created. | The Start<nowiki>’</nowiki>n Go function helps the user to immediately start the test or set-up. If a set-up has already been defined, it can be loaded at this stage. Otherwise, a new project can be created. | ||
If the objective is to analyze a measurement, it can be loaded through the Start<nowiki>’</nowiki>n Go interface as shown below. | If the objective is to analyze a measurement, it can be loaded through the Start<nowiki>’</nowiki>n Go interface as shown below. | ||
| Line 106: | Line 106: | ||
''The Start<nowiki>’</nowiki>n Go window'' | ''The Start<nowiki>’</nowiki>n Go window'' | ||
In order to avoid overwriting | In order to avoid overwriting project names, the "GO" button is protected: It will automatically be grayed if an existing name is entered. | ||
If the purpose is to go through a post analysis, a signal should be loaded. The signal to be loaded should be located in the current NVGate project database. The signal should contain at least one tachometer channel recorded on the external trigger. This signal can be recorded from NVGate or ORBIGate. | If the purpose is to go through a post analysis, a signal should be loaded. The signal to be loaded should be located in the current NVGate project database. The signal should contain at least one tachometer channel recorded on the external trigger. This signal can be recorded from NVGate or ORBIGate. | ||
| Line 132: | Line 132: | ||
====Project management and operating modes==== | ====Project management and operating modes==== | ||
Projects are used to save a set-up. It | Projects are used to save a set-up. It controls both the acquisition set-up and the display set-up. | ||
Projects are saved in the directory defined at the installation and modifiable with the "environment" software. The default path is "C:\OROS\ORBIGate data\Projects". One directory is created for each saved project. | Projects are saved in the directory defined at the installation and modifiable with the "environment" software. The default path is "C:\OROS\ORBIGate data\Projects". One directory is created for each saved project. | ||
| Line 143: | Line 143: | ||
====Saving a project==== | ====Saving a project==== | ||
It is possible to save a project in different ways: either at the end of the setup wizard or through the "file menu". When switching from one mode another, it is recommended to save the project in each mode (for example, "test1 ACQ", "test1 PA", "test1 NAV") as the configuration is different. ORBIGate tracks any risks of overwriting projects when changing | It is possible to save a project in different ways: either at the end of the setup wizard or through the "file menu". When switching from one mode another, it is recommended to save the project in each mode (for example, "test1 ACQ", "test1 PA", "test1 NAV") as the configuration is different. ORBIGate tracks any risks of overwriting projects when changing modes. A project was saved in one of the three modes (Acquisition, Post Analysis, and Navigation). Then, if after changing mode one attempt to overwrite the project, the below message is displayed. It proposes either provide a new name (recommended) or gives the flexibility to overwrite the existing one (not recommended). | ||
[[Image:ORBIGate_25.png|framed|none]] | [[Image:ORBIGate_25.png|framed|none]] | ||
| Line 171: | Line 171: | ||
====Loading a measurement==== | ====Loading a measurement==== | ||
A measurement is loaded through the command "File/Load Measurement". The following window is displayed. The measurements | A measurement is loaded through the command "File/Load Measurement". The following window is displayed. The measurements can be browsed through the measurements database interface. | ||
Files can be '''sorted''' based on their: | Files can be '''sorted''' based on their: | ||
| Line 212: | Line 212: | ||
In the preferences, it is also possible to select the maximum sampling frequency allowed for the analyzer. Among others, it enables the user to limit the DSP load. | In the preferences, it is also possible to select the maximum sampling frequency allowed for the analyzer. Among others, it enables the user to limit the DSP load. | ||
It is possible to setup Post analysis signal playback speed in the user preferences: this allows controlling the post processing speed of the results. Increasing playback speed may introduce downsampling of the results collection in the measurement. | It is possible to setup Post analysis signal playback speed in the user preferences: this allows controlling the post processing speed of the results. Increasing playback speed may introduce downsampling of the results collection in the measurement. This will cause results to be collected less often. | ||
When the objective is to control the visualization speed of the results it is recommended to use the navigation mode which is designed for that purpose. | When the objective is to control the visualization speed of the results it is recommended to use the navigation mode which is designed for that purpose. | ||
| Line 227: | Line 227: | ||
''Units preferences'' | ''Units preferences'' | ||
* Trends can be displayed with the absolute time as an X-Scaling. This is especially useful when speed is not changing (steady state measurements) and when one wants to relate the vibration | * Trends can be displayed with the absolute time as an X-Scaling. This is especially useful when speed is not changing (steady state measurements) and when one wants to relate the vibration evolution's with other process phenomena (load, temperature or pressure changes). In order to get the absolute dating on the X axis, the corresponding preference should be chosen in the "preferences", as shown in the window below. | ||
{|border="2" cellspacing="0" cellpadding="4" width="100%" align="center" | {|border="2" cellspacing="0" cellpadding="4" width="100%" align="center" | ||
| Line 274: | Line 274: | ||
=====Probes connections to the analyzer inputs===== | =====Probes connections to the analyzer inputs===== | ||
Depending on the buffered outputs connections provided on the online monitoring systems, the user may have to choose between connecting the X first or the Y first. The choice is now available | Depending on the buffered outputs connections provided on the online monitoring systems, the user may have to choose between connecting the X first or the Y first. The choice is now available. | ||
[[Image:ORBIGate_39.png|framed|none]] | [[Image:ORBIGate_39.png|framed|none]] | ||
| Line 320: | Line 320: | ||
This information will be used | This information will be used | ||
- In the report edition | - In the report edition. | ||
- It also helps when "loading a machine" as keywords. | - It also helps when "loading a machine" as keywords. | ||
| Line 346: | Line 346: | ||
[[Image:ORBIGate_46.jpg|framed|none]] | [[Image:ORBIGate_46.jpg|framed|none]] | ||
|Mono points are extra sensors that come as standalone sensors. Accelerometers or velocimeters or axial proximity probes are typically used | |Mono points are extra sensors that come as standalone sensors. Accelerometers or velocimeters or axial proximity probes are typically used. | ||
|} | |} | ||
| Line 353: | Line 353: | ||
* The Machine train reload function allows loading a machine train that was saved in another project. | * The Machine train reload function allows loading a machine train that was saved in another project. | ||
* Machine train configuration and parameters reload (inputs, configuration, gap reference etc…) | * Machine train configuration and parameters reload (inputs, configuration, gap reference etc…). | ||
* Machine train search and sorting by key word: Machine train, Company, Plant, Project, Date | * Machine train search and sorting by key word: Machine train, Company, Plant, Project, Date. | ||
[[Image:ORBIGate_47.png|framed|none]] | [[Image:ORBIGate_47.png|framed|none]] | ||
| Line 378: | Line 378: | ||
|} | |} | ||
<font color="#3366FF">'''Tip:''' </font>This function is particularly useful when | <font color="#3366FF">'''Tip:''' </font>This function is particularly useful when a user switches from the acquisition mode where a signal has been saved to the post analysis mode. Once in the post-analysis mode, it is then easy to reload the machine train of the acquisition project. | ||
====Test points configuration==== | ====Test points configuration==== | ||
| Line 399: | Line 399: | ||
''The test points configuration'' | ''The test points configuration'' | ||
The default hardware input connection can be modified as in the figure below. It | The default hardware input connection can be modified as in the figure below. It allows the user for example to inverse channel Y and X if those have been connected inversely. | ||
[[Image:ORBIGate_52.jpg|framed|none]] | [[Image:ORBIGate_52.jpg|framed|none]] | ||
| Line 455: | Line 455: | ||
''The fractional tachometer type'' | ''The fractional tachometer type'' | ||
In this case, it is not necessary to measure the second tachometer. It can be simply | In this case, it is not necessary to measure the second tachometer. It can be simply calculated from the first sensor and the gear ratio. | ||
===Analysis=== | ===Analysis=== | ||
| Line 464: | Line 464: | ||
''Step 5, the analysis set up'' | ''Step 5, the analysis set up'' | ||
ORBIGate is able to | ORBIGate is able to complete several types of analysis simultaneously: Sync analysis (Order Tracking analysis for the so called NX data), ASync analysis (FFT Analysis) and Signal Recording for the raw time data recording. | ||
* Sync Analysis is referring to the Analysis Synchronous with the Rotating Speed (results coming from the SOA Analysis). There are two kinds of display X axis for the Sync spectrum: Frequency or Order. The Sync spectrum is available in the Navigation mode. | * Sync Analysis is referring to the Analysis Synchronous with the Rotating Speed (results coming from the SOA Analysis). There are two kinds of display X axis for the Sync spectrum: Frequency or Order. The Sync spectrum is available in the Navigation mode. | ||
| Line 477: | Line 477: | ||
====Sync analysis==== | ====Sync analysis==== | ||
* The "All In One" interactive settings panel has been designed to make the settings as easy as possible for the user | * The "All In One" interactive settings panel has been designed to make the settings as easy as possible for the user by displaying all available choices: | ||
* Order synchronous analysis: Max order, order resolution and selected orders | * Order synchronous analysis: Max order, order resolution and selected orders | ||
* Frequency synchronous analysis (Sync spectrum): Max frequency, Resolution | * Frequency synchronous analysis (Sync spectrum): Max frequency, Resolution | ||
| Line 513: | Line 513: | ||
''Sync, ASync, Trigger, Signal recording'' | ''Sync, ASync, Trigger, Signal recording'' | ||
The Overall level between two cut off | The Overall level between two cut off frequencies can be determined as shown in the window above. This value will be noted as "OvB AS" (it is a RMS quantity). | ||
====Trigger==== | ====Trigger==== | ||
| Line 520: | Line 520: | ||
Four different types of triggers are possible: | Four different types of triggers are possible: | ||
* Free Run: The data is saved in the array without any specific frequency specified | * Free Run: The data is saved in the array without any specific frequency specified. | ||
* Delta RPM: The data is saved in the array every increase (or decrease) of speed with a defined step | * Delta RPM: The data is saved in the array every increase (or decrease) of speed with a defined step. | ||
* Delta Time: The data is saved with a time period | * Delta Time: The data is saved with a time period. | ||
* Delta RPM or Delta Time: The data is saved with a "or" condition. It is saved every DeltaRPM steps or DeltaTime steps depending on which comes first. This trigger type is especially interesting when machines go through a start-up with a sequence of Run-up sessions and stable speeds sessions. | * Delta RPM or Delta Time: The data is saved with a "or" condition. It is saved every DeltaRPM steps or DeltaTime steps depending on which comes first. This trigger type is especially interesting when machines go through a start-up with a sequence of Run-up sessions and stable speeds sessions. | ||
| Line 535: | Line 535: | ||
''nX Recording, Delta Time sampling'' | ''nX Recording, Delta Time sampling'' | ||
'''Delta RPM''' is used to collect data every increase (or decrease) of the rotating speed | '''Delta RPM''' is used to collect data every increase (or decrease) of the rotating speed. | ||
[[Image:ORBIGate_67.jpg|framed|none]] | [[Image:ORBIGate_67.jpg|framed|none]] | ||
| Line 541: | Line 541: | ||
''nX Recording, Delta RPM sampling'' | ''nX Recording, Delta RPM sampling'' | ||
In some cases it is interesting to be able to mix the two above | In some cases it is interesting to be able to mix the two above conditions as shown in the window below. | ||
[[Image:ORBIGate_68.jpg|framed|none]] | [[Image:ORBIGate_68.jpg|framed|none]] | ||
| Line 581: | Line 581: | ||
''Alarms list'' | ''Alarms list'' | ||
The first thing to do is to give a name to the alarm. For example "AlarmStart" as displayed in the window above. There is no chronology aspect in the list: each activated alarm condition is checked permanently. | The first thing to do is to give a name to the alarm. For example, "AlarmStart" as displayed in the window above. There is no chronology aspect in the list: each activated alarm condition is checked permanently. | ||
The alarms are saved in the project. They should be configured for each project, as channels may be different from one machine to another. | The alarms are saved in the project. They should be configured for each project, as channels may be different from one machine to another. | ||
=====Alarm conditions===== | =====Alarm conditions===== | ||
An alarm is made of a condition and an action. If the condition is | An alarm is made of a condition and an action. If the condition is fulfilled, the action is started. | ||
The condition test is done for a number of: | The condition test is done for a number of: | ||
| Line 595: | Line 595: | ||
* A value | * A value | ||
It should be specified if '''all tests have to be | It should be specified if '''all tests have to be fulfilled''' or '''at least one of them should be fulfilled'''. | ||
In the example shown in the window below one should read: | In the example shown in the window below one should read: | ||
| Line 606: | Line 606: | ||
=====Alarm actions===== | =====Alarm actions===== | ||
If the alarm condition is | If the alarm condition is fulfilled, then a number of actions can be achieved (like "Start data record" as shown in the window above). | ||
====Alarm operation==== | ====Alarm operation==== | ||