Table of Contents

Mini program running effect

When your project is still under development, or you need to verify the localization effect before formal development, you can quickly preview the localization effect in real scenarios through Mega Toolbox (WeChat Mini Program). This helps you check positioning accuracy and stability, ensuring the localization service meets project requirements.

Steps to view the effect

Before viewing the real running effect, ensure you have prepared a WeChat device, have access to the WeChat mini program, and that the localization service has been configured.

Scan the Toolbox WeChat mini program QR code

Before verifying the effect, first scan the mini program QR code via WeChat to enter the Mega Toolbox application.

Mega Toolbox WeChat Mini Program

Log in to your EasyAR account

The first step to view the real running effect is logging into your EasyAR account in the mini program.

Toolbox login

Select localization database and annotation data

After logging in, you need to select the corresponding localization service and annotation data resources. This is a key step to achieve precise localization. Note: Annotation data must be selected to preview the real running effect. If the current project has no annotation data, create it first.

Follow these steps to select the corresponding services and data:

  1. Select Cloud localization service group, then choose from the dropdown.
  2. Select the corresponding Cloud localization database, then choose from the dropdown.
  3. Select the corresponding Annotation data, then choose from the dropdown. (If no annotation data exists, refer to: Create annotation data)
  4. Click Start.

Select localization database and annotation data

Authorize relevant permissions

To use the localization function normally, you need to authorize camera and location information permissions.

Authorize relevant permissions Authorize relevant permissions

View the on-site effect

Video demo:

Note

For a better visual experience, close Debug information to view the positioning visual effect of annotation content more intuitively.

Status judgment explanation:

You can judge the current localization status through the following three key indicators:

  • Annotation cube status: Displays a white MEGA texture during normal localization; displays gray when localization fails.
  • Parameters in Debug information return box:
    • status status value: Shows current localization status.
    • Sequence parameter: N indicates not loaded, F indicates localization failure, S indicates localization success.
    • Status button: Green indicates successful localization; white indicates localization failure.

The mini program displays status based on service return information, helping you understand the operation of the localization service:

  • Localization success status: If you are at the on-site location, the localization debug information shows status: Found text prompt, the Status button turns green, the Sequence parameter displays S, and the annotated cube shows a white MEGA texture normally, indicating the localization service has successfully located the target.

    View localization success effect

  • Concurrency warning: If the localization debug information shows status: QpsLimitExceeded text prompt, the Status button turns white, and the Sequence parameter displays F, it indicates the localization service is running normally, but the current QPS exceeds the limit. To resolve this, see Localization service capacity overload and expansion.

    Concurrency warning

  • Target not found status: If you are not at the on-site location or the localization database has no matching scene, the localization debug information shows status: Not Found, the Status button turns white, the Sequence parameter displays F, indicating the localization service is running normally but failed to locate the target.

    View target not found effect

  • Localization service abnormal: If the localization debug information shows UnKnownError text prompt, it indicates the localization service is running abnormally. Please enable Record logs and Record data, record the error information, and contact EasyAR customer service.