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:ui-overview:config [2026/02/13 15:29] – reid_go-ci.comvcs:ui-overview:config [2026/02/18 21:01] (current) – [Save/Recording Setup] reid_go-ci.com
Line 1: Line 1:
 =====VCS UI Config===== =====VCS UI Config=====
  
-Configuration tools are generally similar across testing types.  The displayed configuration tab is from a random test type.   +Configuration tools are generally similar across testing types.  The displayed configuration tab is from a **random test type**.   
  
-===Shaker Parameters===+====Shaker Parameters====
    
 {{::shaker_parameters.png?600|}} {{::shaker_parameters.png?600|}}
Line 44: Line 44:
 **Abort sensitivity** can be customized or scaled so that the test will either allow for testing to continue while being pushed into abort range territory for higher or lower ranges.   **Abort sensitivity** can be customized or scaled so that the test will either allow for testing to continue while being pushed into abort range territory for higher or lower ranges.  
  
-===Pre-Test Parameters===+====Pre-Test Parameters====
    
 {{::pre-test_parameters.png?600|}} {{::pre-test_parameters.png?600|}}
Line 50: Line 50:
 Before testing begins it is important to run a check to build a new FRF, or use previous FRF, based on a low input drive.  The test will also check to make sure that the test drive will not exceed shaker parameters.  Pretest drive and response level of ultimate testing excitation are adjustable to user preference. Before testing begins it is important to run a check to build a new FRF, or use previous FRF, based on a low input drive.  The test will also check to make sure that the test drive will not exceed shaker parameters.  Pretest drive and response level of ultimate testing excitation are adjustable to user preference.
  
-===Test Profile===+====Test Profile====
    
 {{::test_profile.png?600|}} {{::test_profile.png?600|}}
Line 67: Line 67:
  
  
-===Run Schedule===+====Run Schedule====
    
 Run schedule allows the user to define the testing process and resulting actions after a test is completed.  Run schedule creation follows basic logic structuring and gives users options for setting the drive level, recording times, amplifier usage, report generation, loop creation and user defined events.   Run schedule allows the user to define the testing process and resulting actions after a test is completed.  Run schedule creation follows basic logic structuring and gives users options for setting the drive level, recording times, amplifier usage, report generation, loop creation and user defined events.  
Line 75: Line 75:
 To create run schedule you simply click on the desired entry or event on the item to insert window.  Once the item is clicked it will either be inserted into schedule or parameters pop up window will display and allow you to make adjustments.  Once inserted into schedule it can be modified via the ribbon above the schedule.  The placement of the entry can also be adjusted by dragging it into the correct placement. To create run schedule you simply click on the desired entry or event on the item to insert window.  Once the item is clicked it will either be inserted into schedule or parameters pop up window will display and allow you to make adjustments.  Once inserted into schedule it can be modified via the ribbon above the schedule.  The placement of the entry can also be adjusted by dragging it into the correct placement.
  
-===Limit channels===+====Limit channels====
  
 {{::limit_channels.png?800|}} {{::limit_channels.png?800|}}
Line 91: Line 91:
 {{::event_actions_properties.png?600|}} {{::event_actions_properties.png?600|}}
    
-===Digital IO===+====Digital IO====
  
 Digital Input/Output tab gives the user the options to send output signal before running and Digital Output when schedule ends or is aborted.   Digital Input/Output tab gives the user the options to send output signal before running and Digital Output when schedule ends or is aborted.  
  
-===File Directory===+====File Directory====
  
 Allows you to control where data is stored and naming conventions of files. Allows you to control where data is stored and naming conventions of files.
  
-===Save/Recording Setup===+====Save/Recording Setup====
  
-User can define when data should be saved to system.+User can define when data should be saved to system.  
  
-===Output Settings===+Save options vary by test type to allow for greater customization of data saving. 
 + 
 +====Output Settings====
  
 Output settings give user control over which output channel should control shakers.  Additionally, it can define second output channel and relation to primary drive. Output settings give user control over which output channel should control shakers.  Additionally, it can define second output channel and relation to primary drive.
 +
 +=====Control Panel=====
 +
 +Control Panel allows users to conduct testing and acts as a shortcut to other vital testing parameter windows.  
 +
 +**Connect/Disconect**
 +
 +{{::control_panel.png?400|}}
 +
 +Will attempt to connect to selected hardware device.  Will bring control panel Online.  
 + 
 +**Run**
 +Begins Run process.  Hardware Check List will appear.
 +
 +{{::pre-test_run.png?600|}}
 + 
 +Pre-test check process will begin once you left-click OK.  Pre-test confirmation page displays testing information and gives directory location final choice.  
 +
 +{{::pre-test_success.png?600|}}
 + 
 +If the check is successful there will be no warnings displayed and you may conclude Pre-test confirmation with Proceed.
 +
 +**Pause**
 +Pause option will become active once the test run schedule begins.  It behaves as described and stops excitation.  The test will not end by clicking pause.
 +
 +**Stop**
 +This command will end the testing process.
 +
 +**Save**
 +This will save the frequency domain data from the last time block created.  The last block of time stream data which was processed will save be saved.
 +
 +**Config**
 +
 +[[config|]]
 +
 +Configuration window can be selected on the ribbon as well as through the control panel Magenta Config button.
 +
 +Configuration tools are generally similar across testing types, but there will be unique parameters for each testing type.