I. Device Connection Issues

For detailed VinciBot connection instructions, please refer to the Link

 

1. No response when accessing Matatacode programming interface via WhatsApp or other messaging apps and clicking on USB or Bluetooth connection.

Solution: Close the page and open the link in a browser (Google Chrome recommended), or use other clients such as the desktop version, offline version, or mobile app to connect the robot.

 

2. Bluetooth connection failed?

Solutions:

① Bring the device close to the computer or tablet, start pairing, and wait until the Bluetooth indicator light stops flashing, indicating a successful connection;

② Ensure Bluetooth discovery is enabled on your computer or tablet;

③ Google Chrome is recommended.

Note: Currently not supported on Windows 7 or earlier.

 

II. Line-following Program and Color Sensor Issues

1. VinciBot cannot run the line-following program properly?

Solutions:

① Click the “Download” button to load the program into VinciBot and run it in offline mode;

② After successful download, disconnect VinciBot from the computer to ensure it operates in offline mode.

Note: Running the program in online mode may cause significant delays. Offline mode is recommended for better performance.

 

2. Line-following performance degrades after changing environments?

When the environment changes, the color sensor may still be adjusted to previous settings. Recalibration is recommended to ensure accuracy.

Solutions:

① Connect VinciBot via Bluetooth or USB, open the “Toolbox” tab, go to “Calibration Tools,” and select “Color Calibration.” Follow the prompts to calibrate the sensor carefully.

②Use a light shield to reduce environmental light interference.

 

3.Color misrecognition during line-following

VinciBot uses color values for recognition, and many colors (red, yellow, blue, green, purple) fall between black and white values. At the boundary between black and white lines, misrecognition can occur.

Solution: Implement color filtering—only confirm a color when it is recognized multiple times consecutively.

 

 

III. External Motor Malfunction or Device Reboots

1. LEGO MOTOR

①Ensure the LEGO motor is properly connected to the module (refer to link);

②Download the LEGO MOTOR driver onto the device(refer to link);

③Due to different driving mechanisms, set the motor speed between 70%–100% for reliable performance;

④Due to batch issues with the motor,If device reboots at 100% speed due to motor batch issues, set speed below 90%.

 

2. DC MOTOR

①Ensure proper connection(refer to link);

②Download the driver onto the device(refer to link);

③For third-party motors, identify the minimum operational speed and ensure speed is set above that value.

 

3.Drivers installed but still malfunctioning?

Outdated drivers may cause issues.

Solutions:

① Update VinciBot firmware to the latest version;

② Connect the device via Type-C and open the VINCIBOT USB drive;

③ Open the “extension” folder and delete “lego_motor.py,” “dc_motor.py,” and “servo.py”;

④ Re-download and reinstall the drivers for LEGO MOTOR, DC MOTOR, and SERVO.

 

IV. Camera Feed Not Available

Follow these steps (Google Chrome recommended):

① Confirm the camera is properly inserted into the extension port;

② Enable “Insecure Content” in browser settings:

·Click site settings on the left of vinci.matatastudio.com,

·select “Network Settings” → “Insecure Content” → Allow;

·Refresh the page.

   

③Disable any active network proxies

 

V. Firmware Upgrade Failure

If the upgrade fails, press and hold any button for 1 second to exit upgrade mode.Please refer to the link for firmware upgrade。

1. Low battery (battery icon with X) → Charge the device to medium or high level;。

2. Bluetooth disconnect (Bluetooth icon with X) → Reconnect and retry;

3. Incorrect WiFi credentials (WiFi icon with X) → Ensure 2.4GHz WiFi and correct password;

 

4. Cloud connection failure (Cloud icon with X) → Retry the upgrade;

 

5. Firmware installation error (Triangle with exclamation mark) → Use USB upgrade mode .(refer to link)

 

 

VI. LED Matrix Error Messages

①Script errors: Caused by logic errors or improper block usage (e.g., sending a number instead of a string).

Solution: Check for logical errors in the program.

 

②Missing motor drivers:

Solution: Connect VinciBot and download the required drivers(refer to link).

 

③Model not loaded for recognition:

Solution: Use the “Load Model and Predict Once” block to select and load the model.

 

 

④Outdated firmware limits functions:

Solution: Upgrade firmware to the latest version (refer to link).

Refer to the link for uncommon error messages and solutions.

 

VII. Infrared Remote Control Not Working

Infrared control is disabled after downloading custom programs.

To restore it:

1.Power on and connect VinciBot;

2.Open “Toolbox” → select “Restore Infrared Remote Control”;

3.Click “Start Restore”;

4.Restoration complete.

Note: This will erase the currently downloaded program.

 

VIII. “Infinite Loop” Causing Crashes

Issue: Infinite loops can overload the CPU.

Solution: Add a delay block (e.g., 0.01 seconds) inside the loop to prevent crashes.

IX. Enabling/Disabling Bluetooth

To avoid interference during competitions or multi-device use:

Disable Bluetooth:

1.Power on VinciBot;

 

2.Quickly press the power button three times;

3.Bluetooth LED off indicates Bluetooth is disabled.

Note: Rebooting re-enables Bluetooth.

 

X. Low Battery Issues

1. Inaccurate TOF distance measurements

2. Motor speed drops or restarts during high-speed operation

 

XI. Loading New Features in MatataCode

