#Abb robotstudio t gripper software
To demonstrate to the customer how the finished cell would work before installation, ABB used its RobotStudio® software to simulate the complete solution in a virtual environment, including showing the cycle time for the robot’s operations. Michey Piavantinha, Plant Director for Nestlé Caçapava, said: “Thanks to the partnership with ABB, it has been possible to develop solutions that make our manufacturing process more agile and efficient, ensuring that our products continue to have the same high level of quality and excellence that make the Nestlé brand successful.” Financial details of the contract were not disclosed. The new installation has been so successful that it has now been installed in three other Nestlé factories in Brazil, with 13 palletizing cells already in operation and further installations and commissioning underway. This allows large industrial robots to work safely and reliably alongside people, without the need for fences, safety switches, doors and locks.Īt Nestlé’s Caçapava factory, the use of SafeMove instead of fences resulted in an approximately 30 to 40 percent smaller footprint compared to previous ABB cells at the Nestlé site. SafeMove, ABB’s robot monitoring software, detects movement and restricts a robot’s speed, motion and position when a person comes near. “Collaborative robot technologies like SafeMove help us deliver on all of these requirements, and by removing the need for extensive fencing, enable us to bring automation to smaller spaces, anywhere on the production line.” At the same time, they require higher levels of productivity and efficiency while maintaining the highest levels of product quality. Sami Atiya, president of ABB Robotics & Discrete Automation, says: “Food and beverage manufacturers like Nestlé increasingly need more flexibility on their production lines to enable them to adapt to changing consumer tastes and demands, allowing their employees to collaborate intermittently with robots in their production centers. An important requirement was for the robot to safely interact with employees, who occasionally need to enter the palletizing area to speed up pallet changes.ĪBB’s new, compact robotic palletizing cell, co-developed by ABB and Nestlé’s engineering team, features an ABB IRB 660 robot with a suction gripper head to move boxes from the end of the production line to the pallet, stacking them accurately to ensure a balanced load, while SafeMove technology enables safe intermittent collaboration between the robot and production line workers. While the company currently uses ABB Robotics palletizing solutions, the latest requirement was for a more compact cell that could fit into a smaller area and easily be replicated at other sites. (See video below.)ĪBB robots are supporting Nestlé, the world’s largest food and beverage company, to improve the productivity of pallet loading in its chocolate manufacturing facilities in Brazil “by 53 percent”, using a new ABB palletizing robot solution. The company says its SafeMove collaborative robot technology “enhances employee safety while increasing efficiency at Nestle’s confectionary factories”. I can't find anything about this in the manual, so I suggest you to ask about this in the official ABB Robotics User Forum (if you haven't already done so).ABB says its robots have boosted productivity at Nestlé’s Brazilian plants by more than 50 percent. This is mainly because it is better for the robot to not have EGM active all the time.Īnyway, I just tried out some longer running scenarios with RobotStudio simulations, and it appears there is an upper limit of about 15 minutes as you have noticed. I usually start EGM, do my motions (for a few minutes maximum) and then stop EGM until I need it again. I haven't really used EGM motions for extended time periods, so I haven't noticed any upper limit for continuously running EGM. Internal supervision error occurs (e.g.references sent by the user are out of bounds). The StateMachine Add-In's default settings for this are DEFAULT_COND_MIN_MAX and DEFAULT_CONDITION_TIME.
EGM convergence criteria is fulfilled ( if I understood you correctly, then this is the same thing as the "idle timeout" you mentioned).The StateMachine Add-In's default settings for this is DEFAULT_COMM_TIMEOUT.EGM communication timeout occurs (e.g.Hi should only be the robot controller that automatically closes active EGM communication channels, for example if: