Remove the pneumatics variables from Cabinet_Configuration and move them to
Pneumatic_Box program.Because of that the program now handles onle the
cabinet monitoring. Rename the prgram to reflect that change
deleted: solution/tc_project_app/POUs/Application_Specific/Applications/Cabinet_Configuration.TcPOU
new file: solution/tc_project_app/POUs/Application_Specific/Applications/Cabinet_Monitoring.TcPOU
Add a template for safety shutter, wher ethe PSS permit signals are created.
Add a program for the Pneumatic_Box, where all the signals for pressure sensors
and pressure calcualtions are implemented.
Correct the Pneumatics_Template TaskInfo was missing a _, delete the pressurelimtis,
and add the pressure group selection.
Call the new programs from PROG() MAIN.
The variable bPSSPneumaticAxisShutter changed to bSafetyShutter
The low and high pressure limts are not defined per axis but per pressure group
in GVL_APP. Remove tehm from the template.
modified: solution/tc_project_app/POUs/Application_Specific/Axes/Pneumatics_Template.TcPOU
As all shutter OP are the same, it is safe to add the TcLinkTo attribute in the
outputs for the LEDs.
modified: solution/tc_project_app/POUs/Application_Specific/Applications/Shutter_Operator_panel_Template.TcPOU
Add getting the scaled values of the cabinet pressure groups as part of the
Cabinet_Configuration program. To later link those values for the alarms in
PILS
modified: solution/_Config/PLC/tc_project_app.xti
modified: solution/tc_project_app/POUs/Application_Specific/Applications/Cabinet_Configuration.TcPOU
modified: solution/tc_project_app/POUs/MAIN.TcPOU
Because the pressure limits belong to the cabinet and are application specific,
move the variables to GVL_APP as constants
modified: solution/tc_project_app/GVLs/GVL_APP.TcGVL
Unpin the TwinCAT verison 4024.56 and build solution with version 4024.62.
Update the tc_mca_std_lib to commit 9cfc5a1.
Build solution including the new variables from tc_mca_std_lib and new templates.
Add the comment to explain the source of the AMS NetId for the fbCabinetMonitoring.
The NetId should be from the Device (EtherCAT) of the I/O section of the solution.
Add the commented call for the fbCabinetMonitoring in MAINS/PROG().
For each declared output of the shutter OP template add the attribute
TcLinkTo. The shutter OP are always the same and will have the same
terminals name and connected to the same ouputs.
modified: solution/tc_project_app/POUs/Application_Specific/Applications/Shutter_Operator_panel_Template.TcPOU
Cabinet_Configuraiton contains the cabinet monitoring and the
pressure limits high and low for the cbainets and pneumatic boxes.
modified: solution/tc_project_app/POUs/Application_Specific/Applications/Cabinet_Configuration.TcPOU
modified: solution/tc_project_app/POUs/MAIN.TcPOU
The pressure limits are for the pressure groups and not for individual
axes therefore, the definition of those limits was move as part of the
cabinet_configuration.
modified: solution/tc_project_app/POUs/Application_Specific/Axes/Pneumatics_Template.TcPOU
Update the pointer to the commit after fixing the bug of the double
variables in ST_BacklashConfig.
Pointing now to version v2.7.0 of tc_mca_std_lib
modified: solution/tc_project_app/tc_mca_std_lib
The variable is used in the ESS's FAT_SAT_tools python scripts for
performance testing to keep track of the test number sequence.
modified: solution/_Config/PLC/tc_project_app.xti
modified: solution/tc_project_app/POUs/MAIN.TcPOU
Restructure the call to the pneumatic axes according to FB_Axes:
1. Link the axis structure for the pneumatic axes by calling the
new stPneumaticAxis property.
2. Execute the pneumatic axes.
