FAQ
Q: Can UNO Q be developed using only Arduino IDE?
A: Yes. Arduino IDE is mainly used for MCU-side Arduino Sketch development. If you need to develop Linux applications, Python programs, AI models, graphical interfaces, or hybrid projects, Arduino App Lab is recommended.
Q: Is UNO Q compatible with UNO Shields?
A: UNO Q retains the classic UNO form factor and common pin headers, making it suitable for a wide range of UNO ecosystem expansion boards (Shields). Actual compatibility still requires checking the expansion board's electrical requirements, pin usage, and software library support.
Q: Are the GPIOs on UNO Q 5V or 3.3V?
A: The MCU GPIOs are 3.3V logic. Most GPIOs are 5V tolerant. A0 and A1 are not 5V tolerant, so special attention must be paid to the voltage range when connecting external circuits.
Q: Can UNO Q automatically run an application on boot?
A: Yes. Arduino App Lab provides an auto-start option, allowing an application to be set to run automatically on boot, suitable for standalone applications deployed in the field.
Q: How to handle a Linux computer not recognizing UNO Q?
A: First check whether the USB-C cable supports data transfer, whether the udev rules are installed, whether user permissions are set correctly, and whether the device is recognized by the system after re-plugging.
Q: App Lab can access UNO Q via IP, but the device is not visible in Network Mode. How to fix?
A: Network Mode relies on local network discovery. Please check that your computer and UNO Q are on the same local network, that the firewall allows mDNS/UDP port 5353, that client isolation is not enabled on the router, and that a VPN is not interfering with local discovery.
Q: Can UNO Q directly connect to 5V sensors?
A: The module's supply voltage and signal level need to be checked separately. Some modules can be powered with 5V, but their signal lines may still output 5V. UNO Q's MCU GPIOs are 3.3V logic; although most GPIOs are 5V tolerant, A0 and A1 are not. Before wiring, consult the module specifications and the UNO Q pinout diagram, and use level shifters or voltage dividers if necessary.
Q: What scenarios are suitable for Bridge / RPC?
A: Bridge / RPC is used when the Linux-side program needs to control peripherals on the MCU side, or when data collected by the MCU needs to be processed by the Linux side. For example, a Python program performs image recognition then instructs the MCU to control a servo, or the MCU reads sensor data and passes it to the Linux side for uploading to the cloud.
Q: How to troubleshoot when connected peripherals show no response?
A: First check whether power supply is correct, whether GND is shared, whether signal wires are reversed, whether voltage levels are compatible, whether the correct interface is selected, and whether the example code uses the correct pins. For I2C devices, also check the address; for UART devices, check TX/RX and baud rate; for SPI devices, check the CS pin.