Chrome cache may block new features after firmware updates.

Force refresh recommended:

·Windows: Ctrl + Shift + R

·Mac OS: Cmd + Shift + R

For other clients (desktop, offline, app), update as prompted.

I. Device Connection Issues

For detailed connection instructions, please refer to the link.

1. No response when entering the MatataCode programming interface via WhatsApp or other communication platforms and clicking USB or Bluetooth connection.

Solution: Close the page and open the link in a web browser (Google Chrome recommended), or use the desktop client, offline client, or app to connect the robot.

 

2. Bluetooth connection unsuccessful?

Solutions:

① Bring the device close to the computer or tablet and initiate pairing. Wait for the device to confirm a successful connection;

② Ensure that Bluetooth discovery is enabled on your computer or tablet;

③ Google Chrome is recommended.

Note:

·Supported Bluetooth versions: Bluetooth 4.0 (BLE), 4.1, 4.2, and 5.0; Bluetooth 2.0 is not supported.

·System requirements:

·Windows: Must have built-in Bluetooth 4.0 or later; otherwise, use a Bluetooth 5.0 adapter.

·Mac OS: Most models are supported.

 

II. Line-following and Pressure Sensor Calibration

1.Line Sensor Color Calibration

Environmental changes affect the threshold values for color recognition. It is recommended to calibrate the sensor against white paper whenever the environment changes.

Steps:

·Insert the line sensor into the Nous HUB;

·On the HUB screen, go to Settings;

·Tap “Color Calibration”;

·Ensure the sensor faces white paper, then tap “Start” to calibrate;

·Calibration complete.

 

2.Pressure Sensor Calibration

The pressure sensor measures force via spring displacement. Zero-point calibration ensures accurate readings. Calibration must occur with the spring fully released.

Steps:

·Insert the knob and pressure sensor into the Nous HUB;

·On the HUB screen, go to Settings;

·Tap “Pressure Calibration”;

·Ensure the spring is fully released, then tap “Start”;

·Calibration complete.

 

III. Electronic Module ID Settings, Errors, and Solutions

1. Servo Motors

·ID Conflict: If two servos have the same ID, only one will appear in the device manager. Disconnect one, change the ID of the connected servo, then reconnect and reconfigure the other.

   

 

·ID Mismatch Error on Screen: If the program’s servo ID does not match the actual servo, an error will appear. Adjust either the servo ID or the program accordingly.

 

2.Other Electronic Modules

Line-following sensor, knob, pressure sensor, and ultrasonic sensor all require matching IDs.

Note: The camera module does not require an ID.

Error conditions may include:

Camera not connected

Line-following sensor not connected or ID mismatch

Knob or pressure sensor not connected or ID mismatch

Ultrasonic sensor not connected or ID mismatch

 

IV. Camera Image Feed Not Working

If the camera feed fails to load (Chrome recommended):

If the camera feed fails to load (Chrome recommended):

1.Ensure the camera is properly connected to the Nous HUB;

2.Enable "Insecure Content" in browser settings:

Step 1: On the left side of vinci.matatastudio.com, open site settings and select “Network Settings”;

Step 2: Find and enable “Insecure Content” → select “Allow”;

Step 3: Refresh nous.matatastudio.com.

3.If using a proxy, disable it.

 

V. Firmware Upgrade Issues and Solutions

For firmware upgrade instructions, refer to the link.

Problem: Entering USB drive mode instead of “Upgrade” during firmware update, and receiving a disk space error when importing the upgrade file.。

Solution: Restart the Nous HUB, enter Settings → select “Upgrade,” then drag the firmware file into the system disk and wait for the upgrade to complete.

 

VI. Program Freezes Due to “Infinite Loop” Block

Infinite loops can overload the CPU, causing the program to freeze.

Solution: Add a “Wait” block inside the loop and set the time to 0.01 seconds.

 

VII. First-Time Authorization for MatataChat and MatataDraw

To use MatataChat or MatataDraw for the first time:

1.Connect Nous HUB to MatataCode;

2.In the top menu, go to “AI” → select “Authorization Code”;

3.Click the “Authorize” icon to complete the authorization.

 

VIII. Loading the Latest Features in MatataCode

New programming features are released with each firmware update. Browser cache may prevent features from appearing.

Recommended Refresh:

·Windows: Ctrl + Shift + R

·Mac OS: Cmd + Shift + R

Other clients (desktop, offline, app) should be updated as prompted.

 

IX. Issues Caused by Low Battery in the Nous HUB

1.Low battery can reduce TOF sensor accuracy;

2.Below 20% battery, the Nous HUB will shut down automatically after 2 minutes;

3.When connected to a computer while at low battery, it may request excess current, triggering a “USB Overcurrent” warning. In this case, charge the HUB with a power adapter before reconnecting to the computer.

 

X. Servo or Motor Not Moving

1. Servo won’t move if the ID in the program doesn’t match the actual device ID.

2. Servo blocks using Chinese comma characters instead of English commas for parameters will fail.

 

3.Servo blocks with a mismatch between the number of servos and the number of parameters (e.g., speed) will not work. 

XI. Other Common Errors

1. ‘int’ object isn’t subscriptable

This Python error occurs when setting L, A, B thresholds as a single value instead of a value range in color blocks.

Correct Usage: Use a range of values instead of a fixed number.