How to connect wio terminal with grove vision ai module v2

Products & Technology Wio Terminal
3

Here’s how AL recommend connecting the Wio Terminal to the Grove Vision AI Module V2, along with some practical caveats:

Physical Connection

  1. Use a Grove Cable
    Connect the Grove Vision AI V2 to the Wio Terminal’s Grove I²C port. The Vision module supports both UART and I²C via this port—use I²C for reliability. github.com+12wiki.seeedstudio.com+12forum.seeedstudio.com+12
  2. Power Considerations
    The I2C Grove port provides 3.3 V power, which is sufficient. Ensure a good connection—any misalignment can cause intermittent issues.
  3. Cable Order
    Plug the cable firmly so that SCL/SDA, GND, and 3.3 V line up correctly. Mis-wiring leads to the most common issues. smi

Software Setup

A) If Using UART (Bleed-through)

#include <Seeed_Arduino_SSCMA.h>
#include <HardwareSerial.h>

HardwareSerial atSerial(2); // For Wio Terminal: use UART2

SSCMA AI;

void setup() {
  Serial.begin(115200);
  atSerial.begin(921600, SERIAL_8N1, RX2, TX2);
  AI.begin(&atSerial);
}

:backhand_index_pointing_right: Replace RX2, TX2 with the correct GROVE UART pins.

If Using I²C (Recommended) this is PJ choice :grin: 

#include <Seeed_Arduino_SSCMA.h>
#include <Wire.h>

SSCMA AI;

void setup() {
  Serial.begin(115200);
  Wire.begin();         // Initialize I²C on standard SDA/SCL
  AI.begin(&Wire);      // Comm via I²C
}

Make sure you’re using the I²C Grove port, not UART. :+1:

Common Pitfalls & Tips

  • Firmware Support
    The Vision module firmware must support I²C mode. AT commands via I²C only work if the firmware includes that stack.
  • Baud Rate for UART
    If switching to UART mode, note that the default Baude is 921600—slower speeds may fail. wiki.seeedstudio.com+1github.com+1
  • Module Bootloader
    If communication fails, double-click the boot button to reflash firmware, ensuring full protocol support. wiki.seeedstudio.com

Recommended Troubleshooting Steps

  1. Use a standard Grove I²C port & cable—avoid custom wiring.
  2. In your code, begin communication with AI.begin(&Wire); after calling Wire.begin();
  3. Check the module’s firmware supports I²C AT commands.
  4. Monitor Serial logs to verify AI.invoke() results or errors.

If you still have issue’s and have verified the above. come back I have some communication test code I can post to test further, but I would bet it’s in the above somewhere. You are not the first forsure, so Stay at it and double check the connections if the hardware is updated firmware wise the only option is the connections.

I would assume you have run the basic examples for each device and can move around in your IDE and dev environment, thus far :crossed_fingers:

It’s not rocket science but does require attention to detail is all. you’ll get there.

HTH
GL :slight_smile: PJ :v: