in mtconnect_environment.xacro: added non-articulated robotiq gripper, all path planning with this new configuration results in collision even when no objects are nearby.  Will fix
in files mtconnect_planning_description.yaml, ompl_planning.yaml,constraint_aware_kinematics.launch and ompl_planning.launch: changed all references to tip_link to use 'tcp_frame' instead of 'Link_6' to accomodate the robotiq gripper
in MoveArmActionClient.cpp: added a method 'getArmInfo' to read the arm information from the ros paameters
added robot_padding.yaml: sets the padding value used for collision checks.  It is not clear how this value is applied since planing procceeds normally even when the padding value is very large
added pick_place_robotiq_parameters.yaml: defines the parameters for the pick and place moves using the robotiq gripper frame
 hardcoded constants in header and source files under mtconnect_cnc_robot example package have been assigned to constant variables declared in the corresponding header files
modified location and thickness of the window object
modified the values for the retreat and approach distances
loads the pick_place_robotiq_parameters.yaml file for the pick & place move values
now loads robot_padding.yaml file
modified value of collision padding
removed collision item in order to enable collision checks between link 4  and the links in the robotiq gripper