Differences

This shows you the differences between two versions of the page.

--- vcs:random [2024/05/22 19:25] – [Input Channels] dsain_go-ci.com
+++ vcs:random [2024/05/22 19:32] (current) – [Test Configuration] dsain_go-ci.com
@@ Line 13: / Line 13: @@
 ===== Test Configuration =====
-The test will now need to be configured to run. This includes inputting information regarding the shaker, creating the schedule for the test to follow, and determining the parameters for the frequency analysis. To access the **Test Configuration** menu, press the **Config** button that can be found on the right side of the screen.
-{{ :vcs:2024-04-30_14-27-04.png?nolink&400 |}}
+The test will now need to be configured to run. This includes inputting information regarding the shaker, creating the schedule for the test to follow, and determining the parameters for the frequency analysis. To access the **Test Configuration** menu, press the **Config** button that can be found on the right side of the screen. {{ :vcs:2024-04-30_14-27-04.png?400&nolink }} **Shaker Parameters**\\ Click on **Edit Parameters** and enter the information from the shaker specifications. This is important for the safety of the shaker and testing unit. {{ :vcs:pasted:20240522-192613.png }}{{ :vcs:pasted:20240522-192619.png }}\\  **Test Parameters**\\ The **Test parameters** section in the **Test Configuration** window has settings for the analysis parameters, abort sensitivities and control strategy.{{ :vcs:pasted:20240522-192759.png }}\\  //Lines//- The useful number of spectral lines, proportional to block size. Increasing the lines / block size will improve the resolution of the frequency spectrum (allowing better detection of lower frequencies) at the tradeoff of increased calculation time and slower response. {{ :vcs:2024-04-30_14-31-57.png?400&nolink }} //Control Strategy//- Determines whether one or multiple control channels are used, and how the composite control signal is generated (if multiple channels are used). **Test Profile**\\ The test profile is defined in the Test Profile section of the Test Configuration window. A graphical preview of the profile plot is displayed above, with a breakpoint table below for entering the profile. CSV import / export is also supported as an alternative to profile editing.{{:vcs:pasted:20240522-192948.png}}\\ Breakpoint Table: Breakpoints can be added via **Insert row**, **Delete row** and **Append row**. Use **Clear table** to clear out all rows except for the first and last row. Breakpoint Calculation: In the profile editor, EDM can calculate the crossover point given a specified slope and point value. If a ‘?’ is entered as a Frequency or Amplitude value, EDM will interpolate that value given the slope before and after that point.\\ **RMS Limits**\\ The overall RMS level of the control channel(s) is monitored with alarm and abort limits. These limits are set under the **RMS Limits** section of the **Test Configuration** window. The table displays the expected RMS and peak values for the configured broadband profile, compared to the shaker limits as a percentage. {{:vcs:pasted:20240522-193059.png}}\\  **Run Schedule**\\ The **Run Schedule** defines how the test is run automatically through a preset routine. This schedule can support loops and periods of running at a specified level and duration. The **Run Schedule** can also include user-defined events in **Event Action Rules**. {{:vcs:pasted:20240522-193127.png}}\\  //Start a loop//- Adds a new loop to the schedule – EDM will open a prompt for how many times to loop. Double-click on an existing loop number to edit the number of times for that entry.
-**Shaker Parameters**\\ Click on **Edit Parameters** and enter the information from the shaker specifications. This is important for the safety of the shaker and testing unit.
-{{ :vcs:2024-04-30_14-27-44.png?nolink&600 |}}{{ :vcs:2024-04-30_14-28-08.png?nolink&600 |}}
+//Run at Level//- Adds a new entry to run the test profile at a specified level. Schedule duration must be specified, as well as level as a percentage or dB of the target profile.\\  {{:vcs:pasted:20240522-193137.png}}\\
-**Test Parameters**\\ The **Test parameters** section in the **Test Configuration** window has settings for the analysis parameters, abort sensitivities and control strategy.
-{{ :vcs:2024-04-30_14-31-50.png?nolink&600 |}}
-Lines: The useful number of spectral lines, proportional to block size. Increasing the lines / block size will improve the resolution of the frequency spectrum (allowing better detection of lower frequencies) at the tradeoff of increased calculation time and slower response.
-{{ :vcs:2024-04-30_14-31-57.png?nolink&400 |}}
-Control Strategy: Determines whether one or multiple control channels are used, and how the composite control signal is generated (if multiple channels are used).
-{{ :vcs:2024-04-30_14-32-04.png?nolink&400 |}}
-**Test Profile**\\ The test profile is defined in the Test Profile section of the Test Configuration window. A graphical preview of the profile plot is displayed above, with a breakpoint table below for entering the profile. CSV import / export is also supported as an alternative to profile editing.
-{{ :vcs:2024-04-30_14-34-13.png?nolink&600 |}}
-Breakpoint Table: Breakpoints can be added via **Insert row**, **Delete row** and **Append row**. Use **Clear table** to clear out all rows except for the first and last row.
-Breakpoint Calculation: In the profile editor, EDM can calculate the crossover point given a specified slope and point value. If a ‘?’ is entered as a Frequency or Amplitude value, EDM will interpolate that value given the slope before and after that point.
-{{ :vcs:2024-04-30_14-34-26.png?nolink&600 |}}
-**RMS Limits**\\ The overall RMS level of the control channel(s) is monitored with alarm and abort limits. These limits are set under the **RMS Limits** section of the **Test Configuration** window. The table displays the expected RMS and peak values for the configured broadband profile, compared to the shaker limits as a percentage.
-{{ :vcs:2024-04-30_14-38-04.png?nolink&600 |}}
-**Run Schedule**\\ The **Run Schedule** defines how the test is run automatically through a preset routine. This schedule can support loops and periods of running at a specified level and duration. The **Run Schedule** can also include user-defined events in **Event Action Rules**.
-{{ :vcs:2024-04-30_14-38-23.png?nolink&600 |}}
-Start a loop: Adds a new loop to the schedule – EDM will open a prompt for how many times to loop. Double-click on an existing loop number to edit the number of times for that entry.
-{{ :vcs:2024-04-30_14-38-30.png?nolink&400 |}}
-Run at Level: Adds a new entry to run the test profile at a specified level. Schedule duration must be specified, as well as level as a percentage or dB of the target profile.
-{{ :vcs:2024-04-30_14-38-36.png?nolink&400 |}}
 ===== Input Channels =====
 The input channels will now need to be set up. All sensors will to be properly configured before testing. The **Input Channels** menu can be found through **Setup -> Input Channels**.