Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
vcs:sine [2024/05/01 19:43] – [Test Configuration] Added Pictures dsain_go-ci.comvcs:sine [2024/05/23 19:13] (current) – [Input Channels] dsain_go-ci.com
Line 1: Line 1:
 ====== VCS Swept Sine Testing ====== ====== VCS Swept Sine Testing ======
 +
 ==== Create New Test ==== ==== Create New Test ====
  
 To create a new test, first open up EDM. On the VCS Start Page, select **Swept Sine** under the **Create a test** tab.\\ To create a new test, first open up EDM. On the VCS Start Page, select **Swept Sine** under the **Create a test** tab.\\
-{{ :vcs:2024-05-01_11-52-51.png?nolink&400 |}}+{{:vcs:pasted:20240523-190405.png}}\\
 The **New Test Wizard** will now open up. From here, select **Swept Sine** again and then press **Next**.\\ The **New Test Wizard** will now open up. From here, select **Swept Sine** again and then press **Next**.\\
-{{ :vcs:2024-05-01_11-53-16.png?nolink&400 |}}+{{:vcs:pasted:20240523-190413.png}}\\
 Finally, give the test a name and select the Spider system that will be used to run the test. Once all is complete, press **Create**. Finally, give the test a name and select the Spider system that will be used to run the test. Once all is complete, press **Create**.
-{{ :vcs:2024-05-01_11-53-46.png?nolink&400 |}}+{{:vcs:pasted:20240523-190425.png}}\\ 
 ==== Test Configuration ==== ==== 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.\\ 
