Abstract: A virtual machine controller service of a service provider network may provide a virtual machine controller environment where applications associated with machine controllers (e.g., programmable logic controllers (PLCs), programmable automation controllers (PACs), etc.) can execute and data can be provided as input to the executing applications. An example process may include receiving a request to create a virtual controller instance, and creating the virtual controller instance in a service provider network based at least in part on the request. The example process may further include executing, on the virtual controller instance, an application that is associated with a machine controller that is operable within a facility, and sending data as input to the application to elicit a response from the application. This example process can be used for training personnel and/or for validating machine controller applications prior to their deployment on a physical machine controller in a facility.

Abstract: Controller devices may be communicatively coupled to distributed devices in a workspace. The controller devices may be positioned in various geographic locations relative to locations of the distributed devices within the workspace. Each of the controller devices may be utilized to maintain an account of, and locally control, one or more of the distributed devices. Portal devices may utilize the controller devices to manage the distributed devices by configuring, controlling, and updating the controller devices. The control devices may be utilized to establish communication channels between the portal devices and the distributed devices to provide access for a user to the distributed devices. The communication channels may be accessible to user devices based on security credentials that are modified in real-time or near real-time.

Abstract: A management system (or controller) is configured to send commands to robotic components of different types (e.g., different command types, byte order types, etc.). Once configured, a translation component may be deployed to translate some commands to some robotic components that use a different command type than a native command type used by the management system. The management system uses a native byte order type to create commands, which may be big endian or little endian. While some of the robotic components (e.g., first robotic components) may also use the native byte order type, other robotic components (e.g., second robotic components) may use a non-native byte order type (in relation to the management system). For example, the native byte order type may be big endian while the non-native byte order type may be little endian, or vice versa.

Abstract: A management system (or controller) is configured to send commands to robotic components of different types (e.g., different command types, byte order types, etc.). Once configured, a translation component may be deployed to translate some commands to some robotic components that use a different command type than a native command type used by the management system. The management system uses a native byte order type to create commands, which may be big endian or little endian. While some of the robotic components (e.g., first robotic components) may also use the native byte order type, other robotic components (e.g., second robotic components) may use a non-native byte order type (in relation to the management system). For example, the native byte order type may be big endian while the non-native byte order type may be little endian, or vice versa.