Welcome to RDK X5 Board repository
4.Multimodal-Visual-Voice-Interaction
4. Multimodal Visual Voice Interaction
4. Multimodal Visual Voice Interaction1. Concept Introduction1.1 What is "Visual Understanding"?1.2 Brief Description of the Principle2. Project ArchitectureKey Code1. Tool Layer Entry (largemodel/utils/tools_manager.py)2. Model Interface Layer (largemodel/utils/large_model_interface.py)Code Analysis3. Practical Operation3.1 Configure Online LLM3.2 Start and Test the Function
1. Concept Introduction
1.1 What is "Visual Understanding"?
In the largemodel project, the multimodal visual understanding function refers to enabling the robot not just to "see" a pixel matrix, but to truly "understand" the content, objects, scenes, and their relationships within an image. It's like giving the robot a pair of thinking eyes.
The core tool for this function is seewhat. When the user issues a command like "see what's here," the system calls this tool, triggering a series of background operations that ultimately provide the user with the AI's analysis of the real-time scene in natural language.
1.2 Brief Description of the Principle
The basic principle is to input two different types of information—images (visual information) and text (language information)—into a powerful multimodal large model (such as LLaVA).
Image Encoding: The model first converts the input image into numerical vectors that the computer can understand using a Vision Encoder. These vectors capture the image's color, shape, texture, and other features.
Text Encoding: At the same time, the user's question (e.g., "What's on the table?") is also converted into a text vector.
Cross-modal Fusion: In the most critical step, the model fuses the image and text vectors in a special "Attention Layer." Here, the model learns to "focus" on the parts of the image relevant to the question. For example, when asked about the "table," the model will pay more attention to the area in the image that matches the features of a "table."
Answer Generation: Finally, a large language model (LLM) section generates a descriptive text as the answer based on the fused information.
In simple terms, it's about using text to "highlight" the corresponding parts of the image, and then using language to describe the "highlighted" parts.
2. Project Architecture
Key Code
1. Tool Layer Entry (largemodel/utils/tools_manager.py)
The seewhat function in this file defines the execution flow of the tool.
x# From largemodel/utils/tools_manager.py
class ToolsManager: # ...
def seewhat(self): """ Capture camera frame and analyze environment with AI model. :return: Dictionary with scene description and image path, or None if failed. """ self.node.get_logger().info("Executing seewhat() tool") image_path = self.capture_frame() if image_path: # Use isolated context for image analysis. analysis_text = self._get_actual_scene_description(image_path)
# Return structured data for the tool chain. return { "description": analysis_text, "image_path": image_path } else: # ... (Error handling) return None
def _get_actual_scene_description(self, image_path, message_context=None): """ Get AI-generated scene description for captured image. :param image_path: Path to captured image file. :return: Plain text description of scene. """ try: # ... (Build Prompt) # Force use of a plain text system prompt with a clean, one-time context. simple_context = [{ "role": "system", "content": "You are an image description assistant. ..." }]
result = self.node.model_client.infer_with_image(image_path, scene_prompt, message=simple_context) # ... (Process result) return description except Exception as e: # ...2. Model Interface Layer (largemodel/utils/large_model_interface.py)
The infer_with_image function in this file is the unified entry point for all image understanding tasks. It is responsible for calling the specific model implementation based on the configuration.
xxxxxxxxxx# From largemodel/utils/large_model_interface.py
class model_interface: # ... def infer_with_image(self, image_path, text=None, message=None): """Unified image inference interface.""" # ... (Prepare message) try: # Decide which specific implementation to call based on the value of self.llm_platform if self.llm_platform == 'ollama': response_content = self.ollama_infer(self.messages, image_path=image_path) elif self.llm_platform == 'tongyi': # ... Logic for calling Tongyi model pass # ... (Logic for other platforms) # ... return {'response': response_content, 'messages': self.messages.copy()}
Code Analysis
The implementation of this function involves two main layers: the tool layer defines the business logic, and the model interface layer is responsible for communicating with the large language model. This layered design is key to achieving platform versatility.
Tool Layer (
tools_manager.py):The
seewhatfunction is the business core of the visual understanding function. It encapsulates the complete flow of the "see" action: first, it calls thecapture_framemethod to get an image, then it calls_get_actual_scene_descriptionto prepare a prompt for requesting the model to analyze the image.The most critical step is calling the
infer_with_imagemethod of the model interface layer. It doesn't care which underlying model is used; it is only responsible for passing the core data of "image" and "analysis instruction."Finally, it packages the analysis result (plain text description) received from the model interface layer into a structured dictionary and returns it. This allows the upper-level application to use the analysis result conveniently.
Model Interface Layer (
large_model_interface.py):The
infer_with_imagefunction acts as a "dispatch center." Its main responsibility is to check the current platform configuration (self.llm_platform) and dispatch the task to the corresponding specific processing function (e.g.,ollama_inferortongyi_infer) based on the configuration value.This layer is the key to adapting to different AI platforms. All platform-specific operations (such as data encoding, API call formats, etc.) are encapsulated in their respective processing functions.
In this way, the business logic code in
tools_manager.pycan support multiple different backend large model services without any changes. It only needs to interact with the unified and stableinfer_with_imageinterface.
In summary, the execution flow of the seewhat tool reflects a clear separation of responsibilities pattern: ToolsManager is responsible for defining "what to do" (get an image and request analysis), while model_interface is responsible for defining "how to do it" (select the appropriate model platform according to the current configuration and complete the interaction with it). This makes the tutorial's analysis universal, and its core code logic is consistent whether the user is in online or offline mode.
3. Practical Operation
3.1 Configure Online LLM
Update the key in the configuration file and open the model interface configuration file
large_model_interface.yaml:xxxxxxxxxxvim ~/yahboom_ws/src/largemodel/config/large_model_interface.yamlFill in your API Key: Find the corresponding section and paste the API Key you just copied. Here is an example of Tongyi Qianwen configuration.
xxxxxxxxxx# large_model_interface.yaml## Tongyi Qianwenqianwen_api_key"sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" # Paste your Keyqianwen_model"qwen-vl-max-latest" # You can choose the model as needed, such as qwen-turbo, qwen-plusOpen the main configuration file
yahboom.yaml:xxxxxxxxxxvim ~/yahboom_ws/src/largemodel/config/yahboom.yamlSelect the online platform to use: Modify the
llm_platformparameter to the name of the platform you want to use.xxxxxxxxxx# yahboom.yamlmodel_serviceros__parameters# ...llm_platform'tongyi' # Optional platforms: 'ollama', 'tongyi', 'spark', 'qianfan', 'openrouter'
After modifying the configuration file, you need to recompile and source in the workspace:
xxxxxxxxxxcd ~/yahboom_wscolcon build && source install/setup.bash
3.2 Start and Test the Function
Open a new terminal and start the
largemodelmain program: Open a terminal and run the following command:xxxxxxxxxxros2 launch largemodel largemodel_control.launch.pyTest:
Wake up: Say to the microphone: "Hi,Yahboom."
Conversation: After the speaker responds, you can say:
What do you see?Observe the log: In the terminal where the
launchfile is running, you should see:The ASR node recognizes your question and prints it out.
The
model_servicenode receives the text, calls the LLM, and prints the LLM's reply.
Listen to the answer: After a while, you should be able to hear the answer from the speaker.