Abstract: A system and methods for automated support for industrial robots. The system includes a data collection device which communicates with all robots at a customer site, and uploads data to a remote diagnostic system. The method is activated either automatically when an alarm occurs, or by the robot operator or a remote support team. Upon activation, particular diagnostic files are captured and sent from the affected robot's controller to the data collection device and on to the remote diagnostic system. The system employs a knowledge base to diagnose the cause of the issue from the diagnostic files, and support team personnel are also involved to reach a diagnosis. Based on the diagnosis, updated software or configuration files are sent to the affected robot to correct the issue and allow the robot to return to service, instructions are provided to the robot operator, or an on-site service technician visit is scheduled.

Abstract: A dynamic messaging system for factory automation devices that provides flexible data transport, presentation and scheduling. Custom message instructions are provided to robot controllers using configuration templates which are loadable without rebooting the controller or affecting ongoing operations of the robot. The configuration templates contain data definitions only and no executable code. Custom data messages are sent from the robot controller based on triggers, including periodic timers, transmission of a current message, change of device elements and programmatic requests. Custom message attributes such as transmission rate and priority can be set, and messages may include file attachments. A message template creator, external to the robot controller, creates the configuration templates, ensures message uniqueness and generates data ingestion schema.

Abstract: A dynamic messaging system for factory automation devices that provides flexible data transport, presentation and scheduling. Custom message instructions are provided to robot controllers using configuration templates which are loadable without rebooting the controller or affecting ongoing operations of the robot. The configuration templates contain data definitions only and no executable code. Custom data messages are sent from the robot controller based on triggers, including periodic timers, transmission of a current message, change of device elements and programmatic requests. Custom message attributes such as transmission rate and priority can be set, and messages may include file attachments. A message template creator, external to the robot controller, creates the configuration templates, ensures message uniqueness and generates data ingestion schema.