-**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-04.png?400&nolink }}  
-{{ :vcs:2024-04-30_14-28-08.png?nolink&600 |}} +**Shaker Parameters**\\  
-**Test Parameters**\\ The **Test parameters** section in the **Test Configuration** window has settings for the analysis parameters, abort sensitivities and control strategy. +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-05-01_15-17-30.png?nolink&600 |}} +{{:vcs:pasted:20240523-190703.png}}\\ 
-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 Parameters**\\  
-{{ :vcs:2024-05-01_15-23-49.png?nolink&400 |}} +The **Test parameters** section in the **Test Configuration** window has settings for the analysis parameters, abort sensitivities and control strategy.\\ 
-Sweep Type: +{{:vcs:pasted:20240523-190714.png}}\\ 
-{{ :vcs:2024-05-01_15-24-02.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).\\ 
-Measurement Strategy: + 
-{{ :vcs:2024-05-01_15-24-15.png?nolink&600 |}} +Sweep Type: //Linear// or //Logarithmic//. When the Sweep Type is Linear, the Sweeping Speed is in the unit of //Hz/Min// (Hertz per minute); When the Sweep Type is Logarithmic, the Sweep Speed can be defined in unit of //Octave/Min// or //Decade/Min//.\\ 
-**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-05-01_15-26-14.png?nolink&600 |}} +Measurement Strategy: Defines how the sine waves are measured. The selections are: Filter, RMS, Mean and Peak. In a perfect world when the sine signals have no distortion, all the measurement strategies will generate the same results. When signals are distorted, the controller will generate different drive magnitude by selecting different Measurement Strategy.\\ 
-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. + 
-{{ :vcs:2024-05-01_15-26-22.png?nolink&400 |}} +//Filter//: Only measures the energy in control frequency, ignores harmonics. This tends to under-estimate the control measurement and over-test the system. When Filter is selected, the measurement only takes the component at fundamental frequency into consideration while the energy out of band is ignored. The center of the filter follows the current sweeping frequency and Filter type and Bandwidth determine how the filter bandwidth is changing and the bandwidth, therefore, the filter is called tracking filter. When the filter type is //Proportional Filter//, the bandwidth is changing proportionally to the current sweeping frequency. When the filter type is //Fixed Filter//, the bandwidth is fixed regardless of the current sweeping frequency.\\   
-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-05-01_15-27-21.png?nolink&400 |}}{{ :vcs:2024-05-01_15-27-32.png?nolink&400 |}} +//RMS//: Calculates the total energy, including harmonics, by taking RMS in time domain (which is equivalent to RMS in frequency domain by Parseval’s Theorem). During this, the RMS calculation is scaled by 1.4x to be consistent with other measurement strategies. The “frame size” of the RMS is inversely proportional to width of tracking filter.\\   
-Segment Type:: + 
-{{ :vcs:2024-05-01_15-26-34.png?nolink&400 |}} +//Peak//: Calculates the total energy, including harmonics, by taking Peak in time domain. This tends to over-estimate the control measurement, and under-test the system, because it is possible for many sine components to peak at the same time which results in an inflated estimate.\\  
-**Check Against Shaker**\\  + 
-{{ :vcs:2024-05-01_15-27-51.png?nolink&600 |}} +//Mean//: Similar to RMS, except we take absolute value of all points in time domain and then calculate the mean.\\ 
-**Run Schedule** + 
-{{ :vcs:2024-05-01_15-27-58.png?nolink&600 |}} +**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.\\ 
-Sweep Entry: +{{:vcs:pasted:20240523-190924.png}}\\ 
-{{ :vcs:2024-05-01_15-28-04.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.\\ 
 + 
 +**Check Against Shaker**\\   
 +This tab gives the user an indication of the percentage of the shaker performance would be required during full level test, using the defined profile. The profile and alarm/abort signals are plotted above, while the peak values per current profile and the shaker limits are listed underneath. The percentage value of Profile/Shaker limits provides the user the information about what level the shaker will work per current profile.\\ 
 +{{:vcs:pasted:20240523-191035.png}}\\ 
 + 
 +**Run Schedule**\\   
 +The Run Schedule sets the sequence of test stages that will be executed when the test is run.\\ 
 +{{:vcs:pasted:20240523-191104.png}}\\ 
 +Sweep Entry: The Sweep entry types can be either a fixed frequency range at a fixed sweeping speed, or over a fixed time. Fill in the fields Time per sweep or Sweep speed according to the display: the other field will be shown with the calculated value. Selecting Test Profile (up) will begin from the lowest frequency and go towards the highest frequency, as defined by the Test Profile. Selecting Test Profile (down) will begin from the highest frequency and go towards the lowest frequency. Choosing Custom will allow to manually pick and decide the start and stop frequencies. {{ :vcs:2024-05-01_15-28-04.png?600&nolink }} 
 ==== Input Channels ==== ==== 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**. + 
-{{ :vcs:2024-04-30_14-43-17.png?nolink&400 |}} +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**. {{ :vcs:2024-04-30_14-43-17.png?400&nolink }} **Channel Type**\\ **Control** vs. **Monitor**. When running a test, there will need to be at least one control sensor. The control sensor is used to monitor the actual vibration levels that the shaker is producing. It then sends this data to the controller so that it maintains the targeted profile. This sensor should be mounted somewhere on the shaker/slip table itself, not the Device Under Test (DUT). Monitor sensors will show the levels that the DUT itself is experiencing.\\ 
-**Channel Type**\\ **Control** vs. **Monitor**. When running a test, there will need to be at least one control sensor. The control sensor is used to monitor the actual vibration levels that the shaker is producing. It then sends this data to the controller so that it maintains the targeted profile. This sensor should be mounted somewhere on the shaker/slip table itself, not the Device Under Test (DUT). Monitor sensors will show the levels that the DUT itself is experiencing. + 
-{{ :vcs:2024-04-30_14-43-59.png?nolink&400 |}} +**Measurement Quantity**\\ Defines the physical unit that will be measured by the sensor connected to the channel.\\ 
-**Measurement Quantity**\\ Defines the physical unit that will be measured by the sensor connected to the channel. +
-{{ :vcs:2024-04-30_14-44-21.png?nolink&200 |}}+
 **Sensitivity**\\ Sets the proportionality factor for the measurement (millivolts per engineering unit) given as a parameter of the sensor.\\**Input Mode**\\ There are five modes in which the inputs can operate: **Sensitivity**\\ Sets the proportionality factor for the measurement (millivolts per engineering unit) given as a parameter of the sensor.\\**Input Mode**\\ There are five modes in which the inputs can operate:
  
Line 55: Line 68:
  
 //Charge//- Some sensors provide a high-impedance charge output. Usually, these are high-sensitivity piezoelectric units that lack a built-in voltage mode amplifier (i.e. IEPE), allowing them to be used in high-temperature environments. The Spider-81 front-end module has a built-in charge amplifier that allows the system to read the output of these sensors //Charge//- Some sensors provide a high-impedance charge output. Usually, these are high-sensitivity piezoelectric units that lack a built-in voltage mode amplifier (i.e. IEPE), allowing them to be used in high-temperature environments. The Spider-81 front-end module has a built-in charge amplifier that allows the system to read the output of these sensors
-{{ :vcs:2024-04-30_14-44-49.png?nolink&400 |}}+
 ==== Running the Test ==== ==== Running the Test ====
  
Line 65: Line 78:
   - The Pre-Test will now begin. This will verify that the control loop is properly established and provide data that the control loop needs.    - The Pre-Test will now begin. This will verify that the control loop is properly established and provide data that the control loop needs. 
   - The test is now running   - The test is now running
 +
 +