Troubleshooting Guide

This section documents common issues with Agent for LabVIEW, covering installation, activation, LLM calling, tool calling, image capabilities, and deployment scenarios. It is recommended to troubleshoot in the order: "Problem现象 -> Possible Cause -> Handling Steps".


I. Installation and Activation Issues

Problem Description Possible Cause Solution
After installation, function palette does not show VIRobotics -> AI Agent Installation package bit count is inconsistent with LabVIEW, or LabVIEW was not restarted after installation Confirm 32/64-bit consistency, reinstall .vip, restart LabVIEW
Installation error This package is not compatible... Version or bit count mismatch, VIPM version too low Upgrade LabVIEW to 2018+, VIPM to 2021+, retry in administrator mode
License shows No license Trial not applied for or activation not successful Select product in License Manager and click Apply or execute formal activation
Offline activation failed .lic does not match machine Computer ID Re-export current device Computer ID and apply for new .lic

II. LLM Chat and Streaming Issues

Problem Description Possible Cause Solution
No response from basic.vi API Key is invalid, expired, or account has no balance Re-paste Key, check service provider balance and permissions
No streaming output from stream.vi Model does not support streaming or network is unstable Switch to a model that supports streaming, check network/proxy settings
Authentication error when calling Service provider selection does not match Key Confirm that Server in LLM Keys matches Key source
Response quality fluctuates significantly Unstable prompts, inconsistent parameters Fix system prompt and parameter templates to reduce random fluctuation

III. Tool Calling Issues

Problem Description Possible Cause Solution
Tool calling not triggered Unclear tool description, missing parameter definitions Improve JSON description and parameters
Tool triggered but execution failed VI input types, paths, or dependencies are abnormal Run VI standalone first for verification, then integrate into Agent
Tool executed successfully but abnormal response Tool result return format is non-standard Align with data format required by Generate_Tool_Call_Results
Incomplete tool chain in AI_Agent_Full.vi useTools not enabled or tool directory not loaded Check useTools and confirm tool files are in the correct directory

IV. Visual Understanding and Image Generation Issues

Problem Description Possible Cause Solution
VL.vi cannot recognize images Incorrect image path or incompatible format Use absolute paths, prefer .jpg/.png, avoid Chinese paths
text_to_img_test.vi generation failed Doubao doubao-seedream not activated or API not configured Activate model in service provider backend, return to LLM Keys to complete configuration
Unstable image-to-image/fusion results Insufficient prompt constraints, low input image quality Improve input image quality and use structured prompts
Image capability interface error AI Vision Toolkit for GPU not installed Install GPU vision toolkit as per installation documentation and retry

V. Path and File Issues

Problem Description Possible Cause Solution
VI cannot find tool or model files Path concatenation error or files not in expected directory Output debug logs to check actual paths
Abnormal operation due to Chinese paths Some dependencies have poor compatibility with Chinese/space paths Use English for all paths, no spaces
Batch image reading failure Mixed file formats or inconsistent suffixes Unify image formats and filter illegal files

Troubleshooting Process Recommendations (In Order)

  1. Check authorization first: Is License normal

  2. Then check keys: Is API Key available and has balance

  3. Then check paths: Are model/tool/image paths valid

  4. Then check configuration: Model name, service provider, streaming switch, useTools

  5. Finally check logs: Record input parameters, key return values, error messages


Troubleshooting Assistance Recommendations

  • Add log records in VI to output key parameters and error codes

  • Provide Debug switch to display intermediate variables and tool return results

  • Perform pre-startup checks on external dependencies (models, tools, configurations)

Technical Support

If you still cannot resolve the issue, please contact the technical support team:

When submitting issues, please attach the following information:

  • LabVIEW version and bit count

  • Operating system version

  • Toolkit version number

  • Name of VI with issue

  • Problem screenshots and error messages

  • Reproduction steps (the more specific, the better)