Abstract: An ultrasonic transducer system has an ultrasonic transducer configured to emit ultrasonic energy in a direction and a plurality of light sources, each light source configured to emit a light beam that defines a beam pattern that intersects an axis of the emitted ultrasonic energy.

Abstract: A robotic orchard spraying system having autonomous delivery vehicles (ADV), each autonomously delivering an amount of a premixed solution over a non-overlapping path verified by a forward-looking sensor, video, or both. Also, a mobile control center, configured to wirelessly inform the autonomous delivery vehicle of the path within the areas and to confirm that the autonomous delivery vehicle is following the path within the area. Additionally, a mapper vehicle generates the path within the area, the mapper vehicle being configured to communicate information about the path and the area to the command center. The mapper vehicle senses the path with a forward-looking LiDAR sensor, and senses the area with a GPS sensor. Moreover, a nurse truck has a reservoir of premixed solution for replenishing a tank of the ADV. ADVs and the control center communicate over a radio network, which may be a mesh network, a cellular network, or both.

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.